Oracle® Fusion Middleware

Error Messages

12c (12.1.3)

E51932-05

May 2015

Oracle Fusion Middleware Error Messages, 12c (12.1.3)

E51932-05

Copyright © 2015, 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, then 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 fail-safe, 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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Conventions

1 ADF_FACES-00001 to ADF_FACES-60098

2 ADF-MF-10001 to ADF-MF-16221

3 ADF_TRINID-00001 to ADF_TRINID-30336

4 ADFC-00001 to ADFC-14018

5 ADFDI-00100 to ADFDI-55516

6 ADFF_BIND-00001 to ADFF_BIND-00046

7 ADFSHARE-00002 to ADFSHARE-00150

8 B2B-EVT-10001 to B2B-EVT-10003

9 B2B-50006 to B2B-53019

10 BEA-000001 to BEA-2163006

11 BIACM-00007 to BIACM-00082

12 CFGFWK-20836 to CFGFWK-69504

13 CLONE-20200 to CLONE-92302

14 CONF-30000 to CONF-35141

15 DFW-40000 to DFW-40210

16 DISCMAN-00100 to DISCMAN-90002

17 DMS-50700 to DMS-58075

18 DVT-02012 to DVT-26021

19 EDQ-03400 to EDQ-00651

20 EM-02801 to EM-02804

21 EPMBPMUI-00101 to EPMBPMUI-01804

22 EPMFR-00001 to EPMFR-00356

23 EPMWKSP-00101 to EPMWKSP-02508

24 HELP-00001 to HELP-40001

25 J2EE HTTPC-00004 to J2EE HTTPC-12011

26 J2EE JMX-46000 to J2EE JMX-47006

27 J2EE JSP-00002 to J2EE JSP-00302

28 JBO-24000 to JBO-80008

29 JPS-00001 to JPS-90642

30 JRF-10001 to JRF-20036

31 MCS-38601 to MCS-57840

32 MFT-02001 to MFT-08003

33 MDS-00001 to MDS-92006

34 OAAM-00000 to OAAM-94100

35 OAB-00015 to OAB-960018

36 OAM-00001 to OAM-36105

37 OAMSSA-00001 to OAMSSA-22030

38 ODI-01100 to ODI-999999

39 ODL-52001 to ODL-52816

40 OHS-03506 to OHS-04854

41 ORABPEL-00006 to ORABPEL-20511

42 ORAMED-01001 to ORAMED-09001

43 OSB-75050 to OSB-2032402

44 SOA-10000 to SOA-65070

45 SDP-25001 to SDP-26457

46 TPC-00001 to TPC-60113

47 UCM-ADF-10000 to UCM-ADF-45200

48 UCS-10106 to UCS-31204

49 UPGAST-00001 to UPGAST-00300

50 WC-05319 to WC-05370

51 WCS-03051 to WCS-90200

52 WSM-00001 to WSM-09024

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 that have purchased support 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 ADF_FACES-00001 to ADF_FACES-60098

ADF_FACES-00001: unable to create Persistent ChangeManager: {0} {1}

Cause: Could not load Persistent ChangeManager class specified in adf-config.xml

Action: Ensure that Java class specified in adf-config.xml exists in the Java ClassLoader of the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00002: no listeners for custom event: {0}

Cause: Application attempted to fire event when it never registered any listeners.

Action: Use the development tools to open the page and fix the event.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00003: Unable to mark future region component client IDs that might be added to the RegionModel as needing a redraw because it is not supported in this implementation of the RegionModel.

Cause: The RegionModel was incorrectly subclassed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-00004: Key: {0} is not of type String.

Cause: Marshalling from client to server was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-00005: >attempt to synchronize secure key: {0}

Cause: The client attempted to write to a component property that is only writable by the server.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-00006: Could not coerce key: {0} from value: {1} to type: {2}.

Cause: Renderer's client-side peer marshalled a property that the Renderer doesn't know about.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-00007: Attempt to synchronized unknown key: {0}.

Cause: Renderer's client-side peer marshalled a property that the Renderer doesn't know how to unmarshall.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-00008: A null QueryModel object was found.

Cause: The QueryCriteria had a null or invalid QueryModel or no QueryDescriptors were specified for the model.

Action: Verify that the QueryModel is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00009: Error processing viewId: {0} URI: {1} actual-URI: {2}.

Cause: An exception was thrown when processing the children of the region.

Action: Use action related to thrown exception.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00017: eventContext is set to launcher, but no launch ID is available. To use eventContext launcher the popup must be launched on the client with the hint AdfDhtmlPopupWindow.HINT_LAUNCH_SOURCE_ID set. See the popup doc for more information.

Cause: the eventContext was set to launcher, but no launch ID is available.

Action: To use eventContext launcher the popup must be launched on the client with the hint AdfDhtmlPopupWindow.HINT_LAUNCH_SOURCE_ID set. See the popup doc for more information.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00018: The launcherVar attribute is set, but the eventContext attribute is not set to launcher. LauncherVar is only made available when eventContext is set to launcher.

Cause: The launcherVar attribute was set, but the eventContext attribute was not set to launcher.

Action: Remove launcherVar attribute or set eventContext attribute to launcher.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00019: Error setting: {0} to from value: {1} for event: {2}.

Cause: The setPropertyListener encountered an error when trying to set.

Action: Check that the EL expression is correct.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00020: invokeOnComponent() is being called on the region with id {0} from inside of its RegionModel's processBeginRegion()

Cause: This happens when the RegionModel implementation calls invokeOnComponent() before returning from its RegionModel's processBeginRegion(), typically because the application has used the expression language to bind a task flow parameter to a function that call invokeOnComponent().

Action: Instead of dynamically retrieving the component state with invokeOnComponent(), stash the value in application state, where it can be retrieved directly.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_FACES-00021: The value {0} passed as identifier name to MoveChildComponentChange is not valid. Defaulting to 'id'.

Cause: This happens when a MoveChildComponentChange is constructed with a value other than 'id' for identifier.

Action: Pass 'id' as the value.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-00022: No help topic found for helpTopicId={0}.

Cause: A help topic was not found for the specified helpTopicId.

Action: Ensure a help topic is correctly configured.
Level: 2

Type: WARNING

Impact: Logging

ADF_FACES-00023: The MethodExpression wrapper of an include component was not able to locate the component after being deserialized. The expression will not be functional. Client ID not found was {0}

Cause: Method expression was not deserialized when the include for its component was in the current component tree.

Action: The method expressions of properties of include components may only be desirialized when their component trees are the current ones.
Level: 2

Type: WARNING

Impact: Logging

ADF_FACES-00024: Unable to load the display names for TimeZone: {0} in Locale: {1}.

Cause: No TimeZone information exists for this Locale.

Action: Ensure that the resource information exists for this Locale.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-10001: No representationClass provided.

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10002: wrappedEvent

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10003: Basename is null.

Cause: Application never called setBaseName().

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10004: No null numbers allowed in NumberRange.

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10005: unregistered key: {0}

Cause: An illegal argument was passed to framework.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10006: Renderer {0} is not a rich renderer.

Cause: Attempt was made to delegate rendering of a RichRenderer to a non-RichRenderer.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10007: Null value for: {0} is not allowed.

Cause: Tried to log the user activity information with null value for a non null field.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10008: Parent cannot be null.

Cause: Attempt was made to search for a child component inside a parent which is null.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10011: attempt to add a duplicate ID

Cause: Attempt was made to add a duplicate component under the destination.

Action: Ensure that destination does not already have a child with the ID of source component.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10012: Allowed actions must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10013: Attempt to unsecure an always secured attribute

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-10014: Illegal access of the include attribute map outside of the include context

Cause: An illegal attempt to access the attribute map of an include from outside of its context was made.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10015: Illegal call to setup the context of an include that is already in context

Cause: An illegal attempt to setup the context of an include component while the include was in context was made.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10016: Illegal call to tear down the context of an include that is not in context

Cause: An illegal attempt to tear down the context of an include component while the context was not set up.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10017: Setup of page template context failed due to an unhandled exception.

Cause: An unhandled exception in page template context setup.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10018: Tear down of page template context failed due to an unhandled exception.

Cause: An unhandled exception in page template context tear down.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10019: Setup of include component context failed due to an unhandled exception.

Cause: An unhandled exception in include component context setup.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10020: Tear down of include component context failed due to an unhandled exception.

Cause: An unhandled exception in include component context tear down.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10021: During the processing of the include component, the context change found did not match the current component.

Cause: DDuring the processing of the include component, the context change found did not match the current component.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10022: Attempt to resume an include component that was not suspended.

Cause: An attempt was made to resume an include component that was not suspended.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10023: readObject not supported for deserialization, SerializationProxy Required.

Cause: An attempt was made to call readObject on a class that uses a SerializationProxy, therefore readObject should never be called.

Action: Contact Oracle Support Services.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-10024: The implemementation of AdfFacesContext was not found. If this is a rich client application, it will not function. This is expected for Trinidad applications.

Cause: AdfFacesContextImpl was not found on the class path.

Action: Contact Oracle Support Services if this is a rich client application.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30001: invalid value for configuration parameter Estimated Number of Pages Per Channel: {0}

Cause: Configuration of estimated number of pages per channel in adf-config.xml has exceeded 2,147,483,647.

Action: Fix configuration of pages-per-channel to a reasonable value.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30002: invalid value: {0} specified in configuration for parameter: {1}

Cause: The active data configuration parameter from adf-config.xml was not a positive number.

Action: Fix the configuration to be a reasonable value.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30003: unknown Active Data Service action sent from the client - ignoring the request

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30006: unexpected exception when starting active data on: {0}

Cause: An error occurred in the ActiveModel implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30007: data changed notification on an unknown ActiveDataModel: {0}

Cause: An error occurred in the ActiveModel implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30008: unexpected runtime exception stopping ActiveDataModel: {0}

Cause: An error occurred in the ActiveModel implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30011: could not parse changeCount: {0} for clientId: {1}

Cause: Change count delivered by client was not a number.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30013: cannot register active data when window has no name

Cause: WindowIdProvider returned a null window name. The Auto-PPR (partial page refresh) and ADS (active data service) features will not work.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30014: no drag source for drop target: {0}

Cause: A drop occurred, but no drag source can be found.

Action: Ensure that a drag source is defined for the drop target.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30016: no drop target for drag source: {0}

Cause: Component was targeted for a drop but has no drop target.

Action: Ensure that a drop target is defined for the drag source.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30017: no listeners for custom event: {0}

Cause: Client fired a custom client event for which there are no listeners.

Action: Define a listener for the custom client event.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30018: unable to parse Active Data Service start change count: {0}

Cause: Initial change count for active data was not a number.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30022: error calling drop listener: {0}

Cause: Drop listener threw an exception.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30023: error calling drop listener: {0} on: {1}

Cause: Drop listener threw an exception.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30025: Client events for component: {0} were not in a valid form: {1}.

Cause: A parameter of a client event was marshalled as something other than a Map.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30026: The collectionDragSource: {0} can only be attached to a collection component.

Cause: CollectionDragSource was not attached to UIXCollections.

Action: Application should use a type of DragSource appropriate for this component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30027: invalid align value: {0}

Cause: The popup alignment attribute was not one of the supported values.

Action: Application should use a supported popup alignment attribute.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30028: could not find render kit: {0}

Cause: The render kit with this ID was not registered with the application.

Action: Register this render kit or use the ID of a registered render kit.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30031: error decoding color string: {0} - returning null

Cause: The value was not a supported String representation of a color.

Action: Ensure that the color string is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30032: column: {0} used outside of a table

Cause: A column was used outside of a table.

Action: Move the column inside of the appropriate table.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30036: no skin icon exists with key: {0}

Cause: The icon with this name did not exist in the skin.

Action: Ensure that the icon name is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30037: expected script element: {0}

Cause: Application requested <script> output but wrote a non-script tag.

Action: Ensure the script element is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30038: illegal component hierarchy detected

Cause: Expected UIXCommand but found another type of component instead.

Action: Ensure that the proper UIXCommand is used.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30039: Collection decorator must contain a tree, table or treeTable as its first child.

Cause: A non-tree or table component was used where tree or table was required.

Action: Ensure that the proper component is used.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30040: facet: {0} must be menu component

Cause: A non-menu component was used where menu was required.

Action: Ensure that a menu component is used.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30041: toolbar facet: {0} must be RichToolbar component

Cause: A non-toolbar component was used where toolbar was required.

Action: Ensure that a toolbar component is used.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30042: Loading popup: {0} during a full-page request is not supported.

Cause: An attempt was made to load a popup during a full-page request.

Action: Ensure that the popup is not loaded during a full-page request.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30043: no PPR-capable ID found for elements of: {0}

Cause: Application attempted to PPR an ID that does not exist.

Action: Ensure that a valid ID exists.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30044: Invalid model provided to progressIndicator (should be a BoundedRangeModel); progressIndicator ID: {0}.

Cause: The value of the progressIndicator was not a BoundedRangeModel.

Action: Use the development tools to open the page and fix the progressIndicator.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30045: Mode is null. It does not return correctly from current QueryDescriptor.

Cause: No mode was set on QueryDescscriptor.

Action: Ensure a valid mode is set.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30046: A null QueryDescriptor object was found.

Cause: Either a QueryDescriptor was not set on query component or the object provided was null or invalid.

Action: Ensure a valid QueryDesriptor is set on the query component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30047: Component of ID: {0} cannot receive a client component because it is used as a repeating separator (or a similar usage).

Cause: A ClientComponent is required where none is supported.

Action: Ensure the usage of the client component is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30048: Could not launch window, as render kit does not support the ExtendedRenderKitService.

Cause: Launching a window required the ExtendedRenderKitService, but the current render kit does not support this service.

Action: Switch the RenderKitId to point to a render kit that supports the ExtendedRenderKitService.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30049: overwriting preexisting page flow scope parameters

Cause: One of the dialog parameters conflicted with a page flow scope parameter.

Action: Ensure the parameters are valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30050: The original view root was not set.

Cause: No viewRoot was set.

Action: Check servlet filter order.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30052: The group attribute on the selectBooleanRadio component is null. It must be set to a non-null value for the selectBooleanRadio component to function properly.

Cause: No group attribute was set on selectBooleanRadio.

Action: Set the group value on the selectBooleanRadio component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30053: Skinning property key: {0} cannot be parsed as int.

Cause: The property was not an integer.

Action: Change skin property to be an integer.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30055: The number of items selected for shuttle: {0} exceeds the total number of items in the shuttle. No selected items will be returned.

Cause: State of the shuttle was corrupted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30056: Table with ID: {0} has no visible columns.

Cause: Table contains no visible columns.

Action: Add at least one visible column to the table component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30057: Table inlineStyle will be ignored because width:auto is not supported.

Cause: The inline CSS property width:auto was ignored because it is not supported on table component to control its size.

Action: Remove the inlineStyle property on the table component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30058: Table width attribute will be ignored because auto is not supported.

Cause: The attribute width=auto was ignored because it is not supported on table component to control its size.

Action: Remove the table width attribute.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30059: unknown table fetch type

Cause: The client table peer sent a fetch requests with an unknown fetch type.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30060: Either a MenuModel object was not provided or an invalid object was provided.

Cause: The train component required a value of type MenuModel.

Action: Correct the train definition.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30061: The model provided for the train has no stops.

Cause: No train stops were supplied for the train component model.

Action: Check to see if the model is set up correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30062: The parent stop label was null for the stop: {0}

Cause: The parent stop label was null.

Action: Add a stop label.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30063: The nodeStamp facet on treeTable: {0} is missing or not of type UIXColumn.

Cause: No nodeStamp facet was specified on treeTable.

Action: Specify a nodeStamp facet on the treeTable.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30064: illegal value: {0} for: {1}

Cause: The table banding interval must be >= 0.

Action: Ensure the brandng interval is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30065: The nodeStamp facet on treeTable: {0} is missing or not of type UIXColumn.

Cause: The nodeStamp facet of a treeTable was invalid. It only supports components of type UIXColumn.

Action: Ensure a correct nodeStamp facet is defined.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30066: no registered FacesBean.Type for family: {0} type: {1}

Cause: No FacesBean was registered for this componentFamily and rendererType.

Action: Use a render kit that supports this componentFamily and rendererType.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30067: Multithreaded execution was interrupted.

Cause: Execution of the multithreaded streaming request was interrupted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30068: multithreaded execution exception

Cause: The model threw an exception during multithreaded rendering.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-30071: The collection component with ID: {0} cannot be found inside the component.

Cause: No component with the specified ID was found inside the popup.

Action: Specify a valid component ID.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30072: The component with ID: {0} is not a collection component.

Cause: The collection popup content was not a collection component.

Action: Ensure the popup content is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30073: The collection return listener {0} must be inside of a UIComponent tag.

Cause: The collection return listener was not inside of a UIComponent tag.

Action: Ensure that the collection return listener is inside of a UIComponent tag.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30074: The returnActionListener must be inside of an input popup component.

Cause: The returnActionListener tag was not inside of a tag that created an input popup component.

Action: Correct the returnActionListener .
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30075: Could not find parent include tag for definition: {0}.

Cause: Could not find the tag that included the definition tag.

Action: Ensure that the include tag is defined properly.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30076: Component: {0} must be included as a child of an include tag.

Cause: The parent component of a pageTemplateDef or componentDef tag must be extend UIXInclude.

Action: Ensure that the pageTemplateDef or componentDef is the child of an include tag.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30077: Time-stamp checking enabled for faces component metadata. Do not use in a production environment. property:oracle.application.environment=development

Cause: Application configured to run in development mode.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_FACES-30078: Attribute: {0} is missing on component with ID: {1} in file: {2}.

Cause: A required component attribute is not specified.

Action: Ensure all attributes are defined.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30079: error parsing component tag in file: {0}

Cause: The metatdata for the page template or include component contained an error.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30080: unknown element:{0} at: {1}

Cause: The metadata for the include contained an unknown XML element.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30081: Attribute: {0} is missing at: {1}.

Cause: The include metadata attribute name was not specified.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30082: exception at: {0}

Cause: An exception occurred when parsing the include metadata.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30083: Component: {0} with ID: {1} cannot have children.

Cause: Attempt was made to add a componentRef tag under a component that cannot have children.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30084: Could not get RequestDispatcher for viewId: {0} and uri: {1}.

Cause: The JSP to include could not be found.

Action: Verify that the JSP exists at the specified location.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30085: The facetRef must be inside af:pageTemplateDef or af:componentDef.

Cause: The facetRef tag was used outside of a f:pageTemplateDef or af:componentDef tag.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30086: Cannot find parent include component.

Cause: Cannot find parent include component.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30087: Encountered null from the viewId expression: {0}.

Cause: The URI of the include was null.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30088: Cannot find closing ">" in: {0}.

Cause: XmlContentTag is missing an end tag.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30089: Cannot parse root element in: {0}.

Cause: No root element was started on XmlContentTag.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30090: Could not find root element in: {0}.

Cause: XmlContentTag had no root element.

Action: Use the development tools to open the include and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30091: Could not compute the namespace for element: {0} with prefix: {1} in: {2}.

Cause: No XML namespace found for prefix.

Action: Ensure the namespace is properly defined.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30093: error while loading library: {0}

Cause: IE Exception occurred when attempting to load the deferred library.

Action: Ensure that the library is at the specified location.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30094: unable to get resource: {0}

Cause: Specified resource was not found in classpath.

Action: Ensure that the resource is present in the classpath.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30095: Marshalling of StateHolders not yet supported; skipping: {0}.

Cause: Marshalling of StateHolders not supported and was skipped.

Action: Use the development tools and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30096: Unmarshaling of StateHolders not yet supported.

Cause: Unmarshaling of StateHolders not supported.

Action: Use the development tools and fix the problem.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30097: rich text parse error at position: {0}, unterminated element: {1}

Cause: A rich text value was encountered with an unexpected unterminated element.

Action: Ensure that the tags for this element get terminated.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30098: rich text parse error at position: {0}, unclosed element: {1}

Cause: A rich text value was encountered with an element that requires a closing tag but no closing tag was provided.

Action: Ensure that this element gets a closing tag.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30099: rich text parse error at position: {0}, unsupported element: {1}

Cause: A rich text value was encountered with an element that is not supported.

Action: Do not use this element.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30100: rich text parse error at position: {0}, unterminated attribute name

Cause: A rich text value was encountered with an attribute name that was not terminated.

Action: Ensure that this attribute name gets terminated.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30101: rich text parse error at position: {0}, unterminated value for attribute: {1}

Cause: A rich text value was encountered with an attribute value that was not terminated.

Action: Ensure that this attribute value gets terminated.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30102: The rich text editor is not supported in the specified agent: {0}.

Cause: An attempt was made to use the rich text editor component in an unsupported web browser.

Action: Ensure that the browser used is supported by this rich text editor component.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30107: The view state of the page has expired. Reload the page.

Cause: The UI state of the view has expired, either because the back button has been used too many times, too many page submissions have occurred on ther pages, or because of an underlying bug in the view code.

Action: The application using ADF should install an ADFc error handler for JSF ViewExpiredExceptions, or configure the org.apache.myfaces.trinidad.CLIENT_STATE_MAX_TOKENS web.xml parameter to a larger value.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30108: The view state of the page has expired because of inactivity. Reload the page.

Cause: The UI state of the view has expired because the session has expired.

Action: The application using ADF should install an ADFc error handler for JSF ViewExpiredExceptions.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30109: Conversion failed while trying to synchronize value from client. Attempted to convert: {0}, Component ID: {1}.

Cause: An attempt was made to set a value on the client that could not be converted on the server.

Action: Make sure application setting legal value on client.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30110: export requires HTTP Servlet

Cause: Export operation failed; it is supported only with an HTTP Servlet.

Action: For exporting content, ensurethat HTTP Servlet is available.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30111: Collection with the ID: {0} is not supported by exportCollectionActionListener.

Cause: exportCollectionActionListener used with invalid collection.

Action: Ensure that the exported component is table, tree or treeTable.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30112: Export type: {0} is not supported by exportCollectionActionListener.

Cause: Unsupported export type was specified.

Action: Use one of the supported export types as specified in exportCollectionActionListener tag documentation.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30113: Exported collection with the ID of: {0} was not found.

Cause: Exported collection with the specified ID was not found.

Action: Ensure that the correct ID is specified.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30114: The converter supplied for inputDate with ID: {0} is not an instance of javax.DateTimeConverter: {1}. This input field will only support showing dates. To get time and/or timezone support, subclass the converter from javax.DateTimeConverter.DateTimeConverter or obtain the converter using Application.createConverter (preferred).

Cause: The supplied converter was not a subclass of javax.DateTimeConverter.

Action: Use the converter supplied by javax.faces.application.Application.createConverter, or make the custom converter subclass javax.DateTimeConverter.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30115: The converter supplied for InputDate with ID: {0} does not implement the ClientConverter interface: {1}. The input field will not support client conversion or validation, and only the input field will be displayed (no date-picker popup). To get client conversion and validation support, implement the org.apache.myfaces.trinidad.convert.ClientConverter interface or obtain the converter using javax.faces.application.Application.createConverter (preferred). If you just want to set the converter pattern programmatically, obtain it using createConverter and call setPattern() on it.

Cause: The supplied converter does not implement the ClientConverter interface.

Action: Use the converter supplied by Application.createConverter, or make the custom converter implement org.apache.myfaces.trinidad.convert.ClientConverter.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30116: User activity information for the {0} request is not available.

Cause: User activity Information was null when logging this information to monitoring service.

Action: Ensure that user activity information is not null when monitoring service is enabled.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30117: Component cannot be located by the ID: {0}.

Cause: Component was not found when trying to callback for component using client ID of component.

Action: Ensure that it has been invoked with correct client ID.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30118: No help provider found for helpTopicId={0}.

Cause: A help provider was not found for the specified helpTopicId.

Action: Ensure a help provider is correctly configured.
Level: 2

Type: WARNING

Impact: Logging

ADF_FACES-30120: More than one af:skipLinkTarget found: {0}. Only one af:skipLinkTarget is allowed per page.

Cause: Multiple af:skipLinkTargets were found.

Action: Remove af:skipLinkTarget so that only one is specified per page.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30121: No af:document ancestor for af:skipLinkTarget in component: {0}. af:skipLinkTarget must be used in conjunction with af:document.

Cause: Missing af:document ancestor for af:skipLinkTarget.

Action: Remove af:skipLinkTarget, or move inside of an af:document.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30122: Invalid parent for af:skipLinkTarget in component: {0}. af:skipLinkTarget must placed inside of a component that generates content.

Cause: af:skipLinkTarget must be placed inside of a component that generates content.

Action: Remove the af:skipLinkTarget, or move it inside of a parent which generates content.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30123: Invalid facet size for af:panelStretchLayout: {0}. {1} is not a valid CSS length.

Cause: An invalid value was specified for a panelStretchLayout size (topHeight, bottomHeight, startWidth, endWidth) attribute.

Action: Specify valid CSS lengths for the panelStretchLayout size (topHeight, bottomHeight, startWidth, endWidth) attributes.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30124: Multiple forms detected on viewId: {0}. Rich client currently has some limitations in dealing with multiple forms.

Cause: An ADFFaces page was detect with multiple forms on the same page. Currently there are a number of issues associated with multiple forms on the same page and this should be done with caution.

Action: Reorganize page so that it contains only one form.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30125: Exported rows type: {0} is not supported by exportCollectionActionListener.

Cause: Unsupported exported rows type was specified.

Action: Use one of the supported exported rows types as specified in exportCollectionActionListener tag documentation.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-30126: File name: {0}, Message: {1}

Cause: An error was detected while parsing a feature/partition configuration file.

Action: Verify that the feature/partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30127: Line: {0}, Column: {1}, Error: {2}

Cause: An error was detected while parsing a feature/partition configuration file.

Action: Verify that the feature/partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30128: File name: {0}, Line number: {1}, Column number: {2}, Error: {3}

Cause: An error was detected while parsing a feature/partition configuration file.

Action: Verify that the feature/partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30129: Ignoring feature element because missing feature-name.

Cause: A feature element was missing a required feature-name child.

Action: Verify that the feature configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30130: Ignoring feature-dependency on feature "{0}". No such feature exists.

Cause: A feature-dependency specified a dependency on a feature which does not exist.

Action: Verify that the feature configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30131: Ignoring partition element because missing partition-name.

Cause: A partition element was missing a required partition-name child.

Action: Verify that the partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30132: Ignoring feature element "{0}". No such feature exists.

Cause: A partition element contained an unknown feature.

Action: Verify that the partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30133: A circular dependency between partitions has been detected: {0} Library partitioning will be disabled.

Cause: A circular dependency exists between partitions.

Action: Verify that the partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30134: Partition "{0}" ({1}) depends on partition "{2}" ({3}).

Cause: A circular dependency exists between partitions.

Action: Verify that the partition configuration file is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30135: request for unknown partition: {0}

Cause: A request was made for an unknown partition.

Action: Verify that the partition configuration is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30136: Feature "{0}" is not contained in any partition.

Cause: A request was made for an unknown feature.

Action: Verify that the feature/partition configuration is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30137: Unable to service request for resource: {0}. FacesContext not available.

Cause: The partition resource loader was unable to obtain a FacesContext.

Action: Check the logs for other exceptions/errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30138: Ignoring AdfBootstrap feature in partition {0}. The AdfBootstrapFeature must reside in its own partition.

Cause: A partition was defined which contains both the AdfBootstrap feature as well as other features.

Action: The AdfBootstrap feature should be moved to its own partition.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30139: Could not find the component with relative ID {0} from {1}. This method will try to locate the component for the given ID by calling findComponent on its parent NamingContainer as a final attempt.

Cause: The identifier provided did not account for NamingContainers properly.

Action: Ensure that the relative ID specified is correct and the component with that ID exists.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30140: The slider component with label {0} has too many ticks that are rendered. This will have a huge performance impact.

Cause: The provided minimum is too small or the provided maximum is too large.

Action: Provide a better range for the slider by modifying the maximum and/or minimum attributes.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30141: Unable to remove the criterion with rowKey {0} because a criterion with the specified rowKey could not be located.

Cause: This could happen if an attempt is made to remove an already removed criterion and likely in slow performing applications

Action: Ensure that criterion fields are removed only once.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30142: Component {0} has attribute {1} with type {2}. The attribute should be of type {3}.

Cause: The value supplied for the attribute is returning a wrong type.

Action: Check the method that returns the value for the attribute and correct its type.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30143: A circular dependency between features has been detected: {0} Library partitioning will be disabled.

Cause: A circular dependency exists between features.

Action: Verify that the feature configuration files are valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30144: Feature "{0}" depends on feature "{1}".

Cause: A circular dependency exists between features.

Action: Verify that the feature configuration files are valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30145: A duplicate definition for the feature "{0}" has been found at {1}, line {2}. A feature with the same name was originally defined at {3}, line {4}. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.

Cause: This occurs when there are multiple copies of a jar file containing the same adf-js-features.xml on the class path. Or, alternatively, this may come up if different adf-js-features.xml use the same feature name.

Action: Check for multiple copies of the jar containing the feature definition on the class path. Or, check to see whether feature names are unique.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30146: The calendarDropTarget: {0} can only be attached to a calendar component.

Cause: CalendarDropTarget was not attached to UIXCalendar.

Action: Application should use a type of DragSource appropriate for this component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30147: The converter supplied for InputColor with ID: {0} does not implement the ClientConverter interface: {1}. The input field will not support client conversion or validation, and only the input field will be displayed (no color-picker popup). To get client conversion and validation support, implement the org.apache.myfaces.trinidad.convert.ClientConverter interface or obtain the converter using javax.faces.application.Application.createConverter (preferred). If you just want to set the converter pattern programmatically, obtain it using createConverter and call setPattern() on it.

Cause: The supplied converter does not implement the ClientConverter interface.

Action: Use the converter supplied by Application.createConverter, or make the custom converter implement org.apache.myfaces.trinidad.convert.ClientConverter.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30148: The supplied converter {1} with ID {0} does not implement the ClientConverter interface. The input field will not support client conversion or validation. Only normal string to number conversion will be supported, such as "5" to 5, but not "five" to 5. To get client conversion and validation support, implement the org.apache.myfaces.trinidad.convert.ClientConverter interface or obtain the converter using javax.faces.application.Application.createConverter (preferred). If you just want to set the converter pattern programmatically, obtain it using createConverter and call setPattern() on it.

Cause: The supplied converter does not implement the ClientConverter interface.

Action: Use the converter supplied by Application.createConverter, or make the custom converter implement org.apache.myfaces.trinidad.convert.ClientConverter.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-30149: No PartitionManager found, possibly due to passivation or failover. Re-creating the PartitionManager.

Cause: The PartitionManager object is null, either due to passivation or failover.

Action: No action required. The PartitionManager will be re-created.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_FACES-30150: Unable to parse Date: {0}.

Cause: There was an error parsing the date string sent from the client.

Action: The date string must be set in the proper format.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30151: The {0} facet is not returning a popup.

Cause: The facet is not returning a popup. Only popups are accepted for the Calendar facets.

Action: Check the facet to make sure it contains a popup.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-30152: The Calendar Toolbox Layout contains 'all' as well as built-in value {0}. 'all' will be used.

Cause: If the toolboxLayout contains 'all', the other built-in values should not be used.

Action: Correct the toolboxLayout attribute to specify 'all' or the built-in value desired.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30153: Unable to find facet corresponding to Calendar custom toolboxLayout value {0}.

Cause: A custom value was encountered for the toolboxLayout but no corresponding facet was found.

Action: Check that the facet has been added and that its name matches the value specified in toolboxLayout.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-30154: No providerId was supplied for activity {0}. Provider Id is required.

Cause: A null value was supplied for the activity's providerId.

Action: Check the activity source and ensure the providerId is not null.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-30155: No activityId was supplied for activity {0}. Activity Id is required.

Cause: A null value was supplied for the activity's activityId.

Action: Check the activity source and ensure the activityId is not null.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-30156: The ALLDAY activity {0} has an invalid start and end date and it may not render correctly. See the CalendarActivity Javadoc for information about valid values for startDate and endDate for an ALLDAY activity.

Cause: A null value was supplied for the activity's activityId.

Action: Check the activity source and ensure the activityId is not null.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30157: The ChooseColor component with client id {0} has width {1} which is too large. This will have a huge performance impact. In Design mode, the component will render with maximum width {2}

Cause: The provided width is too large.

Action: Reduce the width attribute of the component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30158: No af:document ancestor for af:resource for the component: {0}. af:resource must be used in conjunction with af:document.

Cause: Missing af:document ancestor for af:resource.

Action: Remove af:resource, or move inside of an af:document.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30159: Invalid value {0} specified for the oracle.adf.view.rich.SUPPRESS_IDS context parameter.

Cause: Invalid value specified for the oracle.adf.view.rich.SUPPRESS_IDS context parameter.

Action: Check web.xml file to verify that a valid SUPPRESS_IDS value is specified.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30160: Invalid value {0} specified for calendar attribute 'availableViews'.

Cause: The value specified for calendar attribute 'availableViews' was not recognized.

Action: Correct the 'availableViews' attribute to one of the following: all, day, week, month, list
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30161: The availableViews attribute contains 'all' as well as built-in value {0}. 'all' will be used.

Cause: If availableViews contains 'all', the other built-in values should not be used.

Action: Correct the availableViews attribute to specify 'all' or the built-in value desired.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30162: The 'view' attribute {0} does not correspond to one of the built-in availableViews. The calendar will display {1}.

Cause: The 'view' attribute should correspond to one of the views specified in 'availableViews'. If 'availableViews' is unspecified or set to 'all', the 'view' attribute should be one of the built-in views: day, week, month, list.

Action: Correct the 'view' attribute to be one of the views displayed in 'availableViews'.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30163: The application is running with the new window detect flag off. It is highly recommended that this flag be turned on to ensure proper functioning of your application when new browser windows are launched. In web.xml set the context parameter oracle.adf.view.rich.newWindowDetect.OPTIONS to 'on'.

Cause: When new window detection is turned off, browser window dialog may not work as expected.

Action: Trun on new window detection by adding context paramter oracle.adf.view.rich.newWindowDetect.OPTIONS to web.xml with a value of on.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30164: {0} should be defined for varyElement in caching rule.

Cause: one of the parameter undefined for varyElement.

Action: define all the parameters for varyElement.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30165: No expression defined for cache-key-pattern.

Cause: No expression defined for cache-key-pattern.

Action: Define expression for cache-key-pattern.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30166: No cache-key-pattern defined for caching-rule.

Cause: no cache-key-pattern defined for caching-rule.

Action: Define cache-key-pattern for caching-rule.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30167: No rule defined for caching.

Cause: No rule defined for caching.

Action: Define rule for caching.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30168: No keys defined for Search-Key.

Cause: No keys defined for Search-Key.

Action: Define keys for Search-Key.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30169: No vary-element defined for VaryBy element.

Cause: No vary-element defined for VaryBy element.

Action: Define vary-element for VaryBy element.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30170: Suppressing Cache header overwriting-- {0}: {1}.

Cause: Suppressing Cache header.

Action: Do not override cache header.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_FACES-30171: WEB CACHE is installed ahead of Application Server.

Cause: WEB CACHE is installed ahead of Application Server.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_FACES-30172: Unable to include contents for region {0}. FaceletContext unavailable.

Cause: This is an unexpected condition which may be due to an ADF Faces bug.

Action: Contact Oracle Support Services.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-30173: deprecated configuration element: parameter: use-polling is replaced by parameter: transport

Cause: The active data configuration parameter from adf-config.xml is deprecated.

Action: Fix the configuration to be a reasonable value.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30174: An invalid or null contextId was provided when logging userActivity information for the previous request.

Cause: This may occur if the previous response sent to the client included a null contextId or an error occurred in the client when retrieving the userActivity info.

Action: None.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30175: A null contextId was returned by the service provider implementation for the ExecutionContextProvider.

Cause: A null contextId was returned by the ExecutionContextProvider implementation.

Action: Ensure that a proper service provider has been registered in META-INF/services.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-30180: Circular dependency detected in the geometry management configuration of component id {0}.

Cause: The component has an attribute assignment that resulted in a circular dependency.

Action: See the geometry management section of that component's tag documentation for more information.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60001: ActiveDataModel is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60002: attempt to register component for STATIC ActiveDataPolicy

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60003: Component with ID: {0} not registered for Active Data.

Cause: Component was not registered properly.

Action: Register the component for Active Data.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60004: ActiveDataModel is not registered.

Cause: The activeDataModel was not registered.

Action: Register the activeDataModel.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60005: <help-provider-class> is required and must come first.

Cause: Online help was configured without first configuring the help-provider-class.

Action: Provide the help-provider-class in adf-config.xml.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60006: Request has not begun.

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60007: Phase {0} has already passed; at least at phase {1}.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60008: Attribute name required.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60009: dropHandler required

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60010: allowed actions required

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60011: Allowed actions must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60012: Single quotes and single quote escaping is not permitted in keys.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60013: End of pattern not found.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60014: NamedMessageFormat: empty argument {} found.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60015: Must have a drop component.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60016: Must have parameters.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60017: Cannot retrieve drop action until DropTarget has been called.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60018: clientActions out of range

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60019: illegal character

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60020: DnDAction.NONE not allowed in Set<DnDAction>.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60021: No DnDActions specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60022: Cannot add null DataFlavor to allowed flavors.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60023: Component: {0} does not support client listeners.

Cause: An invalid client listener was encountered.

Action: Use the development tools to open the page and fix the client listener.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60024: Component: {0} does not support client attributes.

Cause: Only UIXComponents support client attributes.

Action: Use the development tools to open the page and fix the component.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60025: Error trying to change index from: {0} to: {1} rowCount: {2}.

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60026: Path contains a null rowKey.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60027: unexpected navigationPane hint: {0}

Cause: An invalid navigationPane hint was encountered.

Action: Use the development tools to open the page and fix the navigationPane component.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60028: targetComponent must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60029: Fetch constraint:{0} must be serializable if specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60030: Fetch ClientEvent must not specify component.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60031: No returnId is available for returning from the dialog.

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60032: Could not find ExtendedRenderKitService.

Cause: Render kit does not support the ExtendedRenderKitService.

Action: Use a render kit that does support the ExtendedRenderKitService.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60033: The index {0} of the submitted value for selectOne is out of bounds. It should be between 0 and {1}.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60034: SelectOne could not convert index {0} of submitted value into int {1}.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60035: Component {0} does not support a collection indexed by rowKeys.

Cause: A component was found with an invalid index.

Action: Use the development tools to open the page and fix the component.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60036: bad PhaseId: {0}

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60037: ClientId must be specified.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60038: Component ID parameter is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60039: AsyncFetch model parameter is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60040: AsyncFetcher is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60041: Phase {0} has already started or passed; at least at phase {1}.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60042: Cannot recursively nest {0} elements.

Cause: These elements were recursively nested.

Action: Use the application development tools to correct this issue.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60043: {0} is null.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60044: not nested in FacesTag: {0}

Cause: Parent tag was not a FacesTag.

Action: Use the development tools to ensure the tags are correct.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60045: Parent UIComponent instance is null.

Cause: Parent FacesTag had no UIComponent.

Action: Use the development tools to ensure the tags are correct.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60046: unknown render kit ID: {0}

Cause: No render kit with this ID was found.

Action: Register a render kit with a correct ID.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60047: Iterator cannot be null.

Cause: Iterator was found to be null.

Action: Use the development tools to ensure the iterator is properly defined.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60048: JavaScript does not support null keys.

Cause: A null key was found in the JavaScript.

Action: Use the development tools to correct the JavaScript.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60049: rowKeys cannot be null.

Cause: A null row key was found.

Action: Use the development tools to correct the problem.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60050: ActionListener: {0} must be inside of a UIComponent tag for a command component.

Cause: An error was found in the JSP page metadata.

Action: Use the development tools to correct the ActionListener.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60051: Invalid width: {1} specified on column: {0}.

Cause: A column was found with an invalid width.

Action: Use the development tools to open the page and fix the column.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60052: Invalid minimumWidth: {1} specified on column: {0}.

Cause: A column with an invalid minimum width was encountered.

Action: Use the development tools to open the page and fix the column.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60053: rich text parse error at position: {0}

Cause: A rich text value was encountered with a broken comment.

Action: Ensure that the comments in this value are well-formed.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60054: rich text parse error at position: {0}

Cause: A rich text value was encountered with a non-terminated comment.

Action: Ensure that the comments in this value are terminated.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60055: No setPattern method present on converter: {0}.

Cause: A converter was encountered with a missing method.

Action: Use the development tools to open the page and fix the converter.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60056: Error executing setPattern method on converter: {0}.

Cause: A converter was encountered with an invalid method.

Action: Use the development tools to open the page and fix the converter.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60057: Unable to access setPattern method present on converter: {0}.

Cause: A converter was encountered with an invalid method.

Action: Use the development tools to open the page and fix the converter.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60058: Attempt to re-register component with different model.

Cause: An IllegalStateException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60059: A null QueryModel object was found.

Cause: Either a QueryModel was not set on the query component, or the expression for the model property resolved to a null or invalid object.

Action: Use the development tools to open the page and fix the query.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60060: A null ListOfValuesModel object was encountered.

Cause: Either a ListOfValuesModel object was not set on the lov component, or the expression for the model property resolved to a null or invalid object.

Action: Use the development tools to open the page and fix the list of values component.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60061: Current criterion is not valid or null.

Cause: QueryDescriptor.getCurrentCriterion() method was not implemented correctly or returned null.

Action: Use the development tools to open the page and fix the query.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60062: Popup component with the ID: {0} not found.

Cause: The popup with the ID specified for createPopupId on LOV Component is not found.

Action: Use the development tools to open the page and fix the popup.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60063: Invalid facet size for af:decorativeBox: {0}. {1} is not a valid CSS length.

Cause: An invalid value was specified for a decorativeBox size (e.g. topHeight) attribute.

Action: Specify valid CSS lengths for the decorativeBox size (e.g. topHeight) attributes.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60064: unsupported element: {0}

Cause: An unsupported element was encountered while parsing a feature/partition configuration file.

Action: Verify that the feature/partition configuration is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60065: unsupported namespace: {0}

Cause: An unsupported namespace was encountered while parsing a feature/partition configuration file.

Action: Verify that the feature/partition configuration is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60066: Failed to load ADF Faces JavaScript features.

Cause: ADF Faces was unable to load its feature configuration metadata.

Action: Check the logs for other exceptions/errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-60067: Failed to load ADF Faces JavaScript partitions.

Cause: ADF Faces was unable to load its partition configuration metadata.

Action: Check the logs for other exceptions/errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-60068: attempting to add setPropertyListener with type set to valueChange to component that is not editableValueHolder

Cause: Attempted to add setPropertyListener with type set to valueChange to component that is not editableValueHolder.

Action: Move the setPropertyListener tag or change the type event it is listening for.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60069: No methodData information available for type: {0}.

Cause: No methodData information was available for the type given.

Action: Check that the type is supported type. If it is a supported type log a bug.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60070: Attempting to add requested listener to component of type: {0} has failed. For the type: {1}, the setPropertyListener tag requires that the component have a method: {2}.

Cause: For the type given, there was no appropriately named add method for the setPropertyListener to call in order to add itself as a listener.

Action: Change the type attribute to an event type that is supported on the component, or remove the setPropertyListener tag.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60071: The type: {0} is not a legal type. The legal values for type are: {1}.

Cause: An invalid type was passed to the setPropertyListener tag.

Action: Change the type property on the setPropertyListener tag to a supported type.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60072: The setPropertyListener tag must be a child of UIComponent.

Cause: The setPropertyListener tag was not a child of UIComponent.

Action: Move setPropertyListener tag so that it is a child of a UIComponent.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60073: The setPropertyListener "to" attribute must be an EL expression.

Cause: The setPropertyListener "to" attribute was not an EL expression.

Action: Fix the "to" attribute so that it is an EL expression.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60074: attempting to add setPropertyListener with type set to action to component that is not actionSource

Cause: Attempted to add setPropertyListener with type set to action to component that is not actionSource.

Action: Move the setPropertyListener tag or change the type event it is listening for.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60075: Drop handler cannot return null.

Cause: Drop handler cannot return null.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60076: Active Data Service is already initialized

Cause: AdsInitializerListener is registered in web.xml.

Action: Remove the AdsInitializerListener class from your web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60077: The CalendarModel is null.

Cause: The calendar is not bound to a valid CalendarModel.

Action: Check the value attribute of the Calendar and ensure it is set to a valid oracle.adf.view.rich.model.CalendarModel.
Level: 1

Type: SEVERE

Impact: Logging

ADF_FACES-60078: Forcing the client to reload the page, because component with ID: {0} was not registered for Active Data.

Cause: Component was not registered properly.

Action: Register the component for Active Data.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60079: The 'availableViews' attribute of the calendar contains 'month' but not 'day'. If 'month' is present, 'day' is required as well.

Cause: The calendar 'availableViews' is configured to show month view but not day view.

Action: Correct the availableViews attribute to include 'day'.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60080: The 'availableViews' attribute of the calendar does not contain any valid values.

Cause: The calendar 'availableViews' attribute is specified but does not contain any recognized values.

Action: Correct the availableViews attribute to use a valid combination of values (all, day, month, week, list) or leave unspecified to show the default views (all) .
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60081: OutputStream already retrieved.

Cause: OutputStream already retrieved.

Action: OutputStream should be null.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60082: Writer already retrieved.

Cause: Writer already retrieved.

Action: Writer should be null.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60083: Response has already been committed.

Cause: Response has already been committed.

Action: Do not change response once committed.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60084: Component does not support a default DragSource or the provided DragSource was invalid.

Cause: An IllegalArgumentException occurred.

Action: Contact Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60085: Parent not an instance of EditableValueHolder: {0}

Cause: Validator tag requires an EditableValueHolder parent

Action: Add validator to an EditableValueHolder parent
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60086: Failed to create Validator for validatorId: {0}, binding: {1}

Cause: A valid validatorId or binding has to be specified

Action: Check validator's validatorId and binding
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADF_FACES-60089: An attempt to store a file larger than the configured value ({0}) for oracle.adf.view.rich.portal.FILE_DOWNLOAD_MAX_DISK_SPACE was encountered.

Cause: A call to a method on a FileDownloadActionListener resulted in a file being stored on the file system. The oracle.adf.view.rich.portal.FILE_DOWNLOAD_MAX_DISK_SPACE parameter in web.xml was either not configured so the default limit of 2MB was exceeded, or the file was larger than the configured value.

Action: Either add or update the oracle.adf.view.rich.portal.FILE_DOWNLOAD_MAX_DISK_SPACE context-param in web.xml to allow for the desired max file size.
Level: 2

Type: ERROR

Impact: Logging

ADF_FACES-60094: Unrecognized feature in PanelCollection featuresOff attribute: {0}.

Cause: An invalid feature name used in PanelCollection featuresOff attribute.

Action: Use a valid feature name. Feature names are case-sensitive. Refer to the PanelCollection tag docs.
Level: 1

Type: WARNING

Impact: Logging

ADF_FACES-60096: Server Exception during PPR, #{0}

Cause: An exception was thrown durring a PPR request.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-60097: For more information, please see the server's error log for an entry beginning with: {0}

Cause: An exception was thrown durring a PPR request.

Action: Please look in the servers error log for more details on this error.
Level: 1

Type: ERROR

Impact: Logging

ADF_FACES-60098: Faces lifecycle receives unhandled exceptions in phase {0}

Cause: An exception was not handled by any error handlder.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Logging

2 ADF-MF-10001 to ADF-MF-16221

ADF-MF-10001: Unable to load class: {0}

Cause: Couldn't load the passed in class

Action: Please make sure correct class name is passed and the class exists in the path specified by the complete name.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10002: Unable to load class for managed property type; property name: {0}; property type: {1}

Cause: Couldn't load the passed in class

Action: Please make sure correct class name is passed and the class exists in the path specified by the complete name.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10003: Unable to resolve method: {0}

Cause: Unable to resolve method with provided parameters.

Action: Please make sure that correct method is being invoked with correct arguments.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10004: Unresolved class / method: {0} / {1}

Cause: Unable to resolve method with provided parameters.

Action: Please make sure that correct method is being invoked on correct class with correct arguments.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10005: Unable to set Managed Property: {0}; {1}

Cause: An unexpected error occurred while attempting to initialize a managed property definition.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10006: Unable to create bean instance: {0}

Cause: An unexpected error occurred while attempting to creata a managed bean instance.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10007: Process AdfException caught: {0}

Cause: There was a problem generating a response object from the request

Action: Please see the exception message for the exact problem.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10008: Process throwable caught: {0}

Cause: There was a problem generating a response object from the request

Action: Please see the exception message for the exact problem.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10009: {0} Error: {1}

Cause: Unable to invoke method with provided parameters.

Action: Please make sure that correct method is being invoked on correct class with correct arguments.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10010: Looks like the wrong method (parameter: {0})

Cause: Internal Error. An incorrect method signature was passed in a channel request.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10011: adf message (size {0} != {1})

Cause: Internal Error. A VM Channel message size does not match its stated value in the header.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10012: Invalid Exception argument passed

Cause: Invalid Exception argument passed

Action: Invoke this method with valid exception argument.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10013: Attempting to evaluate ({0}) as a boolean.

Cause: Attempting to convert invalid value to boolean.

Action: Please pass valid value to be converted to boolean.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10014: Malformed ADF Message '{0}' of type '{1}'

Cause: Malformed Message received.

Action: Please make sure that a valid message with all the desired fields is returned.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10015: Cannot serialize the object as cyclical reference to {0} ({1}) was detected during the JSON serialization process. A possible resolution to this could be to make the {0} field transient.

Cause: Cyclical object was detected during JSON serialization process.

Action: Make sure to verify that the object being passed to serialize isn't cyclic. A possible resolution to this could be to make erroneous field transient.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10016: No getter defined for property "{0}" in class "{1}"

Cause: No getter was defined for property in the class.

Action: Make sure that the class defines the property and it's getter appropriately.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10017: The number entered is outside the range of values a Long can hold.

Cause: The number entered is outside the range of values a Long can hold.

Action: The number should be between Long.MIN_VALUE and Long.MAX_VALUE.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10018: The number entered is outside the range of values a Double can hold.

Cause: The number entered is outside the range of values a Double can hold.

Action: The number should neither be Double.NEGATIVE_INFINITY nor be Double.POSITIVE_INFINITY.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10019: Not A Number (NaN) was passed.

Cause: Invalid number was passed.

Action: The number should be valid and not equal to Double.NaN.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10020: Unable to create new array of {0} with size {1}

Cause: Failed to create an array of passed in class with passed in length.

Action: Make sure to pass correct and valid values.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10021: Unable to convert the specified String value ''{0}'' into a Date/Time/Timestamp object

Cause: The string was not in one of the standard date formats recognized by the system.

Action: Make sure the String you are trying to convert is in a valid format. Consult the Java documentation for more details on valid date/time/timestamp formats.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10022: Unable to convert the specified String value ''{0}'' into a Date/Time/Timestamp object using the specified format ''{1}''

Cause: The string could not be converted into a date according to the format specified.

Action: Make sure the String you are trying to convert matches the format you have specified.
Level: 1

Type: ERROR

Impact: Logging

Cause: The format specified is invalid.

Action: Consult the Java documentation for more details on valid date/time/timestamp formats.

ADF-MF-10023: Format exception: unknown token {0}

Cause: Unknown token was received.

Action: Make sure to have valid token array to generate a valid Calendar object.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10024: Attempting to log to null/undefined logger

Cause: Logging method was invoked with invalid logger.

Action: Please pass valid logger name or logger object.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10025: Null resource bundle class specified.

Cause: Logging method was invoked with invalid resource bundle class.

Action: Please pass valid resource bundle class.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10026: Null calling class specified.

Cause: Logging method was invoked with invalid calling class.

Action: Please pass valid calling class.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10027: Error processing UTF-8 encoded data.

Cause: The system is unable to process UTF-8 encoded data.

Action: Make sure the application contains the Java libraries necessary to process UTF-8 encoded data.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10034: Batch Validation Exception

Cause: Batched exceptions.

Action: See exceptions.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10035: Validation Exception

Cause: Validation Exception

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10036: Resolution Exception

Cause: Resolution Exception

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10037: Batch Adf Exception

Cause: Batch Adf Exception.

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10038: Invalid Response Exception

Cause: Invalid Response Exception.

Action: See exception. Invalid response seems to be received for the request.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10039: Attempting to send {0} for request {1}

Cause: Invalid Response Exception.

Action: See exception. Invalid response seems to be received for the request.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10040: Malformed Message Exception

Cause: Malformed Message Exception.

Action: See exception. Message body is malformed. Make sure the message body is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10041: Unhandled ADF Message Exception

Cause: Unhandled ADF Message Exception.

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10042: Unhandled ADF Message {0} of type: {1}

Cause: Unhandled ADF Message Exception.

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10043: Unknown ADF Message Exception

Cause: Unknown ADF Message Exception.

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10044: Unknown ADF Message {0} of type: {1}

Cause: Unknown ADF Message Exception.

Action: See exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10045: Date Parse Exception

Cause: Date Parse Exception.

Action: See exception and logs. Make sure date is passed in correct expected format.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10046: Invalid exception message format. "exception" key not found.

Cause: Invalid exception message format.

Action: See exception. Exception message is not passed in expected format.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10047: Unable to convert AdfException object to JSON.

Cause: Serialization of exception object failed.

Action: Internal Error: Make sure valid exception object is passed for serialization.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10048: No setter defined for property "{0}" in class "{1}"

Cause: No setter was defined for property in the class.

Action: Make sure that the class defines the property and it's setter appropriately.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10049: AdfControlChannel.init .... failed can not continue CH = {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10050: Attribute validation failed due to unrecognized attributes: {0}

Cause: The XML element contains attributes that it is not supposed to contain.

Action: Remove unrecognized attributes from XML element.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10051: Children validation failed due to unrecognized children: {0}

Cause: The XML element contains children that it is not supposed to contain.

Action: Remove unrecognized children from XML element.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-10052: Failed to load metadata from: {0}

Cause: Unable to read metadata from xml file.

Action: Make sure that the specfied xml file exists in the desired location and is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10053: Error reading the XmlAnyDefinition at {0}

Cause: The specified resource could not be loaded as an xml document.

Action: Verify the resource is a valid xml document.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10054: Missing '{0}' value

Cause: Could not find the specified attribute.

Action: Verify that the specified attribute exists.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-10055: Class '{0}' is not equal to '{1}'

Cause: Internal error. The ping response from the feature channel was invalid.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11001: Action attribute was an invalid value: {0}

Cause: Internal error. An action binding on a pagedef used an invalid value for the 'action' attribute.

Action: Examine the application log for further exception messages.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11002: Unable to load application metadata directory file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11003: Exception thrown from getCustomOperation (Provider Class: {0})- Exception: {1}; Message: {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11004: {0} - Attempt to create invoker for method: {1} returned null

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11005: Evaluated parameter to pass to invoker - value: ''{0}''

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11006: Unable to locate the data provider for this iterator

Cause: Internal error. A DataControl attempted to create an iterator accessor iterator and was unable to load the data provider.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11007: Check the implementation of {0} with {1} parameters.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11008: Check the implementation of {0} with a {1} parameter.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11009: getIteratorBinding({0}, {1}) has a problem - {2}

Cause: Internal error. An unexpected error occurred in the framework while attempting to create the named iterator.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11010: Data Control: {0} was not found.

Cause: The framework was unable to locate a declaration for the named data control.

Action: Ensure your application defines the named DataControl. If it is java bean based, simply right click on the bean class and choose 'Create Data Control'.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11011: Data Control: {0} is not a supported data control.

Cause: The framework attempted to load an unsupported DataControl type.

Action: Ensure your application only uses java bean based or web service Data controls.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11012: Attempting to set the Web Service Provider to null.

Cause: A web service data control attempted to set a null provider. This may due to a failed call.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11013: Invalid data provider. Expected a WebServiceObject.

Cause: A web service data control attempted to set an invalid provider. This may due to a failed call.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11014: Error: Unable to determine the return type for operation {0}

Cause: Internal error. The framework was unable to determine the return type of a virtual provider operation.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11015: Error defining the property: {0} - {1}

Cause: Internal error. The framework was unable to load a virtual provider type for the given property name.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11016: No Web Service definition defined.

Cause: Internal error. The framework was unable to load a web service definition required for an operation.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11017: Operation {0} should have returned a {1} but nothing was returned.

Cause: A web service data control operation had a null response. This may due to a failed call.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11018: Error with the HTTP connection while processing ''{0}'' - {1}

Cause: There was an exception trying to open the connection to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11019: Error obtaining the output stream with the HTTP connection while processing ''{0}''

Cause: Could not open an output stream to write data to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11020: Error while processing ''{0}'' - SOAP FAULT: {1} - {2}

Cause: A SoapFault occurred while executing an operation.

Action: Determine the cause of the error via the supplied fault code, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11021: Attempting to cache ({0}, {1})

Cause: Internal error. An attempt was made to cache a framework metadata element of an unsupported type.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11022: Connector Error: {0}

Cause: There was an exception trying to open the connection to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11023: Connection Error: {0}

Cause: Could not open an input stream to read data from the server.

Action: Verify that the device is connected to the internet and has access to the specified server.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11024: Connection Error: unable to establish a connection.

Cause: There was an exception trying to open the connection to the server.

Action: Verify that the device is connected to the internet and has access to the specified server.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11025: EL: Unable to resolve variable: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11026: Exception resolving variable: {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11027: Error parsing pageDef metadata : {0}

Cause: Internal error. An unexpected error occurred while parsing pagedef metadata.

Action: Ensure that all pagedef xml files are valid. Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11028: {0} failed to execute - {1}: {2}.

Cause: See Error

Action: See Error.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11029: Could not find or create the binding container for context key: {0}

Cause: See Error

Action: See Error.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11030: Unable to load resource:

Cause: Locale unknown.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11031: Attribute set with value {1} for attribute {0} failed

Cause: The attribute did not pass validation.

Action: Fix the value and set the attribute again.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11032: Attempting to deliver a location update for ID ''{0}'', but no listener has been registered for that ID

Cause: An attempt was made to deliver a location update, but there is no listener registered for the corresponding watchID.

Action: Ensure that you have registered a valid GeolocationCallback for this watchID.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11033: An error occurred while trying to retrieve the requested image data.

Cause: Either the device could not retrieve the requested image from the file system, or the device's camera did not take a valid picture.

Action: If you have requested an image from the camera, ensure that the camera is in proper working order by taking a picture from the standalone camera application. If you have requested an image from the device's file system, try to select the desired image from the photo album. You may also need to reduce the size of the image by specifying a different image encoding, requesting a file instead of a binary image object, or specifying a target height and width to dynamically scale the image.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11034: Unable to determine device's current position.

Cause: The device's current position could not be determined.

Action: Ensure that you have enabled location services for this application on your device, and that you have good wireless reception.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11035: Unable to monitor changes in the device's position.

Cause: The device's current position could not be monitored.

Action: Ensure that you have enabled location services for this application on your device, and that you have good wireless reception.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11036: Error encountered in preferences map: {0}

Cause: The internal map used to maintain preferences has encountered an unexpected error.

Action: Examine error message for more information.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11037: Error retrieving preferences: {0}

Cause: Retrieving preference has encountered an unexpected error.

Action: Examine error message for more information.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11038: Error setting preference: {0}

Cause: Setting preference has encountered an unexpected error.

Action: Examine error message for more information.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11039: Error getting preference from internal map: {0}

Cause: Getting preference from internal map used to maintain preferences has encountered an unexpected error.

Action: Examine error message for more information.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11040: Error setting preference from internal map: {0}

Cause: Setting preference in internal map used to maintain preferences has encountered an unexpected error.

Action: Examine error message for more information.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11041: Unable to create validator ({0}): {1}

Cause: Attempting to create the specified validator failed.

Action: Examine error message for more information.
Level: 1

Type: ERROR

Impact: Data

ADF-MF-11042: setContext: No binding context exists for this feature

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11043: Failed to locate registered pagedef for path: {0}. Container will not be loaded and bindings will not resolve in this context.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11044: Unable to read DataControl Usages, on loadDataControl for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11045: Unable to load DataControls.dcx , on loadDataControl for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11046: Unable to load Adapter DC definition for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11047: Unable to load Data Control Factory, on loadDataControl for id: {0}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11048: The name read from the DataControl {0}, does not match the definition's ID: {1}.

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11049: Unable to load Data Control {0} due to following error: {1}.

Cause: Internal Error, see message.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11050: Invalid (Null) Contact object passed

Cause: An attempt was made to remove/create/update a null contact.

Action: Ensure you are specifying a valid contact object for these operations, then try again.
Level: 1

Type: WARNING

Impact: Logging

ADF-MF-11051: Invalid (Null) arguments passed

Cause: Invalid arguments were passed to an operation that expected non-null arguments.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: WARNING

Impact: Logging

ADF-MF-11052: Unable to get the device data control manager

Cause: A serious internal error has occurred.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11053: A {0} was expected but instead a {1} was found.

Cause: The web service call expected a value of a certain type, but instead a different type was found.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11054: Invalid value for custom HTTP header. Expected {0} but received {1}

Cause: The web service call requires one or more custom HTTP headers, but these headers could not be set correctly.

Action: Check that the application's web service(s) have been properly configured, and that the web service(s) themselves are sending appropriate data values down to the client.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11055: The web service method {0} is unsupported at this time.

Cause: The application attempted to make use of an unsupported HTTP method.

Action: Make sure that the web service(s) are configured to work with a supported HTTP method, such as GET or POST.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11056: Unable to find metadata definition for {0}, which is required for this web service operation.

Cause: The application could not find the required metadata to support the web service operation.

Action: Clean and redeploy the application. Try to execute the same web service operation in JDeveloper's web services tester.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11057: Encountered exception while invoking SOAP request EndPoint: {0} SOAPAction: {1} Exception: {2}

Cause: The application encountered an error while attempting to invoke a SOAP web service operation.

Action: Ensure the web service is available at the specified address. Try to execute the same web service operation in JDeveloper's web services tester.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11058: Operation {0} returned an unknown response.

Cause: The web service returned an unsupported response type.

Action: Try to execute the same web service operation in JDeveloper's web services tester to make sure it is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11059: Unable to remove contact due to: {0}

Cause: The contact could not be removed from the device's address book.

Action: Ensure that the contact exists, and that no other application is currently using the address book.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11060: Exception caught, e: {0}

Cause: Internal error. An unexpected error occurred while processing preferences.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11061: Couldn't load resource bundle. Bundle Name: {0}

Cause: Can't load resource bundle.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11062: Response [Error: {0}]: {1}

Cause: Internal error. An unexpected error occurred while processing an HTTP response.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11063: value is Null

Cause: A null value was passed to a SelectItem object's value property.

Action: Examine the application log for further exception messages.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11064: label is Null

Cause: A null value was passed to a SelectItem object's label property.

Action: Examine the application log for further exception messages.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11065: Unable to load definition for {0}

Cause: Internal error. The framework was unable to load a virtual type definition.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11066: No application definition (cpx) found

Cause: The framework was unable to locate the Data Binding Registry file, usedto map page ids to the pagedef.xml files that define the page's data bindings.

Action: If your application uses data control based bindings, ensure that a valid DataBindings.cpx file exists.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11067: id is null

Cause: Internal error. An unexpected error occurred while trying to process a REST web service definition.

Action: Report this message to Oracle support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11068: Expected id {0} but received {1}

Cause: Internal error. An unexpected error occurred while trying to process a REST web service definition.

Action: Report this message to Oracle support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11069: Invalid connections.xml

Cause: Internal error. An unexpected error occurred while trying to process web service connection information declared in connections.xml.

Action: Report this message to Oracle support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11070: Unable to load class: "{0}" for managed bean definition bean definition - Name: {1}; Class: {2}; Scope: {3}

Cause: An unexpected error occurred while trying to create a new instance of the named class used as a managed bean.

Action: Ensure the class is on your application or feature classpath.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11071: AdfChannel.send response on channel [{0}] failed - {1}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11072: Error handling the VMChannel message: {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11073: Argument "{0}" is null

Cause: A null argument was encountered.

Action: Ensure that the argument is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11074: Error in the channel creation confirmation - {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11074: Feature not found with Id "{0}"

Cause: Invalid Feature Id argument.

Action: Please use an existing and valid Feature Id.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11075: metadataDef is not a BeanBindingIteratorBaseDefinition. Element Name: {0}

Cause: Internal error. A DataControl attempted to create an iterator based on invalid metadata.

Action: Report this message to Oracle support.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11075: Feature not found with Name "{0}"

Cause: Invalid Feature Name argument.

Action: Please use an existing and valid Feature Name.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11076: Can't find bundle for bundlePath: {0}

Cause: The framework was unable to find a resource bundle at the indicated path.

Action: Ensure that the resource bundle is included and packaged in your application at the indicated path.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11076: Invalid type of queue entry : {0}

Cause: There was a problem broadcasting a queued event because event type {0} is not a valid event type.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11077: Unable to load class object for type: {0}. Conversions to or from this type will not occur when evaluating the expression: {1}

Cause: An unexpected error occurred while trying to create a new instance of the named class

Action: Ensure the class is on your application or feature classpath and that it has a public default constructor
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11077: Version {0} failed to be activated: {1}

Cause: There was a problem activating version {0} using Configuration Service.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11078: Caught Throwable, wrapping as RuntimeException and rethrowing. Original Exception type: {0}; Original Exception message: {1}

Cause: This is a notification that a framework initiated call caught an exception and is marshaling it back as an AdfException instance.

Action: Examine the application log for further exception messages.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11078: Version {0} is not available for activation

Cause: Version is not available for activation.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11079: flushDataChangeEvent - Exception from container call to adf.mf.api.processDataChangeEvent.

Cause: A call from the embedded CVM to the container function adf.mf.api.processDataChangeEvent has returned with an Exception.

Action: Examine the application log for further exception messages.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11079: Version {0} is locked

Cause: Version is locked.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11080: flushDataChangeEvent - caught Exception, rethrowing as AdfException

Cause: This is a notification that a framework initiated call caught an exception and is marshaling it back as an AdfException instance.

Action: Examine the application log for further exception messages.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11080: Artifact {0}, Version {1} does not exist

Cause: Artifact cannot be found.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11081: BindingContainer: {0}; Could not locate object with id: {1}

Cause: The named identifier could not be located in the named Binding Container.

Action: Check your pages for for any expressions of the form '#{bindings.id.*}'. Ensure that a bindings, executables, or variable id element in the corresponding pagedef.xml file exists with that id.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-11081: Artifact {0}, Version {1} could not be validated

Cause: Artifact cannot be validated using checksum or last modified information. Please check the manifest.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11082: Checksum do not match for Artifact {0}, new version may be available

Cause: Checksum do not match.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11083: Last Modified time does not match for Artifact {0}, new version may be available

Cause: Last Modified does not match.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11084: Artifact {0} version {1} already exists.

Cause: Artifact already exist, may not have been cleaned up previously.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11085: Failed setting connection security for connection {0}

Cause: Security configuration error. WS cannot set credential from store.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11085: Unable to get Artifact {0} as input : {1}.

Cause: Unable to get input contents of artifact, maybe pointing to invalid location or not accessible.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11086: Error parsing {0}: {1}

Cause: An unexpected error occurred while parsing a PDefViewObject xml file.

Action: Check that any xml files in the application's persDef.* packages are valid xml.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11086: Unable to get handle to a file {0} file - {1}.

Cause: Unable to get handle to a file.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11087: Unable to resolve methodExpression: {0}

Cause: The named EL expression could not resolve to an actual method call.

Action: Verify that the path to the method in the expression will resolve to valid objects, and that the named method (and signature) actually exists.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11087: Unable to copy artifact {0} to {1}.

Cause: Unable to copy file.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11088: Unable to load class: {0}; Error Message: {1}

Cause: An unexpected error occurred while trying to load the named class.

Action: Ensure the class is on your application or feature classpath.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11088: Unable to unzip file {0} to {1}.

Cause: Unable copy file from zip.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11089: Tree binding: {0} has a corrupt key; Cannot serialize collectionModel

Cause: Internal error. An unexpected error occurred trying to serialize a key in the named tree binding's collectionModel.

Action: Report this message to Oracle support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11089: Unable to parse catalog versions. Server returned {0}. Exception : {1}

Cause: Unable to parse catalog versions.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11090: whichSet value is not in {"previous", "current", "next"}

Cause: An invalid value was passed for the whichSet parameter to IteratorHandler.fetchSetRelativeTo.

Action: Check that any calls to this method pass one of the documented valid values.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11090: Unable to parse manifest. Server returned {0}. Exception : {1}

Cause: Unable to parse manifest.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11091: Invalid argument passed to getDirectoryPathRoot

Cause: An invalid argument was passed to AdfmfJavaUtilities.getDirectoryRoot.

Action: Check that any calls to this method pass one of the documented valid values.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11091: Unable to update json profiles : {0}

Cause: Unable to parse json profiles, used to update skin family.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11092: Feature argument is null

Cause: A null feature argument was encountered while processing a feature element from maf-feature.xml.

Action: Ensure that the maf-feature.xml file is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11092: Error processing {0} encoded data.

Cause: The system is unable to process the encoded data.

Action: Make sure the application contains the Java libraries necessary to process the encoded data.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11093: Invalid feature argument form

Cause: An invalid feature argument was encountered while processing a feature element from maf-feature.xml.

Action: Ensure that the maf-feature.xml file is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11093: Unable to retrieve list of sandboxes from the server. Server returned {0}. Exception : {1}

Cause: Unable to get list of sandboxes.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11094: {0}: Unexpected element - {1}; Expected - {2}

Cause: Internal error. An xml parser encountered an unexpected child xml element name for the parsers current xml node.

Action: Report this message to Oracle support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11094: Unable to find base skin with id {0} while going through the ancestors of skin id {1}

Cause: Invalid skin configuration.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11095: {0}: key argument is null

Cause: A call to an iterator operation that takes a key (i.e. setCurrentRowWithKeyValue) passed a null key value.

Action: Check that any values passed to or bound to a key parameter in an iterator operation will pass valid keys.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11095: Complex EL not supported for adding application scope data change listener for expression {0}

Cause: Invalid EL set for configuring skin family / skin version.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11096: Unable to locate key: {0} in Iterator: {1}

Cause: A call to an iterator operation that takes a key (i.e. setCurrentRowWithKeyValue) passed a key value that does not exist on that iterator's provider.

Action: Check that any values passed to or bound to a key parameter in an iterator operation will pass valid keys.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11096: Invalid EL format in expression {0} for adding application scope data change listener, EL should be in the format 'Scope.ManagedBean.Property'

Cause: Invalid EL set for configuring skin family / skin version.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11097: {0} - provider data must be a Map

Cause: A call was made to BasicIterator.createRowWithData passing a provider that does not implement Map.

Action: Ensure that the object passed to createRowWithData is of type Map.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11097: Unsupported scope for adding application scope data change listener in expression {0}. Scope should be applicationScope

Cause: Invalid EL set for configuring skin family / skin version.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11098: No value was returned

Cause: An uxpected error occurred while processing a REST web service operation.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11098: Unable to add property change listener {0} on {1}. Exception {2}

Cause: Internal Error

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11099: Unknown element coming back

Cause: An unexpected error occurred while processing a SOAP data provider type.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11100: SOAP-VERSION {0} not supported.

Cause: The SOAP version encountered is not currently supported.

Action: Refer to the documentation for the supported SOAP versions and contact the server administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11101: Could not load wsdl from location: {0}

Cause: There was an exception trying to load the wsdl.

Action: Verify that the device is connected to the internet and has access to the specified document.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11102: Invalid connection: {0}

Cause: Internal error. The connection specified in the connections.xml could not be found.

Action: Verify that the connections.xml refers to a valid connection.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11103: Transient expressions are unsupported: {0}

Cause: A transient expression was encountered while parsing a PDefViewObject xml file.

Action: Ensure that any xml files in the application's persDef.* packages do not contain transient expressions.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11104: Error parsing {0}: {1}

Cause: An unexpected error occurred while parsing a PDefViewObject xml file.

Action: Check that any xml files in the application's persDef.* packages are valid xml.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11105: Error loading: {0}

Cause: Internal Error. An unexpected error occurred while loading a DataControl.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11107: Unable to create SOAP type for identifier {0}

Cause: The SOAP type for the identifier could not be created.

Action: Verify the identifier is a valid SOAP object and contact the server administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11108: ProviderChangeEvent - provider key: {0} is not a valid accessor on provider: {1}

Cause: A ProviderChangeEvent was sourced using a provider key that does not match an accessor name on the provider it was sourced from.

Action: Check your application for calls to ProviderChangeSupport.fireProviderCreate, Delete, or Update, and ensure that the provider name parameter matches the name of an accessor on the sourcing class
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11109: Unable to encrypt the database due to: {0}. Ensure that you are passing an unencrypted database connection and are specifying a valid password.

Cause: Unable to encrypt the database due to: {0}.

Action: Ensure that you are passing an unencrypted database connection and are specifying a valid password.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11110: Unable to decrypt the database due to: {0}. Ensure that you are passing an unencrypted database connection.

Cause: Unable to decrypt the database due to: {0}.

Action: Ensure that you are passing an unencrypted database connection and are specifying a valid password.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11111: Unable to retrieve Property Descriptors for {0}

Cause: Internal Error.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11112: Unable to invoke setter with value {0} on attribute {1} of {2}

Cause: Internal Error. See Error message.

Action: Ensure that a set accessor exists and is public for this attribute.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11113: Unable to invoke getter on attribute {0} of {1}

Cause: Internal Error. See Error message.

Action: Ensure that a get accessor exists and is public for this attribute.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11114: Unable to retrieve Accessor Attribute for {0} on Java Bean Definition {1}

Cause: The Accessor Attribute for the specified Java Bean Definition could not be found.

Action: Make sure the specified Accessor Attribute exists on the current Java Bean Definition.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11115: Unable to retrieve Java Bean Definition for {0}

Cause: The Java Bean Definition could not be found.

Action: Make sure the specified value is a valid Java Bean Definition.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11117: Unable to create new instance of {0}

Cause: An unexpected error occurred while trying to create a new instance of the named class

Action: Ensure the class is on your application or feature classpath and that it has a public default constructor
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11118: Unable determine array item name for {0}

Cause: The beanClass Class type passed in is an array type, but the attributeName is empty.

Action: Send in a valid attributeName that is a valid field on the GenericType instance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11119: Unable to create GenericType from array {0}. The class type must not be an Array.

Cause: The bean Object passed in is of type Array.

Action: Pass in an Object that is not of type Array.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11120: Error processing list binding metadata: {0}

Cause: An unexpected error occurred while processing list binding declaration

Action: Check that the list binding named in the message has a valid metadata declaration in the pagedef.xml file for the current page
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11121: invokeContainerUtilitiesMethod '{0}' encountered an error [{1}].

Cause: A call from the embedded CVM to a container function has returned with an Exception

Action: Examine the container function named in the message
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11122: Error serializing Data Change Event: {0}

Cause: Internal error. An unexpected error occurred while attempting to serialize a PropertyChangeEvent or a ProviderChangeEvent

Action: Examine the exception message, contact technical support
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11123: Invalid Event

Cause: An instance of a type other than ProopertyChangeEvent or ProviderChangeEvent was passed to DataChangeManager.enqueue

Action: Check your application for calls to DataChangeManager.enqueue and ensure valid parameters.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11124: Exception from container call to {0}

Cause: A call from the embedded CVM to a container function has returned with an Exception.

Action: Examine the container function named in the message, examine the application log for further exception messages.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11125: caught Exception, rethrowing as AdfException

Cause: This is a notification that a framework initiated call caught an exception and is marshaling it back as an AdfException instance.

Action: Examine the application log for further exception messages, contact technical support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11126: Feature not found with Id "{0}"

Cause: Invalid Feature Id argument.

Action: Please use an existing and valid Feature Id.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11127: Feature not found with Name "{0}"

Cause: Invalid Feature Name argument.

Action: Please use an existing and valid Feature Name.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11128: Unable to locate treeBindingID: {0} in Binding container: {1}

Cause: Unable to locate tree binding id in binding container.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11129: Binding container in current EL context is null.

Cause: Binding container in current EL context is null.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11130: Unable to resolve binding container in current EL context

Cause: Unable to resolve binding container in current EL context.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11131: Unable to locate connection "{0}" in: {1}

Cause: Unable to locate connection in connections.xml

Action: Make sure you have defined this connection in connections.xml.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11133: Unable to locate connection "{0}". No connections are defined (check connections.xml)

Cause: No connections are defined in connections.xml.

Action: Make sure connections.xml contains valid connection(s).
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11134: Unable to load bundle: basename = {0}

Cause: Unable to load resource bundle.

Action: Make sure the resource bundle exists in the desired location. Contact Administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11136: Connection not found ({0})

Cause: Either connection target cannot be found, or the protocol type is not supported.

Action: See exception message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11137: Security Issue ({0})

Cause: Thrown by the security manager to indicate a security violation.

Action: See exception message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11138: I/O Error ({0})

Cause: I/O exception of some sort has occurred.

Action: See exception message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11139: Internal Problem ({0})

Cause: Internal Problem.

Action: See exception message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11140: Cannot modify read-only collection - operation "{0}" is unsupported.

Cause: An attempt was made to modify a read-only collection.

Action: Do not add, modify, or remove values from this collection.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11141: The EL expression "applicationScope.configuration.{0}" is read-only

Cause: An attempt was made to modify a read-only EL expression.

Action: Do not try to change values that are children of applicationScope.configuration.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11142: An error occurred while populating the EL node "applicationScope.configuration" - {0}. Device-specific configuration properties will not be available

Cause: An internal error occurred.

Action: Contact technical support
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11143: Unable to clear password for username "{0}" with adfCredentialStoreKey "{1}"

Cause: Either the adfCredentialStoreKey or username is invalid.

Action: Please check the adfCredentialStoreKey value and username used to clear password.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11144: Unable to set value to the property due to invalid binding iterator.

Cause: Unable to set value to the property as iterator value was null.

Action: Make sure that the property is bound to a valid iterator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11145: Unable to get value for the property due to invalid binding iterator.

Cause: Unable to get value for the property as iterator value was null.

Action: Make sure that the property is bound to a valid iterator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11146: Cannot invoke asynchronous javascript function due to device is not ready from the Container side.

Cause: The embedded Java framework does not receive device ready event from the Container side within timeout.

Action: Check if there is any deadlock or error during application startup.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11147: Interrupted during waiting for device ready.

Cause: The embedded java thread is interrupted during waiting for device ready.

Action: Restart the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11148: Access violation trying to invoke javascript on communication Id {0} and feature Id {1}.

Cause: Invoke Javascript functions on other feature is not allowed.

Action: Contact administrator to remove the offending logic from the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11149: Unable to display file. Exception: {0}

Cause: The file could not be displayed.

Action: Ensure that the file exists at the given location and that it is of a supported type.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11150: Cannot delegate following notification to feature - {0}

Cause: Feature ID is null or empty

Action: Pass a valid feature ID
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11151: Cannot delegate following notification to feature with ID {0} - {1}

Cause: No Feature Lifecycle Listener is associated with the feature with ID {0}

Action: Associate a feature lifecycle listener with the feature with ID : {0}
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11152: Unknown child node '{0}' encountered in element node '{1}'

Cause: Unknown child node was encountered.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11153: Unknown attribute name '{0}' encountered in element node '{1}'

Cause: Unknown attribute name was encountered.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11154: maf-config.xml could not be loaded due to error: {0}

Cause: Error loading maf-config.xml

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11155: Could not find the data control named: {0} in the binding context.

Cause: Data control name is not valid

Action: Pass a valid data control name defined in the binding context
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11156: Specified watchID "{0}" is already in use.

Cause: The watchID you have specified is already in use, and all watchIDs must be unique.

Action: Either specify a different watchID, or stop listening for updates on this watchID before attempting to reuse it.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11157: Failed to fetch amx file: {0}

Cause: There was a problem loading the amx file

Action: Check that your amx include tags reference valid paths, and confirm the necessary resources are packaged into your deployed application
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11158: Unable to commit changes due to a null data provider

Cause: The data provider is null for an ADFBC REST commit operation.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11159: Unable to commit changes due to an invalid data provider: {0}

Cause: The data provider is not an instance of the expected ADFBC REST type.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11160: Unable to initialize sync framework from settings file {0}; using defaults. Error was: {1}

Cause: There was a problem loading the sync config file

Action: Check that you have correctly specified the sync config file, and that it exists at the location indicated in the error message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11161: Specified sync configuration file {0} not found; using default.

Cause: The specified sync config file does not exist

Action: Check that you have correctly specified the sync config file, and that it exists at the location indicated in the error message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11162: Unable to commit changes due to an invalid data provider: {0}

Cause: The data provider is not an instance of the expected ADFBC REST type.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11163: Unable to commit changes due to an invalid data provider: {0}

Cause: The data provider is not an instance of the expected ADFBC REST type.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11164: Device Access is not enabled for: {0}

Cause: Device Access is not enabled

Action: Enable Device Access in maf-application.xml Overview editor
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11165: No login connection for specified key was found. Check connections.xml for adfCredentialStoreKey={0}

Cause: Login connection is not found in connections.xml for the key

Action: Contact system admin with the error message
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-11166: Invalid connections.xml information for connection: {0}

Cause: Internal error. Expected web service connection information for the specified connection was not found in connections.xml.

Action: Report this message to Oracle support.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12001: Unable to load resource: {0}

Cause: The specified resource could not be found.

Action: Verify the resource exists.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12005: threw an exception: {0}

Cause: An exception occurred while invoking a container method.

Action: Examine the exception message to determine the correct fix.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12006: Timeout after {0} seconds

Cause: A timeout occurred while invoking a synchronous Javascript method.

Action: Verify the Javascript method is valid and returns a value before the timeout period.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12007: Interrupted: {0}

Cause: A thread was interrupted while invoking a synchronous Javascript method.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12008: Received an unsolicited response message: {0}

Cause: Internal error. An unsolicited response message was received from the channel.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12009: Error handling the VMChannel message: {0}

Cause: Internal error. An exception occurred while handling a VMChannel message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12010: InvalidResponseSentException

Cause: Internal error. The specified response is invalid or is not ready to be sent.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12011: AdfControlChannel.init .... failed can not continue

Cause: Internal error. Unable to initialize the control channel.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12012: Unable to establish a control channel

Cause: Internal error. Unable to establish the control channel.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12013: Not supported yet. [control channel: {0}]

Cause: Internal error. The specified control channel action is not supported.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12014: Container was unable to create an associated feature context for the channel

Cause: Internal error. An exception occurred while trying to create an associated feature context for the channel.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12015: ActivationInformation: Missing featureId

Cause: Internal error. Unable to pause feature because the featureId is null.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12016: ActivationInformation: Missing listener

Cause: Internal error. Unable to pause feature because the listener is null.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12017: ActivationInformation: The value of pausedFeature is null.

Cause: Internal error. Unable to pause feature because the pausedFeature value is null.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12018: Invalid action: {0}

Cause: The specified action is invalid or unsupported.

Action: Pass in a valid action.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12019: Error: {0}

Cause: An exception occurred during processing.

Action: Examine the exception message to determine the correct fix.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12020: Exception: {0}

Cause: An exception occurred during processing.

Action: Examine the exception message to determine the correct fix.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12021: AdfSpringboardPhoneGapActivity.activeSpringboard was null

Cause: Could not create a new WebView because the activeSpringboard was null.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12022: Current view's context is not an instance of AdfPhoneGapActivity

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12023: Unable to load feature: {0}

Cause: Internal error. The specified feature could not be loaded.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12024: Failed creating dir: {0}

Cause: Internal error. A local directory could not be created to unpack assets to.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12025: Could not find contact with id: {0}

Cause: The specified contact could not be found.

Action: Pass in a valid contact id.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12026: The argument, 'featureId' cannot be null.

Cause: The featureId specified is null.

Action: Pass in a valid, non-null featureId.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12027: Bad argument in method: {0}

Cause: The argument passed into the method is invalid.

Action: Pass in a valid argument to this method.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12028: The feature id, '{0}' does not seem to be valid.

Cause: The featureId specified is invalid.

Action: Pass in a valid, non-null featureId.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12029: The feature context has not been set on this thread

Cause: The feature context was unable to be retrieved.

Action: Make sure the feature context is set on the local thread before attempting to retrieve it.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12031: File not found: {0}

Cause: Could not find the specified file.

Action: Make sure the file exists and is accessible.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12032: Exception finding styleable: {0}

Cause: The specified styleable resource could not be found.

Action: Make sure the styleable resource is valid and exists in the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12033: Exception finding class: {0}

Cause: The specified resource class could not be found.

Action: Make sure the resource class is valid and exists in the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12034: RemoteFileManager.copySecuredFileFromUrlToLocalPath failed with error code ({0}): {1}

Cause: Could not retrieve secured file from the specified URL.

Action: Verify the url is accessible and credentialis are valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12035: Invalid ping response.

Cause: Internal error. The ping response from the feature channel was invalid.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12036: Failed to suspend NFCM constructor.

Cause: Internal error. Could not suspend the thread in the Native Feature Context Manager.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12037: Failed to send ping

Cause: Internal error. A ping request to the feature channel could not be sent.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12038: Unable to send message as text messaging is not available on this device.

Cause: The text messaging Activity could not be found.

Action: Verify this device is provisioned to use text messaging.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12039: Unable to send email as email service is not available on this device.

Cause: The email Activity could not be found.

Action: Verify this device is provisioned for email.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12040: Unable to inject Query String data into the webview because the Activity is null.

Cause: Internal error. The current activity is not a valid Mobile Application Framework Activity to inject query string data to.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12041: Exception when trying to set value on model: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12042: Failed to persist installation date to file: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12043: Could not read installation date from file: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12044: Exception thrown when resetting feature: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12045: Failed to safely encode given URL: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12046: Failed to redirect output: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12047: Could not get Phonegap plugin manager: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12048: Exception thrown when notifying a lifecycle listener that a feature activation was paused: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12049: The copy of the connections.xml file from the bundle to the config service managed location has failed: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12800: ACS Failed

Cause: ACS is not running or ACS configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12801: ACS not configured for default connection and constrained features are not made available.

Cause: Login connection is not configured correctly.

Action: Provide correct URL for ACS.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12802: Application level login failed due to missing authentication context.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12803: Application level login failed due to missing authentication context.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12804: General login error occurred. User might have entered invalid credentials, or login connection configuration may contain error. E.g. login URL and/or cookie name may be missing or wrong.

Cause: User error or configuration error.

Action: Enter correct usrname/password. If problem persists, contact aministrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12805: Multi-tenant header name is missing.

Cause: Configuration error.

Action: Contact aministrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12806: Cannot authenticate as not enough information is provided for authentication in multi-tenant application. Configuration is missing multi-tenant header name. Contact administrator.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12807: Tenant name was not entered.

Cause: User did not enter tenant name or configuration error.

Action: Enter tenant name. If problem persistes, contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12808: Cannot authenticate as tenant name was not provided. Please retry.

Cause: User did not enter tenant name or configuration error.

Action: Enter tenant name. If problem persistes, contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12809: Configuration Error.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12810: Configuration error. Contact administrator.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12811: Configuration Error.

Cause: Unknown configuration Error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12812: Error in Username.

Cause: User entered invalid user name.

Action: Enter correct user name.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12813: User name and/or tenant name used are different from original user name and/or tenant name. You need to correct the user name and/or tenant name if you entered wrong user name and/or tenant name. To log in as a new user, you must first exit application.

Cause: User entered wrong user name that is different from the original user name used.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12814: Feature level login failed due to unexpected condition.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12815: Invalid ACS configuration. User object was not retrieved correctly due to ACS configuration error. User may not be registered to ACS. Contact administrator.

Cause: ACS configuraton error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12816: Invalid username/password. Please try again.

Cause: User entered invalid credentials.

Action: Try again.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12818: Login Error

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12819: The server cannot be reached. Please make sure you are connected to Internet.

Cause: Server down, or error in device network setting. Network is not available.

Action: Connect to internet. Check proxy setting. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12820: The login server is not reachable.

Cause: Server down, or error in device network setting. Network is not available.

Action: Connect to internet. Check proxy. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12821: Logout

Cause: Logout was initiated.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12822: Logout was initiated. Application will terminate.

Cause: User initiated logout.

Action: None.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12823: Server is not reachable. Make sure your device is connected to Internet.

Cause: Server down, or error in device network setting. Network is not available.

Action: Connect to Internet. Check proxy. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12824: Authentication error with unknown cause. Please contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12826: Authentication Error

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12827: Access control service failed during application login.

Cause: ACS down or configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12828: Access control service failed due to unsupported encoding.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12829: Application login connection is not defined. This application cannot be run. Contact administrator.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12830: Invalid username/password. If the problem persists, please contact your system administrator.

Cause: User entered invalid credentials or configuration error.

Action: Retry. If problem persists, contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12831: Failed to setup IDM security service.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12832: Failed to retrieve IDM authentication context.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12833: Failed to execute OMMobileSecurityService.authenticate. {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12834: Failed to retrieve user object from credential store.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12835: Failed to get OMCredentialStore from service.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12836: Failed to retrieve credential for a key.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12837: URL is not valid when injecting cookies.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12838: Failed to create OMMobileSecurityService.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12839: Invocation of access control service failed. {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12840: Exception while parsing access control service response.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12841: Exception while parsing node of access control service response.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12842: Exception while parsing elements in access control service response.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12844: Contact administrator. Security configuration has serious error.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12845: Failed to complete IDM setup. {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12846: Failed to call authenticate. {0}

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12847: Cannot connect to login server. Check the network and try again. If the problem persists, contact administrator.

Cause: Network error or configuration error.

Action: Connect to Internet. Check proxy setting. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12848: Internal Error: OIC error when the challenge answer is invalid

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12849: Invalid username/password. If the problem persists, please contact your system administrator.

Cause: User did not enter username/password that is not recognized by the authentication server.

Action: Enter correct username/password and retry. Contact administrator to verify the credentials, if necessary.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12850: Internal Error: Not able to parse the response from the server. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12851: The device is not yet authentication with the OIC server.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12852: There is no valid authentication scheme provided. Contact administrator. Internal error.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12853: Authentication failed.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12854: Configuration Error: Not able to find a valid sso agent application. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12855: Configuration Error: Not able to find a valid sso agent application. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12856: Configuration Error: Cannot authenticate through sso agent application. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12857: Configuration Error: Application profile is invalid. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12858: Internal Error: Setup not completed before calling authenticate method. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12859: SSO agent application service domain does not match to the business application in OIC. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12860: User token is missing when trying to access a resource. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12861: Application signatures are invalid for processing the authentication. Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12863: Configuration error: MobileSecurityService object is not initialized properly.(SSOAgentApp initialization) Contact administrator.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12864: Login Failed

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12865: Maximum allowed login attempts has exceeded. The application will terminate. Contact administrator.

Cause: User has exceeded maximum allowed attempts for login without success.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12866: Could not find string resource for ID {0} extracted from {1}

Cause: The strings.xml file did not contain a value for the given ID.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12870: Device's location is currently unavailable

Cause: Device location is currently unavailable.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12871: pausedFeature was not obtained

Cause: pausedFeature was not obtained.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12872: Authentication context was not obtained

Cause: The authentication context was not obtained.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12873: Error while logging in: {0}

Cause: There was an error while logging in.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12874: Could not find connection for ID: {0}

Cause: connections.xml did not contain a connection for the given ID.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12875: An error occurred while attaching phonegap to SpringView, threw an exception {0}

Cause: Internal Error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12876: Configuration error.

Cause: Security not configured correctly. Shutting down the application.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12877: Login connection configuration error. {0} Contact administrator.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12878: Credential Store Key is not specified.

Cause: Configuration error. Credential store key in connection.xml is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12879: Invalid or missing username and/or password.

Cause: Username is not correctly entered.

Action: Edit and retry.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12881: Error in composite credential store key.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12882: Invalid Access Control Service URL.

Cause: Configuration error. Access Control Service URL is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12883: Invalid Logout URL.

Cause: Configuration error. Logout URL is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12884: Invalid Login URL.

Cause: Configuration error. Login URL is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12885: Cookie is not specified.

Cause: Configuration error. Login server cookie is not configured correctly.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12886: Idle timeout must be 10 or larger, session timeout must be 30 or larger and larger than idle timeout.

Cause: Configuration error. Error in timeout values.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12887: Login Connection Configuration Error

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12888: Authentication URL responded with illegal HTTP response code. It is not a basic authentication end point. Please contact administrator.

Cause: Configuration error. The login URL responded with an HTTP response code that cannot be processed by basic authentication response handler. The login URL cannot be used as the authenticaton URL.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12889: Terminating...

Cause: Title for application termination dialog. Fatal error in security configuration or fatal user input error in login screen.

Action: Contact administrator if it was caused by configuration error and error says contact administrator..
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12890: Failed to get active security context. Internal error. Contact administrator.

Cause: Internal framework (MAF) error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12891: Error encountered displaying application settings: {0}

Cause: Preferences are corrupted.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12892: Failed to invoke method {0}. Threw an exception: {1}

Cause: Internal framework (MAF) error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12893: Exception invoking getLoginViewInitData. Contact administrator.

Cause: Internal framework (MAF) error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12894: File not found. URL: {0}

Cause: Could not find a file at the given URL.

Action: Provide a URL that points to an existing file.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12895: No activity found capable of displaying file: extension = {0}, MIME type = {1}

Cause: Could not find an activity capable of displaying given file type

Action: Install an application capable of displaying files of given type.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12898: Unable to load ADF_HIDDEN_BACKGROUND feature; device datacontrol features will be unavailable.

Cause: Internal error. The metadata which defines this feature could not be found.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12899: The previous execution of the application was terminated abruptly. Please close the application and restart again.

Cause: The application was terminated abruptly earlier and credential store has residual security information.

Action: User must restart the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12900: Calling Invoke Java on another feature is not allowed.

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12901: Access violation

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12902: GetPassword failed

Cause: Failed to decrypt password retrieved from credential store

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12903: Javascript is not currently available for feature {0}

Cause: The current feature is not yet set up to invoke Javascript.

Action: Wait until the feature is fully loaded and no login prompts are being displayed, then try again.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12904: Error registering for receiving push notifications. Error ID returned from GCM is {0}

Cause: Error ID returned from GCM is {0}

Action: Consult GCM documentation for the error ID to determine the corrective action.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12905: Failed to get current install date: {0}

Cause: See exception message for cause

Action: Please see application log for exact source of error.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF-MF-12906: An attempt was made to invoke a Java method {0} from the main thread.

Cause: Invalid attempt to invoke Java method from the main thread.

Action: Use a worker thread when invoking Java methods.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12907: Unable to complete action due to the device not supporting the activity.

Cause: The requested activity could not be found.

Action: The web element should not be rendered on this device.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12908: Configuration error in getSecuredDomain. Security configuration was not persisted.

Cause: The persisted security configuration was not found for key. It suggests configuration error.

Action: The administrator needs to verify the configuration.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12909: An error occurred while accessing stored credentials.

Cause: An unexpected error occurred while accessing the stored credentials for the current user.

Action: Attempt to logout and restart the application. If the error persists contact the administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12910: An error occurred while showing login view.

Cause: An unexpected error occurred while showing login view.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-12911: The passed in configuration parameter does not conform to the required format. key = {0}

Cause: An unexpected parameter error occurred while parsing login configuration.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15001: Error while resolving value {0}

Cause: Error resolving attribute.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15002: Volatile state access requires an AMX node ID but was given: {0}

Cause: An attempt was made to get or set the volatile state of an AMX node but the AMX node ID was not able to be determined. This is most likely the result of using the API improperly or at the wrong time.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15003: Volatile state access failed to establish a place for storage: {0}

Cause: The application was unable to establish a place to retrieve or store the volatile state for an AMX node.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15004: Client state access requires an AMX node ID but was given: {0}

Cause: An attempt was made to get or set the client state of an AMX node but the AMX node ID was not able to be determined. This is most likely the result of using the API improperly or at the wrong time.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15005: Client state state access failed to establish a place for storage: {0}

Cause: The application was unable to establish a place to retrieve or store the client state for an AMX node.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15006: Client state access failed: {0}

Cause: The application was unable to access the client state data.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15007: Navigation failed due to not being able to set the mobile framework context: {0}

Cause: The application was unable to establish the mobile framework context during a navigation.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15008: Navigation failed due to not being able to remove the mobile framework context: {0}

Cause: The application was unable to remove the mobile framework context during a navigation.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15009: Navigation failed due to an unexpected error: {0}

Cause: The application was unable to navigate due to an unexpected error.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15010: Critical section in use

Cause: An attempt was made to enter the AMX critical section when other code is already inside of the critical section.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15011: Critical section in not currently in use

Cause: An attempt was made to queue a critical section task when the AMX critical section is not in use.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15012: Failed to sort AMX nodes

Cause: Sorting of AMX nodes failed. The error has most likely been caused by passing AMX nodes that are not in the same hierarchy.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15013: Invalid use of $jq.drag, use adf.mf.api.amx.addDragListener instead.

Cause: Improper use of an internal API has been made to $.fn.drag.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15014: Failed to load an XML document: {0}

Cause: An XML file was not able to be parsed. The XML file should be checked for improper syntax.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15015: No attribute list defined for the given location. List name: {0}

Cause: An attribute list for an AMX fragment was used without a definition for the list.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15016: Attribute list used outside of a fragment. List name: {0}

Cause: An attribute list was used outside of a fragment.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15017: Nested attribute list when the parent list is not currently being processed

Cause: A nested attribute list was used outside when the parent list was not being processed.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15018: Attribute list step attribute set to 0

Cause: The step attribute of the attribute list must be set to a positive or negative number, not zero.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15019: amx:fragmentDef must have a <fragment> tag definition as the first child

Cause: fragment definition must have a fragment meta-data tag as its first child.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15020: No attribute defined for name {0}

Cause: An amx:attribute tag has been used for an attribute that was not declared in the meta-data of the fragment.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15021: No facet defined for name {0}

Cause: An amx:facet tag has been used for a facet that was not declared in the meta-data of the fragment.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15022: Required attribute {0} missing value

Cause: A required attribute for a fragment was either not passed or the value that was passed was null.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15023: Recursive fragment inclusion detected

Cause: A fragment is being included in a recursive loop.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15024: Unassignable EL '{2}' in attribute '{1}' for AMX node '{0}'

Cause: AMX node has an unassignable EL value for one of its attributes.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15501: Error message for Selenium test with argument: {0}

Cause: Error while parsing EL expression.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15502: The number of MIME types specified, {0}, does not match the number of attachments, {1}.

Cause: An attempt was made to send an e-mail with attachments, but the number of MIME types does not correspond to the number of attachments.

Action: Either explicitly specify a MIME type for each attachment, or do not specify any MIME types at all and let the system automatically determine the correct MIME type for each file.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15503: Request: {0} exception: {1}

Cause: Error happened in the request.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15504: Exception: {0} when trying to resolve: {1}

Cause: Exception happened while resolving EL expression.

Action: Please make sure that the EL expression being passed is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15505: Exception: {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15506: Set local value failed, but callback threw exception: {0}

Cause: Exception happened while calling error callback for setLocalValue.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15507: Set local value succeeded, but callback number {0} threw exception: {1}

Cause: Exception happened while calling success callback for setLocalValue.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15508: Get value succeeded, but callback number {0} threw exception: {1}

Cause: Exception happened while calling success callback for getValue.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15509: Get value failed, but callback number {0} also threw exception: {1}

Cause: Exception happened while calling error callback for getValue.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15510: Set local value failed, and about to execute callback(s). Thrown exception was: {0}

Cause: Exception happened in setLocalValue.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15511: Error processing the data change event - {0}

Cause: Exception happened in processing data change event.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15512: Unable to set data change event values [{0}]

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15513: Error encountered when calling the bulk data change notification callback. Error: {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15514: Error encountered when calling the data change notification callback for {0}. Error: {1}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15515: Error encountered when calling the error callback

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15516: Error encountered when calling the error handlers. - {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15517: Error when resetting the binding context. - {0}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15518: Managed beans in a non-java based environment is not supported.

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15519: Ran into a problem updating {0} keys - {1}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15520: Unable to update the provider because cm is undefined.

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15521: EL Parsing Error: {0} -- [column {1}] {2}

Cause: Exception happened.

Action: Please contact your local administrator for assistance.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15522: Unable to resolve {0} with the given variables:

Cause: Unable to resolve EL expression.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15523: Incorrect number of operands {0} - {1}

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15524: Non-matching () or []

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15525: No ending expression marker found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15526: Unknown character '{0}' found.

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15527: Unexpected constant found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15528: Unexpected number constant found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15529: Unexpected string constant found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15530: Unexpected variable found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15531: Nested EL Expressions are not supported.

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15532: Unexpected operator found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15533: Unexpected (unary) operation found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15534: Unexpected (binary) operation found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15535: Unexpected (ternary) operation found

Cause: Exception happened parsing EL expressions.

Action: Please make sure that a valid EL expression is passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-15536: Incorrect number of arguments passed

Cause: Exception happened as incorrect number of arguments were passed to setLocalValue.

Action: Please make sure that you have exactly 3 arguments passed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16000: ERROR: %@

Cause: A generic error occurred prefix. See the text in the error for more details.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16001: Class %@ generated an error when it was alloc-ed and init-ed - Aborting add of Application Lifecycle Listener ERROR: %@

Cause: A configured native Objective-C lifecycle listener class could not be allocated or initialized.

Action: Ensure the configured native Objective-C class is implemented and linked into the iOS native framework. Ensure the initialization of the object is not throwing an exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16002: Invalid Use

Cause: Used as the title for an exception when a method that must run of the main thread has been called on the main thread. Can also be used as the title in the case where a method required to run on the main thread has not been called on the main thread.

Action: See the error message for more details on altering the type of thread the method is called on.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16003: This function must be called on the main thread.

Cause: A method that must be called on the main thread has been called on a thread other than the main thread.

Action: Alter your use of the method to call the method on the main thread.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16004: This function must NOT be called on the main thread.

Cause: A method that must NOT be called on the main thread has been called on the main thread.

Action: Alter your use of the method to call the method off the main thread.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16005: Bad Config File

Cause: Loading the configuration file into a string for inspection has failed. One example is the verification of connections.xml during a configuration service check for new configuration.

Action: Verify the connections.xml file on the configuration server is not corrupt or the connections.xml in the app bundle is not corrupt.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16006: Invalid Configuration

Cause: The configured Container Utilities class could not be created or initialized.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16007: AdfmfContainerUtilities implementer not configured.

Cause: The configured Container Utilities class could not be found. Are all native dependency libraries linked in?

Action: Ensure all iOS native libraries have been linked in.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16008: AdfmfContainerUtilities implementer class not found.

Cause: The configured Container Utilities class could not be found. Are all native dependency libraries linked in?

Action: Ensure all iOS native libraries have been linked in.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16009: AdfmfContainerUtilities implementer could not be created.

Cause: The configured Container Utilities class was found but could not be allocated or initialized. Are all native dependency libraries linked in?

Action: Ensure all iOS native libraries have been linked in. Ensure the class is not throwing an exception on initialization.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16010: Bad Request

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 400 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16011: Could not download file due to 400 Bad Request.

Cause: Downloading a configuration file failed with a 400 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16012: Unauthorized

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 401 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16013: Could not download file due to 401 Unauthorized (bad username or password).

Cause: Downloading a configuration file failed with a 401 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16014: Forbidden

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 403 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16015: Could not download file due to 403 Forbidden.

Cause: Downloading a configuration file failed with a 403 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16016: Not Found

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 404 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16017: Could not download file due to 404 Not Found.

Cause: Downloading a configuration file failed with a 404 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16018: Bad Gateway

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 502 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16019: Could not download file due to 502 Bad Gateway.

Cause: Downloading a configuration file failed with a 502 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16020: Service Unavailable

Cause: Used as a title for an error encountered when downloading a configuration file failed with a 503 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16021: Could not download file due to 503 Service Unavailable.

Cause: Downloading a configuration file failed with a 502 error from the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16022: Invalid Argument

Cause: Used as a title for an error when an invalid argument is passed into a method.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16023: A nil package name was passed to [oraADFLogger getLogger:].

Cause: A nil package name was passed into the get logger call.

Action: Pass a non nil string into the call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16024: Error file url cannot be nil

Cause: A nil file url was passed into the initialization of a remote file manage.

Action: Pass a non nil string url into the initialization.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16025: Property name cannot be nil.

Cause: A nil key was passed into a get value call when requesting a value for the adf-config.xml file.

Action: Pass a non nil key name into the call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16026: Too few arguments.

Cause: The PhoneGap handler for goto feature is missing the feature id.

Action: Pass a feature id to the PhoneGap call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16027: Missing classname.

Cause: A call to one of the Container Utilities invoke calls is missing a classname.

Action: Pass a classname to the invoke call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16028: Missing method.

Cause: A call to one of the Container Utilities invoke calls is missing a method name.

Action: Pass a method name to the invoke call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16029: Feature Id missing.

Cause: A call to one of the Container Utilities invoke calls is missing a featureId.

Action: Pass a featureId to the invoke call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16030: Unrecognized Call Type

Cause: The PhoneGap handler received a request for a Container Utilities invoke of something other than Java, Container or JavaScript.

Action: Pass a valid invoke type.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16031: FeatureContext not found.

Cause: The Container Utilities invoke call was passed a featureId for a feature that may not be available.

Action: Insure the featureId is valid and the user has access to that feature.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16032: Unexpected Response

Cause: Used as a general title in a situation where an unexpected response was encountered.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16033: CVM Response returned a nil response.

Cause: The CVM return a nil response message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16034: CVM Response returned a nil FeatureContextAccessor.

Cause: The feature context accessor returned by a CVM call was nil.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16035: JS Response returned a nil response.

Cause: The framework return from the a call to JavaScript was nil. Even if the JavaScript did not have a return that information should have been returned in a response.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16036: Cannot send JavaScript calls to the channel '%@' that does not have a webview.

Cause: A JavaScript call was made on the control channel or a channel that does not yet have a webview. There is no associated web view so this request cannot be fulfilled.

Action: Make the JavaScript call using your featureId and that feature has been activated.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16037: IO Error

Cause: A generic title for an IO error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16038: Error removing file.

Cause: The configuration service could not remove an old file.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16039: Error copying file.

Cause: The configuration service could not copy a file.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16040: Expected file is missing.

Cause: After copying a file to a location a subsequent check for the file found it was missing.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16041: Error moving file.

Cause: Configuration Service had a problem placing the updated file in place. An attempt was made to place the original file back in place and that failed as well.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16042: Could not create directory.

Cause: Configuration Service had a problem creating the managed directory.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16043: Download Error

Cause: There was an error downloading a configuration file.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16044: Could not create connection

Cause: A connection to the configuration could not be made.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16045: There was an unexpected error downloading the file.

Cause: After the download of a file succeeded the path to the local file was nil.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16046: Authentication Failure

Cause: The credentials were either not provided to the remote file manager or were invalid.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16047: We have no username or password.

Cause: The credentials were not provided to the remote file manager.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16048: Could not download file due to authentication failure.

Cause: The credentials provided to the remote file manager were invalid.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16049: Invalid Container Document

Cause: The configuration file was invalid. See the message for more details.

Action: See the error message for details on why the document is invalid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16050: Element 'feature' was encountered while an active 'feature' was being processed.

Cause: A feature element was encountered by the container while the container was parsing a previous feature element.

Action: Ensure your maf-feature.xml file conforms to the required format.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16051: The Feature Id, '_Control_Channel_' conflicts with a reserved VM Channel Identifier Name

Cause: A feature element is using '_Control_Channel_' as its id. This is a reserved feature id.

Action: Use a different feature id.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16052: Class 'OracleAdfmfFeature' was initialized with a wrong element type.

Cause: An internal error has caused the feature object model to be initialized with an element other than feature.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16053: Bad State

Cause: The remote file manager has been initialized with a nil URL.

Action: Initialize the remote file manager with a non-nil URL string.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16054: File url cannot be nil

Cause: The remote file manager has been initialized with a nil URL.

Action: Initialize the remote file manager with a non-nil URL string.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16055: Attempted to add an object that was not an ASIHTTPRequest to an ASINetworkQueue

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16056: Create Contact Error

Cause: During the save of a contact in the PhoneGap handler an error was encountered and the contact could not be saved.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16057: Remove Contact Error

Cause: During the delete of a contact in the PhoneGap handler an error was encountered and the contact could not be deleted.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16058: Invalid argument Error

Cause: During contact operation an error was encountered that indicates an invalid argument was passed in.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16059: Timeout Error

Cause: During contact operation an error was encountered that indicates a timeout had occurred.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16060: Pending operation Error

Cause: During contact operation an error was encountered that indicates a pending operation error occurred.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16061: I/O Error

Cause: During contact operation an error was encountered that indicates an IO error occurred.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16062: Not Supported Error

Cause: During contact operation an error was encountered that indicates that contacts on this device are not supported.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16063: Permission Denied Error

Cause: During contact operation an error was encountered that indicates this user does not have permissions for the operation.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16064: Unknown Error

Cause: During contact operation an unknown error was encountered.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16066: Invalid Class

Cause: A class is missing an implementation of a function that must be overriden.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16067: Class missing an implementation of a required function. Enable debug to log information about the class.

Cause: A class is missing an implementation of a function that must be overriden.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16068: Feature view class not found.

Cause: A custom native Objective-C classname was specified as a feature view. That class could not be found.

Action: Ensure the library is properly linked in and the classname was properly specified.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16069: Feature view class could not be created.

Cause: A custom native Objective-C classname was specified as a feature view. That class was found but could not be allocated.

Action: Ensure the library is properly linked in and the classname was properly specified.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16070: View controller provided a nil view for feature view.

Cause: A custom native Objective-C classname was specified as a feature view controller. That class was found and created but when it provided its view it returned nil.

Action: Ensure the library is properly linked in and the classname was properly specified. Ensure your view controller returns a view.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16071: Class is not a valid view type. Currently supported subclass must be from: UIView or UIViewController

Cause: A custom native Objective-C classname was specified and was found to be something other than a UIView or UIViewController.

Action: Ensure the specifed custom native Objective-C classname is a UIView or UIViewController.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16072: An HttpURLConnection used by a feature was not found.

Cause: A feature specified a connection that was not found in the connections.xml configuration file.

Action: Ensure the feature specifies a valid connection.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16073: An HttpURLConnection used by a feature has a nil url.

Cause: A feature specified a connection that was found in the connections.xml configuration file but had a nil URL.

Action: Ensure the feature specifies a connection that has a url.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16074: Invalid Message

Cause: An invalid message was found. See the error message for more details.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16075: Unknown Message Type specified by message.

Cause: A low level ADF Message type other than 10000 was encountered.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16076: Login Error

Cause: There was an error logging into the app or a feature. See the message for more information.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16077: Configuration Error

Cause: There was an error while configuration service was processing the configuration files.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16078: UIWebView Load Failure

Cause: The Web UI failed to load. See the error message for more details.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16079: Failed to load feature '%@' URL: %@

Cause: The Web UI failed to load. This error should contain the content of the error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16080: Please contact administrator.

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16081: The login server is not reachable.

Cause: This error code is returned by NSNetwork and IDM Mobile SDK passes it through. This error code indicates that network is active and Internet is reachable but cannot reach the specified login connection URL. Possible cause is the target server down, error in URL, etc.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16082: Invalid username/password. If the problem persists, please contact your system administrator.

Cause: The user has entered an invalid password and username combination.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16083: Configuration error. Contact administrator.

Cause: These error codes are returned by IDM Mobile SDK and indicates some sort of configuration error. because of the configuration error, SDK could not create a authentication request, or server returned error code that indicates configuration error in the request.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16084: ACS Failed

Cause: There was a authentication failure. See the error message for more details.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16085: Invalid ACS configuration. User object was not retrieved correctly due to ACS configuration error. User may not be registered to ACS. Contact administrator.

Cause: An invalid ACS configuration for this user.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16086: Server is not reachable. Make sure your device is connected to Internet.

Cause: The authentication server can not be reached.

Action: Make sure your device is connected to Internet. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16087: Invalid username/password. Please try again.

Cause: The user entered an invalid username/password combination.

Action: Enter the correct username or password. Ensure you have a valid username.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16088: Configuration error. Access control service URL is missing. Contact administrator.

Cause: The security configuration is incorreclty missing a service URL.

Action: Provide the valid URL.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16089: You exceeded maximum allowed login attempts. You are locked out. Contact administrator.

Cause: The user has attempted to login with bad credentials too many times.

Action: Shutdown the app and restart it to try again.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16090: The check for configuration changes could not be performed. Please check your network connection or contact an administrator.

Cause: There was an error while trying to download the new configuration and test if it has changed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16091: Could not update configurations from configuration service.

Cause: The new configuration files could not be moved into place for use after new configuration was found on the server.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16092: Malformed Message

Cause: A message was sent to the native framework from the CVM and it did not have the proper format.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16093: Empty request message is not allowed.

Cause: A VM Message was sent to the native framework from the CVM which resulted in a nil ADF Message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16094: Unsupported Message

Cause: An invalid message was sent to the native framework from the CVM. See the message for more details.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16095: System messages are not supported on this channel

Cause: A system message was sent to the native framework from the CVM on a channel that does not have a system message handler.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16096: Invalid system request %@

Cause: A system message was sent to the native framework from the CVM but resulted in a non-AdfSystemRequest ADF Message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16097: Application messages are not supported on this channel

Cause: An application message was sent to the native framework from the CVM on a channel that does not have an application message handler.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16098: Invalid application request %@

Cause: An application message was sent to the native framework from the CVM but resulted in a non-AdfApplicationRequest ADF Message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16099: Unhandled Message

Cause: A message was sent to the native framework from the CVM but resulted in a non-application and non-system ADF Message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16100: UnhandledAdfMessage - ReferenceId: %d Type: %d Body: %@

Cause: A message was sent to the native framework from the CVM but resulted in a non-application and non-system ADF Message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16101: Received an unsolicited response message

Cause: A response message was sent to the native framework from the CVM but there was no recorded request expecting the response.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16102: Received an unknown message type

Cause: A message was sent to the native framework from the CVM abd resulted in a non-request and a non-response message.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16103: AdfChannel.handle - Error handling the VMChannel message: %@ - ERROR: %@

Cause: An exception occurred while processing a message sent to the native framework from the CVM.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16104: No '%@' specified. Error dropped: '%@'

Cause: An exception occurred in the processor for container utilities calls and a recovery could not be made. The request was lost.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16105: Device access disabled for feature '%@': url:%@, baseUrl:%@, msg:%@

Cause: A feature that was not granted access to the device through white listing made a PhoneGap request.

Action: Ensure the feature is granted white list access to the device.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16106: URL not allowed device access for feature '%@': url:%@, baseUrl:%@, msg:%@

Cause: A URL that was not granted access to the device through white listing made a PhoneGap request.

Action: Ensure the URL is included in the white list providing access to the device.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16107: ERROR During Whitelist: %@

Cause: There was an unexpected error during the processing of the white list for a device access request.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16108: Unable to send updated width/height to Java side

Cause: The native class used to update the width and height was not found or the required method was missing.

Action: Ensure the proper libraries are linked in. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16109: Unable to register for network status change events. The network status will be unavailable

Cause: The iOS API class for registering for netowkr changes was either not found or did not have the required method.

Action: Ensure the proper libraries are linked in. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16110: The default login connection, '%@', is not defined.

Cause: A default authorization connection was specified but it was not found in the connections.xml file.

Action: Add the connection to the connections.xml file.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16111: Skin '%@' is missing a family. Ignored.

Cause: A skin family in the specified skin was not found so the skin could not be added.

Action: Add a family to your skin.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16112: Active skin family '%@' returned no skin.

Cause: There was no skin family found for the configured active skin.

Action: Ensure you have specified the correct skin-family in your maf-config.xml file.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16113: Attachment %@ was not found or could not be read

Cause: During the attempt to send out an e-mail, the attachments specified could not be found at the specified location on the device.

Action: Ensure you have passed in the correct location for the file to be attached.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16114: %@ does not support deliverResponseJson:toCallbackSet:forRequest:

Cause: A UIView that does not implement deliverResponseJson was asked to deliver a response JSON.

Action: Implement the method deliverResponseJson:toCallbackSet:forRequest: on your custom view.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16115: %@ is not defined in the webview. JavaScript result call aborted.

Cause: While trying to deliver a response JSON message to a UIWebView it was discovered the response handler JavaScript functions do not exist.

Action: During normal use this should not happen. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16116: There was a problem calling the function '%@': %@

Cause: An unexpected response was received while delivering a JSON response to a UIWebView JavaScript.

Action: During normal use this should not happen. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16117: ERROR: encountered an exception when executing the %d callback: %@

Cause: An exception was generated while attempting to deliver a JSON response to a UIWebView JavaScript.

Action: During normal use this should not happen. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16118: Application Authentication Error. Reason = %@

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16119: Feature Authentication Error. Feature disabled. Reason = %@

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16120: Authentication Error. Please retry.

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16121: ACS returned error: %@

Cause: Generic Authentication Error. The message will provide the details.

Action: See the details in the message.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16122: ACS not configured for connection %@. User objects are not registered.

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16123: Application level login failed due to missing authentication context.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16124: File Exists At Cache Path

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16125: Cannot create a directory for the cache at '%@', because a file already exists

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16126: Failed To Create Cache Directory

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16127: Failed to create a directory for the cache at '%@'

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16128: Failed To Traverse Cache Directory

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16129: Listing cache directory failed at path '%@'

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16130: Failed To Remove Cache File

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16131: Failed to remove cached data at path '%@'

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16132: Crashing Now because configuration could not be downloaded.

Cause: This message will appear if the configuration service could not download the configuration on the first launch.

Action: Ensure you have network access. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16133: Show Feature Failed

Cause: An exception occurred during the show of a feature. See the message for more details.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16134: Could not show feature. Attempt to show feature '%@' failed. ERROR: %@

Cause: An exception occurred during the show of a feature. The message should have more details about the failure.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16135: Application Controller Error

Cause: The folder specified as the application controller cannot be found.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16136: The application controller folder '%@' does not exist.

Cause: The folder specified as the application controller cannot be found.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16137: Could not load .properties file: %@ - ERROR: %@

Cause: Phrase appears to be unused.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16138: Error serializing return: %@

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16139: FeatureId could not be determined. Aborting call to Java Class.

Cause: The feature id could not be obtained from the ADFFeature.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16140: CVM Channel verification failed.

Cause: The ping/pong message on CVM starup did not succeed. This means the CVM did not properly start because a value of pong was not retured.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16141: CVM returned an unexpected object type: %@

Cause: The ping/pong message on CVM starup did not succeed. This means the CVM did not properly start because a string was not returned.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16142: Cannot Send Message

Cause: Title indicating an SMS message could not be sent.

Action: Ensure you have access to SMS and it is properly configured.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16143: Unable to send message as text messaging is not available on this device.

Cause: An error indicating an SMS message could not be sent.

Action: Ensure you have access to SMS and it is properly configured.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16144: Unable to send message as unable to get text message composer.

Cause: An error indicating an SMS message could not be sent.

Action: Ensure you have access to SMS and it is properly configured.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16145: AdfGenericInvokeHandler.processRequest - The 'classname' was not specified

Cause: The class name was not provided to the native container invoke method.

Action: Include the classname for the object type you want to call.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16146: adfGenericInvokeHandler.processRequest - The morphClassName call caused an ERROR: %@

Cause: The class name provided to the native container invoke method could not be morphed into an Objective-C class name.

Action: Ensure the class name you have provided is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16147: AdfGenericInvokeHandler.processRequest - The 'classname' morphClassName failed.

Cause: The class name provided to the native container invoke method could not be morphed into an Objective-C class name.

Action: Ensure the class name you have provided is valid.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16148: AdfGenericInvokeHandler.processRequest - The 'method' was not specified

Cause: The method name was not provided to the native container invoke method.

Action: Ensure the method name is provided.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16149: Could not create class: %@

Cause: The class name provided to the native container invoke method did not result in an Objective-C class.

Action: Ensure the class name you have provided is valid. Ensure the libraries your class is in have been linked into the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16150: Requested class to be invoked could not be created: %@

Cause: The class name provided to the native container invoke method resulted in an Objective-C class that was found but could not be created.

Action: Ensure the class name you have provided is valid. Ensure the libraries your class is in have been linked into the application.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16151: Instance of %@ class does not respond to '%@' selector.

Cause: The class name provided to the native container invoke method result in an Objective-C class that does not support the method name requested.

Action: Ensure the class name you have provided is valid and has a selector that has a single parameter.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16152: Invoking '%@' caused error: %@

Cause: The class name provided to the native container invoke method result in an Objective-C class that generated an error during the invoke of the requested method.

Action: Ensure the class name you have provided is valid and has a selector that has a single parameter and that method does not throw and exception.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16153: Serializing result from '%@' on %@ type caused ERROR: %@

Cause: The class name provided to the native container invoke method result in an Objective-C class that returned an object that could not be serialized to JSON.

Action: Ensure the class/method name returns a JSON serializable object such as an NSDictionary or NSArray.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16154: Serializing result from '%@' on %@ type generated nil.

Cause: The class name provided to the native container invoke method result in an Objective-C class that returned an object that could not be serialized to JSON.

Action: Ensure the class/method name returns a JSON serializable object such as a non-nil NSDictionary or NSArray.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16155: credentialStoreKey for connection %@ cannot be nil

Cause: Incorrect security configuration, see your admin.

Action: Check connections.xml and ensure that adfCredentialStoreKey attribute exists inside the Reference element for the connection name %@
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16156: credentialStoreKey for connection cannot be nil

Cause: Incorrect security configuration, see your admin.

Action: Check connections.xml and ensure that adfCredentialStoreKey attribute exists inside the Reference element for all connections
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16157: General login error occurred. User might have entered invalid credentials, or login connection configuration may contain error. E.g. login URL and/or cookie name may be missing or wrong.

Cause: There was an error logging into the app or a feature. See the message for more information.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16158: The server cannot be reached. Please make sure you are connected to internet.

Cause: This error code is returned by NSNetwork and IDM Mobile SDK passes it through. This error code indicates that network is active but Internet is not reachable. Possible cause is the proxy setting error, firewall down, ISP down, etc.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16159: Error in threadShellInitializationComplete: %@

Cause: While processing the initilization of the UI after the configuration files were loaded, an exception was generated.

Action: See the message for more details. Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16160: Error in paintMirrorLoop: %@

Cause: There was an exception when tryign to paint the screen mirror.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16161: ACS not configured for default connection and constrained features are not made available.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16162: Error in Username

Cause: An attempt was made to login with a username different from the original login. This is not supported.

Action: Shutdown the application to log in as a different user.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16163: User name and/or tenant name used are different from original user name and/or tenant name. You need to correct the user name and/or tenant name if you entered wrong user name and/or tenant name. To log in as a new user, you must first exit application.

Cause: An attempt was made to login with a username different from the original login. This is not supported.

Action: Shutdown the application to log in as a different user.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16164: Multi-tenant header name is missing

Cause: The app is configured for multi-tenant and no multi-tenant header name was found.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16165: Cannot authenticate as not enough information is provided for authentication in multi-tenant application. Configuration is missing multi-tenant header name. Contact administrator.

Cause: The app is configured for multi-tenant and no multi-tenant header name was found.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16166: Tenant name was not entered

Cause: The user did not enter a tenant name.

Action: Enter a tenant name in the login dialog.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16167: Cannot authenticate as tenant name was not provided. Please retry.

Cause: The user did not enter a tenant name.

Action: Enter a tenant name in the login dialog.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16168: Application level login will be attempted. Server=%@ for user=%@

Cause: Logged just before the login is being attempted.

Action: No action needed. This is just information.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16169: Application level login succeeded.

Cause: Logged just after the login succeeded.

Action: No action needed. This is just information.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16170: OMCredentialStore did not return property for kSecAttrLabel.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16171: Application user objects is fetched from credential store: %@

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16172: User authentication test returns %@.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16173: Feature level login failed due to unexpected condition.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16174: Feature level login attempt for user=%@.

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16175: Feature level logout attempt.

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16176: User objects are being pulled as it is a remote feature login.

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16177: Authentication success.

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16178: returned user objects response=%@

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16179: returned user objects privileges=%@ roles=%@

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16180: Invoking ACS with payload=%@.

Cause: Internal information (security).

Action: No action needed.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16181: CredentialStoreHandler.logout: authContext was not obtained.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16182: CredentialStoreHandler.isAuthenticated: pausedFeature was not obtained.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16183: CredentialStoreHandler.isAuthenticated: authContext was not obtained.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16184: CredentialStoreHandler.login: pausedFeature was not obtained.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16185: CredentialStoreHandler.login: authContext was not obtained.

Cause: Internal error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16186: Configuration Error

Cause: Configuration error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16187: Application login connection is not defined. This application cannot be run. Contact administrator.

Cause: Configuration error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16188: Feature login connection is not defined. This feature cannot be accessed. Contact administrator.

Cause: Configuration error (security).

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16189: Logout

Cause: Title for a shutdown notification due to logout.

Action: No action.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16190: Logout was initiated. Application will terminate.

Cause: Message that the application is shutting down due to a logout.

Action: No action.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16191: Login connection configuration error. {0} Contact administrator.

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16192: Credential Store Key is not specified.

Cause: Configuration error. Credential store key in connection.xml is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16193: Invalid or missing username and/or password.

Cause: Username and/or password is not correctly entered.

Action: Edit and retry.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16195: Error in composite credential store key.

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16196: Invalid Access Control Service URL.

Cause: Configuration error. Access Control Service URL is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16197: Invalid Logout URL.

Cause: Configuration error. Logout URL is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16198: Invalid Login URL.

Cause: Configuration error. Login URL is missing or malformed.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16199: Cookie is not specified.

Cause: Configuration error. Login server cookie is not configured correctly.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16200: Idle timeout must be 10 or larger, session timeout must be 30 or larger and larger than idle timeout.

Cause: Configuration error. Error in timeout values.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16201: Login Connection Configuration Error

Cause: Configuration error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16202: Authentication URL responded with illegal HTTP response code. It is not a basic authentication end point. Please contact administrator.

Cause: Configuration error. The login URL responded with an HTTP response code that cannot be processed by basic authentication response handler. The login URL cannot be used as the authenticaton URL.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16203: File not found: %@

Cause: The URL was not pointing to an existing file.

Action: Please provide a URL that points to an existing file.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16204: The email message was not saved or queued, possibly due to an error.

Cause: Network or configuration error.

Action: Verify the device is connected to the network and that at least one e-mail account is properly configured.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16205: An error occurred trying to save the email message to the Drafts folder.

Cause: An underlying operating system error prevented the e-mail draft from being saved

Action: Ensure the device has sufficient free space to save the draft.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16206: An error occurred while trying to queue or send the email message.

Cause: Network or configuration error.

Action: Verify the device is connected to the network and that at least one e-mail account is properly configured.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16207: An unknown error occurred while trying to compose or send an e-mail

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16208: An unknown error occurred while trying to compose or send a text message

Cause: Internal error.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16209: File not found

Cause: Used as a title for an error when a URL points to a non-existant location.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16210: Encountered an invalid prefix to URI mapping. Prefix: %@ is already mapped to URI: %@, re-mapping the prefix to URI: %@ is not allowed

Cause: The metadata contains same prefix mapped to multiple URI's.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16211: Encountered an invalid prefix to URI mapping. URI: %@ is already mapped to prefix: %@, re-mapping the URI to prefix: %@ is not allowed

Cause: The metadata contains multiple prefixes mapped to a URI.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16212: Unable to find UIWebview for feature %@.

Cause: There seems to be some problem with the internal view structure.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16213: Calling Invoke Java on another feature is not allowed.

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16214: Access violation

Cause: A request was made to invoke Java from a feature using some other feature's ID. This is not allowed.

Action: The developer needs to either remove the Feature ID from the request or use the feature ID or the background Channel ID.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16215: Unable to encrypt password: %@

Cause: A problem occurred while attempting to encrypt the generated password.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16216: Unable to generate password via hashing: %@

Cause: A problem occurred while attempting to generate a password.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16217: Unable to decrypt password: %@

Cause: A problem occurred while attempting to decrypt the generated password.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16218: Invalid parameter key. ParameterKey= %@

Cause: A problem occurred while iterating through parameter list before persisting them.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16219: loginComplete failed with exception: %@

Cause: A problem occurred in loginComplete.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16220: Could not determine the return type of class %@ for method %@.

Cause: The return type of the method being invoked could not be determined.

Action: Ensure the class name you have provided is valid and has a selector that has a single parameter that returns a supported type.
Level: 1

Type: ERROR

Impact: Logging

ADF-MF-16221: Invalid return type for method %@ in class %@.

Cause: The return type of the method being invoked is not void or an Objective-C object.

Action: Ensure the class name you have provided is valid and has a method that returns either void or an Objective-C object.
Level: 1

Type: ERROR

Impact: Logging

3 ADF_TRINID-00001 to ADF_TRINID-30336

ADF_TRINID-00001: Could not find FacesBean class {0}

Cause: FacesBean class name could not be found.

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00002: Could not create instance of FacesBean {0}

Cause: IllegalArgumentException

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00003: No faces-bean.properties files located

Cause: Could not find the faces-bean.properties file in any jar

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-00004: Could not load {0}

Cause: Cannot find the url

Action: Log a bug against the application. Check that the jsf jars are all installed correctly. Check that the url is written correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00005: Error on trying to create new component instance for {0}

Cause: Error in ChangeManager

Action: Log a bug against the application. Check that the Trinidad and jsf jars are all installed correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00006: Conversion class: {0} not of type {1}

Cause: Error in ChangeManager

Action: Change the type so that it can be converted or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00007: Unable to instantiate converterClass: {0}

Cause: Error in ChangeManager

Action: Make sure the converter class can be instantiated or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00008: Saved child count does not match current count (was {0}, now {1})

Cause: Error in TreeState implementation

Action: Fix the TreeState implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00009: State for some facets of {0} is missing, and will not be restored.

Cause: Error in TreeState implementation

Action: Fix the TreeState facet state implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00010: Saved facet state includes state for facet "{0}" which is not present in restored tree; discarding this state.

Cause: Error in TreeState implementation

Action: Fix the TreeState facet state implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00011: Saved state includes state for a transient component: {0}

Cause: Error in TreeState implementation

Action: Fix the TreeState state implementation or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00012: Could not find rowKey for clientRowKey:{0}

Cause: Error in UIXCollection implementation when setting/getting clientRowKey

Action: Fix UIXCollection implementation or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00013: There was no initial stamp state for currencyKey:{0} and currencyKeyForInitialStampState:{1} and stampId:{2}

Cause: Error in UIXCollection

Action: Fix UIXCollection implementation or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00014: Could not find renderer for {0} rendererType = {1}

Cause: Error in renderer registration on render kit

Action: Log a bug against the application and make sure the Trinidad jars are installed and check the faces-config.xml files.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00015: Could not load type properties

Cause: Error getting faces-bean-type.properties from any jar

Action: Log a bug against the application and make sure the Trinidad and jsf jars are installed.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00016: Could not get resource key {0} from skin {1}

Cause: ResourceBundle key does not exist in any resource bundle in framework or skin.

Action: Log a bug against the application or make sure the resource key exists in skin by checking the skin resource files (see trinidad-skins.xml).
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00017: Trying to attach RenderingContext to a thread that already had one.

Cause: Thread already had a RenderingContext attached to it.

Action: Log a bug against the application. Call release()
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00018: Cannot find RequestContext; two-digit-year-start will be defaulted

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00019: Cannot find RequestContext; TimeZone will default.

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00020: Failed to get hold of DecimalFormat for type: {0} decimal separator, number grouping separator, currency code will be defaulted based on locale {1}

Cause: DecimalFormat not set up

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00021: RequestContext is null: decimal separator, number grouping separator, currency code will be defaulted based on locale

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00022: RequestContext is null, unable to get currency code

Cause: RequestContext was not set up yet.

Action: Log a bug against the application. Make sure all jars are installed and filters are specified correctly in web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00023: Number format was not instance of DecimalFormat: ignoring currency information while formatting.

Cause: Number format was not set up correctly.

Action: Set up the Number format correctly or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00024: CollectionModel was set to null

Cause: setCollectionModel was passed a null parameter

Action: Check the code that calls setCollectionModel or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00025: Invalid rowkey:{0} type:{1}

Cause: ClassCastException rowkey should be an Integer

Action: Fix the rowkey to be an Integer or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00026: The viewId property in ViewIdPropertyMenuModel is null. The viewId property is needed to find the focus rowKey.

Cause: viewIdProperty that is used to retrieve the viewId from a node in the tree is null.

Action: Set the viewIdProperty to be non-null or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00027: EL Expression {0} is invalid or returned a bad value

Cause: ELExpression evaluation caused an exception

Action: Fix the ELExpression to be valid or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00028: Exception opening URI {0}

Cause: Exception in openStream

Action: Check the URI. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00029: Exception creating menu model {0}

Cause: Exception while creating menu model

Action: Fix the menu model code or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00030: Resource "{0}" at path "{1}" not found

Cause: Error calling getResource

Action: Make sure the resource can be found or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00031: Unable to retrieve image data for icon of type {0}. Try using ContextImageIcon.

Cause: Icon openStream method called, and it is not supported.

Action: Try using a ContextImageIcon in your code instead or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00032: Error parsing:{0}

Cause: Error parsing a service from a file in /META-INF/services

Action: Check the services to make sure the urls are valid or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00033: error loading resource:{0}

Cause: IOException while loading services

Action: Check your server or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00034: Resource name "{0}" begins with a slash, which is not portable.

Cause: resource name begins with a slash and it shouldn't.

Action: Fix the resource name to not begin with a slash or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00035: unable to load bundle {0}

Cause: MissingResourceException; bundle could not be loaded.

Action: Fix the resource bundle so that it can be loaded or log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00036: Unable to load faces bundle {0}

Cause: MissingResourceException

Action: Make sure the jsf jars are installed correctly. Make sure you can find the faces bundle. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00037: Unable to find ResourceLoader for ResourceServlet at servlet path:{0} Cause: Could not find resource:{1}

Cause: Resource missing

Action: Make sure the resource can be found. Make sure the jars are installed correctly. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00038: Trinidad ResourceServlet is running in debug mode. Do not use in a production environment. See the {0} parameter in /WEB-INF/web.xml

Cause: Application is running in debug mode.

Action: Change the parameter in web.xml so that it is not running in debug mode.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-00039: Could not find context class loader.

Cause: Thread.getContextClassLoader returned null.

Action: Fix the code so the ContextClassLoader can be loaded. Check the web server.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00040: Could not convert:{0} into int[]

Cause: value is not a list of integers

Action: Change the value so that it can be converted to an array of integers. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00041: Could not parse value {0} into a Date using pattern "yyyy-MM-dd"; ignoring.

Cause: date property's value is not in the correct format

Action: Nothing if the pattern it uses is ok. Otherwise log a bug against the application.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-00042: no parent <tr:componentRef> found!

Cause: No parent componentRef component exists

Action: Log a bug against the application. Add a componentRef component on the page.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-00043: Event {0} was delivered to a showDetail already in that disclosure state.

Cause: Renderer delivered an unnecessary event or it set disclosed on its own instead of waiting for the disclosure event.

Action: Check the showDetail renderer code or log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-00044: Name "{0}" had already been registered.

Cause: FacesBean addKey with name already added.

Action: Make sure you do not have duplicate names. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00045: Index "{0}" had already been registered.

Cause: FacesBean addkey with index already added

Action: Make sure you do not have duplicate indexes. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00046: Type is already locked

Cause: The FacesBean type object is locked, preventing further changes. . IllegalStateException, name already in keymap

Action: Fix code that has locked the FacesBean.Type. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00047: Property "{0}" cannot be bound.

Cause: IllegalArgumentException, trying to set valuebinding on a key that does not support binding

Action: Do not valuebind the property or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00048: Key {0} cannot be used for lists

Cause: IllegalArgumentException, PropertyKey is not a list and it should be to call this method.

Action: Fix the code so that the PropertyKey can be used for lists or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00049: Key {0} is a list key

Cause: IllegalArgumentException, propertykey passed is a list and it shouldn't be.

Action: Fix code so that the propertyKey is not a list key or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00050: Default value {0} is not assignable to type {1}

Cause: IllegalStateException; PropertyKey constructor error

Action: Fix the PropertyKey constructor to pass in a non-null defaultValue parameter or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00051: Capability mask {0} not understood

Cause: IllegalStateException; PropertyKey constructor error

Action: Check the PropertyKey API and use a valid Capability mask or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00052: Invalid index

Cause: IllegalStateException; PropertyKey constructor error

Action: Check the PropertyKey API and provide a valid index to the PropertyKey constructor or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00053: Attempt to add a duplicate ID {0}

Cause: ChangeManager, already a child with ID

Action: Remove duplicate ids or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00054: No node specified

Cause: ChangeManager, componentNode passed to the method is null.

Action: Specify a node or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00055: component required

Cause: ChangeManager, constructor error

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00056: DocumentFragment required

Cause: ChangeManager, IllegalArgumentException

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00057: Cannot construct an AttributeChange with null attribute name.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00058: Cannot add a Change with either of facesContext, uiComponent or Change being null.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Check the ChangeManager API and code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00059: Cannot construct an ChangeComponentProxy with null uiComponent.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Use a non null UIComponent parameter in the ChangeComponentProxy. Check the API. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00060: target class name must be provided

Cause: ChangeManager, IllegalArgumentException

Action: Fix call to ChangeManager.registerDocumentFactory to provide a targetClassName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00061: converter class name must be provided

Cause: ChangeManager, IllegalArgumentException

Action: Fix call to ChangeManager.registerDocumentFactory to provide a converterClassName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00062: Parent cannot be null

Cause: ChangeManager, null parameter

Action: Set the parent to be non-null or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00063: Cannot construct a RemoveChildChange with null childId.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to provide a non-null childId or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00064: Cannot construct a RemoveFacetChange with null facetName.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null facetName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00065: Cannot construct a ReorderChange with null childIds.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null childId or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00066: Cannot construct an AddFacetChange with either of facetName or facetComponent being null.

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null facetName or facetComponent or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00067: Facet name must be specified

Cause: ChangeManager, IllegalArgumentException, constructor error

Action: Fix the constructor to use a non-null facetName or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00068: index:{0} size:{1}

Cause: ChildArrayList was not built properly

Action: Fix the code that builds the ChildArrayList or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00069: Bad PhaseId:{0}

Cause: The phaseId passed to the method is invalid

Action: Make sure the phaseId is valid when calling this method or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00070: Illegal id: {0}

Cause: The component has a bad id. First character might be a separator character or empty

Action: Fix the illegal component id in your page or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00071: wrappedEvent

Cause: Illegal use of the WrapperEvent constructor. The wrappedEvent parameter was null.

Action: Fix the code that creates a WrappedEvent object or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00072: RenderingContext was already released or had never been attached.

Cause: An attempt was made to release an unattached RenderingContext

Action: Fix the code that tried to release the RenderingContext or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00073: Trying to release a different RenderingContext than the current context.

Cause: An attempt was made to release a RenderingContext that is not the current RenderingContext.

Action: Fix the code that tried to release the RenderingContext or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00074: This is not an error. This trace is for debugging.

Cause: This is not an error. This trace is for debugging the RequestContext class.

Action: No action needed since this is a debugging log message only. You can set the LOG to greater than FINEST to turn off the message.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00075: Trying to release a different RequestContext than the current context.

Cause: An attempt was made to release a RequestContext that is not the current RequestContext.

Action: Make sure the release method was called by the same code that created the RequestContext or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00076: Factory already available for this class loader.

Cause: IllegalStateException, an attempt was made to set in a map a RequestContextFactory that already exists for this classloader

Action: Do not call setFactory(RequestContextFactory factory) with a RequestContextFactory that already exists for the class loader or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00077: Supplied FacesContext or UIComponent is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Fix the code that caused this NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00078: FacesContext or UIComponent is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Fix the code that caused this NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00079: Patterns should contain atleast one value and cannot be null

Cause: IllegalArgumentException in ColorConverter; pattern is null or empty

Action: Fix the pattern in the ColorConverter or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00080: Cannot format given Object as a Color

Cause: Object passed to method was not an instance of Color or Number

Action: Fix the Object that you pass into the method or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00081: Invalid attribute name {0}

Cause: IllegalArgumentException, attribute name not found in FacesBean.Type

Action: Check your value bindings to make sure the attribute name exists or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00082: value:"{0}" is not of type java.util.Date, it is {1}

Cause: ClassCastException, value is not a String or Date.

Action: Fix the value binding to point to a String or a Date or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00083: Invalid date style ''{0}''

Cause: IllegalStateException, the date style was not default, short, medium, long, full, or shortish.

Action: Fix the DateTimeConverter's dateStyle attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00084: Invalid time style ''{0}''

Cause: IllegalStateException, the time style was not default, short, medium long or full.

Action: Fix the DateTimeConverter's timeStyle attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00085: Invalid type ''{0}''

Cause: IllegalStateException, the type was not "date", "time", or "both"

Action: Fix the DateTimeConverter's type attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00086: Illegal message id unexpected value {0}

Cause: IllegalArgumentException in DateTimeConverter.

Action: Fix the message pattern or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00087: Illegal value for attribute "type" unexpected value {0}

Cause: IllegalArgumentException

Action: Fix the DateTimeConverter's type attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00088: FacesContext or Component is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Fix the code that caused the NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00089: Either "pattern" or "type" must be specified

Cause: IllegalArgumentException, pattern and type parameters were both null.

Action: Set the NumberConverter's type or pattern attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00090: "value" is not of type java.lang.Number

Cause: IllegalArgumentException in NumberConverter

Action: Fix NumberConverter's value to be a Number or String or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00091: {0} is not a valid type

Cause: IllegalArgumentException in NumberConverter. type should be number, currency or percent

Action: Fix NumberConverter's type attribute or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00092: Illegal pattern character ''{0}''

Cause: IllegalArgumentEcxeption in RGBColorFormat when checking the rgb pattern character

Action: Fix the rgb pattern in RGBColorFormat or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00093: Logger required

Cause: TrinidadLogger constructor error

Action: Fix the code that creates the TrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00094: Logger Name required

Cause: Attempt was made to create a TrinidadLogger without a name which is a required parameter to this method.

Action: Check the call to TrinidadLogger.createTrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00095: Class required

Cause: Attempt was made to create a TrinidadLogger without a Class which is a required parameter to this method.

Action: Fix the call to TrinidadLogger.createTrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00096: Package required

Cause: Attempt was made to create a TrinidadLogger without a package which is a required parameter to this method.

Action: Fix the call to TrinidadLogger.createTrinidadLogger or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00097: rowData is null

Cause: IllegalStateException in TreeModel or MenuModel. rowData is null.

Action: Fix rowData or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00098: Cannot exit the root container

Cause: IllegalStateException in TreeModel or MenuModel.

Action: Fix code in the TreeModel or MenuModel regarding the path size or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00099: Illegal value being set - value should be between -1 and maximum

Cause: The constructor was called with the wrong value

Action: Fix the code that creates a DefaultBoundedRangeModel or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00100: Could not convert:{0} into a MenuModel

Cause: IllegalArgumentException, the value could not be converted to a MenuModel.

Action: Fix the MenuModel's value so it can be converted to a MenuModel or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00101: rowKey

Cause: IllegalStateException, PathHelper's rowKey has not been set and is null.

Action: Set PathHelper's rowKey or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00102: No Path element to pop

Cause: IllegalStateException in PathHelper

Action: Fix the path or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00103: Could not clone

Cause: CloneNotSupported, an attempt was made to call clone() on an object that is not clonable.

Action: Make sure the object is clonable before calling the method or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00104: No element to remove

Cause: IllegalStateException, an attempt was made to remove a null element.

Action: Fix the rowKeySet code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00105: todo

Cause: This is only a todo. No cause.

Action: This is only a todo. No action.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00106: property is null

Cause: SortCriterion constructor error, NullPointerException

Action: Fix the NullPointerException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00107: No MenuContentHandler was registered.

Cause: IllegalStateException, no MenuContentHandler was registered on services.

Action: Fix the code to register a MenuContentHandler or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00108: No RenderingContext

Cause: IllegalStateException, RenderingContext is null and it shouldn't be.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00109: Resource path regular expression "{0}" does not have leading slash

Cause: IllegalArgumentException, there was no leading slash and there should be.

Action: Fix the resource path by adding a leading slash or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00110: Factory already available for this class loader.

Cause: IllegalStateException, SkinFactory already available for the class loader.

Action: Fix call to SkinFactory.setFactory or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00111: byte[] cannot be null

Cause: NullPointerException, argument is null

Action: Fix the NullPointerException by setting byte[] to a non-null value or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00112: Actual Length:{0} offset:"{1} length:{2}

Cause: IndexOutOfBoundsException, byte[], offset, length arguments passed to the method are incorrect.

Action: Fix the IndexOutOfBoundsException or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00113: FastMessageFormat only supports numeric arguments

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the arguments passed into the method to be numeric or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00114: End of pattern not found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the FastMessageFormat pattern or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00115: FastMessageFormat: empty argument - {} - found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the call to the method to have a non-empty argument or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00116: bundle not found

Cause: No bundle was found.

Action: Fix the resource bundle (for example, the ApplicationFacesMessageBundle) so that it can be found by the code or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00117: resourceId is null

Cause: NullPointerException. A null value was passed to a method.

Action: Fix the NullPointerException by passing in a non-null resourceid or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00118: The default FacesMessage.FACES_MESSAGES cannot be found

Cause: NullPointerException. FacesMessage.FACES_MESSAGES from the jsf spec could not be found.

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00119: FacesContext is null

Cause: NullPointerException, FacesContext is null when it is passed to a method and it should not be null.

Action: Log a bug against the application. Check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00120: custom message should be of type ValueBinding or String

Cause: IllegalArgumentException, custom message in method was not of the correct type.

Action: Fix the customMessagePattern to be a ValueBinding or a String Object or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00121: Provider {0} did not return an object implementing {1}

Cause: This error is no longer in the code.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00122: FacesContext.getRenderKit() returned null while trying to get the {0} service; please check your configuration.

Cause: IllegalStateException, while getting a service in the Service utility code.

Action: Log a bug against the application. Check your configuration and check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00123: FacesContext or Component is null

Cause: NullPointerException, the FacesContext or UIComponent passed to the method was null.

Action: Log a bug against the application. Check your configuration and check that the jsf jars are all installed correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00124: Encoding: {0} is unsupported by JVM

Cause: IllegalCharsetNameException while trying to encode in the ByteLength Validator using an encoding that is not supported by the JVM.

Action: Check the encoding and check the JVM. Otherwise log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00125: ''value'' is not of type java.util.Date

Cause: Value is not the type it should be.

Action: Change the value to be of type java.util.Date or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00126: Pattern null

Cause: The regular expression's pattern is null and it shouldn't be.

Action: Fix the regular expression to be a non-null value or log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00127: Invalid attribute name {0}

Cause: This error is no longer in the code.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-00128: <f:view> was not present on this page; tag {0}encountered without an <f:view> being processed.

Cause: view tag was not present on the page.

Action: Log a bug against the application. Add a view tag on your jspx page.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30001: The User-Agent "{0}" is unknown; creating an agent with null agent attributes.

Cause: The user-agent of the user's agent is unknown.

Action: Use a known agent, like IE7 or Firefox.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30002: The agent type is unknown; creating an agent with null agent attributes.

Cause: The agent type of the user's agent is unknown.

Action: Use a known agent, like IE7 or Firefox.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30003: could not get capabilities from capabilities document

Cause: RuntimeException when trying to get user agent's capabilities map

Action: Use a known agent, like IE7 or Firefox. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30004: Could not locate Capabilities document

Cause: Could not find Capabilities document META-INF/agent/capabilities.xml

Action: Make sure the Apache Trinidad framework jars are installed. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30005: "Cannot resolve capabilities file"

Cause: Exception while attempting to load the Capabilities document META-INF/agent/capabilities.xml

Action: Make sure the Apache Trinidad framework jars are installed. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30006: Invalid dependency found in include by reference

Cause: Invalid dependency found while resolving the capabilities for a give capabilitiesNode

Action: Use a known agent, like IE7 or Firefox. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30007: Reference to id: {0} not found

Cause: An attempt to get capabilities of node using a node refid, and refid was not found.

Action: Log a bug against the Apache Trinidad framework. Make sure the capabilities document is valid xml.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30008: Failed to parse capabilities document

Cause: An IOException while parsing the XML-based capabilities document.

Action: Log a bug against the Apache Trinidad framework. Make sure the capabilities document is valid xml.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30009: Unable to parse agent string

Cause: ParseException while parsing the agent string.

Action: Use a known agent, like IE7 or Firefox.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30010: Element {0} has missing (or empty) attributes

Cause: While attempting to parse a document, the element should have attributes but doesn't.

Action: Make sure the document that is being parsed has the correct syntax and attributes. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30011: Failed to parse capabilities data document

Cause: The capabilities data document was being parsed and failed.

Action: Log a bug against the Apache Trinidad framework. Make sure the capabilities document is valid xml.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30012: Unable to parse model string

Cause: Error occured while parsing the device nodes in the capabilities file

Action: Check the capabilities document. Make sure the capabilities document is valid xml. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30013: Capability data url {0} is invalid

Cause: MalformedURLException while creating the URL.

Action: Check the capabilities document and make sure url is correctly formed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30014: Could not find saved view state for token {0}

Cause: Could not find the saved view state in the StateManager.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30015: No structure available and no root available

Cause: While attempting to restore the state in the StateManager, no view root was available.

Action: Log a bug against the Apache Trinidad framework or against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30016: No structure available

Cause: While attempting to restore the state in the StateManager, no structure was available.

Action: Log a bug against the Apache Trinidad framework or against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30017: Ignoring servlet init parameter:{0} unable to parse:{1}

Cause: Attempting to parse servlet init parameter gave error.

Action: Check servlet init parameters. Check your web server.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30018: Could not load ViewHandler {0}

Cause: Attempting to load viewhandler threw exception.

Action: Log a bug against the Apache Trinidad framework or against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30019: Apache Trinidad is running with time-stamp checking enabled. This should not be used in a production environment. See the {0} property in WEB-INF/web.xml

Cause: time-stamp checking is enabled in web.xml.

Action: Turn off time-stamp checking in a production environment.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30020: Could not load {0}

Cause: Attempting to load an url and an exception occurred.

Action: Make sure the url can be found on the server. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30021: Could not instantiate UploadedFileProcessor

Cause: Attempting to instantiate UploadedFileProcessor failed.

Action: Make sure the Trinidad jars are installed correctly. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30022: Trinidad is running in debug mode. Do not use in a production environment. See:{0}

Cause: debug mode is turned on.

Action: Set debug to false in web.xml.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30023: Element {0} is not understood

Cause: Attempting to parse WEB-INF/trinidad-config.xml, an invalid element was found.

Action: Check the trinidad-config.xml file to make sure the element is valid.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30024: Element {0} does not support EL expressions.

Cause: Attempting to parse WEB-INF/trinidad-config.xml, and found an element that does not support EL binding EL bound.

Action: Check the trinidad-config.xml file and don't EL bind the element.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30025: "Element {0} only accepts integer values

Cause: Found problem in WEB-INF/trinidad-config.xml.

Action: Check the trinidad-config.xml file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30026: Could not find context class loader.

Cause: Attempting to call Thread.currentThread().getContextClassLoader()

Action: Check the web server. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30027: Configurator services already initialized.

Cause: While initializing the global configurator and the configurator services, discovered they are already initialized.

Action: Do not initial configurator services more than once.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30028: RequestContext had not been properly released on earlier request.

Cause: RequestContext was checked to see if it was released and it wasn't.

Action: No action needed, since the code will clean this up. Check the code to make sure it is properly releasing the RequestContext.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30029: Unable to set request character encoding to {0}, because request parameters have already been read.

Cause: Attempting to set the character encoding after parameters have been retrieved.

Action: Log a bug against the Apache Trinidad framework because the code is calling setCharacterEncoding at the wrong time.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30030: No 'DialogUsedRK' key available for returnFromDialog to do the right thing!

Cause: Return from a dialog caused this error.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30031: Could not queue return event: no launch source

Cause: Attempting to queue return event.

Action: Check your dialog code to make sure the launch source exists. Log a bug against the Apache Trinidad framework or the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30032: RenderKit {0} does not support DialogRenderKitService, and cannot be used to launch dialogs; using a single window instead.

Cause: Attempting to launch dialog.

Action: Use a renderkit that supports DialogRenderKitService or don't use DialogRenderKitService.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30033: Apache Trinidad is using HTTPSession for change persistence

Cause: Notification to tell application developer that Trinidad is using HTTPSession

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30034: Unable to create ChangeManager:{0}

Cause: Exception attempting to create the ChangeManager.

Action: Check your ChangeManager configuration. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30035: Could not find partial trigger {0} from {1}

Cause: Attempting to find partial trigger.

Action: Make sure the partialTriggers are set to an existing component's id. View the jspx page in JDeveloper and JDeveloper will flag the errors for you. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30036: Failed to set character encoding {0}

Cause: Attempting to set character encoding failed.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30037: Detecting request character encoding is disable.

Cause: Exception getting character encoding from ServletRequest.

Action: Enable ServletRequest's character encoding if needed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30038: Failed to obtain ServletRequest#setCharacterEncoding() method: {0}

Cause: Exception getting character encoding from ServletRequest

Action: Enable ServletRequest's character encoding if needed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30039: The component is null, but it is needed for the client id, so no script written

Cause: The UIComponent passed to the method is null.

Action: Make sure you pass an non-null UIComponent into the method. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30040: Client id is null, no script rendered

Cause: The UIComponent passed to the method is null.

Action: Make sure you pass an non-null UIComponent into the method. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30041: Tried to create converter for type {0}, but could not, likely because no converter is registered.

Cause: Attempting to create a converter failed.

Action: Log a bug against the application. Register a converter.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30042: Client id is null, no script rendered

Cause: Attempting to create a converter failed.

Action: Log a bug against the application. Register a converter.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30043: Instantiation of Property {0} failed.

Cause: Attempting to instantiated a Property caused an Exception.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30044: Couldn't get unique name!

Cause: Attempting to get a unique name from the image cache failed.

Action: Log a bug against the Apache Trinidad framework. This exception should never happen.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30045: Elapsed time:{0} secs to encode gif

Cause: Encoding gifs.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30046: laf "{0}" not found.

Cause: Attempting to find the look and feel failed.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30047: Illegal character (space) in "name" attribute

Cause: Attempting to parse the name attribute.

Action: Log a bug against the application. Check the name attribute and remove space
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30048: "name" attribute incorrectly set to "name"

Cause: Attempting to parse the name attribute.

Action: Log a bug against the application. Check the name attribute and remove space
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30049: "name" attribute set to "target", which will cause Javascript errors.

Cause: Attempting to parse the name attribute.

Action: Log a bug against the application. Check the name attribute and remove space
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30050: The value of the "{0}" attribute starts with "javascript:"; this is unnecessary, and in fact can lead to Javascript errors.

Cause: Attempting to write the html to the page.

Action: Fix the attribute in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30051: Elements not closed:

Cause: Attempting to write the html to the page.

Action: Fix the element in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30052: Comments cannot include "--"

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30053: Ending {0} when {1} expected. Passes:{2}

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page.Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30054: Writing attribute outside of element

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30055: Attribute "{0}" output twice; writing attribute as "duplicate_{1}" instead.

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30056: Element End name:{0} does not match start name:{1}

Cause: Attempting to write the html to the page.

Action: Fix this in the jspx page. Log a bug against the application or if it is in the renderer, against the Apache Trinidad framework
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30057: GroupNode {0} refers to no valid node.

Cause: Attempting to process the group node.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30058: Exception creating model {0}

Cause: Attempting to create a menu model.

Action: Fix the menuModel. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30059: EL Expression {0} is invalid or returned a bad value.

Cause: Attempting to create a menu model, and invalid EL expression was found.

Action: Fix the invalid EL expression. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30060: Resource bundle {0} could not be found.

Cause: Attempting to load a bundle in the menu model.

Action: Make sure the resource bundle can be found. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30061: error closing file:{0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30062: Error getting region-metadata files:{0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml and make sure it can be found on the filesystem. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30063: Error reading region-metadata file:{0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30064: Replaced jspUri {0} with {1} for componentType:{2}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30065: Unknown element:{0} at {1}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30066: <{0}> is missing at {1}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30067: Exception at {0}

Cause: Attempting to process the region metatdata file.

Action: Fix the region metadata file to be a valid xml. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30068: Instantiation of Renderer {0} failed

Cause: Attempting to instantiate a Renderer failed.

Action: Check that your renderer is registered correctly in faces-config.xml. Log a bug against the application or Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30069: Renderer '{0}' not found for component family '{1}'

Cause: Attempting to instantiate a Renderer failed.

Action: Check that your renderer is registered correctly in faces-config.xml. Log a bug against the application or Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30070: There is no SkinFactory

Cause: Trying to find the SkinFactory failed. The SkinFactory was not registered.

Action: Log a bug against the application. Make sure the TrinidadFilter is installed since this registers the SkinFactory.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30071: The skin {0} specified on the requestMap will not be used because the styleSheetDocument id on the requestMap does not match the local skin's styleSheetDocument's id.

Cause: A skin was specified on the requestMap but it can't be used.

Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30072: The skin {0} specified on the requestMap will not be used because its styleSheetDocument id was not in the requestMap and it is needed to compare with the local skin's styleSheetDocument's id to make sure the skins are the same.

Cause: A skin was specified on the requestMap but it can't be used.

Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match. Also, send the styleSheetDocument id to the server as well as the skin id.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30073: The skin {0} specified on the requestMap will not be used because it does not exist.

Cause: A skin was specified on the requestMap but it can't be used because it does not exist on the server.

Action: Log a bug against the application. Check to make sure the jars on the portal server match the jars on the portlet server to make the skin's styleSheetDocument ids match.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30074: Could not get skin {0} from the SkinFactory

Cause: Attempted to get a skin failed.

Action: Log a bug against the application. The skin requested was not registered with the SkinFactory on startup. Make sure the TrinidadFilter is installed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30075: The java.io.File handle ("javax.servlet.context.tempdir") is not set in the ServletContext

Cause: Attempting to get the file handle from the ServletContext.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30076: No AdfRenderingContext available

Cause: Attempting to get the RenderingContext failed.

Action: Check that your Trinidad jars are installed properly. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30077: Basic HTMLRenderKit could not be located

Cause: Attempting to locate the HTMLRenderKit failed.

Action: Check that your Trinidad jars are installed properly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30078: Could not find basic HTML renderer for {0}, type={1}

Cause: Could not find basic HTML renderer.

Action: Check that your Trinidad jars are installed properly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30079: Could not get stylesheet cache

Cause: Attempting to get the stylesheet cache failed.

Action: Make sure your stylesheet directory is writable.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30080: Model not specified for the chart component.

Cause: Attempting to get the model on the chart component failed.

Action: Specify the model for the chart component. Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30081: Trains must be used inside of a form

Cause: The train component is not inside a form component.

Action: Log a bug against the application. Put the train inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30082: Train expect a nodeStamp facet, no such facet was found for train {0}

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set a nodeStamp facet on the train
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30083: Visible stop count must be > 0, found {0}

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set the train visible count to > 0.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30084: Visible stop count must be an integer, found {0}

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set the train visible count to > 0.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30085: 'nodeStamp' facet missing!

Cause: Problem found while rendering the train.

Action: Log a bug against the application. Set a nodeStamp facet on the train
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30086: Frames must appear inside FrameBorderLayouts

Cause: Problem found while rendering frames.

Action: Log a bug against the application. Set frame inside of frameborderlayout
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30087: No PPR-capable 'id' found for elements of {0}. This component has not written-out an 'id' attribute.

Cause: Trying to PPR update components failed.

Action: Log a bug against the application. Add ids to your components.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30088: Invalid string attribute for chooseDate: {0}

Cause: Attempting to convert value to a Date.

Action: Log a bug against the application. See the chooseDate documentation.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30089: Unable to encode URL '{0}' using encoding '{1}'

Cause: Attempting to encode an url failed.

Action: Recheck your url to make sure it is valid. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30090: Sorting disabled; table is not in a form

Cause: Attempting to render a table that is not in a form.

Action: Log a bug against the application. Add a form as a parent to the table.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30091: {0}: Column used outside of a Table

Cause: Attempting to render a table that has a column outside of the table.

Action: Log a bug against the application. Put all column components inside a table component.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30092: Cannot add client side converter and validators as the node name is null

Cause: Attempting to add client-side converters and validators to the page.

Action: Log a bug against the applicaton. Set the node name.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30093: Null validators iterator for {0}

Cause: Attempting to process validators found null validator iterators.

Action: Log a bug against the application. Check the validators.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30094: There is already a converter on "{0}". There should only be one converter per component.

Cause: More than one converter found on a component.

Action: Log a bug against the application. Ensure you have only one converter per component in your page.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30095: frame:{0} is missing attribute:{1}

Cause: Missing attribute in frameborderlayout.

Action: Log a bug against the application. Add the missing attribute.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30096: Warning: illegal component hierarchy detected, expected UIXCommand but found another type of component instead.

Cause: Did not find the expected command component in the hierarchy.

Action: Log a bug against the application. Check your component hierarchy in your page.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30097: Warning: NavigationLevelRenderer was looking for child property "{0}" but none was found, it is likely that an unexpected child component was found (expected CommandNavigationItem).

Cause: Rendering navigationLevel component and did not find expected child.

Action: Log a bug against the application. Make sure CommandNavigationItem is a child of the navigationLevel component
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30098: PanelAccordion must be used inside of a form

Cause: Rendering panelAccordion that was not in a form.

Action: Log a bug against the application. Make sure panelAccordion is inside a form.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30099: Error during partial-page rendering

Cause: Rendering a partial-page pass failed.

Action: Log a bug against the application. Check your page to make sure you are using PPR correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30100: The poll component must be inside of a form; disabling poll {0}

Cause: Rendering poll component that wasn't in a form component.

Action: Log a bug against the application. Make sure poll is inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30101: The number of items selected for shuttle '{0}' exceeds the total number of items in the shuttle. No selected items will be returned.

Cause: Rendering the shuttle component and the selected items.

Action: Log a bug against the application. Check the shuttle component and its children.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30102: showDetail is not in a form, and will not function correctly

Cause: Rendering showDetail component that wasn't in a form component.

Action: Log a bug against the application. Make sure showDetail is inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30103: Some entries in value of {0} not found in SelectItems: {1}

Cause: Rendering a selectMany component found inconsistency in selectItem values.

Action: Log a bug against the application. Check your selectMany components and the selectItems.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30104: Could not find selected item matching value "{0}" in {1}

Cause: Rendering a select component and found problem with the select items.

Action: Log a bug against the application. Check your select components and the value and selectItems
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30105: Table with id: {0} has no visible columns!

Cause: Rendering a table found no visible columns.

Action: Log a bug against the application. Make sure your table has at least one visible column.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30106: The tree component must be used inside of a form.

Cause: Rendering tree component that wasn't in a form component.

Action: Log a bug against the application. Make sure tree is inside a form
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30107: Couldn't find scriptlet: {0}

Cause: Rendering a component and a scriptlet could not be found.

Action: Check the code that registers teh scriptlet if this is in our component. Log a bug against the application or the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30108: Unable to get resource {0}

Cause: Rendering a scriptlet.

Action: Log a bug against the Apache Trinidad framework. Possibly a problem in the build system.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30109: Apache Trinidad is running with debug javascript. Do not use in a production environment. See the "+_DEBUG_JAVASCRIPT+" parameter in /WEB-INF/web.xml

Cause: debug javascript is enabled in web.xml.

Action: Turn off debug javascript checking in a production environment in web.xml.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30110: Illegal value:{0} for {1}

Cause: Rendering the table component and found illegal banding interval.

Action: Log a bug against the application. See the table and column component documentation regarding column and row banding intervals.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30111: Unknown value for align:{0}

Cause: Rendering the table component and found illegal value for the align attribute.

Action: Log a bug against the application. See the column component documentation for valid align attribute values.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30112: tableSelect components may only be used inside table and treeTable

Cause: While rendering tableSelect component the valid parent component was not found.

Action: Log a bug against the application. Make sure tableSelect components are inside table or treeTable.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30113: nodeStamp facet on treeTable:{0} is missing or not of type UIXColumn

Cause: While rendering a treeTable component, a problem with the nodeStamp facet was found.

Action: Log a bug against the application. See the treeTable documentation and check your jspx page.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30114: Unexpected tree state: focus rowKey is empty on an expand/collapse all request.

Cause: While rendering a tree component an unexpected tree state was found.

Action: Log a bug against the application. See the treeTable or tree documentation and check your jspx page.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30115: Page contains no form, it will not work properly

Cause: Rendering the page without a form component.

Action: Log a bug against the application. Make sure there is a form in the page
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30116: Only tr:showDetailItem is allowed as child of tr:panelTabbed.

Cause: While rendering a panelTabbed component an illegal child was found.

Action: Log a bug against the application. Use showDetailItem as the child of panelTabbed.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30117: Value for component with id '{0}' is not a valid BoundedRangeModel instance

Cause: Rendering component and found an invalid BoundedRangeModel.

Action: Log a bug against the application. See the BoundedRangeModel documentation.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30118: Resource "{0}" at path "{1}" not found

Cause: While rendering the resource was not found.

Action: Make sure the resource exists. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30119: Could not find bundle {0}

Cause: While rendering, a translation bundle could not be found.

Action: Log a bug against the Apache Trinidad framework. Make sure the jars are installed correctly.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30120: Required attribute "{0}" not found.

Cause: While rendering, a required attribute was not found.

Action: Set the required attribute on the component in the jspx file. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30121: {0} is not an understood child element

Cause: While parsing a document, an unknown element was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30122: "{0}" is not an understood attribute

Cause: While parsing the document, an unknown attribute was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30123: Only one child element is allowed here.

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30124: Could not parse value of attribute: {0}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30125: Could not parse value of attribute: {0}, namespace={1}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30126: Unknown attribute: {0}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30127: Unknown attribute: {0}, namespace={1}

Cause: While parsing the document, an error was found.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30128: Error when parsing the skin css file. The property's name cannot be null or the empty string. The parser will ignore it. name is '{0}' and value is '{1}'

Cause: While parsing the skin css file, an error was found.

Action: Log a bug against the application. Check your skin css file.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30129: Ignoring properties {0} because there is no corresponding selector.

Cause: While parsing the skin css file, an error was found.

Action: Log a bug against the application. Check your skin css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30130: Error reading from the skin css file

Cause: While parsing the skin css file, an error was found.

Action: Log a bug against the application. Check your skin css file.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30131: Can't add Skin with null skinId or null skin

Cause: While registering skins, an error was found.

Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30132: Can't get Skin with null skinId

Cause: While retrieving a skin, an error was found.

Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30133: Can't find a skin that matches family {0} and renderkit {1}, so we will use the simple skin

Cause: While retrieving a skin, an error was found.

Action: Log a bug against the application. Check your trinidad-skins.xml file to make sure the skin is defined correctly. Check trinidad-config and the skin-family element. Make sure the skin's renderkitid matches the current renderkit id
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30134: Could not get the stylesheet document's timestamp because we couldn't open the connection.

Cause: Trying to get the skin's stylesheet document's timestamp failed.

Action: Log a bug against the application. Check the stylesheet document file and directory to make sure it can be opened.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30135: The following skins extend each other in a circular fashion or the skin they extend does not exist:{0}

Cause: While registering the skins from the trinidad-skins.xml files, an error was found.

Action: Log a bug against the application. Check all the trinidad-skins.xml files (even the ones in jars on the classpath) to fix any skins that extend others in a circular fashion.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30136: Unable to locate base skin "{0}" for use in defining skin of id "{1}", family "{2}", renderkit ID "{3}". Using the default base skin "{4}".

Cause: While registering the skins from the trinidad-skins.xml files, an error was found.

Action: Log a bug against the application. Check all the trinidad-skins.xml files (even the ones in jars on the classpath) to make sure the base skin exists and do not extend a skin that doesn't exist.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30137: Error parsing:{0}

Cause: While parsing the trinidad-skins.xml file, an error was found.

Action: Log a bug against the application. Check the trinidad-skins.xml files (even ones in jars) for format problems.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30138: error loading file:{0}

Cause: While attempting to load the trinidad-skins.xml file, an error was found.

Action: Log a bug against the application. Check the trinidad-skins.xml files (even ones in jars) for format problems.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30139: Could not load style sheet: {0}

Cause: Could not load the skin's css file.

Action: Log a bug against the application. Check the skin's css file to make sure it exists and the style-sheet-name url in trinidad-skins.xml is correct.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30140: IOException during parse of {0}

Cause: IOException while creating a skin's stylesheet document.

Action: Log a bug against the application. Check the stylesheet document.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30141: No styles found context - {0}

Cause: While creating the skin's stylesheet document, no styles were found that matched the StyleContext.

Action: Log a bug against the application. There should always be base skin definitions for all contexts.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30142: IOException while creating file: {0}

Cause: IOException while creating the skin's stylesheet document.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30143: Unable to generate the style sheet {0} in cache directory {1}.Please make sure that the cache directory exists and is writable.

Cause: Error while generating skin's stylesheet.

Action: Log a bug against the application. Make sure that the cache directory exists and is writable.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30144: IOException while opening file for writing: {0}

Cause: Error while generating skin's stylesheet.

Action: Log a bug against the application. Check the cache directory to make sure it is writable.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30145: The css file has hit IE's limit of 4095 CSS selectors. It has {0} selectors. The selectors after that will be ignored.

Cause: Error while generating the skin's stylesheet.

Action: Log a bug against the application. You will need to simplify your skinning file if possible. Otherwise log a bug against Apache Trinidad.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30146: Consecutive sub-element (::) syntax used in selector {0}. This is not supported.

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. The skin's css file has two pseudo-elements in one selector and that is illegal in CSS.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30147: An url value delimited by url() is expected for the property '{0}' in style sheet '{1}'. Found: '{2}'.

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. Check the skin's css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30148: Invalid image uri '{0}' in style sheet '{1}'

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. Check the skin's css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30149: An empty URL was found in style sheet'{0}'

Cause: Problem found in skin's stylesheet css file.

Action: Log a bug against the application. Check the skin's css file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30150: "<style> elements must have either a name or a selector attribute

Cause: Problem found in skin's XSS stylesheet.

Action: Log a bug against the application. Check the skin's XSS file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30151: Could not parse import: {0}

Cause: Problem found in skin's stylesheet.

Action: Log a bug against the application. Check the skin's stylesheet files.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30152: Import missing required href attribute

Cause: Problem found in skin's stylesheet.

Action: Log a bug against the application. Check the skin's stylesheet files.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30153: 'componentType' attribute is required

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30154: Could not find metadata for componentType:{0} in region-metadata

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30155: There was no jspUri for componentType:{0}

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30156: attribute:{0} is missing on componentType:{1}

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30157: facetRef must be inside of a UIComponent tag.

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30158: Cannot find parent <tr:componentRef>>

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30159: facetName is required on facetRef

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30160: validator tag is not inside a UIComponent.

Cause: Problem found processing page.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30161: could not create validator for validatorId:{0} and binding:{1}

Cause: Problem found creating the validator.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30162: attribute 'validatorId' is missing

Cause: Problem found creating the validator.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30163: Could not parse value {0} into a Date using pattern "yyyy-MM-dd"; ignoring.

Cause: Problem found parsing the date value.

Action: Log a bug against the application. Check the jspx page. Use the yyyy-MM-dd format.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30164: No RendererFactory registered for components in namespace {0}

Cause: RendererFactory not registered.

Action: Log a bug against the Apache Trinidad framework. Make sure the Trinidad and jsf jars are installed correctly.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30165: No Renderer registered for {0}

Cause: Renderer was not registered.

Action: Log a bug against the Apache Trinidad framework or the application. Check the faces-config.xml file.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30166: Could not get image cache

Cause: Could not find the image cache.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30167: Cannot convert {0} of class:{1} into DataObjectList

Cause: Creating a DataObjectList adapter class around an object fails

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: NOTIFICATION

Impact: Logging

ADF_TRINID-30168: Could not convert {0} into a {1}

Cause: Error converting a value into another value.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30169: Unsupported UINode:{0}, path = {1}

Cause: Unsupported UINode found while rendering.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30170: Invalid value. Defaulting component with id '{0}' to indeterminate mode

Cause: Invalid value rendering processing component.

Action: Log a bug against the application. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30171: No form found for {0}

Cause: Rendering a component that wasn't in a form component.

Action: Log a bug against the application. Make sure your form components are inside a form. Check your jspx page in JDeveloper so it can flag the errors.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30172: Could not get image provider for icon: {0}

Cause: Error while attempting to get image provider.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30173: Could not get colorized icon for: {0}

Cause: Error while attempting to get colorized image.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30174: Could not find icon with key given

Cause: Error while attempting to get colorized image.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30175: Could not find renderer for alias {0}

Cause: Error finding renderer.

Action: Check the faces-config.xml file to make sure the renderer is registered. Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30176: Unable to flip icon '{0}' because it is not under the current request context, which is '{1}'

Cause: Error trying to flip laf icon.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30177: Could not locate parent form for formValue {0}

Cause: Rendering the page and couldn't find a form as a parent..

Action: Log a bug against the application. Make sure the formValue has a form parent.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30178: The component is null for node with local name {0}

Cause: Error while finding component.

Action: Check the faces-config.xml file to make sure the component/renderers are registered. Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30179: Could not get flipped icon for: {0}

Cause: Error while trying to find a flipped icon.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30180: The node name is null and therefore no client side required validator added for node with local name {0}

Cause: Error finding validator.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30181: Could not find class {0}

Cause: Error finding class in Coercions.

Action: Make sure the jars are installed correctly. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30182: Could not load class {0}:{1}

Cause: Error finding class in Coercions.

Action: Make sure the jars are installed correctly. Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30183: Method {0} does not return an Icon

Cause: Error attempting to retrieve an Icon.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30184: Could not find method {0} in {1}

Cause: Error trying to find method.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30185: Could not find access {0} in {1}

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30186: Required element 'skin-id' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has a skin-id
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30187: Required element 'style-sheet-name' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has a style-sheet-name
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30188: Required element 'id' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has a unique id.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30189: Required element 'family' not found.

Cause: Error in trinidad-skins.xml file.

Action: Log a bug against the appication. Check the trinidad-skins.xml file and make sure your skin has the skin-family set.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30190: Malformed property entry: {0}={1}

Cause: Error in renderertype-localname.properties.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30191: Could not load renderer type to local name mapping.

Cause: Error in renderertype-localname.properties.

Action: Log a bug against the Apache Trinidad framework.
Level: 1

Type: ERROR

Impact: Logging

ADF_TRINID-30192: Encoding {0} is not supported at the client side. This will skip client side validation.

Cause: Attempting to use an encoding the client doesn't support.

Action: Contact the system administrator to see if the encoding is supposed to be supported.
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30193: The TrinidadFilter has not been installed. Apache Trinidad requires this filter for proper execution.

Cause: Detected that the TrinidadFilter was not installed.

Action: Log a bug against the application. Install the TrinidadFilter; see web.xml
Level: 1

Type: WARNING

Impact: Logging

ADF_TRINID-30194: mergeCapabilities() may only be used with Agents created by this class.

Cause: Attempting to merge capabilities with unsupported agent.

Action: Use a supported agent/browser. Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30195: Invalid Namespace: {0}

Cause: Invalid namespace parsing capabilities document.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30196: Invalid Root Element: {0} {1}

Cause: Invalid root element parsing capabilities document.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30197: Unexpected ''\''.

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30198: Unexpected character. Expecting ''.'' or ''\''

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30199: Unexpected character. Expecting ''*''

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30200: Expecting char

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30201: Unterminated quote.

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30202: Unexpected char.

Cause: Error parsing agent's name and version.

Action: Log a bug against the Apache Trinidad framework. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30203: Invalid saved state object

Cause: Saved state wasn't an instance of PageState.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30204: Don't support transient here

Cause: transient isn't supported.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30205: Per-request disk space limits exceeded.

Cause: per-request disk space limits exceeded.

Action: See the System Administrator.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30206: popView(): No view has been pushed.

Cause: IlegalStateException in DialogService.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30207: popView(): No view has been pushed.

Cause: IlegalStateException in DialogService.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30208: You must call next() at least once

Cause: This is no longer an error in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30209: {0} UnsupportedOperationException

Cause: This is no longer an error in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30210: Only HttpServletRequest supported

Cause: Attempting to get a paramter from ServletExternalContext without a HTTPServletRequest.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30211: {0} can not be null.

Cause: Attempting to get a paramter from ServletExternalContext without a HTTPServletRequest.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30212: Request is null on this context.

Cause: Calling ServletExternalContext's dispatch without a servletRequest.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30213: Response is null on this context.

Cause: Calling ServletExternalContext's dispatch without a servletResponse.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30214: Unsupported conversion from:{0} to:{1}

Cause: IllegalArgumentException while converting values in the BaseConverter.

Action: Check the converter code. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30215: Cannot convert to:{0}"

Cause: This is no longer an error in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30216: Null name

Cause: The name attribute is null.

Action: Log a bug against the application. Set the name to a non-null value.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30217: Null value

Cause: The value attribute is null.

Action: Log a bug against the application. Set the value to a non-null value.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30218: putAll operation not supported for WrappingMap

Cause: UnsupportedOperationException, the WrappingMap which implements Map does not support the putAll operation and it was called.

Action: Log a bug against the Apache Trinidad framework. Fix code to not call putAll.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30219: clear operation not supported for WrappingMap

Cause: UnsupportedOperationException, the WrappingMap which implements Map does not support the clear operation and it was called.

Action: Log a bug against the Apache Trinidad framework. Fix code to not call clear.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30220: Problem loading...

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30221: While grabbing pixels:

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30222: Error while fetching image. grabbed {0} pixel values of the {1} x {2} image.

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30223: Exceeded gif color limit.

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30224: No space left for transparency

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30225: Different lengths - sourceColors and targetColors

Cause: While generating images, there was a problem.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30226: Cannot yet nest:{0} elements

Cause: Region metadata was nested and it shouldn't be.

Action: Log a bug against the application. Do not nest region metadata in your page. Use JDeveloper to check the syntax of your page.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30227: Duplicate renderer type "{0}" for family "{1}"

Cause: Attempting to add a duplicate renderer for a family to the render kit.

Action: Log a bug against the Apache Trinidad framework. Check the renderer registration in the faces-config.xml file.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30228: No returnId is available for returning from the dialog; this usually means that you aren't in a dialog in the first place.

Cause: Returning from a dialog and found no returnId.

Action: Log a bug against the application. To return from a dialog, you need to be in a dialog, or make the pageFlowScope available
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30229: TrainRenderer can only renders instances of {0}, found {1}

Cause: While rendering the train the wrong instance was found.

Action: Log a bug against the application. Check your jspx page.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30230: SelectOne submittedValue's index {0} is out of bounds. It should be between 0 and {1}

Cause: Rendering the selectOne component, the submittedValue was out of bounds from what it should be.

Action: Log a bug against the application. Possibly the model changed when it shouldn't have, so check the model.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30231: SelectOne could not convert submittedValue's index {0} into int {1}

Cause: While rendering the selectOne component, the submittedValue couldn't be converted to an int.

Action: Log a bug against the application. Check the selectOne component's model.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30232: Don't call this for column headers

Cause: While rendering the table, the method getHeaderFormatClass was called for a column header.

Action: Log a bug against the Apache Trinidad framework. Fix code to not call the method for a column header.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30233: contextURI is null

Cause: Attempting to get a configuration context url where the directory is unavailable.

Action: Log a bug against the Apache Trinidad framework. Check the directory.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30234: context URI for {0} ends with a slash

Cause: The configuration context URI ends with a slash and it shouldn't.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30235: contextPath is null {0}

Cause: The configuration context path is null.

Action: Log a bug against the Apache Trinidad framework
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30236: Registered null URI

Cause: Registering a configuration url and found it is null.

Action: Log a bug against the Apache Trinidad framework
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30237: A null path was registered for {0}

Cause: Registering a configuration found a null path being registered.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30238: No base path registered

Cause: Registering a configuration found no base path was registered.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30239: # of keys and values must match

Cause: While processing ServletRequestParameters an error was found.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30240: {0} is not a character

Cause: Trying to coerce a type to a character and found that it wasn't a character.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30241: Could not find class {0}

Cause: Error finding class in Coercions.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30242: {0} cannot be parsed into a {1}

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30243: type is null

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30244: Could not coerce value of type {0} into type {1}

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30245: {0} cannot be coerced into a java.awt.Color

Cause: Attempting to coerce a value.

Action: Log a bug against the application. Check the valuebindings.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30246: Could not find {1}

Cause: Attempting to find file failed.

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30247: DecimalFormatContext is not cloneable!

Cause: IllegalStateException while attempting to clone the DecimalFormatContext.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30248: User-defined subclasses not supported.

Cause: IllegalStateException because you cannot subclass the LocaleContextImpl.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30249: Unknown reading direction: {0}

Cause: Attempting to set the reading direction to an unknown value.

Action: Log a bug against the application. Try a different browser.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30250: Format.parseObject(String) failed

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30251: Cannot format given Object as a Color

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30252: Illegal pattern character ''{0}''

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30253: Illegal pattern character ''{0}''

Cause: Attempting to parse a ColorFormat failed.

Action: Ensure the ColorFormat is correct. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30254: FastMessageFormat only supports numeric arguments

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Use only numeric arguments in FastMessageFormat. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30255: End of pattern not found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the pattern in FastMessageFormat. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30256: FastMessageFormat: empty argument - {} - found

Cause: IllegalArgumentException, in FastMessageFormat while formatting.

Action: Fix the FastMessageFormat. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30257: Content is not multipart form data

Cause: IllegalStateException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30258: Item is not a file

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30259: Item has already been read past.

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30260: Input stream has already been requested.

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30261: Uploaded file of length {0} bytes exceeded maximum allowed length ({1} bytes)

Cause: EOFException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Use smaller files. Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30262: Item has already been read past.

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30263: End Of File

Cause: IOException while attempting to create a MultipartFormHandler for the given InputStream and content

Action: Log a bug against the application.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30264: Undeclared prefix: {0}

Cause: Exception while attempting to parse the namespace from a value.

Action: Log a bug against the application. Check the format of the namespace in the file that is being parsed. JDeveloper will flag errors.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30265: parser is null

Cause: While setting up the ParserManager, a null parser was passed in.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30266: Both rootClass and rootParser are null

Cause: While parsing an xml document the root parser and root class were null.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30267: Circular include of {0} detected!

Cause: SAXParseException while parsing an xml file because a cirular include was detected.

Action: Log a bug against the application. Check the file that is being parsed and remove the circular include.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30268: Null id

Cause: While creating a SkinExtension the skin id was null.

Action: Log a bug against the application. Check that the skin-extensions (defined in trinidad-skins.xml) have an id specified.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30269: Null lContext

Cause: While getting a translated value from the Skin, the locale context was null.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30270: Null iconName

Cause: A null icon was being registered with the Skin.

Action: Log a bug against the Apache Trinidad framework. Check the skin-extensions to make sure the icons are defined correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30271: "Null styleSheetName"

Cause: A null stylesheet was being registered with the Skin.

Action: Log a bug against the Apache Trinidad framework. Check the skin-extensions to make sure the stylesheet name is defined correctly.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30272: No Skin specified.

Cause: Creating a SkinStyleProvider with no skin object.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30273: Null inputStream

Cause: NullPointerException, no inputStream while parsing trinidad-skins.xml file.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30274: Null parserManager

Cause: NullPointerException, no parserManager while parsing trinidad-skins.xml file.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30275: Required XSS file {0} does not exist.

Cause: While registering a skin, the required XSS file does not exist.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30276: Null sourceName

Cause: No source name found while parsing the skin's xss stylesheet.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30277: Null argument

Cause: Error registering a look and feel extension, null baselookandfeel, id or family.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30278: Null propertyName

Cause: While trying to parse an include from an xss file a null property name was found.

Action: Log a bug against the application. Check the xss file being parsed for a null property name.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30279: PropertyNode's name cannot be null or the empty string.name is ''{0}'' and value is ''{1}''

Cause: While trying to parse an include from an xss file a null property name was found.

Action: Log a bug against the application. Check the xss file being parsed for a null property name.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30280: child not instance of PropertyNode

Cause: While trying to parse an include from an xss file an invalid child node was found.

Action: Log a bug against the application. Check the xss file being parsed.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30281: child not an instance of IncludePropertyNode

Cause: While trying to parse an include from an xss file an invalid child node was found.

Action: Log a bug against the application. Check the xss file being parsed.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30282: Not nested in a UIComponentTag

Cause: JSPException while processing an attribute tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30283: No component associated with UIComponentTag

Cause: JSPException while processing an attribute tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30284: Name attribute cannot be EL bound

Cause: JSPException while processing an attribute tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30285: "componentDef cannot be run as a stand-alone. It must be included inside a JSF component tree.

Cause: JSPException while processing an componentDef tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30286: componentDef must be included as a child of an <tr:componentRef>.

Cause: JSPException while processing an componentDef tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30287: tr:componentDef does not support EL on ''var''

Cause: JSPException while processing an componentDef tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30288: "items" must be a simple JSF EL expression

Cause: IllegalArgumentException while processing a forEach/items tags.

Action: Log a bug against the application. Check the jspx page and fix error with 'items'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30289: "var" cannot be an expression

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error with 'var'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30290: "varStatus" cannot be an expression

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error with 'varStatus'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30291: "items" must point to a List or array

Cause: IllegalArgumentException while processing a forEach/items tags.

Action: Log a bug against the application. Check the jspx page and fix error with 'items'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30292: ''begin'' and ''end'' should be specified if ''items'' is not specified

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30293: ''var'' and ''varStatus'' must not have same value

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30294: ''begin'' < 0

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30295: ''step'' < 1

Cause: IllegalArgumentException while processing a forEach tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30296: ResetActionListener must be inside of a UIComponent tag.

Cause: JSPException while processing an resetActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30297: returnActionListener must be inside of a UIComponent tag.

Cause: JSPException while processing an returnActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30298: setActionListener must be inside of a UIComponent tag.

Cause: JSPException while processing an setActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30299: setActionListener's ''to'' attribute must be an EL expression.

Cause: JSPException while processing an setActionListener tag.

Action: Log a bug against the application. Check the jspx page and fix error.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30300: Color code {0} in ''{1}'' does not start with a ''#''

Cause: ParseException processing the chooseColor's colordata.

Action: Log a bug against the application. Start the color code with a '#'.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30301: This method changed to getRenderer(RenderingContext, UINode)

Cause: IllegalStateException, calling an unsupported method.

Action: Log a bug against the Apache Trinidad framework. Call the correct method
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30302: Replaced in 2.0 by getIndexedNodeList()

Cause: IllegalStateException, calling an unsupported method.

Action: Log a bug against the Apache Trinidad framework. Call the correct method
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30303: Instantiation of UIX Components Renderer failed, class {0} not found.

Cause: Attempting to register a uix component rendered failed.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30304: Reusing role index

Cause: IllegalArgumentException creating NodeRoles.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30305: Attempt to register a null renderer for {0}

Cause: Attempting to register a null renderer.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30306: Only ContextBasedConfiguration is supported

Cause: Attempting to set an invalid configuration type on the RenderingContext.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30307: The facet may not be set after the RendererManager has been assigned.

Cause: IllegalStateException trying to set the facet after the RendererManager has been assigned.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30308: It is illegal to set children on a {0}

Cause: UnsupportedOperationException trying to replace a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30309: It is illegal to add children to a {0}

Cause: UnsupportedOperationException trying to add a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30310: It is illegal to remove children from a {0}

Cause: UnsupportedOperationException trying to remove a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30311: It is illegal to set children on an UnmodifiableCompoundNodeList

Cause: UnsupportedOperationException trying to modify a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30312: It is illegal to add children to an UnmodifiableCompoundNodeList

Cause: UnsupportedOperationException trying to add a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30313: It is illegal to remove children from an UnmodifiableCompoundNodeList

Cause: UnsupportedOperationException trying to remove a child.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30314: Adapter class doesn't implement BeanDOAdapter

Cause: IllegalArgumentException registered ia BeanAdapter class.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30315: {0} is not an instance of {1}

Cause: IllegalArgumentException trying to attach an instance of the bean class to the adapter.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30316: leftSideValue is null

Cause: Attempting to create a ComparisonBoundValue caused IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30317: rightSideValue is null

Cause: Attempting to create a ComparisonBoundValue caused IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30318: Unknown comparison

Cause: Attempting to create a ComparisonBoundValue caused IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30319: test BoundValue required

Cause: Attempting to create a IfBoundValue with IllegalArgumentException.

Action: Log a bug against the appication.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30320: Null list argument

Cause: NullPointerException in deprecated code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30321: Null data object argument

Cause: NullPointerException in deprecated code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30322: No factory registered for {0}

Cause: No renderer factory found in LookAndFeelExtension.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30323: Null baseScorer

Cause: NullPointerException in skinning's NameOnly scorer.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30324: Null baseScore

Cause: NullPointerException in skinning's NameOnly scorer.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30325: Facet {0} is not supported on {1}

Cause: IllegalArgumentException returning Skins RendererFactory.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30326: # of keys and values much match

Cause: Error encoding the Javascript event object because the number of keys and values did not match.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30327: child is not null and not an instance of IconNode

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30328: "Null renderers or no renderers passed"

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30329: Null child or child not an instance of RendererNode

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30330: Null family

Cause: While parsing skin nodes a null skin-family was found.

Action: Log a bug against the application. Check all trinidad-skins.xml on classpath and WEB-INF and make sure that the skin-family is set for each skin
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30331: Non Null child and child not an instance of SkinPropertyNode

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30332: RenderingContext has already been created!

Cause: Attempting to create a RenderingContext when it already exists.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30333: {0} not superclass of {1}

Cause: IntrospectionException

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30334: Unexpected reflection exception: {0}

Cause: This error is no longer in the code.

Action: Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30335: Javascript does not support null keys

Cause: IllegalArgumentException while encoding a Map in JavaScript Object Notation.

Action: Do not use null keys. Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

ADF_TRINID-30336: Encoding: {0} is unsupported by JVM

Cause: IllegalCharsetNameException while enabling byte length validation at the client side.

Action: Use a supported JVM. Log a bug against the Apache Trinidad framework.
Level: 2

Type: ERROR

Impact: Logging

4 ADFC-00001 to ADFC-14018

ADFC-00001: An exception is encountered.

Cause: An unknown problem caused an exception.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00002: The ADF Controller cannot run without {0}. Ensure that ''{1}'' is present in the classpath.

Cause: The ADF Controller was unable to locate the required class on the classpath.

Action: Modify the classpath to include the required class.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00003: AdfFacesContext is not found. The ADF Controller cannot run.

Cause: The ADF Controller was unable to locate the required class on the classpath.

Action: Modify the classpath to include the required class.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00004: RequestContext is not found. The ADF Controller cannot run.

Cause: The ADF Controller was unable to locate the required class on the classpath.

Action: Modify the classpath to include the required class.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00005: The ADF Controller cannot execute task flow template ''{0}''.

Cause: An attempt was made to execute a task flow template. Task flow templates cannot be executed.

Action: Correct the associated task flow call activity to refer to a task flow definition.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00006: Existing transaction is required when calling task flow ''{0}''.

Cause: The ADF Controller attempted to enter a task flow that requires an existing transaction, but no transaction was open.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00007: Transaction type is unknown.

Cause: The ADF Controller encountered an unknown transaction type.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00008: The ADF Controller is unable to find DataControlFrame for a task flow.

Cause: The ADF Controller was unable to find the model layer DataControlFrame for a task flow.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00010: A DataControlFrame savepoint handle does not exist.

Cause: Restore of a DataControlFrame savepoint was attempted when a savepoint handle did not exist. Savepoint handle can become null after an ADFc save for later savepoint was restored.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00011: The ADF Controller is unable to create an MDSSession. See exception for details.

Cause: The ADF Controller requires an MDSSession to locate metadata. An attempt to create an MDSSession failed. This could be caused by a number of problems.

Action: See the accompanying exception.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00012: The ADF Controller is unable to parse configuration file adf-config.xml.

Cause: An unspecified error occurred while parsing configuration file adf-config.xml.

Action: See the accompanying exception.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00013: Configuration file adf-config.xml has too many ''{0}'' elements.

Cause: Configuration file adf-config.xml contained more instances of the specified element than are allowed.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00014: Configuration file adf-config.xml contains duplicate phase-listener ''{0}'' registrations.

Cause: One or more phase-listeners had the same listener-id value.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00015: Configuration file adf-config.xml contains duplicate phase-listener ''{0}'' in either ''before-id-set'' or ''after-id-set''.

Cause: A phase-listener was specified twice in the same set.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00016: Configuration file adf-config.xml contains an invalid value: [element, value] = [''{0}'', ''{1}''].

Cause: Configuration file adf-config.xml contained invalid XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00017: Configuration file adf-config.xml does not contain mandatory element ''{0}''.

Cause: Configuration file adf-config.xml contained invalid XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00018: EL expression for UrlParameterConverter is null.

Cause: An attempt was made to convert a URL parameter, but the converter EL expression was null.

Action: Correct the metadata for the converter.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00019: An incorrect object is specified by EL expression ''{0}'' for a URL parameter converter.

Cause: An object was specified by the EL expression that did not implement the oracle.adf.controller.UrlParameterConverter interface.

Action: Specify an object that implements the oracle.adf.controller.UrlParameterConverter interface.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00020: Task flow ''{0}'' requires a new transaction, but a transaction is already open on the frame.

Cause: A new transaction could not be started on the frame because a transaction was already open.

Action: Correct the application's flow or the task flow's metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00021: Task flow ''{0}'' requires a shared DataControlFrame but parent frame is null.

Cause: The task flow is configured to share its DataControl scope with its parent. The parent DataControlFrame is null.

Action: Correct the application's flow or the task flow's metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00022: Unable to create logger ''{0}''.

Cause: An attempt was made to create a logger with a null name.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Logging

ADFC-00023: The ControllerContext is null.

Cause: The ControllerContext was found to be null when expected to be non-null.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Programmatic

ADFC-00024: No ExternalContext could be found.

Cause: No ExternalContext value could be found.

Action: Contact your Oracle Support Services.
Level: 2

Type: INCIDENT_ERROR

Impact: Programmatic

ADFC-00025: The ADF controller has not been successfully initialized.

Cause: The ADF controller has not been successfully initialized, probably due to a configuration error.

Action: Contact the system administrator and inspect the server logs for information on why the initialization failed.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00026: Attempt made to unlock a request lock that is not locked.

Cause: Attempt made to unlock a request lock that is not locked.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00027: Attempt to modify a request lock by another request.

Cause: Attempt to modify a request lock by another request.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00028: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.

Cause: The ADF controller encountered an error while parsing the /WEB-INF/web.xml file.

Action: Review the /WEB-INF/webg.xml file and inspect the server logs for information on why the parsing failed.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-00029: Attempt to acquire the root view port request lock failed due to a timeout.

Cause: Typically caused by another thread holding the request lock for to long, possible due to a deadlock.

Action: Contact the system administrator and inspect the server logs.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00030: The ADF Page Flow functionality requires the full ADF Faces runtime which does not appear to be present, application configuration is invalid.

Cause: The ADF Page Flow feature was not able to verify a fully functional ADF Faces runtime is present.

Action: Update the application's deployment configuration to include the full ADF Faces runtime.
Level: 2

Type: ERROR

Impact: Installation

ADFC-00617: Absolute action URLs are not supported in a portal environment.

Cause: An attempt was made to construct an absolute action URL while running in a portal environment.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00618: View ID ''{0}'' is invalid.

Cause: The value provided was not a valid view ID in the context in which it was being used.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00619: Authorization check failed: User ''{0}'' does not have ''{1}'' permission on ''{2}''.

Cause: An attempt was made to access a task flow without appropriate privilege.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-00620: Parameter value is invalid.

Cause: The value provided for one of the parameters failed validation.

Action: Check the parameter value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00621: The ADF Controller is unable to make a view bookmarkable.

Cause: The ADF Controller was unable to make a view bookmarkable.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00622: Attempt to set view port view ID outside of INVOKE_APPLICATION phase.

Cause: The view ID of a view port may only be set during the INVOKE_APPLICATION phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00623: Task flow ID EL expression ''{0}'' for region ''{1}'' evaluated to null.

Cause: The EL expression for a region's task flow ID evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00624: Task flow ID EL expression ''{0}'' for region ''{1}'' evaluated to invalid object type ''{2}''.

Cause: The EL expression for a region's task flow ID evaluated to an invalid type of object.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00625: A new session URL may only be requested during the RENDER_RESPONSE phase.

Cause: A request for a new session URL was made during an incorrect phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00626: ADF does not support calling ConfigurableNavigationHandler.performNavigation() after the INVOKE_APPLICATION phase has completed.

Cause: A call to ConfigurableNavigationHandler.performNavigation() was made during an incorrect phase of the request lifecycle.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00627: ADF Controller was unable to issue a sendError() call.

Cause: Something triggered a response.sendError() call, and that call failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00628: ADF Controller was unable to update a bookmark URL.

Cause: Something triggered a response.sendError() call, and that call failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00629: ADF Controller is unable to trigger authentication.

Cause: A permission check failed, and the user is not yet authenticated. ADFc cannot redirect to the authentication service.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-00630: ADF Controller received an invalid remote task flow return request.

Cause: A remote task flow call return request was sent to the server when a remote call was not outstanding.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-00631: This viewport does not support executing an activity of type ''{0}''.

Cause: An attempt was made to execute an activity type that is not supported by this viewport.

Action: Contact the application developer.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02000: The ADF Controller is not able to initialize the metadata service.

Cause: The ADF Controller was unable to initialize the metadata service.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Configuration

ADFC-02001: The ADF Controller cannot find ''{0}''.

Cause: An attempt was made to load metadata that cannot be found.

Action: Verify that all required files are available.
Level: 2

Type: ERROR

Impact: Files

ADFC-02002: The ADF Controller cannot parse the task flow metadata.

Cause: The metadata did not represent a valid task flow.

Action: See the associated exceptions. Validate the metadata.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02003: Default activity must be specified in task flow definition ''{0}''.

Cause: The ADF Controller was unable to find task flow default activity in the task flow definition.

Action: Add a default activity to the task flow definition.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02004: Default activity ID ''{0}'' is invalid.

Cause: The ADF Controller was unable to construct the default activity ID.

Action: Correct the default activity ID.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02005: Task flow definition is not found: ''{0}''.

Cause: An attempt was made to read the specified task flow. The task flow cannot be found.

Action: Verify that the required file is available.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02006: A task flow ID is not found in the URL.

Cause: The specified task flow ID was requested and could not be found.

Action: Verify that the task flow reference is correct. Verify that all required files can be found.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02007: A task flow document is not found in the URL.

Cause: An attempt was made to access a task flow using URL parameters. The specified document could not be found.

Action: Correct the value for the document parameter.
Level: 2

Type: ERROR

Impact: Browser

ADFC-02008: The value for ''documentName'' cannot be null or empty.

Cause: An attempt was made to reference a task flow using a null value for ''documentName''.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02009: The value for ''localTaskFlowId'' cannot be null or empty.

Cause: An attempt was made to reference a task flow using a null value for ''localTaskFlowId''.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02010: The value for ''localTaskFlowId'' cannot be ''#''.

Cause: An attempt was made to reference a task flow using an invalid value for ''localTaskFlowId''.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02011: The value for ''localActivityId'' cannot be null or empty.

Cause: An attempt was made to construct an oracle.adf.controller.internal.metadata.ActivityId using an invalid value for 'localActivityId'.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02012: The activity ID string cannot be null or empty.

Cause: An attempt was made construct an oracle.adf.controller.internal.metadata.ActivityId using an invalid value.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02013: The ADF Controller cannot find metadata for activity ''{0}''.

Cause: An attempt was made to access an activity that has no metadata defined.

Action: Validate the task flow document.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02014: No activity implementation is available for activity type ''{0}''.

Cause: An attempt was made to access an activity that is not a known activity type.

Action: Validate the task flow document.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02015: Task flow ID ''{0}'' in document ''{1}'' is invalid.

Cause: The ADF Controller was unable to construct the task flow ID.

Action: Correct the task flow ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02016: A possible cyclic reference to template ''{0}'' is detected when parsing ''{1}''.

Cause: The task flow metadata references a template that is already referenced by this task flow.

Action: Verify that the task flow templates do not reference each other in a cyclic manner.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-02017: The value for ''url'' cannot be null or empty.

Cause: An attempt was made to reference a URL view activity using a null value for ''url''.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Browser

ADFC-02018: Root tag ''{0}'' in ''{1}'' does not match <adfc-config>.

Cause: A document with an invalid root tag was referenced.

Action: Correct the root tag.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02019: No activities are specified in task flow definition ''{0}''.

Cause: The task flow definition did not contain any activities.

Action: Add activities to the task flow definition.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02020: Cannot find default activity ''{0}'' in task flow definition ''{1}''.

Cause: The ADF Controller was unable to find a default activity in the task flow definition.

Action: Add a default activity.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02021: Customization of the documents that appear multiple times on the classpath is not supported. Document name: ''{0}''.

Cause: A document appears multiple times on the classpath.

Action: Remove multiple documents.
Level: 2

Type: ERROR

Impact: Compliance

ADFC-02022: Either ''parent-outcome'' or ''root-outcome'' has to be specified.

Cause: An attempt was made to parse a parent action activity with neither ''parent-outcome'' and nor ''root-outcome'' specified.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Browser

ADFC-04000: The value of PagePhaseListener cannot be null.

Cause: An attempt was made to use a PagePhaseListener with a null value.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04001: The value of a listener ID string cannot be null or empty.

Cause: An attempt was made to identify a PagePhaseListener using a null listener ID.

Action: Use a nonempty string for the listener ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04002: A PagePhaseListener with the listener ID of ''{0}'' already exists.

Cause: Each PagePhaseListener should be registered with a unique listener ID.

Action: Use a listener ID that does not already exist.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04003: The PagePhaseListener of type ''{0}'' with listener ID of ''{1}'' cannot be registered because it is part of the internal API.

Cause: The ADF Controller was unable to register an internal PagePhaseListener using the public API.

Action: Use a PagePhaseListener that is not internal.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04004: The value ''any_public_listener'' is not allowed.

Cause: The value ''any_public_listener'' was part of the afterSet or beforeSet parameter.

Action: Do not use ''any_public_listener'' as the listener ID for beforeSet or afterSet.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04005: The PagePhaseListener with ID ''{0}'' is internal and cannot be removed.

Cause: A failed attempt was made to remove an internal PagePhaseListener. This operation is not supported.

Action: Ensure that a PagePhaseListener is public, not internal, before attempting to remove it.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04006: The value of LifecycleContext cannot be null.

Cause: An attempt was made to create a PagePhaseEvent with a null LifecycleContext.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04007: The FacesPageLifecycleContext does not exist yet.

Cause: An attempt was made to retrieve the FacesPageLifecycleContext before it was created.

Action: Wait until the RestoreView phase of the JavaServer Faces lifecycle to retrieve the FacesPageLifecycleContext.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-04008: The BindingContext on the session is null.

Cause: The BindingContext retrieved from the session was null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06000: The ADF Controller caught exception ''{0}'' while performing control flow routing. See the stack trace for details.

Cause: An unhandled exception occurred while the ADF Controller was executing the application's control flow.

Action: See the associated exception. Verify that the navigation rules are correctly specified. Verify that the correct outcome was generated to trigger routing.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06001: TaskFlowId ''{0}'' is invalid.

Cause: An attempt was made to construct a TaskFlowId using an invalid string.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06002: unhandled exception

Cause: The ADF Controller encountered an exception. Either no exception handler activity was defined or the ADF Controller and task flow were not configured to catch this exception.

Action: See the associated exception. Verify that the exception handler activity is correctly defined. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06003: TaskFlowId for a child view port must be specified.

Cause: An attempt was made to create a child view port using a null value for TaskFlowId.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06004: Invalid transport ''{0}'' used. Task flows require ''{1}''.

Cause: An attempt was made to access a task flow without using the required transport.

Action: Use the appropriate transport. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Security

ADFC-06005: The ADF Controller is unable to invoke URL parameter validator.

Cause: A view activity defines one or more parameter validators. Invoking the parameter validator failed.

Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06006: An exception occurred when evaluating method expression ''{0}'' specified for ''{1}'' defined in ''{2}''.

Cause: A view activity defines a bookmark method. Invoking the specified method failed.

Action: See the associated exception. Verify that the metadata refers to the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06007: The ADF Controller is unable to copy task flow input parameters. Objects must be serializable.

Cause: The task flow call activity specifies one or more input parameters. The ADF Controller was unable to copy the specified values.

Action: See the associated exception. Verify that the metadata refers to the correct class and method. Verify that the specified objects are serializable.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06008: Router case expression ''{0}'' did not evaluate to a boolean value, type of result = ''{1}''.

Cause: A router activity case contained an EL expression that did not evaluate to a boolean value.

Action: Correct the expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06009: The ADF Controller is unable to encode a URL.

Cause: The ADF Controller was unable to encode a URL.

Action: See the associated exception. Correct the metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06010: The ADF Controller is unable to encode remote task flow URL: ''{0}''.

Cause: The ADF Controller was unable to invoke a task flow using a URL.

Action: See the associated exception. Correct the metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06011: The ADF Controller is unable to encode remote process return URL: ''{0}''.

Cause: The task flow metadata specified an invalid return URL.

Action: See the associated exception. Correct the metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06012: Task flow ID returned from a remote call does not match the called task flow's ID, calledId= ''{0}'', returnedId= ''{1}''.

Cause: The task flow ID returned from a remote task flow call did not match the ID of the task flow that was called.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06013: The ADF Controller is unable to encode bookmark parameter ''{0}''.

Cause: The ADF Controller was unable to encode a bookmark parameter.

Action: See the associated exception.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06014: An exception occurred when invoking a task flow finalizer.

Cause: Execution of the task flow finalizer raised an exception.

Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06015: An exception occurred when invoking a task flow initializer.

Cause: Execution of the task flow initializer raised an exception.

Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06016: Task flow reentry is not allowed: ''{0}''.

Cause: A failed attempt was made to reenter a task flow where reentry is prohibited.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06017: Task flow ID is null.

Cause: The task flow ID for a remote taskflow call is null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06018: Task flow ID EL expression ''{0}'' on activity ''{1}'' evaluated to null.

Cause: The EL expression for a remote task flow ID evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-06019: Router case expression ''{0}'' evaluated to a null value.

Cause: A router activity case contained an EL expression that did not evaluate to a boolean value.

Action: Correct the expression to return a non-null boolean value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08000: The ADF Controller is unable to obtain the view state for the savepoint operation.

Cause: An attempt to save or restore the UIViewRoot failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08001: The ADF Controller is unable to commit the savepoint database transaction.

Cause: The ADF Controller was unable to commit a savepoint to the database.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08002: The ADF Controller is unable to log in to the database or obtain a database connection.

Cause: The ADF Controller was unable to log in to the database.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08003: The ADF Controller is unable to delete all savepoint records for user ''{0}'' from the database.

Cause: The ADF Controller was unable to delete all specified savepoints.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08004: The ADF Controller is unable to delete savepoint record ''{0}'' from the database.

Cause: The ADF Controller was made to delete the specified savepoint.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08005: Exception occured when evaluating an expression used for savepoint ID.

Cause: The task flow contains at least one save point restore activity. An attempt to evaluate the value for savepoint ID failed.

Action: See the associated exception. Check the task flow metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08006: The ADF Controller was unable to get the savepoint with ID = ''{0}''.

Cause: The ADF Controller was unable to retrieve the specified savepoint.

Action: Verify that the correct ID was specified. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08007: The savepoint ID is empty.

Cause: An attempt was made to create or get a savepoint with a null ID.

Action: Specify a valid savepoint ID.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08008: The ADF Controller is unable to insert a savepoint record for ID ''{0}''.

Cause: The ADF Controller was unable to insert a savepoint into the database.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08009: The ADF Controller was unable to registering JDBC driver ''{0}''.

Cause: The ADF Controller was unable to establish a JDBC connection.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08010: The ADF Controller was unable to find the JOC-based state manager implementation.

Cause: The ADF Controller was unable to use the Java Object Cache to store savepoints.

Action: Make sure that the JOC is available. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08011: The JNDI connection name is not specified in configuration file adf-config.xml.

Cause: An attempt was made to establish a JDBC connection.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08012: The specified data source JNDI name, ''{0}'', could not be found.

Cause: An attempt was made to establish a database connection.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08013: The ADF Controller is unable to query the database for the current user's savepoint IDs.

Cause: The ADF Controller was unable to query the database for the set of savepoints.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08014: The ADF Controller is unable to execute the save point restore activity.

Cause: The task flow contains a savepoint restore activity. An attempt to execute that activity failed.

Action: See the associated exception. Verify that the metadata is correct. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08015: Cannot restore the savepoint. The savepoint ID is null.

Cause: An attempt was made to restore a null savepoint.

Action: Verify that the task flow metadata is correct. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08016: The ADF Controller is unable to retrieve savepoint ''{0}'' from the database.

Cause: The ADF Controller was unable to retrieve the specified savepoint from the database.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08017: The ADF Controller is unable to save the savepoint.

Cause: The ADF Controller was unable to save the savepoint to the persistence manager.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08018: The ADF Controller is unable to create or execute a SQL statement: ''{0}''.

Cause: The ADF Controller generated SQL that is was unable to create or execute.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08019: The ADF Controller is unable to find the transaction manager.

Cause: The ADF Controller attempted to suspend or resume a transaction.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08020: The ADF Controller is unable to resume a transaction.

Cause: The ADF Controller was unable to resume the transaction.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08021: The ADF Controller is unable to suspend a transaction.

Cause: The ADF Controller was unable to suspend the transaction.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08022: The ADF Controller is unable to update the savepoint record for ID ''{0}''.

Cause: The ADF Controller was unable to update a savepoint.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08023: The ADF Controller is encountering an error while invoking a savepoint restore finalizer.

Cause: The task flow specifies a savepoint restore finalizer. Execution of the finalizer raised an exception.

Action: See the associated exception. Verify that the metadata references the correct class and method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08024: The savepoint ID ''{0}'' is not valid.

Cause: An attempt was made to create or use a savepoint with an invalid ID.

Action: Specify a valid savepoint ID conforming to the UUID format.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08025: The ADF Controller is unable to serialize the savepoint.

Cause: The ADF Controller was unable to serialize the savepoint.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08026: The ADF Controller is unable to deserialize the savepoint.

Cause: The ADF Controller was unable to deserialize the savepoint.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08027: The ADF Controller is unable to close the database connection.

Cause: The ADF Controller was unable to close the database connection.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08028: The ADF Controller is unable to restore the savepoint with ID = ''{0}''.

Cause: The ADF Controller is unable to restore a non existing savepoint.

Action: Verify that the savepoint ID is correct. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-08029: The ADF Controller is unable to find in memory savepoint created before dialog window was shown.

Cause: An attempt to create save point failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10000: cannot find class ''{0}'' for a method parameter

Cause: A method call activity attempted to call the specified class and could not find it.

Action: Correct the classpath. Verify that the metadata refers to the correct class.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10001: cannot instantiate class ''{0}''

Cause: The task flow specifies a managed bean. Instantiation of this managed bean failed.

Action: Verify that the metadata for the managed bean is correct. Verify that the class has a default constructor.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10002: cannot get a value from value binding expression ''{0}''

Cause: Task flow metadata references a managed bean. Bean instantiation failed.

Action: See the associated exception. Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10003: cannot set a null value into array of ''{0}''

Cause: The task flow specifies a managed bean of type 'LIST'. An attempt was made to set a null value.

Action: Change the bean type or modify the code that is attempting to set the bean value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10004: cannot set managed bean property ''{0}''

Cause: An attempt was made to set the property in a managed bean.

Action: See the associated exception. Validate the task flow metadata.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10005: cannot find MethodExpression for ''{0}''

Cause: Task flow metadata references a method binding. Invoking the specified method failed.

Action: See the associated exception. Verify that the metadata is correct. Correct the specified method.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10006: An exception occurred when evaluating an expression ''{0}'' specified for ''{1}''.

Cause: Task flow metadata refers to an EL expression. Evaluation of this expression failed.

Action: See the associated exception. Correct the expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10007: A possible cyclic reference to managed bean ''{0}'' is detected.

Cause: The task flow metadata referenced a managed bean that was already referenced by this task flow.

Action: Verify that the managed bean is not already specified in a referenced template.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10008: Outcome to-string metadata cannot be specified for a method call activity that points to a void Java method. Activity ID: ''{0}''.

Cause: The method call activity outcome metadata specified to-string.

Action: Change the method outcome metadata to use fixed-outcome, or change the Java to return a java.lang.String value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-10009: An exception occurred during invocation of ''{0}'' method.

Cause: Annotated managed bean method cannot be invoked.

Action: Check method implementation.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12000: State ID in request is invalid for the current session.

Cause: The request contained a state instance ID, but it did not exist in the session, nor was this a request for a bookmarked resource. This might be due to a session timeout.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12001: The ADF Controller is attempting to pop last entry from page flow scope stack.

Cause: The ADF Controller attempted to pop the top task flow off the task flow stack.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12002: The ADF Controller is unable to pop the top-level ADF unbounded task flow from the page flow stack.

Cause: The ADF Controller attempted to pop the unbounded task flow off the page flow stack.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12003: The page flow scope stack is empty.

Cause: The ADF Controller attempted to get the current task flow

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12004: Page flow stack ID ''{0}'' is invalid.

Cause: The ADF Controller attempted to calculate the delta between two page flow stacks. The specified stack ID is invalid.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12005: The ADF Controller cannot find a common page flow stack element.

Cause: The ADF Controller attempted to calculate the delta between two page flow stacks. The two stacks have no elements in common.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12006: The scope of the referenced object ''{0}'' is shorter than the referring object ''{1}''.

Cause: An attempt was made to access a managed bean outside its scope.

Action: See the associated exception. Verify that the managed bean is correctly defined and that the reference is valid.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12007: Page flow scope instance ID ''{0}'' is invalid.

Cause: The ADF Controller attempted to get the unbounded task flow for this instance ID.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12008: The ADF Controller request state is missing or invalid.

Cause: A missing or invalid ADF Controller request state was detected.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12009: An application is accessing the page flow scope prematurely.

Cause: An application attempted to access the page flow scope early in the request lifecycle, before the page flow scope was available.

Action: Modify the application to access the page flow scope later in the request lifecycle.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12010: A null window ID is detected in a situation where it should never be null.

Cause: A null window ID is detected in a situation where it should never be null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12011: Window ID ''{0}'' is invalid.

Cause: A window ID was submitted that was not a valid window ID generated during the current HTTP session.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12012: The request has an invalid state ID, and the session timed out.

Cause: The request contained a state instance ID, but the session was created during the current request.

Action: Return to the start page of the application.
Level: 2

Type: ERROR

Impact: Session

ADFC-12013: Controller state has not been initialized for the current request.

Cause: Controller request initialization has not been performed on the current request.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12014: Attempted access to an object that has already been released, object type: ''{0}''.

Cause: Attempted access to an object that has already been released.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12015: Null backingBeanScope ID.

Cause: Null backingBeanScope ID detected.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12016: Attempt to add the ADF Controller state to URL failed.

Cause: Attempt to add the ADF Controller state to URL failed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12017: A non-ADF scope was specified is a place where only an ADF scope is permitted.

Cause: A non-ADF scope was specified is a place where only an ADF scope is permitted.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12018: A null ADF controller state was encountered.

Cause: The ADF controller state was found to be null when it should not be.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Session

ADFC-12019: Window ''{0}'' has already been closed.

Cause: The ADF controller received a request from a window that has already been reported closed.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-12020: The ADF controller received a request to open a dialog when no dialog request was pending.

Cause: The ADF controller received a request to open a dialog when no dialog request was pending..

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14000: View port ID ''{0}'' is invalid.

Cause: A reference was made to an invalid view port ID.

Action: Correct the value.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14001: The ADF Controller cannot create a child view port.

Cause: No root view port was created.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14002: The ADF Controller is unable to set a view port hierarchy that has no root view port.

Cause: The ADF Controller was unable to set the hierarchy of view ports with no root view port.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14003: Region does not have or cannot reach a view activity.

Cause: The region specified a task flow where no view activities could be reached.

Action: Verify that the correct task flow is specified. Verify that the task flow has at least one navigable view.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14004: The ADF Controller cannot execute task flow ''{0}'' that uses page fragments in the root view port.

Cause: The task flow definition declares this task flow as using page fragments. The root viewport can only run task flows that use pages, not page fragments.

Action: Remove the use-page-fragments flag from the task flow definition ''{0}''.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14005: Unused

Cause:

Action:
Level: 1

Type: Error

Impact: Other

ADFC-14006: Client ID ''{0}'' already exists.

Cause: Attempt to create child view port with a client ID that's already in use.

Action: Circular references to regions are not supported. Remove the region from the page.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14007: Display name ''{0}'' must evaluate to java.lang.String.

Cause: An EL expression for the display-name property must evaluate to a java.lang.String.

Action: Fix the EL expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14008: Task flow call activity cannot invoke remote task flow inside a region.

Cause: An attempt was made to invoke a remote task flow from inside a region.

Action: Fix the application.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14009: No RegionData stack was found was found while executing pop operation.

Cause: The RegionStack did not exist or was empty when attempting a pop operations, possibly the results of a pop without a push.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14010: Attempt to suspend a task flow context that's already suspended.

Cause: Attempt to suspend a task flow context that's already suspended.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14011: Attempt to resume a task flow context that has not been suspended.

Cause: Attempt to resume a task flow context that has not been suspended.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14012: Attempt to set the request's submitted view ID on a region's view port.

Cause: Attempt to set the request's submitted view ID on a region's view port.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14013: Task flow binding ''active'' attribute is not a boolean value, binding=''{0}'', expression=''{1}''.

Cause: The ''active'' attribute of a task flow binding did not evaluate to a boolean value.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14014: Task flow binding ''active'' attribute evaluated to null, binding=''{0}''.

Cause: The ''active'' attribute of a task flow binding evaluated to null.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14015: Task flow binding ''active'' attribute was not specified, binding=''{0}''.

Cause: The ''active'' attribute must be specified when activation="conditional" is used.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14016: Unknown value for task flow binding attribute ''activation'', binding=''{0}'', value=''{1}''.

Cause: An unknown value for the task flow binding attribute ''activation'' was encountered.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14017: Invalid expression ''{0}'' for multi task flow binding ''{1}''.

Cause: The expression of the taskFlowList attribute does not evaluate to an object of type java.util.List.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFC-14018: Cannot create a taskflow binding with a null id. Check taskFlowList attribute for multi task flow binding ''{0}''.

Cause: The expression of the taskFlowList attribute evaluate to a list that contain a TaskFlowBindingAttributes with a null id.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

5 ADFDI-00100 to ADFDI-55516

ADFDI-00100: Unable to send a request for BindingContext: a DIRemoteServlet call is already in progress.

Cause: A request to DIRemoteServlet was attempted while another one is already in progress.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00101: unexpected value found in attribute metadata: {0}

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00103: Unable to locate start element: BindingContainer in response stream.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00105: invalid child element <{0}> encountered within <{1}> element

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00106: missing end element: </{0}>

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00107: row limit exceeded

Cause: Too many rows exist in result set.

Action: Refine your query in order to reduce the number of matching rows.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00108: user session required

Cause: A valid user session is required to communicate with server.

Action: Log in to server and retry request.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00109: invalid GetResourceBundle response

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00110: unable to locate element {0} or parse its contents

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00111: unable to create request object

Cause: Unable to establish a connection to the DIRemoteServlet.

Action: Verify that the DIRemoteServlet URL is specified properly and retry request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00112: unable to create XmlTextWriter

Cause: An unexpected error occurred while sending a request to the DIRemoteServlet.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00113: unable to get request stream

Cause: An unexpected error occurred while sending a request to the DIRemoteServlet.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00114: The DIRemoteServlet returned an unrecognized value for element {0}, attribute {1}: {2}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00115: The DIRemoteServlet returned an unexpected element type in the response XML: {0}

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00116: The DIRemoteServlet returned invalid XML: unexpected end of response.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00117: An unexpected error occurred while reading the server response. Consult the logs for more information.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00118: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response.

Cause: An unexpected error occurred while reading the DIRemoteServlet response.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00119: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response: unexpected element type: {0}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00120: The DIRemoteServlet returned an error. A subsequent error occurred reading the error details from the response: unexpected element name: {0}.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00121: The expected XML element {0} was not found. Instead, the element {1} of type {2} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00122: An unexpected XML element name was encountered (expected: {0}, found {1}).

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00123: The expected XML end element {0} was not found. Instead, the element {1} of type {2} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00124: The expected XML end element {0} was not found. Instead, the element {1} was found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00125: The expected XML attribute {0} for element {1} was not found.

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00126: An attempt was made to set the row position for control binding {0} to {1}. Iterator has {2} rows.

Cause: Row index out of bounds.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00127: A version mismatch was detected for {0}. Version {1} was found, version {2} was expected.

Cause: The servlet version did not match the required level for the client.

Action: Upgrade the client and/or server so that compatible versions are in use.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00128: unable to locate the column metadata for column with ID: {0}

Cause: The binding container metadata did not match the data returned from the server.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00129: invalid Encode URL response

Cause: The response received from the server for this request could not be processed. It may be caused by an exception in the server component.

Action: Retry your request. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00130: The size of requested resource bundle ({1}) exceeds the maximum allowable limit: {0} bytes.

Cause: The size of the resource bundle exceeded the supported size.

Action: Reduce the size of the resource bundle.
Level: 1

Type: WARNING

Impact: Files

ADFDI-00131: The connection attempt has been canceled.

Cause: The attempt to connect to the server was canceled.

Action: Retry the current action.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00132: unable to execute Wininet method {0}; error code: {1}

Cause: The Wininet library was unable to provide the requested service.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00133: The user session has changed.

Cause: The user session timed out or was otherwise invalid.

Action: Retry the current action, re-login, or re-establish a valid user session.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00134: An attempt to connect to the web application has failed.

Cause: The web application may not have been running or may not have been configured to allow client connections.

Action: Confirm that the web application is accepting connections from a web browser.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00135: The server-side list is not positioned as expected.

Cause: The server-side list was not positioned as expected.

Action: This is an unexpected error condition. The system administrator can check the server logs for more information.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00136: A server side certificate could not be verified. Open Internet Explorer, visit the site that your workbook is attempting to reach, install the certificate, and retry the current action.

Cause: A server side certificate could not be verified.

Action: Open Internet Explorer, visit the site that your workbook is attempting to reach, install the certificate and retry the current action.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00137: The client and server versions are not compatible. Contact the system administrator and ensure that the client and server versions match.

Cause: The version of the server was not compatible with the version of the client.

Action: Contact the system administrator and ensure that the client and server versions match.
Level: 1

Type: ERROR

Impact: Deployment

ADFDI-00138: The current user is not authorized to access the binding container.

Cause: The current user did not have the necessary permissions to access the binding container.

Action: Log out and log back in as a different user, or contact the system administrator to request the necessary permissions.
Level: 1

Type: ERROR

Impact: Security

ADFDI-00139: The setup action has failed unexpectedly. Review the server log files for more information.

Cause: The specified setup action failed to execute as expected.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00140: An error was encountered while connecting to or communicating with the web application. Details: {0} ({1}: {2}).

Cause: The client encountered an error when attempting to communicate with the web application.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00141: An attempt to establish a user session with the web application has failed.

Cause: Something has prevented the client from establishing a valid user session with the web application.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00142: The transaction size limit was exceeded.

Cause: Too much data was sent to the server without committing any changes to the database.

Action: Reduce the amount of pending changes and retry the current action.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00143: Failed to locate metadata.

Cause: The server cannot find the metadata requested by the client.

Action: Contact the system admin to make sure the workbook metadata is correctly deployed
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-00144: Failed to locate metadata.

Cause: The key used to reference the client metadata is invalid

Action: Contact the workbook developer to correct the metadata key
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-00145: A server-side error has occurred when loading metadata.

Cause: A server-side error has occurred and prevented the client from loading metadata.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-00146: Invalid ClientMetadata response

Cause: The XML response returned from the DIRemoteServlet is invalid.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00147: Create savepoint failed

Cause: An unexpected error occurred while creating a savepoint.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00148: Restore savepoint failed

Cause: An unexpected error occurred while restoring a savepoint.

Action: Review the server logs for more details on the cause of the failure.
Level: 1

Type: ERROR

Impact: Session

ADFDI-00500: unable to execute Wininet method {0}; error code: {1}

Cause: The Wininet library was unable to provide the requested service.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00501: An unexpected status: {0} ({1}) was returned from the server while requesting the URL: {2}

Cause: The client was unable to complete its request to the server for the given URL. The server returned an unexpected status code.

Action: Retry the current action, confirm connectivity, and/or consult the client logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00502: The client was unable to establish an unauthenticated session with the web application.

Cause: An unexpected problem prevented the client from establishing a valid, unauthenticated session with the web application.

Action: Retry the current action, confirm the authentication configuration and connectivity, and/or consult the client logs and exception details for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-00505: Unexpected exception

Cause: There was an unexpected error during the current operation.

Action: Review configuration and installation. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-01001: A validation error occurred for metadata property {0}. Detail: {1}

Cause: An invalid property value was specified in the configuration metadata.

Action: Correct the specified property.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-01002: A validation warning occurred for metadata property {0}. Detail: {1}

Cause: An invalid property value was specified in the configuration metadata.

Action: Correct the specified property.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05000: Unexpected components exist at origin, {0}.

Cause: More than one component was found at the specified origin.

Action: Delete the unwanted components.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05002: unable to locate page definition element in {0}

Cause: The root element was missing from the page definition file.

Action: Ensure that the page definition file is well formed.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05006: A component already exists at origin {0}.

Cause: An attempt was made to insert or move a component to a cell that is already in use as the origin of another component.

Action: Choose a different destination cell for the insertion or move operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05011: unable to move the component to new position; a component already exists at that position: {0}

Cause: An attempt was made to move a component to a cell that is already in use as the origin of another component.

Action: Choose a different destination cell for the move operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05012: Unable to locate or open the page definition: {0}. Control bindings are not available for this worksheet. File: {1}.

Cause: An attempt was made to load the file specified. Either some portion of the file path was invalid, the file did not exist, or the user had insufficient permissions to open the file.

Action: Ensure that the relevant properties are configured correctly.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05013: There is no page definition selected. Control bindings are not available for this worksheet.

Cause: User canceled the operation of selecting a page definition.

Action: Select a valid page definition to associate with the current worksheet.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05015: An error occurred while updating the client registry

Cause: The attempt to update the client registry was unsuccessful.

Action: Check client log file for more details.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05016: The workbook, {0}, is missing one or more required settings: ApplicationHomeFolder, WebPagesFolder.

Cause: The specified workbook was missing one or more settings required for publishing.

Action: Provide valid values for all settings required for publishing.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05017: The value '{0}' is not valid for the property {1}.

Cause: The property value entered was not valid.

Action: Enter a valid property value.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05018: Unable to locate or open the page definition: {0}. Control bindings are not available for this worksheet.

Cause: The specified page definition could not be located or opened.

Action: Check the spelling of the page defintion usage id and refresh the bindings list.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05019: The component cannot be placed at the requested location since it would overlap with one or more other components.

Cause: An attempt was made to place a component in a position that would overlap with other components.

Action: Choose a different location that will not overlap.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05020: Unexpected components exist at cell, {0}.

Cause: More than one component was found at the specified cell.

Action: Delete the unwanted components.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05021: The destination workbook name, {0}, is already being used by an open workbook. The published workbook name cannot be the same as an open workbook even if the directories are different.

Cause: The published workbook name was the same as a workbook that was currently open.

Action: Choose a different name or close the open workbook.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05022: An unexpected exception has occurred. The workbook {0} cannot be published.

Cause: An unexpected exception occurred while attempting to publish the workbook.

Action: Verify settings, installation, and configuration. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-05023: There is a mismatch between the destination file extension, {0}, and source file extension, {1}. The workbook cannot be converted during publication.

Cause: The publish destination and source workbooks did not have the same file extension.

Action: Publish the workbook to a file with the same extension. Or, convert the workbook to the desired type before publishing.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05024: This workbook cannot be published because the format is not supported. Use a supported format like 'Excel Workbook (*.xlsx)'.

Cause: The source workbook was not a supported file type.

Action: Convert the workbook to a supported type.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05025: The destination file path exceeds the Excel limit of 219 characters. File path: {0}

Cause: The file path length exceeded the length limitation imposed by Microsoft Excel.

Action: Reduce the length of the path and retry the publish operation.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05026: Cannot publish a customizable workbook to the destination: {0}

Cause: The customizable workbook was published to a invalid destination.

Action: Publish the customizable workbook to a location under the public_html directory of the project associated with current workbook.
Level: 1

Type: ERROR

Impact: Files

ADFDI-05500: error restoring server data context

Cause: A failed attempt was made to re-establish the server state for a new user session.

Action: Check the configuration of the workbook to ensure that the attributes and actions used to reestablish the server state are defined correctly. Check the server to determine whether data has been deleted.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05501: value does not match for attribute {0}

Cause: The value in the cache was not equal to the attribute value.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05502: unable to locate control binding {0} in binding container {1}

Cause: A failed attempt was made to locate the binding information of a UI component.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05503: An incorrect binding type, {0}, exists for the control binding {1} in the binding container {2}.

Cause: The binding type of the component differed from the binding type defined in the binding container.

Action: Check the configuration of the workbook and retry the operation. Ensure that the control binding type is defined correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05504: unable to find attribute: {0}

Cause: A failed attempt was made to find an attribute in the data context cache.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05505: unable to find action: {0}

Cause: A failed attempt was made to find a restore data context action in the data context cache.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05506: unable to find list control binding: {0}

Cause: A failed attempt was made to locate the list control binding.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05507: invalid list control binding: {0}

Cause: The binding type of the list control was not valid.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05509: unable to find component: {0}

Cause: A failed attempt was made to find the binding of the component.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05510: unable to insert column; column out-of-bounds

Cause: A failed attempt was made to insert a dynamic column into the Table because the column was not within the named range.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05511: unable to remove column; column out-of-bounds

Cause: A failed attempt was made to delete a dynamic column into the Table because the column was not within the named range.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05513: cannot find record

Cause: A failed attempt was made to locate the record flagged for deletion.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05517: unable to find control {0}

Cause: A failed attempt was made to locate the control in the binding container.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05518: unable to set expression value for read-only expression

Cause: A failed attempt was made to set the value for a read-only expression.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05519: unable to find component method, {0}, to invoke.

Cause: A failed attempt was made to invoke the specified component method.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05524: unable to position on current table row

Cause: A failed attempt was made to update the row position in a table for the purpose of invoking an action set on the row.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05529: unable to load binding container metadata

Cause: A failed attempt was made to load the metadata that defines the binding container.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05530: unable to initialize worksheet: {0}

Cause: A failed attempt was made to initialize a worksheet.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05531: one or more rows could not be uploaded

Cause: A failed attempt was made to upload data to the web application.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05535: one or more flagged rows could not be deleted

Cause: A failed attempt was made to delete flagged rows.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05537: The integrity of the workbook integration could not be determined. This workbook cannot be used safely. The integration will now terminate.

Cause: The server was unable to read the client registry.

Action: Verify/correct the client registry in the web application.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05538: The workbook integration has been altered after publishing. It can no longer be used safely. The integration will now terminate.

Cause: The tampering check has determined that the workbook has been altered.

Action: Obtain a fresh, unaltered copy of the published workbbook.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05553: An invalid character was found in the server XML response. Verify the data from the data source and avoid any invalid character or binary data such as image be sent in the response.

Cause: An attempt was made to read an invalid character in the XML data sent by the server.

Action: Verify the data from the data source and remove the invalid character from the data.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05554: An incorrect version of the UI metadata schema is used in the workbook. Convert the UI metadata to the current version.

Cause: The workbook contains UI metadata from an obsolete schema version.

Action: Convert the UI metadata to the current version.
Level: 1

Type: WARNING

Impact: Session

ADFDI-05555: Required property {0} missing for component {1}.

Cause: Required component property not defined.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05557: inserted row data must first be refreshed from server

Cause: The row was successfully inserted to the database, but the row data has not been updated in the worksheet.

Action: First perform a Download or DownloadFlaggedRows operation, then retry the DeleteFlaggedRows operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05558: CacheDataContext must specify an action and at least one attribute.

Cause: The metadata for this worksheet contains one or more invalid CacheDataContext definitions.

Action: Review and resolve CacheDataContext configuration issues and retry.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05559: Row cache data is invalid.

Cause: The row data cached for an ADF Table component is not valid.

Action: Re-download ADF Table data.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05561: Failed to read multi-sync response as expected.

Cause: The number of multi-sync responses did not match the number of multi-sync requests.

Action: Check your configuration and try the operation again.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05562: Dependent list component has been misconfigured.

Cause: The developer has incorrectly configured a list component that depends on another list component.

Action: Enable verbose logging on the client and review log for additional details on the specific configuration issue.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05563: Restore Server Data Context Cache is corrupted

Cause: The hidden cache of data was not in the expected format

Action: Obtain a new version of the workbook or Clear All Data
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05564: The list binding "{0}" has {1} values. Only the first {2} items are stored in the cache.

Cause: The number of items in the list exceeded the allowable limit.

Action: Reduce the number of items in the list. Or, configure the workbook to use a web page dialog for selecting an item from a large list of values.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05565: unable to retrieve values for the list binding "{0}"

Cause: A failed attempt was made to retrieve list values from the server.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05566: unable to retrieve values for the list binding "{0}", or for one or more of its dependent lists

Cause: A failed attempt was made to retrieve list values from the server.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05567: Unable to restore server state. This condition is an unrecoverable error. You will now be logged out of your current session.

Cause: The attempt to restore server state failed.

Action: Log in to the application and retry the operation. Examine the server logs for additional information.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05568: Failed to initialize cache for List binding: {0} in component/column: {1}, owned by type: {2} (in table: {3}).

Cause: A failed attempt was made to retrieve and cache list values from the server.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05569: Unable to report table status: status column is not visible.

Cause: The table was configured so that the Status column is not visible.

Action: Configure the table so that the Status column is visible.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05570: The Automation API encountered an unexpected condition. Details: {0}

Cause: The Automation API encountered an unexpected condition.

Action: Check the configuration of the workbook and/or the automation scripts.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05571: Failed to find resource. Alias: {0} Key: {1}

Cause: The specified alias-key combination could not be located.

Action: Check the configuration of the workbook and/or resource files.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05572: Failed to find resource bundle. Alias: {0}

Cause: The specified resource bundle could not be located.

Action: Check the configuration of the workbook and/or resource files.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-05573: Unable to perform the requested action because the worksheet protection could not be changed.

Cause: A failed attempt was made to temporarily remove protection from the worksheet.

Action: Check the protection configuration of the worksheet and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05574: You have modified cells in the key column. This operation can lead to data corruption. Your change will now be reverted.

Cause: An attempt was made to modify cells in the key column of an ADF Table.

Action: Do not modify cells in the key column.
Level: 1

Type: WARNING

Impact: Data

ADFDI-05575: Unable to revert the changes to cells in the key column. The affected table(s) should be considered corrupt. You should revert to a previous version.

Cause: A failed attempt was made to revert changes to the key column.

Action: Obtain a fresh copy of the integrated workbook and re-attempt the operation without modifying cells in the key column.
Level: 1

Type: ERROR

Impact: Other

ADFDI-05576: The action, {0}, cannot be invoked in this context.

Cause: An attempt was made to invoke a row-level action in a non-row-level action set.

Action: Remove this action from this action set.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05577: Failed to retrieve table row data from the server.

Cause: A failed attempt was made to retrieve table row data from the server.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05578: The reserved table named range, '{0}', cannot be not found or is invalid.

Cause: A failed attempt was made to access the reserved named range for the table component.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05579: An unexpected exception occurred while performing an operation on the table identified by: {0}. Close the workbook without saving it and retry the operation.

Cause: A failed attempt was made to execute a table operation.

Action: Close the workbook without saving it and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05580: unable to bind expression part: {0}

Cause: A failed attempt was made to bind the expression part.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05581: Unable to write component data into worksheet: {0}

Cause: A failed attempt was made to write component data to the worksheet.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-05582: Unable to download flagged rows because the table structure has changed.

Cause: The DownloadFlaggedRows action was invoked on a table and the column structure is different from when rows were last downloaded.

Action: Check the configuration of the worksheet.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-05584: Unable to convert: '{0}' to the target time zone. Close the workbook without saving it and retry the operation.

Cause: An unexpected failure has occurred while converting date time values from one time zone to another.

Action: Close the workbook without saving it and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05585: The {0} element in the dialog page {1} should be a <span> element; the type <{2}> is not supported.

Cause: The html tag used for the reserved element in the dialog page was not supported.

Action: Contact the developer of this dialog page to use <span> tag for the reserved element
Level: 1

Type: Warning

Impact: Configuration

ADFDI-05586: Fail to hook event handler to the {0} element due to {1}. Closing the dialog with client side scripts is disabled.

Cause: Unable to hook an event handler to the reserved html element in the dialog page.

Action: Close the dialog manually if it is not closed automatically. The developer of this dialog page should avoid using client side scripts to change the value of the reserved element.
Level: 1

Type: Warning

Impact: Other

ADFDI-05587: The client and server versions do not match. Using this version of the client may result in unexpected behavior or errors.

Cause: The client and server versions did not match.

Action: Install a client that matches the server version.
Level: 1

Type: Warning

Impact: Upgrade

ADFDI-05588: The number of resource bundles ({1}) exceeds the supported limit of {0}.

Cause: The number of resource bundles exceeded the supported limit.

Action: Reduce the number of resource bundles in this workbook.
Level: 1

Type: WARNING

Impact: Files

ADFDI-05589: You are not authorized to use this worksheet for interacting with the web application.

Cause: The current user did not have the necessary permissions to access the page definition file associated with this worksheet.

Action: Log out and log back in as a different user, or contact the system administrator to request the necessary permissions.
Level: 1

Type: ERROR

Impact: Security

ADFDI-05591: The user session has changed. Re-try the operation.

Cause: The user session changed during the execution of an action set.

Action: The end-user should re-try the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-05592: Too much changed data was uploaded.

Cause: The amount of changed data that was uploaded exceeds the web application limit.

Action: Retry the operation with less changed data.
Level: 1

Type: ERROR

Impact: Data

ADFDI-05593: The operation ({0}) was canceled.

Cause: The end-user canceled the operation.

Action: None required. The end-user may continue to interact with the worksheet and if desired, retry the operation.
Level: 1

Type: WARNING

Impact: Other

ADFDI-05594: Failed to load the client metadata

Cause: A failure occured when loading the client metadata

Action: Check the client and server logs for details about the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-05595: DownloadForInsert action ignored (InsertRowEnabled is false) for table: {0}.

Cause: DownloadForInsert action was included in an action-set, but was not applicable since InsertRowEnabled was false.

Action: The developer should remove the action, or alter the table so that InsertRowEnabled is true.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-05597: Dynamic columns are always visible. Ignoring Visible expression: {0}

Cause: The workbook configuration specified a Visible expression for a dynamic column

Action: The developer should adjust the configuration: remove the Visible expression or set Dynamic to True.
Level: 1

Type: WARNING

Impact: Metadata

ADFDI-05598: TableRowErrorsCache '{0}' is out of space. All previous entries will be purged.

Cause: The worksheet storing error message details was out of space.

Action: No action required.
Level: 1

Type: WARNING

Impact: Other

ADFDI-05599: This source scheme is not supported: {0}.

Cause: The specified URL is of an unsupported scheme.

Action: The developer should use a URL with a supported scheme.
Level: 1

Type: ERROR

Impact: Other

ADFDI-05600: This URL is invalid: {0}.

Cause: The specified URL is incorrectly formatted.

Action: The developer should verify and correct the URL.
Level: 1

Type: ERROR

Impact: Other

ADFDI-06000: Workbook {0} is not enabled for {1}.

Cause: The specified workbook was not the expected type.

Action: Specify only workbooks enabled for use with this product.
Level: 1

Type: ERROR

Impact: Files

ADFDI-06001: An unexpected exception has occurred. The workbook {0} cannot be published.

Cause: An unexpected exception occurred while attempting to publish the workbook.

Action: Verify settings, installation, and configuration. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-06002: Error parsing the command line arguments.

Cause: The command line arguments were not specified in the correct format.

Action: Check the usage of the tool and correct the input format.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-06003: Unexpected arguments specified: {0}

Cause: The number of command line arguments exceeded the expected number.

Action: Specify only the expected arguments.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07001: unable to find Excel file: {0}

Cause: A failed attempt was made to find a workbook file.

Action: Ensure that the necessary file permissions have been applied, and that the file exists.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07006: unable to update web.xml for {0}

Cause: An attempt to update the web application deployment descriptor failed.

Action: Apply the necessary changes using the deployment descriptor Properties dialog.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07007: unable to update adf-config.xml for {0}

Cause: An attempt to update the application configuration failed.

Action: Apply the necessary changes by opening adf-config.xml in the source editor.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07008: Unable to find {0} installer {1}

Cause: The installer application was not found in the expected location.

Action: Ensure that the necessary file permissions have been applied, and that the file exists.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07009: unable to start {0} installer

Cause: A failed attempt was made to execute the installer.

Action: Ensure that the necessary file permissions have been applied, that the file exists, and is not in use.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07010: unable to copy template workbook

Cause: A failed attempt was made to copy the template workbook.

Action: Ensure that the necessary file permissions have been applied, that the file exists, and is not in use.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07011: Page Definition name already in use: {0}

Cause: A duplicate name was proposed for a new page definition.

Action: Ensure that the proposed page definition name is not already in use in the application.
Level: 1

Type: WARNING

Impact: Files

ADFDI-07012: Page Definition name must be non-empty

Cause: An empty name was proposed for a new page definition.

Action: Ensure that the proposed page definition name is not empty.
Level: 1

Type: WARNING

Impact: Files

ADFDI-07013: unable to open Excel file

Cause: A failed attempt was made to open a workbook file.

Action: Ensure that the necessary file permissions have been applied, that the file exists, is not in use, and that it is a valid workbook file.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07400: unable to open Excel file

Cause: A failed attempt was made to open a workbook file.

Action: Ensure that the necessary file permissions have been applied, that the file exists, is not in use, and that it is a valid workbook file.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07401: unable to find Excel file: {0}

Cause: A failed attempt was made to find a workbook file.

Action: Ensure that the necessary file permissions have been applied, and that the file exists.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07507: given buffer size is incorrect; given: {0}

Cause: An incorrect value was supplied for the Workbook Parameters buffer size.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07508: did not find expected start tag; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07509: did not find expected end tag; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that matching versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07510: mode length is incorrect; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07511: AppRoot length is incorrect; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07512: Workbook initialization parameters length is incorrect; found: {0}

Cause: The workbook's internal format may be corrupted.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07513: Destination length {0} is less than found length {1}.

Cause: Internal buffer size mismatch detected.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07516: A worksheet version mismatch was detected in worksheet {0}. Version {1} was found, version {2} was expected.

Cause: The workbook's internal format may be corrupted, or incompatible versions of the framework are in use.

Action: Ensure that compatible versions of the framework are in use; upgrade the workbook and framework.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07517: There are no more rows available in the metadata worksheet {0}.

Cause: The maximum capacity for storing metadata has been reached, or the workbook's internal format may be corrupted.

Action: Remove some components from the workbook in order to free up space.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07518: The workbook has no metadata.

Cause: The workbook may be corrupted or the metadata has been erased manually.

Action: Publish the workbook and try again or contact administrator.
Level: 1

Type: ERROR

Impact: Data

ADFDI-07520: Unable to evaluate the expression '{0}' in '{1}'. Detail: {2}

Cause: A failed attempt was made to evaluate an invalid expression.

Action: Verify and correct the expression.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07521: Unable to evaluate the Excel formula '{0}' in '{1}'. Detail: {2}

Cause: A failed attempt was made to evaluate an invalid Excel formula.

Action: Verify and correct the Excel formula.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07522: Unable to execute the command '{0}' while a cell is in edit mode. Accept or cancel the changes to the current cell and then retry the command.

Cause: An attempt was made to invoke a menu or toolbar command while a cell is open in editing mode.

Action: Accept or cancel the changes to the current cell and then retry the command.
Level: 1

Type: WARNING

Impact: Programmatic

ADFDI-07527: An unexpected exception has occurred. The Workbook Designer cannot initialize. The design-time session will now abort.

Cause: A failed attempt was made to initialize the workbook for Design Time mode.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07528: An unexpected exception has occurred. The UI Controller cannot initialize. The runtime session will now abort.

Cause: A failed attempt was made to initialize the workbook for Run Time mode.

Action: Check the configuration of the workbook and retry the operation. Ensure that the web application is running and accepting requests.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07529: An unexpected exception has occurred. The workbook cannot initialize and will now abort.

Cause: A failed attempt was made to initialize the workbook for an unknown mode.

Action: Check the configuration of the workbook and retry the operation.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07530: An unexpected exception has occurred. The workbook cannot switch to test mode.

Cause: A failed attempt was made to switch from Design Time mode to Test mode.

Action: Check the configuration of the workbook and retry the operation. Ensure that the web application is running and accepting requests.
Level: 1

Type: ERROR

Impact: Session

ADFDI-07532: The workbook {0} cannot be used with this edition of {1}.

Cause: An attempt was made to open a design-time or test mode workbook using the runtime edition.

Action: Use only published workbooks with the runtime edition. Install the designer edition for other workbook types.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07533: Unable to load add-in {0} because multiple editions are installed.

Cause: Multiple editions of the add-in were installed.

Action: Remove one of the editions.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07537: Ignored exception thrown by {0} event subscriber

Cause: An event subscriber threw an exception.

Action: Review and correct the event subscriber implementation.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-07538: The Automation API encountered an unexpected condition. Details: {0}

Cause: The Automation API encountered an unexpected condition.

Action: Check the configuration of the workbook and/or the automation scripts.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-07539: The workbook '{0}' was created or altered by version '{1}' of {2} and is not compatible with the current version ({3}).

Cause: The workbook was created or altered by a newer version of the product and is not compatible with the current version.

Action: Use a newer version of the Oracle ADF Desktop Integration client.
Level: 1

Type: ERROR

Impact: Upgrade

ADFDI-07540: The workbook '{0}' was created or altered by version '{1}' of {2} and is not compatible with the current version ({3}). Do you wish to use it anyway?

Cause: The workbook was created or altered by a newer version of the product and is not compatible with the current version.

Action: Use a newer version of the Oracle ADF Desktop Integration client, or continue with the current client. You may encounter unexpected errors.
Level: 1

Type: WARNING

Impact: Upgrade

ADFDI-07541: Unable to write metadata to file: {0}

Cause: There was an unexpected exception while attempting to write the XML to the specified file.

Action: Review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07542: Unable to import workbook configuration metadata.

Cause: There was an unexpected exception while attempting to load the workbook configuration metadata into the current workbook.

Action: Review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07543: Unable to import workbook configuration metadata due to schema validation failures.

Cause: The attempt to import workbook configuration metadata failed due to XML schema validation failures.

Action: Review the client logs for detailed information on the schema validation failures and correct the XML.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07544: Unexpected exception during write to metadata cache. The workbook may be corrupted.

Cause: The attempt to write workbook configuration metadata failed while writing to the cache.

Action: Discard the workbook and review the inner exception details to determine root cause.
Level: 1

Type: ERROR

Impact: Files

ADFDI-07545: Unable to display help file.

Cause: The attempt to display the help file failed unexpectedly.

Action: Check the local browser and network settings. Then, retry the operation.
Level: 1

Type: ERROR

Impact: Other

ADFDI-07546: Duplicate component id detected during import: {0}. Replacing with {1}.

Cause: A duplicate component id was found.

Action: Review and update any dependencies on the old component id.
Level: 1

Type: WARNING

Impact: Other

ADFDI-08200: A valid {0} property must be chosen before editing this property.

Cause: An attempt was made to edit the Web Pages Folder or Page Definition Folders properties before specifying a valid Web Application Home folder.

Action: Specify a valid Web Application Home folder property and retry the operation.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-08201: A valid 'Web Pages' folder must be chosen. Do you want to do that now?

Cause: An attempt was made to choose a web page for an ActionSet's Dialog.Page property before a valid Web Pages Folder property was specified.

Action: Specify a valid Web Pages Folder property and retry the operation.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-08202: A valid path that is relative to the 'ApplicationHomeFolder' property must be chosen.

Cause: An attempt was made to choose a folder that is not a valid subfolder of the parent folder property.

Action: If necessary, change the 'ApplicationHomeFolder' property to a different value, and then choose a valid subfolder for this property.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-08203: A valid, absolute path name must be entered for this property.

Cause: An attempt was made to choose a folder for the Application Home Folder property that is not a valid, absolute folder.

Action: Navigate to the folder in which your web application resides.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-50001: Resource bundle not found. bundle: {0}

Cause: Unable to load the desired resource bundle class.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-50002: Resource key not found. bundle

Cause: Unable to find the desired key in the bundle.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55000: An unexpected exception occurred on the server. Consult the server logs for more detail.

Cause: An unexpected condition arose while handling the desktop integration request.

Action: Review the server logs for additional detail on the underlying cause.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55001: XML element {0} missing required attribute {1}

Cause: Invalid request XML was received.

Action: Review the server logs to ensure that only supported clients are accessing the ADFdi Remote Servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55002: The object, {0}, is not available.

Cause: An expected object was not found or was unavailable.

Action: Ensure that both the client and server metadata are configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55003: The object, {0}, is not available. Name: {1}

Cause: An expected object was not found or was unavailable.

Action: Ensure that both the client and server metadata has been configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55004: invalid GetResourceBundle request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55005: invalid SyncModel request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55006: unexpected value specified for XML element {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55007: invalid request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55008: invalid request method: {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55009: user session unavailable

Cause: The user was not authenticated.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55010: expected XML element {0}; current element is {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55011: unexpected end-of-file in XML input stream

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55012: invalid XML element: {0}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55013: expected XML reader state {0}; current state is {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55014: invalid child XML element {1} within XML element {0}

Cause: The XML request sent by the client was invalid.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55017: The current row count exceeds the configured limit.

Cause: The maximum number of rows requested by the client was exceeded.

Action: Submit a new request that conforms to the limit.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55018: exception occurred while reading an XML request

Cause: A malformed request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55019: exception occurred while writing the XML response

Cause: Details about the underlying cause of the error are contained in the server logs.

Action: Review the server logs for details about additional steps to take.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55021: A version mismatch was detected for {0}. Version {1} was found, version {2} was expected.

Cause: The client version does not match the required level for the DIRemoteServlet.

Action: Upgrade the client and/or server so that compatible versions are in use.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55022: invalid SessionStatus request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55023: invalid MultiSyncModel request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55025: The control binding definition for item {0} is incorrect or incompatible. {1}

Cause: The control binding definition has been misconfigured, or an incompatible control binding has been encountered.

Action: Check the control binding definition and ensure that only supported control bindings are used.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55026: invalid TamperCheck request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55027: invalid EncodeURL request XML

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55028: unexpected value specified for XML element {0}: {1}

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55030: Cannot find the client registry file: {0}

Cause: System could not find the client registry file in the web-inf location.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55031: An error occurred while trying to read client registry file

Cause: While trying to read the client registry file, an I/O error occurred.

Action: Check logs for details of I/O error and address root case to enable file access.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55032: Unable to set attribute {0} (row object unavailable: {1})

Cause: Client attempted to set an attribute value when no server row is available.

Action: Refresh the client data and retry the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55033: {0}: cannot convert the input value ({1}) to the expected data type ({2}).

Cause: The input values were not consistent with expected data type.

Action: Correct input values according to data type.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55034: Tamper check is disabled.

Cause: The servlet was configured to disable the tamper check feature.

Action: Adjust servlet initialization parameters as desired.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55035: Tamper check did not succeed. Result: {0}

Cause: Tamper check was unable to match the hashcode of the client to the expected value.

Action: Adjust the configuration of tamper check or obtain a new copy of the workbook.
Level: 1

Type: WARNING

Impact: Data

ADFDI-55036: Received a request with unexpected content type: {0}

Cause: A request with an unexpected content type was received.

Action: Use only supported content types.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55037: Tamper check is configured to allow missing entries.

Cause: The tamper check feature was configured to allow missing entries.

Action: Adjust servlet initialization parameters as desired.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55038: The region binding includes an unsupported control type: {0}

Cause: The page definition was configured to use an unsupported control type.

Action: Remove the unsupported type.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55039: Unexpected servlet failure

Cause: The servlet has failed due to an unexpected condition.

Action: Review the server logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55040: Unable to read requested resource bundle: {0}

Cause: An attempt was made to load a resource bundle that was not available.

Action: Review the configuration to ensure that the resource bundle is available.
Level: 1

Type: ERROR

Impact: Configuration

ADFDI-55041: Aborting the commit action for a transaction.

Cause: The commit action was aborted for the transaction due to error in the binding container.

Action: Clear the error conditions and retry the operation.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55042: Unable to set position for {0} with value {1}

Cause: A failed attempt was made to position a control binding by attribute value.

Action: Refresh the client data and retry the operation or review the server logs for more information.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55043: Unable to locate parameter {0} for binding container {1}

Cause: A failed attempt was made to set a parameter.

Action: Review the configuration to ensure that the parameter is available.
Level: 1

Type: WARNING

Impact: Configuration

ADFDI-55044: user session has changed

Cause: The client user session timed out or was otherwise invalid.

Action: Establish a valid user session.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55045: unable to set position to row {0}

Cause: A failed attempt was made to position a control binding by row index value.

Action: Refresh the client data and retry the operation or review the server logs for more information.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55046: A value is required for {0}.

Cause: An attempt was made to set an empty value for a mandatory attribute.

Action: Provide a non-empty value for this property.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55047: retry failed for batch request #{0}

Cause: A failed attempt was made to retry a successful batch request after restoring to datacontrol savepoint.

Action: Review the server logs for more details about the cause of the failure.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55048: The current user is not authorized to access the binding container: {0}

Cause: The current user did not have the necessary permissions to access the binding container.

Action: Log out and log back in as a different user, or contact the system administrator to request the necessary permissions.
Level: 1

Type: ERROR

Impact: Security

ADFDI-55049: unable to run the setup action: {0}

Cause: The specified setup action was either unavailable on the server or failed with an exception.

Action: Review the configuration to ensure the setup action id is correct, and see server logs for more details on the cause of failure.
Level: 1

Type: ERROR

Impact: Programmatic

ADFDI-55050: Authorization enforcement has been disabled for this instance of ADF Desktop Integration

Cause: The web application was configured so that authorization will not be enforced by ADF Desktop Integration.

Action: Configure the web application so that authorization is enforced by ADF Desktop Integration.
Level: 1

Type: WARNING

Impact: Security

ADFDI-55051: The transaction size limit was exceeded

Cause: Too much data was sent to the server without committing any changes to the database.

Action: Reduce the amount of pending changes and retry the current action.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55052: invalid client metadata request

Cause: An invalid request was received.

Action: Review the server logs to ensure that only supported clients are accessing this servlet.
Level: 1

Type: ERROR

Impact: Requests/Responses

ADFDI-55502: The length of the source data, {0}, is greater than the size of the destination buffer, {1}.

Cause: Internal buffer size mismatch was detected.

Action: Ensure that compatible versions of the client and server framework are in use. Check the workbook configuration and retry the operation with a different workbook.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55510: unable to find expected workbook parameters start tag; found: {0}

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55511: unable to find expected workbook parameters end tag; found: {0}

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55512: The workbook parameters buffer size is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55513: The workbook parameters mode length is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55514: The workbook parameters application root length is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Data

ADFDI-55515: The workbook parameters collection length is incorrect: {0}.

Cause: The internal format of the workbook might be corrupted.

Action: Run the workbook admin tool on this workbook. Ensure that compatible versions of the client and server framework are in use.
Level: 1

Type: ERROR

Impact: Session

ADFDI-55516: Unexpected filter failure

Cause: The filter has failed due to an unexpected condition.

Action: Review the server logs for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

6 ADFF_BIND-00001 to ADFF_BIND-00046

ADFF_BIND-00001: ADFv: Trouble getting the mutable document from MDS. {0}.

Cause: MDS repository may be configured incorrectly, or may have been corrupted.

Action: Check MDS repository configuration and clear repository.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00002: ADFv: ADF JSF databinding support installed.

Cause: n/a.

Action: n/a.
Level: 2

Type: NOTIFICATION

Impact: Configuration

ADFF_BIND-00003: ADFv: ADF JSF databinding support for BC4J installed.

Cause: n/a.

Action: n/a.
Level: 2

Type: NOTIFICATION

Impact: Configuration

ADFF_BIND-00004: ADFv: Cannot convert "{0}" into Array. Updating of arrays not supported.

Cause: Error in application.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00005: ADFv: closing } not found in expression: {0}.

Cause: Error in binding expression in application.

Action: Contact your application support person to correct binding expression.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00006: ADFv: rowIterator is null.

Cause: Internal error.

Action: Contact your application support person.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00007: ADFv: Rowkey does not have any primary key attributes. Rowkey: {0}, table: {1}.

Cause: Application or data error.

Action: Contact your application support person to check for data corruption.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00008: ADFv: No row found for rowKey: {0}.

Cause: Application or data error.

Action: Contact your application support person to check for data corruption.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00009: ADFv: Could not find selected item matching value {0} of type: {1} in the list-of-values.

Cause: Application or data error.

Action: Contact your application support person to ensure list data has not been corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00010: ADFv: AttributeDef not found for property: {0}.

Cause: Application or binding metadata error.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00011: ADFv: Property '{0}' not supported on AttributeHints.

Cause: Application or binding metadata error.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00012: ADFv: Row is null for rowKey: {0}.

Cause: Application or data error.

Action: Contact your application support person to ensure data is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00013: ADFv: Row is null at absoluteIndex: {0} rangeStart: {1} rangeSize: {2} estimatedRowCount: {3}.

Cause: Application or data error.

Action: Contact your application support person to ensure data is correct.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00014: ADFv: Unable to create the temporary file while saving the layout of the resultant component for the query.

Cause: Error in MDS configuration.

Action: Ensure MDS configuration is correct and resources are accessible.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00015: ADFv: Something bad has happened. The file should have been there.

Cause: Error in MDS file.

Action: Ensure MDS configuration is correct and all resources are accessible.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00016: ADFv: The resultant component with the Id {0} does not exist.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00017: ADFv: Result component with the Id {0} not found in the parent.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00018: ADFv: The resultant component layout was not saved for the {0} viewcriteria.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00019: ADFv: Unable to read the contents of the streamedObject.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00020: ADFv: Error filtering based on date strings is not supported(filter field): {0}.

Cause: Error in MDS repository metadata.

Action: Contact your application support person to ensure that MDS repository isn't corrupted.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00021: ADFv: Null PagePhaseListener.

Cause: Trying to add a null phase listener to a page.

Action: Contact your application support person to check the page configuration.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00022: ADFv: Unknown DataChangeType: {0}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00023: ADFv: Invalid attribute name: {0}.

Cause: Check source page for attribute and correct.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00024: ADFv: Illegal DataExceptionEvent severity type: {0}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00025: ADFv: Could not convert instance: {0} of type: {1} into type {2} {3}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00026: ADFv: Property: {0} not found on Row: {1}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00027: ADFv: Unsupported operation exception.

Cause: Application performed an unsupported operation.

Action: Contact your application support person to correct application error.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00028: ADFv: Abort processing exception.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00029: ADFv: No container available.

Cause: Binding metadata is incorrect or corrupted.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00030: ADFv: Not inside a container.

Cause: Binding metadata is incorrect or corrupted.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00031: ADFv: Unknown DataChangeEventPolicy {0}.

Cause: Binding metadata is incorrect or corrupted.

Action: Contact your application support person to ensure binding metadata is correct.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00032: ADFv: Illegal state exception.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00033: ADFv: Attempt to start active for same DataUpdateListener.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00034: ADFv: stopActiveData called for the unregistered listener.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00035: ADFv: Illegal state, parent can't be null.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00036: ADFv: rowIndex: {0} cannot be less than -1.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00037: ADFv: Could not find row: {0} with key: {1} inside parent: {2} with key: {3}.

Cause: Cause unknown.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00038: ADFv: Error getting the application factory.

Cause: Error configuring databinding library.

Action: Ensure that the databinding library is included in the application.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00039: ADFv: Error getting the application object from factory.

Cause: Error configuring databinding library.

Action: Ensure that the databinding library is included in the application.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00040: Invalid Data Provided for search operation.

Cause: Invalid data.

Action: Clear Search Data and enter valid data.
Level: 2

Type: WARNING

Impact: Data

ADFF_BIND-00041: ADFv: Null Calendar Activity Definition. Please check the page definition page.

Cause: Application error.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Data

ADFF_BIND-00042: ADFv: Calendar Activity Id and Provider Id cannot be null.

Cause: Application data error.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00043: ADFv: Illegal state, trying to associate client id {0} with databinding which is already associated with a different client id {1}.

Cause: Application data error.

Action: Contact your application support person.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00044: ADFv: Unable to resolve URL through MDS for the facelet resource. Customizations if any will not be applied. {0}.

Cause: Failed to attach MDS stream handler to the URL for facelet resource.

Action: Contact your application support person.
Level: 2

Type: WARNING

Impact: Programmatic

ADFF_BIND-00045: Invalid value: {0}.

Cause: Invalid value entered in the input field of listofvalues component.

Action: Enter a valid value or pick a value from the list of values.
Level: 2

Type: ERROR

Impact: Programmatic

ADFF_BIND-00046: ViewCriteriaItem for lov attribute not found.

Cause: Search Viewcriteria doesn't have lov attribute as vcItem defined.

Action: While configuring search VC for lov search and select dialog, include lov attribute.
Level: 2

Type: WARNING

Impact: Programmatic

7 ADFSHARE-00002 to ADFSHARE-00150

ADFSHARE-00002: Found {0} sticking to oldContext, while the current application is {1}

Cause:

Action:
Level: 1

Type: Error

Impact: Other

ADFSHARE-00010: An exception is encountered.

Cause: An unknown problem caused an exception.

Action: Contact the system administrator.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00020: Config XML parsing error.

Cause: Encountered error while parsing the config XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00030: Callback parsing error

Cause: Encountered error.

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00040: Close config stream error

Cause: Error encountered while closing the inputStream to remove reference to the adf-config.xml file so that it undeploys successfully.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00050: Config XML syntax error. Error at Column number: {0}, Line number: {1}.

Cause: Encountered error while parsing the config XML.

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00110: MDS Exception encountered in parse ADF Configuration

Cause: Error encountered while parsing ADF Configuration. {0}

Action: Correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00120: Error encountered while creating the MDS Session. Application state will be reset. Please logout and log back in if problem persists.

Cause: Encountered error {0}.

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00130: Error while building the MDS customization configuration

Cause: Encountered error {0}.

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00140: Error while creating MDS tenant instance

Cause: Encountered error while creating MDS tenant instance. {0}

Action: See the associated exceptions.
Level: 2

Type: ERROR

Impact: Programmatic

ADFSHARE-00150: MDS Configuration Exception encountered in parse ADF Configuration

Cause: Encountered MDS exceptions while parsing the ADF Configuration. {0}

Action: See the associated exceptions and correct the contents of the file.
Level: 2

Type: ERROR

Impact: Programmatic

8 B2B-EVT-10001 to B2B-EVT-10003

B2B-EVT-10001: Message Parsing Failed on endpoint and Parse failure exceeded limit. Disabling the endpoint

Cause: Failed to parse the incoming MLLP Message.

Action: Endpoint disabled. Enable the Endpoint and check the payload to make sure it is valid.
Level: 1

Type: ERROR

Impact: Process

B2B-EVT-10002: Pausing the endpoint. Nack received and skip threshold exceeded for endpoint

Cause: Pausing the endpoint. Nack received and skip threshold exceeded for endpoint

Action: Resume the endpoint
Level: 1

Type: ERROR

Impact: Process

B2B-EVT-10003: Resetting the connection. Message Parsing Failed on endpoint and Parse failure exceeded limit

Cause: Resetting the connection. Message Parsing Failed on endpoint and Parse failure exceeded limit

Action: Make sure the payload is valid.
Level: 1

Type: ERROR

Impact: Process

9 B2B-50006 to B2B-53019

B2B-50006: Exception Received

Cause: B2B received an exception message from the trading partner.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50007: Notification of failure received

Cause: B2B received a notification of failure - out of band exception from trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50008: Document level retry count is exhausted.

Cause: Maximum number of document level retries has been reached.

Action: Increase the maximum number of document level retries
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50009: Failed to Send

Cause: B2B cannot send message to the trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50010: Trading partner agreement identification error

Cause: B2B cannot identify an agreement using the current details

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50011: Message Correlation Error

Cause: B2B cannot correlate the message

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50012: Pack/Unpack Error

Cause: Error in packaging

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50013: Security Error

Cause: Error in security validation

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50014: General Error

Cause: Internal error in engine

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50015: In-band notification error

Cause: Internal engine error

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50021: User request to set error for all pending batch messages with same batch id [{0}].

Cause: User request to set error for all pending batch messages with same batch id [{0}]

Action: User request to set error for all pending batch messages with same batch id [{0}]
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50025: Repository error

Cause: Error accessing metadata repository

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50026: Repository error

Cause: Error accessing stream data store

Action: Review the diagnostic log to verify the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50027: Failed to write data into output stream.

Cause: Failed to write data into output stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50028: Failed to read data from input stream.

Cause: Failed to read data from input stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50029: B2B runtime error

Cause: A runtime error has occurred.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50030: B2B Negative Ack Received

Cause: B2B has received a negative acknowledgement

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50031: B2B general error

Cause: A general error has occurred

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50032: B2B exchange protocol negative acknowledge received

Cause: Received a negative exchange acknowledge message.

Action: Review the negative exchange acknowledge message to determine the cause, or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50033: B2B functional acknowledgment processing error

Cause: An error occurred during functional acknowledgment processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50034: B2B negative functional acknowledgment

Cause: A negative functional acknowledgment is received.

Action: Review the negative functional acknowledge message to determine the cause or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50035: B2B exception message processing error

Cause: An error occurred during exception message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50036: B2B trading partner agreement identification error

Cause: An error had occurred during identify trading partner agreement.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50037: B2B inbound message processing error

Cause: An error occurred during incoming message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50038: B2B outbound app message input {0} header processing error

Cause: An error occurred during outbound {0} input processing.

Action: Review the input properties sent for outbound message processing. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50039: Negative Interchange acknowledgment received

Cause: A negative Interchange acknowledgment is received.

Action: Review the negative Interchange acknowledge message to determine the cause or check with the trading partner.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50040: Unable to correlate the received Functional Ack

Cause: A Functional Ack received for unknown message.

Action: Review the control number of the incoming message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50041: TopLink server session initialization error

Cause: An error occurred during TopLink server session initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50042: B2B trace context initialization error

Cause: An error occurred during trace context initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50043: Functional acknowledgement received for errored business message with id {0}

Cause: Functional acknowledgement received for errored business message.

Action: Review the control number of the original business in the incoming FA payload.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50044: Exception Message Received from backend

Cause: An Exception Message Received from backend.

Action: Review the payload from the Exception message.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50050: Engine initialization error.

Cause: An error occurred during engine initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50051: Failed to shut down the B2B engine.

Cause: An error occurred during engine shut down.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50052: Engine already initialized.

Cause: Attempt made to initialize B2B engine which has been initialized already.

Action: Ensure that the engine is stopped before attempting to initialize
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50059: Error in starting B2B Server.

Cause: An error has occurred while starting the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-50060: Error in stopping B2B Server

Cause: An error has occurred while stopping the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50075: Error loading document or exchange plug-in.

Cause: Error loading document or exchange plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50076: Error loading packaging plug-in.

Cause: Error loading packaging plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50077: Cannot Initialize Transport.

Cause: Cannot Initialize Transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50078: Cannot shut down transport.

Cause: Cannot shut down transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50079: Transport error

Cause: An error has occurred in transport layer

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50080: Exchange protocol identification error.

Cause: Failed to identify the exchange protocol of the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50081: Duplicate exchange protocol message error

Cause: Duplicate exchange protocol message generated by the trading partner.

Action: Report this error to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-50082: Duplicated Control Number error

Cause: Message received with duplicate control number {0}.

Action: Report this error to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-50083: Document protocol identification error.

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50084: No service found

Cause: Requested service was not registered in system

Action: Check requested web service URL
Level: 1

Type: ERROR

Impact: Process

B2B-50085: Duplicated transaction number error for xpath {0} with value {1}. The message id : {2}

Cause: Message received with duplicate transaction number error for xpath {0} with value {1}. The message id : {2}

Action: Check the xpath value of the message
Level: 1

Type: ERROR

Impact: Process

B2B-50086: Error during the identification of Group segment in payload. {0}

Cause: Failed to identify the document protocol for the message.

Action: Check the group segment in the payload.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50087: Error during the identification of Interchange segment in payload. {0}

Cause: Failed to identify the document protocol for the message.

Action: Check the group segment in the payload.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50545: An agreement {0} has expired or is not in force as yet. The effective From/To dates are {1} - {2}.

Cause: An agreement effective From/To dates are invalid.

Action: Change the agreement effective From/To dates.
Level: 1

Type: ERROR

Impact: Process

B2B-50546: Information given to identify an agreement is insufficient: FromTP {0}, ToTP {1}, document type {2}.

Cause: Failed to identify the agreement

Action: Make sure From/To TP and document information is not Null.
Level: 1

Type: ERROR

Impact: Process

B2B-50547: Agreement not found for trading partners: FromTP {0}, ToTP {1} with document type {2}.

Cause: Failed to identify the trading partner agreement from the given input values.

Action: Make sure there is an agreement configured for the From/To trading partner and document information that presents in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50548: Agreement {0} not in active state.

Cause: Agreement was not in active state.

Action: Make sure the agreement is deployed and it is in Active state.
Level: 1

Type: ERROR

Impact: Process

B2B-50549: Cannot uniquely identify the trading partner. The trading partners {0} have the same set of identifications.

Cause: The trading partners {0} have the same set of identifications

Action: Make sure the trading partners have unique identifications
Level: 1

Type: ERROR

Impact: Process

B2B-50550: Cannot find the trading partner for the given identification type {0} and value {1}

Cause: The trading partner was not exist for the given identification type and value.

Action: Create or update the trading partner with the given identification type and value.
Level: 1

Type: ERROR

Impact: Process

B2B-50601: Agreement found but the certificate used for client authentication may not represent the Trading Partner {0} whom it claims to be.

Cause: Certificate used for client authentication may not belong to the Trading Partner.

Action: Please make sure Trading partner alias has been configured correctly against Security Identifier. If it is not, then it is a serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

B2B-50602: Keystore not available to validate the incoming certificate over SSL.

Cause: Keystore may not be properly configured in B2B to validate the incoming SSL client certificate.

Action: Please make sure keystore has been configured correctly in B2B.
Level: 1

Type: ERROR

Impact: Process

B2B-50603: Agreement found but authenticated principal(user) over http do not represent the Trading Partner {0} whom it claims to be.

Cause: Authenticated user may not represent the Trading Partner.

Action: Please make sure the Security Identifier configuration in B2B against the Trading Partner is correct. If the value is correct, then it is serious security error, please consult your security administrator for further course of action.
Level: 1

Type: ERROR

Impact: Process

B2B-50651: Agreement not found for trading partners: FromTP {0}, ToTP {1} with {2}.

Cause: Failed to match the service, action, servicetype for the trading partner agreement from the message.

Action: Make sure there is an agreement that contains a matching service, action, servicetype in the CPA configured for the From/To, service,action, servicetype information that is present in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50701: The agreement {0} cannot be activated because a similar agreement {1} found in active state

Cause: Similar agreement found in active state. There cannot be two agreements with the same trading partners, document type, version, and direction.

Action: Make inactive existing active agreement which has the same trading partners, document type, version, and direction.
Level: 1

Type: ERROR

Impact: Process

B2B-50702: {0} does not exist in the repository.

Cause: {0} does not exist in the repository.

Action: Channel/TPName does not exist in the repository. Get the latest list of channels.
Level: 1

Type: ERROR

Impact: Process

B2B-50703: Endpoint {0} does not exist in the group.

Cause: Endpoint {0} does not exist in the group.

Action: Endpoint does not exist in the group. Get the latest list of endpoints.
Level: 1

Type: ERROR

Impact: Process

B2B-50704: Group {0} does not exist in the repository.

Cause: Group {0} does not exist in the repository.

Action: Group does not exist in the repository. Get the latest list of group.
Level: 1

Type: ERROR

Impact: Process

B2B-50705: Duplicate Endpoint {0}.

Cause: Endpoint {0} already exist in the repository

Action: Endpoint already exist in the repository.Can not create same name endpoint
Level: 1

Type: ERROR

Impact: Process

B2B-50706: No callout for internal delivery channel.

Cause: Callout can not be set for internal delivery channel.

Action: Remove callout from internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-50707: Endpoint Validation Error

Cause: Endpoint validation error.

Action: Endpoint validation error.Check the diagnostic log for more details.
Level: 1

Type: ERROR

Impact: Process

B2B-50708: Mandatory parameter value missing.

Cause: Mandatory Parameter can not be null.

Action: Provide the mandatory parameter value.
Level: 1

Type: ERROR

Impact: Process

B2B-50709: Endpoint Disablement Failed.

Cause: Endpoint can not disabled

Action: Endpoint Disablement Failed. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50710: Document Protocol {0} does not supported

Cause: Document Protocol {0} not supported.

Action: Document Protocol does not supported.
Level: 1

Type: ERROR

Impact: Process

B2B-50711: Document definition {0} not exists

Cause: Document definition {0} does not exists.

Action: Document definition does not exists.
Level: 1

Type: ERROR

Impact: Process

B2B-50712: Error in removing document.

Cause: Error while removing document from endpoint.

Action: There is error while removing document from endpoint. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50713: Internal Delivery Channel is used in endpoint document

Cause: Internal Delivery Channel is used in endpoint document

Action: Internal Delivery Channel is used in endpoint document. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50714: IDREF_KEY Missing.

Cause: IDREF_KEY Missing in configuration.

Action: IDREF_KEY Missing in configuration. Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50715: No document attached to endpoint

Cause: There is no document attached to endpoint.

Action: There is no document attached to endpoint.There should be at least one document attached to enable the endpoint.Check the diagnostic log.
Level: 1

Type: ERROR

Impact: Process

B2B-50716: FTP Sequencing Parameters missing

Cause: timestamp_format,timestamp_offset,timestamp_source values are must for FTP if Sequencing is enabled

Action: Provide timestamp_format,timestamp_offset,timestamp_source values for FTP endpoint.
Level: 1

Type: ERROR

Impact: Process

B2B-50717: Block characters missing

Cause: Block characters parameters values are missing.

Action: Provide the Block characters parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-50718: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Cause: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Action: Make sure channel is not associated with any TradingPartner(s).
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50741: WS-HTTP transport protocol must have WSDL Artifacts.

Cause: WS-HTTP transport protocol did not have WSDL Artifacts.

Action: make sure WS-HTTP transport protocol has WSDL Artifacts.
Level: 1

Type: ERROR

Impact: Process

B2B-50742: Service parameter are not well formed in WS-HTTP channel.

Cause: service parameter did not have namespace encloses with curly braces in WS-HTTP Channel.

Action: Make sure service parameter has namespace encloses with curly braces in WS-HTTP channel.
Level: 1

Type: ERROR

Impact: Process

B2B-50743: Invalid Payload received for Sync Request from Backend. Payload is null

Cause: Either Back-end composite is a One-Way composite, or it is not configured properly to return a response.

Action: Make sure Composite is configured to send a response
Level: 1

Type: ERROR

Impact: Process

B2B-50744: Keystore details missing or invalid.

Cause: Keystore details have not been provided or are invalid.

Action: Provide Keystore details.If provided then check the validity of keystore location and password.
Level: 1

Type: ERROR

Impact: Process

B2B-50801: No input value is specified. At least one input value is needed: From/To trading partner or Document or Action

Cause: Missing input values

Action: Specify input values such as From/To trading partner or Document or Action
Level: 1

Type: ERROR

Impact: Process

B2B-50901: Failed to find a business message with B2BMessageId {0}.

Cause: Failed to find a business message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.
Level: 1

Type: ERROR

Impact: Process

B2B-50902: Failed to find a wire message with B2BMessageId {0}.

Cause: Failed to find a wire message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.
Level: 1

Type: ERROR

Impact: Process

B2B-50903: Message {0} retry count is zero.

Cause: The maximum number of message retries has been reached.

Action: Increase the maximum number of retries in delivery channel.
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50904: ReferTo message not found.

Cause: The message ID specified in the header RefToMessageID not found.

Action: It is possible that the original message was purged. Try resubmitting the original message.
Level: 1

Type: ERROR

Impact: Process

B2B-50906: Failed to retrieve value for the given XPATH.

Cause: Error occurred while extracting XPATH value.

Action: Make sure XPATH in document definition is correct and applicable for the payload
Level: 1

Type: ERROR

Impact: Process

B2B-51000: General packaging Error

Cause: Packaging details were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-51001: Packaging fail

Cause: Packaging information were insufficient.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51002: Unpacking fail

Cause: Packaging headers were incorrect.

Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51003: Encoding failed

Cause: Encoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51004: Decoding failed

Cause: Decoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51005: Validating packaging metadata failed.

Cause: Packaging metadata was insufficient.

Action: Verify packaging metadata to pack the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51006: Invalid input parameter

Cause: Packaging input parameters were invalid.

Action: Verify the packaging parameters and packaging metadata.
Level: 1

Type: ERROR

Impact: Process

B2B-51007: Missing packaging metadata information.

Cause: Missing few packaging metadata.

Action: Verify the packaging metadata.
Level: 1

Type: ERROR

Impact: Process

B2B-51008: Circular dependency in packaging metadata.

Cause: Circular dependency found in packaging metadata.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51009: Missing one or more packaging elements in packaging metadata.

Cause: Missing one or more packaging elements in packaging metadata.

Action: Verify packaging metadata has packaging elements.
Level: 1

Type: ERROR

Impact: Process

B2B-51010: Missing composite packaging element in packaging metadata.

Cause: None of the composite packaging elements exist in the Multipart message.

Action: Make sure Multipart message has at least one composite packaging element.
Level: 1

Type: ERROR

Impact: Process

B2B-51011: Invalid packaging metadata.

Cause: Message has more than one simple part. Hence, failed to package the message.

Action: Verify MIME message has only one simple part.
Level: 1

Type: ERROR

Impact: Process

B2B-51012: Missing list of message components.

Cause: Missing list of message component in the message.

Action: Verify the message has list of component.
Level: 1

Type: ERROR

Impact: Process

B2B-51013: Missing one or more message components in the list of message components.

Cause: Protocol components did not have all the required components while packaging information.

Action: Verify the protocol components and set all the required components for packaging the information.
Level: 1

Type: ERROR

Impact: Process

B2B-51014: Missing data for message component.

Cause: Invalid data for message component.

Action: Verify message has component data.
Level: 1

Type: ERROR

Impact: Process

B2B-51015: Missing security information.

Cause: Invalid security information.

Action: Verify security information is exist in packaging.
Level: 1

Type: ERROR

Impact: Process

B2B-51016: Missing signature information.

Cause: Invalid digital signature information.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51017: Missing encryption information.

Cause: Required envelope information did not exist.

Action: Verify the required envelope information available in packaging.
Level: 1

Type: ERROR

Impact: Process

B2B-51018: Message is not digitally signed.

Cause: Message was not digitally signed.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51019: Message is not encrypted.

Cause: Message was not encrypted.

Action: Verify the message which has to be encrypted.
Level: 1

Type: ERROR

Impact: Process

B2B-51020: Signature protocol is not supported.

Cause: Signature protocol was not Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a signature protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51021: Encryption protocol is not supported.

Cause: Encryption protocol was not a Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a encryption protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51022: Digest algorithm does not match.

Cause: Invalid digest algorithm.

Action: Verify digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51023: Required signature information are already set for message.

Cause: Attempt made to set the signature information when it already has been set.

Action: Remove the existing signature information before attempting to set this new signature information.
Level: 1

Type: ERROR

Impact: Process

B2B-51024: Required envelope information is already set for message.

Cause: Attempt made to set envelope information when it has already been set.

Action: Remove the existing envelope information before attempting to set this new envelope information.
Level: 1

Type: ERROR

Impact: Process

B2B-51025: Keystore resource location incorrect

Cause: Incorrect keystore location specified.

Action: Specify correct keystore location.
Level: 1

Type: ERROR

Impact: Process

B2B-51026: Encoding type is not supported

Cause: Encoding type was not supported.

Action: Verify supported encoding type as any one of base64, quoted-printable, 7bit, 8bit, or binary.
Level: 1

Type: ERROR

Impact: Process

B2B-51050: MIME Content-Types do not match.

Cause: Mismatched MIME body part and MIME type.

Action: Verify the Content-Types in MIME body part.
Level: 1

Type: ERROR

Impact: Process

B2B-51051: MIME Content-Type parameter lists do not match.

Cause: While creating MIME body part, MIME Content-Type parameter lists mismatch.

Action: Verify the MIME Content-Type parameters list.
Level: 1

Type: ERROR

Impact: Process

B2B-51052: Invalid MIME Content-Type header or information.

Cause: Missing MIME Content-Type and value.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51053: Invalid MIME content disposition header or information.

Cause: Missing MIME content disposition header value.

Action: Verify MIME header content disposition.
Level: 1

Type: ERROR

Impact: Process

B2B-51054: Missing MIME Content-Type header information.

Cause: MIME Content-Type information was not exist.

Action: Verify MIME Content-Type header exist.
Level: 1

Type: ERROR

Impact: Process

B2B-51055: Missing information for message component.

Cause: Information were not exist for message component.

Action: Verify the message component information.
Level: 1

Type: ERROR

Impact: Process

B2B-51056: Missing or unable to read data from message.

Cause: Failed to read data from message.

Action: Verify the message data.
Level: 1

Type: ERROR

Impact: Process

B2B-51057: Invalid or corrupted message.

Cause: Invalid message format.

Action: Verify the message format.
Level: 1

Type: ERROR

Impact: Process

B2B-51075: Missing signer certificate.

Cause: Signer certificate not found.

Action: Provide the certificate to sign the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51076: Missing encryption certificate.

Cause: Encryption certificate not found.

Action: Provide the certificate to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51077: Missing certificate chain.

Cause: Invalid certificate chain was exist.

Action: Provide the proper certificate with certificate chain.
Level: 1

Type: ERROR

Impact: Process

B2B-51078: Message has invalid digest information.

Cause: Failed to digest message or message corrupted.

Action: Provide appropriate digest for message.
Level: 1

Type: ERROR

Impact: Process

B2B-51079: S/MIME version is not supported.

Cause: Unsupported S/MIME version.

Action: Verify the S/MIME version should be either 2.0 or 3.0.
Level: 1

Type: ERROR

Impact: Process

B2B-51080: Signature algorithm {0} is not supported.

Cause: Unsupported signature algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51081: Digest algorithm {0} is not supported.

Cause: Unsupported digest algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: ERROR

Impact: Process

B2B-51082: Encryption algorithm {0} is not supported.

Cause: Unsupported encryption algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51083: General failure creating S/MIME digital signature.

Cause: A failure has occurred when creating the S/MIME digital signature.

Action: Verify that the keystore has the correct private key and certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51084: General failure verifying S/MIME digital signature.

Cause: A general failure has occurred when attempting to verify the S/MIME digital signature.

Action: 1. Use correct certificate to verify the signature. 2. Message might have been corrupted. Check with the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51085: General failure encrypting S/MIME message.

Cause: A general failure has occurred when attempting to encrypt the S/MIME digital signature.

Action: Use valid trading partner certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51086: General failure while decrypting S/MIME message.

Cause: General failure while decrypting S/MIME message.

Action: 1. Use correct Key Pair to decrypt the message. 2. Message might have been corrupted. Check with the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51087: Could not create digest data for S/MIME digital signature {0}.

Cause: Creating digest data for S/MIME digital signature failed {0}.

Action: Use the supported algorithm as per the S/MIME standard or as per the exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-51088: Creating S/MIME digital signature failed {0}.

Cause: Failed to create S/MIME digital signature.

Action: Check the signing credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51089: Unable to verify S/MIME digital signature.

Cause: Verifying S/MIME digital signature failed {0}.

Action: Use correct certificate to verify the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51090: Unable to create S/MIME message recipient.

Cause: Creating S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51091: Unable to add a recipient to S/MIME message recipient list {0}.

Cause: Adding recipient to S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51092: Encrypting S/MIME message failed {0}.

Cause: Failed to encrypt S/MIME message.

Action: Check the certificate used to encrypt the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51093: Decrypting S/MIME message failed {0}.

Cause: Message encrypted using a wrong certificate.

Action: Check the key-pair used to decrypt the message or verify with the trading partner that the certificate used to encrypt the message is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51094: Processing signature information for S/MIME message failed.

Cause: Failed to Process signature information for S/MIME message.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51095: Processing envelope information for S/MIME message failed.

Cause: Failed to process envelope information for S/MIME message.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51096: Cannot include more than one signer in the S/MIME digital signature.

Cause: More than one signer in the S/MIME digital signature was not supported.

Action: Ask the trading partner to send the message with the single signer.
Level: 1

Type: ERROR

Impact: Process

B2B-51097: Found empty packaging IDs list during packaging plug-in initialization.

Cause: An empty packaging IDs list is passed for packaging plug-in initialization.

Action: Make sure correct packaging is mentioned.
Level: 1

Type: ERROR

Impact: Process

B2B-51098: Invalid Content-Type {0} in packaging metadata.

Cause: Packaging metadata contains invalid Content-Type.

Action: Make sure correct packaging details are mentioned.
Level: 1

Type: ERROR

Impact: Process

B2B-51099: An incorrect RosettaNet version has been found in the message.

Cause: Not a RosettaNet 1.1 message.

Action: Verify the packaging version.
Level: 1

Type: ERROR

Impact: Process

B2B-51105: Unsupported algorithm

Cause: Algorithm used was not supported by the S/MIME or exchange protocol.

Action: Use correct algorithm as specified by the exchange protocol or S/MIME standard.
Level: 1

Type: ERROR

Impact: Process

B2B-51107: Digest mismatch

Cause: Document might have been corrupted during transport.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51108: Failed to digest the message.

Cause: Failed to create the digest for the message.

Action: Check the payload or digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51112: An invalid CRL has been found in the incoming message.

Cause: Invalid CRL.

Action: Check with the trading partner that CRL is correct and request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51114: CRL missing issuer

Cause: Issuer not found in CRL.

Action: Check with the trading partner that CRL issuer is correct and request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51120: Invalid Content-Type

Cause: Content-Type of the signed/encrypted message was not correct.

Action: Request a re-send from the partner or resend the message with correct Content-Type.
Level: 1

Type: ERROR

Impact: Process

B2B-51121: Empty recipient list

Cause: No recipient list was exist in the encrypted message.

Action: Check with the trading partner and request a re-send with recipient list.
Level: 1

Type: ERROR

Impact: Process

B2B-51122: Certificate decode error

Cause: Certificate was not correct.

Action: Check if the certificate is in correct format.
Level: 1

Type: ERROR

Impact: Process

B2B-51124: Failed to create certificate chain

Cause: Unable to create certificate chain while generating the message.

Action: Check if the certificate used is a trusted certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51125: No certificate to sign

Cause: Certificate used to sign the message was not available in the keystore.

Action: Check if the certificate is available in the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-51128: Certificate missing issuer

Cause: The certificate that is being used was missing issuer information.

Action: Use a trusted certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51143: Certificate expired

Cause: The certificate has expired.

Action: 1. Make sure host and trading partner has selected the local time zone, 2. If the time zone is correct request the trading partner to generate a new certificate.
Level: 1

Type: ERROR

Impact: Process

B2B-51145: Certificate is not valid yet.

Cause: Certificate was not valid. Because the certificate creation date was later than current system date.

Action: 1. Make sure Host and trading partner has selected the local time zone 2. System current date is later than certificate creation date.
Level: 1

Type: ERROR

Impact: Process

B2B-51147: Missing recipient information

Cause: Missed recipient information.

Action: Ask the trading partner to check the recipient certificate added during encryption and request for a re-send.
Level: 1

Type: ERROR

Impact: Process

B2B-51150: Failed to verify certificate chain.

Cause: Unable to verify the certificate chain while processing the message.

Action: Verify the certificates used and request a re-send.
Level: 1

Type: ERROR

Impact: Process

B2B-51152: CRL verification failed

Cause: CRL verification failed.

Action: CRL received not matching with the certificates in the keystore. Request the trading partner to send the correct CRL.
Level: 1

Type: ERROR

Impact: Process

B2B-51153: Certificate revoked

Cause: Certificate revoked.

Action: Request a re-send with the valid certificate from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51154: Certificate signature verification failed.

Cause: Failed to verify the certificate signature.

Action: Request for the valid certificate from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51165: Digest algorithm missing.

Cause: Message received with incorrect digest algorithm.

Action: Request a re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51193: Failed to open keystore.

Cause: Keystore file was not in correct format, incorrect location or incorrect password.

Action: Make sure the keystore is generated properly or the location or password is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51195: Failed to get key pair from keystore

Cause: Unable to retrieve key pair from the keystore.

Action: Verify that the keystore has valid key pair.
Level: 1

Type: ERROR

Impact: Process

B2B-51197: LDAP error

Cause: LDAP error

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51198: LDAP connect failed.

Cause: LDAP connect failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51199: LDAP bind failed.

Cause: LDAP bind failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51200: LDAP search failed.

Cause: LDAP search failed.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51201: LDAP entry missing attribute.

Cause: LDAP entry missing attribute.

Action: Check the LDAP details.
Level: 1

Type: ERROR

Impact: Process

B2B-51202: No certificate in the directory for this user

Cause: Unable to retrieve the certificate for this user from the directory.

Action: Make sure that the certificate is available in the directory.
Level: 1

Type: ERROR

Impact: Process

B2B-51203: Error compressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload.
Level: 1

Type: ERROR

Impact: Process

B2B-51204: Error decompressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload received or request for re-send from the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51205: The alias is not present or configured incorrectly in partner profile

Cause: The alias is not present or configured incorrectly in partner profile.

Action: Make sure that the alias is available in the partner profile.
Level: 1

Type: ERROR

Impact: Process

B2B-51206: Validation of signatures or checks on the authenticity or authority of the sender of the message have failed.

Cause: Alias is present but received message is unsigned

Action: Make sure received message is signed
Level: 1

Type: ERROR

Impact: Process

B2B-51207: Database Connection Failed.

Cause: Database Connection failed.

Action: Check the Datasource details.
Level: 1

Type: ERROR

Impact: Process

B2B-51208: SQL Exception occurred during JDBC processing

Cause: SQL Exception occurred during JDBC processing.

Action: Check the Datasource details.
Level: 1

Type: ERROR

Impact: Process

B2B-51300: Interface Sequencing failure - Inbound sequence row not present for correlation

Cause: Inbound sequence row not present for correlation.

Action: Check if the group count is configured incorrectly or if the sequence row was discarded.
Level: 1

Type: ERROR

Impact: Process

B2B-51500: Document exchange success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-51501: Document exchange initialization failure.

Cause: Failed to initialize the document specific guidelines.

Action: Verify the document specific initialization parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51503: General create message error.

Cause: Failed to create message components.

Action: Verify values for message creation components.
Level: 1

Type: ERROR

Impact: Process

B2B-51504: General decode error.

Cause: Failed to decode the message.

Action: Verify the incoming message contents.
Level: 1

Type: ERROR

Impact: Process

B2B-51505: General validation error.

Cause: An unexpected error occurred during validation.

Action: Verify the validity of the document against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51506: Message digest validation error.

Cause: Message digest obtained from the incoming message payload, did not match with the original message digest.

Action: Verify the digest algorithm.
Level: 1

Type: ERROR

Impact: Process

B2B-51507: Payload validation error.

Cause: An error occurred during message payload processing in document plug-in.

Action: Verify the message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51508: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system. {0}

Cause: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system.{0}

Action: Verify the EDI group header parameters of the message validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51509: Create message error: component- {0}.

Cause: Failed to create message components.

Action: Verify all components of the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51510: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify the batch message payload validity against the document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-51511: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51512: Message payload parameter validation error.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51513: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Action: Verify the EDI Interchange header parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51514: Validation of Message header parameters failed. Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.

Cause: An error occurred in message header of document during message processing.

Action: Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51515: Validation of parameters failed. Some or all of the following parameters do not match the configured parameters in B2B.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.
Level: 1

Type: ERROR

Impact: Process

B2B-51516: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in B2B.
Level: 1

Type: ERROR

Impact: Process

B2B-51517: Document protocol identification error.{0}

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51518: Mandatory parameter {0} {1} is missing.

Cause: Mandatory parameter {0} {1} is missing.

Action: Verify mandatory parameter is the same in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51519: Interchange Receiver Id is not present.

Cause: Interchange Receiver Id is not present.

Action: Verify the Interchange Receiver Id is the same in payload and configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51520: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Cause: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Action: Verify the document Interchange parameters of the message validity against the document definition
Level: 1

Type: ERROR

Impact: Process

B2B-51521: Document Callout Translation error: {0}.

Cause: Error while using callout to translate document

Action: Check payload and read the parsing error
Level: 1

Type: ERROR

Impact: Process

B2B-51522: Translation is not enabled in the agreement. {0}

Cause: Translation is not enabled in the agreement. {0}

Action: Enable the translation in the associated agreement in the B2B console
Level: 1

Type: ERROR

Impact: Process

B2B-51550: Invalid usage code.

Cause: Specified usage code was neither production nor test.

Action: Verify that the usage code is either production or test.
Level: 1

Type: ERROR

Impact: Process

B2B-51551: Invalid timestamp.

Cause: Timestamp was not in the correct format.

Action: Correct timestamp format is CCYYMMDDThhmmss.sssZ.
Level: 1

Type: ERROR

Impact: Process

B2B-51552: Mismatch in the PIP binding ID.

Cause: PIP binding ID in the initiating message did not match the PIP binding ID in the response message.

Action: Ensure that the PIP binding ID in the initiating message matches the PIP binding ID in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51553: Mismatch in PIP code.

Cause: PIP code in the initiating message did not match the PIP code in the response message.

Action: Ensure that PIP Code in the initiating message matches the PIP code in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51554: Mismatch PIP in instance ID.

Cause: PIP instance ID in the initiating message did not match the PIP instance ID in the response message.

Action: Ensure that the PIP instance ID in the initiating message matches the PIP instance ID in the responding message.
Level: 1

Type: ERROR

Impact: Process

B2B-51555: Mismatch in PIP version.

Cause: PIP version in the initiating message did not match the PIP version in the response message.

Action: Ensure that PIP version in the initiating message matches the PIP version in the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51556: Invalid response message.

Cause: Message ID in the initiating message did not match the message ID in the RefTo field of the response message.

Action: Ensure that message ID in the initiating message matches the message ID in the RefTo field of the response message.
Level: 1

Type: ERROR

Impact: Process

B2B-51557: PIP binding ID exceeds 255 characters.

Cause: PIP binding ID cannot exceed 255 characters.

Action: Limit the total characters of PIP binding ID to 255.
Level: 1

Type: ERROR

Impact: Process

B2B-51558: Invalid value for secure transport required attribute.

Cause: Secure transport was neither Yes nor No.

Action: Ensure that the secure transport has values Yes or No.
Level: 1

Type: ERROR

Impact: Process

B2B-51559: Mismatch in manifest content-type.

Cause: Content-type in the manifest did not match the content-type associated with the attachment.

Action: Ensure that the content-type in the manifest and attachment are the same.
Level: 1

Type: ERROR

Impact: Process

B2B-51560: Mismatch in manifest content-ID.

Cause: Content-ID in the manifest did not match the content-ID associated with the attachment.

Action: Ensure that the content-ID in the manifest matches the content-ID associated with the attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51561: Mismatch in the service of the host and the trading partner.

Cause: FromService field in the initiating message did not match the ToService field in the response message.

Action: Verify the FromService field of the host matches with ToService field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51562: Mismatch in the service of the host and the trading partner.

Cause: ToService field in the initiating message did not match the FromService field in the response message.

Action: Verify the ToService field of the host matches with FromService of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51563: Mismatch in the role of the host and the trading partner.

Cause: FromRole field in the initiating message did not match the ToRole field in the response message.

Action: Verify the FromRole field of the host matches with ToRole field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51564: Mismatch in the role of the host and the trading partner.

Cause: ToRole field in the initiating message did not match the FromRole field in the response message.

Action: Verify the ToRole field of the host matches with FromRole field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51565: An unexpected error occurred while initializing the XML parser.

Cause: Failed to initialize XML parser.

Action: Ensure that the XML parser initialized properly.
Level: 1

Type: ERROR

Impact: Process

B2B-51566: Parse stream error

Cause: An unexpected error occurred while parsing the input stream.

Action: Verify the message components of incoming message.
Level: 1

Type: ERROR

Impact: Process

B2B-51567: Invalid Content-Type

Cause: Sub-type of the Content-Type in the HTTP header was neither Multipart/related nor Multipart/signed.

Action: Check for the Content-Type in the HTTP header.
Level: 1

Type: ERROR

Impact: Process

B2B-51568: encoding error

Cause: An unexpected error occurred while encoding data.

Action: Verify encoded type is base64.
Level: 1

Type: ERROR

Impact: Process

B2B-51569: decoding error

Cause: An unexpected error occurred while decoding data.

Action: Verify the decode type is base64.
Level: 1

Type: ERROR

Impact: Process

B2B-51570: Attachment error

Cause: An unexpected error occurred while creating an attachment as component data.

Action: Verify the well-form of the XML content for attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51571: Attachment error

Cause: An unexpected error occurred while forming an attachment as XML data.

Action: Verify that the XML format of the data for the attachment is well-formed XML. Also verify the encoding and type attributes of attachment.
Level: 1

Type: ERROR

Impact: Process

B2B-51572: Error reading input stream.

Cause: An unexpected error occurred while reading the input stream.

Action: Ensure the input value is nonempty.
Level: 1

Type: ERROR

Impact: Process

B2B-51573: Unexpected payload file naming, default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat

Cause: Payload file name was not as per expected naming convention.

Action: Expect default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat.
Level: 1

Type: ERROR

Impact: Process

B2B-51574: Error loading XEngine libraries. XEngine is most likely not installed.

Cause: XEngine was not installed.

Action: Make sure XEngine is installed.
Level: 1

Type: ERROR

Impact: Process

B2B-51575: Incorrect document exchange version.

Cause: Document exchange version mismatch.

Action: Verify the document exchange header value.
Level: 1

Type: ERROR

Impact: Process

B2B-51576: Incorrect document exchange.

Cause: Document exchange mismatch.

Action: Verify the document exchange name.
Level: 1

Type: ERROR

Impact: Process

B2B-51577: Document exchange validation error

Cause: Document exchange validation failed.

Action: Verify the document exchange header values
Level: 1

Type: ERROR

Impact: Process

B2B-51578: Exception Reported: {0}

Cause: B2B is unable to continue processing due to Control Number sequence generation failure.

Action: Please refer to documentation for EM property : b2b.useSequenceControlNum for further information.
Level: 1

Type: ERROR

Impact: Process

B2B-51703: Failed to unpack the message.

Cause: An unexpected error occurred during the unpackaging of the RosettaNet business message.

Action: Verify the message headers.
Level: 1

Type: ERROR

Impact: Process

B2B-51705: Unable to read the preamble.

Cause: Failed to read preamble.

Action: Ensure the correctness of preamble content.
Level: 1

Type: ERROR

Impact: Process

B2B-51707: Unable to read the delivery header.

Cause: Failed to read delivery header.

Action: Ensure the correctness of the delivery header content.
Level: 1

Type: ERROR

Impact: Process

B2B-51709: Unable to read the service header.

Cause: Failed to read the service header.

Action: Ensure the correctness of the service header.
Level: 1

Type: ERROR

Impact: Process

B2B-51715: Failed to unpack the message - reading the service content.

Cause: Failed to read the service content.

Action: Ensure the correctness of the service content.
Level: 1

Type: ERROR

Impact: Process

B2B-51915: No type is specified in party ID.

Cause: No type was specified in party ID.

Action: Specify a party ID type.
Level: 1

Type: ERROR

Impact: Process

B2B-51916: Reference ID in the manifest does not match payload ID.

Cause: Reference ID in the manifest did not match payload ID.

Action: Make sure that reference ID in the manifest matches the payload ID.
Level: 1

Type: ERROR

Impact: Process

B2B-51917: Content-Type set for ebMS message is incorrect.

Cause: Content-Type set for ebMS message was incorrect.

Action: Set a valid Content-Type for the ebMS message.
Level: 1

Type: ERROR

Impact: Process

B2B-51918: This version of ebMS is not supported. Only version 2.0 is supported.

Cause: This version of ebMS was not supported. Only version 2.0 is supported.

Action: Make sure to exchange messages for the supported version.
Level: 1

Type: ERROR

Impact: Process

B2B-51919: Hub mode not supported.

Cause: As Hub mode was not supported, the actor value is incorrect.

Action: Specify the actor as urn:oasis:names:tc:ebXML-msg:actor:toPartyMSH
Level: 1

Type: ERROR

Impact: Process

B2B-51921: SOAP message has defective packaging.

Cause: Defect identified in packaging of the SOAP message.

Action: Make sure that the message is a valid SOAP message.
Level: 1

Type: ERROR

Impact: Process

B2B-51922: If the service type is not specified then the service must be a URI.

Cause: If the service type was not specified then the service must be a URI.

Action: Specify a service URI if the service type is not specified.
Level: 1

Type: ERROR

Impact: Process

B2B-51923: Value {0} for the element {1} is not recognized.

Cause: Failed to recognise value for the element.

Action: Specify a correct value for the element.
Level: 1

Type: ERROR

Impact: Process

B2B-51924: Message failed the security check.

Cause: Message failed the security check.

Action: Verify that the message has been encrypted and signed with the correct credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51925: Feature {0} is not supported.

Cause: Selected feature is not supported.

Action: Make sure the feature is currently supported.
Level: 1

Type: ERROR

Impact: Process

B2B-51926: SyncReply element must exist in the message.

Cause: SyncReply element must be present in the message.

Action: Add a SyncReply element in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51927: Time to live has expired for the message.

Cause: Time to live has expired for the message.

Action: Make sure to send a message with a valid time to live value.
Level: 1

Type: ERROR

Impact: Process

B2B-51928: Message header validation failed. The received {0} does not match with the configured {1}.

Cause: Message header did not have the element.

Action: Make sure to add element to the message header.
Level: 1

Type: ERROR

Impact: Process

B2B-51929: No payload is found for the reference ID {0}.

Cause: No payload attached for the reference ID.

Action: Make sure to have a payload for the reference ID, or remove this reference ID from the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51930: Message with ID {0} is a duplicate message.

Cause: Duplicate message identified with same ID.

Action: Make sure to send a message with a unique message ID, a message which is not duplicated.
Level: 1

Type: ERROR

Impact: Process

B2B-51931: Error found in decrypting or verifying the message.

Cause: Error in decryption or on message verification.

Action: Make sure that the message is being decrypted and verified with the correct credentials.
Level: 1

Type: ERROR

Impact: Process

B2B-51932: Multiple parts with same Content-ID or Content-Location header.

Cause: Multiple parts with same Content-ID or Content-Location header.

Action: Use different Content-ID or Content-Location header values for different MIME parts of the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51933: Referenced Content-ID or Content-Location header not found.

Cause: Referenced Content-ID or Content-Location header not found.

Action: Make sure that the referenced Content-ID or Content-Location header values are valid.
Level: 1

Type: ERROR

Impact: Process

B2B-51934: Unhandled attachment object {0} found.

Cause: Unhandled attachment object found.

Action: Make use of correct attachment type for attaching objects.
Level: 1

Type: ERROR

Impact: Process

B2B-51935: Error in resolving the content ID reference.

Cause: Failed to resolve the content ID reference.

Action: Make sure that the content ID reference is valid.
Level: 1

Type: ERROR

Impact: Process

B2B-51936: Signed acknowledgement requested, but not configured in delivery channel.

Cause: Signed acknowledgement requested, but not configured in delivery channel.

Action: Make sure that the sign acknowledgement is configured in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52250: Error decoding incoming message at MLLP exchange.

Cause: Message received consists of more than one part or component.

Action: Check the payload to make sure it has only one part/component.
Level: 1

Type: ERROR

Impact: Process

B2B-52251: Error identifying remote trading partner at MLLP exchange with MLLP ID {0}.

Cause: MLLP ID received from in the message header did not exist.

Action: Make sure that the MLLP ID of the remote trading partner is configured as in the trading partner identification section or the anonymous trading partner is configured.
Level: 1

Type: ERROR

Impact: Process

B2B-52252: Only one trading partner in the system can have hosted=true.

Cause: More than one trading partner has hosted=true.

Action: Make sure only one trading partner in the system has hosted=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52253: Trading partner {0} must have trading partner name as one of the identification.

Cause: Trading partner must have trading partner name as one of the identification.

Action: Make sure trading partner has an identification with value as name of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52254: Delivery channel {0} must have exchange protocol, if listening=false.

Cause: Delivery channel did not have exchange protocol.

Action: Make sure delivery channel has exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52255: Certificate alias not specified in the secure delivery channel {0}.

Cause: Security was enabled in delivery channel, but no certificate alias specified.

Action: Make sure certificate alias specified in the delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52256: In delivery channel {0}, Transport protocol {1} is not supported by exchange protocol {2}.

Cause: Specified transport protocol was not supported by exchange protocol.

Action: Choose transport protocol which is supported by exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52257: In delivery channel {0}, algorithm {1} is not supported for exchange protocol {2}.

Cause: Specified algorithm was not supported by exchange protocol.

Action: Choose algorithm which is supported by exchange protocol.
Level: 1

Type: ERROR

Impact: Process

B2B-52258: In delivery channel {0}, exchange protocol parameter {1} is not supported for exchange protocol {2}.

Cause: Selected exchangeProtocolParameter was not part of the specified exchange protocol.

Action: Select specified exchangeProtocol and re-save again in UI.
Level: 1

Type: ERROR

Impact: Process

B2B-52259: In delivery channel {1}, exchange protocol {0} has to have acknowledge mode as ASYNC or NONE.

Cause: RNIF exchange protocol did not support SYNC acknowledge mode.

Action: Verify RNIF exchange protocol has acknowledge mode as ASYNC or NONE.
Level: 1

Type: ERROR

Impact: Process

B2B-52260: effectiveToDate {0} in agreement {1} must be a date in the future.

Cause: Date specified in effectiveToDate was not a future date.

Action: Ensure that the effectiveToDate in the agreement is a date in the future.
Level: 1

Type: ERROR

Impact: Process

B2B-52261: The effectiveFromDate {0} should be less than effectiveToDate {1} in agreement {2}.

Cause: The effectiveFromDate should be less than effectiveToDate.

Action: Make sure the effectiveFromDate is less than effectiveToDate.
Level: 1

Type: ERROR

Impact: Process

B2B-52262: Agreement {0} does not have a host and trading partner.

Cause: Agreement did not have a host and trading partner.

Action: Make sure agreement has a host and trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52263: One of the participants must be a host in an agreement {0}.

Cause: None of the participants was host in agreement.

Action: Make sure a participant in agreement is host.
Level: 1

Type: ERROR

Impact: Process

B2B-52264: Document type name {0} and document protocol version {1} used in agreement {2} are not in sync with the corresponding definition in trading partner {3}.

Cause: Document type name and document protocol version used in agreement were not in sync with the corresponding definition in trading partner.

Action: Make sure agreement has document type name and document type version as given in trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52265: DUNS identification value {0} must be 9 digit.

Cause: DUNS identification was not have value in 9 digit.

Action: Verify DUNS identification has value in 9 digit.
Level: 1

Type: ERROR

Impact: Process

B2B-52266: Identification type {0} and value {1} must be unique in the trading partner.

Cause: Identification type and value occurred more than once in the trading partner.

Action: Make sure type and value of identification unique in the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52267: Only one exchange protocol can have default=true.

Cause: More than one exchange protocol has default=true.

Action: Make sure only one exchange protocol has default=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52268: Only one document protocol can have default=true.

Cause: More than one document protocol has default=true.

Action: Make sure only one document protocol has default=true.
Level: 1

Type: ERROR

Impact: Process

B2B-52269: Participant {0} cannot have more than one identification of the same type {1}.

Cause: Participant has more than one identification of the same type.

Action: Make sure participant is not referring to more than one identification of same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52270: Participant {0} identification reference {1} is not part of same trading partner identification.

Cause: Participant refer to some other trading partner identification.

Action: Make sure identification referred in participant is part of same trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52271: Participant {0} delivery channel reference {1} is not part of same trading partner.

Cause: Participant delivery channel reference was not part of either same trading partner or host.

Action: Make sure delivery channel referred in participant is part of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52272: Participant {0} document definition {1} is not part of same trading partner.

Cause: Participant document definition was not part of same trading partner.

Action: Make sure trading partner has specified document definition.
Level: 1

Type: ERROR

Impact: Process

B2B-52273: Participant {0} identification type {1} and value {2} are not synchronous with trading partner identification.

Cause: Participant identification type and value were not sync with trading partner identification.

Action: Make sure the value and type given in identification reference in participant is synchronous with trading partner identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52274: Participant {0} can have only one exchange identifier.

Cause: Participant has more than one exchange identification.

Action: Make sure only one exchange identification found in participant.
Level: 1

Type: ERROR

Impact: Process

B2B-52275: Type of the parameter {0} must match with the default value {1}.

Cause: Parameter type and default value type mismatched.

Action: Check the type and value of parameter are same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52276: Type of the parameter {0} must match with the value.

Cause: Parameter type and given value mismatched.

Action: Check the type and value of parameter are same type.
Level: 1

Type: ERROR

Impact: Process

B2B-52277: Only Custom document protocol can set custom attribute equal to true.

Cause: Other than custom document protocol has custom attribute set to true.

Action: Make sure only custom document protocol has this attribute set to true.
Level: 1

Type: ERROR

Impact: Process

B2B-52278: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID starts with doc_
Level: 1

Type: ERROR

Impact: Process

B2B-52279: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol reference is in the form of doc_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52280: Trading partner {0} must have at least one exchange identification.

Cause: None of the exchange identification found in trading partner.

Action: Add at least one exchange identification in trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52281: Trading partner {0} must have ID {1} starts with tp_

Cause: Trading partner has ID which did not start with tp_

Action: Make sure trading partner has ID which starts with tp_
Level: 1

Type: ERROR

Impact: Process

B2B-52282: Trading partner {0} reference must be tp_id.xml

Cause: Trading partner reference was not in the form of tp_id.xml

Action: Make sure trading partner has reference in the form of tp_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52283: In delivery channel {0}, certificate alias {1} not found in the keystore.

Cause: Given certificate alias did not exist in the keystore.

Action: Verify certificate alias is present in the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-52284: Delivery channel {0} which has transport protocol {1} cannot be a listening channel.

Cause: Selected transport protocol was not capable of listening

Action: Select listening transport to create listening delivery channel
Level: 1

Type: ERROR

Impact: Process

B2B-52285: Internal delivery channel {0} must use generic exchange.

Cause: Internal delivery channel has other than generic exchange protocol.

Action: Make sure internal delivery channel uses generic exchange.
Level: 1

Type: ERROR

Impact: Process

B2B-52286: HTTP transport protocol must have a URL.

Cause: HTTP transport protocol did not have a URL.

Action: Make sure HTTP transport protocol has a URL.
Level: 1

Type: ERROR

Impact: Process

B2B-52287: Agreement {0} must have ID {1} starts with tpa_

Cause: Agreement has ID which did not start with tpa_

Action: Make sure agreement has ID which starts with tpa_
Level: 1

Type: ERROR

Impact: Process

B2B-52288: Agreement {0} reference must be tpa_id.xml

Cause: Agreement reference was not in the form of tpa_id.xml

Action: Make sure agreement has reference which is in the form of tpa_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52289: Agreement {0} has document definition with mismatching initiator flag.

Cause: Agreement has document definition with mismatching initiator flag in trading partner.

Action: Make sure document definition is supported to send or receive by trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52290: Agreement {0} must have exactly one supported document type.

Cause: Agreement has not exactly one supported document type.

Action: Make sure agreement has only one supported document type.
Level: 1

Type: ERROR

Impact: Process

B2B-52291: Duplicate agreement {0} found with same combination of trading partners {1}, {2}, and document type {3} and document protocol version {4}.

Cause: More than one agreement has same combination of trading partners, document type and version.

Action: Make sure only one agreement has same combination of trading partners, document type and version.
Level: 1

Type: ERROR

Impact: Process

B2B-52292: In agreement {0}, trading partner {1} must have a delivery channel.

Cause: The trading partner did not have delivery channel to send out bound message.

Action: Make sure in a agreement, the trading partner has a delivery channel to send out bound message.
Level: 1

Type: ERROR

Impact: Process

B2B-52293: In agreement {0}, the host {1} can refer to only the internal delivery channel.

Cause: Host refers to other than internal delivery channel.

Action: Make sure host is not referring to other than internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52294: In agreement {0}, participant {1} cannot have more than one delivery channel.

Cause: Participant has more than one delivery channel.

Action: Make sure only one delivery channel exist for participant.
Level: 1

Type: ERROR

Impact: Process

B2B-52295: At least one name identification type present in system.

Cause: Name identification type did not present in system.

Action: Check at least one name identification type present in system.
Level: 1

Type: ERROR

Impact: Process

B2B-52296: Exchange identification {0} must have a value.

Cause: Exchange identification did not have a value.

Action: Make sure all exchange identification has a value.
Level: 1

Type: ERROR

Impact: Process

B2B-52297: Packaging protocol reference {0} must point to packaging protocol element.

Cause: Packaging protocol reference refer to other than packaging protocol element.

Action: Verify packaging protocol reference refers to packaging protocol element.
Level: 1

Type: ERROR

Impact: Process

B2B-52298: Transport URL {0} already used in system.

Cause: More than once same endpoint used in system.

Action: Make sure same endpoint not attached with different delivery channel in system.
Level: 1

Type: ERROR

Impact: Process

B2B-52299: Participant {0} must have at least one exchange identification.

Cause: None of the exchange identification referred in participant.

Action: Make sure participant has at least one exchange identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52300: Duplicate ID {0} found in node {1} and node {2}.

Cause: Duplicate unique ID found in two different nodes.

Action: Target system has element with the same , change ID of importing node.
Level: 1

Type: ERROR

Impact: Process

B2B-52301: MDSReference {0} is not referring to the trading partner.

Cause: MDSReference did not refer to the trading partner.

Action: Make sure given reference is pointing to the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52302: MDSReference {0} is not referring to an agreement.

Cause: MDSReference did not refer to an agreement.

Action: Make sure given reference is pointing to an agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52303: Compressed file expected to import.

Cause: Given file was not compressed using ZIP format.

Action: Verify given file is in compressed in ZIP format.
Level: 1

Type: ERROR

Impact: Process

B2B-52304: Agreement {0} cannot have listening channels.

Cause: Listening channels referred in agreement.

Action: Verify agreement is not referring to any listening channels.
Level: 1

Type: ERROR

Impact: Process

B2B-52305: In agreement {0}, trading partner {1} cannot have internal delivery channel.

Cause: Trading partner has internal delivery channel(s).

Action: Make sure none of the trading partners has internal delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52306: Internal delivery channel {0} must not use HTTP transport.

Cause: Internal delivery channel has HTTP as transport.

Action: Make sure internal delivery channel is not using HTTP transport.
Level: 1

Type: ERROR

Impact: Process

B2B-52307: Listening delivery channel {0} must have a polling interval value.

Cause: Listening channel did not have value for polling interval.

Action: Make sure listening channel has polling interval value.
Level: 1

Type: ERROR

Impact: Process

B2B-52308: Listening delivery channel {0} with transport {1} does not have user name and password.

Cause: Listening delivery channel did not have user name and password in transport.

Action: Make sure listening delivery channel has user name and password in transport.
Level: 1

Type: ERROR

Impact: Process

B2B-52309: Validation error: see the diagnostic log for more details.

Cause: Unknown exception found in validation engine.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52310: The XML {0} is not well-formed.

Cause: Given XML content was not well-formed.

Action: Check XML content is well-formed and valid based on XSD/DTD constraints.
Level: 1

Type: ERROR

Impact: Process

B2B-52311: New document protocol {0} found in source reference {1}.

Cause: New document protocol name found in import source.

Action: Check name of the document protocol is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-52312: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID which starts with doc_
Level: 1

Type: ERROR

Impact: Process

B2B-52313: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol has reference in the form of doc_id.xml
Level: 1

Type: ERROR

Impact: Process

B2B-52314: Repository host name {0} and source Host name {1} are different.

Cause: Different host name found in repository and source.

Action: Make host name as unique in source and target system, while doing import.
Level: 1

Type: ERROR

Impact: Process

B2B-52315: Duplicate identification type {1} and value {2} found in source trading partner {0}.

Cause: More than one identification type found in source trading partner(s) for a same value and type.

Action: Make sure combination of identification type and value unique in the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52316: Pre-import transfer operation failed.

Cause: Pre-import validation(s) failed while importing.

Action: Check validation error messages found below this message and correct source files accordingly.
Level: 1

Type: ERROR

Impact: Process

B2B-52317: Duplicate identification type {1} and value {2} found in source agreement {0}.

Cause: More than one identification type found in source agreement(s) for a same value and type.

Action: Make sure combination of identification type and value unique in agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52318: MDSReference {0} does not exist in Repository.

Cause: Specified reference was not available in repository.

Action: Make sure specified reference is available in repository.
Level: 1

Type: WARNING

Impact: Process

B2B-52319: Transfer error: see log for more details.

Cause: Unknown exception identified in transfer.

Action: Check the diagnostic log. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52320: In agreement {0}, functional acknowledge can be enabled only when translate=true.

Cause: Agreement has functional acknowledge with translate flag set to inactive.

Action: Functional acknowledge can be active only when translate is active.
Level: 1

Type: ERROR

Impact: Process

B2B-52321: No metadata found to import.

Cause: No metadata identified in recommended package.

Action: Check given import file has metadata in correct package.
Level: 1

Type: ERROR

Impact: Process

B2B-52322: Mandatory field {0} is missing in {1}.

Cause: Metadata might be imported without all mandatory fields.

Action: Import metadata with all mandatory fields or save again the business object which has error, using UI.
Level: 1

Type: ERROR

Impact: Process

B2B-52323: Out-bound agreement {0} has to have only one exchange identifier type - {1}, in both participants

Cause: Out-bound agreement has more than one exchange identifier, or has different type of exchange identifier which is not suitable to exchange protocol.

Action: Make sure given exchange identifier is supported by chosen exchange protocol in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-52324: Listening Delivery channel {0} has duplicate endpoint {1}

Cause: Already a delivery channel has same endpoint, hence new delivery channel cannot be activated with same endpoint.

Action: Make sure all listening channel endpoints are unique.
Level: 1

Type: ERROR

Impact: Backup and Recovery

B2B-52325: Error in the SOA Composite {0}

Cause: See the base error message in the SOA Composite.

Action: Correct the error in the Fabric Composite.
Level: 1

Type: ERROR

Impact: Process

B2B-52326: Transport protocol with HTTPs URL has to have valid keystore location and password in host

Cause: Valid keystore location and password was not specified in host.

Action: Check with administrator, whether valid keystore location specified in host.
Level: 1

Type: ERROR

Impact: Process

B2B-52327: Channel {0} with transport {1} should have Queue name along with either datasource or the combination of SID, port number, user name, host name and password.

Cause: AQ channel does not have required parameter values to connect to AQ queue.

Action: Provide AQ Queue name along with either datasource or the combination of SID, port number, user name, host name and password.
Level: 1

Type: ERROR

Impact: Process

B2B-52328: Channel {0} with transport {1} should have either password or the combination of private key file and pass phrase.

Cause: SFTP channel does not have required parameter values to connect to SFTP server.

Action: Provide either password or the combination of private key file and pass phrase.
Level: 1

Type: ERROR

Impact: Process

B2B-52329: Web Service outbound flow invocation error.

Cause: An abnormal condition occurred during outbound flow invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52330: Error invoking translation Web Service.

Cause: An abnormal condition occurred during translation Web Service invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52331: Translated content is not available

Cause: B2B metadata or XEngine configuration was invalid.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52332: Message is discarded and moved to error state with message id {0}

Cause: Message is discarded and moved to a error state based on a user input.

Action: Resubmit the message
Level: 3

Type: ERROR

Impact: Process

B2B-52333: received data from trading partner is too long

Cause: received data from trading partner is too long.

Action: resend hllp message where payload length should be less than or equal to 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52334: checksum validation failed

Cause: checksum validation failed for received data.

Action: resend hllp message with correct checksum value.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52335: payload length is incorrect in received hllp packed message.

Cause: payload length is incorrect in received hllp packed message.

Action: resend hllp message with correct payload length.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52336: validation of received hllp message failed

Cause: validation of received hllp message failed

Action: resend hllp message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52337: payload length is too large(>99994 bytes) at client side

Cause: payload length is too large(>99994 bytes) at client side

Action: resend hllp message with payload length less than or equal to 99994 bytes.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52338: Negative Ack Received from trading partner.

Cause: received negative ack from trading partner

Action: resend hllp message
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52339: Large Payload directory is inaccessible

Cause: Specified directory for large payload is inaccessible

Action: Ensure specified directory for large payload exists and it is write enabled
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52340: Un-delivered Sequenced Message has been resubmitted. Moved to ERROR state

Cause: Un-delivered Sequenced Message has been resubmitted. Moved to error state

Action: N/A
Level: 3

Type: ERROR

Impact: Process

B2B-52341: Interface Sequence Message discarded. Message id {0}. Dependent Outbound Rows discarded {1}

Cause: Interface Sequence Message discarded.

Action: N/A
Level: 3

Type: ERROR

Impact: Process

B2B-53001: Handler is null while registering a Webservice End point

Cause: The handler is null when registering an endpoint.

Action: Provide a valid handler implementation while registering an endpoint. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53002: Unable to find a registered handler for this end point.

Cause: Unable to process the message due to handler identification failure.

Action: Re-register a valid handler for the end point. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53003: Unable to register an endpoint.

Cause: Registration of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53004: Unable to remove a registered end point

Cause: Removal of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53005: Unable to package the payload to a SOAP message

Cause: Packing the payload into a message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53006: Unable to retrieve the payload from the SOAP message

Cause: Unpacking the soap message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53007: No payload component found in the message

Cause: No payload component found in the message

Action: Provide a payload component when enqueuing the message. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53008: Unable to create the SOAP Protocol components

Cause: Unable to create the SOAP Protocol components

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53009: Unable to decode the soap message

Cause: Unable to decode the soap message

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53010: An exception occurred while processing the received message.

Cause: Unable to process the SOAP message received in the transport layer.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53011: Duplicate message with same message id found in a batch. Changing original message id {0} to new message id {1} and rejecting the message.

Cause: Duplicate message with same message id found in a batch.

Action: Make sure that duplicate messages with same message id are not passed in the same batch.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53012: Invalid argument found. Name or identificationType is null.

Cause: Invalid argument found. Name or identificationType is null

Action: Make sure that name of trading partner and identificationType is passed correctly.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53013: Unable to evaluate Payload XPath Expression

Cause: Provided XPath Expression can not be evaluated.

Action: Make sure that configured XPath Expression to extract Payload is correct.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53014: No payload or XPath not able to retrieve the payload

Cause: No payload or wrong XPath.

Action: Check the Payload and XPath
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53015: Unable to find specified security provider

Cause: Security Provider was not found in the environment.

Action: Verify provider.
Level: 1

Type: ERROR

Impact: Process

B2B-53016: Specified algorithm is not available from the specified provider

Cause: Algorithm was not available from the provider.

Action: Verify algorithm and provider .
Level: 1

Type: ERROR

Impact: Process

B2B-53017: Private key can not be recovered

Cause: Private key could not be recovered.

Action: Check the keystore and private key password.
Level: 1

Type: ERROR

Impact: Process

B2B-53018: KeysStore usage failure

Cause: Problem found in Keystore resource usage.

Action: Check the keystore.
Level: 1

Type: ERROR

Impact: Process

B2B-53019: Transport layer security context initialization failure

Cause: SSLContext was not getting initialized.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists
Level: 1

Type: ERROR

Impact: Process

10 BEA-000001 to BEA-2163006

BEA-000001: Server must be started by Node Manager when consensus leasing is enabled.

Cause: The server was not started by Node Manager.

Action: Start the server using Node Manager.
Level: 1

Type: INTERNAL_ERROR

Impact: ConsensusLeasing

BEA-000002: Failed to initialize a Coherence cluster due to {0}

Cause: Failed to initialize a Coherence cluster due to {0}

Action: Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: weblogic-coherence-integration

BEA-000003: Shutting down a Coherence cluster scoped to classloader {0}

Cause: Shutting down a Coherence cluster scoped to classloader {0}

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: weblogic-coherence-integration

BEA-000004: Failed to shut down a Coherence cluster due to {0}

Cause: Failed to shut down a Coherence cluster due to {0}

Action: Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: weblogic-coherence-integration

BEA-000005: Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server.

Cause: Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server.

Action: Create a CoherenceClusterSystemResourceMBean appropriately and associate it with the server, or the cluster of which this server is a member.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000006: Server {0} is configured with 'localhost' as the Unicast Listen Address. A generated Coherence WKA list will not operate correctly across multiple machines. This will result in an error if Coherence is run in Production mode.

Cause: Server {0} is configured with 'localhost' as the Unicast Listen Address. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines. This will result in an error if Coherence is run in Production mode.

Action: Explicitly define a Well Known Address (WKA) list for the Coherence cluster.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000007: Could not find the JNDI resource [{0}] referenced by {1}.

Cause: The JNDI resource [{0}] referenced by {1} could not be found.

Action: Define the JNDI resource [{0}] referenced by {1}.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000008: The Coherence cluster service failed to start or failed to join cluster due to {0} using {1}.

Cause: The Coherence cluster service failed to start or failed to join cluster due to {0} using {1}.

Action: Review the Coherence configuration for the cause of the exception.
Level: 1

Type: ERROR

Impact: weblogic-coherence-integration

BEA-000009: Coherence configuration failed due to {0} using {1}.

Cause: The Coherence configuration failed due to {0} using {1}.

Action: Review the Coherence configuration for the cause of the exception.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000010: The WeblogicCoherenceBean and CoherenceClusterParamsBean are not defined for the CoherenceClusterSystemResourceMBean {0}.

Cause: The CohererenceClusterSystemResourceBean {0} needs to have an association with valid WeblogicCoherence and CoherenceCluster Beans.

Action: Create a CoherenceClusterSystemResource MBean with the required associations.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000011: While configuring the Coherence Cluster Service, the Server MBean or Server CoherenceMemberConfig MBean or both were not defined.

Cause: The Server MBean or Server CoherenceMemberConfig MBean or both were not defined and thus will not be used when configuring the Coherence Cluster Service.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: weblogic-coherence-integration

BEA-000012: Server {0} is configured with 'localhost' as the Unicast Listen Address which is an error in Coherence Production mode. A generated Coherence WKA list will not operate correctly across multiple machines.

Cause: Server {0} is configured with 'localhost' as the Unicast Listen Address resulting in an error when Coherence is in Production mode. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines.

Action: Explicitly define a Well Known Address (WKA) list for the Coherence cluster.
Level: 1

Type: ERROR

Impact: weblogic-coherence-integration

BEA-000013: While undeploying a GAR, the deployment module received an exception when closing files {0}.

Cause: While undeploying a GAR, one or more files could not be closed due to {0}.

Action: Review the exception and determine if there any file system issues for the referenced files.
Level: 1

Type: WARNING

Impact: weblogic-coherence-integration

BEA-000101: Cannot resolve ClusterAddress: {0}

Cause: The cluster address {0} could not be resolved. ClusterAddress should be a DNS name that maps to multiple IP addresses.

Action: Set the correct ClusterAddress property for the cluster.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000102: Joining cluster {0} on {1}:{2}

Cause: The server has joined cluster {0}.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000103: Disconnecting from cluster {0}

Cause: When a server is suspended, it is no longer a member of cluster {0}.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000104: Cluster members are running incompatible versions. Local version: {0}. Remote version ({1}): {2}

Cause: This server is a different version than other servers in this cluster.

Action: Ensure that all members of this cluster are running the same version.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000105: The server is leaving the cluster because it is an incompatible version.

Cause: This server is running a different version of WebLogic Server.

Action: Set a different multicast address for this cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000107: Failed to install {0} in place of those currently installed due to {1}.

Cause: An error occurred while resolving non-local conflicting offers for a node in the JNDI tree.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000108: Attempt to retract offer {0}, which is neither installed nor pending.

Cause: An attempt was made to retract an offer, which was neither previously installed nor is in the conflict resolution stage.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000109: An error occurred while sending multicast message: {0}.

Cause: An error occurred while trying to send a message over multicast.

Action: WebLogic Server will try to recover from this error. If the problem continues to persist, make sure that the network infrastructure and NIC are functioning properly. If you believe no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000110: Multicast socket receive error: {0}.

Cause: An error occurred while trying to receive a message over the multicast.

Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000111: Adding {0} with ID {2} to cluster: {1} view.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000112: Removing {0} from cluster view due to timeout.

Cause: Removing {0} from cluster as it failed to send heartbeats over the multicast in the past 30 seconds.

Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000113: Removing {0} from cluster view due to PeerGone.

Cause: The TCP/IP connection to server {0} was lost.

Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000114: Failed to find cluster license: {0}

Cause: A valid license file is required to run clusters.

Action: Contact an Oracle sales representative for a valid license.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000115: Lost {0} multicast message(s).

Cause: This is an informational message. When a server joins a stable cluster, this message will appear since multicast messages sent out by servers in the cluster were not received.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000116: Failed to join cluster {0} at address {1} due to: {2}.

Cause: This happens if you specify an incorrect multicast address for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.

Action: Set a valid multicast address and try again.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000117: Received a stale replication request for object {0}.

Cause: This happens when a network problem exists, or one of the servers is taking a long time to collect garbage, causing the virtual machine to freeze.

Action: Tune garbage collection so that it does not pause. If the problem still persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000118: Lost {0} replication updates of object {1}.

Cause: If the secondary failed to receive some of the updates, it indicates this to the primary server by causing a NotFoundException to the primary so that the primary server can recreate the session state.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000119: Missing multicast address for cluster: {0}. Set the MulticastAddress="a.b.c.d" property for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.

Cause: The cluster does not have a defined multicast address.

Action: Specify a valid multicast address.
Level: 1

Type: INTERNAL_ERROR

Impact: Cluster

BEA-000120: Received error while creating ClusterRuntimeMBean.

Cause: The JMX framework failed to initialize the ClusterRuntimeMBean.

Action: Check the cluster configuration. If it appears that there are no configuration problems, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000121: Two domains in the same LAN should not use the same multicast address. Domains in conflict are {0} and {1}.

Cause: Two clusters on the local area network are using the same multicast address.

Action: Change the multicast address of either domain {0} or {1}.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000122: Clusters {0} and {1} cannot use the same multicast address.

Cause: Multiple clusters in the same domain are using the same multicast address.

Action: For efficiency purposes, use two different multicast addresses.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000123: Conflict start: You tried to bind an object under the name {0} in the JNDI tree. The object {1} is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.

Cause: The cluster is not homogeneous. Two servers in the cluster are providing different services under the same name {0}. If the object is non-clusterable, only one server in the cluster can provide this service.

Action: There are various options. 1. Make the object clusterable. 2. Change the JNDI name of the object under which it is bound. 3. Make sure the object gets deployed only on one server. 4. Deploy the service on all the servers. However, binding it into the JNDI tree, set the replicate bindings property to false.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000124: Conflict start: The object {1} you tried to bind under the name {0} in the JNDI tree is clusterable but is incompatible. Ensure that all the servers in the cluster use an identical copy of the object.

Cause: The object {1} is clusterable. However, it implements different or incompatible interfaces on different servers.

Action: Ensure that all the servers in the cluster use an identical copy of the object.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000125: Conflict resolved: {0} for the object {1} under the bind name {0} in the JNDI tree.

Cause: Corrective action was taken to resolve the conflict.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000126: All session objects should be serializable to replicate. Check the objects in the session. Failed to replicate a non-serializable object.

Cause: Objects in the session are not serializable or externalizable.

Action: Ensure that all user-defined objects in the HTTP session are serializable.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000127: Adding {0} to the cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000128: Updating {0} in the cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000129: Removing {0} from the cluster.

Cause: This is an informational message.

Action: No action is required unless you did not shut down a server.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000133: Waiting to synchronize with other running members of {0}.

Cause: The cluster member is waiting to synchronize cluster information with other cluster members before completing startup and entering running mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000137: Error sending multicast message: {0}.

Cause: The multicast message failed to send due to an IOException.

Action: Enable cluster debugging to see a detailed message.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000138: Listening for announcements from cluster {0} on {1}:{2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000139: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.

Cause: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.

Action: Change either the multicast address or the multicast port.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000140: Failed to deserialize statedump from server {0} with {1}.

Cause: The server failed to deserialize an object since it does not have the class definition. This usually happens if the application classes are not deployed on all the nodes in the cluster. It is preferable to deploy beans to all the nodes of the cluster.

Action: Ensure that all the classes are available on all the nodes of the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000141: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}.

Cause: An IOException occurred in the operating system.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000142: Trying to download cluster JNDI tree from server {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000143: Trying to download JNDI tree from a server listening on {0}.

Cause: This is an informational message.

Action: If this message continues to appear, ensure that the network is stable. Contact My Oracle Support for further assistance.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000144: Managed Server {0} has been suspended or shut down.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000145: Managed Server {0} is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC data source to ensure that the migratable server is highly available.

Cause: The cluster is misconfigured.

Action: Configure the DataSourceForAutomaticMigration property.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000147: Server "{0}" failed to renew lease in the {1}.

Cause: The server failed to renew the lease on time.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000148: Migratable server "{0}" is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should have at least a couple of machines assigned to it for automatic migration.

Cause: The migratable server is misconfigured.

Action: Ensure that the server is targeted to a machine and restart the migratable server.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000149: Server failed to get a connection to the {1} during {0}.

Cause: The database or the consensus leasing basis appears to be down.

Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis the server is in the minority partition and the leasing basis is in some other partition that is not reachable.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000150: Server failed to get a connection to the {1} in the past {0} seconds for lease renewal. Or, Server could get a connection but failed to renew the lease. Server will shut itself down.

Cause: The database or consensus leasing basis appears to be down.

Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis, the server is in the minority partition and the leasing basis is in some other partition that is not reachable. If this message continues to appear even when the database is accessible, something may be wrong in the database. Contact My Oracle Support for further assistance.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000151: Server "{0}" has taken over the role of Cluster Master.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000152: Server "{0}" lost the privileges to be the Cluster Master.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000153: Cluster is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should at least have a couple of machines assigned to it for automatic migration.

Cause: The cluster is misconfigured.

Action: Assign a pool of machines for automatic migration and refer to WebLogic Server documentation for more details.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000154: Cluster is misconfigured. The remote cluster address {0} is not a valid URL.

Cause: The server is misconfigured.

Action: Set the correct remote cluster address and restart the servers. If it is not clear on how to set remote ClusterAddress, refer to WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000155: Configured cluster address is invalid : {0}. Constructing cluster address dynamically.

Cause: The cluster configuration is invalid.

Action: Ensure that the cluster address contains either a DNS name or a comma-separated host list (or IP list) or a comma-separated host:port list (or IP:port list).
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000156: Could not send out new attributes for cluster member {0}: {1}.

Cause: There was a problem sending out changed member attributes.

Action: Examine the server logs.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000158: Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.

Cause: The server is going out of the cluster as a result of the suspend or shutdown operation.

Action: No action is required
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000159: The clocks of the machines hosting local server and remote server "{0}" are off by {1} seconds

Cause: The clocks of the machines hosting servers in the cluster are not synchronized.

Action: Ensure that all the machines are synchronized to the same time.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000160: A request to synchronize the JNDI tree has been made over an insecure channel. Configure a secure HTTP channel for all of the servers in the cluster.

Cause: The cluster was configured to encrypt multicast data but the request to synchronize the JNDI tree was done on a non-secure channel (HTTP). To secure the cluster completely, configure a secure HTTP channel for all of the servers in the cluster.

Action: Configure a secure HTTP channel on all of the servers in the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000161: Multicast message from server {0} appears to have been tampered with.

Cause: The authenticity of the message could not be verified.

Action: Ensure that the network is not being hijacked.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000162: Starting "{0}" replication service with remote cluster address "{1}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000163: Stopping "{0}" replication service

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000164: Synchronized cluster JNDI tree from server {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000165: Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in {0}. Two domains in the same LAN should not use the same multicast address.

Cause: Two clusters on the local area network are using the same multicast address.

Action: Change the multicast address of either domain.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000166: Some other cluster in this domain is configured to use the same multicast address as {0}. Clusters cannot use the same multicast address.

Cause: Multiple clusters in the same domain are using the same multicast address.

Action: For efficiency purposes, use two different multicast addresses.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000167: Some services failed to roll back successfully when trying to abort the migration: {0}.

Cause: An exception caused the rollback to fail: {0}.

Action: It would be safest to shut down this server so that any lingering services will stop. They will not be automatically restarted upon reboot. Once the cause of the rollback has been fixed, attempts to migrate to this server should be successful.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000168: Failed to restart/migrate server "{0}" because of {1}

Cause: There was an error while restarting migratable server: {1}

Action: Examine the server logs.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000170: The server {0} did not receive the multicast packets that it sent.

Cause: Each WebLogic Server instanec is expected to receive the messages it multicast to its multicast group. Since the server does not receive its own messages, the multicast address configuration in the cluster configuration or the interface address specification may be wrong.

Action: Ensure that the cluster configuration and server interface configuration are valid
Level: 1

Type: ERROR

Impact: Cluster

BEA-000171: Failed to load the custom Singleton Services SQL Query Helper: {0}, because of {1}.

Cause: The most likely cause for failing to load the named class is either a typo in the name of the class or that the class is missing from the server classpath.

Action: Ensure that the provided classname is valid and that the class exists in the classpath of the server.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000172: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}. Error message received: {2}. The request was generated by {3}. {1}

Cause: An IOException occurred in the operating system.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000176: {0} does not specify a machine.

Cause: {0}'s configuration does not specify the machine on which it is running. Machines must be specified if scripts are to be executed when migrations happen.

Action: Specify the machine on which {0} is running in the server's console page.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000178: Failed to execute {0} because of {1}.

Cause: While trying to run {0}, an exception occurred: {1}.

Action: Check that the script, {0}, is fully debugged. It may help to run the script by hand to see if any errors are raised.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000179: {0} failed while altering its lease.

Cause: An exception occurred: {1}.

Action: Ensure that, if a database is being used for leasing, it is available.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000180: Unable to retrieve Job {0} from the database. The retrieval failed with {1}

Cause: An error occurred while reading a job from the database.

Action: ENsure that the classes corresponding to the job are present in the server classpath and are of the correct version.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000182: Job Scheduler created a job with ID {0} for TimerListener with description {1}

Cause: Job Scheduler created an entry in the database for a submitted job.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000183: Successfully cancelled job with ID {0}

Cause: Job Scheduler removed a job entry from the database based on application request

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000184: This server did not attempt to renew its lease for {0} seconds. The server may need to be restarted or migrated.

Cause: The thread that is supposed to regularly renew the lease has become blocked for some reason.

Action: Ensure that the server is not overloaded with work and that there are enough system resources available on the machine.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000185: Despite the delay in the lease-renewing thread, the server has successfully renewed its lease. It is no longer in imminent risk of being migrated or restarted.

Cause: The thread that is supposed to regularly renew the lease became blocked, but is running properly again and has successfully renewed the lease.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000186: An error was encountered while migrating {0}: {1}

Cause: See the error in the message body.

Action: Ensure that there are enough candidate servers running in the cluster.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000187: The Singleton Service {0} is now registered on this server. This server may be chosen to host this service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000188: The Singleton Service {0} is no longer registered on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000189: The Singleton Service {0} is now active on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000190: The Singleton Service {0} has been deactivated on this server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000191: Now monitoring the Migratable Server {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000192: A running server was not found to host {0}. The server will retry in a few seconds.

Cause: All running servers failed when asked to activate {0}.

Action: Ensure that there is at least one active candidate server for this service and that there is no bug in the activate() method. The service will be tried on all running servers in another few seconds.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000193: The JTA service for {0} has failed, but {0} is still running. JTA cannot be migrated from a running server.

Cause: The JTA service failed.

Action: Check the logs of {0}; {0} should be restarted once the cause of the error has been determined and fixed. Upon restart, the JTA service will be migrated and running transactions recovered.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000194: An error was encountered while trying to report a migration event: {0}.

Cause: The most likely cause is the Administration Server being unavailable. If this is intended, this message can be ignored.

Action: If monitoring information is desired, the Administration Server should be running and reachable.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000195: An error was encountered while trying to save a migration event. The error was: {0}.

Cause: An internal error occurred while trying to create a runtime MBean to encapsulate this data.

Action: Contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000196: Received data about a migration of type {0}, but no such type is recognized by the Administration Server.

Cause: If the Managed Servers have been upgraded to a newer version of WebLogic Server, they may be reporting data that the Administration Server does not know how to handle.

Action: Upgrade the Administration Server to the same version as the cluster members.
Level: 1

Type: WARNING

Impact: Cluster

BEA-000197: Listening for announcements from cluster using unicast cluster messaging

Cause: Unicast cluster messaging mode is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000198: All replication calls for cluster {0} must be made over channel {1}

Cause: All replication calls for cluster {0} must be made over channel {1}

Action: Check the configured channel for replication calls.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000199: Replication calls can only be made by {0} over {1} channel

Cause: Replication calls can only be made by {0} over {1} channel

Action: Check the roles of the users for whom the replication calls are being made.
Level: 1

Type: ERROR

Impact: Cluster

BEA-000214: WebLogic Server "{1}" version: {0} Copyright (c) 1995,2014, Oracle and/or its affiliates. All rights reserved.

Cause: The startup banner used when a server starts.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000215: Loaded license: {0}.

Cause: This prints from the location from which the license file was loaded.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000220: Cannot shut down the server because the request was from a null user (Principal).

Cause: The server refused to shut down since the command came from an unauthorized user.

Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000221: Cannot shut down the server because the request was from a nameless user (Principal).

Cause: The server refused to shut down since the command came from an unauthorized user.

Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000222: Cannot disable server logins because the request was from a null user (Principal).

Cause: The server refused to lock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000223: Cannot disable server logins because the request was from a nameless user (Principal).

Cause: The server refused to lock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000224: Cannot enable server logins because the request was from a null user (Principal).

Cause: The server refused to unlock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000225: Cannot enable server logins because the request was from a nameless user (Principal).

Cause: The server refused to unlock itself since the command came from an unauthorized user.

Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000226: The enabling of server logins has been requested by {0}.

Cause: The server has been requested to unlock itself and enable server logins again.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000227: Server logins have been enabled.

Cause: Server logins have been enabled.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000228: The disabling of server logins has been requested by {0}.

Cause: A LOCK command was issued by an administrator.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000229: Server logins have been disabled.

Cause: A LOCK command was issued by an administrator.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000231: Waiting {0} seconds for server shutdown.

Cause: A shutdown command was issued with a wait time. The server will wait the specified number of seconds before starting shutdown.

Action: A cancel shutdown command can be issued during the wait time to cancel the shutdown process. Otherwise no action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000232: Server shutdown is commencing now and is irreversible.

Cause: A shutdown command was issued by an administrator.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000236: Stopping execute threads.

Cause: An administrator issued a shutdown command.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000238: Shutdown has completed.

Cause: Shutdown has completed.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000240: Cannot cancel the server shutdown because the request was from a null user (Principal).

Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.

Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000241: Cannot cancel the server shutdown because the request was from a nameless user (Principal).

Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.

Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000242: Cannot cancel server shutdown because there is no shutdown in progress.

Cause: The server shutdown cannot be canceled as the server is not in the state 'Shutdown in Progress'.

Action: No action is needed. Check the Administration Console for the state of the server.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000243: It is too late to cancel the server shutdown because the shutdown is already in progress.

Cause: The server has already started to shut down. It is too late to cancel shutdown at this point.

Action: No action is needed.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000244: Canceling server shutdown.

Cause: An administrator has issued a cancel shutdown operation.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000246: Server shutdown has been canceled and logins are enabled.

Cause: The cancel shutdown operation was successful.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000248: An exception occurred while trying to find a localized T3Srvr message, message ID {0}, {1}

Cause: The localized version of the message could not be found.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000249: Because the weblogic.ConsoleInputEnabled property is set to true, the server can only be shut down from the command line. Type the command "shut" in the window in which the server was started.

Cause: The weblogic.ConsoleInputEnabled property was set true on the server startup command line.

Action: To shut down the server, type the command "shut" in the window in which the server was started.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000251: The server switched to the group "{0}".

Cause: A non-privileged group was specifed. The server switched to the specified group after starting.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000252: Cannot switch to the group "{0}". {1}

Cause: The server was unable to switch to the specified group.

Action: Ensure that the specified group exists.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000253: Switched to the user "{0}".

Cause: A non-privileged user was specified. The server switched to the specified user after starting.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000254: Cannot switch to the user "{0}". {1}

Cause: The server could not switch to the specified non-privileged user.

Action: Ensure that the specified user exists.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000256: Invoking {0}.main({1})

Cause: The server configuration specifies startup and shutdown classes to run.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000257: Exception reading command: {0}

Cause: An exception occurred while reading commands from the shell window.

Action: Disable the shell command input property weblogic.ConsoleInputEnabled.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000258: Command [{0}]

Cause: The Administration Console received the specified command and is about to execute it.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000259: Administration Console: profiling enabled.

Cause: Profiling has been enabled in the Administration Console.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000260: Administration Console: profiling disabled.

Cause: Profiling has been disabled in the Administration Console.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000261: The system user is not permitted to shut down, {0}.

Cause: The server was not shut down because the user is not authorized to shut down the server.

Action: See the exception text in {0} for more information on diagnosing the problem. See the previous log messages for more information on authorization failure. If the user does not have permission to shut down the server, but should, use the Administration Console to define a policy for this server that allows the user to shut down.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000262: No such command: {0}.

Cause: The unknown command was entered.

Action: Refer to the list of known commands.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000263: GC: before free/total={0}/{1} ({2}%).

Cause: The GS statistics are shown before forcing GC.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000264: GC: after free/total={0}/{1} ({2}%).

Cause: The GS statistics are shown after forcing GC.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000265: Attempt to unbind ClientContext "{0}" that is not bound.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000266: {0} has {1,choice,1#one pending ExecuteRequest|2#{1,number} pending ExecuteRequests}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000267: {0} had a negative workQueueDepth of {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000268: Failed to send unsolicted message "{0}" to client, {1}

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000269: The connection to the client using "{0}" has been unexpectedly lost due to {1}. The server is initiating a hard disconnect.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000270: Timing out "{0}" because it was idle.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000271: Ignoring a repeated request to schedule the death of "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000272: Scheduling the death of "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000273: Removing "{0}" because of hard disconnect timeout.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000274: Removing "{0}" because of soft disconnect timeout.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000275: Soft disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000276: Hard disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000277: Idle disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000283: Failed to marshal response, {0}

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000284: Unexpected failure to marshal response, {0}

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000286: Failed to invoke startup class "{0}", {1}.

Cause: An exception occurred in a startup class.

Action: Determine the error in the startup class code and restart the server. To work around the problem, set the "abort on startup failure" property to false.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000287: Invoking startup class: {0}.startup({1}).

Cause: The startup class was invoked with the specified arguments.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000288: {0} reports: {1}.

Cause: The return value of the startup class was logged.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000289: Failed to invoke shutdown class "{0}", {1}.

Cause: An exception occurred in a shutdown class.

Action: Determine the error in the shutdown class code and restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000290: Invoking shutdown class: {0}.shutdown({1}).

Cause: The server is invoking shutdown classes as a part of shutdown.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000291: {0} reports: {1}.

Cause: The server logs the return value of the shutdown class.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000297: Inconsistent security configuration, {0}

Cause: An exception occurred in SSL initialization.

Action: Look at the exception in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000298: Certificate expires in {0} days: {1}

Cause: The certificate is about to expire.

Action: Obtain a new server certificate or trusted CA certificate before it expires.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000306: Cannot use SSL because no certificates have been specified in the WebLogic Server configuration.

Cause: No certificates can be found for use by SSL.

Action: If using a keystore for the server certificate, set the ServerPrivateKeyAlias in the SSL MBean. If using the Server Certificate File, ensure that valid certificates are contained within the file.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000307: Exportable key maximum lifespan set to {0} uses.

Cause: The server logs the exportable key maximum lifespan so it is clear what lifespan is being used.

Action: Verify that the lifespan is the desired value.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000314: The execution class "{0}" did not retrieve a T3Executable or T3ExecutableLazy.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000315: Unexpected failure of T3ExecutableLazy, {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000316: enableWatchDog() is not permitted from within a server.

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000317: disableWatchDog() is not permitted from within a server.

Cause: Deprecated functionality

Action: Deprecated functionality
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000320: Error creating runtime MBean for execute queue {0}.

Cause: An internal system error occurred.

Action: Contact My Oracle Support with the server logs.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000329: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in production mode.

Cause: The production mode of the server is enabled.

Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000330: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in production mode.

Cause: The production mode of the server is enabled.

Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script file to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000331: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in development mode.

Cause: The production mode of the server is disabled (default).

Action: Set the weblogic.ProductionModeEnabled property of the domain in the configuration script to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000332: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in development mode.

Cause: The production mode of the server is disabled (default).

Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000333: Queue usage is greater than QueueLengthThresholdPercent "{0}%" of the maximum queue size. An attempt will be made to allocate ThreadsIncrease "{1}" thread(s) to help.

Cause: The server is under high load.

Action: Review the execute queue settings.
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000337: {0} has been busy for "{1}" seconds working on the request "{2}", which is more than the configured time (StuckThreadMaxTime) of "{3}" seconds in "{4}". Stack trace: {5}

Cause: The server is extremely busy or the thread is hung.

Action: Monitor the method that the hung thread is running. Use the Administration Console monitor execute request feature or take a thread dump (weblogic.Admin THREAD_DUMP).
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000339: {0} has become "unstuck".

Cause: A thread previously stuck is now available.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000342: Unable to initialize the server: {0}.

Cause: An exception occurred during the server initialization.

Action: Analyze the weblogic.log file to determine why the server did not initialize completely.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000343: The health monitor for "{0}" failed to register because of exception "{1}".

Cause: Refer to the exception printed in the log message.

Action: Refer to the exception printed in the log message.
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000344: The health monitor for "{0}" failed to unregister because of exception "{1}".

Cause: Refer to the exception printed in the log message.

Action: Refer to the exception printed in the log message.
Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000357: Started WebLogic Server independent Managed Server "{0}" for domain "{1}" running in development mode.

Cause: The server started with the Managed Server independence mode enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000358: Started WebLogic Server independent Managed Server "{0}" for the domain "{1}" running in production mode.

Cause: The production mode of the server is enabled.

Action: Set the ProductionModeEnabled property of the domain in the configuration file to change the server mode.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000360: The server started in {0} mode.

Cause: The startup mode was set to SUSPENDED.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000362: Server failed. Reason: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000365: Server state changed to {0}.

Cause: The server progressed through the startup or shutdown sequence.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000366: The server failed to shut down. Exception: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000371: An error occurred during server shutdown: {0}.

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000374: Waiting for ExecuteQueue {0} to finish {1} pending requests.

Cause: The server found pending requests in one of the execute queues while suspending. The server will wait for the requests to complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000377: Starting WebLogic Server with {0} Version {1} from {2}.

Cause: The server is starting.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000378: The server failed to shut down within the configured timeout of {0} seconds. The server process will now exit.

Cause: Forced shutdown is taking too long to complete.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000381: ServerLifeCycle operation failed. Message: {0} {1}

Cause: A server operation, such as shutdown, failed.

Action: If the error is not application related, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000382: A critical service failed. The server will automatically transition to the ADMIN state.

Cause: A server lifecycle operation or a critical service failed.

Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000383: A critical service failed. The server will shut itself down.

Cause: A critical service failed.

Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000384: A fatal configuration failure occurred during startup. Check if the config.xml file contains invalid entries. Reason: {0}

Cause: The server failed to start due to invalid configuration.

Action: Check if the config.xml file contains invalid entries. Contact My Oracle Support for more information.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000385: Server health failed. Reason: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000386: Server subsystem failed. Reason: {0}

Cause: Inspect the log file for indications of the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000388: JVM called the WebLogic Server shutdown hook. The server will force shutdown now.

Cause: The JVM called the WebLogic Server shutdown hook. The server will force shutdown now.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000394: Deadlock detected: {0}.

Cause: There are threads deadlocked in the server.

Action: Report this error to My Oracle Support if the deadlock involves WebLogic Server internal code.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000395: The following extensions directory contents added to the end of the classpath: {0}.

Cause: Extensions directory contents were added to the classpath.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000396: Server {0} has been requested by {1}.

Cause: A request was made to perform the specified server operation.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000398: WebLogic Server "{0}" for domain "{1}" is running with class caching enabled in production mode. Class caching is not supported in production mode. Disable class caching by setting CLASS_CACHE to "false" in the startWeblogic script and then restarting the server.

Cause: Class caching is turned on by default when server production mode is enabled.

Action: Set the CLASS_CACHE to false in the startWeblogic script and then restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000401: Socket queue full, dropping socket {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000402: There are: {0} active sockets, but the maximum number of socket reader threads allowed by the configuration is: {1}. The configuration may need altered.

Cause: When non-native I/O is used, I/O is performed in a blocking manner. Therefore, if the number of socket reader threads is less than the number of active sockets, performance may degrade significantly.

Action: Optimally, increase the ThreadPoolPercentSocketReaders, or the ThreadPoolSize, or both. Optimally, decrease the SocketReaderTimeoutMinMillis, or the SocketReaderTimeoutMaxMillis, or both.
Level: 1

Type: WARNING

Impact: Socket

BEA-000403: IOException occurred on socket: {0} {1}.

Cause: An unexpected IOException occurred while performing I/O for the socket.

Action: Check network connectivity. If the situation persists after environmental issues are resolved, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000404: ThreadDeath in processSockets {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000405: Uncaught Throwable in processSockets {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000406: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000409: Problem on socket: {0} {1}

Cause: An exception occurred while registering the socket with the muxer. It is possible that the file descriptor cannot be obtained from the socket.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000414: Could not initialize the POSIX performance pack.

Cause: The shared library for the POSIX performance pack could not be loaded.

Action: Ensure that the muxer shared library (libmuxer.so) exists in a directory that is in the LD_LIBRARY_PATH. If the situation persists, contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000415: System has file descriptor limits of soft: {0}, hard: {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000416: Using effective file descriptor limit of: {0} open sockets and files.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000421: Uncaught Throwable in processSockets {0}.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000429: Muxer received error: {0} {1}.

Cause: An unexpected error occurred while processing socket I/O requests.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000431: Accepted connection: filtering is set to: "{0}", remote address: "{1}", remote port: "{2,number,0}", local address: "{3}", local port: "{4,number,0}", protocol: "{5}"

Cause: This is an informational message for the administrator.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000432: Unable to load performance pack. Using Java I/O instead. {0}

Cause: The native library for the performance pack was unable to be loaded.

Action: Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000435: Unable to initiate read for the socket. The maximum allowed number of pending I/O requests ({0}) has been exceeded.

Cause: This is an internal error.

Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000436: Allocating {0} reader threads.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000437: The default setting for MuxerClass was overridden and no muxer class name was specified. Resorting to implementation class: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000438: Unable to load performance pack. Using Java I/O instead. {0}

Cause: The native performance pack was unable to be loaded.

Action: Ensure that the appropriate path for the native libraries is set properly in the environment.
Level: 1

Type: ERROR

Impact: Socket

BEA-000439: Unable to create the Java socket muxer.

Cause: This is an internal error.

Action: Ensure that the classpath is set properly. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000440: Unable to initiate I/O for {0} {1}.

Cause: The initiation of the I/O operation failed, which could have been caused by the network, I/O or other problems. It could also have been an internal error.

Action: Correct any conditions as suggested by the error message, if applicable. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000441: Unable to find internal data record for the socket {0}, with I/O completion result {1}

Cause: This is an internal error.

Action: If the situation persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Socket

BEA-000442: The connection attempt was rejected because the incoming protocol is not enabled on channel "{0}".

Cause: The connection attempt was rejected because a protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.

Action: Enable the protocol on the channel.
Level: 1

Type: WARNING

Impact: Socket

BEA-000443: The connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.

Cause: The connection attempt was rejected because the {1} protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.

Action: Enable the {1} protocol on the channel.
Level: 1

Type: WARNING

Impact: Socket

BEA-000444: Could not load the performance pack that can take advantage of the /dev/(e)poll device due to: {0}. Will attempt to use the performance pack that does not depend on the /dev/(e)poll device.

Cause: The operating system does not support the /dev/(e)poll or the device is not initialized.

Action: Ensure that the operating system supports the /dev/(e)poll device.
Level: 1

Type: WARNING

Impact: Socket

BEA-000445: Connection rejected, filter blocked {0}, {1}

Cause: The incoming message was not recognized as one of the supported protocols.

Action: Ensure that the server is configured for the relevant protocol.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000446: Native I/O enabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000447: Native I/O disabled. Using Java I/O.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000448: Socket channel support has been enabled for a JVM on which the feature is unsupported.

Cause: This error is caused by turning on a feature that is not supported on the underlying JVM.

Action: Either disable socket channel support or use a JVM version on which this feature is supported.
Level: 1

Type: ERROR

Impact: Socket

BEA-000449: Closing the socket, as no data read from it on {1}:{2} during the configured idle timeout of {0} seconds.

Cause: The WebLogic Server instance or the network may be overloaded, which is causing the socket to idle timeout.

Action: Capacity tuning of the server is required.
Level: 1

Type: WARNING

Impact: Socket

BEA-000451: Closing the socket, as end of file is encountered while reading from the socket to the ONS server at {0}.

Cause: The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.

Action: Check the status of the remote ONS process.
Level: 1

Type: WARNING

Impact: Socket

BEA-000452: An exception occurred on the socket to the ONS server at {0}: {1}.

Cause: An exception occurred while reading from the socket. The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.

Action: Check the network connectivity to the remote ONS process. If the situation persists after environmental issues are resolved, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Socket

BEA-000453: An exception occurred while processing the message sent from the ONS at {0}: {1}

Cause: An error occurred while parsing the message received from the remote ONS.

Action: Check the ONS log file for additional details.
Level: 1

Type: ERROR

Impact: Socket

BEA-000454: Unable to establish connection to the remote ONS process at {0}:{1}. Exception occurred while doing handshake: {2}

Cause: An exception occurred while doing handshake with the remote ONS process.

Action: Check the exception and ONS log file for additional details.
Level: 1

Type: ERROR

Impact: Socket

BEA-000455: Attempting to remove unregistered HandshakeCompletedListener: class={0}, instance={1}.

Cause: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.

Action: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.
Level: 1

Type: ERROR

Impact: Socket

BEA-000456: Unable to load performance pack. Using Java I/O instead.

Cause: The native library for the performance pack could not be loaded.

Action: Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Socket

BEA-000457: NIOInputStream received error while closing java.nio.channels.Selector: : {0} {1}.

Cause: An unexpected error occurred while processing socket I/O requests.

Action: If the situation persists, capture the errors and send the server log files to My Oracle Support.
Level: 1

Type: WARNING

Impact: Socket

BEA-000458: {0}

Cause: See the message body.

Action: Review the message body to determine the appropriate action to take.
Level: 1

Type: WARNING

Impact: Socket

BEA-000501: Peergone send failed - target unreachable.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000502: Peergone send failed - target already gone.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000503: Incoming message header or abbreviation processing failed. {0}

Cause: While processing an incoming message an error was encountered. It is likely that the message was corrupted.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000504: Unmarshal exception: received illegal command code: {0}

Cause: A message containing an invalid command code was received. This message cannot be processed. One of the possible reasons is that the message was corrupted in transit.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000505: Peer did not send us a valid heartbeat interval; using the default heartbeat specified as a property.

Cause: The incoming message has an invalid heartbeat interval. This is either due to message corruption in transit or to an invalid choice for the heartbeat interval on the peer that is attempting to establish communication with this JVM.

Action: If the peer that is attempting to establish communication is overriding the default heartbeat interval, ensure that a valid interval is used. If not, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000506: Closing: {0} because of {1}

Cause: This JVM has received an incoming message that is incompatible with the way the protocols are supposed to work.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000507: Could not create/send request to close duplicate connection message. {0}

Cause: Creation or sending of the message to request closing a connection caused an I/O error.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000508: ID: {0} in use by: {1}, can not install {2}

Cause: The ID {0} is already associated with and in use by {1} and hence cannot be used in association with {2}.

Action: Ensure that unique IDs are used in registration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000509: Finder not initialized.

Cause: This JVM was created without a valid finder.

Action: Ensure that a valid finder is used when creating this JVM.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000510: Unsolicited response: {0}

Cause: A duplicate response has been received for a request that has already received its response.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000511: Unsolicited error response for: {0}

Cause: A duplicate error response was received for a request that has already received its response or its error response.

Action: This is most likely a temporary situation. No action is necessary. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000512: New heartbeat period: {0} is different from established heartbeat period: {1}; using established heartbeat period

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000513: Failure in heartbeat trigger for RJVM: {0}. {1}

Cause: This error indicates a temporary failure in the heartbeat trigger mechanism.

Action: No action is required. This is usually a temporary failure.
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000514: openConnection() failed. {0}

Cause: Possible causes are an invalid target address or the target not being active or reachable.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000515: execute failed {0}

Cause: A failure was encountered when handling the incoming HTTP message.

Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000519: Unable to connect to a remote server on address {1} and port {2,number,0} with protocol {0}. The exception is {3}

Cause: The target is either not reachable or is not active.

Action: Ensure that the target is active.
Level: 1

Type: WARNING

Impact: RJVM

BEA-000570: Network Configuration for Channel "{0}" Listen Address {1} Public Address {2} Http Enabled {3} Tunneling Enabled {4} Outbound Enabled {5} Admin Traffic Enabled {6} ResolveDNSName Enabled {7}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000572: The server rejected a connection attempt {0} probably due to an incorrect firewall configuration or administrative command.

Cause: The incoming connection attempt was probably made through an address translating firewall. WebLogic Server needs to be correctly configured for this to work. This message can also occur if an administration connection attempt, requiring administrator level security, is made on a non-administrative port.

Action: Configure the public and private addresses for this WebLogic Server instance to reflect the configuration of the firewall. The private address is the actual address the server is running. The public address is the address that external clients use to connect.
Level: 1

Type: ERROR

Impact: RJVM

BEA-000573: RequestTimeout for message id {0} with message: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: RJVM

BEA-000600: Callback {0} failed: {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000601: AdminProxyWatchDog: Enabled. Interval = {0} secs.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000602: AdminProxyWatchDog: Enable failed.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000603: AdminProxyWatchDog: Disabled.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000604: AdminProxyWatchDog: Disable failed.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000605: Connectivity lost to WatchDog Client. Shutting down.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000606: AdminProxyWatchDog: No echo received in last {0} minutes. Shutting down.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: Common

BEA-000607: AdminProxyWatchDog: Echo Received.

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000608: AdminProxyWatchDog: Tick. diff = {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000609: An error occurred during server shutdown: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000611: No resources in the pool {0} will be tested, as specified MaxUnavailable {1} has been reached.

Cause: The application MaxUnavailable attribute for this pool has been configured. Since the number of unavailable resources in the pool has reached or exceeded the configured limit, no more resources will be tested (as resources become unavailable to the application during the testing).

Action: If necessary, tune the value for the MaxUnavailable attribute for the pool.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000612: All {1} resource instances currently available in the pool {0} are being tested.

Cause: This is a warning indicating that all currently available resources in the pool are being tested. Therefore, some or all of them may become unavailable to the application for a short time.

Action: Reduce the current setting of the MaxUnavailable attribute for the pool.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000613: Testing of resources upon creation has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000614: Testing of resources upon creation has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000615: Testing of resources when being reserved has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000616: Testing of resources when being reserved has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000617: Testing of resources when being released has been dynamically enabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000618: Testing of resources when being released has been dynamically disabled for pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000619: Unable to forcibly release resource "{1}" back into the pool "{0}". Received exception: {2}.

Cause: As part of the InactiveResourceTimeout feature, resources that are found to be inactive for the configured period of time are forcibly released back into the pool. The operation could not be performed for the indicated reason.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000620: Forcibly releasing inactive resource "{1}" back into the pool "{0}".

Cause: The resource was found to be unused by the application for the specified duration, and hence is being forcibly released back into the pool.

Action: Check application code for leakages of resource objects, or tune the configured value of the relevant pool attribute.
Level: 1

Type: WARNING

Impact: Common

BEA-000621: Expected RemoteException, RuntimeException, or Error {0}

Cause: An unexpected low-level message was sent to the server.

Action: This is likely to be due to an internal server/client error that should be reported to My Oracle Support.
Level: 1

Type: ERROR

Impact: Common

BEA-000622: Ignoring attempt to release resource "{1}" to pool "{0}" after the pool has been shut down.

Cause: Application is trying to release a resource to a pool after the pool has been shutdown.

Action: Check application behaviour. All resources should be closed before the application is shutdown.
Level: 1

Type: WARNING

Impact: Common

BEA-000623: Setting CapacityIncrement for pool "{0}" to 1. The specified value of "{1}" is not valid.

Cause: The application had specified an invalid value for CapacityIncrement.

Action: Check and correct the specified value for CapacityIncrement for the indicated pool.
Level: 1

Type: WARNING

Impact: Common

BEA-000624: Setting frequency of testing of free resources in pool "{0}" to 5 seconds, since the specified value of "{1}" is not valid.

Cause: The application had specified an invalid value for the test frequency.

Action: Check and correct the specified value for TestFrequencySeconds for the indicated pool.
Level: 1

Type: WARNING

Impact: Common

BEA-000625: The application has disabled periodic testing of free resources in pool "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000626: Free resources in pool "{0}" will be tested every "{1}" seconds.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000627: Reached maximum capacity of pool "{0}", making "{2}" new resource instances instead of "{1}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000628: Created "{1}" resources for pool "{0}", out of which "{2}" are available and "{3}" are unavailable.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000629: Recreated "{2}" out of "{1}" resources for pool "{0}".

Cause: As part of forcibly suspending a pool, all resources currently in use are destroyed and recreated. This message indicates that not all required resources were recreated.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Common

BEA-000630: Unable to create "{1}" resources for pool "{0}".

Cause: As part of the ConnectionCreationRetry feature, pools periodically attempt to create unavailable resources. This message indicates that in the current attempt, the indicated number of resources could not be created.

Action: Check whether the failure condition that prevents the resources from being created (for example, the database server or downed network connectivity to it) is still persisting.
Level: 1

Type: WARNING

Impact: Common

BEA-000631: Unknown resource "{1}" being released to pool "{0}": {2}

Cause: Application is trying to release a resource to a pool that is no longer part of the pool. This could happen if the pool was forcibly suspended (which results in all borrowed resources being closed and replaced with new ones) while the resource was borrowed by the application.

Action: Check application behavior.
Level: 1

Type: WARNING

Impact: Common

BEA-000632: Resource Pool "{0}" shutting down, ignoring {1} resources still in use by applications..

Cause: The administrator is shutting down the pool while applications are still using resources that they have obtained from the pool. It is possible that these resources may have been leaked by the applications.

Action: Check application behavior.
Level: 1

Type: WARNING

Impact: Common

BEA-000633: Resource Pool "{0}" suspending due to consecutive number of resource creation failures exceeding threshold of {1}

Cause: Resource creation or resource tests have repeatedly failed.

Action: Determine the cause of resource failures and take corrective action.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000634: Resource hang detected for pool "{0}", group "{1}". Waited {2} milliseconds where a typical test has been taking {3}.

Cause: Resource tests have been taking longer than expected.

Action: Correct the condition that causes the resource tests to block for extended periods of time.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000635: Resource Pool "{0}", group "{1}" disabled due to number of resource creation or test failures exceeding threshold of {2}.

Cause: Resource creation or resource tests have repeatedly failed.

Action: Determine the cause of resource failures and correct.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000636: Resource Pool "{0}", group "{1}" enabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000637: Resource Pool "{0}" resuming due to successful resource creation or test.

Cause: This is an informmational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000638: Resource Pool "{0}" is being suspended by an external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000639: Resource Pool "{0}" is being force-suspended by an external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000640: Resource Pool "{0}" resuming by external command (multi data source or console or other).

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000701: Unable to mount the fileSystem named {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000702: Unable to unmount the fileSystem named {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000703: Unable to get fileSystem context from Root {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000704: Cannot create file system at {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000705: Created file system at {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: NOTIFICATION

Impact: T3Misc

BEA-000706: Unable to find remote file {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000707: Unable to open remote file {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000708: T3RemoteOutputStreamProxy: write timed out or interrupted - {0}, {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000709: T3RemoteOutputStreamProxy: flush timed out or interrupted - {0}, {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000710: TimeRepeat trigger scheduled to run at a date in the past : {0}, trigger will not repeat

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000711: Uncaught throwable in run {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000712: Exception invoking {0} {1}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000713: Exception closing stream {0}

Cause: Deprecated functionality.

Action: Deprecated functionality.
Level: 1

Type: ERROR

Impact: T3Misc

BEA-000800: {0} stopped.

Cause: A ThreadDeath exception caused a shutdown.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: Kernel

BEA-000801: ExecuteRequest: {0} cancelled.

Cause: This only happens when WebLogic Server is used in conjunction with an IDE, which uses JVMDI to cancel in-flight requests. If this occurs in normal operation, contact My Oracle Support.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000802: ExecuteRequest failed {0}.

Cause: An execute request generated an exception that was not handled.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000803: The Class {0} has a setter {1} for attribute {2} which does not have a constructor that could be initialized from a String value of {3}.

Cause: No constructor that takes a String argument was found for the declared attribute type.

Action: Provide a constructor with a String argument.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000804: The Class {0} attribute {1} could not be initialized with value {2}. The exception message is {3}.

Cause: See the exception stack trace for details.

Action: Take the appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Kernel

BEA-000805: The self-tuning thread pool is disabled. An execute queue will be created for each Work Manager definition.

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000807: Work Manager {0} has reached its capacity. It is rejecting from thread {1}. The message is {2}. Throwable is {3}.

Cause: This is a Work Manager bug.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000808: The executing thread is a non-WebLogic Server thread. Modify the application to use the Commonj Work Manager API.

Cause: The use of an application spawned a Java thread instead of the Commonj Work Manager API.

Action: Modify the application to use the Commonj Work Manager APIs.
Level: 1

Type: WARNING

Impact: Kernel

BEA-000810: The memory pressure field has changed from {0} to {1}.

Cause: The memory pressure in the system has gone either up or down.

Action: The system should be responding to the memory pressure level. No further action should be taken.
Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000902: A duplicate expression was found in the system property {0}.nonProxyHosts: {1}.

Cause: The system property {0}.nonProxyHosts contains a pipe character delimited list of hosts, which should be connected to directly and not through the proxy server.

Action: Check the system property {0}.nonProxyHosts. The value can be a list of hosts, each separated by a |. In addition, a wildcard character (*) can be used for matching. For example: -D{0}.nonProxyHosts="*.foo.com|localhost".
Level: 1

Type: ERROR

Impact: Net

BEA-000903: Failed to communicate with proxy: {0}/{1}. Will try connection {2}/{3} now.

Cause: An IOException was received while communicating with the proxy server.

Action: Check the exception for more information. Check if the proxy is running by pinging the proxy: {0}/{1} from the same machine.
Level: 1

Type: ERROR

Impact: Net

BEA-000904: {0} initializing the URL stream handler with custom factory: {1}.

Cause: The factory class that was specified against the system property weblogic.net.http.URLStreamHandlerFactory failed to load or invoke.

Action: Check the system property weblogic.net.http.URLStreamHandlerFactory. This property is used to set a custom URLStreamHandlerFactory.
Level: 1

Type: ERROR

Impact: Net

BEA-000905: Could not open connection with host: {0} and port: {1}.

Cause: The connection attempt failed.

Action: Ensure that the server is running on the specified host and port.
Level: 1

Type: WARNING

Impact: Net

BEA-001035: The following error has occurred: {0}.

Cause: The embedded message should contain an explanation of the failure.

Action: Take appropriate action based on the reported error.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001058: Could not get JNDI context: {0}

Cause: Look at the printed exception to see why the call failed.

Action: Correct the problem and re-run the operation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001064: Ignoring the property "enableTwoPhaseCommit" for JDBCTxDataSource "{0}". This property is used only for those drivers that do not natively support XA.

Cause: The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001066: Delaying {0,number} seconds before making a {1} pool connection.

Cause: Some databases cannot handle a tight loop of making multiple connections from one application. If this is the case and the delay is more than 2 seconds, this message will be printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001067: Connection for pool "{0}" refreshed.

Cause: A connection for the specified pool has been refreshed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001068: Connection for pool "{0}" created.

Cause: A connection for the specified pool has been created.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001072: Connection for XA pool "{0}" created.

Cause: A connection for the specified XA pool has been created.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001073: Connection for XA pool "{0}" refreshed.

Cause: A connection for the specified XA pool has been refreshed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001074: A JDBC pool connection leak has been detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. The following stack trace at create shows where the leaked connection was created. {0}

Cause: A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. A stack trace is printed indicating where the leaked connection was created.

Action: Close the connection appropriately.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001076: An attempt has been made to release a connection that belongs to a non-existing pool. Ensure that the pool "{0}" has been destroyed by intent.

Cause: An attempt was made to release a connection that belongs to a non-existing pool.

Action: Correct the destroy operation to specify a valid pool name.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001083: Multi data source "{0}" was created with {1,number} connection pools for {2}.

Cause: A multi data source was created with the specified number of connection pools.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001084: Multi data source "{0}" will be shutdown

Cause: The specified multi data source is being shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001086: Data source "{0}" with JNDI name "{1}" will be shut down.

Cause: The specified data source is being shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001089: Data source connection pool {0} has been started for application {1}, module {2}.

Cause: The specified data source connection pool is being started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001099: Data source connection pool "{0}" reset by "{1}".

Cause: The specified connection pool has been reset.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001100: Data source connection pool "{0}" shut down by "{1}".

Cause: The specified data source connection pool has been shut down, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001101: Data source connection pool "{0}" disabled by "{1}".

Cause: The specified data source connection pool has been disabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001102: Data source connection pool "{0}" enabled by "{1}".

Cause: The specified data source connection pool has been enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001104: A globally scoped data source connection pool named ({0}) already exists.

Cause: When adding or referencing a JDBC data source connection pool that is an application-scoped pool, a globally scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.

Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001105: Referenced global pool ({0}) has the same name as a locally defined data source connection pool or data source ({1}).

Cause: When deploying a JDBC data source connection pool (not application-scoped) an application (locally) scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.

Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001107: There is a globally defined data source ({0}) with the same JNDI name ({1}) as a locally defined data source.

Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is a pool that the application meant to use and it is bound into comp/env. However, a check in the global namespace indicates that there is also a global pool with the same JNDI name.

Action: If you want to reference the global pool in your application, the JNDI name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001108: A locally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).

Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is the pool that the application meant to use and it is bound into comp/env.

Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001109: A globally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).

Cause: It is possible to use a resource descriptor with global data source connection pools. If the JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is the pool that the application was meant to use and it is bound into comp/env.

Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001110: No test table set up for pool "{0}". Connections will not be tested.

Cause: TestConnectionsOnReserve, TestConnectionsOnRelease, TestConnectionsOnCreate, TestFrequencySeconds were configured but TestTableName was not configured.

Action: Configure a valid TestTableName for the data source connection pool.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001111: Unable to verify the test "{1}" set up for pool "{0}". Connections will not be tested. The test will not be used by isValid either.

Cause: While creating a data source connection pool with the attributes specified to test the pool connections, a test is run during the pool initialization. This test failed with the printed error.

Action: Check the SQL error that occurred and correct the problem. The specified TestTableName might not exist.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001112: Test "{1}" set up for pool "{0}" failed with exception: "{2}".

Cause: The specified data source connection pool has been configured with one or more attributes to test the pool connections. One of those test attempts failed. The associated error is printed.

Action: Check the associated error to see what the problem is and correct it. Normally, this indicates that a connection was lost to the database (the database is down). This needs to be corrected by the database administrator.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001113: Data source connection pool "{0}" shrunk by "{1}".

Cause: The data source connection pool has been shrunk by the specified amount as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001114: Soft shutdown called on data source connection pool "{0}" by "{1}".

Cause: A soft shutdown operation on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001115: Hard shutdown called on data source connection pool "{0}" by "{1}".

Cause: A hard shutdown operation on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001116: Disable and freeze users called on data source connection pool "{0}" by "{1}".

Cause: An operation to disable and freeze users on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001117: Disable and drop users called on data source connection pool "{0}" by "{1}".

Cause: An operation to disable and drop users on the specified data source connection pool has been started, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001118: Unable to register for receiving MBean notifications of dynamic configurations changes for data source connection pool "{0}": "{1}". Pool will not be dynamically reconfigured.

Cause: The server was unable to register for receiving MBean notifications of dynamic configurations changes for the specified data source connection pool. The connection pool will not be dynamically reconfigured.

Action: Check the exception that is printed along with this message to see what the cause of the failure was.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001119: Unable to delete configuration MBean for pool "{0}": "{1}"

Cause: While doing a forced shutdown, the data source connection pool was removed but the associated MBean for the connection pool was not removed.

Action: Check the exception that is printed along with this message to see what the cause of the failure was.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001120: Created data source named {0} for Pool {1}.

Cause: There was a user request to create a data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001121: Created TX data source named {0} for Pool {1}.

Cause: The user requested that the TX data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001122: Destroyed TX data source named {0} for Pool {1}.

Cause: There was a user request to destroy the TX data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001123: Destroyed data source named {0} for Pool {1}.

Cause: There was a user request to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001124: Created Connection Pool named {0}.

Cause: There was a user request to create the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001125: Created multi data source named {0}.

Cause: There was a user request to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001126: Destroyed Connection Pool named {0}.

Cause: There was a user request to destroy the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001127: Destroyed multi data source named {0}.

Cause: There was a user request to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001128: Connection for pool "{0}" has been closed.

Cause: A connection for the specified data source connection pool has been closed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001129: Received exception while creating connection for pool "{1}": {0}.

Cause: The exception message should indicate the probable cause of the error.

Action: Check the error to see why the connection creation failed and correct the problem.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001130: Disabled statement caching for connection in pool "{0}" as it is using the WebLogic Type-2 XA driver.

Cause: Statement caching was disabled for the specified data source connection pool because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when the XAResource.end is called, causing all prepared statements to be no longer valid.

Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001131: Received an exception when closing a cached statement for the pool "{0}": {1}.

Cause: When closing a prepared statement in the prepared statement cache for the specified data source connection pool, an error occurred.

Action: Check the associated error that is printed and, if possible, correct the problem.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001132: Initialized statement cache of size "{1}" for connection in pool "{0}".

Cause: A prepared statement cache has been enabled for a connection in the specified data source connection pool.

Action: No action is required. If you do not want statement caching turned on for the pool, do not configure or disable it.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001133: Statement caching is not enabled for connection in specified data source connection pool "{0}".

Cause: A configured data source connection pool has been started without statement caching being enabled.

Action: No action is required. If you want statement caching turned on for the pool, configure and enable it.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001134: Statement caches of connections in the data source connection pool "{0}" have been cleared by "{1}".

Cause: The statement caches for connections in the specified data source connection pool have been cleared, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001135: Initializing the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001136: Initialization failed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001137: Initialization complete.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001138: Resuming the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001139: Resume failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001140: Resume complete.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001141: Suspending the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001142: Suspend of JDBC service failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001143: Suspend completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001144: Force Suspending the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001145: Force suspend of the JDBC service failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001146: Force suspend of the JDBC service completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001147: Shutting down the JDBC service.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001148: Shutdown of the JDBC service failed.

Cause: Check earlier messages that are printed in the log.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001149: Shutdown of the JDBC service has completed.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001150: Connection pool "{0}" deployment failed with the following error: {1}.

Cause: The cause should be indicated in the exception message.

Action: Correct the problem described in the exception message.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001151: Data source "{0}" deployment failed with the following error: {1}.

Cause: The cause should be indicated in the exception message.

Action: Correct the problem described in the exception message.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001152: Cannot enable statement caching for connection in pool "{0}", because it is using the WebLogic Type-2 XA driver.

Cause: Statement caching has been disabled for the specified data source connection pool because the connection pool is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to no longer be valid.

Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001153: Forcibly releasing inactive/harvested connection "{1}" back into the data source connection pool "{0}", currently reserved by: {2}.

Cause: The connection was found to be unused by the application for the specified duration (configured using InactiveConnectionTimeoutSeconds attribute of the pool MBean), and therefore is being forcibly released back into pool. Alternatively, the connection was harvested and the application callback did not close the connection.

Action: Check the application code for leakages of connection objects, or tune the configured value of the specifed connection pool attribute.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001154: Disabling statement caching for connection in pool "{0}".

Cause: Statement caching has been disabled for the specified data source connection pool for one or more reasons. 1. The size is explicitly configured to 0. 2. The Oracle replay driver is being used. 3. The Oracle statement cache is enabled.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001155: The following exception has occurred:

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001156: Stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001157: Data source connection pool "{0}" being suspended by user "{1}".

Cause: The specified data source connection pool is being suspended, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001158: Data source connection pool "{0}" being forcibly suspended by user "{1}".

Cause: The specified data source connection pool is being forcibly suspended, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001159: Data source connection pool "{0}" is being resumed by user "{1}".

Cause: The specified data source connection pool is being resumed, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001160: Data source connection pool "{0}" being forcibly destroyed by user "{1}"

Cause: The specified data source connection pool is being forcibly destroyed, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001161: Data source connection pool "{0}" being destroyed by user "{1}".

Cause: The specified data source connection pool is being destroyed, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001162: Data source connection pool "{0}" being forcibly shutdown by user "{1}".

Cause: The specified data source connection pool is being forcibly shutdown, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001163: Data source connection pool "{0}" being shut down by user "{1}".

Cause: The specified data source connection pool is being shut down, as requested by the application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001164: Unable to initialize connection in pool "{0}". Initialization SQL = "{1}". Received exception: "{2}".

Cause: The exception message should contain a reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001165: Invalid statment cache size "{1}" specified for connection in pool "{0}".

Cause: An invalid value has been specified for statement cache size for connections in the indicated data source connection pool.

Action: Check the allowed limits for statement cache size for this data source connection pool and fix the specified value.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001166: Activation of application-scoped data source connection pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".

Cause: The error message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001167: Deactivation of application-scoped pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".

Cause: The error message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001168: Attempt to resume JDBCService when it is already running...Ignoring.

Cause: The application attempted to resume JDBCService, although the service is already running.

Action: Take appropriate corrective action.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001169: Error occured during shutdown of pool "{0}". Received exception: "{1}".

Cause: The exception should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001170: Unable to initialize JDBC Log. Received exception: "{0}".

Cause: The message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001171: Unable to close connection "{0}". Received exception: "{1}".

Cause: The message should contain the reason for the failure.

Action: Take suitable action if possible. Otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001172: Error occurred during shutdown of data source "{0}". Received exception: "{1}".

Cause: The message should contain the reason for the failure.

Action: Take appropriate corrective action.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001173: "TestTableName" attribute for pool "{0}" being dynamically changed to "{1}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001174: Creating data source named {0}, JNDI Name = {1}.

Cause: The user requested that the data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001175: Creating transactional data source named {0} for Pool {1}.

Cause: The user requested that the transactional data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001176: Creating multi data source named {0}.

Cause: The user requested that the multi data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001177: Creating data source connection pool named {0}, URL = {1}, Properties = {2}.

Cause: A request was issued to create the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001178: Attempt to set query timeout on a statement failed : {0}.

Cause: The reported message should contain a description of the failure.

Action: Contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001250: Unable to load application configured callback {1} for multi data source {0}, got error: {2}. Application control of multi data source failover behaviour will not work.

Cause: This is most likely because the application-defined class location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001251: Application configured callback {1} for multi data source {0} does not implement required interface {2}. Application control of multi data source failover behaviour will not work.

Cause: The configured callback {1} does not implement the required interface {2}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001252: Unable to add notification listener for Config MBean for multi data source {0} failed, got exception: {1}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001254: Multi data source {0} unable to disable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001255: Multi data source {0} unable to disable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001256: Dynamically changing the value of attribute FailoverRequestIfBusy for multi data source {0} from {1} to {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001257: Dynamically changing value of attribute HealthCheckFrequencySeconds for multi data source {0} from {1} to {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001258: Unable to setup timer for multi data source {0}, got exception: {1}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001259: Application has disallowed multi data source {0} from re-enabling data source connection pool {1}, which had previously been found dead and was disabled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001260: Multi data source {0} unable to enable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001261: Multi data source {0} unable to enable connection pool {1}, got exception: {2}.

Cause: The reported exception should indicate the cause of the failure.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001262: Registered application callback {1} for multi data source {0} to control multi data source failover behavior.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001500: Creating application-coped multi data source {0}, algorithm type {3} for Application {1}, Module {2}.

Cause: The user requested that the multi data source be created, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001501: Creating multi data source {0}, algorithm type {1}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001503: Creating application-scoped data source connection pool {0} for Application {1}, Module {2}, URL = {3}, Properties = {4}.

Cause: A request was made to create the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001504: Destroying multi data source {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001505: Destroying multi data source Pool {0}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001507: Destroying data source connection pool {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001508: Destroying data source connection pool {0}.

Cause: A request was made to destroy the data source connection pool, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001510: Creating application-scoped data source {0} for Application {1}, Module {2}, Application Context Name = {3}.

Cause: A request was made to create the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001512: Data source {0} has been successfully created.

Cause: A request was made to create the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001513: Destroying application-scoped data source {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001514: Destroying data source {0}.

Cause: A request was made to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001515: Data source {0} has been successfully destroyed.

Cause: A request was made to destroy the data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001516: Data source connection pool "{0}" connected to Database: "{1}", Version: "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001517: Data source connection pool "{0}" using Driver: "{1}", Version: "{2}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001518: Data source connection pool "{0}" Connection Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001519: Id : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001520: Timestamp : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001521: User : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001522: Data source connection pool "{0}" Connection Wait Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001523: Data source connection pool "{0}" Connection Leak Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001524: Data source connection pool "{0}" Connection Reserve Fail Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001525: Data source connection pool "{0}" Statement Cache Entry Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001526: Unable to load class "{0}", got exception : {1}. Driver Interception feature disabled.

Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001527: Application configured class {0} does not implement required interface {1}. Driver Interception feature disabled.

Cause: The configured class {0} does not implement the required interface {1}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001528: Driver Interceptor class {0} loaded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001529: JDBC loggging last resource (LLR) connection pool {0} did not find its table and is creating a new one using the following SQL: {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001530: JDBC loggging last resource (LLR) connection pool {0} retrieved {1} record(s) from the database table {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001531: Received updated event for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001532: Data source connection pool "{0}" Statement Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001533: Pool Name : "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001534: Data source connection pool "{0}" Connection Last Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001535: Data source connection pool "{0}" Connection Multi-threaded Usage Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001536: Creating multi data source named {0}, JNDI Name = {1}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001537: Creating application-scoped multi data source {0} for Application {1}, Module {2}, Application Context Name = {3}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001538: Created multi data source named {0}.

Cause: A request was made to create the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001539: Destroying multi data source {0}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001540: Destroying application-scoped multi data source {0}, created for Application {1}, Module {2}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001541: Destroyed multi data source named {0}.

Cause: A request was made to destroy the multi data source, either implicitly or explicitly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001542: JVM DriverManager Login Timeout value set to {0}.

Cause: The application has specified this behavior to be enabled, via the corresponding configuration setting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001543: Received change event: {1} for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001544: Received add event: {1} for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001545: Received unexpected event: {1} for unexpected type of bean: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001546: Data source connection pool "{0}" is being started by user "{1}".

Cause: The specified data source connection pool is being started, as requested by the administrator.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001547: The "{0}" field value "{1}" in table reference "{2}" format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.

Cause: This is a configuration error.

Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001548: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).

Cause: This is a configuration error.

Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, ensure that there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001549: An old style WebLogic driver URL {0} is used. Because the WebLogic driver URL auto-convert switch is turned on, it is converted to {1}.

Cause: An old style WebLogic driver URL is used and the WebLogic driver URL auto-convert switch is turned on.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001550: WebLogic Oracle driver is being used. The driver URL is {0}. WebLogic Server no longer supports the WebLogic Oracle driver.

Cause: The WebLogic Oracle driver has been deprecated and removed.

Action: Stop using the WebLogic Oracle driver, use the Oracle Thin driver instead.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001551: Application context for member data source {1} not found for standalone multi data source module {0}. Ensure that multi data source standalone modules have a higher deployment order than member data source standalone modules.

Cause: The deployment order of the multi data source is the same or lower than one of its member datasources.

Action: Change the deployment order of the standalone multi data source to be greater than each member data source's deployment order.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001552: The logging last resource (LLR) data source {0} will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.

Cause: Remote JDBC access over RMI is disabled.

Action: Either configure the data source to use an XA-capable driver, or enable remote JDBC on all servers.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001553: Unable to deploy JDBC data source {0}. No credential mapper entry found for password indirection user {1}

Cause: No credential mapper entry was found for user {1} on data source {0}

Action: Ensure that a credential mapper entry is defined for the data source {0} that maps the specified user name {1} to a password. The WebLogic Server administration console provides support for managing data source credential mapper entries.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001554: Data source connection pool "{0}" Connection Unwrap Data:

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001555: Invalid member data source {1} specified for multi data source {0}. GridLink data source may not be used in multi data source configurations.

Cause: A GridLink data source was specified as a multi data source member.

Action: Either use a single GridLink data source or define generic data sources for use in a multi data source configuration.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001556: Data source {0} for service {1} registering with ONS daemons using configuration string {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001557: Data source {0} for service {1} unregistering with ONS daemons {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001558: Data source {0} for service {1} received a service down event for instance {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001559: Data source {0} for service {1} received a node down event for node {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001560: Data source {0} for service {1} received a service up event for instance {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001561: Data source {0} for service {1} received a node up event for node {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001562: Data source {0} for service {1} not registering for Fast Application Notification (FAN) events.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001563: ADM_DDL LLR (logging last resource) connection pool {0} did not find its table {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001564: JTSLoggableResourceTable.existsForADMDDL about to return: return value = {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001565: Logging last resource (LLR) data source {0} using LLR table {1} defined by system property weblogic.llr.table.{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001566: JTSLoggableResourceTable.init for ADMDDL is generating SQL statement(createSQL): {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001567: SQLRuntimeException caught at existsForADMDDL for poolName: {0} ddlName: {1} by: {2}.

Cause: Look at the printed exception to see why the call failed.

Action: Correct the problem and run the operation again.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001568: Data source {0} for service {1} received a service up event

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001569: Data source {0} failed to create runtime MBean for RAC instance {1}. Exception={2}

Cause: Refer to the exception error message for the cause of the failure.

Action: Try redeploying the data source or restart the WebLogic Server instance.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001570: Attempt to enable Fast Application Notification (FAN) support for a non-GridLink data source {0}, which is not supported.

Cause: Subscribing to FAN events is only supported by GridLink data sources.

Action: Either set the FAN enabled attribute to false or configure a GridLink data source.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001571: Unable to load the connection labeling callback class "{0}", got exception : {1}.

Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001572: Application-configured connection labeling callback class {0} does not implement required interface {1}.

Cause: The configured class {0} does not implement the required interface {1}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001573: Connection labeling callback class {0} loaded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001574: Unable to load the connection Initialization callback class "{0}", got exception : {1}.

Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.

Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001575: Application configured connection initialization callback class {0} does not implement required interface {1}.

Cause: The configured class {0} does not implement the required interface {1}.

Action: Refer to the WebLogic Server documentation.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001576: Connection Initialization callback class {0} loaded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001580: An exception was thrown from the ConnectionHarvestingCallback: {0}.

Cause: The application callback threw an exception when the callback was called.

Action: Look at the associated message. If more information is desired, turn on connection debuggging.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001581: An invalid scope of Application instead of Global is specified for data source {0}, URI = {1}.

Cause: The configuration is invalid. The specified datasource must have a Global scope.

Action: Correct the configuration for the specified datasource.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001582: oracle.jdbc.DRCPConnectionClass must be specified if and only if a Database Resident Connection Pooling (DRCP) pool is defined.

Cause: The configuration is invalid.

Action: Correct the configuration for the specified data source.
Level: 1

Type: ERROR

Impact: JDBC

BEA-001583: The WebLogic statement cache size is disabled because Oracle statement cache is configured.

Cause: The WebLogic statement cache is disabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001584: Data source connection pool "{0}" disabled by multi data source "{1}".

Cause: The specified data source connection pool has been disabled by a multi data source.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001585: Data source connection pool "{0}" re-enabled by multi data source "{1}".

Cause: The specified data source connection pool has been re-enabled by a multi data source.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001586: EndRequest failed: {0}

Cause: This generally happens because the application failed to complete a local transaction before closing the connection. See the associated message to determine if this is the case.

Action: The error is ignored if the connection can be cleared. This is, however, an application error to not complete the transaction. Fix the software.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001587: For LLR RAC DataSource {0} Member of MultiDataSource, test-on-reserve is disabled, and the health of the DataSource can not be verified.

Cause: Test on Reserve is disabled in the DataSource configuration.

Action: Enable Test on Reserve in the DataSource configuration. If all memeber DataSources are marked as unhealthy and the WLS admin server fails to boot use WLST to change configuration.
Level: 1

Type: WARNING

Impact: JDBC

BEA-001588: Shrinking connection pools due to memory pressure level of {0} exceeding shrink threshold of {1}.

Cause: There is increased memory consumption in the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001589: Setting all datasource statement cache sizes to {0}% of configured sizes due to memory pressure level of {1}.

Cause: There is increased memory consumption in the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001590: Setting {0} statement cache size to {1} ({2}% of configured size {3}).

Cause: There is increased memory consumption in the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-002001: Received an unknown message type.

Cause: This should not occur. This indicates that the client is sending garbaged messages. It might also indicate that malicious third parties are trying to access the server using IIOP.

Action: Contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002002: Failed to parse method name {0}.

Cause: This can happen for a variety of reasons. Normally, it is because the caller made a request for a non-existent method. Alternatively, the IDL mangling of the method name may be ambiguous, so WebLogic Server cannot decide which method to call.

Action: If the IDL mangling is causing a problem, try changing the name of the method. In particular, names such as getSomedata() (where somedata is also the name of an attribute or method) can cause problems. Also, some bugs with name mangling exist in JDK 1.3.1. Try using a JDK 1.4 client.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002003: Unable to send the message: {0}.

Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.

Action: Verify that the client-server network connection is working.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002005: OutOfMemoryError in adapter: {0}.

Cause: This is often caused by marshalling mismatches between the client and the server and is generally a bug in either the client or the server or both.

Action: Restart the server and contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: IIOP

BEA-002006: Cannot scavenge idle connections, {0}

Cause: The server was unable to schedule a trigger to watch for idle IIOP connections. The fact that it was unable to do so indicates some core failure in the server.

Action: Restart the server. If this occurs again, contact Oracle Customer Support.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002008: Failed to export {0}. The following exception occurred: {1}.

Cause: This is most often caused by the server being unable to find or generate an IIOP stub for the remote object. Ensure that the Common Object Request Broker API (CORBA) objects have corresponding _Stub classes in the server classpath. RMI-IIOP object stubs should be generated automatically.

Action: For CORBA objects, ensure that the idlj was run on the server class. For RMI-IIOP objects, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002011: Failed to marshal exception {0}: {1}.

Cause: The server could not find the appropriate exception definitions in its classpath. For Common Object Request Broker API (CORBA) exceptions, the application must contain the exception helper classes as well as the exception classes.

Action: Add missing exception classes to the application.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002012: Failed to send exception {0}: {1}.

Cause: This only happens if the connection between the client and server was very unreliable.

Action: Verify that the client-server network connection is working. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002013: Complete failure to send exception {0}: {1}.

Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.

Action: Verify the client-server network connection.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002014: IIOP subsystem enabled.

Cause: The IIOP subsystem is operational and is listening for incoming IIOP requests.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002015: Using javax.rmi.CORBA.UtilClass {0}; The IIOP subsystem requires a WebLogic Server-compatible UtilClass.

Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.UtilClass or tried accessing javax.rmi.CORBA.Util functions before the IIOP subsystem had initialized.

Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002016: Using javax.rmi.CORBA.PortableRemoteObjectClass {0}, the IIOP subsystem requires a WebLogic Server-compatible PortableRemoteObjectClass.

Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.PortableRemoteObjectClass or tried accessing javax.rmi.PortableRemoteObject functions before the IIOP subsystem had initialized.

Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002017: LocateRequest is {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002018: Default GIOP version is 1.{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002019: LocationForward policy is {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002021: SecurityService registered under {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002022: Could not bind SecurityService {0}.

Cause: This is an internal JNDI problem.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002023: Could not resolve SendingContext RunTime: {0}.

Cause: An invalid object reference for SendingContext RunTime was provided by the client.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002026: Transaction mechanism is {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002027: Complete failure to rewrite exception from {0}: {1}.

Cause: This error should not occur.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: IIOP

BEA-002028: An OTS error occurred: {0}, {1}.

Cause: OTS errors are generally not bugs but always result in exception information being lost when propagated to the caller. Thus, the root cause is always logged, so that system administrators can determine the real cause. OTS errors are generally caused by some transaction subsystem operation (for instance, a transaction being rolled back).

Action: Ensure that this is an expected error.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002033: Codeset for {0} data set to {1}, OSF registry entry {2}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002037: CosNaming Service registered under {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002038: Could not bind the CosNaming Service {0}.

Cause: This is an internal JNDI problem.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002039: Replacer: {0}

Cause: The replacer did not have enough information to do a proper replacement.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002041: Connection attempt was rejected because IIOP is not enabled on this channel.

Cause: The connection attempt was rejected because IIOP is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.

Action: Enable IIOP.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002043: Naming exception: {0}

Cause: A standard exception was generated by the naming implementation.

Action: No action is required.
Level: 1

Type: WARNING

Impact: IIOP

BEA-002605: Adding address: {0} to the licensed client list.

Cause: The server accepted a connection from the specified client.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002606: The server is unable to create a server socket for listening on channel "{3}". The address {0} might be incorrect or another process is using port {1,number,0}: {2}

Cause: The address was incorrect or another process was using the port.

Action: Use ipconfig or ifconfig to check if the listen address is valid, and use netstat to check that the specified port is not in use by another process.
Level: 1

Type: ERROR

Impact: Server

BEA-002607: Channel "{2}", listening on {0}:{1,number,0}, was shut down.

Cause: The server or channel was shut down.

Action: No action is required. If this was an unexpected error, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002608: The ListenThread failed because of an error: {0}

Cause: An exception occurred when the server socket was unable to accept client connections.

Action: Check the file descriptor limit. Tune the operating system parameters that handle socket creation using ServerSocket.
Level: 1

Type: ERROR

Impact: Server

BEA-002609: Channel Service initialized.

Cause: The Channel subsystem is operational.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002610: Dynamic Listener Service initialized.

Cause: The dynamic listener subsystem is operational.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002611: The hostname "{0}", maps to multiple IP addresses: {1}.

Cause: The host name of the server resolved to multiple IP addresses, which can cause problems for the Administration Server.

Action: Check if this was done on purpose.
Level: 1

Type: WARNING

Impact: Server

BEA-002612: Channel "{2}", listening on {0}:{1,number,0}, did not start did not start properly.

Cause: Some of the listen ports did not open or failed within the configured grace period.

Action: Ensure that none of the configured listen ports are in use by other processes.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002613: Channel "{2}" is now listening on {0}:{1,number,0} for protocols {3}.

Cause: The server successfully started the listen thread and server socket.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002614: Reopening channel "{2}" on {0}:{1,number,0}.

Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002615: After having failed to listen, the server is now listening on channel "{2}" on {0}:{1,number,0}.

Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002616: Failed to listen on channel "{2}" on {0}:{1,number,0}, failure count: {3}, failing for {4} seconds, {5}

Cause: An exception occurred while trying to accept client connections. The server will try to back off to aid recovery.

Action: The operating system (OS) limit for the number of open file descriptors (FD limit) needs to be increased. Tune the OS parameters that might help the server to accept more client connections (for example, TCP accept back log).
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002617: Attempting to close and reopen the server socket on channel "{2}" on {0}:{1,number,0}.

Cause: The server listener could not accept a socket connection and failed after several simple retries. It has closed and reopened the server socket.

Action: Check if the file decriptor limit needs to be increased. Tune the operating system parameters that might help the server accept more client connections.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002618: An invalid attempt was made to configure a channel for unconfigured protocol "{0}".

Cause: The server configuration specified a channel that uses a protocol that is not enabled.

Action: Enable the protocol in the server configuration.
Level: 1

Type: ERROR

Impact: Server

BEA-002619: One or more listen ports did not start properly.

Cause: One or more listen ports failed to open during server startup.

Action: Ensure that none of the configured listen ports are in use by other processes.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002620: An invalid attempt was made to configure a channel for server "{0}" on an unknown listen address "{1}".

Cause: The server configuration specified a channel that uses a listen address that does not exist.

Action: Correct the server configuration.
Level: 1

Type: ERROR

Impact: Server

BEA-002621: The connection was rejected because the server license only allows connections from {0} unique IP addresses.

Cause: Clients tried to connect from more distinct addresses than the license allows.

Action: Use a server license that allows for more clients to connect.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002622: The protocol "{0}" is now configured.

Cause: The server has loaded a protocol making it available for outbound traffic and configurable for inbound traffic.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002623: Connection rejected, the server is in the {0} state. Remote Server contacting us is {1}

Cause: Clients tried to connect to the server before it was in the RUNNING state.

Action: Connect to the server after it has started.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002624: The administration protocol is "{0}" and is now configured.

Cause: The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002625: An attempt to configure channel "{0}" failed because of {1}.

Cause: The cause is detailed in the accompanying exception.

Action: Review the exception.
Level: 1

Type: ERROR

Impact: Server

BEA-002626: The protocol "{0}" could not be loaded: {1}

Cause: Consult the exception for why the protocol could not be loaded.

Action: Consult the exception for why the protocol could not be loaded.
Level: 1

Type: WARNING

Impact: Server

BEA-002627: The domain configuration must have at least one administration channel on every server or no administration channels at all.

Cause: The server was contacted by a server that did not reflect the same administration state as itself.

Action: Modify the domain configuration so that all servers have administration channels, or enable the domain-wide administration port.
Level: 1

Type: ERROR

Impact: Server

BEA-002628: Unable to export RemoteLifeCycleOperations RMI object due to {0}.

Cause: The RMI export failed.

Action: Contact My Oracle Support and provide the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002630: Accepting connections again.

Cause: The server is accepting client connections again after refusing connections as part of server throttling.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002631: Max threshold reached for open sockets [total open sockets: {0}, allowed max: {1}]. No more connections allowed.

Cause: The MaxOpenSocketCount attribute of the server configuration defines the upper bound of the number of open sockets.

Action: Increase the MaxOpenSocketCount attribute of the server configuration. Use the server tuning tab in the Administration Console.
Level: 1

Type: WARNING

Impact: Server

BEA-002632: Found jrmp.jar in {0} directory. JRMP service is now enabled.

Cause: JRMP is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002633: A port conflict was detected in the server "{4}" configuration. The server "{4}" is configured to listen on two ports that have the same port number and IP address. Channel "{0}" address "{1}" conflicts with channel "{2}" address "{3}".

Cause: The server is configured to listen on two ports that have the same port number and IP address.

Action: Ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002634: The server "{0}" disconnected from this server.

Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002635: The server "{0}" connected to this server.

Cause: The remote server may have been booted or a network partition may have been resolved.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002636: Unable to update server "{0}" with local channel information.

Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Server

BEA-002637: Failed to register a disconnect listener because of {0}

Cause: This can happen during server startup when the incoming network connection is not suitable for callbacks and the booting server does not yet have a listen port open.

Action: No action is required. The server should eventually be connected properly.
Level: 1

Type: WARNING

Impact: Server

BEA-002638: {0} was issued remotely from {1}.

Cause: Log the host address of the machine that issued the SLC operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002639: ServerRuntime:{0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002640: A request has been received to force a shutdown of the server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002641: -DserverType is set to an unrecognized value: {0}. The server will start with all services enabled.

Cause: An undefined server type was specified or a typographical error was made.

Action: See the WebLogic Server documentation for valid values for -DserverType.
Level: 1

Type: WARNING

Impact: Server

BEA-002642: {0} not found. The server will start with all services enabled.

Cause: The file was deleted or moved.

Action: Replace the file from the WebLogic Server installation.
Level: 1

Type: WARNING

Impact: Server

BEA-002643: Attempt to read {0}, failed: {1}

Cause: The file has been corrupted or had its permissions changed.

Action: Replace the file with one from the WebLogic Server installation.
Level: 1

Type: WARNING

Impact: Server

BEA-002644: The JAR file {0} being processed as a potential service plug-in could not be read: {1}

Cause: The file may be damaged.

Action: Check the file, replace & and try again.
Level: 1

Type: ERROR

Impact: Server

BEA-002645: The manifest of the JAR file {0} being processed as a potential service plug-in, could not be read: {1}

Cause: The manifest may be corrupted.

Action: Replace the file and retry.
Level: 1

Type: ERROR

Impact: Server

BEA-002646: Unable to load the service plug-in activator class from {0}: {1}

Cause: The plug-in JAR file does not meet the service plug-in requirements.

Action: Check the contents of the JAR file and retry.
Level: 1

Type: ERROR

Impact: Server

BEA-002647: The service plug-in, {1}, was added from {0}.

Cause: The plugin was placed in the domain lib directory.

Action: No action is required. To remove the plug-in, remove it from the domain lib directory.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002648: Could not obtain the relevant ServerRuntimeMBean for server {0}.

Cause: The remote server runtime object for server {0} could not be obtained. This can happen if the server has already been shut down or is otherwise unavailable.

Action: If the server is active when this error occurs, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Server

BEA-002649: A port conflict was detected in the server "{3}" configuration. Both TCP and SDP channels are configured to listen on the same port number and IP address. Channels "{0}" and "{1}" on address "{2}".

Cause: Both TCP and SDP channels are configured to listen on the same port number and IP address.

Action: Ensure that the channels with the same [ListenAddress and ListenPort combinations] either all support SDP or do not support SDP.
Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002650: Unable to schedule reconnection to a disconnected server.

Cause: The default timer manager has stopped. This is normal during server shutdown.

Action: None required if the server is in the process of shutting down.
Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002651: The process for the server {0} has not completely shut down. This problem should be reported and you may have to kill the process manually.

Cause: The process for the server {0} has not completely shut down.

Action: Kill the process manually.
Level: 1

Type: ERROR

Impact: Server

BEA-002652: The server has no configured channels.

Cause: The server has no configured channels.

Action: Create or define a correct channel configuration.
Level: 1

Type: ERROR

Impact: Server

BEA-002653: The server's administration channel conflicts with the Administration Server's channel.

Cause: The server's administration channel conflicts with the Administration Server's channel.

Action: Check the server channel configuration and fix the conflicts.
Level: 1

Type: ERROR

Impact: Server

BEA-002654: Initialization Failed: {0}

Cause: Initialization Failed: {0}

Action: Review the returned error and take appropriate action to fix it.
Level: 1

Type: ERROR

Impact: Server

BEA-002655: Cannot dynamically create new channel with admin protocol on Managed server {0} while it is running.

Cause: An attempt was made to create a new channel with admin protocol on Managed server {0} while the server is running.

Action: Shut down the Managed Server and then try creating the channel again.
Level: 1

Type: ERROR

Impact: Server

BEA-002656: Cannot dynamically enable or disable adminstration port on Managed Server {0} while it is running.

Cause: An attempt was made to dynamically enable or disable the adminstration port on Managed Server {0} while the server is running.

Action: Shut down the Managed Server and then try enabling or disabling the port again.
Level: 1

Type: ERROR

Impact: Server

BEA-002657: Cannot change MaxOpenSockCount enablement dynamically on Managed Server {0} while it is running.

Cause: An attempt was made to dynamically change MaxOpenSockCount enablement on Managed Server {0} while the server is running.

Action: Shut down the Managed Server and then try to change MaxOpenSockCount enablement again.
Level: 1

Type: ERROR

Impact: Server

BEA-002658: No configured outbound channel for {0}.

Cause: No configured outbound channel for {0}.

Action: Review the returned error and take appropriate action to fix it.
Level: 1

Type: ERROR

Impact: Server

BEA-002659: Only local HostID is supported {0}.

Cause: Only the local HostID is supported {0}

Action: Check and fix the error.
Level: 1

Type: ERROR

Impact: Server

BEA-002660: Failed to parse replication ports for server {0} port range: {1}.

Cause: Parsing replication ports for server {0} port range: {1} failed.

Action: Check and fix the error.
Level: 1

Type: ERROR

Impact: Server

BEA-002900: Initializing self-tuning thread pool.

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002901: Creating Work Manager "{2}" for module "{0}" and application "{1}"

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002902: Creating execute queue "{0}".

Cause: The server is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002903: Creating Work Manager from "{1}" WorkManagerMBean for application "{0}"

Cause: The application is being initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002905: Removing {0} threads from the thread pool.

Cause: The server has realized that some threads are not needed to handle the present load.

Action: No action is required as the server auto tunes.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002908: Unable to create runtime MBean for Work Manager {0}. {1}

Cause: A fatal error occurred while creating the runtime MBeans.

Action: Contact My Oracle Support with the server logs.
Level: 1

Type: INTERNAL_ERROR

Impact: WorkManager

BEA-002911: Work Manager {0} failed to schedule a request due to {1}

Cause: Work Manager did not schedule a request due to a fatal failure.

Action: This is a critical failure. Report to My Oracle Support with the logs.
Level: 1

Type: INTERNAL_ERROR

Impact: WorkManager

BEA-002912: Overload Manager {0} rejected request as current length {1} exceeds max capacity of {2}

Cause: A request was rejected as the overload capacity was reached or exceeded.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002913: Work Manager {0} rejected request as the server is low on memory

Cause: A request was rejected as the server was low on memory.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002914: Shutdown callback invocation failed with: {0}

Cause: There was an internal error in the application shutdown.

Action: Report to My Oracle Support with the logs.
Level: 1

Type: ERROR

Impact: WorkManager

BEA-002916: Request belonging to Work Manager {0}, application {1} is rejected as the WorkManager is shutdown.

Cause: The request was refused entry because the Work Manager was shutdown.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002917: Enqueued request belonging to Work Manager {0}, application {1} is cancelled as the Work Manager is shutdown.

Cause: The request was refused because the Work Manager was shutdown.

Action: No action was required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002918: Server detected execute queue(s) in self-tuning mode. Execute queues will not be self-tuned. They retain their behavior from earlier releases. Consider using Work Managers to take advantage of self-tuning.

Cause: The execute queues were detected in the self-tuning server.

Action: Consider removing the execute queues. The server automatically adjusts the thread pool size for optimal performance. Work Managers can be used to change the default behavior where needed.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002919: Unable to find a Work Manager with name {0}. Dispatch policy {0} will map to the default Work Manager for the application {1}

Cause: There is no Work Manager with the given name.

Action: This could indicate a configuration error. Check the dispatch-policy and ensure that it matches the name of a Work Manager defined either within the same application or globally.
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002920: An instance of the mSA Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002921: The name of the Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002922: The number of waiting requests in the queue

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002923: The number of requests that have been processed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002924: An instance of the MinThreadsConstraint for a particular Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002925: Completed request count

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002926: Pending requests that are waiting for an available thread

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002927: Number of requests that are currently executing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002928: Number of requests executed out of turn to satisfy this constraint

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002929: Number of requests that must be executed to satisfy the constraint

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002930: The maximum time a request had to wait for a thread. Only requests whose execution is needed to satisfy the constraint are considered.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002931: Number of requests that must be executed to satisfy the constraint

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002932: An instance of the MaxThreadsConstraint for a particular Work Manager

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002933: Number of requests that are currently executing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002934: Number of requests that are denied a thread for execution because the constraint is exceeded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002935: request-class-name reference within ContextCase element for entry {0} with value: {1} ;cannot be resolved for Work Manager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: WorkManager

BEA-002936: maximum thread constraint {0} is reached

Cause: The number of threads assigned to this work manager has reached the configured value in the maximum threads constraint

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002937: The maximum thread constraint {0} is no longer reached.

Cause: The number of threads assigned to this Work Manager has dropped below the configured value in the maximum threads constraint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002938: Global work manager "{0}" created with customized configuration

Cause: The default configuration for a global work manager has been overriden and the work manager is created with a customized configuration

Action: no action needed
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002939: The maximum thread constraint {0} has been reached {1} times for the last {2} seconds.

Cause: The number of threads assigned to this work manager has reached the configured value for the maximum threads constraint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002940: Shutting down work manager "{0}" according to the configured work manager shutdown trigger.

Cause: A work manager is being shut down because the number of stuck threads has reached the configured value in a work manager shutdown trigger.

Action: Monitor the stuck threads to determine the reason why the requests have been taking a long time to process. If resumeWhenUnstuck is true, the work manager will be resumed when there are no more stuck threads for the work manager.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002941: Removed {0} threads from the standby thread pool.

Cause: The server is reducing the number of threads in the standby thread pool either because they are not needed or to reduce overall resource usages of the server.

Action: No action is required as the server auto tunes.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002942: CMM memory level becomes {0}. Setting standby thread pool size to {1}.

Cause: CMM memory level has changed. Standby thread pool size may be adjusted accordingly.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-003000: Could not send cache multicast message for key "{0}", {1}.

Cause: UThis error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: Cache

BEA-003001: Leasing failure: {0}

Cause: This error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: Cache

BEA-003002: Replication failure: {0}

Cause: This error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: Cache

BEA-003004: Unexpected failure {0}

Cause: This is a general purpose warning message.

Action: No action is required. The cache will try to adjust to the failure.
Level: 1

Type: WARNING

Impact: Cache

BEA-003005: CacheFilter not caching the response for uri: {0} reason: {1}

Cause: CacheFilter does not cache responses unless the status is 200.

Action: Check the message for information on how to fix the problem.
Level: 1

Type: WARNING

Impact: Cache

BEA-003090: Could not send cache multicast message for key "{0}", {1}.

Cause: This error is usually caused by some communication failure.

Action: Check the exception message for details.
Level: 1

Type: WARNING

Impact: LLD

BEA-003101: Modified non-dynamic {0} property on the Administration Server.

Cause: The non-dynamic {0} property was updated while the server was in a running state.

Action: Reboot the Administration Server so that the {0} property takes effect.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003102: There was a failure in the execution of the post script {0} while deactivating MigratableTarget {1}. Since post script failure is marked as fatal, the MigratableTarget will not be automatically migrated. To enable automigration, fix the post script failure and manually migrate the failed migratable target or disable the post script failure fatal flag.

Cause: The execution ofthe post deactivation script failed.

Action: Fix the post deactivation script and migrate the MigratableTarget manually.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003103: {0} failed to release its lease because of {1}. This may affect its automatic migration behavior.

Cause: An exception occurred: {1}.

Action: If a database is being used for leasing, ensure that it is available.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003104: Failed to notify the execution failure of the post script {1} for {0} to the SingletonServiceStateManager because of {2}. This may affect its automatic migration behavior.

Cause: An exception occurred: {2}.

Action: Ensure that the network is working properly.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003105: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. This session has not been replicated to any backup at this point.

Cause: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. Once full, the queue waits until it has space for the object. This wait took longer than the ClusterMBean specified AsyncSessionQueueTimeout, thus the session object was not put into the queue and will not be replicated at this time.

Action: This could be due to the secondary server or persistent store slowing down the replication process. To better handle this, the SessionFlushInterval and the SessionFlushThreshold can be reduced to replicate less at a time and to replicate more often. Checking the performance of the secondary server or persistent store is advised.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003106: An unexpected exception occured during replication: {0}. Future session updates should replicate as expected.

Cause: An unexpected runtime exception occured during replication probably from the Remote Management Interface (RMI) stub. Future session updates should replicate as expected.

Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support. with the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003107: Lost {0} unicast message(s).

Cause: This is an informational message. When a server joins a stable cluster, this message will appear since the server did not receive unicast messages sent out by other servers in the cluster.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003108: Unicast receive error : {0}

Cause: An error occurred while trying to receive a message over the cluster broadcast.

Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003109: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.

Cause: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.

Action: Ensure that the data source is created and set for database migration basis.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003110: Connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.

Cause: The connection attempt was rejected because the {1} protocol is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.

Action: Enable the {1} protocol on the channel.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003111: No channel exists for replication calls for cluster {0}

Cause: No channel exists for replication calls for cluster {0}

Action: Configure the channels for replication calls.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003112: Channels "{0}" configured for replication traffic.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003113: Using one-way RMI for replication

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003114: Ignoring one-way RMI calls for replication because multiple replication channels are not present.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003115: Failed to synchronize a secondary session due to missing updates.

Cause: The Work Manager queue might be full and as a result update messages were dropped.

Action: Either increase the number of servers in the cluster (preferred) or add more replication channels (requires server re-start).
Level: 1

Type: ERROR

Impact: Cluster

BEA-003116: Starting Member Death Detector.

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003117: Starting Member Death Detector Heartbeat Receiver.

Cause: None.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003118: WLS Server "{0}" does not have an associated machine configured. Member Death Detector will not be enabled for this server.

Cause: No associated machine configured with the server.

Action: Please associate a machine with this server.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003119: The singleton service {0} is now registered on this server but will not be activated because this server is not part of a cluster.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003120: hostname {0} is failed to resolve in cluster initialization

Cause: name service like DNS is unavailable or unstable.

Action: Please check name service configuration or name service availability.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003121: Unicast cluster may not function correctly as the listen address of server {0} is not specified.

Cause: The listen address of the Managed Server is not specified.

Action: Set the listen address of the Managed Servers.
Level: 1

Type: WARNING

Impact: Cluster

BEA-003122: {0} : A cluster that has migratable servers could not create/execute SQL statement when validating the database connection. The cluster is misconfigured. Check the leasing table on the database and connection configuration.

Cause: The cluster is misconfigured.

Action: Check the leasing table on the database and connection configuration.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003501: The migration of server {0} from machine {1} has failed. No suitable candidate machines could be found.

Cause: No candidate machines are available, or the server {0} has encountered an error on booting independent of its location.

Action: Further migration of server {0} has been disabled. When the cause of the problem has been determined and fixed, the server {0} should be started by the user, at which point it will resume standard automatic migration behavior.
Level: 1

Type: ERROR

Impact: Cluster

BEA-003502: Beginning the migration of server {0} from machine {1} to machine {2}

Cause: The failure of server {0} has provoked a migration attempt to a new machine, machine {2}.

Action: No action is required, but the logs of server {0} should be examined to determine why it crashed and could not successfully restart on machine {1}.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003503: The migration of server {0} from machine {1} to machine {2} has succeeded.

Cause: The failure of server {0} provoked a migration attempt to a new machine, machine {2}. The migration is now complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003504: The migration of server {0} from machine {1} to machine {2} has failed, because machine {2} is not reachable.

Cause: Machine {2} was not reachable. A new machine for server {0} will be chosen.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-010000: Exception occurred during ejbActivate: {0}

Cause: An error occurred while calling ejbActivate() on the bean.

Action: Check your implementation of the ejbActivate method.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010001: While deploying EJB "{0}", class {1} was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.

Cause: The specified class is located in the server classpath.

Action: Remove this class from the server classpath. It should only be located in the packaged application.
Level: 1

Type: WARNING

Impact: EJB

BEA-010002: An error occurred while undeploying: {0}.

Cause: An error occurred while undeploying.

Action: Please check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010003: Exception occurred while loading _WL_TIMESTAMP FILE.

Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. If the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error reading this file.

Action: The container will automatically recompile the beans.
Level: 1

Type: ERROR

Impact: EJB

BEA-010006: Error occurred while saving ejb deployment timestamps. {0}

Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error writing this file.

Action: Please check the exception for the exact error message. The container will recompile the beans if this file is not found.
Level: 1

Type: ERROR

Impact: EJB

BEA-010007: License validation passed for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010008: EJB Deploying file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010009: EJB deployed EJB with JNDI name {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010011: Exception looking up current transaction: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010012: Exception looking up current transaction: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010014: Error occurred while attempting to rollback transaction: {0}

Cause: There was an error when rolling back the transaction.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010015: Error occurred while marking transaction for rollback: {0}.

Cause: The container was unable to mark the transaction for rollback.

Action: Please check the exception for exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010016: Exception occurred while marking transaction for rollback: {0}.

Cause: The container was unable to mark the transaction for rollback.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010017: Exception occurred during rollback of transaction {0}: {1}.

Cause: The container was unable to rollback the transaction.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010018: Error occurred while resuming caller transaction: {0}

Cause: The container was unable to resume the transaction.

Action: Please check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010019: Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.

Cause: The DNS name of the cluster is not set.

Action: Set the DNS cluster name.
Level: 1

Type: WARNING

Impact: EJB

BEA-010020: EJB-20 - MessageDriven - Could not start the JMS connection: {0}

Cause: The JMS provider may not be available, or the Message-Driven Bean deployment descriptors or annotation or both may not be correct.

Action: Verify that the JMS provider is running and accessible through the network. Verify that the deployment descriptors or annotation or both specify the correct configuration information for the JMS provider.
Level: 1

Type: ERROR

Impact: EJB

BEA-010022: Error occurred in ejbPassivate: {0}.

Cause: There was an error passivating the bean.

Action: Please check the exception for the exact error message. Verify the implementation of the ejbPassivate method in the bean.
Level: 1

Type: ERROR

Impact: EJB

BEA-010024: Error occurred during passivation: {0}

Cause: The container was unable to passivate the bean.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010025: Exception occurred during rollback of transaction {0}: {1}

Cause: An error occurred when rolling back the transaction.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010026: Exception occurred during commit of transaction {0}: {1}.

Cause: An error occurred when committing the transaction.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010029: Exception occurred during commit of transaction {0}: {1}.

Cause: An error occurred while committing the transaction.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010030: Ignoring exception that occurred when rolling back a transaction during undeployment of {0}.

Cause: An error occurred while undeploying the bean.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010031: EJB exception in method: {0}: {1}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010032: Exception during ejbActivate(): {0}

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010033: Exception from ejbLoad: {0}

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010034: Exception from ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010036: Exception from ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010038: Exception from __WL_superEjbLoad: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010039: Exception in ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010040: Exception in ejbStore: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010043: Exception in ejbActivate: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010044: Exception trying to resume transaction: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010045: Exception in afterBegin: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010046: Exception in beforeCompletion: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010047: Exception during setRollbackOnly: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010048: Exception in afterCompletion: {0}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010049: EJB exception in method: {0}: {1}.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010050: A stateless session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.

Cause:

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010051: EJB exception occurred during invocation from home: {0} generated exception: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010052: An exception occurred while creating the free pool for EJB {0}. Since this occurred during server startup, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: {1}

Cause: An exception occurred while the EJB container was initializing the free pool of bean instances. The root exception should be printed as part of the warning message issued by the EJB container. Check the server log for further details.

Action: If you believe the root exception is due to a temporary condition that will automatically be resolved, no action is required. If this exception was not due to a temporary condition, fix the cause of the root exception. If changes to your application are required to fix this issue, redeploy the updated application.
Level: 1

Type: WARNING

Impact: EJB

BEA-010054: EJB deployment: {0} has a class {1} that is in the classpath. This class should only be located in the ejb-jar file.

Cause: {1} is in the classpath.

Action: Remove this class from the classpath. It should only be in the ejb-jar.
Level: 1

Type: WARNING

Impact: EJB

BEA-010055: Could not load the RDBMS deployment descriptor for EJB {0} from the file {1}. The file was not found in the JAR file {2}.

Cause: {1} is missing from the JAR file.

Action: Please add the missing file to the JAR file.
Level: 1

Type: ERROR

Impact: EJB

BEA-010057: Could not find a license for EJB 3.0. Please contact Oracle to get a license.

Cause: Unable to get license for EJB 3.0.

Action: Contact Oracle to get a license.
Level: 1

Type: ERROR

Impact: EJB

BEA-010058: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010059: An error occurred while attempting to invalidate the target Read-Only Entity EJB: {0}. The error was: {1}

Cause: The invalidation of read-only beans failed.

Action: Check the message for the cause.
Level: 1

Type: ERROR

Impact: EJB

BEA-010060: The Message-Driven EJB {0} has connected or reconnected to the JMS destination {1}.

Cause: The JMS connection has been re-established.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010061: The Message-Driven EJB {0} is unable to connect to the JMS destination {1}. The Error was: {2}

Cause: The JMS destination is not available due to a network problem or a problem with the JMS provider, or the configuration information in the MDB deployment descriptor or annotation or both is incorrect. This warning may also occur during WebLogic cluster startup if the JMS destination is located on another server.

Action: Check that the JMS provider is running and that network connectivity is available. Also check that the configuration information in the MDB deployment descriptor and/or annotation is correct.
Level: 1

Type: WARNING

Impact: EJB

BEA-010065: MessageDrivenBean threw an Exception in onMessage(). The exception is: {0}.

Cause: The onMessage method of the MDB may have generated an exception for a legitimate reason, such as the loss of a database connection. If that is not the case, then the MDB may have a programming error that causes it to generate an unchecked Java exception, such as a NullPointerException.

Action: Unless you are sure that the MDB has generated the exception on purpose, check the source code to ensure that it does not contain any programming errors that might cause it to generate an unchecked Java exception such as a NullPointerException or IndexOutOfBoundsException.
Level: 1

Type: WARNING

Impact: EJB

BEA-010066: The Entity EJB {0} generated an exception when its unsetEntityContext was called. This error is ignored by the EJB container. The error is: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010067: Exception during ejbRemove: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010071: Error occurred while performing Pop of Caller Principal: {0}

Cause: This is a possible internal container error.

Action: Check the security settings related to the run-as roles and principals setting.
Level: 1

Type: ERROR

Impact: EJB

BEA-010072: Error occurred while starting EJB module {0}. Exception is: {1}

Cause: The container was unable to start the EJB module.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010073: Unable to add the {0} interface "{1}" and any dependent classes to the client-jar since it was loaded from the classpath.

Cause: EJB interface and other dependent classes exist in the system classpath.

Action: Please remove the classes from the system classpath.
Level: 1

Type: WARNING

Impact: EJB

BEA-010074: Unable to create the client-jar file due to classes being loaded from the classpath rather than the input JAR. Please modify your classpath so that it does not contain these classes and try again.

Cause: EJB interface and other dependent classes exist in the system classpath.

Action: Please modify your classpath so it does not contain these classes and try again.
Level: 1

Type: WARNING

Impact: EJB

BEA-010075: Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010076: Client-jar {0} created.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010079: An error occurred while attempting to receive a message from JMS for processing by a Message-Driven Bean: {0} The exception is : {1}

Cause: The JMS provider for the MDB may have been shut down or has crashed, or network connectivity may have been lost.

Action: Check that the JMS provider is available and accessible through the network.
Level: 1

Type: ERROR

Impact: EJB

BEA-010080: An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}

Cause: This error usually occurs if the onMessage method of the MDB throws an exception.

Action: Check that the MDB is able to process messages by ensuring that any resources it uses (such as database connections) are available. Check the MDB source code to ensure that it does not have any bugs that cause an exception (such as a NullPointerException) to be generated.
Level: 1

Type: ERROR

Impact: EJB

BEA-010081: The Message-Driven Bean {0} was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.

Cause: The nature of the JMS API does not permit this in a standard way.

Action: No action is required. However, if you require better performance for a foreign JMS provider and do not need exactly-once transactional semantics, redeploy the MDB so that it has a transaction mode of NotSupported.
Level: 1

Type: WARNING

Impact: EJB

BEA-010082: Failed to undeploy security role for resource {0}, while undeploying EJB.

Cause: Unable to remove the role from the security layer.

Action: Check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: EJB

BEA-010083: Failed to undeploy security policy for resource {0}, while undeploying EJB.

Cause: The policy could not be removed from the security layer.

Action: Check the exception for the exact error message.
Level: 1

Type: WARNING

Impact: EJB

BEA-010084: The Message-Driven Beans are being suspended. This may take a minute or two.

Cause: The server is being suspended or shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010085: The Message-Driven Beans have all been suspended.

Cause: The server is being suspended or shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010086: The deployment unit {0} that contains Message-Driven Beans is undeployed already. The server cannot start the Message-Driven Beans that are part of undeployed unit.

Cause: The beans were started after having been undeployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010087: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes. The generated source files will be placed in {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010088: Could not find a license for in-memory replication of the EJB. This feature is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010089: Failed to create copy of bean {0} with error: {1}.

Cause: The server was unable to create the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010090: Failed to update secondary copy with: {0}

Cause: The server was unable to update the secondary.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010091: Failure during stateful session bean replication: {0}

Cause: The container was unable to replicate the stateful session bean.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010092: Failure while updating secondary server during replication of {0}. The error was: {1}

Cause: The server was unable to update the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010094: Failed to update the secondary copy of a stateful session bean from home {0}.

Cause: The server was unable to update the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010096: The Message-Driven EJB {0} is unable to connect to the JMS destination or bind to JCA resource adapter {1}. The onnection failed after {2} attempts. The MDB will attempt to reconnect/rebind every {3} seconds. This log message will repeat every {4} seconds until the condition clears.

Cause: The JMS provider or JCA resource adapter is not available, or the configuration is incorrect and WebLogic Server is not able to connect.

Action: Ensure that the JMS provider is running and is reachable using the network, or the JCA resource adapter is deployed. Also ensure that the configuration information in the MDB deployment descriptor or the annotation or both are correct.
Level: 1

Type: WARNING

Impact: EJB

BEA-010097: Exception occurred during the invocation of EJB {0} with primary key {1}.

Cause: The bean generated a system exception.

Action: Check the exception for the exact error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010098: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.

Cause: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.

Action: Check the database-type tag inside weblogic-cmp-rdbms-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-010099: WARNING(S) from EJB QL Compiler. {0}

Cause: The compilation of EJB-QL succeeded. These are some non-fatal warnings.

Action: Check the message for the exact warnings.
Level: 1

Type: WARNING

Impact: EJB

BEA-010100: This server is not part of a cluster. Therefore the InMemory replication feature for StatefulSession EJB {0} will have no effect on this server.

Cause: The bean has been deployed on a server, which is not a part of cluster. Hence the InMemory replication feature will be ignored.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-010102: Error encountered while attempting to create default DBMS table {0}. Error text: {1}

Cause: An error was encountered while attempting to create the default DBMS table.

Action: Take appropriate action based on the logged error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010124: Method SecurityHelper.{0} returned a NULL principal. The CallerPrincipal stack has been corrupted.

Cause: One cause of corruption might be that a bean has created its own threads. Note that this would be in violation of EJB2.0 Final Spec Chapter: Runtime Management 24.1.2.

Action: Review your code about thread safety. If a bean does not create its own thread, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.
Level: 1

Type: ERROR

Impact: EJB

BEA-010127: Incorrect data source type detected. The data source with JNDI name {0}, specified in the RDBMS deployment descriptor for the EJB {1}, does not support global transactions.

Cause: The EJB container requires that a data source which supports global transactions be specified for transactions to be managed correctly.

Action: Specify the correct data source for the EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010128: Error during deployment of EJB {0}. The EJB references an application-level cache, {1}, that is not defined in the weblogic-application.xml descriptor.

Cause: The weblogic-ejb-jar.xml descriptor for the EJB refers to an unknown application-level cache.

Action: Ensure that the application-level cache is defined in the weblogic-application.xml descriptor and ensure the cache name defined in the weblogic-ejb-jar.xml is correct.
Level: 1

Type: ERROR

Impact: EJB

BEA-010129: Error during deployment of EJB {0}. The EJB references a MultiVersion application-level cache {1}, but it must use an Exclusive cache instead. EJBs with a concurrency-strategy of Exclusive must use an Exclusive cache.

Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.

Action: Specify the correct concurrency strategy.
Level: 1

Type: ERROR

Impact: EJB

BEA-010130: An error occurred during deployment of EJB {0}. The EJB references an Exclusive application level cache {1}, but it must use a MultiVersion cache instead. EJBs with a concurrency-strategy of Database, ReadOnly, or Optimistic must use a MultiVersion cache.

Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.

Action: Specify the correct concurrency strategy.
Level: 1

Type: ERROR

Impact: EJB

BEA-010132: Error during deployment of EJB {0}. The EJB has been deployed with use-select-for-update set to true. The database indicates it does not support SELECT ... FOR UPDATE.

Cause: The database indicates it does not support SELECT ... FOR UPDATE.

Action: Modify use-select-for-update to false, or use a different database that supports SELECT ... FOR UPDATE.
Level: 1

Type: ERROR

Impact: EJB

BEA-010139: Bean with primary key {0} already exists.

Cause: A bean with the indicated primary key value already exists.

Action: Do not use a non-unique value as a primary key.
Level: 1

Type: ERROR

Impact: EJB

BEA-010141: Creation of Many-To-Many relationship for primary key: {0} and {1} effected {2} rows in {3}, instead of just 1.

Cause: JoinTable contains a non-unique row for specified primary keys, indicating a Many-To-Many relationship.

Action: Check the JoinTable to remove the duplicate row.
Level: 1

Type: ERROR

Impact: EJB

BEA-010144: The setXXX method for a primary key field may only be called during ejbCreate.

Cause: The setXXX method for a primary key field may only be called during ejbCreate.

Action: Remove the setXXX method call (for a primary key field) from places other than ejbCreate.
Level: 1

Type: ERROR

Impact: EJB

BEA-010145: When a cmp-field and a cmr-field (relationship) are mapped to the same column, the setXXX method for the cmp-field may not be called.

Cause: The cmp-field is read-only.

Action: Remove the setXXX method call if cmp-filed is also used as cmr-field.
Level: 1

Type: ERROR

Impact: EJB

BEA-010146: The setXXX method for a cmr-field that is mapped to a primary key may not be called.

Cause: The cmr-field is read-only.

Action: Remove the setXXX method call if it is cmr-field mapped to a primary key.
Level: 1

Type: ERROR

Impact: EJB

BEA-010147: The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.

Cause: The setXXX method should be called during ejbPostCreate instead.

Action: Move the setXXX method call for a cmr-field to ejbPostCreate.
Level: 1

Type: ERROR

Impact: EJB

BEA-010148: In EJB {0}, the primary key field {1} was not set during ejbCreate.

Cause: All primary key fields must be initialized during ejbCreate.

Action: Be sure to initialize the primary key field during ejbCreate.
Level: 1

Type: ERROR

Impact: EJB

BEA-010149: According to the EJB 2.0 specification, a value of "null" may not be assigned to a collection valued cmr-field.

Cause: This violates the EJB 2.0 specification.

Action: Avoid using a null argument for a collection valued cmr-field.
Level: 1

Type: ERROR

Impact: EJB

BEA-010152: Illegal value for concurrency-strategy. Value was {0}, but must be one of ReadOnly, Exclusive, Database, or Optimistic.

Cause: An illegal value was used for concurrency-strategy.

Action: Specify a correct value for concurrency-strategy. It must be one of ReadOnly, Exclusive, Database, or Optimistic
Level: 1

Type: ERROR

Impact: EJB

BEA-010153: Only instances of beans with a remote client view can invoke getEJBObject().

Cause: See the error message body.

Action: Remove the getEJBObject() method call from the local client.
Level: 1

Type: ERROR

Impact: EJB

BEA-010154: Only instances of beans with a local client view can invoke getEJBLocalObject().

Cause: See the error message body.

Action: Remove the getEJBLocalObject() method call from remote client.
Level: 1

Type: ERROR

Impact: EJB

BEA-010155: Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().

Cause: See the error message body.

Action: Remove the getRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010156: Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction

Cause: See the error message body.

Action: Make sure to begin the transaction before calling the getRollbackOnly() method.
Level: 1

Type: ERROR

Impact: EJB

BEA-010157: Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().

Cause: See the error message body.

Action: Remove the setRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010158: Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction

Cause: See the error message body.

Action: Begin the transaction before calling the setRollbackOnly() method.
Level: 1

Type: ERROR

Impact: EJB

BEA-010159: To support the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, {0}, was deployed without specifying a JNDI name. To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Cause: This EJB, {0}, was deployed without specifying a JNDI name.

Action: To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
Level: 1

Type: ERROR

Impact: EJB

BEA-010160: Security violation: User {0} has insufficient permission to access EJB {1}.

Cause: The specified user has insufficient permission to access the EJB.

Action: Grant sufficient permissions to the user to enable to access the EJBResource.
Level: 1

Type: ERROR

Impact: EJB

BEA-010166: Error occurred while starting transaction: {0}.

Cause: An exception occurred while starting the Message-Drive Bean transaction.

Action: Take appropriate action based on the text of the exception message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010167: Message-Driven Beans are not allowed to call {0}.

Cause: The method is unavailable for MDBs.

Action: Remove the method call from the MDBs.
Level: 1

Type: ERROR

Impact: EJB

BEA-010168: Method {0} has been declared in an assembly-descriptor exclude-list and cannot be executed.

Cause: The specified method is declared in the exclude-list.

Action: Remove the method name from the exclude-list or remove the method call.
Level: 1

Type: ERROR

Impact: EJB

BEA-010173: env-entry for type java.lang.Character had length = 0.

Cause: If there is env-entry for type java.lang.Character, the parameter value should not be length = 0.

Action: Use a non-zero length value for java.lang.Character env-entry.
Level: 1

Type: ERROR

Impact: EJB

BEA-010188: Error encountered while attempting to drop Default DBMS Table {0}.

Cause: See the exception stack trace included in the logged message.

Action: Take appropriate action based on the exception stack trace in the logged message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010189: Error encountered while attempting to alter Default DBMS Table: {0}.

Cause: See the exception stack trace included in the logged message.

Action: Take appropriate action based on the exception stack trace in the logged message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010191: The alter table option is not supported in {0}. Use the DropAndCreate option.

Cause: The alter table option is not supported in the given database.

Action: Use the DropAndCreate option.
Level: 1

Type: ERROR

Impact: EJB

BEA-010194: Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().

Cause: An illegal invocation was made to the getUserTransaction() method on a Container Managed Bean.

Action: Remove the getUserTransaction() method call from EJBs that are using container-managed transaction.
Level: 1

Type: ERROR

Impact: EJB

BEA-010195: Security violation: User {0} has insufficient permission to access method {1}.

Cause: The specified user has insufficient permission to access the specified method.

Action: Grant sufficient permissions to the user to enable access to the method.
Level: 1

Type: ERROR

Impact: EJB

BEA-010197: The entity bean {0} uses optimistic concurrency with read-verification enabled. The database indicates that exclusive row locks are not supported. Read-verification will not guarantee data integrity if the isolation level of the transaction is lower than repeatable read.

Cause: This is a mismatch problem between the concurrency strategy and the transaction isolation level.

Action: If data integrity should be guaranteed under a read-verification enabled configuration, use the appropriate transaction isolation level.
Level: 1

Type: WARNING

Impact: EJB

BEA-010198: An exception occurred while uninitializing the EJB module {0}.

Cause: Check the exception for the exact cause.

Action: Check the exception for the exact error message, and take appropriate action.
Level: 1

Type: WARNING

Impact: EJB

BEA-010199: EJB {0} with run as role {1} has no run-as-principal-name specified in its deployment descriptor or annotation. The EJB container has chosen principal-name {2} from the security-role-assignment list for role {1} to be the run as principal name.

Cause: The specified EJB with the specified run as role has no run-as-principal-name specified in its deployment descriptor or annotation.

Action: Specify run-as-principal-name explicitly if the chosen principal-name is not the appropriate one.
Level: 1

Type: WARNING

Impact: EJB

BEA-010201: The Message-Driven Bean {0} encountered an error while recovering a JMS session. This is a secondary error. The original error occurred while the Message-Driven Bean was processing a message. The recover action was taken in an attempt to recover from the original error, which will be logged separately.

Cause: The Message-Driven Bean may have generated an exception, or there may be a problem with the JMS provider.

Action: Check that the JMS provider is running and accessible through the network. In addition, check that the Message-Driven Bean onMessage method does not generate any unchecked Java exceptions such as NullPointerException or IndexOutOfBoundsException.
Level: 1

Type: ERROR

Impact: EJB

BEA-010202: Call-by-reference is not enabled for EJB {0}. The server will have better performance if it is enabled. To enable call-by-reference, set the enable-call-by-reference element to True in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Cause: Call-by-reference is not enabled.

Action: If appropriate, enable call-by-reference in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for the EJB.
Level: 1

Type: WARNING

Impact: EJB

BEA-010204: The EJB component, {0}, will be rolled back and redeployed to update class {1}. This class is not a bean implementation class. Only bean implementation classes can be updated without redeploying the entire module, and only when enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml.

Cause: A command was issued to update the specified class.

Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed, since this can cause disruption to clients using an EJB in this EJB module.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010205: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. Bean implementation classes, such as this, can be updated without redeploying the entire EJB module. However, this can only be done if enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml or the corresponding annotation. If this is the behavior you want, set this value to True and redeploy.

Cause: A command was issued to update the specified class.

Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010206: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. This bean implementation class could not be updated without redeploying the entire EJB module because it was changed incompatibly. Incompatible changes are any changes that cause the EJB compiler to be run. This includes modifying a public variable name or a public method signature.

Cause: A command was issued to update the specified class.

Action: No action is necessary. This is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010207: License validation not passed for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010208: ddl-file {0} created.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010209: ddl-file {0} could not be deleted.

Cause:

Action: Check the file permissions.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010210: Unable to write to ddl-file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010211: Unable to alter the table, as the primary key has changed.

Cause:

Action: Use the DropAndCreate option to create the table.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010212: The EJB {0} contains at least one method without an explicit transaction attribute setting. The default transaction attribute of {1} will be used for the following methods: {2}.

Cause: The ejb-jar.xml deployment descriptor or corresponding annotation does not contain transaction attribute settings for the specified EJB methods.

Action: Assign transaction attributes for all methods of your EJB.
Level: 1

Type: WARNING

Impact: EJB

BEA-010213: Message-Driven EJB: {0}'s transaction was rolled back. The transaction details are: {1}.

Cause: The transaction was rolled back by the MDB container.

Action: This is an informational message. No action is needed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010214: Error starting MDB {0}.

Cause: This error itself does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: ERROR

Impact: EJB

BEA-010215: The durable subscription store with jms-client-id equal to {0} is deleted when MDB {1} is removed from the server.

Cause: The durable subscription store is deleted when the MDB is removed from the server and its durable-subscription-deletion is set to true.

Action: This is an informational message. No action is needed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010216: The Message-Driven EJB: {0} is generating an exception when processing the messages. Delivery failed after {1} attempts. The EJB container will suspend the message delivery for {2} seconds before retry.

Cause: The Message-Driven Bean is generating an exception.

Action: Check the message delivery methods and resolve the exception condition.
Level: 1

Type: WARNING

Impact: EJB

BEA-010221: The Message-Driven EJB: {0} is unable to bind to the JCA resource adapter: {1}. The Error was: {2}

Cause: The JCA resource adapter is not deployed, or the configuration information in the MDB deployment descriptor or corresponding annotation is incorrect.

Action: Check that the JCA resource adapter is deployed and the configuration information in the MDB deployment descriptor or corresponding annotation is correct.
Level: 1

Type: WARNING

Impact: EJB

BEA-010222: The aggregate query {0} has a primitive return type but the query returned null because there were no values to which to apply the aggregate function.

Cause: There were no values to which to apply the aggregate function

Action: Handle ObjectNotFoundException correctly on the application side.
Level: 1

Type: ERROR

Impact: EJB

BEA-010223: EJB deployed Message Driven Bean {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010224: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. The container will delay the timeout for {2} milliseconds as configured for the timer.

Cause: This was caused by a failed ejbTimeout.

Action: It is possible that no action needs to be taken. However, it may be good to investigate why the original ejbTimeout failed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010225: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. Since no retry delay was configured for this timer, the container will automatically delay the timeout for {2} seconds.

Cause: This was caused by a failed ejbTimeout.

Action: It is possible that no action needs to be taken. However, it may be good to investigate why the ejbTimeout has consecutively failed.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010226: Error executing clustered EJB timer for EJB {0} of module {1} of application {2}. While executing, the timer was unable to find a necessary internal resource required to execute. The most likely cause of this issue is that the EJB is no longer configured to use the clustered EJB timer service but timers still exist in the database.

Cause: The most likely cause of this error is that the EJB associated with this timer is no longer configured to use the clustered EJB timer service.

Action: If the EJB in question is no longer configured to use EJB timers, the timers associated with it should be removed from the database. This can be achieved by re-enabling clustered EJB timers for the EJB and then undeploying the EJB. This will cause any timers associated with the EJB to be removed from the database.
Level: 1

Type: ERROR

Impact: EJB

BEA-010227: EJB exception occurred during invocation from home or business: {0} generated exception: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010228: Failed to update the secondary copy of a stateful session bean business: {0}.

Cause: The server was unable to update the secondary server.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-010230: EJB {0} : method name {1} and method name {2} are equal under case-insensitive comparison but both methods have declarative security settings. Declarative security checks are case-insensitive.

Cause: Both of the specified methods have declarative security settings.

Action: Avoid case-insensitive method name conflicts if method permissions are configured.
Level: 1

Type: WARNING

Impact: EJB

BEA-010231: The lock request from EJB {0} with primary key {1} timed-out after waiting {3} ns. The transaction or thread requesting the lock was {2}.

Cause: See error message body.

Action: See error message body.
Level: 1

Type: ERROR

Impact: EJB

BEA-010232: The version of EJB in Module "{0}" is "{1}". However, the deprecated "enable-bean-class-redeploy" feature is not supported in EJB 3.

Cause: See error message body.

Action: Use the FastSwap feature instead and remove the "enable-bean-class-redeploy" settings in the weblogic-ejb-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-010233: The configuration of "MessagesMaximum" is ignored for non Weblogic JMS.

Cause: See error message body.

Action:
Level: 1

Type: WARNING

Impact: EJB

BEA-011047: In ejb-jar.xml or annotation, EJB {0} has container-transactions set when the EJB has a transaction-type of Bean. The container-transaction settings will be ignored.

Cause: The specified EJB has container-transactions set when the EJB has a transaction-type of Bean.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-011057: The table {0} was created by the user. The container does not drop or alter user-created tables. The container would verify the table in this case.

Cause: The table was already created by the user.

Action: Drop the table if the existing table is not correct. The container will then be able to create the table.
Level: 1

Type: WARNING

Impact: EJB

BEA-011059: The container was unable to create the DDL file.

Cause: This error does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.

Action: Inspect the log file for indications of the root cause of the failure.
Level: 1

Type: WARNING

Impact: EJB

BEA-011061: Stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011062: The following exception has occurred:

Cause: An error condition was reported.

Action: Review the stack trace, which will help with debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011063: Stateless session beans with bean-managed transactions must commit or roll back their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an Exception without properly completing a transaction.

Cause: A transaction started by the stateless session bean method did not complete before the method completed.

Action: Check the bean code to determine what caused the transaction to not commit or roll back, and fix code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
Level: 1

Type: ERROR

Impact: EJB

BEA-011070: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <field-group>(s) are defined but are not used in any <weblogic-query>, <weblogic-relationship-role> or <relationship-caching> <caching-element>s. The <group-name>(s) of the unreferenced <field-group>(s) are: {1}

Cause: Some field group definitions are not referenced in any query or relationship.

Action: Remove the field groups listed in the logged message from the descriptor or include its usage appropriately.
Level: 1

Type: WARNING

Impact: EJB

BEA-011071: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <relationship-caching>(s) are defined but are not used in any <weblogic-query>. The <caching-name>(s) of the unreferenced <relationship-caching>(s) are: {1}

Cause: There are unused relation cachings defined in the weblogic-rdbms descriptor.

Action: Remove the unused relationship cachings listed in the logged message from the descriptor or include its usage appropriately.
Level: 1

Type: WARNING

Impact: EJB

BEA-011073: An error occurred while the EJB container was attempting to obtain information about the table {0} from the database. This information is necessary to validate the mapping between the fields of the EJB {1} and the table. The exception is: {2}

Cause: The most likely cause is an error communicating with the database. The error message should include the specific error message.

Action: The action depends on the specific error that occurred. Actions may range from retrying the failed deployment to seeking help from your database administrator. Also, ensure that you are using a supported database.
Level: 1

Type: ERROR

Impact: EJB

BEA-011076: Unable to deploy the EJB {0} because the database table {1} is not accessible. Ensure that this table exists and is accessible.

Cause: A required database table was not accessible.

Action: Ensure that the database table exists and is accessible.
Level: 1

Type: ERROR

Impact: EJB

BEA-011077: The EJB deployment contains settings for automatically creating or altering database tables. However, the server is in production mode, so no database tables will be created or altered.

Cause: The server is in production mode so the create-default-dbms-tables settings are being ignored.

Action: No action is required. To suppress the warning, remove the create-default-dbms-tables setting from your EJB deployment.
Level: 1

Type: WARNING

Impact: EJB

BEA-011078: An exception occurred while starting the freepool idle timeout timer for ejb: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011079: An exception occurred while stopping the freepool idle timeout timer for ejb: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011080: An exception occurred while starting the Cache idle timeout timer for cache: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011081: An exception occurred while stopping the Cache idle timeout timer for cache: {0}, {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011082: Error: The message-destination-link {0} for the Message-Driven Bean {1} in the application module {2} could not be resolved. The target message-destination for the Message-Driven Bean could not be found. Ensure that the link is correct.

Cause: The target of the message-destination-link could not be found in the application.

Action: Fix the message-destination-link to point to a valid message-destination.
Level: 1

Type: ERROR

Impact: EJB

BEA-011083: The EJB specification prohibits stateful session beans from using the TimerService.

Cause: An illegal call was made to the getTimerService() method on the stateful session beans SessionContext.

Action: Correct the stateful session bean code so that it does not call the getTimerService() method from the bean class.
Level: 1

Type: ERROR

Impact: EJB

BEA-011084: This EJB class does not support EJB timers and therefore is prohibited from using the TimerService. To use EJB timers, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.

Cause: An illegal call to the getTimerService() method on the EJBContext.

Action: Correct the EJB class so it either implements the javax.ejb.TimedObject interface or ensure that it does not call the getTimerService() method on the EJBContext.
Level: 1

Type: ERROR

Impact: EJB

BEA-011085: This timer has either expired or been canceled and therefore cannot be invoked.

Cause: An illegal call to a timer object after the timer had expired or was canceled.

Action: Ensure your bean class does not invoke expired or canceled timers.
Level: 1

Type: ERROR

Impact: EJB

BEA-011086: The timer associated with this TimerHandle has either expired or been canceled.

Cause: The timer associated with the TimerHandle has expired or been canceled.

Action: No action is required.
Level: 1

Type: ERROR

Impact: EJB

BEA-011087: This TimerHandle is being invoked outside of the context of the application in which it was created. Since timers are local objects, they can only be called from within the same application in which they were created.

Cause: This TimerHandle is being invoked outside of the context of the application in which it was created.

Action: Ensure that your application does not pass any TimerHandle references outside of the scope of the application.
Level: 1

Type: ERROR

Impact: EJB

BEA-011088: The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB {0}.

Cause: This could be caused by erroneous code in the ejbTimeout method or by the failure of a dependent resource.

Action: All exceptions that occur while invoking or attempting to invoke the ejbTimeout method should be investigated and resolved. If the ejbTimeout method is non-transactional, that is, has a transaction attribute of NotSupported, or if the bean uses bean-managed transactions, the ejbTimeout method may not be retried, leading to missed timeout notifications.
Level: 1

Type: ERROR

Impact: EJB

BEA-011089: The following error occurred while attempting to remove an EJB timer from the persistent store for EJB {0}.

Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.

Action: This cause of this error should be investigated and resolved promptly.
Level: 1

Type: ERROR

Impact: EJB

BEA-011090: The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB {0}.

Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.

Action: All exceptions that occur while attempting to invoke the ejbTimeout method should be investigated and resolved.
Level: 1

Type: ERROR

Impact: EJB

BEA-011091: The table {0} cannot be dropped or created since it uses a trigger to update the optimistic column of the EJB. The container will only verify the existence of the table.

Cause: The table uses a trigger to update the optimistic column of the EJB.

Action: To suppress this warning, set the create-default-dbms-tables value in the RDBMS deployment descriptor to Disabled.
Level: 1

Type: WARNING

Impact: EJB

BEA-011092: In production mode, the DropAndCreate, DropAndCreateAlways, and AlterOrCreate options are ignored. The container will only attempt to verify the existence and increment value of the sequence {0}.

Cause: Options that apply only to development mode are ignored in production mode.

Action: Do not use these values for Automatic Oracle SEQUENCE Generation in production mode.
Level: 1

Type: WARNING

Impact: EJB

BEA-011093: The SEQUENCE named {0} with INCREMENT {1} was not found in the database. This SEQUENCE was specified in the CMP deployment descriptor to be used for automatic primary key generation.

Cause: The SEQUENCE was not found.

Action: Examine the <automatic-key-generation> tag in the CMP deployment descriptor. In particular, re-examine the <generator-name> and verify that this is the correct name of the SEQUENCE. Also, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
Level: 1

Type: ERROR

Impact: EJB

BEA-011094: The SEQUENCE named {0} does not have INCREMENT value of {1} in the database as specified in the CMP deployment descriptor. Either modify the key-cache-value for this SEQUENCE in the deployment descriptor or update the SEQUENCE in the database.

Cause: The SEQUENCE named {0} does not have an INCREMENT value of {1} in the database as specified in the CMP deployment descriptor.

Action: In the <automatic-key-generation> tag of the CMP deployment descriptor, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
Level: 1

Type: ERROR

Impact: EJB

BEA-011095: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}. {2}

Cause: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}.

Action: The message contains the cause of the error. See the message body and resolve the reported error.
Level: 1

Type: ERROR

Impact: EJB

BEA-011096: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}. {2}

Cause: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}.

Action: The message contains the cause of the error. See the message body and resolve the reported error.
Level: 1

Type: ERROR

Impact: EJB

BEA-011097: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}. {2}

Cause: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}.

Action: The message contains the cause of the error. See message body and resolve the reported error.
Level: 1

Type: ERROR

Impact: EJB

BEA-011098: No generated primary key was returned from the database insert statement as expected. Verify that the primary key database column for this EJB is an IDENTITY column as declared in the CMP deployment descriptor for this EJB.

Cause: This is most likely caused by a database configuration error. It may also be caused by a JDBC driver that does not support the getGeneratedKeys() method on java.sql.Statement.

Action: Verify that the primary key column in the database is marked as an IDENTITY column (or a functional equivalent is setup for the column such as a database trigger to insert a value into the primary key column).
Level: 1

Type: ERROR

Impact: EJB

BEA-011099: Multiple generated keys were returned from the database insert statement. The EJB container is unable to determine which generated key corresponds to the primary key column. To use the IDENTITY primary key generator, you must only have a single automatically generated database column per EJB.

Cause: This is most likely caused by a database configuration error. Each EJB may only have a single automatically generated database column.

Action: Verify that the database table corresponding to the EJB only has a single generated column.
Level: 1

Type: ERROR

Impact: EJB

BEA-011109: Failed to register JACC policy context handlers for the EJB container.

Cause: An unexpected error condition occurred while registering JACC context policy handlers.

Action: See the error message stack trace for details on how to resolve this issue.
Level: 1

Type: ERROR

Impact: EJB

BEA-011110: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database. This may generate missing keys.

Cause: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database.

Action: In the <automatic-key-generation> tag, re-examine the <key-cache-size> and verify that it is set correctly.
Level: 1

Type: WARNING

Impact: EJB

BEA-011111: The SEQUENCE named {0} has key-cache-size set to {1} which is greater than the INCREMENT_BY value for the sequence in the database. This is not allowed as it may generate duplicate keys.

Cause: The key-cache-set size for the SEQUENCE is not valid.

Action: in the <automatic-key-generation> tag, re-examine the <key-cache-size> and set it to a value less than or equal to the INCREMENT_BY value for the sequence in the database.
Level: 1

Type: ERROR

Impact: EJB

BEA-011120: The CMP EJB {0} has enable-batch-operations set to true. The update queries, however, are not suitable for batching. Batched operations are turned off for this batch and the queries will be executed with multiple update statements.

Cause: Batching is turned off for update queries.

Action: No action is required.
Level: 1

Type: WARNING

Impact: EJB

BEA-011121: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.

Cause: The plugin-class could not be found in the server classpath.

Action: Add the plugin-class in the server classpath.
Level: 1

Type: ERROR

Impact: EJB

BEA-011122: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be instantiated.

Cause: The plugin-class could not be instantiated.

Action: Add the plugin-class in the server classpath.
Level: 1

Type: ERROR

Impact: EJB

BEA-011123: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.

Cause: The plugin-class could not be accessed.

Action: Add the plugin-class in the server classpath.
Level: 1

Type: ERROR

Impact: EJB

BEA-011124: Error in Message-Driven Bean EJB {0}. The plugin-class {1} does not implement weblogic.ejb.spi.SecurityPlugin.

Cause: The plugin-class does not implement weblogic.ejb.spi.SecurityPlugin.

Action: Make the plugin-class implement weblogic.ejb.spi.SecurityPlugin.
Level: 1

Type: ERROR

Impact: EJB

BEA-011125: An unexpected error was encountered while attempting to remove any EJB timers from the persistent store for the EJB {0}.

Cause: An unexpected error occurred while attempting to remove EJB timers from the persistent store.

Action: See the particular error message for details about the error. If your application is failing to deploy because of this error, it may be necessary to manually remove the timers from the store.
Level: 1

Type: ERROR

Impact: EJB

BEA-011126: The same exception has consecutively caused the expiration to fail for EJB timer {0}. Consecutive errors of this type will no longer be logged for the current timer expiration.

Cause: The same exception has consecutively caused expiration of an EJB timer to fail.

Action: Investigate what caused the ejbTimeout method to fail. The original exception will be logged in a previous error message.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011127: Error deserializing one or more EJB timers from the persistent store for the EJB deployment {0}. An incompatible change to the class of a Serializable object associated with the timer may be the cause. If this is the case, you can either undeploy your application entirely to remove the EJB timers from the persistent store or revert the incompatible changes to the Serializable class so the EJB timer can be deserialized. The error was: {1}

Cause: A common cause of this error is an incompatible serializable class change in your application.

Action: If the error is due to an incompatible serializable class change in your application, there are two options for dealing with the serialization errors. The first option is to completely undeploy the EJB. which will cause all of the EJB timers in the persistent store to be permanently removed. The second option is to revert changes to the serializable class that is associated with the EJB timer and redeploy the application. This allows the EJB timer to be deserialized.
Level: 1

Type: ERROR

Impact: EJB

BEA-011128: Error creating an instance of the EJB {0}: {1}

Cause: See the reported error message for the cause. This error may be due to a configuration issue or a bug in the EJB container.

Action: See the specific error message for details and take appropriate action.
Level: 1

Type: ERROR

Impact: EJB

BEA-011129: Error deploying EJB {0} to server {1}. This EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.

Cause: It is illegal to deploy an EJB that uses clustered EJB timers to a server that is not part of a cluster.

Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or ensure that any servers to which you deploy the EJB are part of a cluster.
Level: 1

Type: ERROR

Impact: EJB

BEA-011130: Error deploying EJB {0}. This EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler cluster attribute is not configured.

Cause: While deploying this EJB, the EJB container determined the data-source-for-job-scheduler cluster attribute has not been set.

Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or configure the data-source-for-job-scheduler attribute for your cluster.
Level: 1

Type: ERROR

Impact: EJB

BEA-011132: Error deploying EJB {0}. While binding a business interface to the JNDI name {1}, the following error occurred: {2}

Cause: See the specific error for details.

Action: The action to take depends on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.
Level: 1

Type: ERROR

Impact: EJB

BEA-011135: The EJB {0} is a singleton session bean. EJB 2.1 client views are not supported for singleton session beans.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011136: wasCancelCalled() should only be invoked from within an asynchronous business method invocation with return type Future.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011137: A singleton session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011138: Singleton session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an exception without properly completing a transaction.

Cause: A transaction started by the singleton session bean method did not complete before the method completed.

Action: Check the bean code to determine what caused the transaction to not commit or roll back and fix the code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
Level: 1

Type: ERROR

Impact: EJB

BEA-011139: The following exception occurred when processing the asynchronous invocation : {0}.

Cause: There error was encountered during the asynchronous invocation.

Action: See the exception stack trace for details.
Level: 1

Type: ERROR

Impact: EJB

BEA-011140: The argument {0} is not a valid local client view for the EJB {1}.

Cause: The argument is not a valid local client view for the EJB.

Action: Review the EJB configuration and calling code to determine the discrepancy.
Level: 1

Type: ERROR

Impact: EJB

BEA-011141: This EJB has already been removed.

Cause: The EJB has already been removed.

Action: Avoid the call for removed objects.
Level: 1

Type: ERROR

Impact: EJB

BEA-011142: Error creating EJB reference: {0}

Cause: An exception occurred while creating an EJB reference.

Action: The reported exception contains the root cause of the issue. Review the exception to identify the exact problem.
Level: 1

Type: ERROR

Impact: EJB

BEA-011143: Error removing stateful session bean: {0}

Cause: An unexpected error occured while trying to remove a stateful session bean.

Action: The reported exception has the root cause of the issue. Review the exception to identify the actual problem.
Level: 1

Type: ERROR

Impact: EJB

BEA-011144: Singleton EJB {0} failed to initialize.

Cause: A singleton EJB {0} failed to initialize.

Action: The message body has the root cause of the issue. Review it to identify the essential problem.
Level: 1

Type: ERROR

Impact: EJB

BEA-011145: Illegal call to a Write method from a Thread holding Read lock.

Cause: An illegal call to a Write method was made

Action: Remove or rewrite the call.
Level: 1

Type: ERROR

Impact: EJB

BEA-011146: Timed out while trying to aquire lock on Singleton {0} to invoke method {1}.

Cause: A timeout occurred while trying to aquire a lock.

Action: Check Singleton concurrency. A timeout has been reached.
Level: 1

Type: ERROR

Impact: EJB

BEA-011147: Singleton {0} is in use by another thread.

Cause: While this Singleton is being invoked, it cannot be called from other threads.

Action: Check Singleton concurrency.
Level: 1

Type: ERROR

Impact: EJB

BEA-011148: Singleton {0} not initialized as Singleton {1} from the DependsOn transitive, closure failed initialization.

Cause: A singleton was not initialized as a Singleton from the DependsOn transitive, closure failed initialization.

Action: Check the server log for the cause of the dependent Singleton initialization error and resolve it.
Level: 1

Type: ERROR

Impact: EJB

BEA-011149: The EJB {0} contains an illegal value for the activation config property MessagesMaximum. The specified value is {1} but the legal values are -1, and 1 through 2^63-1.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-011223: Cannot invoke stateful callback on {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011224: Unable to bind the interface {0} to {1}. Another EJB has already bound an interface to that name.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011225: Unable to bind the interface {0} to {1}. This EJB has declared another interface already bound to that name.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011226: Error during {0}. Could not get connection: {1} {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011227: Error during finder {0}. Exception while preparing query: {1} {2} {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011232: Error during finder {0}. Exception while setting parameters for query {1} {2} {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011233: Error during finder {0}. Exception while executing query {1} {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011234: Could not find an EJB with a field that is mapped to table {0} and column {1}. The SQL query is {2}. Try using an SqlShape annotation to describe the query results or check that the SqlShape annotation in use is correct.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011235: Error in {0}, could not map relationship {1} role {2} to an EJB populated by the query {3}. EJBs populated by this query are: {4}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011236: Error executing finder {0}: SqlShape {1} contains {2} columns, but the result set returned by JDBC contains {3} columns. The number of columns in the SqlShape and the JDBC result set must match.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011237: A stored procedure or function is used by {0}, but no SqlShape is specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011238: Error in {0}. SQL query {1} does not select column values for all primary key fields of bean {2}. No columns were selected for the following fields: {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011239: Query-caching is not supported for read-write beans.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011240: Error obtaining nativeQuery: {0}, {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011241: An attempt was made to do an executeQuery on query {0}, using a non-WebLogic EntityManager.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011242: Internal Error: Extended Persistence Context has been closed!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011243: attempt at illegal state transaction from {0} to {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011244: An illegal call was made to the EJBContext method. getMessageContext can only be called from SLSBs with web-service endpoint interfaces.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011245: The EJB {0} is not an EJB3.0 bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011246: The EJB {0} does not declare a {1} home interface.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011247: The EJB {0} does not implement the business interface {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011248: The bean has not been invoked through a business interface.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011249: It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011250: It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011251: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011252: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateful session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011253: It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a stateless session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011254: It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a stateless session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011255: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateless session bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011256: Single expiration timers cannot be cancelled from within ejbTimeout.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011257: It is illegal to invoke Timer methods in ejbRemove or a PreDestroy method from asession bean or Message-Driven Bean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011258: It is illegal to invoke Timer methods in ejbActivate or a PostActivate method.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011259: It is illegal to invoke Timer methods in ejbPassivate or a PrePassivate method.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011260: It is illegal to invoke Timer methods during a dependency injection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011261: Invocation timed out. Timer is busy.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011262: Error cancelling timer

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011263: EjbJarBean is not set yet.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011264: Method {0} is marked TX_NEVER, but was called within a transaction.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011265: Unexpected exception in afterDelivery(): {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011266: An attempt was made to execute getDatabaseProductName using a non-WebLogic EntityManager.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011267: Error calling getDatabaseProductName: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011268: An attempt was made to execute nativeQuery on query {0}, using a non-WebLogic EntityManager.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011269: Error obtaining nativeQuery: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011270: Error preparing query: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011276: An illegal attempt was made to make a re-entrant call to a stateful session bean: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011277: An illegal attempt was made to make a re-entrant call to a stateful session bean from home: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011278: The following dependency that was declared by {0} is not a Singleton Session Bean: {1}.

Cause: A dependency that was specified by a Singleton Session Bean must also be a Singleton Session Bean.

Action: Remove the illegal dependency from the dependency list or replace it with a Singleton Session Bean.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011279: The following exception occured in PreDestroy processing for singleton session bean {0}: {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-012030: Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE {0} not permitted. Only DOCTYPE {1} permitted here.

Cause: An illegal DOCTYPE was used.

Action: Make sure to update appropriate DOCTYPE to the descriptor file.
Level: 1

Type: ERROR

Impact: EJB

BEA-012031: The EJB {0} has a finder {1} for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases.

Cause: The deprecated sql-select-distinct attribute was used.

Action: Use the EJB-QL DISTINCT clause instead. The container will automatically filter duplicates if necessary.
Level: 1

Type: WARNING

Impact: EJB

BEA-012032: For EJB {0}, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The EJB method referred to by the weblogic-query element is {1}.

Cause: The weblogic-query element references a wrong or non-existent query method for this entity EJB.

Action: Remove the weblogic-query element or update it so that it references the correct query method.
Level: 1

Type: WARNING

Impact: EJB

BEA-012033: Compiling generated EJB classes produced the following Java compiler output: {0}

Cause: While compiling EJB generated classes, the Java compiler produced output.

Action: Typically, there is no action to take. The Java compiler output is printed for informational purposes. If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-012035: The Remote interface method: {0} in EJB {1} contains a parameter of type {2} which is not serializable. Though the EJB {1} has call-by-reference set to false, this parameter is not serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is serializable.

Cause: The EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is serializable. As this parameter is not serializable, the parameter will be passed by reference.

Action: The parameter should implement the java.io.Serializable interface for it to be passed by value.
Level: 1

Type: WARNING

Impact: EJB

BEA-012036: Compiling generated EJB classes produced the following Java compiler error message: {0}

Cause: While compiling EJB generated classes, the Java compiler produced output.

Action: If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.
Level: 1

Type: ERROR

Impact: EJB

BEA-012037: In weblogic-ejb-jar.xml or annotation, a singleton-session-descriptor element was found for EJB {0}. This EJB was not declared as a singleton session bean in ejb-jar.xml or annotation.

Cause: There is an incompatible configuration between weblogic-ejb-jar.xml and ejb-jar.xml.

Action: Modify weblogic-ejb-jar.xml or ejb-jar.xml to keep configuration consistency whether singleton or non-singleton.
Level: 1

Type: ERROR

Impact: EJB

BEA-014000: Problem, encountered illegal value for transaction-isolation {0}.

Cause: See the error message body.

Action: Specify one of the following legal values: TransactionSerializable, TransactionReadCommitted, TransactionReadCommittedForUpdate, TransactionReadCommittedForUpdateNoWait, TransactionReadUncommitted, or TransactionRepeatableRead.
Level: 1

Type: ERROR

Impact: EJB

BEA-014001: RDBMS descriptor {0} contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console.

Cause: The specified RDBMS descriptor contains transaction-isolation settings.

Action: Move the isolation-level settings to the weblogic-ejb-jar.xml descriptor.
Level: 1

Type: ERROR

Impact: EJB

BEA-014003: EJB {0} uses optimistic concurrency and contains a finder or select method, {1}, for which include-updates is true. This combination of features does not work properly with database {2}.

Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks, unless Oracle is used as the database. Oracle read consistency does not hold read locks, so in this case reads are performed using the current JTA transaction. When reads are performed in a local transaction updates that have been flushed prior to commit of the transaction are not visible.

Action: Set include-updates for the query to false to avoid this warning message, or if you are using Oracle as your database, set the database-type to Oracle in weblogic-cmp-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-014004: In EJB {0}, <generator-type> is set to {1}. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.

Cause: These are database limitations.

Action: Turn off automatic-key-generation in order to use batch operations.
Level: 1

Type: WARNING

Impact: EJB

BEA-014005: The configured dispatch policy {1} for Message-Driven Bean (MDB) {0} will be ignored: the MDB is not running in a WebLogic thread.

Cause: The queue MDB is driven asynchronously by a non-WebLogic JMS implementation and runs in a non-WebLogic thread mechanism, so the MDBs application thread pool is not configurable.

Action: To disable this warning, remove the dispatch-policy setting from the MDBs WebLogic descriptor file.
Level: 1

Type: WARNING

Impact: EJB

BEA-014006: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.

Cause: The specified MDB named has a dispatch policy that refers to an unknown execute queue thread pool.

Action: Create an execute thread queue pool for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing execute queue thread pool.
Level: 1

Type: WARNING

Impact: EJB

BEA-014007: The bean named {0} contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified. This may result in corruption of BLOB and CLOB data.

Cause: The specified bean contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified.

Action: Specify "version" or "timestamp" in the <table-map> <verify-columns> element and specify the name of the <version> or <timestamp> column in the <optimistic-column> element.
Level: 1

Type: WARNING

Impact: EJB

BEA-014008: In EJB {0}, {1} references an SqlShape element {2} that is not defined. The list of SqlShape elements that are defined for this EJB is: {3}.

Cause: An undefined SqlShape element was referenced.

Action: Use an existing SqlShape or create the SqlShape that you wish to use.
Level: 1

Type: WARNING

Impact: EJB

BEA-014009: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS destination {2} and a new application version {3} is being redeployed.

Cause:

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014010: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS topic {2} and a new application version {3} is being redeployed. Note also that the current Message-Driven Bean is not a durable subscriber to the topic, and messages published by the topic after the currently active version of the Message-Driven Bean is suspended may not be received by the new application version.

Cause: The specified Message-Driven Bean listens to the specified global JMS topic and a new application version is being redeployed.

Action: To ensure that the new application version will receive all messages published while the Message-Driven Bean was suspended, set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.
Level: 1

Type: WARNING

Impact: EJB

BEA-014011: EJB {0} uses optimistic-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. This combination of features is incompatible. The use-select-for-update is turned off by the EJB container in this case.

Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks. The element use-select-for-update in the RDBMS deployment descriptor when set to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the table. This conflicts with the Optimistic Concurrency strategy.

Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014012: EJB {0} uses optimistic-concurrency and disables cluster invalidation, but does not have verify-rows set to Read. This combination will prevent detection of stale data if the bean is never modified in a transaction.

Cause: Optimistic concurrency beans verify consistency of data only if the bean has been modified, unless verify-rows is set to Read. If some other member of a cluster modifies a bean, other members will not be notified of this modification and will continue to store stale data unless the other members also attempt to modify the bean.

Action: Set either of the elements verify-rows to Read or cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014013: EJB {0} does not have a concurrency-strategy of either optimistic or readOnly and disables cluster invalidation. Cluster invalidation is relevant only for these concurrency strategies.

Cause: When an EJB is using either optimistic or readOnly concurrency-strategy and is deployed to a cluster, the container invalidates such beans on modification to avoid throwing OptimisticConcurrencyExceptions. This invalidation can be turned off by setting the cluster-invalidation-disabled to true in the RDBMS deployment descriptor.

Action: Set cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014014: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown work manager. The default work manager will be used instead.

Cause: The specified MDB has a dispatch policy that refers to an unknown work manager.

Action: Create a work manager for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing work manager.
Level: 1

Type: WARNING

Impact: EJB

BEA-014016: EJB {0} uses readonly-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is read-only, select-for-update is unnecessary.

Cause: Read-only beans cannot be updated. Therefore, use-select-for-update is unnecessary.

Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014017: EJB {0} uses exclusive-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is locked at the server level during a transaction, select-for-update on the database is unnecessary.

Cause: Exclusive concurrency is implemented by locking the bean at the server level when the bean participates in a transaction. Setting the element use-select-for-update in the RDBMS deployment descriptor to true causes SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the row in the database too. This may be unnecessary, as the bean is locked by the container.

Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014018: EJB {0} uses a verify-columns element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.

Cause: verify-columns is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.

Action: Remove verify-columns element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014019: EJB {0} uses a verify-rows element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.

Cause: verify-rows is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.

Action: Remove the verify-rows element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014020: EJB {0} uses an optimistic-column element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.

Cause: optimistic-column element is applicable only for optimistic concurrency beans. If the bean does not use optimistic concurrency, this element will be ignored.

Action: Remove the optimistic-column element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1

Type: WARNING

Impact: EJB

BEA-014021: The EJB {0} has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014022: {0} is bound with JNDI name {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015000: The following exception occured while processing annotations: {0}.

Cause: See the exception to determine the cause.

Action: See the exception to determine the action to take.
Level: 1

Type: ERROR

Impact: EJB

BEA-015001: Unable to link class {0} in Jar {1} : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015002: Unable to load class {0} in Jar {1} : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015003: Unable to create virual Jar {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015004: The super class {0} of session bean class {1} is also a session bean class.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015005: The session type is not set in the deployment descriptor or annotation for session bean {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015007: No ejbCreate method was found for init method {0} in bean {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015008: No matching create method for @Init method {0} in bean {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015009: Could not load interceptor class {0}: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015010: In bean {0}, there are multiple method permission annotations for method {1}, which is illegal.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015011: There are multiple method permission annotations for class {0}, which is illegal.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015012: Unable to load interface class {0}: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015013: Bean class {0} does not implement interface method {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015014: ServiceEndpoint class {0} was specified but cannot be found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015015: The super class {0} of Message-Driven Bean class {1} is also a Message-Driven Bean class.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015016: Message-Drive Bean {0} does not implement the message listener interface, has no messaging-type specified in the deployment descriptor, or has no messageListenerInterface specified by using @MessageDriven annotation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015017: In bean class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015018: In interceptor class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015022: {0} is not valid in this context. Bean class: {1}.

Cause: {0} is not valid in this context. Bean class: {1}.

Action: Remove {0} from the invalid location.
Level: 1

Type: ERROR

Impact: EJB

BEA-015023: {0} is not valid in this context. Bean method: {1}.{2}.

Cause: {0} is not valid in this context. Bean method: {1}.{2}.

Action: Remove {0} annotation from invalid location.
Level: 1

Type: ERROR

Impact: EJB

BEA-015024: Could not specify @JNDIName on local business interface {0} of Bean {1}.

Cause: The @JNDIName could not be specified on the local business interface {0} of Bean {1}.

Action: Remove the annotation from the local business interface.
Level: 1

Type: ERROR

Impact: EJB

BEA-015025: Unable to load a class that is specified in your ejb-jar.xml: {0}.

Cause: A class that is specified in your ejb-jar.xml cannot be loaded.

Action: Check ejb-jar.xml in the EJB JAR file.
Level: 1

Type: ERROR

Impact: EJB

BEA-015026: Reference name {0} of @{1} annotation on class {2} is not unique.

Cause: Reference name {0} of @{1} annotation on class {2} is not unique.

Action: Change the reference name {0} of @{1} annotation on class {2}.
Level: 1

Type: ERROR

Impact: EJB

BEA-015027: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.

Cause: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.

Action: Make the Message-Driven EJB non-transactional, or use a different connection factory that supports XA.
Level: 1

Type: ERROR

Impact: EJB

BEA-015028: The EJB {0} contains an illegal value for the activation config property DistributedDestinationConnection. The specified value is {1} but the legal values are EveryMember and LocalOnly.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015029: The EJB {0} contains an illegal value for the activation config property TopicMessagesDistributionMode. The specified value is {1} but the legal values are Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015030: The EJB {0} has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topics work with Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application, but partitioned distributed topics only work with One-Copy-Per-Server or One-Copy-Per-Application. The EJB is configured to partitioned distributed topic and Compatibility.

Cause: See the error message body.

Action: Review the compatibility of distributed topic types and topicMessagesDistributionMode and fix them.
Level: 1

Type: ERROR

Impact: EJB

BEA-015031: The EJB {0} has a distributedDestinationConnection configured but the EJB is configured to connect to a remote cluster. Since the distributedDestinationConnection configuration is only valid in a local cluster, the setting will be ignored.

Cause: See the error message body.

Action: Connect to a local cluster, or remove the distributedDestinationConnection configuration.
Level: 1

Type: WARNING

Impact: EJB

BEA-015032: The EJB {0} is configured with the activation config property topicMessagesDistributionMode but the EJB is configured to connect to a JMS Queue. The topicMessagesDistributionMode is valid only for JMS Topic destinations.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015033: The EJB {0} has an invalid value configured for the activation config property {1}. Only WebLogic JMS server 10.3.4 or later versions support the values One-Copy-Per-Server or One-Copy-Per-Application. Prior to 10.3.4.0 Weblogic JMS server or other non-Weblogic JMS vendors, only the Compatibility value is supported.

Cause: See the error message body.

Action: Correct the activation config property.
Level: 1

Type: ERROR

Impact: EJB

BEA-015034: This destinaiton {1} is a remote replicated distribution topic which does not support durable subscriptions when the Message-Drive Bean {0} works in Compatibility mode.

Cause: See the error message body.

Action: Review and fix the compatibility of the activation config property SubscriptionDurability and topicMessagesDistributionMode.
Level: 1

Type: ERROR

Impact: EJB

BEA-015035: The EJB {0} is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.

Cause: See the error message body.

Action: Change distributed-destination-connection to EveryMember to remove the warning.
Level: 1

Type: WARNING

Impact: EJB

BEA-015036: In the EJB {0}, the value for the activation config property {1} will be ignored since it is overridden with the value {2}.

Cause: See the error message body.

Action: To remove this warning, remove the duplicated configuration from the activation config property.
Level: 1

Type: WARNING

Impact: EJB

BEA-015037: In EJB {0}, the throws clause for method {1} in the bean class contains exceptions that are NOT in the throws clause of the corresponding {2} interface method.

Cause: See the error message body.

Action: Correct the throws clause. Implementation methods must have all exceptions that are provided by the corresponding interfaces.
Level: 1

Type: WARNING

Impact: EJB

BEA-015038: Problems definitively matching up the interface method {0} with a method in the bean class. Please modify your bean class to implement the interface {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015039: Cannot start an inactive Message-Driven Bean {0}. A redployment may be needed.

Cause: See the error message body.

Action: Redeploy the application and restart it.
Level: 1

Type: ERROR

Impact: EJB

BEA-015040: The Message-Driven Bean {0} is inactive now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015041: The Message-Driven Bean {0} is active now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015042: The JNDI name {0} is set for {1} home interface of EJB {2}, but cannot find {1} home in deployment descriptor. Specify {1} home in ejb-jar.xml.

Cause: See the error message body.

Action: Specify {1} home in ejb-jar.xml.
Level: 1

Type: WARNING

Impact: EJB

BEA-015043: A concurrent-call attempt failed on a stateful session bean instance because the lock was held by another thread or transaction, either because concurrent-access is prohibited or access could not be granted in a specific time period. You may change the concurrent-access behavior using the @AccessTimeout annotation or a corresponding element in deployment descriptor.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015044: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.

Cause: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.

Action: Remove @JNDIName from either {1} or {2}.
Level: 1

Type: ERROR

Impact: EJB

BEA-015045: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.

Cause: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.

Action: Remove @JNDIName from {0} or provide the class name of each client view.
Level: 1

Type: ERROR

Impact: EJB

BEA-015046: Illegal operation, context data is not supported for the Entity Bean.

Cause: An illegal operation has occurred, context data is not supported for the Entity Bean.

Action: Remove the retrieval operation for the Entity Bean's context data.
Level: 1

Type: ERROR

Impact: EJB

BEA-015047: Unable to bind portable JNDI name {0}.

Cause: The portable JNDI name could not be bound. See the exception for the cause.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: EJB

BEA-015048: This EJB class does not have a timeout method. To use TimerService, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.

Cause: User is trying to create timer but the corresponding EJB doesn't have a timeout method.

Action: Correct the EJB class and add a timeout method.
Level: 1

Type: ERROR

Impact: EJB

BEA-040010: JMSServer "{0}" configured {1,choice,0#no session pools|1#1 session pool|2#{1} session pools}.

Cause: This message indicates the number of session pools that were configured or deployed for the JMSServer while processing the configuration file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040014: Failed to start JMSServer. JMS is shutting down.

Cause: The JMS server failed to initialize.

Action: Modify the configuration and restart the server file. Then reboot the system. There should be earlier messages that indicate the cause of the failure.
Level: 1

Type: ERROR

Impact: JMS

BEA-040015: JMS shutdown is complete.

Cause: JMS has been shut down, either at the request of the administrator or due to configuration errors.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040017: JMSServer "{0}" connection factory JNDI binding failed, {1}. JMS is shutting down.

Cause: An error was found when binding the connection factory to a JNDI name during configuration.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040018: Could not obtain a replicated or non-replicated InitialContext from the default provider, {0}.

Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.

Action: Modify the configuration and restart the server file. Then reboot the server.
Level: 1

Type: ERROR

Impact: JMS

BEA-040019: JMSServer "{0}" failed to bind to JNDI name: {1}.

Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040024: JMSServer "{0}" byte threshold for destination {1} has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040025: JMSServer "{0}" byte threshold condition for destination {1} has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040026: JMSServer "{0}" message threshold for destination {1} has been exceeded.

Cause: This is an informational message.

Action: No action
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040027: JMSServer "{0}" message threshold condition for destination {1} has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040028: JMSServer "{0}" byte threshold for the server has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040029: JMSServer "{0}" byte threshold for server has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040030: JMSServer "{0}" message threshold for the server has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040031: JMSServer "{0}" message threshold for the server has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040068: JMSServer "{0}" error occurred while unregistering destination {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040069: JMSServer "{0}" error occurred while unregistering producer {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040070: JMSServer "{0}" error occurred while unregistering connection {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040071: JMSServer "{0}" error occurred while unregistering session {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040072: JMSServer "{0}" error occurred while unregistering consumer {1}.

Cause: Look for earlier messages that might explain the error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040089: JMSServer "{0}". JMS messages in store ({1}) were migrated from version {2} to 600.

Cause: Message migration happens automatically when starting JMS and an old store exists.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040090: Deployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.

Cause: This message indicates the number of default connection factories deployed while processing the configuration file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040095: JMSServer "{0}". Store I/O failure, {1}.

Cause: There is no more of file space, a disk failure occurred, or a database failure occurred.

Action: Restart the database, if applicable, and restart JMS.
Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040107: Undeployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.

Cause: This message indicates the number of default connection factories that were undeployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040108: User connection factory "{0}" is started.

Cause: The specified user connection factory has been started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040109: JMSServer "{0}" is started.

Cause: The specified JMS Server has been started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040113: JMSServer "{0}", Opening file store "{1}" in directory "{2}". Starting scan of {3,choice,0#0 files|1#1 file|2#{3} files} totaling {4} bytes.

Cause: A JMS server has opened its persistent file store and is about to scan its contents for messages.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040119: Failed to deploy a JMS connection factory "{0}" due to {1}.

Cause: The JMS connection factory failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new connection factory.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040120: Failed to bind JMS connection factory "{0}" with its JNDI name due to {1}.

Cause: This is a JNDI failure.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040121: JMSServer "{0}". Cannot be deployed on multiple servers.

Cause: A JMS Server was deployed on more than one WebLogic Server instance, and this is not allowed.

Action: Change the configuration file and reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040122: Failed to deploy JMS Server "{0}" due to {1}.

Cause: The JMS server failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040123: Failed to start JMS Server "{0}" due to {1}.

Cause: A JNDI failure occurred, or there was a failure when starting destinations, server session pools and/or connection consumers.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040124: JMSServer "{0}". Failed to create JMS server session pool "{1}" due to {2}.

Cause: The JMS server session pool failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server session pool.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040125: JMSServer "{0}". Failed to create JMS connection consumer "{1}" due to {2}.

Cause: The JMS connection consumer failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS connection consumer.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040127: Failed to create JMS multicast socket due to {0}.

Cause: The JMS multicast socket failed to initialize.

Action: Reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040215: JMS server "{0}". Cannot set "{1}" to -1 when paging is enabled. The value of the attribute remains unchanged.

Cause: This is caused by an invalid configuration.

Action: Disable paging before setting this value to -1.
Level: 1

Type: ERROR

Impact: JMS

BEA-040305: JMS service is initialized and in standby mode.

Cause: The initialization phase of the JMS service is completed and the JMS service is in standby mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040306: JMS service is active now.

Cause: The activation phase of the JMS service is completed, and the JMS service is in active mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040307: JMS service is suspending gracefully.

Cause: The JMS service has started the suspension phase. No new work will be accepted and JMS Service will attempt to complete all existing work before it brings itself to standby mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040308: JMS service is suspending.

Cause: The JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040321: JMSServer "{0}" is resuming.

Cause: The JMSServer "{0}" is resuming.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040324: JMSServer "{0}" is suspending.

Cause: The JMSServer "{0}" is suspending.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040325: JMSServer "{0}" is suspended.

Cause: The JMSServer "{0}" is suspended.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040351: ExpiredJMSMessage JMSMessageID={0} > {1} {2} </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040352: ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log the message header fields so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040353: ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log the messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040354: ExpiredJMSMessage JMSMessageID={0} > </ExpiredJMSMessage

Cause: A message has been expired and the policy is to log only the MessageId, or there are no matching message header fields or message properties.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040359: Distributed Destination "{0}", member "{1}" is not associated with a physical destination.

Cause: This was caused by a onfiguration error.

Action: Modify the configuration and restart the server.
Level: 1

Type: WARNING

Impact: JMS

BEA-040368: The following exception has occurred:

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help in debugging an existing problem.
Level: 1

Type: ERROR

Impact: JMS

BEA-040370: Linked Exception -----------

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040371: JMSServer "{0}" JMS server session pool is invalid and has not been started "{1}". Exception is "{2}".

Cause: The server session pool is invalid because it has an invalid Connection Factory or Listener.

Action: Edit the JMS session pool, verify that it has valid attributes, and reboot the server. Alternatively, delete the session pool and add a new valid JMS session pool.
Level: 1

Type: ERROR

Impact: JMS

BEA-040372: JMSServer "{0}" error occurred while unregistering the runtime MBean, {1}.

Cause: Unable to contact the Administration Server or unable to find the runtime MBean.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040373: Could not find a license for JMS. Please contact Oracle to get a license.

Cause: Unable to get a license for JMS.

Action: Contact your Oracle sales representative to get a license.
Level: 1

Type: ERROR

Impact: JMS

BEA-040376: Destination {0} has been paused for new message production.

Cause: A Production Pause request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040377: Destination {0} has been resumed for new message production.

Cause: A Production Resume request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040378: Destination {0} has been paused for insertion of messages from in-flight work completion.

Cause: An Insertion Pause request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040379: Destination {0} has been resumed for insertion of messages from in-flight work completion.

Cause: An Insertion Resume request was issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040380: Destination {0} has been paused for consumption.

Cause: A Consumption Pause request has been issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040381: Destination {0} has been resumed for consumption.

Cause: A Consumption Resume request has been issued for the specified destination.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040382: JMSServer {0} has been paused for new message production.

Cause: A Production Pause request was issued for the specified JMSServer.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040383: JMSServer {0} has been resumed for new message production.

Cause: A Production Resume request was issued for the specified JMSServer.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040384: JMSServer {0} has been paused for insertion of messages from in-flight work completion.

Cause: An Insertion Pause request was issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040385: JMSServer {0} has been resumed for insertion of messages from in-flight work completion.

Cause: An Insertion Resume request has been issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040386: JMSServer {0} has been paused for consumption.

Cause: A Consumption Pause request has been issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040387: JMSServer {0} has been resumed for consumption.

Cause: A Consumption Resume request has been issued for the specified JMS server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040404: Foreign JMS Server "{0}" is started.

Cause: The specified foreign JMS server was started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040405: Failed to bind an entity of Foreign JMS Server "{0}" with their JNDI names due to {1}.

Cause: This was caused by a JNDI failure.

Action: Modify the JMS module descriptor of the corresponding application and redeploy the application.
Level: 1

Type: ERROR

Impact: JMS

BEA-040406: Distributed destination "{0}" is started.

Cause: The specified distributed destination was started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040407: Default connection factory "{0}" with its JNDI name "{1}" is started.

Cause: The specified default connection factory was started.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040408: Failed to bind default connection factory "{0}" with its JNDI name "{1}" due to {2}.

Cause: This was caused by a JNDI failure.

Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1

Type: ERROR

Impact: JMS

BEA-040409: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} {2} </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040410: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040411: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040412: FailedJMSMessage for store-and-forward: JMSMessageID={0} > </FailedJMSMessage

Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log only the MessageId. Alternatively, there are no matching message header fields or message properties.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040420: The JMS transaction branch {1} for destination {0} was administratively committed.

Cause: This was caused by an administrative action.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040421: An administrative request to commit the JMS transaction branch {1} on destination {0} failed with the following exception. {2}

Cause: The cause of the failure may be indicated by the exception provided in the error message.

Action: The transaction may be in an invalid state to allow commit processing. Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040422: The JMS transaction branch {1} for destination {0} was administratively rolled back.

Cause: This was caused by an administrative action.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040423: An administrative request to rollback the JMS transaction branch {1} on destination {0} failed with the following exception. {2}

Cause: The cause of the failure may be indicated by the exception provided in the error message.

Action: Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040430: The "UserTransactionsEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.

Cause: A deprecated attribute was used.

Action: Use the XAConnectionFactoryEnabled attribute instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040431: The "XAServerEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.

Cause: A deprecated attribute is used.

Action: Use the XAConnectionFactoryEnabled attribute instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040442: While attempting to bind JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI.

Cause: Some other entity has already bound this JNDI name globally.

Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040443: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.

Cause: Some other entity has already bound this JNDI name globally.

Action: Determine the owner the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040444: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised globally.

Cause: A network connection between the local server and the Administration Server may have gone down.

Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.
Level: 1

Type: WARNING

Impact: JMS

BEA-040445: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.

Cause: Some other entity has already bound this JNDI name locally.

Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040446: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised locally.

Cause: A network connection between the local server and the Administration Server may have gone down.

Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.
Level: 1

Type: WARNING

Impact: JMS

BEA-040447: While attempting to bind the JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI locally.

Cause: Some other entity has already bound this JNDI name locally.

Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1

Type: WARNING

Impact: JMS

BEA-040448: JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "{0}" has been replaced in the configuration with a FileStoreMBean with the same name.

Cause: A deprecated MBean was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040449: JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "{0}" has been replaced in the configuration with a JDBCStoreMBean with the same name.

Cause: A deprecated MBean was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040450: The "PagingStore" attribute on the JMSServerMBean "{0}" has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.

Cause: A deprecated MBean attribute was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040451: The PagingStore attribute on the JMSServerMBean {0} has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory.

Cause: A deprecated MBean attribute was replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040452: The server session pool feature has been deprecated, and it will be removed in an upcoming release. New applications should use message-driven beans (MDBs) instead.

Cause: A deprecated feature was detected in the configuration.

Action: Plan to replace use of server session pools in your application.
Level: 1

Type: WARNING

Impact: JMS

BEA-040453: The BytesPagingEnabled and MessagesPagingEnabled parmeters on the JMSServer {0} have been deprecated. These parameters are now ignored. The MessageBufferSize parameter should be used to configure paging in this release.

Cause: A deprecated parameter was encountered.

Action: Plan to use the new MessageBufferSize to control paging.
Level: 1

Type: WARNING

Impact: JMS

BEA-040455: Flow control has been enabled on JMS server "{0}" because memory is low

Cause: Too much memory is being used.

Action: Either increase the amount of memory available to the server, or decrease the MessageBufferSize parameter on the JMS server so that fewer messages remain in memory.
Level: 1

Type: WARNING

Impact: JMS

BEA-040456: An entity of type "{3}" with name "{2}" in JMS module "{0}" is not targeted. There is no subdeployment with name "{1}" in the configuration repository (config.xml). Therefore, this entity will not exist anywhere in the domain.

Cause: The entity of the given name and type in the given JMS module does not have a corresponding subdeployment in the configuration repository (config.xml). In order for this entity to exist in the domain, it must be targeted with a sub-deployment element.

Action: Add a sub-deployment stanza to the appropriate deployment descriptor in config.xml. This will either be a jms-system-resource for a system module, or an app-deployment for a stand-alone JMS deployable module. If the JMS module is inside a J2EE application (an EAR file), then you must add the sub-deployment stanza to the subdeployment that represents this JMS module in the J2EE application. You do not necessarily have to target the subdeployment yet. Simply adding the subdeployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain you must target the sub-deployment.
Level: 1

Type: WARNING

Impact: JMS

BEA-040457: The Template named "{1}" element of Distributed Destination "{0}" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.

Cause: An unsupported attribute JMSTemplate is used in a Distributed Destination.

Action: Use a Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040458: Unable to unprepare {0} in module {1} due to {2}.

Cause: The prepared entity could not unprepare itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040459: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040460: Unable to close the JMS component of module {0} due to {1}.

Cause: The JMS component could not close itself.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040461: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: Refer to the available exception for more information.
Level: 1

Type: WARNING

Impact: JMS

BEA-040464: Unable to destroy {0} in module {1} due to {2}.

Cause: The initialized entity could not destroy itself in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040467: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040470: Unable to deactivate {0} in module {1} due to {2}.

Cause: The activated entity could not deactivate itself during dynamic deletion.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040475: The destination {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases, a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040476: The destination {0} does not have an associated quota object. The setting of messagesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040477: An error occurred while unbinding a remote JNDI object from local JNDI name "{0}". The exception encountered was {1}.

Cause: There may be an error in the JNDI subsystem. See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040478: The JMS subsystem could not deploy or undeploy the default JMS connection factories due to {0}.

Cause: There may be an error in the JNDI subsystem. See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040479: The system failed to roll back an added connection consumer of name {0}. The exception received was {1}.

Cause: See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040480: The system failed to remove a connection consumer of name {0}. The exception received was {1}.

Cause: See the exception for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: JMS

BEA-040490: {0} {1} has a conflicting name attribute value, which is now changed to have a unique name with its JMSServer name. The new destination-name attribute now holds the original name value.

Cause: A name conflict has been detected during upgrade for JMS destinations, maybe because in WebLogic Server versions prior to 9.2, more than one destination was allowed to have the same name, as long as the destinations belonged to different JMS servers.

Action: Ensure that destinations are created with their name decorated with the target JMS server name to avoid conflict.
Level: 1

Type: WARNING

Impact: JMS

BEA-040491: A {0} {1} with multiple targets has been split into multiple deployments one for each unique target.

Cause: A JMS Deployment found with multiple unique targets configured.

Action: In WebLogic Server versions prior to 9.2, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, cluster, or both. During upgrade of this configuration to WebLogic Server 9.2, these configuration entities are split into more than one entity, one for each unique target.
Level: 1

Type: WARNING

Impact: JMS

BEA-040494: An error occurred while shutting down the JMS server {0}: {1}.

Cause: See the detail message.

Action: The server should still shut down normally. No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040496: The template {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040497: The template {0} does not have an associated quota object. The setting of MessagesMaximum to {1} will have no effect.

Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.

Action: Consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1

Type: WARNING

Impact: JMS

BEA-040498: An error occurred while forwarding a message for distributed destination member {0}: {1}

Cause: There may be a temporary network problem, or one of the members of the cluster may be unavailable.

Action: See the detail message.
Level: 1

Type: WARNING

Impact: JMS

BEA-040499: An error occurred while pushing messages to a JMS client: {0}

Cause: There may be a network failure.

Action: The JMS protocol will recover automatically from such a problem eventually. Check for networking issues or crashed clients.
Level: 1

Type: WARNING

Impact: JMS

BEA-040500: Unable to deactivate entity "{0}" in module "{1}" due to {2}.

Cause: The activated entity could not rollback the proposed targeting change.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040501: Unable to roll back targeting change of the entity "{0}" in module "{1}" due to {2}.

Cause: The changed entity could not roll back in a failure case.

Action: More information may be available from the exception.
Level: 1

Type: WARNING

Impact: JMS

BEA-040502: While attempting to change the targeting of JMS module "{0}", an error occurred while activating the change. The exception returned is: {1}

Cause: The JMS module failed to activate a prepared change during a targeting update.

Action: More information may be available from the exception.
Level: 1

Type: ERROR

Impact: JMS

BEA-040503: The delivery mode override value of destination "{0}" hosted on JMS server "{1}" has been changed from {2} to {3}.

Cause: During the upgrade process, a configuration was detected that would force all messages through the given destination to be non-persistent. Therefore, the upgrade process made that override explicit.

Action: Review your application code and configuration. If you need a behavior other than the one that the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMS server on which the destination is targeted.
Level: 1

Type: WARNING

Impact: JMS

BEA-040504: While attempting to add an entity with name "{0}", an error occurred while trying to convert the old style entity to the new style entity. The error was "{1}".

Cause: See the description of the exception that occurred for more information on the cause of this failure.

Action: Take appropriate action based on the determined cause.
Level: 1

Type: WARNING

Impact: JMS

BEA-040505: The JMS module named "{0}" inside application "{1}" does not have a sub-deployment stanza named "{0}". Without such a stanza, no entities inside the module will be deployed, since the subdeployments inside of the sub-deployment stanza named "{0}" control where JMS entities inside this module are targeted.

Cause: When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.

Action: Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment, you can target the entities in the module as you normally would.
Level: 1

Type: WARNING

Impact: JMS

BEA-040506: The JMS store-and-forward (SAF) forwarder has successfully connected to the remote destination "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040507: The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "{0}", because of {1}.

Cause: This is either due to a configuration error, a network failure, or the remote destination being temporarily unavailable.

Action: Check the configuration, network connection, or remote destination.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040508: BridgeDestinationMBean has been deprecated. The BridgeDestination "{0}" has been replaced in the configuration with a JMSBridgeDestination with the same name.

Cause: A deprecated MBean is being replaced in the configuration.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMS

BEA-040509: Failed to ${1} JMS Server "{0}" because the earlier attempt to ${2} was failed.

Cause: This error occurred during deployment of the JMS server.

Action: Fix any deployment errors related to this JMS server.
Level: 1

Type: ERROR

Impact: JMS

BEA-040510: While attempting to rename a connection factory named "{0}", an error occurred while attempting to establish a JNDI listener. The cause was {1}.

Cause: There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.

Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMS

BEA-040511: The system is waiting to unbind connection factory "{0}". An attempt is being made to change the JNDI name of this connection factory from "{1}" to "{2}".

Cause: An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040512: An attempt is being made to change the JNDI name of connection factory "{0}" from "{1}" to "{2}". The system has waited to unbind "{1}" for five minutes. The new JNDI name "{2}" may or may not be bound properly.

Cause: The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.

Action: In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise, the connection factory is in an indeterminate state.
Level: 1

Type: ERROR

Impact: JMS

BEA-040513: While attempting to rename a connection factory named "{0}", an error occurred while attempting to remove a JNDI listener. The cause was {1}.

Cause: There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.

Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040514: While attempting to rename a connection factory named "{0}" an error occurred in the JNDI listener. The error was {1}

Cause: While attempting to dynamically change the JNDI name of a connection factory, a JNDI error occurred. The error itself will tell more about the cause of this failure.

Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040515: A failured occured while attempting to unregister an InterceptionPoint, {0}.

Cause: An exceptoin coccurred while attempting to unregister an InterceptionPoint. The error will provide more details about the cause of this failure.

Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JMS

BEA-040520: One or more Weighted Distributed Destination (WDD) resources were detected in JMS configuration module "{1}": {0}. This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.

Cause: Deprecated resource was used.

Action: Use the Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040521: The JMS resource "{0}" that you are trying to create in module "{1}" is a Weighted Distributed Destination (WDD). This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.

Cause: A deprecated resource is trying to create.

Action: Use the Uniform Distributed Destination instead.
Level: 1

Type: WARNING

Impact: JMS

BEA-040522: Failed to update distributed destination membership in a multi-domain environment: {0}.

Cause: Cross domain security configuration is not properly set up.

Action: Check the security configuration, especially the cross-domain security configuration if the cross domain security feature is enabled. Contact My Oracle support if the problem persists.
Level: 1

Type: WARNING

Impact: JMS

BEA-045002: An error occurred while binding the remote JNDI object to the local JNDI name "{0}".

Cause: The local JNDI name that is attempting to bind to may not be valid.

Action: Check the JNDI name to see if its syntax is correct.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045028: The messages threshold for the JMS server {0} has been exceeded for more than one hour.

Cause: The threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045029: The messages threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.

Cause: The messages threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045030: The bytes threshold for the JMS server {0} has been exceeded for more than one hour.

Cause: The bytes threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045031: The bytes threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.

Cause: The bytes threshold of the JMS server was exceeded.

Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045032: While attempting to create destination {1} in module {2} the JMS server {0} could not be found.

Cause: The JMS server may be shutting down or may not have completed startup.

Action: Deploy the module again once the JMS server has completed startup.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045039: An attempt was made to add a JMS entity of an unknown type {1} in the module {0}.

Cause: The JMS module given to the update was invalid. It contained an unknown type.

Action: Ensure that the JMS module is valid.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045040: While attempting to add a {1} named {2} in module {0}, an error occurred.

Cause: A linked ModuleException will contain more detail about the cause of the failure.

Action: Examine the linked exception, which will contain more information about the cause of this failure.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045041: An attempt was made to remove a JMS entity of an unknown type {1} in the module {0}.

Cause: The JMS module given to the update was invalid. It contained an unknown type.

Action: Ensure that the JMS module is valid.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045042: An error occurred while adding {1} to the JMS module {0}.

Cause: See the linked exception for more detail.

Action: The linked exception will contain more information about why this add operation failed.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045043: An error occurred while removing {1} from the JMS module {0}.

Cause: See the linked exception for more detail.

Action: The linked exception will contain more information about why this add operation failed.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045045: A subdeployment named {1} was not found in the module {0}.

Cause: A subdeployment removal was attempted, but the subdeployment was unknown to the module.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045047: The SubDeploymentMBean {0} in deployment {1} can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value {0}

Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single JMS server because an element of the JMS module that points to that subdeployment can only be targeted to a single JMS server.

Action: Modify the target of the subdeployment so that it only contains a single JMS server.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045048: The JMS server named {0} has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is {1}, and the template name is {2}. However, a JMSSystemResourceMBean of name {1} could not be found. The JMS server {0} will not boot until this problem has been fixed.

Cause: The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.

Action: Put the temporary template into a JMSSystemResource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045049: JMS server {0} does not have a configured temporary template. However an attempt was made to create a temporary destination. This is not allowed.

Cause: A JMS server without a configured temporary template was used to create a temporary destination. This usage is not allowed.

Action: Create a JMSSystemResource that contains a template. Use that template as the temporary template for this JMS server.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045050: A destination named {3} has a jms-create-destination-identifier named {1}. However, another destination named {2} has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot both be located on the JMS server named {0}.

Cause: Two destinations cannot both have the same jms-create-destination-identifier on the same JMS server, even if the two destinations are from different modules.

Action: Either deploy the destination with the offending jms-create-destination-identifier to a different JMS server, or change the value of the jms-create-destination-identifier attribute.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045051: Two destinations with name {1} were deployed to the JMS server {0}.

Cause: Two destinations with the same fully qualified name cannot be deployed to the same JMS server. This error should have been caught during the validation phase of the JMS module.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045052: An attempt was made to change the target of a JMS entity that cannot have its target changed. The entity has name "{0}". The original target has name "{1}". The proposed target has name "{2}"

Cause: An attempt was made to change the target of an entity that cannot have its target changed dynamically.

Action: Untarget a subdeployment and then retarget that subdeployment elsewhere. However, by doing so, the persistent state maintained for entities retargeted in this fashion will not be kept on the old target and may or may not be removed by the system.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045054: Cannot dynamically add member {1} to sistributed destination {0}.

Cause: This member has either not been prepared yet or has already been removed.

Action: Ensure that the distributed destination member is not removed and is in a prepared state.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045055: Cannot dynamically remove member {1} from distributed destination {0}.

Cause: This member has either not been activated yet or is an invalid member.

Action: Ensure that the distributed destination member is valid and is in an activated state.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045060: The JMS module named "{0}" is neither an AppDeployment nor a JMSSystemResource.

Cause: An invalid application context was passed to a JMS module.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045061: An attempt was made to create a durable subscription on a queue named "{3}". The client identifier is "{0}", the subscriptionName is "{1}" and the selector is "{2}". Durable subscriptions may only be created on topics.

Cause: An attempt was made to create a durable subscription on a queue.

Action: Do not attempt to create a durable subscription on a queue.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045062: There can be no more than one jms-interop-module element in the config.xml file.

Cause: More than one jms-interop-module element was found in the config.xml file.

Action: Do not attempt to define more than one jms-interop-module element in the config.xml file.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045063: The jms-interop-module must have name interop-jms and a descriptor file name jms/interop-jms.xml. This has name "{0}".

Cause: An attempt was made to use a jms-interop-module with a name other than interop-jms.

Action: Do not attempt to define a jms-interop-module element in the config.xml file with a name other than interop-jms.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045064: The target named "{1}" of a JMS module inside a deployment named "{0}" must be a WebLogic Server instance or a cluster. Instead, it is of type "{2}".

Cause: An attempt was made to target a JMS module to an invalid type of target.

Action: Do not attempt to target a JMS module to anything other than WebLogic Server instances or clusters. Any other type of target is not understood.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045065: A JMS module with fully qualified name "{1}" in an application named "{0}" does not have the proper hierarchy of targets. In particular, the subdeployment named "{2}" has a target "{3}" that is not a subtarget of any of the targets of "{0}". For example, the target "{3}" is not a subtarget of "{4}".

Cause: A target of a subdeployment of a JMS module was not contained within the targets of the whole JMS module.

Action: Ensure that the JMS module is targeted to a super-set of all the targets of the subdeployment, or retarget the subdeployment within the set of targets for the JMS module.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045066: The target named "{1}" of a JMS subdeployment named "{3}" inside a deployment named "{0}" must be a JMS server, WebLogic Server instance, or a cluster. Instead, it is of type {2}.

Cause: An attempt was made to target a JMS subdeployment to an invalid type of target.

Action: Do not attempt to target a JMS subdeployment to anything other than JMS servers, WebLogic Server instances or clusters. Any other type of target is not understood.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045067: The field "destination-name" was set to "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}". The destination-name field of a distributed destination may only be set in the interop module.

Cause: An attempt was made to set the destination-name field of a distributed destination member type. This is only allowed in the interop module in order to accommodate older clients.

Action: Change the name of the distributed destination member to the name of the physical queue or topic being referenced, and unset the destination-name field.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045068: The physical destination named "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}" does not exist.

Cause: An attempt was made by a distributed destination member to reference a destination that does not exist. The physical destination referenced to by a distributed destination must already exist.

Action: Create the physical destination before referring to it, or create the physical destination in the same edit session as the creation of the distributed destination member.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045069: The JMS module entity named "{2}" of type "{1}" does not exist in the JMSSystemResource "{0}".

Cause: An attempt was made to reference a JMS module entity that does not exist in the specified JMSSytemResource.

Action: Create the JMS module entity in the specified JMSSystemResource before referring to it.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045070: The configuration entity named "{2}" of type "{1}" does not exist in the domain "{0}".

Cause: An attempt was made to reference a configuration entity that does not exist in the specified domain.

Action: Create the configuration entity in the specified domain before referring to it.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045071: The JMS module entity named "{2}" of type "{1}" cannot be created in JMSSystemResource "{0}".

Cause: The JMS module entity creation using the the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045072: The configuration entity named "{2}" of type "{1}" cannot be created in domain "{0}".

Cause: The configuration entity creation using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045073: The JMS module entity named "{2}" of type "{1}" cannot be deleted from JMSSystemResource "{0}".

Cause: The JMS module entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045074: The configuration entity named "{2}" of type "{1}" cannot be deleted from the domain "{0}".

Cause: The configuration entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045075: The JMS module managed entity named "{2}" of type "{1}" cannot be found in the JMSSytemResource "{0}" for modification.

Cause: The JMS module entity modification using the JMSModuleHelper API failed. See the accompanying exception for details.

Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045076: An attempt was made to find and modify a JMS module entity named "{2}", of type "{1}", from the JMSSystemResource "{0}" using a null modifier.

Cause: The JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null.

Action: Use a valid weblogic.jms.extensions.JMSEntityModifer implementation as the modifier argument.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045077: The destination named "{0}" on the JMS server "{1}" would have caused the JMS server not to boot because the destination StoreEnabled value is true, but the JMS server does not have a store.

Cause: This configuration does not work in older releases because the destination StoreEnabled value is true, but the JMS server does not have a store.

Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the StoreEnabled parameter on the destination.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045078: The destination named "{0}" on the JMS server "{1}" has a DeliveryParamsOverrides.DeliveryMode parameter set to persistent, but the JMS server does not have a store.

Cause: Messages cannot be made persistent on this JMS server because it does not have a store.

Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the DeliveryParamsOverrides.DeliveryMode parameter.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045079: An attempt was made to send a persistent message to the destination "{0}" hosted on the JMS server "{1}". This JMS server does not have a store, so the quality of service requested is not available.

Cause: An attempt was made to send a persistent message to a destination hosted by a JMS server that does not have a store. Since the message cannot be persisted, this message cannot be sent at the required quality of service.

Action: There is a parameter on the JMS server called "AllowsPersistentDowngrade". If this parameter is set to true, then persistent messages sent to this JMS server will be downgraded to non-persistent.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045080: The flow steps value {1} is larger than the flow interval value {2} in the connection factory "{0}". The flow steps value must be less than or equal to the flow interval value.

Cause: This is an invalid configuration. The flow steps value must be less than the entire flow interval.

Action: Modify the configuration of the connection factory to have the flow steps value be less than or equal to the flow interval.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045081: The SessionsMaximum attribute of a JMSSessionPoolMBean has the bad value {0}. The value should be -1 or a positive integer.

Cause: This is an invalid configuration.

Action: Modify the configuration of the JMSSessionPoolMBean.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045082: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}".

Cause: The naming exception should contain more information about why this operation failed.

Action: See the attached naming exception message, which should have more information about why this operation failed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045083: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the local JNDI context.

Cause: The naming exception should contain more information about why this operation failed.

Action: See the attached naming exception, which should have more information about why this operation failed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045084: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the application JNDI context.

Cause: The naming exception should contain more information about why this operation failed.

Action: See the attached naming exception, which should have more information about why this operation failed.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045085: Could not find a license for JMS. Contact Oracle to obtain a license.

Cause: A license for JMS was not obtained.

Action: Contact Oracle to obtain a license.
Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045086: The jms-system-resource cannot have the name interop-jms.

Cause: An attempt was made to define a jms-system-resource with the name interop-jms.

Action: Do not attempt to define a jms-system-resource element in the config.xml file with the name interop-jms.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045087: The JMS deployment "{0}" has the descriptor file name "{1}", which is reserved for internal use only.

Cause: An attempt was made to define a JMS deployment with the reserved file name "interop-jms.xml". This name is reserved by the system for use as the interop module.

Action: Do not attempt to define a JMS deployment with the reserved name "interop-jms.xml" as its file name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045088: The JMS module descriptor file "{1}" used by the JMS system resource "{0}" is illegal. Either the descriptor file name does not end with -jms.xml or the descriptor is being used by another JMS system resource in the configuration.

Cause: An attempt was made to define a JMS system resource with the illegal descriptor file name.

Action: Do not attempt to define a jms-system-resource element in the config.xml file with the illegal descriptor file name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045089: SAF error destination {2} of {1} is targeted to a different subdeployment from {0}.

Cause: The configuration was invalid.

Action: Correct the deployment descriptor.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045090: The error handling {1} configured for {0} does not exist in the module.

Cause: The configuration was invalid.

Action: Correct the deployment descriptor.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045091: One of the target ("{1}") of the subdeployment "{2}" for the imported destinations "{0}" is not a legal target type.

Cause: The configuration was invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045092: Imported destinations "{0}": its subdeployment is targeted to a target ("{1}"), which is a receiving-only SAF agent.

Cause: The configuration was invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045093: A UDQ named "{0}" was found in the JMS interop module. UDQs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDQ in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045094: A UDT named "{0}" was found in the JMS interop module. UDTs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDT in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045095: An SAF imported destinanation named "{0}" was found in the JMS interop module. SAF imported destinations were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF imported destinations in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045096: An SAF remote context named "{0}" was found in the JMS interop module. SAF remote contexts were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF remote context in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045097: An SAF error handlings named "{0}" was found in the JMS interop module. SAF error handlings were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF error handlings in that module.

Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.

Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045098: There is a JMS system resource and an application deployment both named "{0}". The names of all JMS system resources and all application deployments must be different.

Cause: Both a JMS system resource and an application deployment have the same name. This would cause similarly named resources in a JMS module descriptor file to have conflicting runtime names, and therefore is not allowed.

Action: Change the name of either the JMS system resource or application deployment so that there is no name conflict.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045099: An attempt was made to create a temporary destination. However, no JMS server in the cluster is able to host temporary destinations. Ensure that at least one of the JMS servers in the cluster has the HostingTemporaryDestinations parameter set to true (which is the default).

Cause: None of the JMS servers in the cluster are available for hosting temporary destinations.

Action: Modify the HostingTemporaryDestinations parameter on at least one JMS server in the cluster. Note that in releases prior to 9.0, the default for the ability to host temporary destinations was false, while in 9.0 and beyond, the default for the ability to host temporary destinations is true.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045100: The createQueue or createTopic call was made with a null or zero length destination name.

Cause: The createQueue or createTopic call must be made with the name of a destination to find.

Action: Do not pass a null or zero length string to createQueue or createTopic.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045101: The destination name passed to the createTopic or createQueue "{0}" is invalid. If the destination name does not contain a "/" character, then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character, then the string before the "/" must be the name of a JMS server or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WebLogic Server instance will be returned.

Cause: Either a distributed destination of the given name does not exist in the cluster to which the client is attached or the destination name passed to createTopic or createQueue does not contain a "/" character, or there is nothing before the "/" character.

Action: Ensure that the distributed destination is available on the same cluster where the client is located, or format the destination name string properly.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045102: A destination named "{0}" was not found on WebLogic Server instance "{1}".

Cause: An attempt was made to find a destination of a given name on a particular WebLogic Server instance. No destination of that name could be found on that WebLogic Server instance.

Action: It is possible that the createTopic or createQueue call was routed to a WebLogic Server instance that does not contain a destination with the given name. The set of WebLogic Server instances where this request can be routed can be controlled by using a connection factory that is only targeted to WebLogic Werver instances that have destinations of the desired name.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045103: While trying to find a topic or a queue, the specific JMS server requested could not be found. The linked exception may contain more information about the reason for failure.

Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.

Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045104: While trying to find a topic or a queue, the specific JMS server requested could not be found.

Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.

Action: Ensure that the JMS server requested exists in the configuration of the cluster to which the client is attached.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045105: While trying to find a topic or a queue, communication failed with the specific JMS server requested. The linked exception may contain more information about the reason for failure.

Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not communicate with the JMS server of that name.

Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045106: A destination named "{0}" was found. However, the requested destination was of type "{1}", and the destination found was not of that type.

Cause: Either the user called createTopic and the destination found was a queue or the user called createQueue and the destination found was a topic.

Action: Ensure that the destination name requested is of the correct type.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045107: A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure.

Cause: While attempting to remove a durable subscription a communication failure occurred.

Action: Check on the status of WebLogic Server instance where the destination which the durable subscription refers to resides. Check the linked exception for more information about the cause of this failure.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045108: The JMS system does not understand request ID {0}.

Cause: An invalid request ID was presented to the front end manager.

Action: If this condition persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045109: A foreign server named "{0}" was found which does not have a connection URL specified. However, it contains a "{2}" named "{1}" that has the same local and remote JNDI name value "{3}". This is an invalid configuration and is not allowed.

Cause: The user has configured a foreign server without a connection URL and has either a foreign connection factory or a foreign destination with both the local and remote JNDI name matching.

Action: Ensure that either the foreign server has a connection URL to the foreign server or that the local and remote JNDI names are different.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045110: The JMS resource named "{0}" has incorrect targeting information. This resource has the default-targeting-enabled attribute set to true and has a valid sub-deployment-name value specified.

Cause: A JMS resource cannot have both default targeting enabled and a subdeployment name specified.

Action: Ensure that either the default targeting is enabled or that the valid subdeployment name is specified.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045111: The JMS resource named "{0}" has incorrect targeting information. A JMS physical destination cannot have the default-targeting-enabled attribute set.

Cause: A JMS physical destination cannot have the default-targeting-enabled attribute set.

Action: Ensure that the default-targeting-enabled attribute is not set for the physical destinations.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045112: The flow minimum value {1} is larger than or equal to the flow maximum value {2} in connection factory "{0}". The flow minimum value must be less than the flow maximum value.

Cause: This is an invalid configuration. The flow minimum value must be less than the flow maximum value.

Action: Modify the configuration of the connection factory to have the flow minimum value be less than the flow maximum value.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045113: JMS distributed destination forward request denied for the destination named "{1}". Reason "{0}".

Cause: JMS distributed destinations may not have been fully initialized.

Action: If forwarding does not begin after a few minutes, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: JMSExceptions

BEA-045114: Failed to unsubscribe the subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription without a topic object.

Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a client ID policy of UNRESTRICTED.

Action: Use the weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a client ID policy of UNRESTRICTED. If using a pre-AS11gR1PS3 Java client, upgrade to a AS11gR1PS3 client. If using a non-Java client, clean up the durable subscription from the Administration Console or use WebLogic Scripting Tool (WLST) commands or scripts.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045115: The SubDeploymentMBean {0} in JMS Module {1} can only be targeted to a single non-clustered JMSServer as it contains a standalone queue, topic or quota that can only be targeted to a single non-clustered JMSServer.

Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single non-clusterd JMSServer.

Action: Modify the target of the subdeployment so that it contains only a single non-clustered JMSServer.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045116: The Replicated Distributed Topic (RDT) cannot have its members hosted by a cluster targeted JMSServer. The RDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.

Cause: The RDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.

Action: Modify the target of the subdeployment so that it does not contain a cluster targeted JMSServer.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045117: An SAFAgent (store-and-forward agent) cannot be targeted to cluster {0} which has dynamic servers enabled (dynamic servers exist in clusters where the MaximumDynamicServerCount is greater than zero). Instead of using cluster targeting, SAFAgents can be targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Cause: An SAFAgent cannot be targeted to cluster {0} which has dynamic servers enabled (dynamic servers exist in clusters where the MaximumDynamicServerCount is greater than zero). Instead of using cluster targeting, SAFAgents can be targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Action: Modify the target of the SAFAgent such that it is either targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045118: MaximumDynamicServerCount cannot be set higher than 0 for the DynamicServers {0} in cluster {1}. One or more SAFAgents (store-and-forward agents) are currently targeted to the same cluster, and SAFAgents are not supported for a cluster in which dynamic servers are enabled. Instead of using cluster targeting, SAFAgents can be targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Cause: MaximumDynamicServerCount cannot be set higher than 0 for the DynamicServers {0} in cluster {1}. One or more SAFAgents are currently targeted to the same cluster, and SAFAgents are not supported for a cluster in which dynamic servers are enabled. Instead of using cluster targeting, SAFAgents can be targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.

Action: Modify the target of the SAFAgent or SAFAgents that are targeted to this cluster such that they are either targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045119: A JMS message send request failed for distributed destination {0}. Neither Unit-of-Order (UOO) nor Unit-of-Work (UOW) messages are supported for distributed destinations that have a member hosted by a clustered JMS Server. Distributed destination {0} has one or more of its members hosted by a clustered JMS server.

Cause: A JMS message send request failed for distributed destination {0}. Neither Unit-of-Order (UOO) nor Unit-of-Work (UOW) messages are supported for distributed destinations that have a member hosted by a clustered JMS Server. Distributed destination {0} has one or more of its members hosted by a clustered JMS server.

Action: To produce either UOO or UOW messages on a distributed destination, either use a distributed destination that is hosted only on one or more non-dynamic JMS servers, or send messages directly to a member of the distributed destination. Note that when an application sends messages directly to a distributed destination member, the application is responsible for making sure that all messages with the same UOO/UOW string are sent to the same distributed destination. This ensures strictly ordered message processing for the given UOO/UOW.
Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-050000: {0} is an obsolete property. Use {1} to create the context instead.

Cause: Property {0} is obsolete. However, this property name can still be used to retrieve the property value.

Action: Use property {1} instead of {0} in the future.
Level: 1

Type: WARNING

Impact: JNDI

BEA-050001: WLContext.close() was called in a different thread than the one in which it was created.

Cause: The threads used to create and close the context are different. As a result, the context entries associated with the creating thread might not be cleaned up.

Action: Close the context in the creating thread.
Level: 1

Type: WARNING

Impact: JNDI

BEA-050002: Cannot replicate the object that is bound in the JNDI under the name {0}.

Cause: A non-serializable object cannot be serialized.

Action: If the object was not intended to be replicated, set the replicate bindings to false. If the object should be replicated to all nodes in the cluster, ensure that the object is serializable or externalizable.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050003: Cannot create initial context. Reason: {0}

Cause: Initial context cannot be created.

Action: Check the exception in the message body.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050004: Unable to bind. Reason: {0}

Cause: This was unable to bind.

Action: Check the exception in the message body.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050005: Unable to unbind. Reason: {0}

Cause: This was unable to unbind.

Action: Check the exception in the message body.
Level: 1

Type: ERROR

Impact: JNDI

BEA-050006: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.

Cause: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.

Action: Ensure that the possibility of premature retirement of the application version is either tolerated or handled properly. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_EXTERNAL_LOOKUP to "true" when performing lookup of the versioned object.
Level: 1

Type: WARNING

Impact: JNDI

BEA-050007: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.

Cause: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.

Action: Ensure that usages of the global resource by multiple application versions do not conflict. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_GLOBAL_RESOURCE_LOOKUP to "true" when performing lookup of the global resource.
Level: 1

Type: WARNING

Impact: JNDI

BEA-055001: Invalid time-to-deliver, must be >= -1

Cause: The time-to-deliver parameter passed to setTimeToDeliver was invalid.

Action: Change the code to pass a time-to-deliver parameter that is >= -1.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055002: Cannot convert {0} to a boolean.

Cause: An object that was not null, not a boolean, and not a string could not be converted to a boolean value.

Action: Ensure that the object passed in is either a boolean or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055003: Cannot convert null to a byte.

Cause: The null object cannot be converted to a byte value

Action: Avoid passing null where a byte value is expected
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055004: Cannot convert {0} to a byte.

Cause: An object that was not null, not a byte, and not a string could not be converted to a byte value

Action: Ensure that the object passed in is either a byte or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055005: Cannot convert null to a short.

Cause: The null object cannot be converted to a short value.

Action: Avoid passing null where a short value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055006: Cannot convert {0} to a short.

Cause: An object that was not null, not a short, and not a string could not be converted to a short value.

Action: Ensure that the object passed in is either a short or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055007: Could not serialize object.

Cause: An object could not be serialized. The linked exception may contain more details.

Action: See the linked exception which may contain more details.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055008: Invalid RedeliveryLimit, must be >= -1.

Cause: The RedeliveryLimit parameter passed to setRedeliveryLimit was invalid.

Action: Change the code to pass a RedeliveryLimit parameter that is >= -1.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055009: Invalid SendTimeout, must be >= 0

Cause: The SendTimeout parameter passed to setSendTimeout was invalid.

Action: Change the code to pass a SendTimeout parameter that is >= 0.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055014: Error sending message

Cause: The linked exception will contain more details concerning the failure to send the message.

Action: The action will depend on the error that occurred. More information about the specific error that occurred can be found in the linked exception.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055015: Invalid DeliveryMode

Cause: The DeliveryMode parameter passed to setDeliveryMode was invalid.

Action: Change the code to pass a valid DeliveryMode value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055016: Invalid Priority

Cause: The Priority parameter passed to setPriority was invalid.

Action: Change the code to pass a valid Priority value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055017: Durable connection consumers are not supported.

Cause: The system does not support durable connection consumers.

Action: Do not attempt to create a durable connection consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055018: QueueSessions do not support multicast.

Cause: The MULTICAST_NO_ACKNOWLEDGE flag was set in createQueueSession.

Action: Do not use MULTICAST_NO_ACKNOWLEDGE when creating a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055019: Duplicate session

Cause: The cause is unknown.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055021: ClientID is null

Cause: ClientID is null in a call to setClientID.

Action: Do not use null in a call to setClientID.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055022: Zero length clientID

Cause: The clientID passed to setClientID was zero length.

Action: The clientID must not be zero length.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055023: Invalid value for messagesMaximum, {0}

Cause: The value given for messagesMaximum in createConnectionConsumer is invalid.

Action: Change the code to pass a valid messagesMaximum value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055024: No such method {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055025: Invalid messagesMaximum value

Cause: The messagesMaximum parameter passed to setMessagesMaximum was invalid.

Action: Change the code to pass a valid messagesMaximum value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055026: Invalid overrunPolicy value, {0}

Cause: The overrun policy passed to setOverrunPolicy is invalid.

Action: Change the code to pass a valid overrun policy value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055027: Invalid redelivery delay, must be >= -1

Cause: The redeliveryDelay parameter passed to setRedeliveryDelay was invalid.

Action: Change the code to pass a valid redeliveryDelay value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055028: Name must not be null.

Cause: The name parameter passed to createDurableSubscriber was null.

Action: Change the code to pass a valid name to createDurableSubscriber.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055029: Name must not be an empty string.

Cause: The name parameter passed to createDurableSubscriber had a length of zero.

Action: Change the code to pass a valid name to createDurableSubscriber.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055030: This topic does not support durable subscriptions.

Cause: Durable subscribers are not supported on Distributed Topics and no subscribers at all are supported on SAF topics

Action: Avoid attempting to create a durable subscriber on a distributed topic or do not create a subscriber on an SAF topic.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055031: This connection does not have a clientID.

Cause: Unsubscribe was called on a connection without a clientID.

Action: Avoid attempting to unsubscribe a connection with no clientID
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055032: An attempt was made to create a named consumer ({0}) on a connection with no clientID.

Cause: An attempt was made to create a named consumer on a connection with no clientID.

Action: Avoid attempting to create a named consumer on a connection with no clientID.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055033: Queues do not support multicast.

Cause: Queues do not support multicast.

Action: Avoid attempting to create a multicast consumer on a queue
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055034: Topic {0} does not support multicast.

Cause: An attempt was made to create a multicast consumer on a topic that does not support multicast.

Action: Avoid attempting to create a multicast consumer on the given topic.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055035: Cannot open multicast socket, {0}.

Cause: An attempt was made to open a multicast socket and failed. The reason for the failure may be in the exception

Action: For more details, check the printed exception on the failure to open the multicast socket.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055036: Cannot join multicast group ({0}) {1}

Cause: An attempt was made to join a multicast group and failed. The reason for failure may be in the exception.

Action: For more details, check the printed exception on the failure to join the multicast group.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055037: Subscription {0} is in use.

Cause: Two subscriptions with the same name are not allowed.

Action: Avoid attempting to use a subscription name more than once. If necessary, unsubscribe the previous subscription
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055038: An unexpected response ({0}) was received from the server.

Cause: An internal protocol error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055039: A system error has occurred. The error is {0}.

Cause: The cause of this error may be contained in the printed exception.

Action: The action will depend on the error that has occurred. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055040: Subscription {0} is in use.

Cause: An attempt was made to remove the named subscription while the subscription was in use.

Action: Avoid attempting to remove a subscription that is currently in use.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055041: Cannot leave multicast group ({0}) {1}

Cause: An attempt was made to leave a multicast group and failed. The reason for failure may be in the exception.

Action: For more details, check the printed exception on the failure to leave the multicast group.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055042: No such method {0} for class {1}

Cause: An internal error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055043: No such method {0} for class {1}

Cause: An internal error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055044: Multicast sessions do not support synchronous receives.

Cause: An attempt was made to do a synchronous receive on a multicast consumer.

Action: Avoid attempting to make a synchronous receive with a multicast consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055045: An invalid value ({0}) for timeout was specified.

Cause: The timeout given to a receive call is invalid. Timeout values must be positive.

Action: Change the code so that it does not pass a negative number into a receive call.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055046: A listener already exists.

Cause: A call to receive cannot be made if the consumer already has a listener.

Action: Avoid attempting to call receive if a listener already exists for the consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055047: No such method {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055048: Multicast selectors are not supported in the thin client.

Cause: Multicast selectors are not supported in the thin client.

Action: If selectors are required, avoid using the JMS thin client. If selectors are not required, avoid using them while using the thin client.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055049: Internal error {0}.

Cause: An internal error occurred. More detail about the error can be found in the exception.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055050: Internal error {0}

Cause: An internal error occurred. More detail about the error can be found in the exception.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055051: Internal error {0}

Cause: An internal error occurred. More detail about the error can be found in the exception.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055052: Invalid selector {0}

Cause: An error occurred while parsing a selector. The printed exception should have more detail.

Action: The course of action will depend on the nature of the error. Use a well-formed selector.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055053: Error creating connection to the server: {0}.

Cause: The printed exception may have information regarding the cause of this failure.

Action: The course of action will depend on the error printed out in the exception.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055054: Error finding dispatcher: {0}.

Cause: An internal error has occurred.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055055: No transaction

Cause: A call to commit was made on a session but there is no current transaction.

Action: Avoid calling commit on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055056: Error committing session

Cause: An error occurred while committing an XA session.

Action: Examine the transaction logs to see what occurred to the transaction
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055057: No transaction

Cause: A call to rollback was made on a session but there is no current transaction.

Action: Do not call rollback on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055058: Error committing session

Cause: An error occurred while committing an XA session.

Action: Examine the transaction logs to see what occurred to the transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055059: getXAResource can be called only from the server.

Cause: A call to getXAResource was made from a client JVM; getXAResource is not supported in the client.

Action: Avoid calling getXAResource from a client JVM.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055060: No transaction.

Cause: A call to commit was made on a session but there is no current transaction.

Action: Avoid calling commit on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055061: No transaction.

Cause: A call to rollback was made on a session but there is no current transaction.

Action: Avoid calling rollback on a session that is not currently in a transaction.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055062: This session is transacted.

Cause: A call to recover was made on a transacted session.

Action: Avoid calling recover on a transacted session. Use rollback instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055063: This session has consumer listeners.

Cause: The session on which setMessageListener was called already has consumer listeners.

Action: Avoid calling setMessageListener on a session that already has consumer listeners.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055064: Unsupported topic operation on a queue session

Cause: A call to createTopic was made on a QueueSession.

Action: Avoid calling createTopic on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055065: Unsupported topic operation on a queue session

Cause: A call to createDurableSubscriber was made on a QueueSession.

Action: Avoid calling createDurableSubscriber on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055066: Unsupported topic operation on a queue session

Cause: A call to createTemporaryTopic was made on a QueueSession.

Action: Avoid calling createTemporaryTopic on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055067: Unsupported topic operation on a queue session

Cause: A call to unsubscribe was made on a QueueSession.

Action: Avoid calling unsubscribe on a QueueSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055068: There is no subscription from which to unsubscribe.

Cause: The user called unsubscribe on a session that does not have a subscription.

Action: Avoid calling unsubscribe on a session that does not have a subscription.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055069: Unsupported queue operation on a topic session

Cause: A call to createQueue was made on a TopicSession.

Action: Avoid calling createQueue on a TopicSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055070: Unsupported queue operation on a topic session

Cause: A call to createBrowser was made on a TopicSession.

Action: Avoid calling createBrowser on a TopicSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055071: Unsupported queue operation on a topic session

Cause: A call to createTemporaryQueue was made on a TopicSession.

Action: Avoid calling createTemporaryQueue on a TopicSession.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055072: Wrong connection for this temporary destination

Cause: An attempt was made to call createConsumer on an invalid connection from a temporary destination.

Action: Create consumers using the same connection that was used to create the temporary destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055073: Dropping new message

Cause: A new message is being dropped because too many messages have arrived.

Action: Either consume messages faster or produce messages slower for this session.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055074: Dropping old message

Cause: An old message is being dropped because too many messages have arrived.

Action: Either consume messages faster or produce messages slower for this session.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055075: It is possible that the client is malfunctioning: a RuntimeException was thrown from its onMessage method.

Cause: The onMessage method of the client threw a RuntimeException.

Action: Modify the code such that the RuntimeException does not occur from within the body of the user code. This warning is required by section 4.5.2 of the JMS Specification.
Level: 1

Type: WARNING

Impact: JMSClientExceptions

BEA-055076: The session is closed.

Cause: An operation was attempted on a closed session.

Action: Avoid attempting this operation on a closed session.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055077: Cannot override producer destination.

Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.

Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055078: Cannot override producer destination

Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.

Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055079: Must provide destination to send to

Cause: There is no destination to send to.

Action: Use the version of send that has a destination or bind a destination to the producer before calling send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055080: Must provide destination to send to

Cause: There is no destination to send to.

Action: Use the version of send that has a destination or bind a destination to the producer before calling send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055081: Unsupported topic operation on a queue session

Cause: A call to createDurableConnectionConsumer was made on a QueueConnection.

Action: Avoid calling createDurableConnectionConsumer on a QueueConnection.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055082: The connection is closed.

Cause: The connection has been closed. Only a few operations are valid on a closed connection.

Action: Avoid calling any illegal operations on a closed queue connection.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055083: Cannot set clientid to {0}. The client ID is already set to {1}

Cause: The clientID {1} is already set on this connection. The clientID cannot be set to {0}

Action: Avoid attempting to set a clientID on a connection that already has one.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055084: A connection consumer works only on the server.

Cause: A connection consumer can be created only in the same JVM in which the server is running.

Action: Avoid attempting to create a connection consumer on a JVM that is not running the server.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055085: Destination is null.

Cause: In a call to createConnectionConsumer or createConsumer, the destination parameter was null.

Action: Avoid using null for the destination in a call to createConnectionConsumer or createConsumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055086: Foreign destination

Cause: Foreign destinations are not supported when creating connectionConsumers.

Action: Avoid using a foreign destination in a call to createConnectionConsumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055087: The session already has a message listener.

Cause: A consumer may not have an individual message listener if its parent session already has one defined.

Action: Avoid attempting to set a message listener for a consumer if the session already has a listener defined.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055088: The consumer is closed.

Cause: The consumer has been closed. Only a few operations are valid on a closed consumer.

Action: Avoid calling any illegal operations on a closed consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055089: Destination is null.

Cause: In a call to send, the destination parameter was null.

Action: Avoid using null for the destination in a call to send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055090: Foreign destination

Cause: Foreign destinations are not supported when sending.

Action: Avoid using a foreign destination in a call to send.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055091: Destination {0} must be a queue.

Cause: An attempt was made to publish to a queue.

Action: Avoid using publish to a queue. Use send instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055092: Destination {0} must be a topic.

Cause: An attempt was made to send to a topic.

Action: Avoid using send to a topic. Use publish instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055093: Error converting foreign message

Cause: An I/O exception occurred while converting a foreign message. The cause of the failure may be contained in the linked exception.

Action: Examine the linked I/O exception.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055094: The producer is closed.

Cause: The producer has been closed. Only a few operations are valid on a closed producer.

Action: Avoid calling any illegal operations on a closed producer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055095: The browser is closed.

Cause: The browser has been closed. Only a few operations are valid on a closed browser.

Action: Avoid calling any illegal operations on a closed browser.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055096: Cannot convert null to a char.

Cause: The null object cannot be converted to a char value.

Action: Avoid passing null where a char value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055097: Cannot convert {0} to a char.

Cause: An object that was not null, not a character, and not a string could not be converted to a char value.

Action: Ensure that the object passed in is either a character or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055098: Cannot convert null to an int.

Cause: The null object cannot be converted to an int value.

Action: Avoid passing null where an int value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055099: Cannot convert {0} to an int.

Cause: An object that was not null, not an integer, and not a string could not be converted to an int value.

Action: Ensure that the object passed in is either an intenger or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055100: Cannot convert null to a long.

Cause: The null object cannot be converted to a long value.

Action: Avoid passing null where a long value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055101: Cannot convert {0} to a long.

Cause: An object that was not null, not a long, and not a string could not be converted to a long value.

Action: Ensure that the object passed in is either a long or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055102: Cannot convert null to a float

Cause: The null object cannot be converted to a float value.

Action: Avoid passing null where a float value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055103: Cannot convert {0} to a float

Cause: An object that was not null, not a float, and not a string could not be converted to a float value.

Action: Ensure that the object passed in is either a float or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055104: Cannot convert null to a double

Cause: The null object cannot be converted to a double value.

Action: Avoid passing null where a double value is expected.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055105: Cannot convert {0} to a double.

Cause: An object that was not null, not a double, and not a string could not be converted to a short value.

Action: Ensure that the object passed in is either a double or a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055106: A byte[] cannot be converted to a string.

Cause: A byte[] cannot be converted to a string.

Action: Avoid passing a byte array that needs to be converted to a string.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055107: Cannot convert {0} to a byte[].

Cause: The given object could not be converted to a byte[].

Action: Ensure that the object passed in can be converted to a byte array.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055108: Read past end of message

Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information

Action: Avoid attempting to read past the end of a StreamMessage. See the linked EOFException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055109: Error reading from stream

Cause: There was an error reading the stream from a StreamMessage. A linked IOException may contain more information.

Action: See the linked IOException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055110: Error writing to stream

Cause: There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information.

Action: See the linked IOException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055111: Cannot convert from {0} to {1}

Cause: A StreamMessage was unable to convert one type to another.

Action: Ensure that the two types are compatible. Avoid attempting to convert incompatible types
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055112: Error reading from stream

Cause: There was an error reading the stream from a StreamMessage. A linked ArrayIndexOutOfBoundsException may contain more information.

Action: See the linked ArrayIndexOutOfBoundsException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055113: Error reading from stream

Cause: There was an error reading the stream from a StreamMessage. A linked ArrayStoreException may contain more information.

Action: See the linked ArrayStoreException for more information.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055114: There was an eeror when deserializing an object. Some typical reasons for failure are: missing application class, application class version mismatch, or Java objects not being supported.

Cause: There was an error deserializing an object. A linked IOException may have more details.

Action: See the linked IOException for more details.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055115: Error deserializing an object

Cause: There was an error deserializing an object. A linked ClassNotFoundException may have more details.

Action: See the linked ClassNotFoundException for more details.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055116: Internal error unknown message type {0}

Cause: This error should never happen.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055117: Invalid delivery mode {0}

Cause: The delivery mode passed into setJMSDeliveryMode is invalid

Action: Change the code so that it calls setJMSDeliveryMode with a valid delivery mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055118: Invalid redelivery limit, must be >= -1

Cause: The redelivery limit parameter passed to setJMSRedeliveryLimit was invalid.

Action: Change the code to pass a redelivery limit parameter that is >= -1.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055119: Invalid priority, {0}

Cause: The priority parameter passed to setJMSPriority was invalid.

Action: Change the code to pass a valid priority value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055121: Invalid property name, "{0}"

Cause: The property name passed to setObjectProperty was invalid.

Action: Change the code to pass a valid property name.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055122: Property write attempted in READ mode.

Cause: An attempt was made to write a property but the message is read-only.

Action: Avoid attempting to write a property to a message in read-only mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055123: Invalid property value, {0}

Cause: The property value passed to setObjectProperty was invalid.

Action: Change the code to pass a valid property value.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055125: Unknown underlying stream type, cannot convert 6.0 class.

Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.

Action: It may not be possible to read the older version of the message. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055126: Stream is corrupted. Possible older version

Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.

Action: It may not be possible to read the older version of the message. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055127: Unsupported version

Cause: The version of the message being read is unsupported.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055128: Read attempted in WRITE mode.

Cause: An attempt was made to read a message in WRITE mode.

Action: Avoid attempting to read a message in WRITE mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055129: Write attempted in READ mode.

Cause: An attempt was made to write a message that is read-only.

Action: Avoid attempting to write to a message in read-only mode.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055130: Invalid data type: {0}

Cause: The class name given is not a valid data type. The type for setObject must be number, string, boolean, byte, character, or null.

Action: Pass one of the acceptable data types to setObject in a MapMessage.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055131: Illegal name: {0}

Cause: The given name is not legal. It is either null or of zero length.

Action: Pass a non-null or non-zero-length string as the name of a MapMessage element.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055132: Could not copy message.

Cause: The system could not copy a MapMessage. The linked IOException should contain more information about the nature of the error.

Action: Examine the linked exception to discover what caused the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055133: Could not deserialize message.

Cause: The system could not deserialize a MapMessage. The linked IOException should contain more information about the nature of the error.

Action: Examine the linked exception to discover what caused the failure.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055134: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.

Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {1} then it is possible an attempt was made to access a newer JMS version than the current version. Otherwise a possible attempt has been made to interoperate with an unsupported older version of JMS.

Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions should be supported, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055135: Could not write object, expected simple type, but got class {0}

Cause: The given object class could not be written because it is not a simple type.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055136: Could not read object, unrecognized class code {0}.

Cause: An unknown class code was received. The object cannot be read.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055137: JMSProducerSendResponse versions {0}, {1} not compatible with peer: {2}

Cause: An interoperability error occurred.

Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055138: Peer not compatible with DistributedDestinationImpl version {0}. Peer Major Version is less than 6.

Cause: An interoperability error occurred.

Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055139: Invalid Temporary Destination

Cause: An attempt was made to delete an invalid temporary destination.

Action: Avoid attempting to delete invalid temporary destinations.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055140: Internal error or marshalling error, unknown destination type {0}

Cause: An unknown type was encountered when marshalling a destination.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055141: Destination is null.

Cause: While checking a destination type, the incoming destination was null.

Action: Avoid attempting to discover the type of a null destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055142: Foreign destination, {0}

Cause: While checking a destination type, the incoming destination was foreign.

Action: Avoid attempting to discover the type of a foreign destination.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055143: Destination must be a queue, {0}

Cause: The given destination must be a queue, but it is not a queue.

Action: Use the proper type of destination when checking types.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055144: Destination must be a topic, {0}

Cause: The given destination must be a topic, but it is not a topic.

Action: Use the proper type of destination when checking types.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055145: Unknown stream version: {0}

Cause: The given version number is invalid for a buffered stream.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055146: The stream cannot handle raw objects.

Cause: The stream is probably from an unintended source, such as a Web browser.

Action: Only connect to the Oracle product TCP port with a proper client. If the client is a proper client, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055147: Not implemented

Cause: readLine was called, but it has not been implemented.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055148: The stream cannot handle raw objects.

Cause: A raw object could not be written to the buffered stream.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055149: Attempt to read past end of message ({0})

Cause: The end of the BytesMessage was reached, but an attempt was made to read past it. {0} indicates where the attempt was made and will only be significant to My Oracle Support.

Action: Avoid attempting to read past the end of the BytesMessage.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055150: Error reading from stream ({0}).

Cause: The linked IOException will have more detail on the cause of the failure.

Action: Examine the linked exception to discover what caused the problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055151: Length ({0}) is negative.

Cause: In a call to readBytes, the length parameter is negative.

Action: Fix the code to ensure a negative length is not passed to readBytes.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055152: length ({0}) is greater than the length of the array ({1}).

Cause: In a call to readBytes, the length parameter is larger than the size of the bytes array to fill.

Action: Fix the code to ensure the length passed to readBytes is less than or equal to the length of the output array.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055153: Error writing to stream ({0}).

Cause: The linked IOException will have more detail on the cause of the failure.

Action: Examine the linked exception to discover what caused the problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055154: Invalid object type: {0}

Cause: The object passed to writeObject is not valid.

Action: Only send valid object types to writeObject. Example valid types include boolean, byte, short, and integer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055155: Cannot forward message

Cause: Modified received messages are not supported when using forward methods.

Action: Avoid modifying a received message in a call to forward.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055156: Peer neither compatible with {0} or {1} or {2} or {3}. PeerInfo is {4}.

Cause: A version mismatch occurred in a message.

Action: This is an internal error that should not occur. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055157: Invalid compression threshold

Cause: The compression threshold was invalid.

Action: Change the code to pass a valid compression threshold.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055158: WebLogic Server JMS failed to decompress the message body.

Cause: The linked IOException will have more detail on the cause of the failure.

Action: Examine the linked exception to discover what caused the problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055159: Message consumer received a compressed message with unknown compression tag - {0}

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055160: WebLogic Server JMS failed to deserialize the text message.

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055161: Cannot forward foreign messages.

Cause: Foreign messages are not supported when using forward methods.

Action: Avoid forwarding a foreign message.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055162: WebLogic Server JMS failed to serialize the text message for interoperability.

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055163: WebLogic Server JMS failed to serialize the XML message for interoperability.

Cause: Contact My Oracle Support.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055164: Cannot forward a message to a WebLogic Server instance prior than version 9.0.

Cause: Cannot forward a message to a WebLogic Server instance prior than 9.0.

Action: Avoid forwarding a message to a WebLogic Server instance prior than 9.0.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055165: The following exception has occurred: {0}.

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or the program to see what the results are. In general, this stack trace will help in debugging an existing problem.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055167: Single session cannot support more than one synchronous message-prefetching consumer.

Cause: There is another opened synchronous message-prefetching consumer.

Action: Close the other synchronous message-prefetching consumer.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055168: Synchronous message-prefetching consumer cannot support user transaction.

Cause: Synchronous message-prefetching consumer cannot support user transaction.

Action: Disable the user transaction or the synchronous message-prefetching consumer in the jms connection factory setting.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055169: Network connection to server was lost.

Cause: The network connection to the server was lost.

Action: This is usually a recoverable error when the JMS client is using the auto-reconnect/failover feature. This error is exposed to the user (JMS client code developer) when the auto-reconnect feature cannot make a decision without user input on a particular course of action after failover. The user can consciously code to continue to use relevant refreshed JMS objects with a potential lowered quality of service such as duplicate/lost/out-of-order messages, or decide to close the relevant JMS object.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055170: Cannot convert string property from its internal format.

Cause: The string property cannot be converted from its internal format.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055171: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe() API.

Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED.

Action: Use weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a Client ID policy of UNRESTRICTED.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055172: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a Client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription with a null topic or distributed topic instance.

Cause: An attempt was made to unsubscribe a durable subscription with a null Topic object or a distributed topic object from a connection that has a Client ID policy of UNRESTRICTED.

Action: Provide a standalone topic object or a member of a distributed topic when calling weblogic.jms.extensions.WLSession.unsubscribe(String topic, String name).
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055173: Read past end of message ({0})

Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information

Action: Do not attempt to read past the end of a StreamMessage. See the linked EOFException for more information
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055174: Error reading from stream ({0})

Cause: There was an error reading the stream from a StreamMessage. A linked IOException may contain more information

Action: See the linked IOException for more information
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055175: Error writing to stream ({0})

Cause: There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information

Action: See the linked IOException for more information
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055176: Active transaction detected during send, publish, or receive while using a non-XATransaction Resource Adapter.

Cause: An active transaction was detected during send, publish, or receive while using a non-XATransaction Resource Adapter.

Action: Use the XATransaction Resource Adapter instead.
Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-080001: Error in dispatcher {0}

Cause: A runtime error occurred while dispatching a request to the server.

Action: If the error is not application related, contact My Oracle Support with the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: RMI

BEA-080002: Unexport failed for: {0}.

Cause: The remote object was unexported twice.

Action: No action is required.
Level: 1

Type: ERROR

Impact: RMI

BEA-080003: A RuntimeException was generated by the RMI server: {0} {1}.

Cause: A runtime exception occurred while dispatching the request to the server.

Action: No action is required.
Level: 1

Type: WARNING

Impact: RMI

BEA-080004: An error was generated by the RMI server: {0} {1}.

Cause: A runtime error occurred while dispatching a response to the client.

Action: The associated stack trace contains information about the error. Check the server logs for more details.
Level: 1

Type: WARNING

Impact: RMI

BEA-080005: An exception was generated by the RMI server: {0} {1}.

Cause: The error response could not be sent to the client. The underlying socket caused an IOException while dispatching the error response.

Action: The associated stack trace contains information about the error.
Level: 1

Type: WARNING

Impact: RMI

BEA-080006: Failed to associate the transaction context with the response while marshalling an exception to the client: {0}.

Cause: An IOException occurred while associating a transaction context with the response. This happened when marshalling an exception in the response. Most likely, the socket has been torn down or an error occurred in the stream.

Action: Check the server logs for more details.
Level: 1

Type: WARNING

Impact: RMI

BEA-080007: RMI runtime is disabled, since it could not initialize the DGC {0}.

Cause: RMI runtime could not be initialized.

Action: Restart the server. If the problem continues, contact My Oracle Support with the stack trace information.
Level: 1

Type: ERROR

Impact: RMI

BEA-080008: Failed to send error reply to client {0}.

Cause: An exception occurred while dispatching an error response to the client.

Action: No action is required.
Level: 1

Type: ERROR

Impact: RMI

BEA-080009: An error was generated by the RMI server: {0} invoking: {1}.

Cause: A java.lang.Error occurred while invoking method {1} on {0}. A ServerError occurred due to the server side RMI method call.

Action: Check the nested exception in the ServerError for more details.
Level: 1

Type: WARNING

Impact: RMI

BEA-080011: Empty workingSet found while assembling the heartbeat for {0}.

Cause: An empty set of references for {0} was found while assembling the deterministic garbage collector (DGC) heartbeats for all remote virtual machines that are referenced from this virtual machine.

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080012: No workingSet found for {0} residing in {1}.

Cause: An empty working set for {0} was found while periodically scanning the list of finalized references and decrementing the count for any reference found. This is related to the deterministic garbage collector (DGC).

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: ERROR

Impact: RMI

BEA-080013: Reference for {0} not found in working set.

Cause: Did not find {0} in the working set while attempting to decrement the reference count. This is related to the deterministic garbage collector (DGC).

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: ERROR

Impact: RMI

BEA-080015: Could not mark references {0}.

Cause: An exception occurred during the execution of the DGC trigger.

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: ERROR

Impact: RMI

BEA-080016: No connection available to: {0}. References to objects hosted by it are in jeopardy.

Cause: The client lost connection to the server {0}. If the server does not receive lease renewal messages on the server, RMI runtime removes the remote objects whose leases are not renewed.

Action: If the server {0} has been shut down or crashed, no action is required. Otherwise, ensure that the network is healthy.
Level: 1

Type: WARNING

Impact: RMI

BEA-080017: Failed to renew lease for: {0} objects hosted by: {1}.

Cause: This message is logged only in debug mode.

Action: No action is required.
Level: 1

Type: WARNING

Impact: RMI

BEA-080019: Marked in: {0} milliseconds

Cause: This message is logged only if the LogDGCStatistics debug flag is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080020: An exception occurred in the DGC server sweep {0}.

Cause: A runtime error occurred while the DGC server (host of remote objects) requested a sweep to periodically clean up server references.

Action: Provide the log files to My Oracle Support for further analysis of the problem.
Level: 1

Type: ERROR

Impact: RMI

BEA-080021: Sweep freed: {0} objects in: {1} milliseconds. {2} exported objects remain.

Cause: This message is logged only if the LogDGCStatistics debug flag is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080022: Tried to enroll lost reference: {0}.

Cause: This message is logged when an attempt is made to increment the reference count of a lost reference. The reference may have already been released.

Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080023: Tried to unenroll a lost reference: {0}.

Cause: This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080024: Tried to renew the lease on the lost reference: {0}.

Cause: This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080026: Exporting remote object {0} with ID {1}.

Cause: When a remote object is exported into RMI, RMI runtime assigns an object ID to it, thus setting up the environment for remote invocation.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080027: A heartbeat was not sent due to probable client disconnect.

Cause: A thin-client was disconnected from the server.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-090000: Unsupported circular group definition, {0}.

Cause: This is an unsupported feature.

Action: Do not define circular groups.
Level: 1

Type: ERROR

Impact: Security

BEA-090001: Failed to broadcast LoginFailureRecord to the other cluster servers, {0}.

Cause: An I/O exception occurred.

Action: For more information on how the invalid login attempts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090002: Failed to broadcast unlock user {0} to the other clustered servers. {1}

Cause: An I/O exception occurred.

Action: For more information on how locked user account lockouts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090004: Problem closing enumeration: {0}.

Cause: An unexpected exception occurred.

Action: Review the exception message in the log message to see if it identifies the cause of the exception.
Level: 1

Type: WARNING

Impact: Security

BEA-090010: ACL {0} contains non-existent principal {1} - ignoring principal.

Cause: The principal contained in the ACL does not exist.

Action: Modify the ACL and remove the principal.
Level: 1

Type: WARNING

Impact: Security

BEA-090020: User lockout expired, unlocking user {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090022: Explicitly unlocked, user {0}.

Cause: This is an informational message.

Action: For information about unlocking a user account, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090034: Not listening for SSL, {0}.

Cause: An IOException occurred when creating the SSL listen thread.

Action: Read the exception text for more help on diagnosing the problem. Contact the system administrator.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090038: Checking User {0} for Permission {1} {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090039: Access failed (Thread = {0}), caused {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090040: The File realm contains more users than the specified maximum. Maximum = {0}, currently have {1}.

Cause: The File realm sets a limit on the maximum number of supported users. The system has exceeded that limit.

Action: Raise the value of the Max Users attribute.
Level: 1

Type: WARNING

Impact: Security

BEA-090041: The File realm contains more groups than the specified maximum. Maximum = {0}, currently have {1}.

Cause: The File realm sets a limit on the maximum number of supported groups. The system has exceeded that limit.

Action: Raise the value of the Max Groups attribute.
Level: 1

Type: WARNING

Impact: Security

BEA-090042: The File realm contains more ACLs than the specified maximum. Maximum = {0}, currently have {1}.

Cause: The File realm sets a limit on the maximum number of supported ACLs. The system has exceeded that limit.

Action: Raise the value of the Max ACLs attribute.
Level: 1

Type: WARNING

Impact: Security

BEA-090043: Group {0} should exist but does not.

Cause: When adding members to a group, the specified group was not found.

Action: Verify that the group is defined in the fileRealm.properties file or in the Groups tab of the Administration Console.
Level: 1

Type: WARNING

Impact: Security

BEA-090044: Principal {0} does not exist and therefore cannot be added to group {1}.

Cause: When specifying group members, a principal that does not exist was specified.

Action: Add the specified principal to a security realm.
Level: 1

Type: WARNING

Impact: Security

BEA-090045: Permission {0} does not exist.

Cause: When loading access control lists (ACLs), the specified permission was not found.

Action: Verify that the ACL and the permission are specified correctly.
Level: 1

Type: WARNING

Impact: Security

BEA-090046: ACL {0} does not exist.

Cause: When loading ACLs, the specified permission was not found.

Action: Verify that the ACL is specified correctly.
Level: 1

Type: WARNING

Impact: Security

BEA-090047: Principal {0} does not exist thus cannot be added to ACL {1}.

Cause: The principal specified in the access control list (ACL) does not exist in any security realm.

Action: Add the principal to a security realm.
Level: 1

Type: WARNING

Impact: Security

BEA-090048: Made an in-memory only change to the File realm.

Cause: Changes made to the File realm cannot be written to filerealm.properties.

Action: Make the changes on the Administration Server and the changes are propagated to the Managed Servers.
Level: 1

Type: WARNING

Impact: Security

BEA-090049: System user {0} does not exist, creating it.

Cause: The system user is required.

Action: Ensure that the system user was created in a security realm before booting the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090051: Error creating security runtime management.

Cause: During initialization, the security runtime registers with the OAM infrastructure. If this process fails, a management exception occurs.

Action: Verify that the user booting the server is a member of the Administrator group.
Level: 1

Type: ERROR

Impact: Security

BEA-090052: Server installed as Windows NT service with incorrect password for user {0}. The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.

Cause: The server is incorrectly configured as a Windows NT service.

Action: Contact the Windows NT system administrator.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090055: The LDAP realm V1 is deprecated. Please use the LDAP realm V2.

Cause: The LDAP realm V1 is deprecated and will be removed in a future release.

Action: Use LDAP realm V2 or one of the LDAP authentication providers.
Level: 1

Type: WARNING

Impact: Security

BEA-090056: User {0} had{1,choice,1# one invalid login attempt|2# {1,number} invalid login attempts}, locking account for {2} minutes.

Cause: User exceeded the value of Lockout Threshhold attempts within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.

Action: For more information about protecting user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090060: The AccessDecision class "{0}" returned an error: {1}

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090063: The DeployableRoleMapper "{0}" returned an error: {1}

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090064: The DeployableAuthorizer "{0}" returned an error: {1}

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090065: Getting boot identity from user.

Cause: The boot identity not provided by the command line argument or a problem exists with the boot.properties file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090066: Problem handling boot identity. The following exception was generated: {0}

Cause: Security permissions are not correct.

Action: Contact the system administrator.
Level: 1

Type: WARNING

Impact: Security

BEA-090067: User lockout expired, unlocking user {0} in security realm {1}.

Cause: The period of time specified for the Lockout Duration attribute has expired for this user account. The user account was locked for exceeding the number of invalid login attempts specified in the Lockout Threshold attribute within the period of time specified in the Lockout Reset Duration attribute.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090070: Failed to broadcast unlock user {0} in security realm {1} to the other cluster servers, {2}.

Cause: An IOException occurred.

Action: For more information about unlocking user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090072: Boot problem with filter rules. The reason was: {0}. The problem is in the rules for the connection filter.

Cause: Rules for the filter are possibly corrupted.

Action: Contact the system administrator and have the rules corrected.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090073: Problem with updating filter rules. The reason was: {0}. The problem is in the rules for the connection filter. The rules will not be updated in the repository.

Cause: Rules for the filter are incorrect.

Action: Correct the offending rules.
Level: 1

Type: WARNING

Impact: Security

BEA-090074: Initializing {0} provider using LDIF template file {1}.

Cause: Either this is the first time this security provider has been initialized or the marker file indicating initialization (with a .initialized extension) has been removed from the system.

Action: Look for a matching LoadedLDIFFForProvider message which indicates the successful loading of the LDIF information for this security provider.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090075: The {0} provider has had its LDIF information loaded from: {1}.

Cause: The provider was requested to import data.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090076: A failure occurred while attempting to load LDIF for provider {0} from file {1}.

Cause: An exception occurred while attempting to open a temporary file as part of the load process.

Action: Examine the exception and correct the cause.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090077: A failure occurred while attempting to create {1} for the {0} provider had been loaded. The exception is {2}.

Cause: Read the exception to determine the cause.

Action: Take appropriate action to keep the exception from happening again. The marker file can be created manually.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090078: User {0} in security realm {1} has had {2,choice,1# one invalid login attempt|2# {2,number} invalid login attempts}, locking account for {3} minutes.

Cause: User exceeded the number of invalid login attempts specified in the Lockout Threshhold attribute within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.

Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090079: Failed to broadcast LoginFailureRecord for security realm {0} to the other cluster servers, {1}.

Cause: An I/O exception occurred.

Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090080: The Server Private Key for server {0} was found in SSL.ServerKeyFileName.

Cause: This is an informational message.

Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090082: Security initializing using security realm {0}.

Cause: This message is for informational purposes.

Action: Verify that the correct security realm is configured.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090083: Storing boot identity in the file: {0}.

Cause: This message is for informational purposes.

Action: Do not delete this file if you want the server to continue to boot without prompting for username and password.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090087: Server failed to bind to the configured administrator port. The port may already be in use by another process.

Cause: Most likely another process opened the administrator port, thus causing a port conflict.

Action: Inspect the log file for messages that identify the reason why none of the listen ports could be opened.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090088: Private Key keystore alias is not specified in the SSL configuration of server {0}, security realm {1}. Assuming 6.x private key configuration. Loading the private key from a file.

Cause: The keystore alias is not specified in the Server Private Key Alias attribute.

Action: Set the Server Private Key Alias attribute with the alias used to load the private key of the server into the keystore.
Level: 1

Type: WARNING

Impact: Security

BEA-090089: SSL did not find the passphrase for the private key of the server on server {0} for security realm {1}. This may cause an error when SSL attempts to load the private key of the server.

Cause: Either the Server Private Key PassPhrase attribute is not set or the Identity PassPhrase attribute is not set.

Action: If a passphrase is required to retrieve the private key from a keystore, set the Server Private Key PassPhrase attribute.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090091: SSL was unable to get a required Security Service.

Cause: A security service was requested, but no value was returned.

Action: It is likely that the server's configuration has been corrupted. Restore the configuration files from backup. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090093: No pre-WLS 8.1 Keystore providers are configured for server {0} for security realm {1}.

Cause: This is an informational message.

Action: To use pre-WLS 8.1 keystores with the SSL configuration, at least one Keystore Provider must be configured.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090095: SSL cannot instantiate the keystore {1} on server {0}.

Cause: An exception occurred while creating the keystore. This exception caused the create to fail.

Action: Most likely, the keystore was not configured correctly. Ensure that the keystore provider has been configured on the named server. Review the server log for subsequent messages that contain the exception from the keystore provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090096: The MBeans configured for the keystore provider on server {0} for security realm {1} are not Keystore MBeans.

Cause: The MBeans passed to the WebLogic Server key management initialization method are not Keystore MBeans.

Action: Most likely, the keystore provider was not configured correctly. Check that the keystore provider has been configured on the named server.
Level: 1

Type: ERROR

Impact: Security

BEA-090097: The KeyManager class for private keys server {0} for security realm {1} could not be instantiated.

Cause: The Key Manager Security service is null.

Action: There was a problem with the installation of WebLogic Server because the KeyManager is an internal class that supports the WebLogic Security service.
Level: 1

Type: ERROR

Impact: Security

BEA-090101: A keystore exception was returned when the server {1} attempted to load trusted CAs from the keystore file {0}.

Cause: The keystore JDK method threw a keystore exception.

Action: There is a problem with the keystore file. Verify that the file is intact and valid. Use the JDK keytool utility to display the contents of the file. If the file is corrupt, down load a new file from the JavaSoft web site or configure a trusted CA keystore. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090108: The server was unable to retrieve the private key aliased by {2} from the configured keystore on server {0} for security realm {1}. Private key password might be invalid.

Cause: An exception was returned by the keystore getKey method.

Action: Check that a private key keystore is configured on the server. Verify that the private key keystore exists. Ensure that the keystore is valid and contains the private key necessary to use SSL on the server. Verify that the passphrase configured for the private key was the one used to load the private key into the keystore when the private key was created. This exception most often occurs when the passphrase is invalid. Check the log for subsequent messages that contain the key store exception. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090109: The server was unable to find the configured private key on server {0} in the file specified by the SSL Server Key File Name attribute.

Cause: The server looks at the Server Key File Name attribute to load the private key of the server when it cannot find the private key in a configured keystore using the alias that is specified in the Server Private Key Alias attribute as the alias string. One possible cause of this error is that server is not configured with a private key keystore or the server is configured to use the pre-7.0 SSL attribute Server Key File Name.

Action: A pre-7.0 configuration is being used for SSL connections, however that configuration does not specify a value for the Server Key File Name attribute. Either provide a value for the Server Key File Name attribute or configure a keystore for the server. SSL will not be able to initialize until the configuration is corrected. For more information, see the security documentation available at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090110: The server was unable to find the configured certificate on server {0} in the file specified by the Server Certificate File Name attribute {1}.

Cause: The server looks at the Server Certificate File Name attribute to load the certificate for the server. One possible cause of this error is that the server is not configured with a certificate, or there is a problem with the file configured as the server's certificate.

Action: Verify that a certificate file is configured for the server and that the certificate contained in the file is valid. For more information, see the security documentation available at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090112: SSL is configured to require clients to present their certificates, however, no trusted certificates have been loaded. The trusted certificates are necessary for validating client certificates.

Cause: Either the "Client Certificates Enforced" option was set by mistake or the problem is with SSL trusted certificates configuration.

Action: Clear the "Client Certificates Enforced" option or specify the location of keystore that contains the trusted certificates.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090113: Loaded {0} client trusted CAs from keystore.

Cause: Loaded the specified number of trusted certificate authority from the trust keystore. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090116: The server {0} is using the private key it retrieved from keystore aliased by {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090118: LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic provider LDIF template file may have been overwritten with an empty file.

Action: If the server boots successfully, no action is needed. If the server does not boot successfully then an attempt should be made to recover non-empty LDIFT template file from the WebLogic Server kit.
Level: 1

Type: WARNING

Impact: Security

BEA-090119: LDIF template file {1} not found. The WebLogic Server provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic Server provider LDIF template file may have been deleted by mistake.

Action: If the server boots successfully, no action is needed. If the server does not boot successfully, an attempt should be made to recover the LDIFT template file from the WebLogic Server kit.
Level: 1

Type: WARNING

Impact: Security

BEA-090120: Cannot find the file specified by SSL.TrustedCAFileName {0} on server {1}.

Cause: The specified file was not found.

Action: Verify that the specified file exists in the expected directory and/or that the value of Trusted CA File Name attribute refers to an existing file.
Level: 1

Type: WARNING

Impact: Security

BEA-090121: Loaded {0} client root CAs from TrustedCA File.

Cause: Trusted CA certificates were loaded from a trusted CA file.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090122: Loaded {0} client root CAs from Default Key Store file {1}

Cause: Trusted CA certificates were loaded from the default keystore.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090123: Cannot access specified trusted CA file {0} on server {1}.

Cause: File might be read-protected

Action: Ensure that the trusted CA file is accessible by the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090124: Cannot read certificates from the trusted CA file {0} on server {1}.

Cause: The file format is not supported by the server.

Action: Ensure that the file format is valid and is supported by the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090125: Loaded {0} trusted certificates from keystore file specified on the command line: {1}.

Cause: Trusted certificates were loaded from the keystore specified on the command line.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090126: Unable to read a valid version number for property {0} from file {1}. Received exception {2}.

Cause: The value for the {0} property may have been corrupted.

Action: Shut down the server. Attempt to determine what the proper value for the {0} property should be and edit the file so that it reflects that value. If it is not possible to determine the proper value for the {0} property, edit the file and reset the {0} value to 0. Restart WebLogic Server.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090127: Encountered a {2} exception while attempting to read from file {1} for WebLogic {0} provider.

Cause: The {1} file may have been deleted while it was being accessed.

Action: Shut down the server. Attempt to restore the file from a backup. If no backup is available, restart the server. Note that the default WebLogic Server provider might not be correctly initialized.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090129: Updating {0} provider to version {2} using LDIF update template file {1}.

Cause: This security provider has not yet been updated or the marker file indicating initialization (with a .initialized extension) has been removed.

Action: Look for a matching LoadedLDIFFForProvider message in the log file which indicates success loading the LDIF information for this security provider.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090130: Failure {3} while attempting to update the LDIF to version {2} in file {1} for WebLogic {0} provider.

Cause: The directory into which the {1} is to be written may not be writable, the file may not be writable, or the file may not be a valid properties file.

Action: Ensure that both the directory and file are writable. If they are writable, restore the file from backup or open the file and see if the properties within it are corrupt and correct accordingly. The version for provider {0} needs to be set to {2} in the file.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090131: Could not create a {0} JDK keystore instance. Exception: {1}

Cause: {0} is not a valid JDK keystore type or the JDK keystore type is not properly configured.

Action: Verify that the correct keystore type was specified and that the keystore type is correctly specified in the java.security file. Verify that the code for the JDK keystore is in the JDK extensions directory. Restart the serverr after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090132: Could not open the keystore file {0} for read access. Exception: {1}

Cause: The file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading.

Action: Verify that the correct path to the keystore file was specified and that the keystore file exists. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090133: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: There is an I/O or format problem with the keystore data.

Action: Verify that the path to the keystore, the keystore type, and the password for the keystore were specified correctly. Note that some keystore types (for example, JKS) do not require a password for read-only access. Read the exception text for more help on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090134: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: Some certificates in the keystore could not be loaded.

Action: Verify that the crypto providers required by the certificates in the keystore are properly configured in the java.security file and that their code is in the JDK extensions directory. Look at the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090135: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: The algorithm used to check the integrity of the keystore cannot be found.

Action: Verify that the algorithm used to check the keystore integrity is properly configured in the java.security file and that the code is in the JDK extensions directory. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090136: Could not open the keystore file {0} for write access. Exception {1}

Cause: The file may exist but is a directory rather than a regular file, the file does not exist and cannot be created, or the file cannot be opened.

Action: Verify that the correct pathname to the keystore was specified and that the parent directory exists. If neither of these problems exist, read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090137: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: There was an I/O problem with the keystore data.

Action: Verify that the passphrase is correct. Some JDK keystore implementations require the use of the password for a previous keystore. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090138: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: Some certificates included in the keystore could not be stored.

Action: Verify that the crypto providers required by the certificates in the keystore are properly configured in the java.security file and that their code is in the JDK extensions directory. Look at the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090139: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: The data integrity algorithm for the keystore could not be found.

Action: Verify that the algorithm used to check the keystore integrity is properly configured in the java.security file and that the code is in the JDK extensions directory. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090140: Could not store a {1} keystore in the file {0}. Exception: {2}

Cause: The keystore has not been initialized (loaded).

Action: Make sure to load the keystore before storing it. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090141: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its private key keystore was not configured.

Cause: The Private Key Store Location attribute was not specified.

Action: To use the WebLogic keystore provider to store private keys, perform the following steps. Create a JDK keystore and load the private keys into the keystore. Use the Administration Console to attributes on the WebLogic keystore provider. Set the Private Key Store Location attribute to the path of the JDK keystore file. Set the Private Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the type of the JDK keystore (the Type attribute may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090142: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted (root) CAs because its trusted (root) CA keystore was not configured.

Cause: The Root Key Store Location attribute was not specified.

Action: To use the WebLogic keystore provider to store trusted CAs, perform the following steps. Create a JDK keystore. Load the trusted CA certificates into the keystore. Set attributes on the WebLogic keystore provider. Set the Root Key Store Location attribute to the path of the JDK keystore file. Set the Root Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the JDK keystore type (the type may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090143: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its configured private key keystore file {2} does not exist.

Cause: The file {2} does not exist as a global pathname or in the domain directory.

Action: To use the WebLogic keystore provider to store private keys, perform the following steps. Create a JDK keystore and load the private keys into the keystore. Use the Administration Console to set attributes on the WebLogic Keystore provider. Set the Private Key Store Location attribute to the path of the JDK keystore file. Set the Private Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the type of the JDK keystore (the Type attribute may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090144: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted (root) CAs because its configured trusted (root) CA keystore file {2} does not exist.

Cause: The file {2} does not exist as a global pathname or in the domain directory.

Action: To use the WebLogic keystore provider to store trusted CAs, perform the following steps. Create a JDK keystore. Load the trusted CA certificates into the keystore. Set attributes on the WebLogic keystore provider. Set the Root Key Store Location attribute to the path of the JDK keystore file. Set the Root Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the JDK keystore type (the type may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090145: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its private key {3} keystore could not be loaded from the file {2}.

Cause: See the error logged before this one for details.

Action: Verify that the Root Keystore Location attribute is specified correctly. Verify that the Root Keystore PassPhrase attribute matches the passphrase of the keystore. Some keystore types (for example, JKS) allow an empty passphrase for read-only access. Verify that the Type attribute is correct. The Type attribute may be left empty if the JDK keystore uses the keystore type configured in the java.security file. Verify that the private key keystore exists and is properly configured. Verify that a keystore for the specified type is properly configured. After correcting the problem, restart the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090146: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted CAs because its trusted CA {3} keystore could not be loaded from the file {2}.

Cause: See the error logged before this one for details.

Action: Verify that the Private Keystore Location attribute is correct. Verify that the Private Keystore PassPhrase attribute matches the passphrase of the keystore. Note that some keystore types (for example, JKS) allow an empty passphrase for read-only access. Verify that the Type attribute is correct. The Type attribute may be empty if the JDK keystore uses the keystore type configured in the java.security file. Verify that the private key keystore exists and is properly configured. Verify that a JDK keystore for the type specified is properly configured. After correcting the problem, reboot the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090152: Demo trusted CA certificate is being used in production mode: {0}. The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.

Cause: A trusted CA keystore contains a demo certificate.

Action: Remove the demo certificate from the trusted CA keystore.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090153: Demo identity certificate is used in production mode: {0} The system is vulnerable to security attacks, since the server private key is available to the public.

Cause: The server is configured with Demo identity and is running in production mode.

Action: Configure the server to use a certificate obtained from a reputable certificate authority.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090154: Identity certificate has expired: {0}.

Cause: Certificate for the server has expired.

Action: Configure the server to use a certificate obtained from a reputable certificate authority.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090155: Identity certificate is not yet valid: {0}.

Cause: The server certificate is not yet valid.

Action: Replace the server certificate with a certificate obtained from a reputable certificate authority.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090156: Invalid identity certificate signature: {0}

Cause: The certificate of the server or the certificate authority that issued the certificate is invalid.

Action: Replace the certificate of the server with a valid certificate.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090157: Unable to verify certificate signature: {0}.

Cause: The certificate of the server or the certificate authority that issued the certificate is invalid.

Action: Replace certificate of the server with a valid certificate.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090158: The server was unable to find the private key with alias {0} at location {1} on server {2}, security realm {3}. Ensure that the keystore exists and contains the key entry under the specified alias.

Cause: The private key alias {0} was not found at location {1} on server {2}, security realm {3}.

Action: Verify that a keystore is configured on the server displayed in the log file. Verify that the keystore for the private key exists, the keystore is a valid, and contains the private key for the server. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090160: Cannot find default trusted CA keystore file {0} on server {1}.

Cause: The keystore does not exist.

Action: Configure a trusted CA keystore.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090161: A failure occurred while attempting to save LDIF for security provider {0} using file {1}.

Cause: An exception occurred while attempting to open a temporary file as part of the export process.

Action: Examine the exception and correct the cause.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090162: The {0} provider has had its LDIF information saved in: {1}.

Cause: The security provider was requested to export data.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090163: The {0} provider did not import a duplicate LDAP entry: {1}

Cause: The security provider already contained the imported data.

Action: Delete the existing data and import data into the security provider again.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090164: Failed to load trusted certificates from keystore {0} of type {1}

Cause: The keystore file cannot be loaded because of invalid password or Keystore type.

Action: Ensure that the keystore configuration is valid.
Level: 1

Type: WARNING

Impact: Security

BEA-090165: Cannot find identity keystore file {1} on server {0}

Cause: The identity keystore does not exist.

Action: Correct the SSL configuration of the server. Specify a valid identity keystore.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090166: Failed to load identity keystore of type {2} from file {1} on server {0}

Cause: File is not a valid keystore file or it is of a different keystore type.

Action: Ensure that the keystore file specified in SSL configuration of the server is valid and of the specified keystore type.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090167: Cannot retrieve identity certificate and private key on server {0}, because the keystore entry alias is not specified.

Cause: The alias for the private key entry in the identity keystore was not specified.

Action: Correct the private key alias in the SSL configuration of the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090168: No identity key/certificate entry was found under alias {2} in keystore {1} on server {0}.

Cause: The private key entry does not exist in the specified keystore under the specified alias. The wrong alias or keystore was specified or the entry under the specified alias is not a private key.

Action: Ensure that the entry for the private key exists in the specified keystore under the specified alias.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090169: Loading trusted certificates from the {1} keystore file {0}.

Cause: The server is loading trusted CA certificates from the specified keystore.

Action: Verify that the correct trusted CA certificate and keystore are being used.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090171: Loading the identity certificate and private key stored under the alias {2} from the {1} keystore file {0}.

Cause: The server is loading the identity certificate and the corresponding private key from the specified keystore.

Action: Verify that the certificate information such as keystore location, alias, and type are correct.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090172: No trusted certificates have been loaded. Server will not trust to any certificate it receives.

Cause: Keystores specified in the SSL configuration of the server do not contain certificates or do not exist.

Action: Correct the trusted CA information in the SSL configuration of the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090173: The server's trust keystore configuration (specified on the command line or in boot.properties) is incorrect.

Cause: Either TrustKeyStores was set to an illegal value or TrustKeyStores was set to CustomTrust but CustomTrustKeyStoreFileName was not specified.

Action: If specifying the server's trust keystore on the command line: To use the trusted CAs in DemoTrust.jks and in the JDK''s cacerts, specify: -Dweblogic.security.TrustKeyStore=DemoTrust defaults to DemoTrust -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=passphrase defaults to no passphrase which means read-only access to the JDK''s cacerts. To use the trusted CAs in the JDK''s cacerts, specify: -Dweblogic.security.TrustKeyStore=JavaStandardTrust -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=passphrase defaults to no passphrase which means read-only access to the JDK''s cacerts. To use the trusted CAs from another keystore, specify: -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName=filename either an absolute pathname or a pathname relative to the directory in which the server was started. -Dweblogic.security.CustomTrustKeyStoreType=type defaults to the default keystore type specified in the JDK''s java.security file. -Dweblogic.security.CustomTrustKeyStorePassPhrase=passphrase defaults to no passphrase. Some keystore types allow this but only grant read-access (for example, JKS). Other keystore types require a keystore passphrase even for read-access. If specifying the server's trust keystore via boot.properties, set the same properties as for the command line to boot.properties but remove the weblogic.security prefix. For example, set TrustKeyStore=JavaStandardTrust.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090174: The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.

Cause: Either the trust keystore type does not match (for example, one specifies CustomTrust and the other specifies JavaStandardTrust) or the configuration values do not match (for example, the CustomTrustKeyStoreFileName values are not the same).

Action: To always specify the trusted CA keystore for the server on the command line or the boot.properties file, set the server's Keystores value in the config.xml file to CustomIdentityAndCommandLineTrust. Otherwise, ensure that the trust keystore configuration for this server in config.xml matches the trust keystore configuration specified on the command line or in boot.properties.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090175: Unrecognized Callback

Cause: Only callbacks of NameCallback or PasswordCallback are supported.

Action: Remove the unsupported callback from the list of callbacks.
Level: 1

Type: ERROR

Impact: Security

BEA-090176: Illegal null Subject passed as a parameter.

Cause: The Subject parameter cannot be null.

Action: Verify that the subject passed as a parameter is not null. If no subject utility methods are being called, this exception indicates an internal coding error in the server. This exception should not normally occur. Check with My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090177: Invalid Message Digest requested, only MD5, SHA, and MD2 are supported.

Cause: The Message Digest type is not supported.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090178: null Class

Cause: The class used to filter principals is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090179: Null action

Cause: The doAs method expects the action to not be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090180: Could not convert AS to AU: {0}.

Cause: An exception occurred when converting.

Action: Look at the exception text to diagnose the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090181: Attempting to modify a sealed subject.

Cause: A sealed subject is read-only and cannot be modified.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090182: {0} is not a java.security.Principal.

Cause: The object is not a principal. Only principals can be added to a subject.

Action: Verify that the authentication provider is correctly creating principals.
Level: 1

Type: ERROR

Impact: Security

BEA-090183: Got a NullPointerException in AuthenticatedUser.hashCode() with actual type {0}.

Cause: The authenticated user name, qos, or localPort is null.

Action: This exception indicates an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090184: invalid constraints

Cause: None of the specified constraints are supported.

Action: Remove the unsupported constraints or pass-in supported constraints. Supported constraints are @quot;users@quot; and @quot;groups@quot;.
Level: 1

Type: ERROR

Impact: Security

BEA-090185: No CallbackHandler was specified.

Cause: The callback handler is null.

Action: Pass a non-null callback handler when initializing the UsernamePasswordLoginModule.
Level: 1

Type: ERROR

Impact: Security

BEA-090186: Error: Callback {0} is not available.

Cause: The callback handler does not support one of callbacks required by the UsernamePasswordLoginModule. The UsernamePasswordLoginModule requires 3 callbacks: NameCallback, PasswordCallback, and URLCallback.

Action: Verify that the callback handler that is specified in the initialize method of UsernamePasswordLoginModule supports the three required callbacks.
Level: 1

Type: ERROR

Impact: Security

BEA-090187: {0} (Unable to delete)

Cause: The file could not be deleted.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090188: Cannot update a read-only PermissionCollection.

Cause: The collection is read-only and permissions cannot be added.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090190: Error creating {0}

Cause: Either the file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading.

Action: Verify the filename. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090191: Error writing realm contents to {0}.

Cause: An error occurred while writing the file.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090192: Could not create temporary file for {0}, .new, {1}.

Cause: An error occurred while creating the temporary file.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090193: Could not create temporary file for {0}, .old, {1}.

Cause: An error occurred when creating the temporary file.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090194: Could not clear temporary file {0}.

Cause: The delete method returned false.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090195: Could not rename {0} to {1}.

Cause: The rename method returned false.

Action: Verify that the file can be renamed and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090196: Could not delete {0}.

Cause: The delete method returned false.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

BEA-090197: Cannot find permission {0}.

Cause: A ClassNotFound exception occurred when instantiating the permission.

Action: Verify that the class is contained in the classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-090198: No appropriate constructor for {0}

Cause: A NoSuchMethod exception occurred when instantiating the permission.

Action: Verify that the permission class implements the constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090199: Cannot instantiate abstract class {0}.

Cause: An Instantiation exception occurred when instantiating the permission.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090200: No permission to instantiate constructor for {0}

Cause: An IllegalAccess exception occurred when instantiating the permission.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090201: Incorrect argument for constructor for {0}

Cause: An IllegalArgument exception occurred when instantiating the permission.

Action: Verify that the permission class implements the appropriate constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090202: Exception in constructor for {0}

Cause: An InvocationTarget exception occurred when instantiating the permission.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090203: Trailing text after grant string

Cause: Text is present after the closing bracket and semicolon.

Action: Remove the text after the closing bracket and semicolon.
Level: 1

Type: ERROR

Impact: Security

BEA-090204: Unexpected end of string in grant statement

Cause: The grant statement is not complete.

Action: Verify the grant statement and add the necessary text.
Level: 1

Type: ERROR

Impact: Security

BEA-090205: Expected "{0}" but found "{1}".

Cause: The syntax is incorrect.

Action: Verify the syntax and add the specified expected construct.
Level: 1

Type: ERROR

Impact: Security

BEA-090206: Expected a guote (") but found "{0}".

Cause: An expected quote was not found.

Action: Verify the syntax and add the quote.
Level: 1

Type: ERROR

Impact: Security

BEA-090207: Version mismatch, have {0}, expected {1}.

Cause: The version number does not match the expected value.

Action: Verify that the SerializedSystemIni.dat file has not been corrupted.
Level: 1

Type: ERROR

Impact: Security

BEA-090208: Corrupt {0}

Cause: An IOException occurred when reading bytes from the file.

Action: Verify that the SerializedSystemIni.dat file is valid. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090209: Could not close stream: {0}.

Cause: An IOException was returned by the input stream close method.

Action: Verify that the SerializedSystemIni.dat file is valid. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090210: Error opening {0}

Cause: A FileNotFound exception occurred while opening the input stream.

Action: Verify that the SerializedSystemIni.dat file exists and is accessible. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090218: decoding error: {0}

Cause: An IOException occurred.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090219: Error decrypting Secret Key {0}

Cause: An exception occurred when getting the secret key for the encryption service.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090220: rule {0}

Cause: A connection filter rule denied access.

Action: None. This exception is used to deny access to the server as specified in the rules of the connection filter.
Level: 1

Type: ERROR

Impact: Security

BEA-090221: Connection filter internal error!

Cause: An unknown connection filter rule was encountered.

Action: Verify the connection filter rules. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090222: unknown protocol "{0}"

Cause: The protocol specified in the connection filter is not supported.

Action: Verify the protocol and ensure it is listed in the rules of the connection filter.
Level: 1

Type: ERROR

Impact: Security

BEA-090223: bad netmask: "{0}"

Cause: The netmask is greater than 32 bits or less than 0.

Action: Verify the netmask in the connection filter.
Level: 1

Type: ERROR

Impact: Security

BEA-090224: bad netmask: "{0}"

Cause: The number of tokens in the netmask is not 4.

Action: Verify the netmask.
Level: 1

Type: ERROR

Impact: Security

BEA-090225: bad netmask: "{0}"

Cause: The number in the netmask is less than 0 or greater than 255.

Action: Change the number in the netmask to be greater than or equal to 0 and less than or equal to 255.
Level: 1

Type: ERROR

Impact: Security

BEA-090226: bad netmask: "{0}"

Cause: A NumberFormat exception occurred when calling Integer.parseInt on the netmask token.

Action: Verify the netmask token to ensure it is an integer.
Level: 1

Type: ERROR

Impact: Security

BEA-090227: bad action "{0}"

Cause: The action is not deny or allow.

Action: Verify the action and change it to deny or allow.
Level: 1

Type: ERROR

Impact: Security

BEA-090228: null filter

Cause: A connection filter cannot be null.

Action: Verify the connection filter and ensure that a connection filter is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090229: Attempt to set connection filter more than once

Cause: A connection filter was set more than once.

Action: Modify the application code to only call the setFilter method once.
Level: 1

Type: ERROR

Impact: Security

BEA-090230: Zero length PEMInputStream

Cause: The Privacy Enhanced Mail (PEM) input stream contained zero bytes.

Action: Verify that the PEM file or PEM input stream is valid and does not contain zero bytes.
Level: 1

Type: ERROR

Impact: Security

BEA-090231: Security already configured

Cause: The Security service initialization method was called twice.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090232: salt is not set

Cause: The salt obtained from the MBean is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090233: problem with connection filter rules

Cause: An exception occurred while setting the connection filter rules. The filter class may not have been loaded or some other error may have caused the exception.

Action: Verify the connection filter class and rules. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090238: could not create User Name Mapper

Cause: An exception occurred while loading the User Name Mapper class.

Action: Verify that the User Name Mapper class exists in the class path and the class implements the UserNameMapper interface.
Level: 1

Type: ERROR

Impact: Security

BEA-090239: Identity Assertion type cannot be null

Cause: The token type was null.

Action: The containers should not be passing a null token type. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090240: Identity Assertion token cannot be null

Cause: The identity assertion token was null.

Action: The containers should not be passing a null token. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090241: Identity Assertion type of {0} is not a configured active type.

Cause: The identity assertion token type was not configured in the WebLogic Identity Assertion provider.

Action: Configure the identity assertion type {0} in the Active Types attribute of the WebLogic Identity Assertion provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090242: Client principal {0} is not trusted to assert identity.

Cause: Client principal {0} is not in the list of clients trusted to assert identity via CSIv2 identity assertion tokens.

Action: Add the client principal to the Trusted Client Principals attribute of the WebLogic Identity Asserter provider or specify asterisk (*) to allow any client to assert any identity.
Level: 1

Type: ERROR

Impact: Security

BEA-090243: user Name Mapper class not configured - cannot assert identity

Cause: No User Name Mapper is configured.

Action: Configure a User Name Mapper. Use either the default User Name Mapper or a custom User Name Mapper. To use the default implementation, set the Use Default User Name Mapper attribute for the WebLogic Identity Assertion provider. To use a custom User Name Mapper, set the User Name Mapper Class Name attribute to the name of the custom implementation.
Level: 1

Type: ERROR

Impact: Security

BEA-090244: Unknown Identity Assertion type {0}

Cause: Identity Assertion type {0} is not supported.

Action: Use a supported identity assertion type or write a custom Identity Assertion provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090245: No mapping for Identity User Name

Cause: The identity assertion token could not be mapped to a username.

Action: If this is not the expected outcome, modify the custom User Name Mapper to correctly map the desired token to a username.
Level: 1

Type: ERROR

Impact: Security

BEA-090246: Token not of type {0}

Cause: The token does not match the token type.

Action: The containers should not be passing a token that is not an AuthenticatedUser. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090247: Unable to verify {0}

Cause: The authenticated user is invalid.

Action: Verify that the user identity was from this domain or from a domain that is trusted by this domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090248: Unrecognized Callback

Cause: Callback type is not supported.

Action: Verify that the LoginModule for the configured Authentication provider is only passing a NameCallback when calling the handle method.
Level: 1

Type: ERROR

Impact: Security

BEA-090249: Cursor is null

Cause: A null cursor is not supported.

Action: Modify the code to pass a non-null cursor.
Level: 1

Type: ERROR

Impact: Security

BEA-090250: Cursor not found {0}

Cause: Cursor was not found in the list of valid cursors.

Action: Verify that the cursor passed to the method is valid and was returned from a method that creates cursors. Examples of such methods are listUsers, listGroups and listRoles.
Level: 1

Type: ERROR

Impact: Security

BEA-090251: haveCurrent error for cursor name {0}

Cause: An LDAP exception occurred during the haveCurrent method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090252: advance error for cursor name {0}

Cause: An LDAP exception occurred while advancing the list.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090253: close error for cursor name {0}

Cause: An LDAP exception occurred while closing this list cursor.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090258: max cannot be < 0

Cause: The maximumToReturn value cannot be less than zero.

Action: Pass in a maximumToReturn parameter value that is greater or equal to zero.
Level: 1

Type: ERROR

Impact: Security

BEA-090259: Group {0}

Cause: Group {0} does not exist in the LDAP server.

Action: Pass in a group that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090261: Wildcard cannot be null.

Cause: The wildcard parameter is null.

Action: Pass a non-null wildcard parameter to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090262: Error listing groups {0}

Cause: An LDAP exception occurred while searching for the groups in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090263: parent group cannot be null

Cause: The parent group name is null.

Action: Pass a non-null parent group name parameter to this method.
Level: 1

Type: ERROR

Impact: Security

BEA-090264: member cannot be null

Cause: The member name is null.

Action: Pass a non-null member name parameter to this method.
Level: 1

Type: ERROR

Impact: Security

BEA-090265: member cannot be parent group

Cause: The member name and parent group name are the same value.

Action: Change either the member name or parent group name parameters of this method.
Level: 1

Type: ERROR

Impact: Security

BEA-090266: group name cannot be null

Cause: The group name cannot be null.

Action: Pass a non-null group name to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090271: Member {0}

Cause: The member does not exist.

Action: Pass in a member name that exists in the LDAP server.
Level: 1

Type: ERROR

Impact: Security

BEA-090278: Error listing member groups {0}

Cause: An LDAP exception occurred while listing the member groups in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090279: Error listing users {0}

Cause: An LDAP exception occurred while listing the users in the LDAP server.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090281: user name cannot be null

Cause: The user name cannot be null.

Action: Pass a non-null user name to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090283: User {0}

Cause: User {0} already exists in the LDAP server.

Action: Pass in another user name.
Level: 1

Type: ERROR

Impact: Security

BEA-090287: User {0}

Cause: User {0} does not exist in the LDAP server.

Action: Pass a user name that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090294: could not get connection

Cause: An LDAP exception occurred because an LDAP connection could not be obtained from the connection pool.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090296: invalid URL {0}

Cause: An LDAP exception occurred because of an invalid dynamic group URL.

Action: Verify the dynamic group definition. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090297: No CallbackHandler specified

Cause: The callback handler is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090298: No Delegate specified

Cause: The LDAP delegate is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090299: Username not supplied.

Cause: The user name returned from the NameCallback cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090300: Identity assertion failed: User {0} does not exist.

Cause: The user does not exist in the LDAP server.

Action: Add the user to the LDAP server or configure the Identity Assertion provider to return a user that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090301: Password not supplied.

Cause: The password cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090302: Authentication failed: User {0} denied.

Cause: The username and password could not bind to the LDAP server.

Action: Verify the username and password.
Level: 1

Type: ERROR

Impact: Security

BEA-090305: Authentication failed getting groups for User {0} {1}.

Cause: A group to which the user belongs was not found.

Action: Verify the groups to which the user belongs.
Level: 1

Type: ERROR

Impact: Security

BEA-090307: DefaultAuthenticatorImpl constructor failed: {0}

Cause: A exception was thrown in the constructor for the WebLogic Authentication provider.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090309: null subject

Cause: The subject cannot be null.

Action: Pass a non-null subject to the method.
Level: 1

Type: ERROR

Impact: Security

BEA-090310: Failed to create resource.

Cause: An EnCreateException occurred when creating the security policy.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090311: Failed to set resource expression.

Cause: An EnCreateException occurred when setting the security policy expression.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090313: policy removal error

Cause: A EnRemoveException occurred during the deletion of security policies for the application.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090314: Entitlement Engine unable to connect to the embedded LDAP server {0}

Cause: An exception occurred when initializing the entitlement engine for the WebLogic Authorization provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090315: DefaultAuthorizerImpl init failed: {0}

Cause: An exception occurred during the initialization of the WebLogic Authorization provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090316: null helper

Cause: The helper cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090318: DefaultRoleMapperImpl init failed: {0}

Cause: An exception occurred in the initialization method of the WebLogic Role Mapping provider.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090319: Unknown resource type: {0}

Cause: The role id cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090320: Failed to create role

Cause: An exception occurred during the createRole method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090321: Failed to set role expression

Cause: An exception was thrown during the setRole method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090322: role removal error

Cause: An EnRemoveException occurred during the delete operation.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090323: Map cannot be modified.

Cause: Not all Map object methods are unsupported.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090330: DefaultCredentialMapperImpl.getCurrentMappingWLSUsername failed: No such resource maps list cursor available

Cause: The cursor is invalid.

Action: Verify that the cursor was returned from the listMappings method.
Level: 1

Type: ERROR

Impact: Security

BEA-090344: A valid security realm name must be specified when initializing.

Cause: The security realm name is null or does not exist.

Action: Verify the security configuration. Ensure that the default security realm is set and that the security realm exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090347: Auditor not yet initialized

Cause: The Auditing provider was not initialized before the writeEvent method was called.

Action: This exception that indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090348: No AuthorizerMBeans and no AdjudicatorMBean provided.

Cause: No provider MBeans were passed during the initialization of the Authorization Manager.

Action: Configure at least one Authorization provider for the security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090349: Need at least one AuthorizerMBean

Cause: An empty array of provider MBeans were passed during the initialization of the Authorization Manager.

Action: Configure at least one Authorization provider for this security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090350: The RoleManager must be initialized prior to initializing an Authorization Manager.

Cause: Role Manager is not initialized.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090357: Calling isProtectedResource before the AuthorizationManager is initialized.

Cause: The Authorization Manager must be initialized before any method calls.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090358: Required parameter not supplied to isAccessAllowed.

Cause: A required parameter was null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090359: Required parameter not supplied to isProtectedResource.

Cause: A required parameter was null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090361: Exception: CredentialManager.initialize, Invalid or missing CredentialMapperMBean Mbean

Cause: The array of Credential Mapping MBeans was null or empty.

Action: Verify the security realm configuration and ensure that a Credential Mapping provider is configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090364: Exception: CredentialManager.getCredentials, credentialsType = null

Cause: The credentialType parameter cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090365: LoginModule error: loginModuleName {0}

Cause: A ClassNotFound, IllegalAccess, or Instantiation exception occurred while loading the delegate LoginModule.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090366: LoginModule error: null delegateLoginModuleName

Cause: The delegate LoginModule is null.

Action: Verify the Authentication provider has correctly implemented the getLoginModuleConfiguration method.
Level: 1

Type: ERROR

Impact: Security

BEA-090368: MBeans are not instances of Keystore MBean.

Cause: An MBean is not of type Keystore MBean.

Action: Verify the WebLogic Keystore provider is configured properly.
Level: 1

Type: ERROR

Impact: Security

BEA-090369: Problem instantiating Keystore provider

Cause: An exception occurred during the creation or initialization of the WebLogic Keystore provider.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090370: Invalid configuration, no AuthenticationProviderMBean passed to initialize.

Cause: No Authentication provider MBeans were passed.

Action: Verify the security realm configuration and ensure that an Authentication provider is configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090372: No CallbackHandler Supplied

Cause: The callback handler is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090375: Null TokenType parameter

Cause: The token type is null.

Action: The containers should not pass a null token types. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090376: Null Token parameter

Cause: The identity assertion token was null.

Action: The containers should not pass null tokens. This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090384: No Provider MBeans

Cause: No MBeans were passed during the initialization of the Role Manager.

Action: Configure a Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090389: RoleManager not yet initialized.

Cause: The Role Manager must be initialized before the getRoles method can succeed.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090391: Null user identity

Cause: The identity for the runAs method cannot be null.

Action: Ensure that the subject passed to the runAs method is valid.
Level: 1

Type: ERROR

Impact: Security

BEA-090392: SecurityServiceManager not yet initialized.

Cause: The Security service must be initialized before any method calls.

Action: This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090393: Security service not yet initialized: {0}.

Cause: The Security service must be initialized before it can be used.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090394: Must specify a Security realm.

Cause: The security realm name cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090395: Must specify a SecurityService.ServiceType.

Cause: The Security service type cannot be null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090396: Security Realm {0} does not exist.

Cause: The security realm is not a valid.

Action: Verify the security realm has all the required providers configured and the realm is set as the default (active) security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090397: Principal set does not contain a RealmAdapterUser.

Cause: A RealmAdapterUser is required to send a authenticated user to a previous version of WebLogic Server.

Action: Configure the Realm Adapter provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090398: Invalid Subject: {0}

Cause: Principal validation failed for this subject.

Action: Ensure that the subject was created by this domain or in a domain trusted by this domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090399: Security services unavailable

Cause: Authentication and Authorization services are required to perform the boot authorization checks.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090402: Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.

Cause: The user name or password or both from the boot identity file may have been changed since the boot identity file was created.

Action: Update the boot identity file with the correct username and password for the boot identity.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090403: Authentication for user {0} denied.

Cause: The user supplied an invalid password or the user name was invalid.

Action: Reboot the server and specify the current user and password.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090404: User {0} is not permitted to start the server. The server policy may have changed in such a way that the user is no longer able to start the server. Restart the server with the administrative user account or contact the system administrator to update the server policy definitions.

Cause: The server policy may have changed in such a way that the user is no longer able to boot the server.

Action: Reboot the server from the administrative user account or contact the system administrator to update the server policy definitions.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090405: Can only initialize the SecurityService once.

Cause: The initialize method of the Security Service Manager was called more than once.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090407: Invalid security configuration, no default security realm found.

Cause: A default security realm is not defined.

Action: Set one of the configured security realms as the default (active) security realm by setting the Default Realm attribute at the domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090408: Security configuration is unavailable.

Cause: The security configuration MBean was null.

Action: Verify that the SecurityConfiguration MBean is defined in the config.xml file.
Level: 1

Type: ERROR

Impact: Security

BEA-090409: Security credential is unavailable, a credential value must be supplied for the Security configuration.

Cause: The Credential attribute is invalid.

Action: Set the Credential attribute for the security configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090410: Invalid security realm name: {0}

Cause: The Realm MBean is null.

Action: Verify that the security realm name {0} refers to a valid configured security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090411: Security Realm [{0}] is improperly configured.

Cause: One or more exceptions occurred when the security realm was validated.

Action: Read the exception text and correct the configuration of the security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090412: Failed to initialize realm: {0}.

Cause: No security services were found in the security realm.

Action: Configure an Authentication, Authorization, Adjudication, Role Mapping, and Credential Mapping provider in the security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090413: No Realm MBean found. Bad configuration, unable to initialize Security.

Cause: A default security realm is not configured.

Action: Set one of the configured security realms as the default (active) security realm by setting the Default Realm attribute at the domain.
Level: 1

Type: ERROR

Impact: Security

BEA-090414: Need to configure at least one RoleMapperMBean.

Cause: The array of Role Mapping providers for this security realm is null or empty.

Action: Configure at least one Role Mapping provider for this security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090415: Need to configure at least one AuthorizerMBean.

Cause: The array of Authorization providers for this security realm is null or empty.

Action: Configure at least one Authorization provider for this security realm.
Level: 1

Type: ERROR

Impact: Security

BEA-090416: Cannot configure the Keystore providers : {0}

Cause: A Security exception occurred during the get or set of the Alg.Alias.KeyStore property.

Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090419: Subject "{0}" is not the kernel identity.

Cause: The current subject is not the kernel identity.

Action: Verify that the subject in {0} is the correct identity. If so, this exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090420: Security provider error: providerClassName {0} creation exception.

Cause: An Instantiation exception or an IllegalAccess exception occurred while creating and initializing the security provider.

Action: Read the associated exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090421: Security provider error: providerClassName {0} not found.

Cause: A ClassNotFound exception occurred when loading the security provider {0}.

Action: Ensure that the class name in {0} is present. Read the associated exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090423: The Server {0} was unable to find the server certificate file {1} specified by the SSL ServerCertificateFileName attribute.

Cause: The server certificate file was not found.

Action: Verify that the Server Certificate File attribute for server is specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090424: Cannot find the private key with alias {0} in the keystore at location {1}.

Cause: The alias was not found.

Action: Verify that the alias specified in the Server Private Key Alias attribute. Also, verify the contents of the keystore.
Level: 1

Type: ERROR

Impact: Security

BEA-090425: Cannot read private key file {0}. Exception is {1}

Cause: An I/O exception was thrown when loading the private key.

Action: Read the exception text in {1} for more information in diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090426: Cannot read private key from file {0}. Ensure that the password specified in environment property {1} is valid. Exception is {2}

Cause: A KeyManagement exception occurred when loading the private key.

Action: Verify that the password specified in environment property {1}. Verify the format of the private key. Read the exception text in {2} for more information in diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090427: The server {0} was unable to find private key in the file {1} specified by the SSL ServerKeyFileName attribute.

Cause: The file {1} could not be found.

Action: Modify the Server Key File Name attribute to specify a file that exists.
Level: 1

Type: ERROR

Impact: Security

BEA-090428: Cannot call setJava2SecurityMode more than once.

Cause: The setJava2SecurityMode method can only be called once.

Action: Ensure that the setJava2SecurityMode method is only called once.
Level: 1

Type: ERROR

Impact: Security

BEA-090431: Received a null user name.

Cause: The user name cannot be null.

Action: Verify that the specified username is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090433: Inconsistent InvalidLogin record

Cause: The vector of failures is null.

Action: This exception indicates an internal coding error in the server. Contact My Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090434: Enumerator returned a null element for a key.

Cause: The invalid login information entry is null.

Action: Check the list of locked out users and unlock any users manually. Reboot the server if necessary. This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090435: Subject {0} does not have permission to unlock user {1} in security realm {2}.

Cause: No permission to unlock the user.

Action: Use an identity that does have permission to unlock this user.
Level: 1

Type: ERROR

Impact: Security

BEA-090436: Inconsistent hashtable, key exists but not value.

Cause: The invalid login information entry is null.

Action: Check the list of locked out users and unlock any users manually. Reboot the server if necessary. This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

BEA-090437: Security service is unavailable.

Cause: The authentication service is null.

Action: If a security realm name is specified in the login method, verify that the name of the security realm is correct. Otherwise, this exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090438: Invalid parameter

Cause: The user, password, or output directory is null or a zero length string.

Action: Pass in a valid user, password, and output directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090439: Invalid file parameter {0} specified for adminstrator account creation.

Cause: Either the template file does not exist or is not a file, or the output directory does not exist or is not a directory.

Action: Pass in a valid template file and a valid output directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090440: Encryption error

Cause: The encrypted password was null.

Action: Verify that a non-zero length password was passed to the wizard.
Level: 1

Type: ERROR

Impact: Security

BEA-090442: location null or empty

Cause: A keystore filename cannot be null or a zero length string.

Action: Set the keystore location to a valid filename.
Level: 1

Type: ERROR

Impact: Security

BEA-090443: null file

Cause: The load and store methods require a non-null filename.

Action: Pass a valid filename to the keystore load or store method.
Level: 1

Type: ERROR

Impact: Security

BEA-090444: null keystore

Cause: A valid keystore is required for the store method. It cannot be null.

Action: Pass in a non-null keystore to the store method.
Level: 1

Type: ERROR

Impact: Security

BEA-090445: null or empty passphrase

Cause: A passphrase is required for the store method. It cannot be null or a zero length string.

Action: Pass in a valid passphrase.
Level: 1

Type: ERROR

Impact: Security

BEA-090446: Invalid base template

Cause: The file did not contain the appropriate templates for the user or password.

Action: If the Domain Configuration wizard was used, this exception indicates an internal coding error in the server. Contact My Oracle Support. If the Domain Configuration wizard is not being used, verify the contents of the specified template file.
Level: 1

Type: ERROR

Impact: Security

BEA-090447: invalid flag value {0}

Cause: The value specified for the LoginModule control flag is not supported.

Action: Pass in a valid value for the LoginModule control flag. Valid values are REQUIRED, OPTIONAL, REQUISITE, or SUFFICIENT.
Level: 1

Type: ERROR

Impact: Security

BEA-090448: Invalid Format: {0}

Cause: Import format was either null, zero length, or not supported by this provider.

Action: Pass in a supported format.
Level: 1

Type: ERROR

Impact: Security

BEA-090449: Invalid constraints

Cause: Constraints are not supported.

Action: Do not pass constraints to the provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090450: Invalid name supplied

Cause: The filename, domain name, or security realm name cannot be null.

Action: Pass a non null filename, domain name, or security realm name.
Level: 1

Type: ERROR

Impact: Security

BEA-090451: Unable to read file: {0}

Cause: The import file cannot be read.

Action: Check the import file.
Level: 1

Type: ERROR

Impact: Security

BEA-090452: Import is only available on the Administration Server.

Cause: Import operation was attempted on a Managed Server.

Action: Run the MBean client on the Administration Server.
Level: 1

Type: ERROR

Impact: Security

BEA-090453: Import file error

Cause: An IO exception occurred while importing from the file.

Action: Verify the import filename. Read the exception text or the associated log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090454: No base data to export

Cause: The base DN to export from is null or empty.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090455: Export File Error

Cause: An I/O exception occurred while exporting to the file.

Action: Verify the export filename. Read the exception text or the associated log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090456: Three arguments are required.

Cause: Three arguments are not specified.

Action: Verify the signature condition in the Administration Console to ensure that three arguments are specified.
Level: 1

Type: ERROR

Impact: Security

BEA-090457: Type must be {0} or {1} value is {2}.

Cause: The Type argument is not valid.

Action: Verify the signature condition in the Administration Console to ensure that the Type argument is @quot;user@quot; or @quot;group@quot;.
Level: 1

Type: ERROR

Impact: Security

BEA-090458: Signature type cannot be null.

Cause: The Signature type value cannot be null.

Action: Verify the signature condition in the Administration Console to ensure that the signature type argument is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090459: Signed by cannot be null.

Cause: The Signed by value cannot be null.

Action: Verify the signature condition in the Administration Console to ensure that the Signed by argument is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090461: Class not Found {0}

Cause: An class not found exception occurred when getting an instance of the wrapper class.

Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090462: Illegal access on context wrapper class {0}

Cause: An illegal access exception occurred when getting an instance of the wrapper class.

Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090463: Instantiation exception on context wrapper class {0}

Cause: An instantiation exception occurred when getting an instance of the wrapper class.

Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090464: Problem accessing private key

Cause: A key management exception occurred when adding the private key and certificates to the SSL identity.

Action: Verify the private key. Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090465: Problem with certificate chain {0}

Cause: A certificate exception occurred when adding the private key and certificates to the SSL identity.

Action: Verify the certificates. Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1

Type: ERROR

Impact: Security

BEA-090466: Assertion: illegal keystores value: {0}

Cause: The keystore attribute is not valid.

Action: Verify that value {0} is one of the legalvalues listed in the Server MBean Keystores attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090467: problem with connection filter

Cause: An exception occurred while calling the setRules method.

Action: Verify that the connection file class is specified correctly and present in the classpath. Verify that the setRules method is implemented correctly. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090468: Set the AuditProviderClassName attribute to a valid value

Cause: An exception occurred while loading the class.

Action: Verify that the class is specified correctly and present in the classpath. Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090469: Invalid file format

Cause: LDIF template file did not contain any substitution entries and does not have the correct file format.

Action: Verify that the file specified to the import operation is really an LDIF template file produced by an export operation.
Level: 1

Type: ERROR

Impact: Security

BEA-090470: Inconsistent security configuration, the {0} security realm has been configured to use security data in deployment descriptors but no {1} has been configured with deployment enabled.

Cause: The {0} security realm has been configured to use security data in deployment descriptors but no {1} has been configured with deployment enabled.

Action: Either uncheck the "Ignore security data in deployment descriptors" attribute for the security realm to ignore all deployment descriptor security information or configure at least one {1} to have deployment enabled.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090473: DefaultAuthorizerImpl search failed: {0}

Cause: An exception occurred when trying to access the data store.

Action: Look at the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090474: Unable to create temporary file: {0}

Cause: The java.io.tmpdir system property is not set correctly or the temporary directory is not writeable.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090475: Plaintext data for protocol {0} was received from peer {1} instead of an SSL handshake.

Cause: A peer is trying to send plaintext data directly instead of using SSL.

Action: Check the port and protocol settings on the peer that is trying to connect. It may be pointing to the SSL port by mistake or it may be specifying a plaintext protocol by mistake.
Level: 1

Type: WARNING

Impact: Security

BEA-090476: Invalid/unknown SSL header was received from peer {0} during SSL handshake.

Cause: A peer is either sending invalid data, trying to connect using a newer version of SSL that is incompatible with the version of SSL used by WebLogic Server, or is trying to connect using plaintext data from a protocol for which WebLogic Server does not check.

Action: Check the peer that is trying to connect. It may be trying to connect using a plaintext protocol over SSL by mistake, or it may be using some newer incompatible version of SSL.
Level: 1

Type: WARNING

Impact: Security

BEA-090477: Certificate chain received from {0} was not trusted causing SSL handshake failure.

Cause: A peer presented a certificate chain to the server that the server does not trust.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the server trusted CA configuration to trust the CA certificate that signed the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090478: Certificate chain received from {0} was not signed properly causing SSL handshake failure.

Cause: A peer presented a certificate chain to the server that was not signed correctly.

Action: Correct the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090479: Certificate chain received from {0} failed date validity checks.

Cause: A peer presented a certificate chain to the server that is either not yet valid or has expired.

Action: Correct the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090480: SSL alert ({1}) received from {0}. Check the peer SSL configuration, or enable SSL debug tracing on the peer.

Cause: The peer determined something was not correct, sent an alert, and ended the SSL session.

Action: Check the peer to determine why it sent the alert and what alert it believes it sent. This action may require enabling SSL debug tracing to determine the exact cause.
Level: 1

Type: WARNING

Impact: Security

BEA-090481: NO_CERTIFICATE alert was received from {0}. Verify that the SSL configuration has a proper SSL certificate chain and private key specified.

Cause: The SSL configuration for this server needs to supply a certificate chain.

Action: If using one-way SSL, verify that the certificate chain and private key are being specified for the SSL server. If using two-way SSL, verify that the certificate chain and private key are being specified for both the SSL server and the client.
Level: 1

Type: WARNING

Impact: Security

BEA-090482: BAD_CERTIFICATE alert was received from {0}. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason for which the certificate was rejected.

Cause: The certificate chain sent to the peer may not be valid, or the peer may not be configured to accept the certificates.

Action: Check the peer configuration to see if the certificate chain was rejected because the certificate was not trusted or because there was a hostname violation. Verify that the certificate chain sent to the peer had valid dates and had the correct issuer ordering. This action may require enabling SSL debug tracing to determine the exact cause.
Level: 1

Type: WARNING

Impact: Security

BEA-090483: CERTIFICATE_REVOKED alert was received from {0}. The certificate chain sent to the peer was rejected because it was revoked by the certificate authority.

Cause: A certificate in the configured certificate chain was revoked by the certificate authority and is no longer valid.

Action: A new certificate chain needs to be issued by the certificate authority, the SSL configuration then needs to be updated to use the new certificate chain and the new private key that corresponds to it.
Level: 1

Type: WARNING

Impact: Security

BEA-090484: CERTIFICATE_EXPIRED alert was received from {0}. A certificate in the certificate chain expired or is not yet valid, or the peer and local machine have a date/time mismatch.

Cause: A certificate in the chain is either expired or is not yet valid. Another possible cause is the peer machine date/time is not set properly causing the check to fail.

Action: Verify the certificate validity and expiration dates in the certificate chain are correct. If they are not, obtain new certificates issued by the certificate authority and update the SSL configuration with the new certificates and private key. If the dates are valid, check the peer machine date/time setup.
Level: 1

Type: WARNING

Impact: Security

BEA-090485: CERTIFICATE_UNKNOWN alert was received from {0}. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.

Cause: The exact cause is unclear. To determine the cause, check messages from the peer to see if they explain the problem.

Action: Review the SSL messages from the peer by turning on SSL debug tracing.
Level: 1

Type: WARNING

Impact: Security

BEA-090486: UNSUPPORTED_CERTIFICATE alert was received from {0}. The peer rejected a certificate in the chain because it was an unsupported type. Verify all certificates in the chain are valid X.509 RSA certificates.

Cause: This problem could be caused by an incorrect type of certificate in the certificate chain or the peer not being able to handle certain attributes in a valid certificate.

Action: The certificate chain should first be checked to ensure the certificates are all valid X.509 RSA certificates and are using the proper strength. If that is correct, SSL debug tracing may be required on the peer to see if it gives more detail on what was specifically not supported.
Level: 1

Type: WARNING

Impact: Security

BEA-090487: UNKNOWN_CA alert received from {0}. The peer is rejecting the certificate chain as being untrusted or incomplete.

Cause: The peer is not configured to trust the CA that signed the certificate chain.

Action: Review the certificate chain and the peer trusted CA configuration to determine whether the peer should be trusting the certificate chain or whether a new certificate chain is required that is trusted by the peer.
Level: 1

Type: WARNING

Impact: Security

BEA-090488: PROTOCOL_VERSION alert received from {0}. Check that the peer supports the same level of the SSL/TLS protocol being used (SSL V3.0 and TLS V1.0).

Cause: The peer may not support the same level of the SSL/TLS protocol, or there was some sort of data corruption occurring with the low-level SSL records.

Action: The peer needs to be checked to determine whether it supports SSL V3.0 and TLS V1.0. If it does, SSL debug tracing may be required to see if the SSL record was rejected for another reason.
Level: 1

Type: WARNING

Impact: Security

BEA-090489: NO_RENEGOTIATION alert was received from {0}. The peer does not support renegotiation.

Cause: The peer does not support renegotiation and is responding to a renegotiation request with a warning to indicate it is not supported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090490: ACCESS_DENIED alert received from {0}. The peer recognizes the certificate chain but a higher-level access control is rejecting it.

Cause: The peer is likely doing an authorization check, perhaps above the SSL layer and is rejecting the connection because of an authorization check failure.

Action: Check the peer configuration to determine why the authorization check is failing.
Level: 1

Type: WARNING

Impact: Security

BEA-090491: INSUFFICIENT_SECURITY alert received from {0}. The peer requires stronger ciphers to be supported.

Cause: The peer requires stronger ciphers than those specified in the SSL configuration of the server.

Action: Determine the ciphers required by the peer and update the SSL configuration. This update may not be possible if the required ciphers are stronger than allowed by the WebLogic Server license.
Level: 1

Type: WARNING

Impact: Security

BEA-090492: UNEXPECTED_MESSAGE alert received from {0}.

Cause: This message indicates a problem in the SSL implementations or data corruption.

Action: Enable SSL debug tracing on both sides of the SSL connection. Also, check the network for possible problems.
Level: 1

Type: WARNING

Impact: Security

BEA-090493: BAD_RECORD_MAC alert received from {0}. The peer indicated it received a record with an invalid MAC.

Cause: The certificate does not match the private key or data corruption has occurred.

Action: Check the SSL configuration to ensure the certificate and private key match, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090494: DECRYPTION_FAILED alert received from {0}. The peer detected errors when decrypting.

Cause: A cryptography error or a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090495: RECORD_OVERFLOW alert received from {0}. The peer received an invalid record with a length greater than allowed.

Cause: A problem in the SSL implementation or a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090496: DECOMPRESSION_FAILURE alert received from {0}. The peer was unable to decompress data.

Cause: WebLogic Server does not support data compression. This message likely indicates a data corruption problem.

Action: Check both sides of the SSL connection for any relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090497: HANDSHAKE_FAILURE alert received from {0}. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.

Cause: There is a mismatch in the SSL configurations.

Action: Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings. SSL Debug tracing may be needed on both sides to determine the exact cause.
Level: 1

Type: WARNING

Impact: Security

BEA-090498: ILLEGAL_PARAMETER alert received from {0}.

Cause: This message is most likely caused by a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090499: DECODE_ERROR alert received from {0}.

Cause: This message is most likely caused by a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090500: DECRYPT_ERROR alert received from {0}. A decryption error occurred during the SSL handshake.

Cause: This message is most likely caused by a data corruption error.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090501: EXPORT_RESTRICTION alert received from {0}.

Cause: This message could be caused by an SSL configuration mismatch between the implementations.

Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1

Type: WARNING

Impact: Security

BEA-090502: INTERNAL_ERROR alert received from {0}. Check for unrelated failures such as insufficient resources.

Cause: There may be failures because of an insufficient resource (memory, file descriptors, or other resource).

Action: Check both sides of the SSL connection for relevant error information.
Level: 1

Type: WARNING

Impact: Security

BEA-090503: The public key from the configured server certificate and the configured server private key do not match.

Cause: The server SSL configuration is incorrect. Either the certificate, the private key, or both are incorrectly specified.

Action: Check the SSL configuration. Check that the server certificate corresponds to the server private key.
Level: 1

Type: WARNING

Impact: Security

BEA-090504: Certificate chain received from {0} failed hostname verification check. Certificate contained {1} but check expected {2}

Cause: A peer presented a certificate chain to the server that did not pass the hostname verification check.

Action: Check that the hostname in the peer certificate matches the hostname expected by the hostname verifier.
Level: 1

Type: WARNING

Impact: Security

BEA-090505: No certificate chain was received from {0}, hostname verification check failed.

Cause: The peer is most likely not configured to support a cipher that presents a certificate.

Action: Check the supported ciphers on the peer and ensure that it supports a cipher that provides a certificate.
Level: 1

Type: WARNING

Impact: Security

BEA-090506: Unspecified exception occurred handling hostname verification for {0}.

Cause: The hostname verifier failed.

Action: Enable SSL debug tracing to determine the exact exception. If this is a custom hostname verifier, there may be coding problems in the implementation.
Level: 1

Type: WARNING

Impact: Security

BEA-090508: Certificate chain received from {0} was incomplete.

Cause: A peer presented a certificate chain to the server that was incomplete (it did not contain a trusted CA).

Action: Check the peer certificate chain to determine if it should be trusted or not. If it should be trusted, then update the server trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090509: The SSL ListenPort attribute {0} cannot be the same as the non-secure ListenPort for the server.

Cause: The same value was specified for the server Listen port and the SSL Listen port.

Action: Correct the configuration of the SSL Listen port. The value must be different that than the server Listen port.
Level: 1

Type: ERROR

Impact: Security

BEA-090510: Error: username not specified.

Cause: The username supplied in the NameCallback is null.

Action: Set a username when a NameCallback is passed to the CallbackHandler.
Level: 1

Type: ERROR

Impact: Security

BEA-090511: The following exception has occurred:

Cause: An error condition has occurred.

Action: Read the associated exception in the log or in the application to determine the problem. In general, the stack trace can be used to debug an existing problem.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090513: ServerIdentity failed validation, downgrading to anonymous.

Cause: Trust has not been properly established between two domains. If the domains are not configured properly, a hacker could make an attempt to guess the server identity for this domain.

Action: See the documentation on "Enabling Trust Between WebLogic Domains" at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090514: The server certificate chain has settings that might cause it to be rejected by peers during SSL handshaking. No action is required unless peers are rejecting the certificate chain.

Cause: The server certificate chain has CA certificates that have BasicConstraints settings which are either missing or set in such a way that a peer may reject it during SSL handshaking.

Action: No action is necessarily required. If peers have trouble handshaking, check that the BasicConstraints settings in the CA certificates in the chain are specified correctly.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090515: The certificate chain could not be completely checked for issues that could cause it to be rejected by a peer during SSL handshaking. No action is required unless peers are rejecting the certificate chain.

Cause: The configured certificate chain was incomplete.

Action: No action is necessarily required. If the entire certificate chain is to be checked, ensure that the entire certificate chain is specified in the configuration.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090516: The {0} provider has pre-existing LDAP data.

Cause: The provider was initialized during a previous boot of the WebLogic Server instance.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090518: Could not decrypt the {1} attribute value of {2} from the file {0}. If an encrypted attribute was copied from boot.properties from another domain into {0}, change the encrypted attribute to its clear text value, and then restart the server. The attribute will be encrypted again. Otherwise, change all encrypted attributes to their clear text values, then restart the server. All encryptable attributes will be encrypted again. The decryption failed with the exception {3}.

Cause: An invalid encrypted value was found in boot.properties.

Action: If an encrypted attribute was copied from boot.properties from another domain into {0}, change the encrypted attribute to its clear text value, and then restart the server. The attribute will be encrypted again. Otherwise, change all encrypted attributes to their clear text values, then restart the server. All encryptable attributes will be encrypted again.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090519: The realm {0} is not properly configured. Follow the directions in subsequent errors to correctly configure the realm.

Cause: See the subsequent errors.

Action: Follow the directions in the subsequent errors to correctly configure the realm.
Level: 1

Type: WARNING

Impact: Security

BEA-090520: The realm {0} does not have an authenticator configured. To correct the problem, configure an authenticator.

Cause: The realm {0} does not have an authenticator configured.

Action: To correct the problem, configure an authenticator.
Level: 1

Type: WARNING

Impact: Security

BEA-090521: The realm {0} does not have a role mapper configured. To correct the problem, configure a role mapper.

Cause: The realm {0} does not have a role mapper configured.

Action: To correct the problem, configure a role mapper.
Level: 1

Type: WARNING

Impact: Security

BEA-090522: The realm {0} does not have a deployable role mapper configured. To correct the problem, configure a deployable role mapper.

Cause: The realm {0} does not have a deployable role mapper configured.

Action: To correct the problem, configure a deployable role mapper.
Level: 1

Type: WARNING

Impact: Security

BEA-090523: None of the deployable role mappers in realm {0} have deployments enabled. To correct the problem, enable deployments in one of the deployable role mappers.

Cause: None of the deployable role mappers in realm {0} have deployments enabled.

Action: To correct the problem, enable deployments in one of the deployable role mappers.
Level: 1

Type: WARNING

Impact: Security

BEA-090524: The realm {0} does not have an authorizer configured. To correct the problem, configure an authorizer.

Cause: The realm {0} does not have an authorizer configured.

Action: To correct the problem, configure an authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090525: The realm {0} does not have a deployable authorizer configured. To correct the problem, configure a deployable authorizer.

Cause: The realm {0} does not have a deployable authorizer configured.

Action: To correct the problem, configure a deployable authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090526: None of the deployable authorizers in realm {0} have deployments enabled. To correct the problem, enable deployments in one of the deployable authorizers.

Cause: None of the deployable authorizers in realm {0} have deployments enabled.

Action: To correct the problem, enable deployments in one of the deployable authorizers.
Level: 1

Type: WARNING

Impact: Security

BEA-090527: The realm {0} does not have a credential mapper configured. To correct the problem, configure a credential mapper.

Cause: The realm {0} does not have a credential mapper configured.

Action: To correct the problem, configure a credential mapper.
Level: 1

Type: WARNING

Impact: Security

BEA-090530: The realm {0} has more than one identity asserter configured with the token type {1} selected as an active type. To correct the problem, decide which of the identity asserters should handle this token type. Set it as an active type in that identity asserter, and unset it as an active type for all the other identity asserters.

Cause: The realm {0} has more than one identity asserter configured with the token type {1} selected as an active type.

Action: To correct the problem, decide which of the identity asserters should handle this token type. Set it as an active type in that identity asserter, and unset it as an active type for all the other identity asserters.
Level: 1

Type: WARNING

Impact: Security

BEA-090531: The realm {0} has multiple authorizers but no adjudicator. To correct the problem, configure an adjudicator.

Cause: The realm {0} has multiple authorizers but no adjudicator.

Action: To correct the problem, configure an adjudicator.
Level: 1

Type: WARNING

Impact: Security

BEA-090532: The realm {0} has a realm adapter adjudicator but no realm adapter authorizer. To correct the problem, configure a realm adapter authorizer.

Cause: The realm {0} has a realm adapter adjudicator but no realm adapter authorizer.

Action: To correct the problem, configure a realm adapter authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090533: The realm {0} has a realm adapter adjudicator but no default authorizer. To correct the problem, configure a default authorizer.

Cause: The realm {0} has a realm adapter adjudicator but no default authorizer.

Action: To correct the problem, configure a default authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090534: The realm {0} has a realm adapter adjudicator but multiple default authorizers. To correct the problem, remove all the default authorizers except one.

Cause: The realm {0} has a realm adapter adjudicator but multiple default authorizers.

Action: To correct the problem, remove all the default authorizers except one.
Level: 1

Type: WARNING

Impact: Security

BEA-090535: The realm {0} has a realm adapter adjudicator but is using an authorizer that is neither a realm adapter authorizer nor a default authorizer. To correct the problem, remove all authorizers except the realm adapter authorizer and the default authorizer.

Cause: The realm {0} has a realm adapter adjudicator but is using an authorizer that is neither a realm adapter authorizer nor a default authorizer.

Action: To correct the problem, remove all authorizers except the realm adapter authorizer and the default authorizer.
Level: 1

Type: WARNING

Impact: Security

BEA-090536: The realm {0} has multiple realm adapter authorizers. To correct the problem, remove all the realm adapter authorizers except one.

Cause: The realm {0} has multiple realm adapter authorizers.

Action: To correct the problem, remove all the realm adapter authorizers except one.
Level: 1

Type: WARNING

Impact: Security

BEA-090537: The realm {0} has multiple realm adapter authenticators. To correct the problem, remove all the realm adapter authenticators except one.

Cause: The realm {0} has multiple realm adapter authenticators.

Action: To correct the problem, remove all the realm adapter authenticators except one.
Level: 1

Type: WARNING

Impact: Security

BEA-090538: The realm {0} has a realm adapter authorizer but no realm adapter authenticator. To correct the problem, configure a realm adapter authenticator.

Cause: The realm {0} has a realm adapter authorizer but no realm adapter authenticator.

Action: To correct the problem, configure a realm adapter authenticator.
Level: 1

Type: WARNING

Impact: Security

BEA-090539: The realm {0} has keystore configured that is not a default keystore. To correct the problem, remove the non-default keystore.

Cause: The realm {0} has keystore configured that is not a default keystore.

Action: To correct the problem, remove the non-default keystore.
Level: 1

Type: WARNING

Impact: Security

BEA-090540: The realm {0} has more than one default keystore configured for trusted CAs. To correct the problem, ensure that only one default keystore provider has its root CA keystore location configured.

Cause: The realm {0} has more than one default keystore configured for trusted CAs.

Action: To correct the problem, ensure that only one default keystore provider has its root CA keystore location configured.
Level: 1

Type: WARNING

Impact: Security

BEA-090541: The realm {0} has more than one default keystore configured for private keys. To correct the problem, ensure that only one default keystore provider has its private key keystore location configured.

Cause: The realm {0} has more than one default keystore configured for private keys.

Action: To correct the problem, ensure that only one default keystore provider has its private key keystore location configured.
Level: 1

Type: WARNING

Impact: Security

BEA-090542: Certificate chain received from {0} was not trusted, causing SSL handshake failure. Check the certificate chain to determine whethr or not it should be trusted. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WebLogic Server instance that is using demo certificates (the default WebLogic Server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.

Cause: A peer presented a certificate chain to the server which the server does not trust.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
Level: 1

Type: WARNING

Impact: Security

BEA-090543: Certificate chain received from {0} was incomplete. Check the peer certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.

Cause: A peer presented a certificate chain to the server that was incomplete (it did not contain a trusted CA).

Action: Check the peer certificate chain to determine whether or not it should be trusted. If it should be trusted, then update the client trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain. If you are connecting to a WebLogic Server instance that is using demo certificates (the default WebLogic Server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
Level: 1

Type: WARNING

Impact: Security

BEA-090544: No search filter was supplied.

Cause: The search filter was empty or not supplied.

Action: Supply a search filter when exporting data.
Level: 1

Type: ERROR

Impact: Security

BEA-090545: DefaultRoleMapperImpl search failed: {0}.

Cause: An exception occurred when trying to access the data store.

Action: Look at the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090546: The server is configured to use custom identity and command line trust, but either demo trust or no trust was specified on the command line or in boot.properties.

Cause: The server's KeyStore value in config.xml is CustomIdentityAndCommandLineTrust, but, on the command line to boot the server or in boot.properties, either no trust or DemoTrust was specified.

Action: To correct the problem, either specify -Dweblogic.security.TrustKeyStore=JavaStandardTrust or -Dweblogic.security.TrustKeyStore=CustomTrust and -Dweblogic.security.CustomTrustKeyStoreFileName on the command line when booting the server (or specify TrustKeyStore=JavaStandardTrust or TrustKeyStore=CustomTrust and CustomTrustKeyStoreFileName in boot.properties).
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090547: The certificate chain received from {0} contained a V3 CA certificate which had basic constraints that were not marked critical. This is being rejected due to the strict enforcement of basic constraints.

Cause: Strict basic constraints checking was explicitly enabled, and a certificate chain received by the peer contained a CA that failed due to the strict check but would have passed the strong check.

Action: If strict compliance of RFC 2459 for basic constraints is really required, then the peer certificate chain was correctly rejected and needs to be corrected. If strict compliance is not really required, consider setting the constraints checking back to the default value of strong to accept the certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090548: The certificate chain received from {0} contained a V3 CA certificate that was missing the basic constraints extension

Cause: The certificate chain received by the peer contained a V3 CA certificate that does not contain a basic constraints extension indicating that it really is a CA. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which CA was missing the basic constraints extension. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090549: The certificate chain received from {0} contained a V3 CA certificate that did not indicate it really is a CA.

Cause: The certificate chain received by the peer contained a V3 CA certificate that contained a basic constraints extension which was not marked as being a CA. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which CA is not correct. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090550: The certificate chain received from {0} contained a V3 CA certificate that indicated a certificate chain path length in the basic constraints that was exceeded.

Cause: The certificate chain received by the peer contained a V3 CA certificate that specified a path length in the basic constraints that was exceeded. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which CA indicated the path length limit that was exceeded. The path length, if specified, limits how many CA certificates are allowed to follow a CA certificate in a certificate chain. A path length of 0 indicates only an end entity certificate may follow it in the chain, positive values indicate how many CA certificates may be in the chain between that CA and the end entity certificate. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090551: The certificate chain received from {0} contained a V3 CA certificate that could not be converted to be checked for basic constraints.

Cause: The certificate chain received by the peer contained a V3 CA certificate that could not be converted to a format which allows the basic constraints to be checked. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to confirm they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact Oracle support. If the certificate can not be processed, you can disable the basic constraints checking as a workaround to allow the certificate chain to be accepted and allows this vulnerability to be exploited
Level: 1

Type: WARNING

Impact: Security

BEA-090552: The public and private key could not be checked for consistency.

Cause: The failure could be due to a keystore being used to hold the private key that does not allow access to private key material. Hardware keystores generally do not give access to the private key material that is needed to perform this operation.

Action: If a keystore is being used the warning should be ignored. If handshaking errors occurs with all clients, check that the private key and public key match.
Level: 1

Type: WARNING

Impact: Security

BEA-090554: Set the RealmClassName attribute of the BasicRealm {0} used by the CachingRealm to a valid value.

Cause: The RealmClassName attribute was not properly configured.

Action: Verify that the class is specified correctly and is present in the classpath. Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090560: Could not load the {0} class named {1}. The exception was {3}. The class was specified via the {2} system property value.

Cause: Could not load the {0} class named {1}.

Action: Ensure that the {2} system property is set to the proper {0} class. Also ensure that the class is in the classpath.
Level: 1

Type: ERROR

Impact: Security

BEA-090561: Could not instantiate a {0} of class {1}. The exception received is {3}. The class was specified via the {2} system property value.

Cause: Could not instantiate a {0} of class {1}.

Action: Ensure that the {2} system property is set to the proper {0} class. Also ensure that the class is a correct {0} implementation.
Level: 1

Type: ERROR

Impact: Security

BEA-090562: Could not create a {0} of class {1} because it is not assignable as a {2}. The class was specified via the {3} system property value.

Cause: Could not create a {0} of class {1} because it is not assignable as a {2}.

Action: Ensure that the {3} system property is set to the proper {0} class. Also ensure that the class is a correct {0} implementation.
Level: 1

Type: ERROR

Impact: Security

BEA-090563: Cannot create instance of Hostname Verifier {0}.

Cause: The class {0} was not found, does not have a public constructor without arguments, or has thrown an exception in its constructor.

Action: Ensure that the {0} class is in the class path, and has a public constructor without arguments.
Level: 1

Type: ERROR

Impact: Security

BEA-090564: Specified HostnameVerifier class {0} is invalid. It does not implement weblogic.security.SSL.HostnameVerifier interface.

Cause: An invalid HostnameVerifier class specified.

Action: Specify a different HostnameVerifier class, or ensure that the {0} class implements weblogic.security.SSL.HostnameVerifier interface.
Level: 1

Type: ERROR

Impact: Security

BEA-090565: The server SSL identity key algorithm {0} is not supported.

Cause: The server SSL identity key algorithm {0} is not supported.

Action: Configure the server identity with a different key pair using a supported RSA algorithm.
Level: 1

Type: WARNING

Impact: Security

BEA-090566: The certificate chain received from {0} contained a V3 certificate with unrecognized critical extension: {1}.

Cause: The certificate cannot be validated because it contains an unrecognized critical extension.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090567: The certificate chain received from {0} contained a V3 certificate for which key usage constraints forbid its key use by the key agreement algorithm.

Cause: Certificate key usage constraints forbid certificate key use in a quality required by the key agreement algorithm.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090568: Cannot check key usage constraints of certificate received from {0} because of the failure to determine the key agreement algorithm.

Cause: A NoSuchAlgorithmException occurred while trying to obtain the key agreement algorithm.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090569: The certificate chain received from {0} contained a V3 CA certificate for which key usage constraints indicate its key cannot be used to sign certificates.

Cause: One of certificate in the check cannot pass validation check because its key is used to sign another certificate while key usage constraints indicate that it cannot be used for that.

Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090571: Successfully loaded the JACC Policy object using {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090572: The javax.security.jacc.policy.provider property points to a non-existant {0} class.

Cause: JACC has been enabled by setting the javax.security.jacc.policy.provider property but the class it points to cannot be found.

Action: Ensure that the class is present or change javax.security.jacc.policy.provider property to point to an existing class.
Level: 1

Type: ERROR

Impact: Security

BEA-090573: {1} exception occurred while attempting to access {0}.

Cause: The class was not accessible.

Action: Check to make sure that the class is accessible.
Level: 1

Type: ERROR

Impact: Security

BEA-090574: {1} exception occurred while attempting to instantiate {0}.

Cause: The class was could not be instantiated.

Action: Check to make sure that the class is instantiatable.
Level: 1

Type: ERROR

Impact: Security

BEA-090575: The {0} class is not an instance of java.security.Policy.

Cause: An non-Policy object was passed as the value of the javax.security.jacc.policy.provider property.

Action: Change javax.security.jacc.policy.provider to point to an instance of a java.security.Policy object.
Level: 1

Type: ERROR

Impact: Security

BEA-090576: A PolicyConfigurationFactory could not be obtained successfully.

Cause: The javax.security.jacc.PolicyConfigurationFactory.provider property may not be set to a valid implementation of PolicyConfigurationFactory.

Action: Change javax.security.jacc.PolicyConfigurationFactory.provider to point to an instance of a javax.security.jacc.PolicyConfigurationFactory object.
Level: 1

Type: ERROR

Impact: Security

BEA-090577: Successfully obtained a {0} PolicyConfigurationFactory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090578: The JACC provider returned a {0}.

Cause: JACC returned a PolicyContextException.

Action: Look at the details of the PolicyContextException to determine the action to take.
Level: 1

Type: ERROR

Impact: Security

BEA-090579: The javax.security.jacc.PolicyConfigurationFactory.provider property points to a non-existant class {0}.

Cause: JACC has been enabled by setting javax.security.jacc.PolicyConfigurationFactory.provider property but the class it points to cannot be found.

Action: Ensure that the class is present or change javax.security.jacc.PolicyConfigurationFactory.provider property to point to an existing class.
Level: 1

Type: ERROR

Impact: Security

BEA-090580: The CertPathBuilderParameters constructor was passed an illegal realm name.

Cause: The realm name must not be empty or null.

Action: Pass a valid security realm name to the CertPathBuilderParameters constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090581: The CertPathBuilderParameters constructor was passed an illegal CertPathSelector.

Cause: The CertPathSelector must not be null.

Action: Pass a valid CertPathSelector to the CertPathBuilderParameters constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090582: The CertPathValidatorParameters constructor was passed an illegal realm name.

Cause: The realm name must not be empty or null.

Action: Pass a valid security realm name to the CertPathValidatorParameters constructor.
Level: 1

Type: ERROR

Impact: Security

BEA-090589: The WLSJDKCertPathBuilder was passed an illegal CertPathParameters.

Cause: The CertPathParameters must be a weblogic.security.pk.CertPathBuilderParameters.

Action: Pass a weblogic.security.pk.CertPathBuilderParameters as the CertPathParameters.
Level: 1

Type: ERROR

Impact: Security

BEA-090590: The WLSJDKCertPathValidator was passed an illegal CertPathParameters.

Cause: The CertPathParameters must be a weblogic.security.pk.CertPathValidatorParameters.

Action: Pass a weblogic.security.pk.CertPathValidatorParameters as the CertPathParameters.
Level: 1

Type: ERROR

Impact: Security

BEA-090591: The realm {0} does not have any Certification Path providers configured. To correct the problem, configure at least one Certification Path provider.

Cause: The realm {0} does not have any Certification Path providers configured.

Action: To correct the problem, configure at least one Certification Path provider.
Level: 1

Type: WARNING

Impact: Security

BEA-090592: The realm {0} does not have a Certification Path builder configured. To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.

Cause: The realm {0} does not have a Certification Path builder configured.

Action: To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
Level: 1

Type: WARNING

Impact: Security

BEA-090593: The realm {0} has an illegal Certification Path builder configured. To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.

Cause: The realm {0} has an illegal Certification Path builder configured.

Action: To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
Level: 1

Type: WARNING

Impact: Security

BEA-090598: Unable to update the domain controller list

Cause: The most likely cause is that the attempt to lock the domain controller list for update timed out. This may happen if there are concurrent updates occurring to the configuration for the same provider instance, and the updates are taking a while to execute (perhaps a long domain controller list or slow network).

Action: If this is an update from the Administration Console, and the domain controller list was modified, apply the changes again.
Level: 1

Type: WARNING

Impact: Security

BEA-090599: Unable to initialize the domain controller list

Cause: The domain controller list was not able to be locked for initialization. This should not occur and was likely caused by an internal coding error.

Action: This indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090600: Failed to retrieve the local machine name.

Cause: There may be a configuration error with either the user account rights required or the local NT machine.

Action: Verify that the user running the server has the specific NT account rights that are required to use the NT authentication provider.
Level: 1

Type: ERROR

Impact: Security

BEA-090601: Cannot access domain controller {0}.

Cause: The domain controller name may not be valid, may be down or unavailable on the network, or the user may not have permission to access it.

Action: If the domain controller is simply down, or temporarily unavailable, it may be retried later on depending on the domain controller retry settings. If the domain controller is available, check that the user account running the server has permission to access the domain controller. This may require logging into the domain controller that failed and verifying the user has been granted access.
Level: 1

Type: WARNING

Impact: Security

BEA-090602: The java and native library versions do not match for the WindowsNTAuthenticator.

Cause: The native library being found and loaded is not in synch with the java portion of the provider.

Action: Verify the correct native library for the WindowsNTAuthenticator is in the PATH and that the correct PATH is being used.
Level: 1

Type: ERROR

Impact: Security

BEA-090615: A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.

Cause: A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.

Action: Ensure that the list of trusted CAs passed in does not include a null trusted CA.
Level: 1

Type: ERROR

Impact: Security

BEA-090623: Failed to get the default trusted CAs for this server.

Cause: This exception is returned when an exception occurs when finding this server's trusted CAs.

Action: Look at the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090625: Policy context {0} not in open state.

Cause: Policy context must be in open state.

Action: Ensure that the policy context is open before attempting an operation on it that requires an open Policy Context. This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090626: Received a {0} when attempting to delete Policy Directory {1}.

Cause: Received a {0} when attempting to delete Policy Directory {1}.

Action: Ensure that files in the policy directory are not open.
Level: 1

Type: ERROR

Impact: Security

BEA-090627: Cannot link a PolicyConfiguration to itself.

Cause: Cannot link a PolicyConfiguration to itself.

Action: This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090628: Cannot have circular policy configuration links.

Cause: A PolicyConfiguration is linked to another PolicyConfiguration which ultimately is linked back to the original PolicyConfiguration. This means that no PolicyConfiguration actually holds the role to principal mapping.

Action: This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090629: Received a {0} when attempting to use the passed role to principal map for PolicyConfiguration with a ContextID of {1}.

Cause: Received a {0} when attempting to use the passed role to principal map for PolicyConfiguration with a ContextID of {1}. The code attempts to do some simple validation the map.

Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090631: Unable to create the PolicyWriter directory {0}.

Cause: Unable to create the PolicyWriter directory {0}.

Action: Unable to create the PolicyWriter directory.
Level: 1

Type: ERROR

Impact: Security

BEA-090632: Cannot create {0}. Non directory file already exists with the same name. Please remove it.

Cause: A non directory file already exists with the same name.

Action: Remove the non directory file.
Level: 1

Type: ERROR

Impact: Security

BEA-090633: Cannot open policy file {0}. Received exception {1}.

Cause: If the exception is a FileNotFoundException, the file path name may be too long for the operating system, or the directory may have been deleted before the policy file was written to it.

Action: Try to shorten the file path name if it is too long for the operating system. The error may also occur if the directory has been deleted before the file was written to it.
Level: 1

Type: ERROR

Impact: Security

BEA-090634: Cannot write to policy file {0}. Received exception {1}.

Cause: The file may have been opened for exclusive access by something other than WebLogic Server.

Action: Ensure that the policy file is writable.
Level: 1

Type: ERROR

Impact: Security

BEA-090635: No results

Cause: There are no policies that match the search criteria.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090636: No results

Cause: There are no roles that match the search criteria.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090637: No role name was supplied.

Cause: The role name is null or contains no data.

Action: Specify a valid role name.
Level: 1

Type: ERROR

Impact: Security

BEA-090638: No resource data

Cause: The resource data parameter was not supplied or is empty.

Action: Specify valid resource data.
Level: 1

Type: ERROR

Impact: Security

BEA-090639: No resource type

Cause: The resource type information was not supplied.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-090640: No resource identifier

Cause: The resource identifier parameter was not supplied or is empty.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090641: No resource keys were found.

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090642: Invalid data type for {0} resource key value

Cause: The data type of a resource key value is not valid.

Action: Specify a valid resource key data type value.
Level: 1

Type: ERROR

Impact: Security

BEA-090643: Invalid resource type: "{0}"

Cause: An invalid or unknown resource type was supplied.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-090644: Expected resource type: {0}

Cause: An invalid or unknown resource type was supplied.

Action: Verify that a valid resource type was supplied and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090645: Expected resource key: {0}

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090646: Unknown resource key: {0}

Cause: The resource key supplied in the resource data is unknown.

Action: Specify only resource keys valid for a specific resource type.
Level: 1

Type: ERROR

Impact: Security

BEA-090647: Invalid application name

Cause: The application name parameter was empty or contains invalid values.

Action: Specify a valid application name.
Level: 1

Type: ERROR

Impact: Security

BEA-090648: Invalid component name

Cause: The component name parameter was empty or contains invalid values.

Action: Specify a valid component name.
Level: 1

Type: ERROR

Impact: Security

BEA-090649: Illegal application search name

Cause: The application name was not a legal search string.

Action: Specify a valid application name search string.
Level: 1

Type: ERROR

Impact: Security

BEA-090650: Illegal component search name

Cause: The component name was not a legal search string.

Action: Specify a valid component name search string.
Level: 1

Type: ERROR

Impact: Security

BEA-090651: No component type

Cause: The component type parameter is empty.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

BEA-090652: Invalid component type: "{0}"

Cause: The specified component type parameter is not valid.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

BEA-090653: Empty array value found

Cause: An empty string was supplied for an array element of the resource key.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

BEA-090654: Unexpected resource identifier data: "{0}"

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090655: Unexpected resource key array value: "{0}"

Cause: An invalid resource identifier was supplied.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

BEA-090658: Unable to convert file {0} to URL. Got exception {1}.

Cause: File {0} could not be converted to a URL.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090660: Certificate chain received from {0} was not validated by the custom trust manager {1} causing SSL handshake failure.

Cause: A peer presented a certificate chain to the server that the custom trust manager did not validate.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the peer certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090661: Certificate chain received from {0} was not validated by the custom trust manager {1} causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the certificate chain.

Cause: A peer presented a certificate chain to the server that the custom trust manager did not validate.

Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the certificate chain.
Level: 1

Type: WARNING

Impact: Security

BEA-090662: The DeployableAuthorizer "{0}" implements the deprecated {1} interface.

Cause: At security provider initialization, a deprecated security interface was detected.

Action: No immediate action is required. However, the security provider should be updated.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090663: The DeployableRoleMapper "{0}" implements the deprecated {1} interface.

Cause: At security provider initialization a deprecated security interface was detected.

Action: No immediate action is required. However, the security provider should be updated.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090666: Deployment handle was not supplied.

Cause: The deployment handle is null.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090667: Application information was not supplied.

Cause: The application information is null.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090668: Ignored deployment of role "{0}" for resource "{1}".

Cause: The application has been configured to ignore security data from deployment descriptors.

Action: Remove role mapping from the application deployment descriptor or change the security configuration to allow deployment of role mappings.
Level: 1

Type: WARNING

Impact: Security

BEA-090669: Ignored deployment of policy for resource "{0}".

Cause: The application has been configured to ignore security data from deployment descriptors.

Action: Remove security policy from the application deployment descriptor or change the security configuration to allow deployment of security policy.
Level: 1

Type: WARNING

Impact: Security

BEA-090670: Unable to verify user name token for user {0}

Cause: The UsernameToken could not be verified.

Action: Verify that the user exists in the WebLogic authentication provider, that the authentication provider has the PasswordDigestEnabled attribute set to true, and that the user entry has set the password since the attribute was set to true.
Level: 1

Type: ERROR

Impact: Security

BEA-090672: Identity assertion object for token type {0} was of type {1} instead of expected type of {2}.

Cause: The token object was not an instance of the correct type.

Action: If called from an application via the identity assertion public API, then modify the application to pass the expected token. If called from the container, then the container should not be passing a token that is not a UsernameToken, and this exception indicates an internal coding error in the server; contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090673: Digest data source {0} was not found. Disabling digest authentication.

Cause: The configured data source does not exist.

Action: Modify the DigestDataSourceName attribute on the WebLogic Identity Assertion provider to be the name of a valid WebLogic data source configured for this domain.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090674: Digest data source {0} was not initialized due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception was thrown when initializing the configured data source.

Action: Verify that the DigestDataSourceName attribute on the WebLogic Identity Assertion provider is valid and a WebLogic data source configured for this domain. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090675: An SQL connection could not be obtained from a digest data source {0} due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception was thrown when obtaining a connection from the configured data source.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090676: The SQL statement {0} could not be prepared due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception occurred when preparing the SQL statement.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090677: The {0} table could not be created due to an exception. Disabling digest authentication. The exception text is {1}.

Cause: An exception occurred when validating or creating the table.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090678: Authentication failed with digest {0} due to an exception that occurred while detecting the replay attack. The exception text is {1}.

Cause: An exception occurred when inserting the digest information row into the database.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090679: Authentication failed due to detection of a replay attack for nonce {0} and digest {1}.

Cause: An entry for this nonce and digest has already been used for authentication in this domain.

Action: Ensure that the client is not performing a replay attack. Investigate the client performing the digest authentication and check that it is using unique nonce, digest, and created values.
Level: 1

Type: ERROR

Impact: Security

BEA-090680: Unable to verify the digest authentication for user {0} since the created time is not within the expiration time period.

Cause: The created timestamp of the digest authentication is not within the expiration time period.

Action: Increase the expiration time for the identity assertion provider or synchronize the system clocks on the client and server machines.
Level: 1

Type: ERROR

Impact: Security

BEA-090681: Digest authentication for user {0} has been disabled due to a previous fatal error in initializing replay detection

Cause: A previous fatal error disabled digest authentication. Therefore, digest authentication for this user has failed.

Action: Look in the log, identity the previous error, and correct the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090682: Problem handling security deployment validation: {0}

Cause: An initialization error or exception from a security provider occurred.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Security

BEA-090700: There is a problem with the class {0} pointed to by the weblogic.security.jacc.RoleMapperFactory.provider property.

Cause: JACC Was enabled by setting weblogic.security.jacc.RoleMapperFactory.provider property but there are problems instantiating the class.

Action: Ensure that the class is present or change weblogic.security.jacc.RoleMapperFactory.provider property to a class that can be instantiated.
Level: 1

Type: ERROR

Impact: Security

BEA-090701: Unable to successfully obtain a RoleMapperFactory.

Cause: The weblogic.security.jacc.RoleMapperFactory.provider property may not be set to a valid implementation of RoleMapperFactory.

Action: Change weblogic.security.jacc.RoleMapperFactory.provider to point to an instance of a weblogic.security.jacc.RoleMapperFactory object.
Level: 1

Type: ERROR

Impact: Security

BEA-090705: The PolicyConfigurationFactory, Policy, RoleMapperFactory class names are not specified or not compatible with each other.

Cause: Incompatible class names have been specified. Generally this is caused by specifying but not specifying all three or by specifying class names that are not designed to work with each other.

Action: Check the documentation and make sure that compatible class names are set for the three system properties.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090707: Successfully obtained a {0} RoleMapperFactory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090709: Inconsistent security configuration.

Cause: The security command line properties are not consistent with each other.

Action: Address the inconsistency and reboot.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090714: The certificate chain from the peer could not be validated. Chain : {0}. Reason : {1}.

Cause: Either the certificate chain from the peer should not be allowed to access the server or the server or one of the configured CertPathProviders is not properly configured to trust the peer.

Action: If the server is not supposed to trust the peer, inform the peer that it should use a different certificate chain. If the server should trust the peer, then either a configured CertPathProvider is improperly configured to not trust the peer, or the server is improperly configured to use the configured CertPathProviders for perform extra validation of SSL peer certificate chains. Check the server SSL configuration and the configured CertPathProvider configurations.
Level: 1

Type: WARNING

Impact: Security

BEA-090716: Failed to retrieve identity key/certificate from keystore {1} under alias {2} on server {0}.

Cause: An incorrect key password was used.

Action: Correct the server SSL configuration.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090717: Invalid server {0} SSL configuration

Cause: The server SSL configuration parameters are inconsistent.

Action: Verify that the SSL and keystore configuration options are consistent.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090718: Security initializing using java security manager.

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090719: Security initializing using JACC for EJB and Servlet authorization.

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090720: The Managed Server could not start because the NodeManager's encryption service data was not found.

Cause: The Managed Server could not start because the NodeManager's NodeManagerProperties file was not found. The NodeManager's encryption service could not be instantiated.

Action: Verify the existence and location of the NodeManager's NodeManagerProperties file.
Level: 1

Type: ERROR

Impact: Security

BEA-090721: The Managed Server could not start because it could not read the NodeManager's encryption service data.

Cause: The Managed Server could not start because it could not read the NodeManager's encryption service data.

Action: Verify the existence and location of the NodeManager's NodeManagerProperties file. Check that the read permissions are correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090724: Challenge identity assertion has not completed, subject is not available yet.

Cause: The method to get the subject was called before the identity assertion completed.

Action: Call the hasChallengeIdentityCompleted method before calling the method to get the subject.
Level: 1

Type: ERROR

Impact: Security

BEA-090725: Challenge identity assertion has completed, challenge token is not available.

Cause: The method to get the challenge token was called after the identity assertion completed.

Action: Call the hasChallengeIdentityCompleted method before calling the method to get the challenge token.
Level: 1

Type: ERROR

Impact: Security

BEA-090764: The ApplicationVersioner "{0}" for application "{1}" returned an error: {2}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090765: Failed to create policies for application version {0}.

Cause: An exception occurred during the application version created method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090766: Failed to create roles for application version {0}.

Cause: An exception occurred during the application version created method.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-090772: The security realm {0} does not support application versioning. Unable to deploy the application {1}.

Cause: The security realm {0} as configured does not support application versioning, and thus the deployment of the application version failed.

Action: Deploy the application using a security realm that supports application versioning.
Level: 1

Type: ERROR

Impact: Security

BEA-090773: Failure in creating security application version information for the application {0}.

Cause: An attempt to create security version information for application {0} failed.

Action: Check the server log for additional security error messages, correct security errors, and try again.
Level: 1

Type: ERROR

Impact: Security

BEA-090774: This method requires an encrypted argument but the argument passed to it was in clear text.

Cause: This method was called with a clear-text argument but requires an encrypted argument.

Action: To call this method programattically, call the non-encrypted set() method on the MBean. This will automatically encrypt the argument.
Level: 1

Type: ERROR

Impact: Security

BEA-090777: Exception when trying to sign a SAML assertion: {0}

Cause: An exception occurred during the signing of a SAML assertion.

Action: Read the exception text from the log message for more information on diagnosing the problem.
Level: 1

Type: WARNING

Impact: Security

BEA-090779: Identity {0} failed validation, downgrading to anonymous.

Cause: Trust has not been properly established between two domains. If the domains are not configured properly, a hacker could make an attempt to guess the server identity for this domain.

Action: See the documentation on "Enabling Trust Between WebLogic Domains" at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1

Type: ERROR

Impact: Security

BEA-090780: The values specified by -Dweblogic.security.URLResourceCaseMapping({0}) and WebAppFilesCaseInsensitive Attribute on SecurityConfiguraitonMBean({1}) do not match.

Cause: The value of the property -Dweblogic.security.URLResourceCaseMapping is different from the value for WebAppFilesCaseInsensitive attribute of the SecurityConfiguraitonMBean.

Action: Correct -Dweblogic.security.URLResourceCaseMapping to start the server.
Level: 1

Type: ERROR

Impact: Security

BEA-090782: Server is running in production mode, and the Native Library (terminalio) to read the password securely from the command line was not found.

Cause: Server could not start because it didn't find the Native Library in the PATH to read the password securely from command line.

Action: Verify that the terminalio library exists in the path. You can set this by setting -Djava.library.path to the directory where this library exists, you can use boot.properties to store the password, or you can use -Dweblogic.management.allowPasswordEcho=true to enter the password in echo mode.
Level: 1

Type: ERROR

Impact: Security

BEA-090783: Server is running in development mode and the Native Library (terminalio) to read the password securely from the command line wes not found.

Cause: Either the server could not start because it did not find the Native Library in the PATH to read the password securely from command line or -Dweblogic.management.allowPasswordEcho=false is set.

Action: Verify that the terminalio library exists in the path. You can set this by setting -Djava.library.path to the directory where this library exists, you can use boot.properties to store the password, or you can use -Dweblogic.management.allowPasswordEcho=true to enter the password in echo mode.
Level: 1

Type: ERROR

Impact: Security

BEA-090787: A null data source name was specified.

Cause: A configuration setting that required a data source name was null.

Action: Check configuration settings that require data source names to verify they are correctly specified.
Level: 1

Type: ERROR

Impact: Security

BEA-090788: Problem with data source or connection pool configuration, verify that data source name {0} is correct and pool configurations are correct.

Cause: A configuration setting that required a data source name was likely incorrect, or the pool settings associated with it are incorrect.

Action: Check configuration settings to ensure that the data source name is correct and the associated pool configuration settings are correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090812: Could not create a {0} keystore instance for provider {1}. Exception: {2}

Cause: {0} is not a valid keystore type, or keystore provider {1} was not properly configured.

Action: Verify that the correct keystore type was specified and that the keystore provider is correctly specified in the java.security file.
Level: 1

Type: ERROR

Impact: Security

BEA-090814: Security Service is shutting down the security realm {0}.

Cause: This message is for informational purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090817: These configuration changes cannot be activated because a default realm is not configured for the domain.

Cause: The "DefaultRealm" is not set for the domain's SecurityConfiguration.

Action: To correct the problem, set the "DefaultRealm" for the domain's SecurityConfiguration to one of its realms. If it does not have any realms, create and configure one.
Level: 1

Type: ERROR

Impact: Security

BEA-090818: These configuration changes cannot be activated because the domain does not have a properly configured default realm.

Cause: The "DefaultRealm" is not properly configured for the domain's SecurityConfiguration. See the nested exceptions that accompany this error for details.

Action: To correct the problem, review and address the nested exceptions that accompany this error.
Level: 1

Type: ERROR

Impact: Security

BEA-090819: The JACC property {0} is not set.

Cause: A JACC provider is attempting to initialize but {0} property has not been set.

Action: Set the property and reboot.
Level: 1

Type: ERROR

Impact: Security

BEA-090820: The internal variable {0} is null and it should not be.

Cause: The cause is unknown.

Action: This exception is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Security

BEA-090823: Could not register the WebLogic Server X509CertificateFactory as the default X509CertificateFactory for this JVM.

Cause: The WebLogic Server X509CertificateFactory could not be registered as the default X509CertificateFactory for this JVM.

Action: The WebLogic Server X509CertificateFactory orders the certificates in a CertPath that was created from PKCS7. Specify -Dweblogic.security.RegisterX509CertificateFactory=false on the command line for booting this server to indicate that WebLogic Server should not register the WebLogic Server X509CertificateFactory as the default X509CertificateFactory when the server boots (since your JDK does not support this). Also, since the WebLogic Server X509CertificateFactory cannot be registered with the JDK as the default X509CertificateFactory, the JDK will use its current default X509CertificateFactory. The default one (for example, the SUN implementation) may not properly convert PKCS7 to an ordered CertPath.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090827: LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.

Cause: A WebLogic provider LDIF template file may have been overwritten with an empty file.

Action: If the server boots successfully, no action is needed. If the server does not boot successfully then an attempt should be made to recover non-empty LDIFT template file from the WebLogic Server kit.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090838: The required WebLogic JACC RoleMapperFactory was not specified. Please specify the factory class using the weblogic.security.jacc.RoleMapperFactory.provider system property.

Cause: A WebLogic JACC RoleMapperFactory class is required.

Action: Check the documentation and ensure that the WebLogic JACC RoleMapperFactory system property is set properly.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090839: Unexpected exception while registering SAML {0} service in application context {1}.

Cause: This is an internal server error.

Action: Check server status.
Level: 1

Type: ERROR

Impact: Security

BEA-090840: Registered SAML service {0} at URI {1} in application context {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090846: {0} provider initialization failed: Invalid {1} attribute "{2}".

Cause: This was caused by an incorrect provider configuration.

Action: Check and update the indicated provider attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090847: {0} provider initialization failed: Missing {1} attribute.

Cause: This was caused by an invalid provider configuration.

Action: Check and update the indicated provider attribute.
Level: 1

Type: ERROR

Impact: Security

BEA-090859: The realm {0} does not have a certification path validator configured. To correct the problem, configure a cert path provider that supports cert path validation.

Cause: The realm {0} does not have a certification path validator configured.

Action: To correct the problem, configure a certification path provider that supports certification path validation.
Level: 1

Type: WARNING

Impact: Security

BEA-090861: Certificate policies extension processing failed. PolicyId: {0} does not exist in the allowed list.

Cause: Certificate policies extension processing failed. PolicyId: {0} does not exist in the allowed list.

Action: Add the Policyid to the Allowed Policyids list.
Level: 1

Type: ERROR

Impact: Security

BEA-090862: Certificate policies extension processing failed. PolicyQualifierID: {0} is not CPS.

Cause: Certificate policies extension processing failed. PolicyQualifierID: {0} is not CPS.

Action: Check the Certificate Presented, as certificates containing a PolicyQualifierID other than CPS are not supported.
Level: 1

Type: ERROR

Impact: Security

BEA-090865: The realm {0} is not configured to handle MBean authorization. To correct the problem, configure an authorization provider that supports MBean authorization.

Cause: The realm {0} is not configured to handle MBean authorization.

Action: To correct the problem, configure an authorization provider that supports MBean authorization.
Level: 1

Type: WARNING

Impact: Security

BEA-090866: The deployment of an unchecked policy for the resource "{0}" has been ignored. Unchecked policy is the default policy for URL and EJB resources. An unchecked policy can result if a deployment descriptor specifies a transport guarantee without the use of an authorization constraint.

Cause: The application has been configured to ignore security data from deployment descriptors.

Action: When the deployment descriptor specifies a transport guarantee without the use of an authorization constraint, no action is needed. Otherwise, remove the security policy from the application deployment descriptor or change the security configuration to allow deployment of security policy.
Level: 1

Type: WARNING

Impact: Security

BEA-090868: The realm {0} has an invalid SAML configuration. To correct the problem, ensure that there is only one of each SAML provider type and that the version of the SAML providers are the same.

Cause: The realm {0} has an invalid set of SAML providers.

Action: To correct the problem, ensure that there is only one of each SAML provider type and that the version of the SAML providers are the same.
Level: 1

Type: WARNING

Impact: Security

BEA-090869: The PolicyConsumer "{0}" returned an error: {1}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090870: The realm "{0}" failed to be loaded: {1}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090871: The RoleConsumer "{0}" returned an error: {1}.

Cause: There are multiple possible causes.

Action: Carefully read the returned error to determine if any action is required.
Level: 1

Type: ERROR

Impact: Security

BEA-090872: The {0} service can not be found for {1}.

Cause: A null was returned when performing a service lookup.

Action: Check the configuration to determine if the missing service was actually configured.
Level: 1

Type: ERROR

Impact: Security

BEA-090873: Expected a {0} object but did not get one.

Cause: There is a possible configuration problem.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090874: {0} returned a null {1}.

Cause: This should never happen.

Action: Examine the specific objects referenced in the error message to see what may be the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-090875: Null parameter supplied to method {0}.

Cause: A parameter was not correctly specified.

Action: This is most likely a coding error.
Level: 1

Type: ERROR

Impact: Security

BEA-090876: {0} Consumer not configured.

Cause: An attempt was made to reference a Consumer, but none are configured

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090877: Service {0} unavailable, see exception text: {1}

Cause: The exception text should indicate the cause. This is likely a configuration error.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090878: Unknown token type: {0}

Cause: This is likely caused by the token type not being properly configured.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

BEA-090880: Could not load JAAS configuration file for JVM.

Cause: A class similar to com.sun/ibm.security.auth.login.ConfigFile was not located in the classpath.

Action: Ensure that com.sun.security.auth.login.ConfigFile/com.ibm.security.auth.login.ConfigFile is available as part of the classpath or that -Dweblogic.security.authentication.Configuration=class name is passed as a startup system property and is available as part of the classpath.
Level: 1

Type: WARNING

Impact: Security

BEA-090882: SSL has established a session that uses a Null cipher.

Cause: The connecting SSL client presented a ciphersuite list to the server that contains only ciphersuites with null ciphers. This may or may not be a problem, depending on your domain configuration.

Action: Verify that the client's security providers are configured correctly, or disable the use of Null ciphers on the server.
Level: 1

Type: WARNING

Impact: Security

BEA-090883: Resource name is null or empty.

Cause: Resource name should not be null or empty.

Action: Check that the resource name is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-090884: User name is null or empty.

Cause: User name should not be null or empty.

Action: Check that the User name is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-090885: Remote user name is null or empty.

Cause: Remote user name should not be null or empty.

Action: Check that the remote user name is not null or empty.
Level: 1

Type: ERROR

Impact: Security

BEA-090886: List number should not be negative.

Cause: The list number should not be negative.

Action: Check that the list number is not negative.
Level: 1

Type: ERROR

Impact: Security

BEA-090888: The SSL client running within the server does not have a certificate. It will use the server's certificate.

Cause: The SSL client running within the server does not have a certificate, but client certificates are required.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090889: The SSL client running within the server could not obtain the server's certificate.

Cause: An exception occurred when the SSL client running within the server tried to obtain the server's certificate.

Action: Check that the server's SSL configuration is correct, and that the server has a certificate and private key configured.
Level: 1

Type: WARNING

Impact: Security

BEA-090890: The loading of the OPSS java security policy provider class {0} failed due to a problem in creating the OPSS java security policy provider instance {0}. Illegal access to the constructor of the class.

Cause: The loading of the OPSS java security policy provider class {0} failed due to an IllegalAccessException.

Action: Ensure that the correct version of the OPSS java security policy provider {0} is used.
Level: 1

Type: ERROR

Impact: Security

BEA-090891: The loading of the OPSS java security policy provider failed due to a problem in instantiating the OPSS java security policy provider. An InstantiationException was received when creating an instance.

Cause: The loading of the OPSS java security policy provider class {0} failed due to InstantiationExceptions.

Action: Ensure that the correct version of the OPSS java security policy provider {0} is used.
Level: 1

Type: ERROR

Impact: Security

BEA-090892: The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server log file for the root cause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: {1}

Cause: The loading of the OPSS java security policy provider class {0} failed due to an exception: {1}.

Action: Check the stack trace or server log file for the root cause of the exception, check for a possible configuration error, or enable the debug flag -Djava.security.debug=jpspolicy to get more information.
Level: 1

Type: ERROR

Impact: Security

BEA-090893: The loading of the OPSS java security policy provider stopped due to a conflict with the JACC Policy provider. Only one security policy provider can be enabled.

Cause: The loading of the OPSS java security policy provider stopped due to a conflict with the JACC Policy provider. Only one security policy provider can be enabled.

Action: If enabling the OPSS java security policy provider {0}, please do not enable the JACC setting.
Level: 1

Type: ERROR

Impact: Security

BEA-090894: Successfully loaded the OPSS Policy Provider using {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090895: OPSS Java Security Policy Provider {0} has already been loaded statically, programmatical loading has been skipped.

Cause: OPSS Java Security Policy Provider {0} has already been loaded statically, programmatical loading has been skipped.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090896: The SSL ListenPort attribute {0} cannot be the same as the Administration Port for the server.

Cause: The same value was specified for the Administration Port and the SSL Listen port.

Action: Correct the configuration of the SSL Listen port or the Administration port. The SSL Listen port value must be different that than the Administration port.
Level: 1

Type: ERROR

Impact: Security

BEA-090897: A failure occurred while attempting to update XACML global policies for security provider {0}.

Cause: An exception occurred while attempting to update XACML global policies.

Action: Examine the exception and correct the cause.
Level: 1

Type: ERROR

Impact: Security

BEA-090898: Ignoring the trusted CA certificate "{0}". Loading of the trusted certificate list raised a certificate parsing exception {1}.

Cause: It is possible that the CA to be added used a signature algorithm that is not supported by the SSL stack.

Action: The server has a long list of trusted CAs, and the one that caused the exception in the server is ignored.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090899: User attribute name cannot be null.

Cause: The user attribute name is null for the request.

Action: Pass in a user attribute name that is not null.
Level: 1

Type: ERROR

Impact: Security

BEA-090900: User attribute name is not supported for the specified operation.

Cause: The user attribute name is not supported.

Action: Pass in a user attribute name that is supported. Refer to documentation for details.
Level: 1

Type: ERROR

Impact: Security

BEA-090901: Invalid group name: {0}. Cannot contain {1}.

Cause: There was improper usage of {1}.

Action: Never use a group name carrying {1}.
Level: 1

Type: ERROR

Impact: Security

BEA-090902: The certificate chain received from {0} contained a V1 certificate which cannot be a CA.

Cause: The certificate chain received by the peer contained a V1 certificate which cannot be a CA. This was rejected by the basic constraints checking for strong and strict and not allowing V1 certificates as CAs, which protects against a specific certificate chain attack on SSL.

Action: The peer certificate chain needs to be looked at carefully to determine which certificate is not correct. If the certificate chain really is from a valid peer, look at updating the peer certificate chain with valid CA certificates. If this is not possible, disable the basic constraints checking to allow the certificate chain to be accepted and to allow this vulnerability to be exploited.
Level: 1

Type: WARNING

Impact: Security

BEA-090903: The JPS or JRF JAR is present in the classpath, but the jps-config.xml file was not supplied in the command line: the required system property "{0}" has not been defined.

Cause: System parameter "oracle.security.jps.config" is not supplied in the command line, but a JPS or JRF JAR is present in the classpath.

Action: If this is not a JRF domain, remove the JPS or JRF JAR from the classpath; otherwise, and add the system parameter "oracle.security.jps.config" in the command line to supply the path to the jps-config.xml file.
Level: 1

Type: WARNING

Impact: Security

BEA-090904: The JPS or JRF JAR is present in the classpath, but no system property was supplied for "{0}" and "{1}". The server will start without setting the OPSS java policy provider.

Cause: System parameters "oracle.security.jps.config" and "oracle.domain.config.dir" are not supplied in the command line, but jps-internal.jar or jrf.jar is present in the classpath.

Action: If this is not a JRF domain, removed the jps-internal.jar and jrf.jar from the classpath. Otherwise, add the required system parameters for the JRF domain.
Level: 1

Type: WARNING

Impact: Security

BEA-090905: Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -D{0}=true.

Cause: The CryptoJ JCE Provider self-integrity check incurs some performance penalty at server startup.

Action: No action is requirecx.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090906: Changing the default Random Number Generator in RSA CryptoJ from {1} to {2}. To disable this change, specify -D{0}=true.

Cause: CryptoJ's default RNG ECDRBG causes certain cryptographic operations to be slower.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090907: Invalid user name: {0}. Cannot contain {1}.

Cause: There was improper usage of {1}.

Action: Never use a user name carrying {1}.
Level: 1

Type: ERROR

Impact: Security

BEA-090908: Using the default WebLogic SSL Hostname Verifier implementation.

Cause: TBD

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090909: Using the configured custom SSL Hostname Verifier implementation: {0}.

Cause: TBD

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090910: Grant statement has invalid syntax: {0}

Cause: There is an error in the syntax of the grant statement.

Action: Verify that the grant statement syntax is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090911: Permission found in grant statement has invalid syntax: {0}

Cause: There is an error in the syntax of the permission within the grant statement.

Action: Verify that the grant statement permission syntax is correct.
Level: 1

Type: ERROR

Impact: Security

BEA-090912: Attempting to check revocation status for certificate with subject: {0}

Cause: X.509 certificate revocation checking is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090913: Unknown revocation status not causing failure for certificate with subject: {0}

Cause: X.509 certificate revocation checking is enabled, however, certificate revocation status cannot be determined, and is configured not to fail on an unknown status.

Action: If validation failure is required, configure certificate revocation status to fail on an unknown status. To determine why the status is unknown, enable debug logging.
Level: 1

Type: WARNING

Impact: Security

BEA-090914: Certificate revocation status: {0}

Cause: X.509 certificate revocation checking is enabled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090915: Nonce was ignored by the OCSP responder, forcing certificate revocation status to be ignored and considered unknown: {0}.

Cause: X.509 certificate revocation checking is enabled, and OCSP is configured with nonces enabled.

Action: To enable use of the ignored status, configure to disable OCSP nonces.
Level: 1

Type: WARNING

Impact: Security

BEA-090916: Unknown revocation status causing failure for certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, certificate revocation status cannot be determined, and is configured to fail on an unknown status.

Action: If validation failure is not required, configure certificate revocation status to not fail on an unknown status. To determine why the status is unknown, enable debug logging.
Level: 1

Type: WARNING

Impact: Security

BEA-090917: Revoked certificate causing validation failure, certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, and the checked certificate was reported revoked.

Action: Contact the certificate presenter (for example, SSL peer) and request that the revoked certificate be updated.
Level: 1

Type: WARNING

Impact: Security

BEA-090918: Non-revoked certificate with subject: {0}.

Cause: X.509 certificate revocation checking is enabled, and the checked certificate was reported NOT revoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090919: The configured SSL minimum protocol version {0} is invalid or not supported. The minimum has been changed to {1}.

Cause: The current SSL implementation does not support the configured SSL minimum protocol version.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Security

BEA-090920: Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by system property {0}, either explicitly or by default.

Cause: The system property {0} is selecting JSSE either explicitly or by default.

Action: To use Certicom for SSL, set the system property {0} to false.
Level: 1

Type: WARNING

Impact: Security

BEA-090921: JSSE has not been selected by system property {0}, however Certicom SSL is not available, so JSSE is being used for SSL.

Cause: Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.

Action: To use Certicom for SSL, install Certicom.
Level: 1

Type: WARNING

Impact: Security

BEA-090922: Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by the SSLMBean.JSSEEnabled attribute, either explicitly or by default.

Cause: The attribute SSLMBean.JSSEEnabled is selecting JSSE either explicitly or by default.

Action: To use Certicom for SSL, set the attribute SSLMBean.JSSEEnabled to false.
Level: 1

Type: WARNING

Impact: Security

BEA-090923: JSSE has not been selected by the SSLMBean.JSSEEnabled attribute, however Certicom SSL is not available, so JSSE is being used for SSL.

Cause: Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.

Action: To use Certicom for SSL, install Certicom.
Level: 1

Type: WARNING

Impact: Security

BEA-090924: JSSE has been selected by default, since the SSLMBean is not available.

Cause: This usually occurs early in server startup, before Management Service runtime access is available.

Action: No action is required. Eventually the Management Service will start and normal operation will commence.
Level: 1

Type: WARNING

Impact: Security

BEA-090925: JSSE has been selected by default, since the system property {0} has the invalid value "{1}".

Cause: The system property {0} was not set to "true" or "false".

Action: Change the system property {0} value to be either "true" or "false".
Level: 1

Type: WARNING

Impact: Security

BEA-090926: Illegal key store source value [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]

Cause: The configured key store source value is not valid for the key store type.

Action: Correct the key store source value, ensuring that the source is appropriate for the key store type. For example, the "jks" key store type requires that the source be a file path to an existing key store file.
Level: 1

Type: ERROR

Impact: Security

BEA-090927: Illegal or unknown key store type value [keyStoreType="{0}", source="{1}"]

Cause: The configured key store type value is not recognized.

Action: Correct the key store type value. For example, the "jks" key store type requires the type value to be "jks".
Level: 1

Type: ERROR

Impact: Security

BEA-090928: Unable to instantiate key store [keyStoreType="{0}", provider="{1}", exception="{2}", message="{3}"]

Cause: Key store instantiation failure usually occurs because no appropriate specified or default provider is available. See the exception for details.

Action: Verify that key store type is correct, and that a supporting Java Cryptography Architecture (JCA) provider is available in the Java Runtime Environment. A "jks" key store provider is usually available by default. An Oracle Key Store Service (type "kss") provider is only available if Oracle Java Required Files (JRF) is installed.
Level: 1

Type: ERROR

Impact: Security

BEA-090929: Unable to load key store [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]

Cause: A key store could fail to load due to an invalid source or password. Since key store instantiation succeeded, the key store type is valid. See the exception for details.

Action: Check the configured key store source and password values.
Level: 1

Type: ERROR

Impact: Security

BEA-090930: One of the Custom Identity Key Store attributes is not set on the channel override (NetworkAccessPointMBean). If any of the following attributes are set, then all of these attributes must be set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Cause: One of the following Custom Identity Key Store attributes are not set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Action: Ensure all of the following attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
Level: 1

Type: ERROR

Impact: Security

BEA-090931: When overriding Custom Identity Key Store attributes, ChannelIdentityCustomized must be enabled.

Cause: ChannelIdentityCustomized is not enabled, and must be when the following Custom Identity Key Store attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Action: Enable ChannelIdentityCustomized.
Level: 1

Type: ERROR

Impact: Security

BEA-090932: When overriding Custom Identity Key Store attributes, CustomPrivateKeyAlias must be set on the channel override (NetworkAccessPointMBean).

Cause: CustomPrivateKeyAlias is not set on the NetworkAccessPointMBean, and must be when the following Custom Identity Key Store attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.

Action: Set the CustomPrivateKeyAlias attribute on the NetworkAccessPointMBean.
Level: 1

Type: ERROR

Impact: Security

BEA-090933: Unable to obtain private key with alias {2} from {1} keystore file : {0}

Cause: Either KeyStoreFileName or KeyStorePassPhrase or KeyStoreAlias or KeyStore private key password is incorrect.

Action: Verify that the path to the keystore, the keystore type, the password for the keystore, the alias for the keystore, and the password for the private key were specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090934: Loading certificates and private key from {1} keystore file {0} caused an Exception :{2}

Cause: Either KeyStoreFileName or KeyStorePassPhrase or KeyStoreAlias or KeyStore private key password is incorrect.

Action: Verify that the path to the keystore, the keystore type, the password for the keystore, the alias for the keystore, and the password for the private key were specified correctly.
Level: 1

Type: ERROR

Impact: Security

BEA-090935: Could not load a {1} keystore from the file {0}. Exception: {2}

Cause: There is an I/O or format problem with the keystore data.

Action: Verify that the path to the keystore, the keystore type, and the password for the keystore were specified correctly. Note that some keystore types (for example, JKS) do not require a password for read-only access. Read the exception text for more help on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1

Type: ERROR

Impact: Security

BEA-099000: Invalid property value: {0}={1}

Cause: An exception occurred while processing the value for the specified property.

Action: Correct the property and restart. This exception should not normally occur as the properties are only used internally.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-099001: Caught exception while evaluating policy expression: {0} associated with: {1}

Cause: The evaluate method of the predicate used by the policy failed with a RuntimeException.

Action: Ensure that parameters which are passed to the predicates in the expression or context are valid.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-099002: An invalid predicate {0} was retrieved from the database. Ensure that the predicate class is in the server classpath.

Cause: The class file belonging to the condition was not in the server classpath.

Action: Update the classpath and restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-099003: Evaluation of policy associated with role {0} failed because the policy expression contains unregistered predicate: {1}.

Cause: The predicate that is specified in the log message is not registered, or the policy is out of date.

Action: Register the predicate or remove its reference from the policy.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-099004: Evaluation of policy associated with resource {0} failed because the policy expression contains unregistered predicate: {1}.

Cause: The redicate that is specified in the log message is not registered, or the policy is out of date.

Action: Register the predicate, or remove its reference from the policy.
Level: 1

Type: NOTIFICATION

Impact: Security

BEA-100000: Invalid call to the deprecated method {0}.

Cause: The method was deprecated in the latest servlet specification.

Action: Check the specification for an alternative. If not corrected, unpredictable behavior might occur.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100005: Could not remove session: "{0}".

Cause: An unexpected error occurred while removing the session.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100006: HTTP session file persistence: storing sessions in directory: {0}.

Cause: This is an informational message.

Action: Ensure that the directory stores the sessions per the PeristentStoreDir session parameter (weblogic.xml).
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100007: Erasing the directory tree for persistent HTTP sessions: {0}.

Cause: The storage directory is being deleted as a result of session invalidation.

Action: Ensure that deletion is occurring while removing sessions.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100008: Cannot delete "{0}".

Cause: The storage directory failed to be deleted.

Action: Ensure that the permissions on this directory are correct and that the file and directory are not in use by another process.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100011: An error occurred while serializing session data. Deleting this session.

Cause: This might be due to a change in the class definition or serialVersionUID.

Action: Check the exception text for the exact error message and take appropriate action.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100013: {0} not invalidated. The session that was serialized into the file system does not exist.

Cause: The session was not found and does not exist.

Action: This session might have been deleted by a trigger in another server, which is pointing to the same storage location.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100015: Deleted file-based session persistent store file: {0}.

Cause: This is an informational message indicating that the storage file is being deleted.

Action: Ensure that the deletion is consistent with the path defined in the PersistentStoreDir (weblogic.xml)
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100016: Session expiration check failed for: {0}. Invalidating the session expiration check.

Cause: An unexpected error occurred while checking the session for expiration.

Action: The session will be removed from the persistent store. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100018: An error occurred while loading the serialized session data for session {0}.

Cause: An unexpected error occurred.

Action: Check the exception text for the exact error message. The file could be corrupted.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100019: The file-based persistent session ID: "{0}" was stored in file: "{1}". File exists: {2}.

Cause: This is an informational message indicating that the session was stored in this path.

Action: Ensure that the file-based persistent session storage is consistent with the PersistentStoreDir (weblogic.xml).
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100020: Received malformed cookie ID: {0}.

Cause: The cookie could not be parsed properly.

Action: Check the cookie format and the exception text for the exact problem.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100022: Session invalidation interval: {0}

Cause: The session invalidation trigger is being created.

Action: Ensure that the session invalidation interval is consistent with the InvalidationIntervalSecs (weblogic.xml).
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100025: An unexpected error occurred in the HTTP session timeout callback while deleting sessions.

Cause: The invalidation trigger failed unexpectedly while deleting sessions.

Action: Check the exception message for the probable cause.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100026: An unexpected error occurred in the HTTP session timeout callback while checking session expiration.

Cause: An unexpected error occurred while checking the sessions for expiration.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100028: The session data could not be deserialized.

Cause: The session data could not be deserialized.

Action: Ensure that the object being put into the session is serializable and that the non-transient objects it aggregates are also serializable. If any of the non-transient objects in the entire object graph are not serializable, this error message will occur.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100030: HTTP session expired. Session ID: {0}

Cause: This is an informational message indicating that the session with ID {0} has expired.

Action: If the session expired sooner than expected, check the SessionTimeout parameter in the weblogic.xml file.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100031: An error occurred while unregistering the servlet session runtime MBean: {0}.

Cause: This MBean could not be removed.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100032: An error occurred while creating a servlet session runtime MBean.

Cause: This MBean could not be created.

Action: Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100033: The license for replicated sessions is invalid: {0}. Downgrading sessions to memory, which are not replicated.

Cause: The license was not valid to support replicated sessions.

Action: Check the license. An upgrade to a clustering and replication license may be desired. Alternatively, file and JDBC persistence can be used for session store reliability.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100035: The timer invalidated session ID: {0}, Web application: {1}, because it expired.

Cause: This message was logged by the Web application level timer, which periodically checks the sessions for expiration. The session expired.

Action: If the session expired too soon, check the SessionTimeout in the weblogic.xml file.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100038: Unknown persistent type: {0} for Web application: {1}. Valid types are: memory, file, replicated, JDBC, cookie, and replicated_if_clustered.

Cause: The specified persistent store type for this Web application was not recognized.

Action: Check the PersistentStoreType parameter in the weblogic.xml file. The valid values are: memory, file, replicated, cookie, JDBC, and replicated_if_clustered.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100039: Replicated HTTP sessions were specified for the Web application: {0}, but clustering was not enabled.

Cause: The session replication mechanism relies on clustering, which was not been configured.

Action: Set up clustering or change the PersistentStoreType in the weblogic.xml file to either memory, file, JDBC, or cookie.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100040: The getAttribute(): {0} was a handle. Reconstructing the EJB object.

Cause: This is an informational message indicating that the container is storing only the handle for the EJB object placed into the session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100041: The setAttribute(): {0} was an EJB object. Storing the handle into the session.

Cause: The container found an EJB handle stored in the session. It will reconstruct the EJB object before returning it.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100042: An error occurred while reconstructing the EJB object: {0}, which was put into the session.

Cause: The container found an EJB handle stored in the session. However, it failed to reconstruct the EJB object using that handle.

Action: Ensure that the handle is still valid. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100043: An error occurred while finding the handle for the EJB object: {0}.

Cause: The container stores only the handle for an EJB object put into the session. However, in this case, it failed to find the handle.

Action: Check the RemoteException for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100044: Found WLCookie cookie {0}={1}.

Cause: The cookie persistence mechanism relies on setting the cookie header.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100045: Malformed WLCookie. Value: {0} will be ignored.

Cause: The cookie persistence mechanism relies on setting the cookie header.

Action: The cookie was found to be malformed. Only strings are supported for cookie-based persistence. Ensure that there are no characters in the attribute names and values, which can break the cookie syntax.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100046: Creating new session with ID: {0} for Web application: {1}.

Cause: A new session was created.

Action: Ensure that the length is equal to the IDLen parameter in the weblogic.xml file.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100047: Performing the database operation: {0} with ID: {1} and Web application: {2}.

Cause: This is an informational message for JDBC-based persistence. It is meant for debugging purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100048: Looked up ROID: {0} from host {1}:{2} for ID: {3}.

Cause: The replicated session ID was not found in the current server, perhaps because this server is not the primary or secondary server. Another attempt to retrieve the session from the assigned secondary server will be made if it is alive.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100049: An error occurred while looking up the session with ID:{0}.

Cause: A RemoteException occurred when looking up the session from the secondary server.

Action: Check if the secondary server is down. Note that it is not recommended to stop both the primary and secondary server at the same time. Because replication happens lazily, upon request, if the secondary server needs to end, give sufficient time so that the active end users hit their sessions and get replicated.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100050: The current server is becoming the primary server for replicated session ID: {0}.

Cause: The current server is taking the role of the primary server for the given session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100051: The current server is becoming the secondary server for replicated session ID: {0}.

Cause: The current server is taking the role of the secondary server for the given session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100052: Unregistering replicated session ID: {0}.

Cause: The current server will unregister the given session.

Action: The session was invalidated. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100053: Failed to update the secondary server for HTTP session ID: {0}.

Cause: Failed to update the secondary server for the modification that occurred in the current request.

Action: Verify that the secondary server is alive, and ensure that the objects put into the session are all serializable. Also, check the exception text for the exact error message.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100054: Failed to find the secondary server for HTTP session ID: {0}.

Cause: The secondary server could not be found for the replicated session.

Action: Verify that the clustering is configured properly and that there is more than one server in the cluster.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100055: The generated session ID: {0} contains a reserved keyword and is regenerating.

Cause: On Windows 32-bit systems, if the session ID contains a reserved keyword, the file-based persistence fails. This is because it relies upon successful creation of subdirectories. The reserved keywords are: "CON", "PRN", "AUX", "NUL" "COM1", "COM2", "COM3", " COM4", "COM5", "COM6", "COM7", " COM8", "COM9", "LPT1", "LPT2", " LPT3", "LPT4", "LPT5", "LPT6", " LPT7", "LPT8", "LPT9", "CLOCK$"

Action: No action is required. The session ID will be regenerated.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100056: For {0}: The session with ID: {1} was invalidated before the session creation and registration could complete.

Cause: This is a past-release problem.

Action: Contact My Oracle Support and file a bug report.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100057: This server does not have deployment for the Web application with context path: {0}. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.

Cause: WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers.

Action: Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100058: The PersistentStoreType for the Web application with context path: {0} is not replicated. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.

Cause: WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers with uniform configuration.

Action: Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster. Also, the PersistentStoreType should be set to "replicated" for all cluster members.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100059: An unexpected error occurred while cleaning up sessions during undeployment of Web application: {0}.

Cause: The trigger failed to clean up the expired session.

Action: Check the exception text for the exact error message. When using JDBC-based HTTP session persistence, ensure that the database is set up properly. For file-based persistence, ensure that the permissions on the storage directory are appropriately set.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100060: An unexpected error occurred while retrieving the session for Web application: {0}.

Cause: The session from persistent store could not be retrieved.

Action: Check the configuration, and check the exception text for the exact error message. Also, check the WebLogic Server documentation for more details about how to configure session persistence for Web applications.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100061: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for memory-based sessions.

Action: If the session data should survive redeployment, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100062: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for a replicated session.

Action: If the session data should survive redeployment and session failovers, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100063: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.

Cause: The session.setAttribute(name, value) was invoked with a non-serializable value for a file-based persistent session.

Action: If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100064: Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.

Cause: The session.setAttribute(name, value) attribute was invoked with a non-serializable value for a JDBC-based persistent session.

Action: If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100065: {0}. Failed to remove attributes for HTTP session ID: {1}.

Cause: An unexpected error occurred during HTTP session invalidation.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100066: Failed to look up the replicated session object for Web application: {0}, session ID: {1}.

Cause: The ReplicationManager returned the NotFoundException.

Action: This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations. Check the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100067: Failed to look up the secondary information for Web application: {0} session ID: {1}.

Cause: The ReplicationManager returned the NotFoundException. This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations.

Action: Check the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100068: Failed to look up the secondary information for Web application: {0} session ID: {1}.

Cause: The ReplicationManager failed to look up the secondary information for a valid session.

Action: This is an unexpected error. Check the error message for details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100069: The getAttribute(): {0} was a HomeHandle, reconstructing the EJBHome.

Cause: This is an informational message indicating that the container is storing only the handle for the EJBHome placed into the session.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100070: Error reconstructing the EJBHome put into session for name: {0}

Cause: The container found an EJBHome handle stored in the session. However, it failed to reconstruct the EJBHome using that EJBHome handle.

Action: Ensure that the HomeHandle is still valid. Check the exception text for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100071: The setAttribute(): {0} was an EJBHome, storing the HomeHandle into the session.

Cause: The container found an EJBHome handle stored in the session. It will reconstruct the EJBHome object before returning.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Session

BEA-100072: Error in finding the HomeHandle for the EJBHome: {0}.

Cause: The container stores only the handle for an EJBHome put into the session. However, in this case, it failed to find the HomeHandle.

Action: Check the RemoteException for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100073: Exception while serializing session object: {0}.

Cause: The session object failed to serialize.

Action: Check the exception text for the exact error message details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100079: WAN failover configuration missing.

Cause: The JDBCTxDataSource or the backup cluster address was not properly configured.

Action: Set the JDBCTxDataSource or the backup cluster address to store session state.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100081: Persistent store settings cannot be changed between versions. The persistent store settings for application {0} is different from the settings for previous versions.

Cause: The persistent store settings of the new version were different from previous versions.

Action: Ensure that the persistent store settings are not changed when deploying a new version of an application.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100082: Failed to deploy {0} because the JDBC data source was missing. Target a JDBC data source to the cluster.

Cause: The configuration was incomplete.

Action: Target a JDBC data source to the cluster. Refer to the cluster documentation for more information.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100083: The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list does not contain all members of cluster: {3}. Non-homogeneous deployment for replicated sessions is not allowed.

Cause: Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.

Action: Fix the targets for this Web application. Specify a cluster or virtual host as the target.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100084: The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list contains virtual host: {3}, for which the target list does not contain all members of cluster: {4}. Non-homogeneous deployment for replicated sessions is not allowed.

Cause: Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.

Action: Fix the targets for this Web application.Specify a cluster or virtual host as the target.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100087: The JDBC session data for session ID: {0} has been modified by another server in the cluster.

Cause: The front-end Web server failed to maintain server affinity.

Action: Ensure that the front-end Web server or load balancer has been properly configured.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100089: The session ID: {0} has been accessed from {1}, a server that is neither the primary ({2}) nor the secondary ({3}). The request URL was: {4}

Cause: The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickiness), when possible.

Action: Please ensure that the front end webserver or load-balancer has been properly configured.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100090: An unexpected error occurred during a batched update of the last accessed time attribute of the updated sessions in application {0}.

Cause: Check the exception message for details.

Action: Check the exception message for details.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100094: The session ID: {0} has been accessed from {1}, a server that is not the primary ({2}). The request URL was: {3}.

Cause: The most likely cause is a configuration error on a front-end hardware load balancer or Web server plug-in. These should be configured to respect the values of the primary or secondary in the cookie (for example, stickiness), when possible.

Action: Ensure that the front-end Web server or load balancer has been properly configured.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100095: persistent-data-source-jndi-name is required for an async-jdbc session.

Cause: persistent-data-source-jndi-name was not used to specify the data source JNDI name for the JDBC connection, but persistent-store-type is async-jdbc.

Action: Use persistent-data-source-jndi-name to specify the data source JNDI name for the JDBC connection.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-100096: persistent-data-source-jndi-name will take effect and persistent-store-pool will be ignored for async-jdbc session in application {0}.

Cause: This is debug information.

Action: No action is required.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100097: The IDLength {0} is too short. It is not secure. WebLogic Server will increase the length to {1}.

Cause: The IDLength of Session Descriptor is smaller than {1}.

Action: Mofify the Weblgoic deployment descriptor. Ensure that the IDLength of Session Descriptor is equal to or greater than {1}.
Level: 1

Type: WARNING

Impact: HTTP Session

BEA-100098: persistent-data-source-jndi-name or persistent-store-pool is required when persistent-store-type is jdbc.

Cause: persistent-data-source-jndi-name or persistent-store-pool was not used to configure the database connection, but persistent-store-type is jdbc.

Action: Use persistent-data-source-jndi-name or persistent-store-pool to configure the database connection.
Level: 1

Type: ERROR

Impact: HTTP Session

BEA-101002: [{0}] Could not deserialize the context attribute.

Cause: The classloader changed. When this happens, the old attributes are deserialized using the new classloader.

Action: Ensure that the attribute class is available to the Web application scope and is serializable.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101003: [{0}] {1} called with a null document root.

Cause: The Web application did not initialize correctly.

Action: Check the log file for error messages about this Web application.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101005: [{0}] {1} called with unsafe path: "{2}".

Cause: The virtual path that was passed in points to a resource outside of the Web application scope.

Action: Check the virtual path being passed to the method and rectify the problem accordingly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101008: [{0}] Cannot get InputStream of resource "{1}".

Cause: The getResourceAsStream() method failed to get an InputSteam for the resource.

Action: Ensure that the resource exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101017: [{0}] Root cause of ServletException.

Cause: The Web application container caught an unexpected exception.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101019: [{0}] Servlet failed with an IOException.

Cause: An unexpected IOException was caught while processing the request.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101020: [{0}] Servlet failed with an Exception

Cause: An unexpected error occurred.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101024: [{0}] Unsupported error status code for the error-page element in web.xml.

Cause: The format of the error status code was invalid.

Action: Check the web.xml and fix the error-page element error status code.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101025: [{0}] Document root is null.

Cause: This should never happen. The initialization failed.

Action: Check the log file for error messages during the Web application initialization phase.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101027: [{0}] Document root: "{1}" does not exist.

Cause: This is an unexpected error message.

Action: Ensure that the directory exists.
Level: 1

Type: INTERNAL_ERROR

Impact: HTTP

BEA-101029: [{0}] cannot make temporary directory "{1}". Will not be able to compile JSPs.

Cause: The creation of the temporary directory failed.

Action: Check the write permissions.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101040: [{0}] Error occurred while trying to set "{1}{2}".

Cause: A NumberFormatException occurred while parsing the value assigned to the reloadCheckSecs parameter in web.xml.

Action: Ensure that the value was entered correctly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101045: [{0}] {1}

Cause: This is a general purpose error message.

Action: Check the message for the exact cause and take proper action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101046: [{0}] {1}

Cause: This is a general purpose error message.

Action: Check the exception for exact cause and take proper action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101047: [{0}] {1}

Cause: This is a general purpose informational message for debug purposes only.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101051: [{0}] started

Cause: This is an informational message indicating that the Web server has been started.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101052: [{0}] Initialized

Cause: This is an informational message indicating that the Web server has been initialized.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101053: [{0}] Loading Web application: {1}

Cause: The Web application is being deployed.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101054: [{0}] {1} is the default Web application for {2}.

Cause: The given Web application is being registered as a default Web application.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101060: [{0}] Loading "{1}" from directory: "{2}"

Cause: The Web application was deployed using an exploded directory structure.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101061: [{0}] Could not find Web application "{1}".

Cause: The descriptor for the Web application with the name given could not be loaded.

Action: Check the error message for details and ensure that the Web application was configured properly.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101062: [{0}] Error reading Web application "{1}".

Cause: An IOException occurred while reading the descriptors for the Web application.

Action: Ensure that the web.xml and weblogic.xml descriptors exist in the right place.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101064: [{0}] Error parsing descriptor in Web appplication "{1}"

Cause: An unexpected error occurred while reading the descriptors for the Web application.

Action: Ensure that web.xml and weblogic.xml exist in the right place
Level: 1

Type: ERROR

Impact: HTTP

BEA-101066: [{0}] Cannot initialize HTTP URL resources. Could not get JNDI context: {1}.

Cause: The URL contexts could not be registered because the JNDI context was not found.

Action: Ensure that the JNDI resources were properly configured.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101067: [{0}] Disregarding null URL resource value for property {1}

Cause: The URL for the JNDI resource specified in URLResource was null.

Action: Correct the configuration (WebServerMBean). The URLs cannot be null.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101068: [{0}] Could not parse URL resource value {1}.

Cause: The URL for the JNDI resource specified in the URL resource was malformed.

Action: Correct the configuration (WebServerMBean). Specify a valid URL.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101069: [{0}] Could not bind URL {1} to JNDI name {2} error message: {3}.

Cause: The URL failed to bind with the JNDI name.

Action: Correct the configuration (WebServerMBean).
Level: 1

Type: ERROR

Impact: HTTP

BEA-101070: [{0}] Bound URL resource "{1}" to JNDI name "{2}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101075: [{0}] HttpServer is shutting down.

Cause: The Web server is shutting down.

Action: This is a debug message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101083: Connection failure.

Cause: The connection failed while writing data into the stream.

Action: Check the exception for the exact cause and take appropriate action.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101086: No host in HTTP header. Dispatching to default HTTP server.

Cause: Host header missing.

Action: Ensure that the requests are accompanied with a host header in order for virtual hosting to work. Also, proper HTTP redirects must have a host header.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101087: {0} is not a virtual host. Dispatching to default HTTP server.

Cause: The host header is missing from the HTTP request.

Action: Make sure the requests are accompanied with a host header in order for Virtual Hosting to work. Also, proper HTTP redirects must have a host header.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101088: Dispatching request to {0}.

Cause: Dispatching the request to the Web server (Virtual Host) defined by the host header.

Action: Check the configuration.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101093: A problem occurred while dispatching the servlet request.

Cause: The request could not be dispatched into the execute queue.

Action: The request could be malformed. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101095: POST time exceeded the configured MaxPostTimeSecs of {0,number}.

Cause: The parameter makes sure that a malicious user does not send slow POSTs to cause a denial of service attack.

Action: If you think the time was too short, try increasing the value of MaxPostTimeSecs using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101096: POST size exceeded the MaxPostSize={0,number}.

Cause: The parameter makes sure that a malicious user does not send huge POSTs to cause a denial of service attack.

Action: If you think the post size is unreasonable, try increasing MaxPostSize using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101100: [{0}] Got bad cookie header: {1} from User-Agent: {2}

Cause: A cookie was malformed.

Action: Refer to the cookie specifications for the correct format: http://www.ietf.org/rfc/rfc2965.txt (Oct 2000; Obsoletes: 2109) http://www.ietf.org/rfc/rfc2109.txt (Feb 1997) http://www.ietf.org/rfc/rfc2616.txt (Jun 1999; Obsoletes: 2068) http://www.ietf.org/rfc/rfc2068.txt (Jan 1997)
Level: 1

Type: ERROR

Impact: HTTP

BEA-101101: [{0}] Unable to create new session.

Cause: A new session could not be created.

Action: Ensure that the persistent store has been properly configured.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101104: Servlet execution in servlet context "{0}" failed, {1}.

Cause: An unexpected error occurred while serving the request. This is not a simple client connection reset error.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101105: [{0}] error-page location: "{1}" for the error-code: "{2,number}" does not exist. Serving the default error page.

Cause: The error-page you configured in web.xml does not exist. A configuration error has occurred.

Action: Correct the web.xml descriptor, or make the resource available.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101106: [{0}] Could not serve custom error page: "{1}" for the error code: "{2,number}"

Cause: The error-page configured in web.xml does not exist. A configuration error has occurred.

Action: Correct the web.xml descriptor or make the resource available.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101107: [{0}] Problem occurred while serving the error page.

Cause: The error-page configured in web.xml could not be served.

Action: Check the configuration in web.xml.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101108: [{0}] Unsupported encoding: "{1}" specified.

Cause: The specified encoding is not supported by the underlying virtual machine(VM).

Action: Ensure that the specified encoding is valid or install the additional encoding classes.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101122: [{0}] Servlet: "{1}" is permanently unavailable.

Cause: The Web application is not currently available.

Action: Ensure that the Web application has been deactivated. Check to see if redeployment is in progress.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101123: [{0}] Servlet: "{1}" will be unavailable for the next: "{2,number}" seconds.

Cause: The servlet has been marked as unavailable.

Action: Make the request again after the specified time.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101125: [{0}] Error occurred while instantiating servlet: "{1}".

Cause: The servlet failed to instantiate.

Action: Ensure that the servlet has been configured properly in web.xml. Also, check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101126: [{0}] Error casting servlet: "{1}" to javax.servlet.Servlet

Cause: The servlet class that has been configured does not implement javax.servlet.Servlet.

Action: Fix the definition of the class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101128: Initializing HTTP services.

Cause: This is an informational message.

Action: Ensure that the resources are available now.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101129: Initializing the Web application container.

Cause: This is an informational message.

Action: This is an informational message. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101133: Initializing Web server {0}.

Cause: The Web server was just initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101135: {0} is the default Web server.

Cause: The default Web server name is being logged.

Action: This is an informational message for debug purposes only. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101136: Registering virtual host: {0}.

Cause: A Virtual Host (non-default Web server) has been registered.

Action: This is an informational message for debug purposes only. No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101138: {0} One of the getParameter family of methods was called after reading from the ServletInputStream. Not merging post parameters.

Cause: If the servlet reads the data from the input stream directly, then the request data will not be available for the getParameter family of methods.

Action: If the code relies on post parameters being available through the getParameter method, fix the code.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101140: An error occurred while creating servlet {1} (class: {2}, initArgs: {3}) for Web application {0}.

Cause: The servlet instance failed to initialize.

Action: Check the configuration and the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101142: There was an error unregistering servlet runtime {0}.

Cause: The servlet runtime MBean that is used for monitoring could not be destroyed.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101143: An error occurred while unregistering Web application component runtime {0}.

Cause: The Web application runtime MBean that is used for monitoring could not be destroyed.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101159: [{0}] Received IllegalAccessException while instantiating servlet: "{1}". Ensure that the servlet implementation is a public class.

Cause: This occurs if WebLogic Server attempts to instantiate a servlet class that is not declared public.

Action: Ensure that the servlet implementation is a public class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101160: Deployment descriptor is malformed; check against the DTD: {0}.

Cause: The web.xml file is not in strict conformance to the DTD. There may be deployment problems if this is not corrected.

Action: Check the web.xml file against the DTD to ensure conformance. Remember that the ordering of elements is important.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101162: User defined listener {0} failed: {1}.

Cause: The listener failed while processing the event fired by the container.

Action: Check the exception for the exact error message and fix the listener code.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101163: Could not load user defined listener: {0}

Cause: The listener class could not be loaded or instantiated.

Action: Check the exception for the exact error message and fix the listener code.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101164: User defined class {0} is not a listener, as it does not implement the correct interface(s).

Cause: The class is invalid.

Action: Fix the listener code to implement the appropriate interfaces.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101165: Could not load user defined filter in web.xml: {0}.

Cause: The filter class could not be loaded.

Action: Check the configuration and ensure that the class is available to the context classloader.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101168: The security-role-assignment references an invalid security-role: {0}.

Cause: The security-role-assignment specified in weblogic.xml is not valid.

Action: Ensure that the role-name defined in web.xml is valid. Also, check the DTD and examples for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101169: The servlet {0} is referenced but not defined in web.xml.

Cause: The servlet-mapping element in web.xml refers to a servlet name that was not defined.

Action: Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101170: The servlet {0} is referenced in servlet-mapping {1} but not defined in web.xml.

Cause: The servlet-mapping element in web.xml refers to a servlet name that was not defined.

Action: Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101171: The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.

Cause: The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.

Action: Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101172: The web.xml descriptor has no ejb-ref entries.

Cause: The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.

Action: Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101173: Did not find resource-ref in web.xml matching {0}.

Cause: The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.

Action: Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101174: Did not find ejb-ref in web.xml matching {0}.

Cause: The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.

Action: Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101175: [{0}] Exception occurred while closing zip file {1}.

Cause: A zip file failed to close while undeploying a Web application.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101180: The auth-constraint references security-role: {0}, which is not defined in web.xml.

Cause: The auth-constraint should refer to roles that have been defined in web.xml.

Action: Add the definition of this role in the security-role element of web.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101188: A bad exception-type exists in web.xml: {0}.

Cause: An invalid class can cause this exception while registering the Web application.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101189: Could not load the url-match-map class defined in weblogic.xml: {0}.

Cause: An invalid classname will cause this exception while registering the Web application.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101194: The preprocessor {0} is referenced but not defined in weblogic.xml.

Cause: The preprocessor element is not defined in weblogic.xml.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101196: [{0}]: Error while parsing the Tag Library Descriptor at "{1}".

Cause: A TLD parsing exception occurred.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101198: Could not deploy role: {0} for Web application: {1} application: {2}.

Cause: The Web application could not deploy the role defined in web.xml.

Action: Ensure that security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101199: Could not deploy policy for resource: {0}.

Cause: The Web application failed to deploy the policy for the security-constraint defined in web.xml.

Action: Ensure that security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101200: CacheFilter not caching the response for URI: {0} reason: {1}

Cause: The CacheFilter does not cache responses unless the status is 200.

Action: Check the message for information on how to fix the problem.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101212: {0}:{1} Failure while precompiling JSPs: {2}.

Cause: The JSPs failed to precompile at startup.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101214: Included resource or file "{0}" not found from requested resource "{1}".

Cause: The included resource or file is missing.

Action: Add the missing resource or file.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101215: Malformed request "{0}". Request parsing failed, Code: {1}

Cause: The request does not follow the pattern specified by the HTTP 1.0/1.1 specification(s).

Action: Fix the client that sent the invalid request.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101216: Servlet: "{0}" failed to preload on startup in Web application: "{1}".

Cause: The servlet that was marked as load-on-startup failed to preload on startup.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101217: Cannot deploy {0} from {1} on {2}, because there is already a Web application named {3} loaded from {4}, using the context path {5}.

Cause: The Web application that is being deployed has been assigned a context path that is already in use.

Action: Choose a different context path.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101218: An error exists in web.xml for servlet "{0}". Neither servlet-class nor jsp-file is defined.

Cause: The servlet element should contain either servlet-class or jsp-file. Both are missing.

Action: Update the web.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101220: An error occurred while setting the document root for "{0}" to "{1}".

Cause: Setting the document root for the Web application failed. The Web application will not be deployed.

Action: Check the IOException message for exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101221: The url-pattern is empty or null for url-pattern {0} in {1}.

Cause: Not a valid url-pattern for the servlet.

Action: If the servlet is intended to be a default servlet, then specify / or /*.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101223: {0}: The server {1} is temporarily suspended.

Cause: The server has been suspended by the administrator.

Action: Wait until it comes back up again.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101226: AuthFilter: {0} invocation failed in: {1} phase for URI: {2}

Cause: The authentication filter that acts before and after the authentication phase failed to execute.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101228: Failed to undeploy security policy for resource: {0} while undeploying Web application.

Cause: The security policy defined in web.xml failed to undeploy upon Web application undeployment.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101229: Failed to undeploy security policy for resource: {0} while undeploying the Web application.

Cause: The security role defined in web.xml failed to undeploy upon Web application undeployment.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101231: The HTTP log file does not use version 1.0 of the Extended Log File format.

Cause: The ELF headers in the existing log file specify a version other than 1.0.

Action: Only version 1.0 is supported. Delete the existing log file and start over again.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101232: An exception occurred while reading headers of HTTP log file.

Cause: An IOException was received while reading the headers.

Action: Check the exception for the exact cause of the problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101234: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed due to an exception.

Cause: An unexpected error occurred while initializing the log file format.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101235: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed because class: {1} is not an instance of weblogic.servlet.logging.CustomELFLogger.

Cause: An unexpected error occurred while initializing the ExtendedLogFormat.

Action: Check the exception for the exact error message.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101236: The format of log field {0} is incorrect.

Cause: The format of the log field is invalid.

Action: Check the log field and fix the format.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101237: HTTP logging has been disabled for the Web server: {0}.

Cause: This is a debug message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101242: Failed to roll the HTTP log file for the Web server: {0}.

Cause: An unexpected error occurred.

Action: Check the exception message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101247: {0}: Public ID references the old version of the Servlet DTD. Change the public ID in web.xml file to "{1}".

Cause: The public ID in WEB-INF/web.xml references the old version of servlet DTD.

Action: Generally, this will not cause any problems with the application unless the DTD has changed in a way such that the web.xml cannot be parsed. To avoid the message, change the public ID in the web.xml file to the current version of the servlet DTD.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101248: [{0}]: Deployment descriptor "{1}" is malformed. Check against the DTD: {4} (line {2}, column {3}).

Cause: The descriptor file is not in strict conformance to its DTD. There may be deployment problems if this is not corrected.

Action: Check the descriptor file against the DTD to ensure conformance. Remember that the ordering of elements is important.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101249: [{0}]: Servlet class {2} for servlet {1} could not be loaded because the requested class was not found in the classpath {3}. {4}.

Cause: The servlet class was not recognized by the Web application classloader.

Action: Ensure that the servlet class is available either in WEB-INF/classes or WEB-INF/lib or the system classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101250: [{0}]: Servlet class {2} for servlet {1} could not be loaded because a class on which it depends was not found in the classpath {3}. {4}.

Cause: One of the classes the servlet class uses was not recognized by the Web application classloader.

Action: Make sure the class is available either in WEB-INF/classes or WEB-INF/lib or system classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101251: [{0}]: Could not load servlet class {2} for servlet {1} because a resource on which it depends was not found in the classpath {3}. {4}.

Cause: This exception occurs if the Java Virtual Machine (JVM) cannot find an appropriate native-language definition of a method that is declared native.

Action: This could be due to a problem with path/LD_LIBRARY_PATH. Check if the resource it complains about exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101252: [{0}]: Servlet class {2} for servlet {1} could not be verified. {3}.

Cause: This exception occurs when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem.

Action: Verify the servlet class.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101253: [{0}]: Servlet class {2} for servlet {1} could not be defined. The class file could be corrupt. {3}.

Cause: This exception occurs when the Java Virtual Machine (JVM) attempts to read a class file and determines that the file is malformed or otherwise cannot be interpreted as a class file.

Action: Check to see if the class file is corrupt.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101254: [{0}]: Servlet class {2} for servlet {1} could not be handled by the classloader with classpath {3}. {4}.

Cause: Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class.

Action: Check the class and its dependencies.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101256: The run-as user: {0} for the servlet: {1} for Web application: {2} could not be resolved to a valid user in the system. Verify that the user exists.

Cause: The run-as element in weblogic.xml refers to an invalid user.

Action: Check to see if the user exists.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101257: Failed to parse the client certificate in header: {0}. Ignoring this certificate.

Cause: The format of the client certificate was invalid.

Action: Check the exception for more details.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101258: Invalid JSP parameter in weblogic.xml with name: {0}.

Cause: The JSP parameter was not recognized.

Action: Check the weblogic.xml descriptor and refer to the DTD for the correct syntax and element information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101260: The JSP parameter name in weblogic.xml is empty.

Cause: One of the mandatory elements in weblogic.xml was found to be empty.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101261: Invalid session parameter name in weblogic.xml: {0}.

Cause: One of the session parameters configured in weblogic.xml was invalid.

Action: Check the weblogic.xml and correct the session parameter.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101262: The session parameter name "{0}" in weblogic.xml is deprecated.

Cause: This parameter has been deprecated.

Action: See the WebLogic Server documentation for an alternative. This parameter might be removed from future releases.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101263: The session parameter name in weblogic.xml is empty.

Cause: The param-name element is a mandatory element.

Action: Check the weblogic.xml descriptor.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101264: {0}: CLIENT-CERT-based authentication failed.

Cause: Authentication failed.

Action: Either the certificate was missing or the user the certificate resolves to is not a valid user in the system.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101267: Failed while destroying filter: {0}.

Cause: Destroying the filter on the Web application undeploy failed.

Action: There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101268: {0}: Failed while destroying servlet: {1}.

Cause: Destroying a servlet on the Web application undeploy failed.

Action: There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101271: The url-pattern element is not specified for the web-resource-collection/web-resource-name: {0} in the web.xml descriptor.

Cause: The url-pattern element is a mandatory element.

Action: If you want the security constraint to apply for all requests, specify url-pattern=/*.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101275: Server has detected non-replicated sessions while SUSPENDING. Server will wait for non-replicated sessions to either become invalidated or timed out or will wait until a secondary is chosen using the lazy process (meaning if a session does not have a secondary, the server waits until the next request to create the secondary). The current timeout value is {0} seconds. To terminate non-replicated sessions immediately, use the FORCESHUTDOWN option.

Cause: During graceful shutdown, the server waits for inflight work to complete. This includes non-replicated sessions.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and force shutdown of the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101276: Web application(s) {1} still have non-replicated sessions after {0} minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.

Cause: The server is waiting for sessions to finish before gracefully shutting down.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and shutdown the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101277: Web application(s) {0} has {1} non-replicated session(s) respectively.

Cause: The server has detected non-replicated sessions while gracefully shutting down.

Action: No action is required. Use FORCESHUTDOWN to ignore inflight work and shut down the server.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101278: There are no active sessions. The Web service is ready to suspend.

Cause: All active sessions have completed. The Web service is ready to gracefully shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101280: Failed to create WebServerRuntimeMBean for the Web server: {0}.

Cause: The Web server creates a runtime MBean during the initialization phase for monitoring.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101282: {0}: jspServlet "{1}" defined in weblogic.xml could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.

Cause: The user-defined class should be a subclass of javax.servlet.http.HttpServlet.

Action: The jspServlet class must be a subclass of javax.servlet.http.HttpServlet.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101283: {0}: jspServlet "{1}" defined in weblogic.xml could not be loaded.

Cause: The user-defined class was unable to load.

Action: Ensure that the class appears in the webapp-classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101287: {0}. The servlet: {1} received an exception during servlet destroy. Ensure that the super.init(config) is called in the init() method.

Cause: This is due to a bug in javax.servlet.GenericServlet.

Action: Ensure that the super.init(config) is called in the init() method for the servlet.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101288: Application:{0} WebAppModule: {1} failed to set contextPath: {2}.

Cause: The set context path call failed for the MBean.

Action: Check that the context path assigned to this Web application module is valid.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101291: The webAppModule: {1} in application: {0} is unable to reload classes because it shares a classloader with other modules.

Cause: An attempt to reload a class was made when the classloader was shared by other modules.

Action: Ensure that the module has its own classloader or reload all modules that share the classloader at once.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101292: Validation failed for the descriptor: {0} param: {1}.

Cause: The container found an illegal value assigned to this parameter.

Action: Check the error message for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101295: Recompiling JSP [{0}], resource [{1}], because it is stale. It was previously compiled using a different version of WebLogic Server. JSP build version: {2} WebLogic Server build version: {3}.

Cause: A JSP was compiled using a different version of WebLogic Server or JSPC.

Action: To precompile JSPs, ensure that you precompile them using the same version, service pack, rolling patches, and temporary-patches in your classpath for WebLogic Server or JSPC. This will ensure the same version string and compatibility at runtime.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101296: Unable to load the default compiler class "{0}". Using the default javac compiler to compile JSPs.

Cause: The compiler class was not found and hence could not be loaded.

Action: Ensure that the class exists in the classpath.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101297: The value assigned to the container-descriptor parameter: index-directory-sort-by in weblogic.xml is invalid: {0}. The valid values are "NAME", "LAST_MODIFIED", or "SIZE".

Cause: An invalid value is specified in weblogic.xml for the container-descriptor parameter: index-directory-sort-by.

Action: Fix the values in the weblogic.xml descriptor. Valid values are "NAME", "LAST_MODIFIED", or "SIZE".
Level: 1

Type: ERROR

Impact: HTTP

BEA-101299: The servlet-mapping for servlet-name "{0}" will override the default mapping for *.jsp. This can lead to a show code vulnerability.

Cause: The url-pattern *.jsp is being overriden in the web.xml by a user-defined servlet.

Action: Since the default JSP servlet will be overriden, care must be taken to ensure that JSP source code does not appear directly on the browser.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101302: Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Will use the first principal-name: {4} specified in security-role-assignment as the run-as-identity. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.

Cause: No mapping was found for the run-as role in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101303: Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for {1} for the servlet. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.

Cause: No mapping was found for the run-as role in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101304: Web application: {0}, the {1}: {3} defined in web.xml {2} not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.

Cause: Did not find a mapping for the roles which were supposed to be mapped to a principal in security-role-assignment in weblogic.xml.

Action: Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101305: [{0}] Error-page location: "{1}" for the error code: "{2,number}" causes an infinite loop condition as it throws the same code for which it has been mapped.

Cause: The servlet for the error-page, which maps to the given error code, throws the same error code. This causes an infinite loop condition.

Action: Fix the error page.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101306: Could not resolve entity "{0}" for the webapp at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).

Cause: The descriptor validation failed.

Action: Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101307: Got an error while resolving entity "{0}" for the Web application at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).

Cause: The descriptor validation failed.

Action: Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101310: Web server: {0}, failed to perform batched update for replicated sessions against jndiname: {1} on the secondary server: {2} http-port: {3} https-port: {4}

Cause: The Remote Management Interface (RMI) call from the trigger, which was intended to periodically update the read-only replicated sessions on the secondary server, failed.

Action: Check the exception for the exact cause.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101317: The Web application: {0} has specified DIGEST as the auth-method in web.xml, which is not implemented. Will default to BASIC.

Cause: DIGEST authentication is not yet implemented. The Web application will fallback to BASIC authentication.

Action: Choose either BASIC, FORM, or CLIENT-CERT.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101318: The Web application: {0} has specified: {1} as the auth-method in web.xml, which is not valid. Valid values are BASIC (default), FORM, and CLIENT-CERT.

Cause: An invalid authentication method was specified in web.xml.

Action: The valid values are BASIC, FORM, and CLIENT-CERT. Fix the web.xml file for the Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101319: The Web application: {0} has "FORM" based authentication specified but the mandatory element: {1} is left blank.

Cause: The form-login-page and form-error-page are mandatory elements when auth-method is "FORM."

Action: Fix the web.xml for the specified Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101325: The local-path: {1} specified for the virtual-directory-mapping specified in weblogic.xml for the Web application: {0} (docroot={2}), is not valid.

Cause: A relative path was possibly assigned to the local-path. If so, the container makes the path relative to the document root.

Action: Ensure that the relative path exists with respect to the document root.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101326: The element: {1} contains an undefined security-role: {0}

Cause: The security-role definition is mandatory.

Action: Ensure that the security role-name is defined in web.xml. Also check the DTD and examples for the correct syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101327: The element: {0} is not allowed to appear more than once in the descriptor: {1}

Cause: The parser found more than one occurrence for the element.

Action: Ensure that than the element appears only once (check the schema).
Level: 1

Type: ERROR

Impact: HTTP

BEA-101328: {0}: invalid dispatcher: {2} for filter-mapping: {1}

Cause: An invalid value was found for the filter mapping dispatcher.

Action: Valid values are: "REQUEST," "FORWARD," "INCLUDE," or "ERROR."
Level: 1

Type: ERROR

Impact: HTTP

BEA-101331: Cannot deploy {0} from {1} on {2}, because there is already a non-versioned Web application named {3} loaded from {4}, using the context path {5}.

Cause: The Web application version that is being deployed has been assigned a context path that is already in use by a non-versioned Web application.

Action: Choose a different context path or undeploy the conflicting Web application.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101332: Failed to register JACC policy context handlers for the Web application container.

Cause: This is an unexpected error.

Action: See the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101337: Received a SecurityException during: {0}, for : {1}, Web application: {2}

Cause: The user does not have enough privileges.

Action: See the error message for more information.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101338: The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead, use the servletMapping = "/" to define the default servlet.

Cause: A deprecated context parameter was used.

Action: The servlet weblogic.servlet.FileServlet is the default servlet. If you want to override the default, define a new servlet-mapping in web.xml with url-pattern = "/".
Level: 1

Type: WARNING

Impact: HTTP

BEA-101339: The context parameter: {0} has been deprecated. Instead, use the element: {1} in weblogic.xml.

Cause: A deprecated context parameter was used.

Action: Replace it with the suggested alternative in weblogic.xml.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101340: The context parameter "weblogic.httpd.servlet.classpath" has been deprecated. Instead use manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual-directories in weblogic.xml

Cause: A deprecated context parameter was used.

Action: There are better ways to extend the classpath exposed to the Web application classloader, including virtual-directories and a manifest classpath.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101341: {0}: Class file up-to-date for JSP: {1}

Cause: This message indicates that the class file associated with the JSP is up-to-date.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101342: {0}: Error(s) encountered while precompiling JSP {1} {2}

Cause: The JSP file shown by the error message had errors and could not be precompiled.

Action: Correct the errors shown by the message so that it gets precompiled without errors.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101343: {0}: Attempting to precompile {1}, since the class file associated with it was found to be out-of-date.

Cause: This message indicates that the class file associated with the given JSP was out of date and needs recompilation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101344: {0}: Attempting to precompile {1}, since the class file associated with it was not found in the Web application classpath.

Cause: This message indicates that the class file associated with the given JSP was not found in the Web application classpath and thus needs to be compiled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101345: A change in value was detected for the "Fields" directive in access.log for webserver: {0}. Rotating the access.log. The value defined for the WebServerMBean will take precedence. Default being "time cs-method cs-uri sc-status". Old value: "{1}" and new value: "{2}".

Cause: This message indicates that the value from WebServerMBean.getELFFields() was different that the value in the "Fields" directive on the top of access.log.

Action: Changing the ELF fields by hand editing access.log is no longer supported. Change the access.log "Fields" using the Administration Console.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101346: The virtual host name: {0} being used by the Virtual Host: {1} is already in use by: {2}

Cause: There is duplicate name usage for VirtualHostNames.

Action: Fix the VirtualHostNames fields for the Virtual Host and choose a unique name.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101347: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is already in use by: {2}

Cause: There is uplicate name usage for ServerChannelName for Virtual Hosts.

Action: Fix the ServerChannelName field for the Virtual Host and choose a unique name.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101348: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is not defined. This virtual host will not be deployed.

Cause: The NetworkAccessPoint is not yet defined.

Action: Choose a different NetworkAccessPoint name or define a new one using the Administration Console.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101349: Failed to save the WorkContexts into the session or cache for the request: {0}

Cause: An unexpected exception occurred.

Action: At the end of the request, the Web application container saves the WorkContexts into the session and the local cache in order to propagate them between successive HTTP requests. Contact My Oracle Support and report this problem.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101350: Web application(s) {2} of module {1} of application {0} has {3} pending session(s) respectively.

Cause: The server has detected pending sessions for the Web application module while the application is gracefully transitioning from running to administration mode.

Action: No action is required. Use the -force option to ignore inflight work and bring the application to administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101351: Server has detected pending sessions while gracefully transitioning webapp module {1} of application {0} from running to administration mode. Server will wait for pending sessions to either become invalidated or timed out. The current timeout value is {2} seconds. To terminate sessions immediately, use the -force option.

Cause: During graceful transition of the application from running to administration mode, the server waits for inflight work to complete. This includes pending sessions.

Action: No action is required. Use the -force to ignore inflight work and force transition of the application from running to administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101352: There are no active sessions. The Web application module {1} of application {0} is ready to go into administration mode.

Cause: All active sessions have completed. The Web service is ready to gracefully transition to administration mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101354: Web application(s) {3} of module {1} of application {0} still have pending sessions after {2} minutes of initiating transition from running to administration mode. Waiting for pending sessions to finish.

Cause: The server is waiting for the application sessions to finish before gracefully shutting down.

Action: No action is required. Use the -force option to ignore inflight work and force transition of the application into administration mode.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101355: [{0}] Version {2} is specified for Web Services {1}, but versioning of Web Services is not supported.

Cause: An attempt was made to deploy Web Services with versioning.

Action: Deploy the Web Services (or the application containing the Web Services) without versioning.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101356: Web application: {0} failed to load the shared library (fastfile) for using native I/O in the FileServlet, falling back to the standard I/O.

Cause: An unexpected error occurred while attempting to load the native library (fastfile) for using native I/O in the FileServlet.

Action: Ensure that the shared library (fastfile) exists in a directory that is in the LD_LIBRARY_PATH or PATH. Also, note that native I/O is supported on Windows, Linux, and Solaris. If problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101357: A force graceful production to administration mode transition was initiated. The Web application module {1} of application {0} is ready to go into administration mode.

Cause: A force graceful production to administration mode transition was initiated. The Web service is ready to transition to administration mode.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101359: The servlet {0} initilization method failed while it was run in the background. The exception was: {1}.

Cause: The servlet initilization method caused an exception.

Action: The cause of the exception must be corrected and then the application should be redeployed.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101360: Recompiling JSP [{0}], resource [{1}], because it is stale.

Cause: The JSP was changed from the last time it was compiled.

Action: The JSP will be always recompiled if it is different from the last compiled version.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101361: [{0}] A library reference in weblogic.xml has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Cause: The Specification-Version of a library reference in weblogic.xml cannot be parsed.

Action: Fix the library's Specification-Version in weblogic.xml to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101362: [{0}] could not deserialize the {1} scoped attribute with name: "{2}"

Cause: Classloader changed. When this happens, the old attributes will be deserialized using the new classloader. The classloader can change either as the result of a dynamic reload of classes (controlled by weblogic.xml parameter "reload-check-secs" or upon across webapp dispatch (include or forward).

Action: Ensure that the attribute class is available to the Web application scope and that the attribute class and all the references it holds are serializable.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101363: Application: {0}, Web application: {1} has context-root specified in application.xml: "{2}". The context-root specified in weblogic.xml: "{3}" will be ignored.

Cause: The context-root specified in application.xml takes higher precedence than the one in weblogic.xml.

Action: This is an informational message. Ensure that this is what you intended to do.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101364: {0}:{1} Failure while precompiling JSP: {2}.

Cause: The JSP failed to precompile on a partial update.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101366: The server could not send the HTTP message during the configured timeout value. The socket has been closed.

Cause: This is an informational message.

Action: Bump up the value of CompleteMessageTimeout. The default is 60 seconds. If you have slow clients that cannot complete the messsage transfer and are getting timed out, raise the value.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101367: An error occurred while extracting archived file for "{0}", located at "{1}".

Cause: An error occurred while extracting the archived WAR file, due to path length limitations on some OS's.

Action: Some OS's only allow a certain number of characters in the file name. This limitation can be noticed when extracting an archive in a deeply nested directory. Since the default temporary directory for extracting all archives is relative to the server root directory, it is recommended that one use the system property weblogic.j2ee.application.tmpDir and set it to a shorter file path, or one could ensure that the server is started in a directory with a shorted file path.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101369: {0}: The encoding jsp-descriptor parameter has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.

Cause: {0}: The encoding jsp-descriptor parameter has been deprecated.

Action: Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101370: There was a failure when merging library descriptors into the application descriptors for application {0}. Ensure that the descriptors are valid. The error is {1}

Cause: The library or the application descriptors are invalid.

Action: Fix the descriptors in the application or the library.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101371: There was a failure when processing annotations for application {0}. Ensure that the annotations are valid. The error is {1}

Cause: The descriptor has an invalid servlet-class, filter-class, or listener-class.

Action: Fix the descriptors in the application or the library.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101372: There was a failure in application {0} when attempting to inject dependencies into {1}. Dependencies will not be injected into this class.

Cause: The annotations defined in the class may be invalid or the descriptor may have conflicting entries.

Action: Check the annotations defined in this class. Also, verify that the descriptor has valid entries.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101373: Reloading classes in application {0} failed due to change of annotations on a refreshed class. Modified or new annotations will not be processed during servlet reload as they involve a non-dynamic change. Redeploy the application for these annotations to be processed.

Cause: New or modified annotations will not be processed in application {0} due to a servlet refresh.

Action: Redeploy the application for reloading classes when annotations are modified.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101374: The Web container failed to look up the transaction associated with the current thread for Web application: ${0}.

Cause: After the response is sent, the container needs to check if there is any active transaction associated with the thread so that it can abort the transaction. See the exception message for more details.

Action: See the exception message for more details.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101375: [{0}]: Error while parsing the JSF Configuration Descriptor at "{1}".

Cause: A JSF Configuration Descriptor parsing exception occurred.

Action: Check the exception for the exact cause.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101376: Unable to purge cache of Bean classes from BeanELResolver, error occurs at "{0}".

Cause: Unable to get the cache property of BeanELResolver.

Action: Contact My Oracle Support and report this problem.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101377: Filtering class loader configuration ignored for web module {1} of application {0}.

Cause: Filtering class loader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone web applications). This configuration is not supported in Web modules of an enteprise application.

Action: Remove the filtering class loader configuration from the deployment descriptor of web module {1} of application {0}.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101378: The version of OpenJPA shipped with WebLogic Server does not support JPA 2.0. Recompile the application with the JPA 1.0 API JAR available at http://www.jcp.org/en/jsr/summary?id=220.

Cause: The Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.

Action: Recompile the application with the JPA 1.0 API jar available at http://www.jcp.org/en/jsr/summary?id=220 or use TopLink if you wish to use a JPA 2.0 persistence provider.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101379: Starting with WebLogic Server 10.3.4.0, some methods changed in the OpenJPA interfaces that ship with WebLogic Server. Recompile the application with the OpenJPA JAR in your WebLogic Server installation.

Cause: Some methods in the OpenJPA interfaces that ship with WebLogic Server have changed.

Action: Recompile the application with the OpenJPA JAR in your WebLogic Server installation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101380: There is more than one Web fragment with the same name: "{0}".

Cause: There is more than one Web fragment with the same name.

Action: Change the duplicate Web fragment names to avoid the conflict.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101381: Both before others and after others found in Web fragment: "{0}".

Cause: Both before others and after others was found in the Web fragment.

Action: Ensure that the Others element appears only in before or after.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101382: WLServlet annotation cannot be used with WebServlet together.

Cause: WLServlet annotation cannot be used with WebServlet together.

Action: Oracle recommends that you use only servlet 3.0 annotations.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101383: WLFilter annotation can't be used with WebFilter together

Cause: WLFilter annotation can't be used with WebFilter together.

Action: Suggest to use servlet 3.0 annotations only
Level: 1

Type: ERROR

Impact: HTTP

BEA-101384: {0} annotation is deprecated, please use servlet 3.0 annotation instead. App:{1}, Class:{2}

Cause: The older WL annotations are deprecated, and replaced by servlet 3.0 annotations, for example WLServlet is replaced by WebServlet, WLFilter is replaced by WebFilter.

Action: Suggest to use servlet 3.0 annotations instead if WL annotations
Level: 1

Type: WARNING

Impact: HTTP

BEA-101385: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface

Cause: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, please check the servlet 3.0 specification.

Action: The class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, suggest to check the servlet 3.0 specification.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101386: The ServletSecurity Annotation is illegal, the root is {0}

Cause: The ServletSecurity Annotation is illegal, the root is {0}.

Action: Suggest not to correct ServletSecurity Annotation accroding to the Servlet 3.0 Specification.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101387: ServletContext has already been initialized, cannot call method {0} any longer.

Cause: ServletContext has already been initialized, cannot call method {0} any longer.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101388: The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Cause: The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101389: Cannot add this ServletContextListener

Cause: Because this ServletContext was passed to the ServletContextListener's contextInitialized() method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.

Action: Check Servlet 3.0 Specification and the corresponding javadoc.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101390: It is illegal to use both value and urlPatterns attributes together in the same WebServlet/WebFilter annotation: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1, both the value attribute and urlPatterns attribute were detected in the identical WebServlet/WebFilter annotation.

Action: Use either the value attribute or urlPatterns attribute, but not both at the same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101391: Circular references found in web fragments relative ordering.

Cause: Circular references found in web fragments relative ordering.

Action: Use absolute ordering to overwrite relative ordering or change relative ordering config.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101392: Glassfish Descriptor element <{0}> was successfully parsed and applied.

Cause: This is an information message.

Action: No action is required if the element parsing was successful.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101393: Glassfish Descriptor element <{0}> is not supported by WebLogic.

Cause: This is an informational message.

Action: No action is required. Note that the element is ignored by the descriptor parser.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101394: The exception "{0}" occurred when processing getParameter or getParameterValues from a multipart value of a ServletRequest.

Cause: The exception "{0}" occurred when processing getPart or getParts from a ServletRequest.

Action: Check whether the size of the uploaded file exceeds the size limit. Check that the content of the post-multipart form data is correct.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101395: Application or module {0} is deployed as a web application.

Cause: The spplication or module {0} was deployed as a web application because there was no hint (descriptors or classes annotated by component annotations) detected. WebLogic Server deploys applications without deployment descriptors or classes annotated by component annotations as web application.

Action: No action is required if the application is a web application or a web module. Otherwise, add the corresponding deployment descriptors so that WebLogic Server can detect the application type correctly.
Level: 1

Type: NOTIFICATION

Impact: HTTP

BEA-101396: Either the urlPatterns or the value attribute in the WebServlet annotation MUST be present: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1.1, neither the value attribute nor the urlPatterns attribute was detected in the WebServlet annotation.

Action: Use either the value attribute or urlPatterns attribute, but not both at a same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101397: The urlPatterns attribute, servletNames attribute, or value attribute of the WebFilter annotation MUST be specified: {0}.

Cause: As per the Servlet 3.0 specification, section 8.1.2, neither the urlPatterns attribute, servletNames attribute, nor value attribute was detected in the WebFilter annotation.

Action: Use either the urlPatterns, servletNames, or value attribute in the annotation. Do not use both the urlPatterns and value attributes at a same time in the same annotation.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101398: Exception : [{0}][{1}] during request upgrade.

Cause: An error occurred while creating an instance of HttpUpgradeHandler. [{0}][{1}]

Action: Check whether the Implement of HttpUpgradeHandler exists or the class has been put under the correct classpath.
Level: 1

Type: ERROR

Impact: HTTP

BEA-101399: The Web application: {0} has specified DIGEST as the auth-method in web.xml, which is not implemented.

Cause: DIGEST authentication is not yet implemented.

Action: Choose either BASIC, FORM, or CLIENT-CERT.
Level: 1

Type: WARNING

Impact: HTTP

BEA-101400: The value of {0} attribute {1} can not be serialized and will be removed when reloading the application, the class of the value object is {2}.

Cause: An exception occurred when serializing the attribute value.

Action: Either correct the serialization issue of the attribute value class or ignore this warning if it is harmless for application reloading.
Level: 1

Type: WARNING

Impact: HTTP

BEA-110000: Transaction log record class name encoding error [{0}]: {1}

Cause: An internal error occurred while writing a record to the transaction log.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110001: Transaction log record encoding error [{0}]: {1}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110003: onError() callback exception: {0}

Cause: An internal error occurred while writing a record to the transaction log.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110004: Unable to read transaction log record checksum.

Cause: The transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system reboot, a crash caused the transaction being logged at that time to be rolled back.

Action: No action is required. Recovery is automatic.
Level: 1

Type: WARNING

Impact: JTA

BEA-110005: Transaction log record checksum failure [{0}].

Cause: A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system re-boot, a crash caused the transaction being logged at that time to be rolled back.

Action: No action is required. Recovery is automatic.
Level: 1

Type: WARNING

Impact: JTA

BEA-110007: Log record class instantiation problem [{0}]: {1}

Cause: An internal error occurred. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic Server software version.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110008: Log record class readExternal problem [{0}]: {1}

Cause: An internal error occurred. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic Server software version.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110011: onRecovery() callback exception: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110013: An error occurred while writing transaction log: {0}.

Cause: The file system is full or permission problems exist.

Action: Verify the transaction log file location and locate any file system problems.
Level: 1

Type: ERROR

Impact: JTA

BEA-110015: A version error occurred while reading the transaction log header file.

Cause: File corruption exists. A new transaction log file may have been given to an older version of WebLogic Server.

Action: The system will automatically create an empty transaction log.
Level: 1

Type: ERROR

Impact: JTA

BEA-110020: Error reading transaction log file [{0}]: {1}

Cause: There are file system or permission problems, or possible corruption of the transaction log.

Action: Verify the transaction log file location and check for file system problems. Crash recovery processing continues as best it can.
Level: 1

Type: ERROR

Impact: JTA

BEA-110021: Format error [{0}] occurred while reading transaction log file [{1}]

Cause: The transaction log file was possibly corrupted.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110022: Format error [{0}] occurred while reading transaction log file [{1}]: {2}

Cause: The transaction log file is possibly corrupted.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110023: Transaction log record checksum failure [{0}]: {1}.

Cause: A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system reboot, a crash caused the transaction being logged at that time to be rolled back.

Action: No action is required. Recovery is automatic.
Level: 1

Type: WARNING

Impact: JTA

BEA-110026: Missing transaction log file [{0}]

Cause: File system or permission problems exist, or the transaction log might be corrupted. The file might also have been manually deleted.

Action: Verify the transaction log file location and check for file system problems. Crash recovery processing will continue.
Level: 1

Type: ERROR

Impact: JTA

BEA-110028: The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during commit.

Cause: See the message details for probable cause.

Action: After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110029: The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during rollback.

Cause: See the message details for the probable cause.

Action: After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110030: XA resource [{0}] has not responded in the last {1} second(s).

Cause: The resource is unavailable (possibly the resource is down, or network problems exist).

Action: Check the resource manager and network condition. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto-refresh feature of the connection pool to do this automatically. For other third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
Level: 1

Type: WARNING

Impact: JTA

BEA-110033: Recovered transaction log header file from backup location [{0}].

Cause: This error is probably caused by a crash that occurred when the the transaction log header file was being rewritten.

Action: No action is required. Recovery is automatic.
Level: 1

Type: ERROR

Impact: JTA

BEA-110101: No license exists for two-phase commit (2PC) processing.

Cause: The 2PC license is not present.

Action: Contact an Oracle sales representative to obtain a 2PC license.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110102: A transaction with multiple resources was rolled back due to an invalid two-phase commit (2PC) license.

Cause: The 2PC license is not present.

Action: Contact an Oracle sales representative to obtain a 2PC license.
Level: 1

Type: WARNING

Impact: JTA

BEA-110200: User [{0}] is not authorized to invoke startCommit on a transaction branch.

Cause: This might be a symptom of a potential security attack or, alternately, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110201: User [{0}] is not authorized to invoke startRollback on a transaction branch.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that client software is not directly invoking an internal WebLogic system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110202: User [{0}] is not authorized to invoke rollback on a transaction branch.

Cause: This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action: Verify that client software is not directly invoking an internal WebLogic system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110204: XA resource [{0}] returns XAER_RMFAIL and is unavailable.

Cause: The resource is unavailable because is down or network problems exist.

Action: Check the resource manager and network conditions. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto-refresh feature of the connection pool to do this automatically. For other third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
Level: 1

Type: WARNING

Impact: JTA

BEA-110207: A previously unavailable XA resource [{0}] is now available.

Cause: The previously unavailable resource is now available. It is possible that the resource has recovered from earlier failures or that previous network problems were cleared.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110208: Unregistration of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110209: Registration of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110210: Failback of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: Examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [{0}].
Level: 1

Type: WARNING

Impact: JTA

BEA-110211: Failback retry of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: Examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [{0}].
Level: 1

Type: WARNING

Impact: JTA

BEA-110212: An attempt was made to manually migrate the Transaction Recovery Service of the current server away from the server while it is still active.

Cause: An attempt was made to manually migrate the current Transaction Recovery Service away from the server while it is still active.

Action: For controlled migration, suspend or shut down the current server first before manually migrating it to a backup server.
Level: 1

Type: WARNING

Impact: JTA

BEA-110213: The activation of Transaction Recovery Service for server [{0}] failed.

Cause: This is an internal error.

Action: Examine the error details, correct the error conditions, and perform the necessary manual migration again if possible. If unsuccessful, My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110400: An error occurred while unregistering Resource Runtime MBean: {0}

Cause: The MBean may have been unregistered previously or there may be an issue with the JMX Administration Server.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110401: Ignoring error in afterCompletion. Object={0}, Exception={1}

Cause: The application-defined javax.transaction.Synchronization callback may have caused an exception.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110402: Unknown state in getStatus(): {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110403: An unexpected exception occurred while processing a transaction during a transaction manager timer event. Exception={0}.

Cause: Refer to the exception information found in the error message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110405: Resource {0} was not assigned to any of these servers: {1}

Cause: The transaction coordinator maintains information regarding where resources are registered among all the servers that are known to the coordinator. The participating resource may have been unregistered or became unavailable prior to attempting the operation. This condition may also occur if the cache belonging to the coordinator was out of date or has not completed initialization at the time the operation was invoked.

Action: Verify the state of resource managers participating in the transaction and retry the operation.
Level: 1

Type: WARNING

Impact: JTA

BEA-110406: Internal error interpreting heuristic status. Expected={0}, Actual={1}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110407: Unknown state in getStatus(): {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-110408: An attempt to add a duplicate transaction to the transaction manager list was ignored.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JTA

BEA-110409: Unable to advertise resource {0}: {1}

Cause: A problem may exist with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110410: Unable to create resource runtime MBean for resource {0}: {1}

Cause: There may be a problem with the JMX Administration Server, or another MBean with this name is already registered with the Administration Server.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110411: Failed to construct local ServerCoordinatorDescriptor: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110412: {0} completed heuristically: {1}.

Cause: The resource manager may have failed, timed out, or detected locking conflicts that prompted it to commit or roll back work for the transaction branch. If the heuristic error was due to a resource manager failure, the resource may not be able to determine if work for the transaction branch was committed, aborted, or both. In this case, the condition is considered a HAZARD or MIXED heuristic.

Action: Check the participants of the transaction should be checked for possible data corruption. The resource manager reporting the heuristic may maintain state information related to the updates involved in the heuristic error. If the JTA ForgetHeuristics configuration parameter is set to false, this information may be preserved in the resource manager. This information might be useful in correcting any data inconsistencies.
Level: 1

Type: ERROR

Impact: JTA

BEA-110414: Illegal State (expected: Prepared or Committing): {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110415: Illegal state. Proceeding with rollback anyway. {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110419: An attempt was made to add an incompatible object as a transaction property: keys must be strings and values must be serializable.

Cause: An attempt was made to add an incompatible object as a transaction property (the class of the key object must be a string and the class of the value object must be serializable).

Action: Change the application to assign the transaction property using a String key and a serializable value.
Level: 1

Type: ERROR

Impact: JTA

BEA-110420: An attempt was made to add an incompatible object as a local transaction property: keys must be String.

Cause: An attempt was made to add an incompatible object as a local transaction property (the key object must be of the class String).

Action: Change the application to add the local property with a String key.
Level: 1

Type: ERROR

Impact: JTA

BEA-110421: Internal error (possibly harmless): Timer method was called on committed transaction {0}.

Cause: This is an internal error, possibly due to a race condition.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110422: Forcibly aborting a transaction found in an unexpected internal state. Details={0}

Cause: This is an internal error.

Action: Check for any data inconsistencies among participating resources. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110423: Abandoning transaction after {0} seconds: {1}

Cause: A resource or participating server may have been unavailable for the duration of the AbandonTimeoutSeconds period.

Action: Check participating resources for heuristic completions and correct any data inconsistencies.
Level: 1

Type: ERROR

Impact: JTA

BEA-110424: An unexpected exception was caught during begin: {0}

Cause: Check the exception detail portion of the log message.

Action: Correct the condition described in the exception detail portion of the log message.
Level: 1

Type: ERROR

Impact: JTA

BEA-110425: Error advertising TransactionManager object: {0}

Cause: There may be a problem with the JNDI provider or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110426: An error occurred while advertising UserTransaction object: {0}

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110427: An error occurred while advertising Coordinator object: {0}

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110428: An error occurred while exporting Coordinator object ID: {0}

Cause: Another remote object may be bound to this object ID.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110429: Error advertising SubCoordinator object: {0}.

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110433: Unable to obtain ownership of the transaction log.

Cause: The Transaction Recovery Service associated with the current server is currently owned by other servers.

Action: Migrate the Transaction Recovery Migratable Service back to the current server before restarting it.
Level: 1

Type: ERROR

Impact: JTA

BEA-110442: An administrative request was made to locally roll back the transaction associated with Xid {0}

Cause: The forced local rollback operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110443: An administrative request was made to locally commit the transaction associated with Xid {0}

Cause: The forced local commit operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110444: An administrative request was made to globally commit the transaction associated with Xid {0}.

Cause: A forced global rollback operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110445: An administrative request was made to globally commit the transaction associated with Xid {0}.

Cause: A forced global commit operation was initiated by an administrative application.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110446: The administrative request to locally roll back the transaction associated with Xid {0} failed because the transaction does not exist.

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110447: The administrative request to locally commit the transaction associated with Xid {0} failed because the transaction does not exist.

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110448: The administrative request to globally roll back the transaction associated with Xid {0} failed because the transaction does not exist.

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110449: The administrative request to globally commit the transaction associated with Xid {0} failed because the transaction does not exist

Cause: The transaction may have completed before the administrative request was made.

Action: No action is required.
Level: 1

Type: ERROR

Impact: JTA

BEA-110450: The administrative request to locally roll back the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110451: The administrative request to globally roll back the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists; the operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110452: The administrative request to locally commit the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110453: The administrative request to globally commit the transaction {0} encountered an error {1}.

Cause: Refer to the exception information in the error message.

Action: Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110454: The administrative request to locally roll back the transaction {0} failed because the transaction is in an invalid state. {1}

Cause: The administrative request is invalid.

Action: Issue a forced commit operation instead to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110455: The administrative request to globally roll back the transaction {0} failed because the transaction is in an invalid state. {1}

Cause: The administrative request is invalid.

Action: Issue a forced commit operation instead to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110456: The administrative request to locally commit the transaction {0} failed because the transaction is in an invalid state. {1}

Cause: The administrative request is invalid.

Action: Issue a forced rollback operation instead to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110458: The administrative request to globally roll back the transaction {0} failed, because the coordinator {1} could not be contacted. {2}

Cause: The coordinating server for the transaction is either not running or is unreachable.

Action: Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110459: The administrative request to globally commit the transaction {0} failed, because the coordinator at {1} could not be contacted. {2}

Cause: The coordinating server for the transaction is either not running or is unreachable.

Action: Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.
Level: 1

Type: ERROR

Impact: JTA

BEA-110460: The administrative request to globally rollback the transaction {0} failed, because the coordinator does not support manual transaction resolution.

Cause: The coordinating server is an older version of WebLogic Server that does not support manual transaction resolution.

Action: Perform local commit operations on all participants that support manual transaction resolution.
Level: 1

Type: ERROR

Impact: JTA

BEA-110462: The administrative request to locally commit the transaction {0} failed, because the transaction has been marked for rollback.

Cause: The transaction has been marked for rollback by an application component.

Action: Attempt to resolve the transaction by using a forced rollback operation instead.
Level: 1

Type: ERROR

Impact: JTA

BEA-110464: The forced commit operation for transaction {0} on resource {1} was not performed, because the resource is busy.

Cause: There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.

Action: Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.
Level: 1

Type: ERROR

Impact: JTA

BEA-110465: The forced rollback operation for transaction {0} on resource {1} was not performed, because the resource is busy

Cause: There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.

Action: Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.
Level: 1

Type: ERROR

Impact: JTA

BEA-110466: The forced commit operation for transaction {0} on resource {1} was not performed because the resource has already been committed.

Cause: The transaction may have completed before the administrative client invoked the commit operation.

Action: No action is required. The transaction has been resolved.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110467: The forced rollback operation for transaction {0} on resource {1} was not performed because the resource has already been rolled back.

Cause: The transaction may have completed before the administrative client invoked the rollback operation.

Action: No action is required. The transaction has been resolved.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110468: The forced commit operation for transaction {0} on resource {1} encountered an error. {2}

Cause: Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action: Determine if administrative operations are required in the resource to resolve the transaction branch.
Level: 1

Type: ERROR

Impact: JTA

BEA-110469: The forced rollback operation for transaction {0} on resource {1} encountered an error. {2}

Cause: Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action: Determine if administrative operations are required in the resource to resolve the transaction branch.
Level: 1

Type: ERROR

Impact: JTA

BEA-110470: User [{0}] is not authorized to invoke a forced global rollback.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110471: User [{0}] is not authorized to invoke a forced global commit.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110472: User [{0}] is not authorized to invoke a forced local rollback.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110473: User [{0}] is not authorized to invoke a forced local commit.

Cause: The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.

Action: Authenticate using an identity with adequate privileges prior to invoking the operation.
Level: 1

Type: ERROR

Impact: JTA

BEA-110474: Unable to advertise non-XA resource {0}: {1}

Cause: There may be a problem with the JNDI provider, or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110475: User [{0}] is not authorized to invoke commit on a non-XA resource transaction branch.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110476: The server has detected pending transactions during graceful shutdown. The server will wait for the pending transactions to complete before suspending the RMI service. A forced shutdown command can be issued to shut down the server immediately.

Cause: The server has detected pending transactions during graceful shutdown.

Action: No action is required. Use a forced shutdown command to ignore inflight work and shut down the server immediately.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110477: The unregisterResource operation for resource {0} timed out after {1} seconds.

Cause: It was requested that the specified resource be unregistered from the transaction manager and transactions that refer to the resource still exist on the server.

Action: Monitor inflight transactions to determine if there are still active transactions that depend on the unregistered resource. Options include using the Administration Console to manually resolve dependent transactions, or the resource may be redeployed for a sufficient period to allow the dependent transactions to complete.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110478: One-phase transaction [{1}] is in an unknown state for logging resource [{0}]. The transaction operations either all rolled back, or all committed, or are blocked. Transaction detail: [{2}]. Root cause: [{3}].

Cause: If the logging last resource is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.

Action: Examine the exception caused by the LLR resource to determine the root cause of the problem.
Level: 1

Type: WARNING

Impact: JTA

BEA-110479: Two-phase transaction [{1}], with logging resource [{0}], is an unknown state. The transaction manager will periodically retry determining the state of the transaction every [{3}] seconds. When the state is determined, the remaining resources in the transaction will be either rolled back or committed accordingly. Transaction detail: [{2}]. Root cause: [{4}].

Cause: If the logging last resource is a database, there are a number of possible root causes. Among them are: the database may have shutdown or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potention dead-lock condition introduced by application operations within the local commit.

Action: Examine the exception caused by the LLR resource to determine the root cause of the problem. Note that no action may be required as the transaction manager will periodically retry the transaction until it can automatically rollback or commit accordingly.
Level: 1

Type: WARNING

Impact: JTA

BEA-110480: The transaction manager is completing logging resource [{0}] transaction [{1}]. The transaction, which was previously in an unknown state, is now resolved and in the [{2,choice,0#rollback|1#commit}] state.

Cause: See previous log messages for the same transaction to determine the root cause.

Action: See previous log messages for the same transaction to determine the root cause.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110482: A logging last resource (LLR) failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}

Cause: If the logging last resource is a JDBC LLR connection, there are a number of possible root causes. Among them are: the database may have shut down or crashed, the database connection may have failed during boot, or the database connection may have incorrect database permissions.

Action: Examine the root exception thrown by the LLR to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-110483: The JTA health state has changed from {0} to {1}.

Cause: An internal event has caused the JTA health state to transition to the normal state. Refer to previous health log entries for the conditions that have been corrected to trigger the state change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-110484: The JTA health state has changed from {0} to {1} with reason codes: {2}.

Cause: Refer to the message body for information regarding the events that caused the health change.

Action: Refer to the message body for the cause of the JTA state change and take the appropriate action to correct the exception condition.
Level: 1

Type: WARNING

Impact: JTA

BEA-110485: The JTA health state has changed from {0} to {1} with reason codes: {2}.

Cause: Refer to the message body for information regarding the events that caused the health change.

Action: Refer to the message body for the cause of the JTA state change and take the appropriate action to correct the exception condition.
Level: 1

Type: ERROR

Impact: JTA

BEA-110486: Transaction {0} cannot complete commit processing because resource [{1}] is unavailable. The transaction will be abandoned after {2} seconds unless all resources acknowledge the commit decision.

Cause: The resource may have been undeployed or is unresponsive and declared unavailable.

Action: Check for related server log messages that may provide additional details regarding the state of the resource. If the resource is undeployed, deploy the resource or the application module if the resource is application scoped. If a problem exists with the resource manager, correct the problem and redeploy the resource.
Level: 1

Type: WARNING

Impact: JTA

BEA-110487: Transaction {0} cannot complete rollback processing because the pending resource [{1}] is unavailable. The transaction will be abandoned after {2} seconds unless all resources acknowledge the rollback decision.

Cause: The resource may have been undeployed or is unresponsive and declared unavailable.

Action: Check for related server log messages that may provide additional detail regarding the state of the resource. If the resource is undeployed, deploy the resource or the application module if the resource is application scoped. If a problem exists with the resource manager, correct the problem and redeploy the resource.
Level: 1

Type: WARNING

Impact: JTA

BEA-110488: The LLR resource(s) {0} are not available and may contain transaction commit records required for recovery processing. Recovery of XA resources will not occur until these resources are deployed.

Cause: Prior to server restart, one or more global transactions were processed that had a LLR participant and may not have completed before the server was restarted. This potentially left a commit record in a LLR resource and prepared resource transaction branches that are awaiting a commit or rollback decision from the coordinator.

Action: Redeploy the specified LLR resources, wait for all in progress transactions to complete, and shut down the server gracefully.
Level: 1

Type: WARNING

Impact: JTA

BEA-110490: User [{0}] is not authorized to invoke Commit on a Coordinator.

Cause: This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110491: User [{0}] is not authorized to invoke AckPrePrepare on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110492: User [{0}] is not authorized to invoke CheckStatus on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110493: User [{0}] is not authorized to invoke AckCommit on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110494: User [{0}] is not authorized to invoke NakCommit on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110495: User [{0}] is not authorized to invoke AckRollback on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110496: User [{0}] is not authorized to invoke NakRollback on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110500: User [{0}] is not authorized to invoke GetSubCoordinatorInfo on a SubCoordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110501: User [{0}] is not authorized to invoke GetProperties on a SubCoordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110502: User [{0}] is not authorized to invoke Recover on a SubCoordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-110503: The migrator (the Administration Server for manual JTA migration policy or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if the TRS of {0} has been migrated to a backup server and the backup server is accessing the TLOG of {0}. More safety can be achieved by setting isStrictOwnershipCheck to [true].

Cause: The Administration Server or Singleton Master is not running or cannot be reached.

Action: Start Administration Server or Singleton Master before starting any Managed Server in the cluster.
Level: 1

Type: WARNING

Impact: JTA

BEA-110504: There was an error advertising TransactionSynchronizationRegistry object: {0}.

Cause: There may be a problem with the JNDI provider or another object is already bound to this context.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JTA

BEA-110505: An attempt was made to set an invalid TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY for transaction property: keys must be number and values must be between -1 and max value of integer.

Cause: See the message detail.

Action: Change the application to assign the proper TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY property value.
Level: 1

Type: ERROR

Impact: JTA

BEA-111001: The Transaction Manager is being started in standalone mode and will not be able to participate in distributed transactions.

Cause: There are no suitable RMI or JNDI providers configured.

Action: Configure the appropriate RMI and JNDI context providers.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111002: The Transaction Manager is being started in distributed mode.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111003: An error occurred while creating the transaction log persistent store: {1}.

Cause: Refer to the associated exception.

Action:
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111004: Transaction could not set CoordinatorURL to use AdminChannel downgrading {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-111005: An in-progress XA operation for transaction {0} on resource {1} could not complete within {2} seconds, or was interrupted. Allowing subsequent calls to proceed.

Cause: The call to the resource manager may have been affected by a server or network problem and could have been interrupted.

Action: Verify that the resource manager is functioning properly and accessible.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111006: Transaction could not set CoordinatorURL to use SSL URL downgrading {0}

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: JTA

BEA-111007: The commit operation for one-phase transaction {0} on resource {1} encountered an error. {2}

Cause: Refer to the resource exception in the error message and any appropriate resource-specific error logs.

Action: Determine if administrative operations are required in the resource to resolve the transaction branch.
Level: 1

Type: ERROR

Impact: JTA

BEA-111008: Transaction Log failed during initialization. The server cannot boot unless Transaction Log initialize. Failing reason: {0}

Cause: An internal error occurred.

Action: Determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111009: activateDeployments failed during initialization. Failing reason: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111010: SetPrimaryStore failed. Failing reason: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111011: A Transaction Log PrimaryStore failed during initialization. The server cannot boot unless configured Transaction Log Primary Store initialize. Failing reason: {0}

Cause: An internal error occurred.

Action: Examine the root exception thrown by the Transaction Log Primary Store to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111012: SetPrimaryStore close failed when retry. Failing reason: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111013: Recover JDBCStore init store exception: {0}

Cause: An internal error occurred.

Action: Contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTA

BEA-111014: There is a naming conflict for resource = [{0}]. This resource is being registered by this server and has already been registered in: [{1}].

Cause: This resource is trying to be registered as a NonXAResource but was already registered as an XAResource.

Action: Correct the configuration either by making the resource name unique or by making the resource consistently either an XAResource or a NonXAResource.
Level: 1

Type: ERROR

Impact: JTA

BEA-111015: The commit operation for transaction {0} timed out after {1} seconds.

Cause: The application may take longer than the time that is specified in timeout-seconds in the JTA parameter before issuing the commit.

Action: Increase the transaction timeout-seconds in the JTA parameter or tuning application.
Level: 1

Type: NOTIFICATION

Impact: JTA

BEA-111016: Recovery is not possible as determiner resource can not be obtained {0}.

Cause: Determiner resource may have been removed or is otherwise unobtainable.

Action: Insure determiner resource can be obtained and has not been removed.
Level: 1

Type: ERROR

Impact: JTA

BEA-114089: User [{0}] is not authorized to invoke ackPrepare on a Coordinator.

Cause: This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.

Action: Verify that the client software is not directly invoking an internal WebLogic Server system object.
Level: 1

Type: ERROR

Impact: JTA

BEA-119000: One-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.

Cause: If the LLR is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.

Action: Examine the root exception generated by the LLR to determine the root cause of the problem.
Level: 1

Type: WARNING

Impact: JTAExceptions

BEA-119001: Two-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.

Cause: If the LLR is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.

Action: Examine the root exception generated by the LLR resource to determine the root cause of the problem.
Level: 1

Type: WARNING

Impact: JTAExceptions

BEA-119002: A LLR failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}

Cause: If the LLR is a JDBC LLR connection, there are a number of possible root causes. Among them are: the database may have shut down or crashed, the database connection may have failed during boot, or the database connection may have incorrect database permissions.

Action: Examine the root exception generated by the LLR resource to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTAExceptions

BEA-119003: LLR [{0}] failed during initialization, as one of its records is corrupted. Failure reason: {1}

Cause: The cause is unknown, but could be possible disk corruption.

Action: Examine the root exception generated by the LLR to determine the root cause of the problem. Possible solutions are: restore LLR resource tables from backup, delete the failing LLR table (which risks producing heuristic hazards), or contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: JTAExceptions

BEA-119004: The user-preferred server of JTAMigratableTargetMBean [{0}] cannot be set to [{1}].

Cause: The value of the user-preferred server is invalid. It must be [{0}].

Action: Change the value of the user-preferred server of JTAMigratableTargetMBean [{0}] from [{1}] to [{0}].
Level: 1

Type: ERROR

Impact: JTAExceptions

BEA-119005: JTA subsystem failed. A forced shutdown of the server was done because the server is in automatic JTA migration mode.

Cause: The JTA subsystem failed.

Action: JTA Transaction Recovery Service will be automatically migrated to back up the server.
Level: 1

Type: ERROR

Impact: JTAExceptions

BEA-119006: A Transaction Log Primary Store failed during initialization. The server cannot boot unless the configured Transaction Log Primary Store initialize. Failing reason: {0}

Cause: This is an internal error.

Action: Examine the root exception generated by the Transaction Log Primary Store to determine the root cause of the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: JTAExceptions

BEA-130000: Insertion of {0} into XML entity cache rejected. Entity size, {1}, exceeded cache size, {2}.

Cause: The cache may be too small or a specific item might be very large. The worst case is that this indicates a denial of service attack.

Action: No action is required. However, performance will be best if items are cached.
Level: 1

Type: WARNING

Impact: XML

BEA-130001: Entity cache appears to be broken. This impacts the performance of XML parsing.

Cause: Unknown

Action: No action is required. However, performance will increase if items are cached. Also the cache provides a backup in the case of a network failure. While the cache is not operating, this backup is not in effect.
Level: 1

Type: WARNING

Impact: XML

BEA-130002: The entity that was just put in the cache cannot be retrieved: "{0}". Timeout may be too short.

Cause: Usually this indicates that the entity timeout was set to a very small value. Otherwise, there is some unknown problem with the cache module itself.

Action: No action is required, but XML parse performance will be impacted. Also, there is no cached copy to act as a backup in the event of a network failure.
Level: 1

Type: WARNING

Impact: XML

BEA-130003: Could not instantiate the specified factory class. {0}.

Cause: The class name of the factory was not correct or it was not in the CLASSPATH.

Action: Check the CLASSPATH or verify the Administration Console entry or MBean value.
Level: 1

Type: ERROR

Impact: XML

BEA-130006: XML cache warning for registry {0}: entry rejection due to entry being larger than the cache memory size. entry: {1} Entry memory size: {2}

Cause: The entry is larger than the cache.

Action: No action is required unless the item should be cached next time. If so, increase the cache memory size.
Level: 1

Type: WARNING

Impact: XML

BEA-130007: XML cache event: memory purge of {0} entries of combined size {1}. Current memory usage is {2} bytes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130008: XML cache event: disk purge of {0} entries of combined size {1}. Current disk usage is {2} bytes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130009: XML cache warning for registry {0}: entry persist attempt rejected due to entry being larger than the cache disk size. Status changed to transient. entry: {1} entry disk size: {2}

Cause: The size of the entry on the disk exceeds the allocated disk space.

Action: No action is required. If the entry should be persisted next time, increase the disk size of the cache.
Level: 1

Type: WARNING

Impact: XML

BEA-130010: XML cache event for registry {0}: entry added. entry: {1}, entry memory size: {2}, storage type: {3}, current memory usage (bytes): {4}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130011: XML cache event for registry {0}: entry deleted. entry: {1}, entry memory size: {2}, entry disk size: {3}, current memory usage (bytes): {4}, current disk usage (bytes): {5}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130012: XML cache event for registry {0}: entry persisted. entry: {1}, entry disk size: {2}, current disk usage (bytes): {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130013: XML cache event for registry {0}: entry loaded. entry: {1}, entry memory size: {2}, current memory usage (bytes): {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130014: XML cache event: statistics checkpointed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130015: XML cache event: cache created. current memory usage (bytes): {0}, current disk usage (bytes): {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130016: XML cache event: cache loaded. Current memory usage (bytes): {0}, current disk usage (bytes): {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130017: XML cache event: cache closed. current disk usage (bytes): {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130018: XML cache error: cache file {0} is corrupted. Creating new cache from scratch.

Cause: The cache file was corrupted. This normally does not occur.

Action: The server should be restarted. If a backup of the cache files exists, restore the cache files, and then restart the server.
Level: 1

Type: ERROR

Impact: XML

BEA-130019: XML cache error for registry {0}: entry file {1} is corrupted. Removing from cache. entry: {2}

Cause: The cache file was corrupted. This normally does not occur.

Action: The server should be restarted. The entry will be re-cached on the next access of the server.
Level: 1

Type: ERROR

Impact: XML

BEA-130020: XML cache error: statistics file {0} is corrupted, reinitializing. Previous statistics are lost.

Cause: The cache file was corrupted. This normally does not occur.

Action: The server should be restarted.
Level: 1

Type: ERROR

Impact: XML

BEA-130021: XML cache error for registry {0}: entry file {1} cannot be written. Status changed to transient. entry: {2}

Cause: This is often a file protection issue.

Action: Determine why the file cannot be saved and make the appropriate adjustments.
Level: 1

Type: ERROR

Impact: XML

BEA-130022: XML cache error: cache file {0} cannot be written.

Cause: This is often a file protection issue.

Action: Determine why the file cannot be saved and make the appropriate adjustments.
Level: 1

Type: ERROR

Impact: XML

BEA-130023: XML cache error: statistics file {0} cannot be written. There are no futher cache statistics for this session.

Cause: This is often a file protection issue.

Action: Determine why the file cannot be saved and make the appropriate adjustments.
Level: 1

Type: ERROR

Impact: XML

BEA-130024: XML cache error for registry {0}: out of memory loading entry. Entry removed from cache. entry: {1}, file: {2}

Cause: The entry might be unusually large or perhaps the JVM heap size is too small.

Action: Check the size of the rejected entry. If entries of that size need to be handled, increase the heap size.
Level: 1

Type: ERROR

Impact: XML

BEA-130025: XML cache error: out of memory loading cache. Cache not opened. file: {0}

Cause: The cache file is not large, so memory usage is almost full.

Action: Increase the JVM heap size.
Level: 1

Type: ERROR

Impact: XML

BEA-130026: XML cache error: out of memory loading statistics. File: {0}

Cause: The cache file is not large, so memory usage is almost full.

Action: Increase the JVM heap size.
Level: 1

Type: ERROR

Impact: XML

BEA-130027: XML cache warning: the requested memory size of the XML cache, {0}, exceeds the available memory, {1}.

Cause: Either the provided parameters are not in sync with the usage, or a lot of the available memory is being used.

Action: Reduce the cache size or increase the JVM heap size. If there should be more available memory, determine what is using all of the available memory.
Level: 1

Type: WARNING

Impact: XML

BEA-130028: XML cache warning: the requested memory size of the XML cache, {0}, is a large percentage of the available memory, {1}.

Cause: Either the provided parameters are not in sync with the usage, or something is using a lot of the available memory.

Action: Reduce the cache size or increase the JVM heap size. If there should be more available memory, determine what is using all of the available memory.
Level: 1

Type: WARNING

Impact: XML

BEA-130029: XML cache error: an unexpected error occurred in the XML cache. {0}

Cause: The cause is unknown.

Action: Refer to the associated text at the end of the message and contact My Oracle Support for help resolving the error.
Level: 1

Type: ERROR

Impact: XML

BEA-130030: XML cache error for registry {0}: the file, {1}, representing entry {2} cannot be read.

Cause: The file is read-protected.

Action: Check the access rights of the file and make the appropriate changes.
Level: 1

Type: ERROR

Impact: XML

BEA-130031: XML cache error: the cache file, {0}, cannot be read.

Cause: The file is read-protected.

Action: Check the access rights of the file and make the appropriate changes.
Level: 1

Type: ERROR

Impact: XML

BEA-130032: XML cache error: statistics file {0} cannot be read.

Cause: The file is read-protected.

Action: Check the access rights of the file and make the appropriate changes.
Level: 1

Type: ERROR

Impact: XML

BEA-130033: Parser or DocumentBuilder cannot be created to satisfy the configuration requested. {0}

Cause: The configuration was invalid.

Action: Verify that the factory that creates the parser and the properties or features set on this parser are configured properly.
Level: 1

Type: ERROR

Impact: XML

BEA-130034: Failed to parse the given XML document. {0}

Cause: An error occurred in the structure of the XML document.

Action: Verify the XML syntax of the document.
Level: 1

Type: ERROR

Impact: XML

BEA-130035: Failed to open XML document. {0}

Cause: The file does not exist.

Action: Check the file name, the file location and its associated permissions.
Level: 1

Type: ERROR

Impact: XML

BEA-130036: Initializing XMLRegistry

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-130037: The stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: XML

BEA-140008: Internal error. Failed to save configuration changes to the configuration repository - {0}.

Cause: The config.xml file is either write-protected, or the user that started the server is not authorized to write to this file or directory.

Action: Ensure that the operating system user who starts the server has authorization to write to the config.xml file and that the config.xml file is not write-protected.
Level: 1

Type: ERROR

Impact: Management

BEA-140013: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141009: Error occurred in the file distribution servlet while processing the request type "{0}", {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141010: Error occurred in the file distribution servlet and received an unacceptable request of type "{0}".

Cause: An invalid request was made to the file distribution servlet.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: Management

BEA-141011: The file distribution servlet failed to distribute the security properties file, because the file was not found at the configured location: {0}.

Cause: The identified file was not available to the Administration Server.

Action: Verify the configuration of this file.
Level: 1

Type: ERROR

Impact: Management

BEA-141021: The cluster property {0} was ignored because the server is not part of a cluster.

Cause: A non-applicable cluster property was specified at server startup.

Action: Modify the configuration to identify that this Managed Server is, in fact, a member of a cluster, or eliminate the specification of the cluster property from the start command.
Level: 1

Type: WARNING

Impact: Management

BEA-141023: An error occurred while setting the attribute value in the MBean proxy {0}, method {1} with value {2} ({3}).

Cause: An invalid attribute value was specified.

Action: Verify that the provided attribute value (specified either in the configuration or through a dynamic setting) is correct.
Level: 1

Type: ERROR

Impact: Management

BEA-141051: The operation failed with message: {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the details of the provided error message.
Level: 1

Type: ERROR

Impact: Management

BEA-141052: The auto deployment poller has started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141053: The auto deployment poller has not started for the production server.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141062: The user does not have permission to perform {1} operation on MBean {0}. Method = {3}, attribute = {2}

Cause: No access control list (ACL) permissions are defined for the user to complete this operation.

Action: The system administrator must add ACL permissions in order for the user to perform this operation.
Level: 1

Type: ERROR

Impact: Management

BEA-141063: The user does not have permission to perform {1} operation on MBean {0}. Method: {2}.

Cause: The user has no defined access control list (ACL) to perform this MBean operation.

Action: The system administrator must define permissions in order for the user to perform this MBean operation.
Level: 1

Type: ERROR

Impact: Management

BEA-141071: The file distribution servlet failed to distribute the embedded LDAP initial replica data file because the file was not found at the configured location: {0}.

Cause: This is an internal error that should not occur during normal operation.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Management

BEA-141073: Migration task ({0}) - {1}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141076: No module with URI ({1}) was found in ({0}).

Cause: The application is potentially misconfigured relative to this module.

Action: Verify that the application archive and its descriptors are correctly configured.
Level: 1

Type: ERROR

Impact: Management

BEA-141077: An error occurred during the parsing of descriptors for {0}. Exception {1} occurred.

Cause: Refer to the exception details for the exact cause of this parsing error.

Action: Take action based upon provided exception details to either correct the identified component or its descriptors.
Level: 1

Type: ERROR

Impact: Management

BEA-141078: A descriptor initialization error occurred for module {0} in EAR file {1}. Creation of the temporary file {2} failed.

Cause: The extraction of the EAR file failed due to an I/O error. See the logged for details.

Action: Ensure that the file referred to in the exception can be created, and there is no directory by the same name.
Level: 1

Type: ERROR

Impact: Management

BEA-141081: The file distribution servlet failed to distribute the embedded LDAP initial replica data file due to the following error: {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141086: An error occurred while setting a value for {0}.

Cause: The specified command line property provided an invalid value for attribute {0}.

Action: Verify that the specified command line property provides a valid attribute value.
Level: 1

Type: ERROR

Impact: Management

BEA-141087: Property: {0} is not a recognized MBean attribute or special property used for management. It is most likely being used by subsystems and will continue to work as expected if it is a supported option.

Cause: An unrecognized property has been specified on the start command.

Action: Eliminate the invalid properties from the start command.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141089: Starting the server based on the WebLogic Server 6.x configuration directory structure.

Cause: The startup directory does not contain the config.xml configuration file. The file was located in the config/domain directory.

Action: Start the server from the directory that contains the domain configuration file.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141102: Subject: {0} does not have access to perform {1} actions.

Cause: Either the named subject is not allowed to perform this action and is appropriately being denied this access, or the named subject should be allowed to perform this action and the role membership of the subject is not properly configured.

Action: Contact the system administrator to modify role definitions.
Level: 1

Type: ERROR

Impact: Management

BEA-141107: Version: {0}

Cause: This is normal system initialization processing.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141124: An invalid system property was specified while booting the server {0}.

Cause: The server might have been started using an invalid system property. For example, starting the server using java -D weblogic.Server will generate this exception.

Action: Correct the invalid system property.
Level: 1

Type: ERROR

Impact: Management

BEA-141126: The configuration file {0} is read-only.

Cause: This occurs when the write permissions on the file are not set to allow the user that booted the server to write to the config.xml file. Write access is often intentionally denied in production environments.

Action: In many cases, write access is intentionally denied. In such cases, this is just an informational message. If the file needs to be writable, change the permissions on the file or ask the system administrator to do so.
Level: 1

Type: WARNING

Impact: Management

BEA-141133: The Name attribute cannot be modified after the MBean {0} has been created.

Cause: The Name attribute is being modified by a setName operation.

Action: Specify the name of the MBean during creation.
Level: 1

Type: ERROR

Impact: Management

BEA-141145: An attempt was made to connect to the Administration Server without credentials.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. It is most likely that an old version of a utility is being used that is not properly supplying these credentials. It is also possible that this represents an attempt to compromise the server.

Action: Determine the source of the request. If it is a legitimate request, ensure that updated software is being used which properly supplies the credentials. It is also important to restrict access to the Administration Server. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
Level: 1

Type: ERROR

Impact: Management

BEA-141146: An attempt was made to connect to the Administration Server by the user {0} and a password which does not match.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities.

Action: Determine the source of the request. If it is a legitimate request, ensure that updated software which properly supplies the credentials is in use. It is also important to restrict access to the Administration Server. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
Level: 1

Type: ERROR

Impact: Management

BEA-141147: An attempt was made to upload a file to the Administration Server by the unauthorized user {0}.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the user specified is not configured with the authorization to upload files.

Action: To enable the user to upload files to the Administration Server, it is necessary that the user be added to the administrator or deployer role. Alternatively, it is possible to authorize a user specifically for "FileUpload". Consult the WebLogic Server documentation for instructions on how to do this.
Level: 1

Type: ERROR

Impact: Management

BEA-141148: An invalid attempt was made to download a {1} resource from the Administration Server by the unauthorized user {0}.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the credentials of the user that is being used to boot the Managed Server are used to authorize the request. That user is not authorized to access files of the type {1}.

Action: Ensure that the proper credentials are being used to initiate the connection. In most cases, this involves ensuring that the credentials being used to boot the Managed Server are properly authorized on the Administration Server.
Level: 1

Type: ERROR

Impact: Management

BEA-141149: An invalid attempt was made to connect to the Administration Server with a salt of {0} and a signature of {1}, likely due to private key mismatch.

Cause: The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities.

Action: Determine the source of the request and ensure that the Managed Server and the Administration Server share the same security credential. That credential is stored in the domain configuration and distributed at server startup. In this case, where the Managed Server is booted using a configuration that is different from that of the Administration Server, perhaps in Managed Server independence mode. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
Level: 1

Type: ERROR

Impact: Management

BEA-141151: The Administration Server could not be reached at {0}.

Cause: The Administration Server is not available at the specified URL or the URL is not specified in the correct format, such as http://myhost:7001.

Action: Ensure that the Administration Server is running at the specified host and port. Check that the URL is specified in the correct format. The URL is specified by the protocol://host:port, for example http://myhost:7001.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141187: Java system properties are defined as follows: {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141190: The commit phase of the configuration update failed with an exception.

Cause: An exception occurred during the commit of the update.

Action: Retry the activate. Take action based upon the provided exception details.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141191: The prepare phase of the configuration update failed with an exception.

Cause: An exception occurred during the prepare of the update.

Action: Ensure that the update is valid. Take action based upon the provided exception details, make any required changes, change the changes, and retry the activate.
Level: 1

Type: WARNING

Impact: Management

BEA-141192: The read of the edit lock file failed with an exception.

Cause: An exception occurred during the read of the edit lock file.

Action: Take action based upon the provided exception details. Try to get the edit lock again.
Level: 1

Type: ERROR

Impact: Management

BEA-141193: The write of the edit lock file failed with an exception.

Cause: An exception occurred during the write of the edit lock file.

Action: Take action based upon the provided exception details. Try to get the edit lock again.
Level: 1

Type: ERROR

Impact: Management

BEA-141194: The registration of the configuration subsystem with the deployment subsystem failed with an exception.

Cause: An exception occurred during the registration of the configuration subsystem.

Action: Take action based upon the provided exception details. Restart the server.
Level: 1

Type: ERROR

Impact: Management

BEA-141196: The Managed Server could not update the configuration files during the registration with the deployment service. The update failed due to an exception.

Cause: An exception occurred during the update of configuration files.

Action: Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
Level: 1

Type: ERROR

Impact: Management

BEA-141197: The deployment of {0} failed.

Cause: An exception occurred during a resource deployment.

Action: Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
Level: 1

Type: WARNING

Impact: Management

BEA-141198: The undeployment of {0} failed.

Cause: An exception occurred during a resource undeployment.

Action: Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
Level: 1

Type: WARNING

Impact: Management

BEA-141199: In the compatibility MBean server, the operation {1} on the MBean {0} modified the configuration without starting an edit session and activating the changes.

Cause: The impact information was incorrect for the MBean operation.

Action: Contact My Oracle Support as this is an internal coding error that should not occur.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141200: Detected a domain that was created from an earlier release of WebLogic Server. The domain will be upgraded to the current {0} release.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141201: Unable to modify the configuration using the compatibility MBean server, as other changes are pending. Activate the pending changes before modifying the configuration with the compatibility MBean server.

Cause: The configuration was not modified because pending changes were present.

Action: Activate the changes before using the compatibility server.
Level: 1

Type: ERROR

Impact: Management

BEA-141202: The addition of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141203: The addition of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141204: The addition of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141205: The removal of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141206: The removal of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141207: The removal of the bean {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141208: The modification of the property {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141209: The modification of the property {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141210: The modification of the property {0} failed during the activate phase because of {1}

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: WARNING

Impact: Management

BEA-141211: An attempt to initialize the property {0} failed because of {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141212: An attempt to initialize the property {0} failed because of {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141213: An attempt to initialize the property {0} failed because of {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141214: The add of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141215: The add of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141216: The add of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141217: The removal of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141218: The removal of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141219: The removal of the bean {0} failed. The encountered exception was {1}

Cause: See the exception message for more information on the cause of this error.

Action: The exception message may have more information about the action to take.
Level: 1

Type: ERROR

Impact: Management

BEA-141220: A required class was not found while upgrading the domain. This could be possible if the security provider JAR files were not upgraded to conform with WebLogic Server version 9.0. Upgrade these providers using java weblogic.Upgrade -type securityproviders.

Cause: The security provider JAR files were not upgraded to conform with new WebLogic Server 9.0 classes.

Action: Run the upgrade tool to upgrade the provider.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141221: An error occurred while performing an undo of unactivated changes in the compatibility MBean server: {0}.

Cause: See the exception message for more information.

Action: Check the exception message for more detail.
Level: 1

Type: ERROR

Impact: Management

BEA-141223: The server name {0} specified with -Dweblogic.Name does not exist. The configuration includes the following servers {1}.

Cause: The -Dweblogic.Name command line property specifies a server that does not exist in the configuration.

Action: Check the configuration for the list of configured servers.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141224: The Administration Server is not reachable.

Cause: This could be a network issue.

Action: Check the status of the Administration Server.
Level: 1

Type: WARNING

Impact: Management

BEA-141225: The delete of pending directory file {0} failed.

Cause: An error occurred while deleting the file.

Action: Ensure that no processes have the file open for write.
Level: 1

Type: ERROR

Impact: Management

BEA-141226: An invalid deployment service prepare callback with ID {0} was received.

Cause: This indicates an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Management

BEA-141227: Making a backup copy of the configuration at {0}.

Cause: This happens during certain server lifecycle transitions and during configuration changes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141228: An attempt to back up the configuration to {0} failed with {1}.

Cause: See the message text for the exception message.

Action: Check the exception information included in the message text.
Level: 1

Type: ERROR

Impact: Management

BEA-141229: The upgrade process has been canceled by the user. The server process will not be started.

Cause: The server startup cannot proceed without upgrading the domain.

Action: Upgrade the domain, and then start the server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141230: Could not locate the descriptor file for System Resource: {0}.

Cause: The descriptor file could not be located in the specified path.

Action: Ensure that the descriptor file is in the appropriate location.
Level: 1

Type: WARNING

Impact: Management

BEA-141231: Could not register the JSR object: {0}.

Cause: There are many possible causes for this warning.

Action: Look at the stack trace and take appropriate action.
Level: 1

Type: WARNING

Impact: Management

BEA-141232: Could not decrypt the {1} attribute value of {2} from the file {0}. The edit session has been canceled. The decryption failed with the exception {3}.

Cause: An invalid encrypted value was found in the edit lock file.

Action: Start a new edit session.
Level: 1

Type: ERROR

Impact: Management

BEA-141233: Could not decrypt the edit lock file {0}. The edit session has been canceled. The decryption failed with the exception {1}.

Cause: An exception occurred when decrypting the edit lock file.

Action: Start a new edit session.
Level: 1

Type: ERROR

Impact: Management

BEA-141234: A rollback of a dynamic change failed. The message for the failure is "{0}". The cause of the exception is "{1}".

Cause: See the message body for the cause.

Action: Look at the possible causes of this error. The cause may give some indication of the possible actions to take.
Level: 1

Type: WARNING

Impact: Management

BEA-141237: Extraneous text found in the config.xml file: {0}.

Cause: This is generally caused by mistakes in hand-edited config.xml files. The config.xml file is a valid XML document, however, the extraneous text is not related to any MBean attributes.

Action: Review the config.xml file for mistakes, such as extra delimeters near the text listed in the error message.
Level: 1

Type: WARNING

Impact: Management

BEA-141238: A non-dynamic change has been made which affects the server {0}. This server must be rebooted in order to consume this change.

Cause: This happens when one or more of the changes made to the configuration affect non-dynamic settings. When this occurs, the affected Managed Servers are determined, and those servers are not updated when the change is activated. In order to consume the change, these servers must be rebooted.

Action: Reboot the named server.
Level: 1

Type: WARNING

Impact: Management

BEA-141239: The non-dynamic attribute {1} on {0} has been changed. This may require redeploying or rebooting configured entities.

Cause: This happens when one or more of the changes made to the configuration affect non-dynamic settings.

Action: The required action, if any, will be indicated in a later log message.
Level: 1

Type: WARNING

Impact: Management

BEA-141240: Found a version {0} config.cml file, but expected a version 9 or higher config.xml file. This could happen if an attempt to boot was made from the config directory rather than the domain root.

Cause: This could happen if an attempt was made to boot from the config directory rather than the domain root. Otherwise, the configuration could be corrupted.

Action: Ensure that the config.xml file is not corrupted and that the boot is attempted from the domain root.
Level: 1

Type: ERROR

Impact: Management

BEA-141241: Found a version {0} config.xml file, but expected a pre-version 9 config.xml file. This could happen if an attempt was made to boot from the config directory rather than the domain root.

Cause: This could happen if a 9.x config.xml file was put in the top level, rather than in the config directory.

Action: Ensure that the config.xml file is in the correct location in the domain.
Level: 1

Type: ERROR

Impact: Management

BEA-141242: Invalid configuration version found at {1} version = {0}.

Cause: WebLogic Server found a config.xml file with a version that does not match any known version of the product.

Action: Ensure that the version string in the config.xml file is valid.
Level: 1

Type: ERROR

Impact: Management

BEA-141243: The property {0} in element {1} has been deprecated in version {2} - {3}.

Cause: The config.xml file contained elements that have been deprecated.

Action: Replace or remove the deprecated configuration artifacts.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141244: Schema validation errors while parsing {0} - {1}.

Cause: The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.

Action: See the error details for more information on the validation problem.
Level: 1

Type: ERROR

Impact: Management

BEA-141245: Schema validation error in {0}. See the log for details. Schema validation can be disabled by starting the server with the command line option: {1}.

Cause: The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.

Action: See the error details for more information on the validation problem.
Level: 1

Type: ERROR

Impact: Management

BEA-141246: The configuration directory {0} does not exist.

Cause: The server was booted from a directory that does not contain a configuration directory.

Action: Ensure that the server is booted from a valid domain directory.
Level: 1

Type: ERROR

Impact: Management

BEA-141247: The configuration directory {0} does not exist, and the Administration Server is not available.

Cause: The configuration directory is missing and the Administration Server is not available to download a copy. In this case, the Managed Server cannot boot.

Action: Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
Level: 1

Type: ERROR

Impact: Management

BEA-141248: The configuration directory {0} is missing the file {1}.

Cause: The server was booted from a directory that does not contain a valid domain configuration.

Action: Ensure that the server is booted from a valid domain directory.
Level: 1

Type: ERROR

Impact: Management

BEA-141249: The configuration directory {0} is missing the file {1}, and the Administration Server is not available to download it.

Cause: The server was booted from a directory that does not contain a valid configuration, and the Administration Server is unavailable to download the current configuration files.

Action: Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
Level: 1

Type: ERROR

Impact: Management

BEA-141251: The attribute {1} from the element {0} was introduced in version 9.0.0.0 or later and is not valid in a pre-9.0 config.xml file.

Cause: An attribute that was introduced in release 9.0 or later was found in a pre-9.0 config.xml file.

Action: Verify that the upgrade process correctly handles the named elements by reviewing the upgraded configuration files.
Level: 1

Type: WARNING

Impact: Management

BEA-141252: The domain version {0} is greater than the release version {1} of this server.

Cause: The DomainVersion in the configuration used by the Administration Server is not compatible with the release version of this Managed Server.

Action: Update the WebLogic Server installation for this server.
Level: 1

Type: ERROR

Impact: Management

BEA-141253: An error occurred while loading the configuration translator {0} : {1}.

Cause: The message includes the specific cause.

Action: Repair or remove the configuration translator.
Level: 1

Type: WARNING

Impact: Management

BEA-141254: Generating new domain directory in {0}.

Cause: There was no domain directory at the specified location. Either a command line option or user input specified creation of the domain, so generation of the domain is commencing.

Action: No action is required. The domain directory will be generated, and the server will continue to boot normally.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141255: Domain generation completed in {0} milliseconds.

Cause: A new domain has been generated.

Action: No action is required. The server will continue to boot normally.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141256: A RuntimeException occurred while adding or removing a configuration element: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141257: An exception occurred while translating a configuration file: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141258: An exception occurred while constructing an ObjectName: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141259: An exception occurred while sending a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141260: An exception occurred while removing a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141261: An exception occurred while unregistering a Notification: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141262: An exception occurred while adding a Filter: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141263: An exception occurred in an MBean customizer: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141264: An exception occurred in an MBeanProxy: {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review this message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141265: Could not get the configuration lock used to serialize access to the configuration files.

Cause: The lock could not be obtained before the specified timeout period had elasped.

Action: Verify the configuration files and ensure that no server has hung, thereby not releasing the lock.
Level: 1

Type: ERROR

Impact: Management

BEA-141266: Parsing failure in {0}: {1}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141267: Parsing failure in {0} on line {1}: {2}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141268: Parsing failure in {0} on line {1}, column {2}: {3}.

Cause: This error occurs when the configuration file has invalid XML syntax or other errors.

Action: Validate the contents of the configuration file.
Level: 1

Type: ERROR

Impact: Management

BEA-141269: The temporary bean tree {0} was allocated for an undo, get, or activate operation, but has not been garbage collected.

Cause: The temporary bean tree has not been garbage collected.

Action: Repeat the specified operation and determine if memory usage in the server is increasing.
Level: 1

Type: WARNING

Impact: Management

BEA-141270: Could not get the configuration lock used to serialize access to configuration files. Retrying for another {0} seconds.

Cause: Another server was reading or writing to the configuration files, and the lock could not be obtained before the specified timeout period had elasped.

Action: No action is required. If the configuration subsystem fails to get the lock, and the number of retries is exhausted, a different message with error severity will be displayed.
Level: 1

Type: WARNING

Impact: Management

BEA-141271: An IOException occurred while recording setAttribute {1} on MBean {0}. Exception: {2}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141272: An IOException occurred while recording invoke {1} on MBean {0}. Exception: {2}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Take action based upon the provided exception details.
Level: 1

Type: ERROR

Impact: Management

BEA-141273: An upgrade framework class was not found. Exception: {0}. The configuration and upgrade framework component may not have been installed.

Cause: The configuration and upgrade framwork component may not have been installed.

Action: Install the Configuration Wizard and pgrade framework component by running the installer again.
Level: 1

Type: ERROR

Impact: Management

BEA-141274: Production mode has been specified at the command line using the the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the development mode specified in the config.xml file.

Cause: The command line overrides are not persisted to the config.xml file.

Action: If the Administration Console or WLST should display production mode defaults for attributes, then enable production mode in the Administration Console or WLST and activate the changes.
Level: 1

Type: WARNING

Impact: Management

BEA-141275: Development mode has been specified at the command line by setting the weblogic.ProductionModeEnabled system property to false. This system property overrides the production mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the production mode specified in the config.xml file.

Cause: The command line overrides are not persisted to the config.xml file.

Action: If the Administration Console or WLST should display development mode defaults for attributes, then enable development mode in the Administration Console or WLST and activate the changes.
Level: 1

Type: WARNING

Impact: Management

BEA-141276: An exception occurred while obtaining the class for interface {0}. The exception is: {1}

Cause: A resource or classloader issue caused the class lookup to fail.

Action: See the underlying exception to troubleshoot further.
Level: 1

Type: WARNING

Impact: Management

BEA-141277: The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WebLogic Server security infrastructure. The Platform MBeanServer will not be used and Platform MBeans will not be available using the WebLogic Server Runtime or Domain Runtime MBeanServers. This can occur if Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement) were defined. To allow the Platform MBeanServer to be used, either remove the system properties and JVM options or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder To eliminate this log error if Platform MBeans do not need to be available when using WebLogic Server, set the PlatformMBeanUsed attribute in the JMXMBean to false.

Cause: A system property was specified that caused the Platform MBeanServer to be created before the WebLogic Server Runtime MBeanServer.

Action: Remove the system properties or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder.
Level: 1

Type: WARNING

Impact: Management

BEA-141278: Java entropy configuration is: {0}.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141279: Detected BLOCKING java entropy configuration. This is the most secure setting, but may cause performance issues on machines with few sources of entropy.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141280: Detected NON-BLOCKING java entropy configuration. This setting will provide the best performance on machines with few sources of entropy, but is less secure than a blocking entropy configuration.

Cause: This message is informational and is printed every time WebLogic Server starts.

Action: Change your jave entropy configuration, if needed.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141281: A ForeignJNDIProvider named {0} has two child ForeignJNDILinks named {1} and {2}, which both have the same LocalJNDIName {3}. This duplication of LocalJNDIName is invalid.

Cause: Two links cannot share the same LocalJNDIName because it would be unclear as to which remote JNDI name to link to.

Action: Change the LocalJNDIName of one of the ForeignJNDILinks.
Level: 1

Type: ERROR

Impact: Management

BEA-141282: Server name {0} not found in domain {1}.

Cause: A managed server is started with -Dweblogic.Name with a value that is not configured in the domain.

Action: Specify the correct value of the param -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Management

BEA-141283: Server name could not be determined.

Cause: Either the name is not specified or the specified name does not exist in the config.xml file.

Action: Specify the correct value of the -Dweblogic.Name parameter.
Level: 1

Type: ERROR

Impact: Management

BEA-141284: A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.

Cause: A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.

Action: Update the configuration file to remove the deprecated MBean.
Level: 1

Type: INTERNAL_ERROR

Impact: Management

BEA-141285: The network access point property {0} was ignored because the specified network access point name was not found.

Cause: The specified network access point does not exist in the configuration.

Action: Modify the system property, and specify a valid network access point name.
Level: 1

Type: WARNING

Impact: Management

BEA-141286: The creation of the dynamic server failed with an exception.

Cause: An exception occurred during the creation of the dynamic server.

Action: Take action based upon the provided exception details, make any required changes, and retry the operation.
Level: 1

Type: WARNING

Impact: Management

BEA-141287: No matching machines were found based on the MachineNameMatchPrefix property. No machine has been calculated for servers from dynamic servers {0}.

Cause: The MachineNameMatchPrefix did not match any of the existing machines in the domain.

Action: Set the MachineNameMatchPrefix property so it matches the machine names in the domain.
Level: 1

Type: WARNING

Impact: Management

BEA-141288: Unable to obtain file lock but will retry.

Cause: This is an informational message only.

Action: If WebLogic Server fails to start because it was unable to obtain the file lock, then the lock files need to be removed manually before restarting WebLogic Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141289: Upgrade of 8.1 or prior domains is no longer supported. Convert the {1} from version {0} to 10.x format using weblogic.Upgrade.

Cause: WebLogic Server found a config.xml file with a version that is no longer supported.

Action: Upgrade the config.xml file to a newer version using weblogic.Upgrade from a 10.3 or lower version of the product.
Level: 1

Type: ERROR

Impact: Management

BEA-141290: Configuration plug-in not found for component type "{0}" in location "{1}"

Cause: The plug-in JAR file was not found.

Action: Verify the installation to ensure that the plug-in was installed correctly.
Level: 1

Type: ERROR

Impact: Management

BEA-141291: A system component for component type "{0}" was not defined in config.xml. The file "{1}" will not be distributed to the external server.

Cause: The system component is not defined in config.xml

Action: Define the corresponding system component in config.xml.
Level: 1

Type: WARNING

Impact: Management

BEA-141292: A machine was not specified in the system component "{0}" in config.xml. The file "{1}" will not be distributed to the external server.

Cause: The machine for the system component is not defined in config.xml

Action: Define the corresponding machine in the system component in config.xml.
Level: 1

Type: WARNING

Impact: Management

BEA-141293: Bad CAM replication exclusive file {0} : {1}.

Cause: See the error message for details.

Action: Correct the error in the CAM replication exclusive file.
Level: 1

Type: WARNING

Impact: Management

BEA-141294: Found invalid entries in CAM replication exclusive file {0}: {1}.

Cause: There are invalid entries in the file.

Action: Correct the invalid entries in the file.
Level: 1

Type: WARNING

Impact: Management

BEA-141295: Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.

Cause: Contact with Node Manager on "{1}" could not be made.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Management

BEA-141296: Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.

Cause: Contact with Node Manager on "{1}" could not be made.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Management

BEA-141297: Could not get the server file lock. Ensure that another server is not running in the same directory. Retrying for another {0} seconds.

Cause: Another server is running and still has the server lock.

Action: Check to see if another server is running.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141298: Could not register with the Administration Server: {0}

Cause: A network connection failed or an I/O exception occurred.

Action: Check the underlying exception and determine why the Managed Server could not connect to the Administration Server.
Level: 1

Type: NOTIFICATION

Impact: Management

BEA-141299: An exception occurred during the registration of MBeans in the MBeanServer : {0}.

Cause: See the exception text for details.

Action: The message includes information on the root cause. Review the message to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Management

BEA-141300: The activate changes operation for request "{0}" could not be completed because the activate timed out. Detailed state info is: {1}

Cause: The activate changes operation timed out.

Action: Try increasing the activate changes timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Management

BEA-149000: Unable to create DeployerRuntimeMBean.

Cause: This may occur if an error at the JMX level exists.

Action: Report this problem to My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149001: No application named "{0}" exists for operation "{1}".

Cause: The application name was likely misspelled.

Action: Verify that the application is correctly named.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149002: The source file was not provided for activation of application: "{0}".

Cause: Source files do not exist for the application to be deployed.

Action: Make source files available for the application to be deployed in the said path.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149003: Unable to access application source information in "{0}" for application "{1}". The specific error is: {2}.

Cause: Source files for the application to be deployed are not accessible.

Action: Ensure that no other process is using the source file(s).
Level: 1

Type: WARNING

Impact: Deployer

BEA-149004: Failures were detected while initiating {1} task for application "{0}".

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149011: Some of the targets in the deployment request are not configured in this domain. The named targets are: "{0}".

Cause: This error occurs when a deployment request is made to a target that is not configured.

Action: Ensure that the target list in the request is correct.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149013: Application "{0}" does not define the module, "{1}". {2} are the known valid module(s) for this application.

Cause: Incorrect deployment information was provided in the activate request.

Action: Ensure that the module information in the request is accurate. If adding modules, ensure that the source file is specified again so that it is reloaded and any new modules are deployed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149014: Target "{0}" is not defined.

Cause: Incorrect deployment information was provided in the activate request.

Action: Ensure that the target information in the request is accurate.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149015: Unable to add "{0}" to component "{1}".

Cause: The component is already targeted to the server, cluster, or virtual host.

Action: Check the target list.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149021: Rejecting {2} request for application "{1}". The specified ID, {0}, is already being used.

Cause: A {1} request included an ID provided by a user that is already assigned to another task.

Action: Choose a different ID or allow the system to allocate an ID for the request.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149025: An invalid attempt was made to target a non-Web application component, "{1}", in application "{0}" to a virtual host, "{2}".

Cause: An invalid attempt was made to target a non-Web application to virtual hosts.

Action: Correct the target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149026: {2} application {0} on {1}.

Cause: This is an informational message about the task description.

Action: This is an informational message about the task description.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149027: Unable to activate the application "{1}" from source "{0}". Reason: {2}

Cause: The application was improperly defined.

Action: Define the application properly.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149028: An invalid path, "{1}", was specified for the application "{0}".

Cause: The configured path for this application does not exist.

Action: Provide the application files in the specified location.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149031: The staging mode of "{0}" is invalid. The legal values are "stage" or "nostage".

Cause: An invalid staging mode has been specified.

Action: Specify a valid staging mode for the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149032: An attempt to restart a task has been rejected. The task has already been started.

Cause: This error results if start is called on a task that has already been started.

Action: Do not call start on a task that has already been started.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149033: {2} application {0} on {1}.

Cause: An application-level deployment notification has been reported.

Action: No action is required. This is an informational log message.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149034: An exception occurred for task {0}: {1}.

Cause: An error occurred while reporting the application status.

Action: The error may be due to server instability. Check the health of the server.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149035: Module {0} reported error: {1}.

Cause: The deployment request failed.

Action: Check the exception log and take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149038: Initiating task for {1} : {0}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149040: An attempt to change the staging mode for the application "{0}" has been rejected.

Cause: An attempt was made to change the staging mode for the application.

Action: The staging mode cannot be changed once it is set. Try deploying again without changing the staging mode.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149045: An attempt to add cluster target "{0}" was rejected, since cluster member "{1}" is also targeted by module "{2}". Targeting to a cluster member results in different behaviors than targeting to the entire cluster.

Cause: A cluster member is already in the target list of the module.

Action: Remove the cluster member from the target list, or re-target the cluster member rather than the cluster itself.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149048: An attempt to add server target "{1}" to module "{2}" has been rejected. This is because its parent cluster, "{0}", is also targeted by the module.

Cause: The module is already targeted to a cluster that contains the server.

Action: Remove the cluster from the target list or remove the cluster member from the target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149054: An attempt to add a virtual host target "{0}" to a non-Web application module "{1}" has been rejected.

Cause: An EJB or connector was attempting to target a virtual host.

Action: Remove the host from target list.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149055: Adding server {1} of cluster {0} as a target for module {3}. This module also includes server {2} that belongs to this cluster as one of its additional targets. Having multiple individual servers of a cluster as targets instead of having the entire cluster as the target can result in non-optimal load balancing and scalability. Therefore, this is not usually recommended.

Cause: The module is already targeted to a different cluster member.

Action: Target the entire cluster to the module.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149058: Distribute can only have stage as its staging mode. Application "{0}" has {1} as its staging mode.

Cause: This is an unexpected error.

Action: Specify a valid staging name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149059: Module {1} of application {0} is transitioning from {2} to {3} on server {4}.

Cause: A module is being deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149060: Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.

Cause: A module is being deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149061: Module {1} of application {0} failed to transition from {2} to {3} on server {4}.

Cause: An error was encountered during a module deployment.

Action: Details of the specific failure are documented in the associated log entries. Take appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149062: The task containing ID {0} cannot be canceled, since it has already completed execution.

Cause: An attempt has been made to cancel a deployment task that has completed execution.

Action: Do not attempt this operation on a completed task.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149066: Unable to deploy application "{0}", because module "{1}" does not provide a valid URI.

Cause: The application is incorrectly configured.

Action: Provide a URI for the module, or remove the application from the configuration.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149068: This is an unexpected exception.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149069: Deploying {0} using a deprecated protocol.

Cause: The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR file (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149073: The application "{0}" has no configured modules.

Cause: The application is improperly configured.

Action: The application will be marked as undeployable. After resolving configuration issues with the application, the administrator can retry the deployment.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149074: Successfully completed deployment task: {0}.

Cause: A deployment operation was requested.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149078: Stack trace for message {0}

Cause: A deployment failure occurred.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149080: A partial update of an archived application is not allowed. Application "{0}" cannot be redeployed.

Cause: There was an attempt to partially redeploy an archived application.

Action: Try deploying the entire application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149081: Cannot {2} application, "{0}", with version "{1}". The application was previously deployed without a version.

Cause: An attempt was made to {2} a versioned application when it was previously deployed without a version.

Action: Try {2} without a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149082: Cannot {2} application "{0}" without a version. The application was previously deployed with version "{1}".

Cause: An attempt was made to {2} an application without a version when it was previously deployed with a version.

Action: Try {2} with a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149083: An attempt was made to activate the application "{0}" when stop was in progress.

Cause: An attempt was made to activate the application "{0}" when stop was in progress.

Action: Try to activate the application "{0}" again after the stop is done. If it is a graceful stop, stop the application forcefully to end the graceful stop immediately.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149085: No application version was specified for application "{0}". The {2} operation will be performed against the currently active version "{1}".

Cause: No application version was specified for the operation.

Action: Verify that the currently active version is the desired version for the operation. If not, perform the operation again with the -app_version operation to specify a particular version.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149086: The application {0} is being retired gracefully.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149087: The application {0} will be retired after {1} seconds.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149088: The retirement for application {0}, which was scheduled to happen after {1} seconds, is canceled.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149089: An attempt was made to activate the application "{0}" when retirement was in progress.

Cause: An attempt was made to activate the application "{0}" when retirement was in progress.

Action: Try to activate the application "{0}" again after the retirement is done. If it is a graceful retirement, undeploy the application to end the graceful retirement immediately.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149091: An attempt was made to deploy application "{0}" with specified archive version "{1}". However, the application archive, as specified in the source, has version "{2}".

Cause: This error occurs when an attempt is made to specify a version that is different from the manifest version of the application archive in the source location.

Action: Perform the deployment again without specifying the version, or specify version "{2}" instead of "{1}".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149092: The source is not specified for the deployment operation of application "{0}", and the expected version is "{1}". However, the application archive at the source location for a previous deployment of version "{1}" now has version "{2}".

Cause: The source is not specified for the deployment operation of application "{0}", and the expected version is either explicitly specified or the currently active version. However, the application archive at the previously configured source location of the expected version has a different manifest version.

Action: Perform deployment again specifying either the source location or version "{2}".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149093: No version specified for the versioned application named "{0}" for operation {1}, and no active version is available.

Cause: The version was not specified for the operation when no currently active version was available.

Action: Specify the version of the application for the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149095: The application {0} is being retired now.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149096: Operation {1} is deprecated and cannot be applied to versioned application "{0}". Use operation {2} instead.

Cause: An attempt was made to perform the deprecated operation {1} on a versioned application. Use operation {2} instead.

Action: Use operation {2} instead.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149097: The retirement for application "{0}" failed.

Cause: This may happen due to a problem in accessing the persistent store or an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149098: An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.

Cause: An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.

Action: To stop the graceful retirement, force the application to undeploy.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149099: Unexpected errors occurred while sending deployment event {1} on behalf of application "{0}".

Cause: Deployment event listeners that are registered to receive a deployment event generated unexpected exceptions when processing the deployment event {1} on behalf of application "{0}".

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149100: Unexpected errors occurred while sending a vetoable deployment event on behalf of application "{0}".

Cause: Deployment event listeners registered to receive a vetoable deployment event generated unexpected exceptions when processing the deployment event {1} on behalf of application "{0}".

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149101: Application "{0}" is not deployed on target "{1}". Therefore, it cannot be undeployed or removed. The requested operation {2} is valid only on the deployed targets of the application.

Cause: Incorrect target information was provided in the {2} operation request.

Action: Ensure that the target information in the request is accurate.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149102: Production redeployment is not supported for application "{0}", which is of module type {1}. Production redeployment is supported for the following module types only: {2}. If not attempting to perform production redeployment, try deploying without a version.

Cause: Attempt was made to perform production redeployment for an unsupported module type.

Action: Ensure that the module type is supported before performing production redeployment. Or, try deploying again without a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149103: An exception occurred while executing task {0} for application "{1}": {2}.

Cause: An exception occurred while executing the deployment task for the application.

Action: If it is an application error, correct it if possible. If it is a system error, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149104: Update request for "{0}" does not specify any descriptors to be updated

Cause: The deployment plan does not include any module overrides.

Action: Ensure that the deployment plan is properly constructed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149105: An attempt was made to deploy a library located at "{2}" with name "{0}", which is different from the one specified in the manifest of the library: "{1}".

Cause: This error occurs when an attempt is made to specify a name that is different from the one in the manifest of the library in the source location.

Action: Perform deployment again without specifying the name of the library.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149106: An attempt was made to deploy a library located at "{0}" without specifying a name, and the library does not have "Extension-Name" specified in its manifest.

Cause: This error occurs when an attempt is made to deploy a library without specifying a name, and the library module does not have "Extension-Name" specified in its manifest.

Action: Perform deployment again specifying the name of the library either during deployment or in the manifest of the library, using the "Extension-Name" attribute.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149107: An attempt was made to deploy library "{0}" with specified specification version "{1}" and implementation version "{2}". However, the library manifest has specification version "{3}" and implementation version "{4}".

Cause: This error occurs when an attempt is made to specify a version that is different from the manifest version of the library.

Action: Perform deployment again without specifying the version or after specifying the same version as specified in the manifest.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149108: Failures were detected while initiating {0} task.

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149110: An exception occurred while processing the completion of the task {0}, {1}. The active application version state may not have been updated.

Cause: This is an internal error.

Action: Report this problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149111: Application "{0}" is non-versioned, and an attempt was made to redeploy application "{0}" with the source. Redeploying with the source is only allowed when redeploying a new version of a versioned application. Try redeploying again without specifying the source.

Cause: An attempt was made to redeploy with the source specified for a non-versioned application "{0}". Redeploy again without specifying the source.

Action: Try redeploying again without specifying the source.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149112: Application "{0}" is already deployed, and the attempt was made to redeploy application "{0}" again with source. Redeploying with the source is only allowed when redeploying a new version of the application. Try redeploying again without specifying the source or with a new version.

Cause: An attempt was made to redeploy with the source specified for application "{0}", but application "{0}" was already deployed. Redeploy again without specifying the source or with a new version.

Action: Try redeploying again without specifying the source or redeploy with a new version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149113: Cannot deploy or redeploy application "{0}" because the maximum number of application versions ({2}) for application "{1}" has been exceeded. Currently deployed versions are: "{3}".

Cause: An attempt was made to deploy or redeploy application "{0}" when the maximum number of application versions ("{2}") for application "{1}" has been exceeded.

Action: Try undeploying the existing application version(s) before deploying or redeploying the new version(s).
Level: 1

Type: ERROR

Impact: Deployer

BEA-149114: Cannot deploy or redeploy application "{0}" with version identifier "{1}" because the maximum length of the version identifier ({2}) has been exceeded.

Cause: An attempt was made to deploy or redeploy application "{0}" with version identifier "{1}" that exceeded the maximum length ({2}).

Action: Try reducing the version identifier length when deploying or redeploying the application version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149115: Cannot deploy or redeploy application "{0}" with invalid version identifier "{1}". Version identifiers may only contain alphanumerics, period, underscore, and hyphen and must be less than 215 characters in length.

Cause: An attempt was made to deploy or redeploy application "{0}" with invalid version identifier "{1}".

Action: Try changing the version identifier to a valid one when deploying or redeploying the application version. Version identifiers can only consist of alphanumeric, period, underscore, or hyphen characters and must not be "." or "..".
Level: 1

Type: ERROR

Impact: Deployer

BEA-149116: Cannot obtain the deployment configuration.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149117: {2} library {0} on {1}.

Cause: This is an informational message about the task description.

Action: This is an informational message about the task description.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149118: "{1}" is not targeted to "{0}".

Cause: An attempt was made to undeploy the application from a target where it is not deployed.

Action: Correct the target list for the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149119: Different targets cannot be specified when deploying a new version "{1}" of application "{0}". The targets specified, "{3}", are different from those of the previous version, "{2}".

Cause: An attempt was made to deploy a new application version with targets that are different from that of the previous version.

Action: Try deploying again without specifying targets, or specify the exact same target as the previous version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149120: The plan version "{1}" cannot be specified when deploying a non-versioned application "{0}".

Cause: An attempt was made to deploy a non-versioned application with a plan version.

Action: Try deploying again with an application version or without the plan version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149121: Rejecting {1} request for application {0} because the deployment service is not started.

Cause: A deployment operation was attempted when the server was starting or shutting down.

Action: Perform the deployment operation again after the server has started or before the server has shut down.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149122: Deployment perations on internal application "{0}" are not permitted;.

Cause: Deployment operations are not permitted on internal applications.

Action: Do not attempt any deployment operations on internal applications.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149123: The application "{0}" currently has security model "{1}", and an attempt was made to redeploy the application again with a different security model "{2}". The specified security model will be ignored for the current deployment operation. To change the security model, undeploy the application and deploy it again with the new security model.

Cause: An attempt was made to redeploy the same application with a different security model.

Action: Undeploy the application and deploy it again with the new security model.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149124: Failures were detected while initiating {1} task for application "{0}". Error is: "{2}"

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate action.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149125: No application version was specified for the {0} operation of application "{1}". The {0} operation will be performed against the retired application version "{2}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149126: No application version was specified for the {0} operation of application "{1}". The application version "{2}" will not be removed as its retirement is still in progress. Oracle recommends that the application version "{2}" be undeployed explicitly after the retirement is done. An explicit undeploy of the application version can also be performed before retirement is done; however, exercise caution as this may interrupt inflight work.

Cause: No application version was specified for the {0} operation of application "{1}".

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149127: Failures were detected while initiating "{0}" task. Error is: "{1}"

Cause: Task creation can fail for many reasons.

Action: Check the error message and take appropriate actions.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149128: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retired application version "{3}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149129: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retiring application version "{3}". Note that retirement is still in progress for version "{3}" and any inflight work will be interrupted.

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149130: The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the currently active version "{3}".

Cause: This is an informational message only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149131: Cannot perform operation {2} because application "{0}" is in state {1}

Cause: The application is no longer active.

Action: Ensure that the application is active. Deploy again if needed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149132: Split directory application {0} can only be deployed on the Administration Server.

Cause: An attempt was made to perform the deployment operation on the split directory application on a server other than the Administration Server.

Action: For split directory application {0}, perform deployment operations on the Administration Server alone.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149133: Auto-deployed application {0} can only be deployed on the Administration Server.

Cause: An attempt was made to perform the deployment operation on the auto-deployed application on a server other than the Administration Server.

Action: For auto-deployed application {0}, perform deployment operations on the Administration Server alone.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149134: A redeploy was performed without specifying -source for the archived versioned application "{0}". Partial update of an archived application is not allowed. To perform production redeployment of versioned applications, specify -source with the redeploy operation.

Cause: An attempt was made to partially redeploy an archived application.

Action: Specify -source for production redeployment, or redeploy the entire application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149135: Operation {2} cannot be performed since application "{0}" is not deployed on the target "{1}".

Cause: Operation {2} could not be performed because the application was not deployed on the provided target.

Action: Rery with a valid target.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149137: {0} is an invalid path for partial redeployment. The URI of the file or directory to be redeployed should be relative to {1}, the root of the enterprise application, or to the standalone module being redeployed.

Cause: The file could not be located in the application.

Action: Use a valid specification for the file.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149138: A subset of the originally configured targets for the application "{0}" was specified. This can potentially lead to out-of-sync applications between the different server targets. The targets specified, "{2}", are different from those of the previous version, "{1}".

Cause: A deployment operation was performed on an existing application with a subset of the originally configured targets.

Action: If the application content has changed since the last operation, Ensure that all configured targets are updated. To do so, repeat the operation without specifying targets in order to automatically use the configured targets.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149139: Application "{0}" is targeted to cluster "{1}", and provided the target for {3} operation is "{2}". The {3} operation on a subset of the targeted clustered servers is not supported.

Cause: The {3} operation was attempted on one or more servers in the targeted cluster.

Action: Retry with the targeted cluster, or undeploy from the cluster and deploy to the desired individual servers.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149140: The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task.

Cause: The user is the current owner of the domain configuration edit lock.

Action: Activate (or cancel) the edit session. The user can exit the deployer tool without affecting the task.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149141: The AppDeploymentMBean already exists for application "{0}".

Cause: The AppDeploymentMBean already exists for application "{0}".

Action: Ensure that different applications do not have the same name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149142: Cluster target "{0}" is configured with no servers, and therefore configuration is updated.

Cause: A deployment to a cluster target was attempted, but the cluster contains no servers.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149143: Submodule targets in an application must be specified with the correct module name.

Cause: A submodule target was specified incorrectly.

Action: Ensure that the submodule target was specified with the correct syntax and with the correct module name.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149145: Unable to contact "{0}". Deployment is deferred until "{0}" becomes available.

Cause: Contact with "{0}" could not be made. Deployment is deferred until "{0}" becomes available.

Action: No action is necessary.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149146: Attempt to reach the Administration Server with alternate URL: "{0}" failed.

Cause: The attempt to reach the Administration Server with the alternate URL: "{0}" failed.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149147: Could not reach the Administration Server through any of its URLs: "{0}".

Cause: The Administration Server could not be reached through any of its URLs: "{0}".

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149148: Exception occurred while receiving a message on loopback.

Cause: An exception occurred while receiving a message on loopback.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149149: Malformed URL: "{0}".

Cause: The URL: "{0}" was malformed.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149150: An IOException occurred while reading the input.

Cause: An IOException occurred while reading the input.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149151: Could not find a registered DeploymentReceiver to handle requests for "{0}".

Cause: A registered DeploymentReceiver could not be found to handle requests for "{0}".

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149152: No deployment request for which to set up the context.

Cause: No deployment request for which to set up the context.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149153: A "prepare" message was received for ID "{0}" that has already been completed or canceled.

Cause: A "prepare" message was received for ID "{0}" that has already been completed or canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149154: A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.

Cause: A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149155: Received "get deployments response" message "{0}" while already handling one. Ignoring the second request.

Cause: A "get deployments response" message "{0}" was received while another was being handled. The second request was ignored.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149156: Illegal state for operation start: "{0}".

Cause: The start operation was called on an application that either had an update pending or was used with the administration mode flag.

Action: To move the application from active to administration mode, use the stop operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149157: There is nothing to do for task "{0}".

Cause: There is nothing to do for task "{0}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149158: No application files exist at "{0}".

Cause: No application files exist at "{0}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149159: There was an attempt to create a staging directory that is null.

Cause: There was an attempt to create a staging directory that is null.

Action: Ensure that the staging directory is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149160: There was an attempt to create a staging directory for a null application name.

Cause: There was an attempt to create a staging directory for a null application name.

Action: Ensure that the application name is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149161: This operation requires that a target be specified.

Cause: This operation requires that a target be specified.

Action: Ensure that the deployment request is complete and contains the required targeting information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149162: This operation requires that a deployment plan be specified.

Cause: This operation requires that a deployment plan be specified.

Action: Ensure that the deployment request is complete and contains the required deployment plan information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149163: The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed. If using "Automatically Aquire Lock and Activate Changes" in the Administration Console, then the lock will expire shortly, so retry this operation.

Cause: The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149164: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.

Cause: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149165: Invalid target specified.

Cause: An invalid target was specified.

Action: See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149166: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.

Cause: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.

Action: Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149167: No action was needed to commit the request for "{0}" on "{1}".

Cause: No action was needed to commit the request for "{0}" on "{1}".

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149168: Request "{0}" has already been completed or was canceled.

Cause: The request "{0}" has already been completed or was canceled.

Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149169: Requires server restart for completion.

Cause: In order to complete the action, the server must be restarted.

Action: Restart the required servers.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149170: Invalid targeting was specified for this operation. Module and submodule targets cannot both be specified for this type of request.

Cause: The operation specified both module and submodule targeting, which is invalid for this operation.

Action: Perform the operation separately for both module and submodule targets.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149171: Deferred deployment task: {0}

Cause: A deployment operation was requested with targets that were unreachable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149172: Deployment request {0} is affecting the system resource {1}, which involves a non-dynamic property {2} in {3}. Therefore, a restart of the resource or the appropriate server targets is required for the changes to be active.

Cause: This is an informational message indicating that deployment involves a non-dynamic property.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149178: Application "{0}" is targeted to cluster "{1}", and the provided target for {3} operation is "{2}". This can potentially lead to client request problems on the cluster.

Cause: An operation was performed on a subset of a cluster for an application targeted to the cluster.

Action: Ensure that the cluster properly serves requests by performing operations on the cluster rather then on individual servers within the cluster.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149181: Deployment service encountered an error while aborting the edit session before start. Initiator for this edit session is "{0}". Error is "{1}".

Cause: See the reported error.

Action: Take appropriate action based on the reported error.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149182: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.

Cause: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.

Action: Repeat the redeploy operation without the alternate descriptor.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149183: An invalid retiretimeout option was specified for the deploy operation. The retiretimeout option was specified as "{2}" for the initial deployment of application "{0}". Retirement policies must be set during the deploy or redeploy of the next version in order to apply to version "{1}" of "{0}".

Cause: An invalid retiretimeout option was specified for the deploy operation.

Action: Specify the retiretimeout option during the deploy or redeploy of subsequent versions in order for the retirement to occur correctly at that time.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149184: The application "{0}" was autodeployed and may only be redeployed by touching the REDEPLOY file in the domain autodeploy directory for the respected application.

Cause: Autodeployed applications cannot be redeployed through tools.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149185: The application "{0}" was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.

Cause: Autodeployed application cannot be undeployed through tools.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149186: The application "{0}" was autodeployed and cannot be redistributed.

Cause: Autodeployed application cannot be redistributed.

Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149187: An unexpected error occurred when specifying configuration information for the application "{0}" due to {1}.

Cause: Application configuration upgrade requires targeting information.

Action: Inspect the problematic application parts and deploy the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149188: No application named "{0}" exists for operation {1}. Operation cannot be performed until the server is restarted.

Cause: The application was created after non-dynamic changes were activated. The server needed to be restarted.

Action: Restart the server and then start the application. In the future, start the application before making non-dynamic changes to the configuration.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149189: An attempt was made to execute the "{0}" operation on an application named "{1}" that is not currently available. The application may have been created after non-dynamic configuration changes were activated. If so, the operation cannot be performed until the server is restarted so that the application will be available.

Cause: The application may have been created after non-dynamic changes were activated. The server needed to be restarted.

Action: Restart the server and then perform the operation on the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149190: Changes are pending from another session whose lock has expired. This deployment operation will not activate changes from another edit session and therefore cannot proceed. Either cancel the edit lock or activate the pending changes using the Administration Console or WLST.

Cause: Changes were made with an edit session that has now expired.

Action: Cancel the edit lock or activate the pending changes using the Administration Console or WebLogic Scripting Tool (WLST).
Level: 1

Type: WARNING

Impact: Deployer

BEA-149191: Operation "{0}" on application "{1}" is initializing on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149192: Operation "{0}" on application "{1}" is in progress on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149193: Operation "{0}" on application "{1}" has failed on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149194: Operation "{0}" on application "{1}" has succeeded on "{2}".

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149195: Operation "{0}" on application "{1}" has been deferred since "{2}" is unavailable.

Cause: This is an informational message indicating deployment status change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149196: Rejecting {1} request for application {0} because {2} request is running for the application.

Cause: A second operation for an application was requested when an operation for the application was runnning.

Action: Perform the operation again when the operation that is running is completed.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149197: Cannot perform operation {3} because application "{0}" is in state {1} and "{2}" is running.

Cause: The application is in the wrong state for the operation.

Action: Ensure that the application is in the correct state before attempting the operation.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149198: Cannot rename directory "{0}" to {1}.

Cause: The rename operation failed since the source directory is not present or there is a privilege issue.

Action: Check that the source directory is present and has the required permissions.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149199: Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server's configuration.

Cause: The server is configured not to allow Java security permissions to be declared in the Weblogic deployment descriptors.

Action: Remove Java security permissions from the deployment descriptor before re-deployment.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149202: Encountered an exception while attempting to commit the {0} task for the application "{1}".

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then re-initiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149205: Failed to initialize the application "{0}" due to error {1}

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149209: The Slave Deployer is resuming.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Deployer

BEA-149229: Server "{0}" in cluster "{1}" is unable to initialize due to failed deployments.

Cause: This problem occurred due to failed deployments, which are already logged.

Action: Correct the deployment problem, and restart the server in the cluster.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149231: Unable to set the activation state to {1} for the application "{0}".

Cause: An unexpected error occurred.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149233: An unexpected error occurred during the deployment process.

Cause: There was a problem with the internal implementation that was not anticipated.

Action: Report the error and any useful information needed to reproduce the problem to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149239: Application deployment failures were detected during startup of the Administration Server, "{0}", member of cluster "{1}".

Cause: One or more applications could not be deployed during the startup of the Administration Server.

Action: Oracle recommends that the Administration Server not be part of a cluster. One response to this warning is to remove it from the cluster and restart the Administration Server. Alternatively, review the Administration Server log to understand why the deployment failed, fix the problem, and redeploy the application.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149243: The internal application "{0}" could not be deployed. An attempt will be made to retry deploying this application after synchronizing the application files again.

Cause: It is likely that the internal staged directory was corrupt or there was a failure when deploying the staged application.

Action: No action is necessary if the retry succeeds. Otherwise, the nature of the failure should provide an indication of the problem and its resolution. If this is not clear, contact My Oracle Support with the relevant logs and configuration files.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149245: The deployment plan at "{0}" for application "{1}" does not define a valid deployment plan.

Cause: The application is configured with an incorrect deployment plan document.

Action: Deploy the application using a valid deployment plan.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149246: The security realm "{0}" does not support application versioning. Deployment of application "{1}" failed.

Cause: The security realm "{0}" does not support application versioning. The deployment of the application version failed.

Action: Deploy the application using a security realm that supports application versioning.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149247: Failed to transition the application "{0}" to running mode due to error {1}

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149248: Failed to transition the application "{0}" to administration mode due to error {1}.

Cause: The cause of this error is likely in the application or the application subsystem for that application type.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149250: Unable to unprepare the application "{0}".

Cause: This was an unexpected error.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149251: Operation {0} failed for application "{1}". Error: {2}

Cause: See the exception in the message body.

Action: Typically, no action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149252: No deployment "{1}" found for operation {0}.

Cause: See the message body.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149256: Failed to find deployment for application "{0}".

Cause: The cause of this error is likely that the deployment was not properly created, possibly because it may not have proper descriptors.

Action: Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149257: Rejecting the attempt to distribute application "{0}" while the application is running.

Cause: The application was not stopped.

Action: Stop the application or redeploy the application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149258: The server failed to completely remove the staged files "{1}" for application "{0}". Check the directory and ensure that no other application is using this directory. This will result in inappropriate results when this server is partitioned and tries to deploy this application.

Cause: Another application might be using the files under a staging directory.

Action: Delete the appropriate staged files manually.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149259: Server "{0}" in cluster "{1}" is being brought up in administration state due to failed deployments.

Cause: This problem occurred due to failed deployments, which are already logged.

Action: Correct the cause of the deployment errors, redeploy the failed deployments, and resume or restart the server in the cluster.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149260: A failure occurred during application startup.

Cause: Check the error stack trace for details of the failure.

Action: Correct the cause of the application failure, if possible, and redeploy the application or restart the server. If it is an Oracle internal application, report it to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149264: Invalid redeploy attempt on application "{0}". There was an attempt to redeploy the application when the application was not running.

Cause: The application was stopped.

Action: Start the application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149265: Failure occurred in the execution of deployment request with ID "{0}" for task "{1}". Error is: "{2}"

Cause: See the reported error in the message body.

Action: Start the application.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149266: Illegal state for operation deploy: "{0}".

Cause: The deploy operation was called on an application that was not new.

Action: Verify that the specified application name and operation are correct.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149267: Cancel operation on deployment task "{0}" on server "{1}" failed.

Cause: See the underlying exception.

Action: Take action based on the underlying exception.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149268: Static deployment of non-versioned application "{0}" failed due to a version being defined in its manifest file.

Cause: The manifest file was modified with a version for a non-versioned application.

Action: Remove the application and redeploy it with a version.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149269: Static file redeployment and module level redeployment cannot be in the same deployment task. Check the usage.

Cause: The server cannot determine which type of redeployment should be processed.

Action: Correct the deployment option.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149400: Activating application: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149401: Removing application: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149403: Application {0} deployed from the applications directory has components that are deployed on servers other than the Administration Server. Refresh of static content (such as JSPs and HTML pages) will not be automatically propagated to the Managed Servers. To propagate your changes to the Managed Servers, you must redeploy the application by touching the REDEPLOY file.

Cause: This is a warning message only.

Action: Touch the REDEPLOY file to properly redeploy the application. The REDEPLOY file is located in the same directory as the deployment descriptor. For EAR files, it is located in META-INF/REDEPLOY.
Level: 1

Type: WARNING

Impact: Application Poller

BEA-149407: An error occurred while undeploying application {0} : {1}.

Cause: Undeployment can fail for many reasons.

Action: Review the error message and take corrective action.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149408: An exception occurred while deploying an application {0}: {1}.

Cause: Deployment of an application can fail for many reasons. Refer to the exception details.

Action: Review the exception. To redeploy the application after correcting the error condition, touch the file called REDEPLOY in the META-INF or WEB-INF directory of the exploded application.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149409: Caught exception while starting the applications poller on server start {0}.

Cause: A misconfigured application may be present in the applications directory.

Action: Review the exception message in the server log.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149410: Runtime deployment error while deploying - {0}.

Cause: The cause of this error is unknown.

Action: Refer to the runtime error in the message.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149411: I/O exception was encountered {0}.

Cause: An I/O exception can occur during file read/write while deploying an application.

Action: Take corrective action based on the exception message details.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149412: Application "{0}" is being redeployed, because it changed since the previous server run.

Cause: This application is deployed using auto-deployment. The application was modified while the server was down, hence it will be redeployed by the auto-deployment poller. Another possible cause is that the internal file used by the poller was removed or moved from disk. In that case, it assumes applications have changed.

Action: No action is required. This is an informational message to explain why this deployment was redeployed after its deployment at startup.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149414: Could not create directory for autodeployed applications: {0}

Cause: This may be an error on the local file system of the Administration Server.

Action: Correct the error by creating the directory or making sure read/write permissions exist.
Level: 1

Type: WARNING

Impact: Application Poller

BEA-149415: An exception was encountered while migrating application poller applications {0}.

Cause: An exception occurred while modifying application's path.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Application Poller

BEA-149416: Application migrated {0} - {1}

Cause: This is informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Application Poller

BEA-149417: Another process is using the file "{0}". The server will attempt to deploy the application once it is unlocked by the other process.

Cause: Another process has a lock on the file that is in the hot deploy directory. The application could still be in the process of being copied.

Action: Ensure that no other process is attempting to lock part or all of this application file. If the copy is ongoing, then no action should be necessary.
Level: 1

Type: WARNING

Impact: Application Poller

BEA-149500: An exception occurred while registering the MBean {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149501: An exception occurred while registering the MBean {0} at property {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149502: An exception occurred while unregistering the MBean {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149503: An exception occurred while unregistering the MBean {0} at property {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149504: The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.

Cause: This is likely due to a misconfiguration of the Managed Server. Often this is associated with the use of the administration channel.

Action: Ensure that the Managed Server adminstration ports are properly configured. It may be helpful to review the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149505: The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.

Cause: This is likely because the Managed Server is simply not running. It may indicated that the administration channels are not properly configured.

Action: Ensure that the Managed Server administration ports are properly configured. It may be helpful to review the documentation on the administration channel configuration.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149506: Established JMX Connectivity with {0} at the JMX Service URL of {1}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149507: JMX Connectivity has been discontinued with the Managed Server {0}.

Cause: This message is logged whenever a Managed Server is shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149508: Unable to establish JMX Connectivity with the Administration Server.

Cause: This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.

Action: If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149509: Unable to establish JMX connectivity with the Administration Server {0} at {1}.

Cause: This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.

Action: If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149510: Unable to establish JMX Connectivity with the Administration Server {0} at {1}.

Cause: This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.

Action: If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
Level: 1

Type: WARNING

Impact: JMX

BEA-149511: Established JMX Connectivity with the Administration Server {0} at {1}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149512: JMX Connector Server started at {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149513: JMX Connector Server stopped at {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149515: An error was encountered getting the attribute {1} on the MBean {0} during a call to getAttributes.

Cause: This problem is the result of an internal error in the WebLogic Server JMX implementation.

Action: Report this message to My Oracle Support.
Level: 1

Type: WARNING

Impact: JMX

BEA-149516: An error was encountered when setting the attribute {1} on the MBean {0} during a call to setAttributes.

Cause: This problem is the result of an internal error in the WebLogic Server JMX implementation.

Action: Report this message to My Oracle Support.
Level: 1

Type: WARNING

Impact: JMX

BEA-149518: An attempt was made to unregister the {0} WebLogic Server MBean through JMX.

Cause: Avoid using the JMX API to unregister a WebLogic Server MBean.

Action: Use the WebLogic Server APIs to control the configuration of the server environment.
Level: 1

Type: WARNING

Impact: JMX

BEA-149519: The JMX Service URL {1} for Managed Server {0} was malformed.

Cause: The URL used to contact a Managed Server was malformed.

Action: See the exception included with this message to determine the proper action.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149520: An attempt was made to register an MBean with ObjectName {0} ObjectName in com.bea domain.

Cause: An attempt was made to register an MBean with the com.bea domain name.

Action: Register your MBeans with another domain name.
Level: 1

Type: ERROR

Impact: JMX

BEA-149521: An exception occurred during the processing of JMX Connectivity with the Administration Server: {0}

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Refer to the embedded exception information for more details and troubleshoot based on that information.
Level: 1

Type: WARNING

Impact: JMX

BEA-149522: No credentials were provided.

Cause: Credentials are required when connecting through Remote MAnagement Interface (RMI).

Action: Retry the connection, supplying a username and password.
Level: 1

Type: ERROR

Impact: JMX

BEA-149523: RmiServerManager not found.

Cause: This problem is the result of an internal error in the WebLogic Server JMX implementation.

Action: Report this message to My Oracle Support.
Level: 1

Type: ERROR

Impact: JMX

BEA-149524: JMX Connector Server started at "{0}".

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149525: JMX Connector Server stopped at "{0}".

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: JMX

BEA-149601: The deployment framework was unable to resume accepting requests.

Cause: This is an internal server error.

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149603: The deployment framework was unable to cleanly shut down.

Cause: This is an internal error.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149605: Failed to create App/Comp MBeans for AppDeploymentMBean {0}. Error - {1}.

Cause: An error was found in the AppDeploymentMBean.

Action: Reconfigure the AppDeploymentMBean.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149606: Failed to configure deployment MBean for {0}.

Cause: An error was found while configuring a deployment MBean.

Action: Review the application and reconfigure it.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149607: Failed to persist state for deployment with name {0}. {1}

Cause: See the exception for more details on the cause of this problem.

Action: See the exception. Undeploy and deploy after correcting the problem.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149608: Unknown type of deployable: "{0}"

Cause: The type of deployable: "{0}" is unknown.

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149609: AppRuntimeStateRuntime only available on the Administration Server.

Cause: AppRuntimeStateRuntime only available on the Administration Server.

Action: Ensure that the Administration Server is running and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149610: Problems were encountered while creating the persistent store.

Cause: An exception occurred: {0}

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149611: Problems were encountered while creating the persistent store.

Cause: An exception occurred: {0}

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149612: Problems were encountered while saving to the persistent store for "{0}".

Cause: {1}

Action: See the exception and check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149613: Problems were encountered while deleting from the persistent store for "{0}".

Cause: {1}

Action: Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149614: There were problems during the server disconnect for listener "{0}". {1}

Cause: {1}

Action: Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149615: Unrecognized type: "{0}".

Cause: There was an unrecognized type: "{0}".

Action: Check for preceding messages in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149616: A critical internal application {0} was not deployed. Error: {1}

Cause: The cause of this error is unknown.

Action: Check for preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149617: Non-critical internal application {0} was not deployed. Error: {1}

Cause: An internal application may not have been installed.

Action: Install the WebLogic Server internal application by running the WebLogic Server installer and choosing the relevant option.
Level: 1

Type: WARNING

Impact: Deployer

BEA-149618: Unable to deploy an internal management Web application - {0}. Managed Servers may be unable to start.

Cause: WebLogic Server was unable to find the relevant WAR files in RootDirectory/lib. This might also be an internal failure. See the exception stack trace for more details.

Action: If you are not running the server from the directory where WebLogic Server was installed, ensure that the value of the provided RootDirectory matches the directory where the WebLogic Server product was installed. Verify that a file with the application name in the log message (with a .war extension) is present in RootDirectory/lib. If not, contact My Oracle Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-149619: The deletion of configuration file {0} failed.

Cause: An error occurred while deleting the file.

Action: Ensure that no processes have the file open for write. Ensure that the permissions on the directory allow for delete of this file.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149621: An error occurred while the Administration Server was performing configuration recovery. Error is : "{0}".

Cause: See the exception details for the cause.

Action: Stop the server and do configuration recovery manually.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149622: Could not get file lock used to serialize access to configuration files.

Cause: The lock could not be obtained before the specified timeout period has elapsed.

Action: Verify the configuration files and ensure no server has hung, thereby not releasing the lock.
Level: 1

Type: ERROR

Impact: Deployer

BEA-149623: Unable to create DeploymentManagerMBean.

Cause: This may occur if an error at the JMX level exists.

Action: Report this problem to Oracle Customer Support.
Level: 1

Type: INTERNAL_ERROR

Impact: Deployer

BEA-150000: An error occurred while establishing a connection back to the Adminstration Server {0} during startup. Since bootstrap succeeded, check that {0} uniquely identifies the Administration Server.

Cause: An improper Administration Server URL has been specified, or the Administration Server is not available at the specified URL. Commonly this is because the Managed Server shares an adminstration URL with the Administration Server. Another possibility is that the host identified by {0}, or the local host, is not configured properly. For instance, an /etc/hosts or DNS lookup on the hostname results in a loopback address.

Action: Verify that the URL specified for the Administration Server is valid, unique and that the Administration Server is available and listening at the specified URL. A common problem is that the administration port is enabled and both the Administration Server and Managed Server are running on the same machine. In this instance a different administration port should be selected for the Managed Server. Another possibility is that the host identified by {0}, or the local host, is not configured properly. For instance, an /etc/hosts or DNS lookup on the hostname results in a loopback address.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150001: An error occurred while connecting to the Administration Server to bootstrap through the URL: {0}, user: {1}.

Cause: The Administration Server might currently be unavailable or the specified URL: {0} or username: {1} might be invalid.

Action: Confirm that the designated Administration Server is running and that the specified URL: {0} and username: {1} are valid for this configuration.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150014: The Managed Server Independence feature is disabled for this server ({0}).

Cause: The specified Administration Server is either incorrect or not reachable on the network.

Action: Ensure that the Administration Server is running and reachable by this server, or set the ManagedServerIndependenceEnabled attribute on this server to true.
Level: 1

Type: INTERNAL_ERROR

Impact: Configuration Management

BEA-150018: This server is being started in Managed Server independence mode in the absence of the Administration Server.

Cause: The Managed Server was unable to communicate with the Adminstration Server at the provided URL because the specified Administration Server either was not running or was partitioned.

Action: Restart the Administration Server with Managed Server discovery enabled so that the running Managed Server can synchronize its configuration with the Administration Server and become centrally managed.
Level: 1

Type: NOTIFICATION

Impact: Configuration Management

BEA-150020: The Managed Server could not reach the Administration Server at {0}.

Cause: The Managed Server was given a URL on which the Administration Server could not be contacted.

Action: Inspect the Administration Server address:port provided to the Managed Server that is being started. This address should be changed to point to the Administration Server rather than resolving locally on the Managed Server.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150021: The Administration Server failed to authenticate the identity of the user {0} starting the Managed Server. The reason for the error is {1}.

Cause: The username and password combination was not correct.

Action: Inspect the username and password of the user starting the Managed Server and supply the correct credentials. The username and password are specified on startup with -Dweblogic.management.username and -Dweblogic.management.password command line options to the java weblogic.Server command.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150024: The server name {0} is being started again as a Managed Server.

Cause: The Administration Server is being started as the Managed Server.

Action: Specify a different server name to start.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150026: The server {0} being started is at an invalid release level {1} with respect to the Administration Server {2}. The major version of the Administration Server must be less than or equal to the major version of the Managed Server.

Cause: A Managed Server of a different major release is attempting to start from the Administration Server.

Action: Point the Managed Server to an Administration Server at the correct release level.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150027: Server name {0} not found in domain {1}.

Cause: A Managed Server is started with -Dweblogic.Name with a value that was not configured in the domain.

Action: Specify the correct value of the parameter -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150028: A security failure or an exception occurred when retrieving the bootstrap information for the Managed Server.

Cause: An invalid username and password might have been supplied while starting the Managed Server.

Action: Supply the correct credentials. Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150032: The Managed Server did not provide any version details at initial contact.

Cause: A Managed Server of a different major and minor release is attempting to start from the Administration Server.

Action: Point the Managed Server to an Administration Server at the correct release level.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150034: An attempt was made to download the configuration for the server {0} without the required credentials.

Cause: This should not happen during normal operations and may represent an attempt to compromise the server.

Action: Identify the server from which the connection was made and ensure that the username and password are being properly specified.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150035: An attempt was made to download the configuration for the server {0} by the user {1} with an invalid password.

Cause: This should not happen during normal operations and may represent an attempt to compromise the server.

Action: Identify the server from which the connection was made and ensure that the username and password are being properly specified.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150036: An attempt was made to download the configuration for the server {0} by the unauthorized user {1}.

Cause: This should not happen during normal operations and may represent an attempt to compromise the server.

Action: Identify the server from which the connection was made and ensure that the username and password are being properly specified.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150038: A configuration file was found in the parent directory {0}, but the root directory is empty.

Cause: This message indicates that a configuration file exists in the parent of the root directory.

Action: If the specified root directory is not correct, then take appropriate action. Otherwise, this message may be ignored.
Level: 1

Type: WARNING

Impact: Configuration Management

BEA-150039: The server name could not be determined.

Cause: The name was not specified or the specified name does not exist in the config.xml file.

Action: Specify the correct value of the parameter -Dweblogic.Name.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150041: The server name {0} is unknown to the Administration Server. Check if restart is required.

Cause: The -Dweblogic.Name command line property specifies a server that does not exist in the configuration that is active on the Administration Server. This can occur if the Managed Server was added to the configuration along with non-dynamic changes that affect the Administration Server. In this case, the Administration Server must be restarted.

Action: Check to see if the Administration Server is marked as needing a restart. If it is, then restart the Administration Server before trying to start this Managed Server. Check the configuration for the list of configured servers.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-150042: The -Dweblogic.management.server value of {0} does not specify a port that has administrator privileges. Change the startup command to specify a -Dweblogic.management.server value of {1}. This server will remain in Managed Server independence mode until it is started with a port that has administrator privileges.

Cause: The specified Administration Server port does not support the administrator traffic required to allow the Managed Server to communicate with the Administration server.

Action: Change the -Dweblogic.management.server property to specify a port that has administator privileges.
Level: 1

Type: INTERNAL_ERROR

Impact: Configuration Management

BEA-150043: Cannot delete server {0} in domain {1} while the server is running. Please shut down the server in order to delete the server.

Cause: An attempt was made to delete a static or dynamic Managed Server while it was still running.

Action: Shut down the server and retry the change that deleted the server.
Level: 1

Type: ERROR

Impact: Configuration Management

BEA-159900: USER {0} CREATED {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159901: USER {0} CREATE {1} FAILED {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159902: USER {0} REMOVED {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159903: USER {0} REMOVE {1} FAILED {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159904: USER {0} MODIFIED {1} ATTRIBUTE {2} FROM {3} TO {4}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159905: USER {0} MODIFY {1} ATTRIBUTE {2} FROM {3} TO {4} FAILED {5}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159907: USER {0} INVOKED ON {1} METHOD {2} PARAMS {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159908: USER {0} INVOKED ON {1} METHOD {2} PARAMS {3} FAILED {4}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159909: USER {0}, configuration auditing is enabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159910: USER {0}, configuration auditing is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-159911: Invalid number {0} was found while encrypting clear text passwords.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration Audit

BEA-160001: Error deploying {0}: {1}

Cause: The application is misconfigured. See the logged exception for more details.

Action: Check the config.xml to ensure that the component MBean is wrapped in a valid application MBean and that it has a valid URI and target attribute. Check the server log for errors.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160032: Unable to create mbean Name: {0} Type: {1} Exception: {2}

Cause: See message body.

Action: See exception message logged.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160039: Failed to undeploy a mail session.

Cause: There was a JNDI unbind error.

Action: Check the error that is reported in the exception.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160040: Deployed MailSession named {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160041: Undeployed MailSession named {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160069: Error while looking for Web services files: {0}

Cause: An IOException occurred while accessing Web services files.

Action: See the stack trace for details.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160083: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. The ejb-jar file "{4}" could not be found in this EAR file.

Cause: The path to the target EJB does not exist in the application.

Action: The ejb-link must be fixed to point to the module containing the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160084: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. The ejb-jar file "{3}" could not be found in this ear file.

Cause: The path to the target EJB does not exist in the application.

Action: The ejb-link must be fixed to point to the module containing the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160085: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. The EAR module "{4}" does not contain an EJB with the name "{5}".

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160086: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. The EAR module "{3}" does not contain an EJB with the name "{4}".

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160087: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" did not resolve to a bean with component interfaces. Ensure that the link is correct.

Cause: The link did not resolve to a valid EJB.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160088: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" did not resolve to a bean with component interfaces. Ensure that the link is correct.

Cause: The link did not resolve to a valid EJB.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160089: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. No EJB named "{0}" with component interfaces exists in the application. Ensure that the link is correct.

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160090: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. No EJB named "{0}" with component interfaces exists in the application. Ensure that the link is correct.

Cause: The specified EJB does not exist in the module.

Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160091: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" is ambiguous. The following list of application modules contain an EJB with the name "{0}": {4}. Qualify this ejb-link to remove the ambiguity.

Cause: The ejb-link is unqualified and resolves to multiple EJBs in the application.

Action: The ejb-link must be fixed to point to a single EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160092: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" is ambiguous. The following list of application modules contain an EJB with the name "{0}": {3}. Qualify this ejb-link to remove the ambiguity.

Cause: The ejb-link is unqualified and resolves to multiple EJBs in the application.

Action: The ejb-link must be fixed to point to a single EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160093: Error: The ejb-link "{0}" declared in the {1} "{2}" for EJB "{3}" in the module "{4}" could not be established. The target of the ejb-link does not have {5} interfaces. Ensure that the link is correct.

Cause: The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action: Ensure that the target of the ejb-link is correct. If it is, either add component interfaces to this EJB that are compatible with the ref type or change the ref type to be compatible with the interfaces exposed by the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160094: Error: The ejb-link "{0}" declared in the {1} "{2}" in the module "{3}" could not be established. The target of the ejb-link does not have {4} interfaces. Ensure that the link is correct.

Cause: The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.

Action: Ensure that the target of the ejb-link is correct. If it is, either add component interfaces to this EJB that are compatible with the ref type or change the ref type to be compatible with the interfaces exposed by the target EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160095: Warning: The {0} "{1}" for EJB "{2}" in the module "{3}" has an invalid {4} element value "{5}". The target bean does not declare that {4} interface. Ensure that the values are correct.

Cause: The home or component interface name in the ejb-ref or ejb-local-ref does not match the home or component interface name of the target EJB.

Action: Ensure that the target of the ejb-link is correct. If it is, fix the ejb-ref or ejb-local-ref so that the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160096: Warning: The {0} "{1}" in the module "{2}" has an invalid {3} element value "{4}". The target bean does not declare that {3} interface. Ensure that the values are correct.

Cause: The home or component interface name in the ejb-ref or ejb-local-ref does not match the home, component or business interface name of the target EJB.

Action: Ensure that the target of the ejb-link is correct. If it is, fix the ejb-ref or ejb-local-ref so that the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160098: Unable to parse the file "{0}" because it uses an invalid encoding name, "{1}". All deployment descriptors must use an IANA or Java encoding name. Change the encoding of the descriptor to be a supported encoding.

Cause: The encoding name used by the deployment descriptor is not supported.

Action: Change the encoding name of the deployment descriptor to an IANA or Java encoding name.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160100: Could not deploy role: {0} for application: {1}.

Cause: The application could not deploy the role defined in application.xml.

Action: Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160101: Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the application module "{2}" could not be resolved. The target EJB for the ejb-ref could not be found. Ensure that the link is correct.

Cause: The target of the ejb-link could not be found in the application.

Action: Fix the ejb-link to point to a valid EJB.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160104: Invalid local reference in application {0}. A local reference from module {1} to {2} is not allowed because the referencing module does not have visibility to the classes of the referenced module.

Cause: The current module does not have visibility to the classloader of the EJB being referenced.

Action: Look at the classloader organization defined by the classloader-structure element in weblogic-application.xml and ensure that the calling module is either using the same classloader as the module containing the referenced EJB or that the calling module is using a classloader that is an offspring of the classloader of the EJB module.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160106: ERROR: The source file, "{0}", could not be found.

Cause: The source file could not be found.

Action: Ensure that the specified source file exists and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160108: ERROR: Error accessing input file "{0}": {1}

Cause: The source file could not be accessed.

Action: Ensure that the source file is accessible and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160109: ERROR: Error copying files to the directory "{0}": {1}

Cause: The compiler was unable to extract the source archive to a directory. This can be caused by a lack of permission to write to the directory or a lack of disk space.

Action: Ensure that the directory is writable and that there is enough free disk space to extract the archive. Alternatively, manually extract the archive to a directory and specify the directory name as the appc argument instead of the archive.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160110: ERROR: appc could not create the working directory, "{0}". Ensure that this directory can be created and try again.

Cause: A directory was specified in the appc command and it could not be created. appc will not be able to finish compiling the application because of this.

Action: Ensure that the directory can be created and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160111: ERROR: appc can not write to the working directory, "{0}". Ensure that you have write permission for this directory and try again.

Cause: The specified directory is not writable.

Action: Ensure that the directory is writable and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160112: Error: The directory, "{0}", does not contain a valid module. If the directory represents an EAR file, it must contain a META-INF/application.xml file. If the directory represents an ejb-jar file, it must contain a META-INF/ejb-jar.xml file. If the directory represents a WAR file, it must contain a WEB-INF/web.xml file. Ensure that the source directory is a valid module and try again.

Cause: The specified directory does not contain a valid module to compile.

Action: Ensure that the specified source directory contains a valid module and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160113: Error: The source file, "{0}", is not a valid ejb-jar file. To be valid, it must contain a META-INF/ejb-jar.xml file.

Cause: The specified source file is not a valid ejb-jar file.

Action: Ensure that the specified source file is a valid ejb-jar file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160114: Error: The source file, "{0}", is not a valid WAR file. To be valid, it must contain a WEB-INF/web.xml file.

Cause: The specified source file is not a valid WAR file.

Action: Ensure that the specified source file is a valid WAR file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160115: Error: The source file, "{0}", is not a valid EAR file. To be valid, it must contain a META-INF/application.xml file.

Cause: The specified source file is not a valid EAR file.

Action: Ensure that the specified source file is a valid EAR file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160117: appc is unable to continue processing file "{0}": {1}

Cause: An error occurred while processing the specified source file.

Action: Find the cause of the exception and take any necessary steps to remedy it.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160118: appc is unable to continue processing the file "{0}". The following error occurred while accessing it: {1}

Cause: An error occurred while processing the specified source file.

Action: Find the cause of the exception and take any necessary steps to remedy it.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160119: appc is unable to process the file "{0}". The following error occurred: {1}

Cause: An error occurred while processing the specified source file.

Action: Find the cause of the exception and take any necessary steps to remedy it.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160120: Error: The module, "{0}", is declared either in the application.xml or in the weblogic-application.xml descriptor but cannot be found in the EAR file.

Cause: The specified module cannot be found in the EAR file.

Action: Ensure that either the application.xml or the weblogic-application.xml declaration is correct.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160121: Errors encountered while compiling module "{0}": {1}

Cause: Errors were encountered while compiling the specified module.

Action: Investigate the specific errors and take any recommended actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160122: Errors validating EAR file: {0}

Cause: Errors were encountered while validating the EAR file.

Action: Investigate the specific errors and take any recommended actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160123: ERROR: Could not create output archive, "{0}", restoring previous archive. The error was: {1}

Cause: An error occurred while creating the output archive.

Action: Investigate the specific error and take any necessary actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160124: ERROR: Could not create output archive "{0}". The error was: {1}

Cause: An error occurred while creating the output archive.

Action: Investigate the specific error and take any necessary actions.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160125: ERROR: Could not delete old backup file: {0}.

Cause: An old backup file could not be removed.

Action: Determine why the old backup file could not be deleted and remedy the problem. Manually deleting the old backup file prior to running appc should fix this issue.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160126: ERROR: Could not create backup file "{0}". The error was: {1}

Cause: The specified backup file could not be created.

Action: Determine why the backup file could not be created and remedy the problem. In particular, ensure that you have write permission to the specified file and that the disk is not full.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160127: ERROR: Could not delete previous archive: {0}

Cause: The specified archive could not be removed.

Action: Determine why the archive could not be deleted and remedy the problem. In particular, ensure that you have permission to modify the specified file.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160128: ERROR: Incorrect appc command. Too many arguments were given. The appc command only takes a single argument, the source file, in addition to the supported options.

Cause: Too many arguments were specified in the appc command.

Action: Correct the command and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160129: ERROR: The alt-dd "{0}", specified for application module "{1}", could not be found. Remove the alt-dd entry from the application.xml descriptor or ensure that it points to a valid deployment descriptor.

Cause: The specified alt-dd could not be found.

Action: Remove the invalid alt-dd entry from application.xml or ensure that it points to a valid deployment descriptor.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160130: ERROR: The application level alt-dd "{0}", specified in the appc command, could not be found. Ensure that the alt-dd points to a valid deployment descriptor or remove it from the command line.

Cause: The specified alt-dd could not be found.

Action: Correct or remove the invalid alt-dd setting in the appc command.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160132: Warning: The {0} "{1}" for EJB "{2}" in the module "{3}" has an ejb-ref-type of {4} but the ejb-link does not resolve to an EJB of that type. Ensure that the ejb-link and ejb-ref-type are correct.

Cause: The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.

Action: Ensure that the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, ensure that the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160133: Warning: The {0} "{1}" in the module "{2}" has an ejb-ref-type of {3} but the ejb-link does not resolve to an EJB of that type. Ensure that the ejb-link and ejb-ref-type are correct.

Cause: The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.

Action: Ensure that the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, ensure that the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160134: Error: The EJB with the name "{0}" in ear module "{1}" has an entity-cache-ref with the name "{2}" in its weblogic-ejb-jar.xml descriptor but no application level entity cache with that name is defined in the weblogic-application.xml descriptor for the application.

Cause: The entity-cache referred to by the EJB could not be found.

Action: Ensure that the entity-cache-ref is correct in the weblogic-ejb-jar.xml descriptor for the EJB. Also, ensure that an entity-cache with the same name is declared in the weblogic-application.xml descriptor for the application.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160137: Error: The message-destination-link "{0}" declared in the message-destination-ref "{1}" in the application module "{2}" could not be resolved. The target message-destination for the message-destination-ref could not be found. Ensure that the link is correct.

Cause: The target of the message-destination-link could not be found in the application.

Action: Fix the message-destination-link to point to a valid message-destination.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160138: Could not set active version state for application: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160139: The following library reference has "context-path" set, which has no effect when referencing a {1} library: {0}.

Cause: The library reference has "context-path" set, but is not referencing a WAR library.

Action: Remove "context-path" from the library reference.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160140: Unresolved optional package references (in META-INF/MANIFEST.MF): {0}. Ensure that the referenced optional package has been deployed as a library.

Cause: One or more MANIFEST.MF files contain references to optional packages (using the Extension-List attribute). One or more of the referenced optional packages are not available.

Action: Register the required optional packages or remove the reference(s) from the manifest(s).
Level: 1

Type: WARNING

Impact: J2EE

BEA-160141: Could not initialize the library {0}. Ensure that the deployment unit is a valid library type (WAR, EJB, EAR, plain JAR). {1}

Cause: Refer to the exception in the message body.

Action: Examine the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160142: The library at {0} has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0; for example: 2.1.1

Cause: The Specification-Version for the library at {0} cannot be parsed.

Action: Fix the library Specification-Version to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160143: Library {0} has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.

Cause: The library cannot be statically deployed because its MBean has an invalid Specification-Version.

Action: Undeploy the library and deploy it again with a correct Specification-Version.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160144: Failed to register library {0}: {1}

Cause: The error is: {1}

Action: Examine the error message.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160145: Failed to deploy library {0}, because of conflicting library Manifest values, and library information registered with the server: {1}. Check the library MANIFEST.MF file and correct version information there to match server settings, or undeploy the misconfigured library.

Cause: Conflict between library manifest values and library settings in the LibraryMBean.

Action: Check the library MANIFEST.MF file and correct the version information there to match server settings, or undeploy the misconfigured library.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160146: Failed to process library at {0}, because of conflicting library manifest values and the library information provided on the appc command line: {1}.

Cause: There was a conflict between the library manifest values and the library information provided on the appc command line.

Action: Avoid setting the library name and version information on the appc command line if its already set in the manifest or remove values from the manifest and set them on the appc command line.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160147: One or more libraries could not be processed. See error above.

Cause: See error above.

Action: See error above.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160148: These libraries were not referenced by the compiled application: {0}.

Cause: The compiled application did not reference the libraries that were passed to appc.

Action: These libraries do not need to be passed to appc to compile this particular application.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160149: Error while processing library references. {0}

Cause: The application has library references that do not resolve.

Action: Ensure that the library references are accurate and that the required libraries are available.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160150: A library reference in weblogic-application.xml has an illegal Specification-Version: {0}. The Specification-Version must be a valid version string: int(.int)*, int >=0; example: 2.1.1

Cause: The Specification-Version of a library reference in weblogic-application.xml cannot be parsed.

Action: Fix the library Specification-Version in weblogic-application.xml to conform to the required version string syntax.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160151: Registered library {0}.

Cause: Library registration was successful.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160152: The library at {0} was not recognized as a valid library type.

Cause: The library at {0} was not recognized as a valid library type.

Action: Ensure that the library is one of the supported library types.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160153: Error while cleaning up library {0}: {1}

Cause: Error while cleaning up library {0}: {1}

Action: Examine the stack trace.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160154: Error while cleaning up library: {0}. {1}

Cause: Error while cleaning up library: {0}. {1}

Action: Examine the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160155: Cannot find library at: {0}.

Cause: {0} is not a file.

Action: Fix the path to the library.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160156: Cannot process libdir: {0} is not a directory.

Cause: {0} is not a directory.

Action: Fix the path to libdir.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160157: The referenced library, {0}, is not a supported application library.

Cause: {0} is not a supported application library.

Action: Remove the reference to library {0} from weblogic-application.xml.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160158: Ignoring Extension-List reference {0}, because the manifest does not have an entry for {0}-Extension-Name. The manifest is at {1}/META-INF/MANIFEST.MF

Cause: A declared Extension-List name does not have the required Extension-Name entry.

Action: Remove {0} from the Extension-List or add {0}-Extension-Name entry into the manifest.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160159: Bad optional package reference in manifest at {2}/META-INF/MANIFEST.MF, for optional package with Extension-Name: {0}. Illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0; example: 2.1.1. Ignoring this Optional Package reference.

Cause: Cannot parse the Specification-Version of an optional package reference.

Action: Change the optional package reference Specification-Version to the required version string syntax.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160161: Error while parsing the application descriptors for {0}: {1}.

Cause: The cause is {1}

Action: Examine the error message.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160162: No META-INF/application.xml was found in the EAR at {0}.

Cause: The application.xml file could not be found.

Action: Ensure that the path to the EAR file is correct and add the missing application.xml.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160163: No modules were found in application.xml for EAR: {0}. Nothing to do.

Cause: There are no modules in this EAR's application.xml

Action: Add module entries to the EAR's application.xml.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160164: Error while importing library {0}: {1}

Cause: See the exception: {1}.

Action: Examine the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160165: The EAR library at {0} is organized using the splitdir directory structure. splitdir is not supported for libraries.

Cause: splitdir is not supported for EAR libraries.

Action: Archive this library. If a build file was generated using BuildXMLGen, run the EAR target in that file.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160166: References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160167: The module {1} in application {0} uses ejb-links but no EJB modules were found for this application.

Cause: The ejb-links must correspond to an EJB module deployed within the same application.

Action: Ensure that the EJB modules to which you intended to link exist and have been configured properly.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160168: An error occurred while merging descriptors: {0}

Cause: An error occurred while merging descriptors. Check the stack trace.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160169: An error occurred while parsing descriptors: {0}

Cause: An error occurred while parsing descriptors.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160170: Imported library {0} for Application {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160171: ERROR: The plan file, "{0}", could not be found.

Cause: The plan file could not be found.

Action: Ensure that the specified plan file exists and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160172: ERROR: To run appc, specify a plan file ending with the suffix .xml.

Cause: The plan file type is not supported.

Action: Correct the plan argument and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160173: ERROR: Error accessing input file "{0}": {1}

Cause: The plan file could not be accessed.

Action: Ensure that the plan file is accessible and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160174: ERROR: Failed to parse deployment plan "{0}": {1}

Cause: The plan file could not be parsed.

Action: Resolve parse errors in the plan and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160175: ERROR: Could not find JMS module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JMS module used in the resource-link cannot be found in the application package.

Action: Package the missing JMS module as part of this application and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160176: ERROR: Could not find the JMS resource named "{4}" of type "{5}" inside the JMS module "{2}" that is specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JMS resource used in th resource-link was not found in the application package.

Action: Create the missing JMS resource in the corresponding JMS module and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160177: The application at "{0}" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, consult the WebLogic Server documentation.

Cause: The application was not a valid J2EE application.

Action: Correct the application and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160180: An error was encountered and ignored while rolling back an update to application {0}. The error was: {1}

Cause: See the included error message.

Action: Correct the application based on the reported error.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160181: An error was encountered and ignored during undeployment. The error was: {0}

Cause: See the included error message.

Action: Correct the application based on the reported error.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160182: An error was encountered and ignored during transition to administration mode. The error was: {0}

Cause: See the included error message.

Action: Correct the application based on the reported error.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160183: Unable to find the jar-uri: {1} specified for the ApplicationLifecycleListener, Startup, or Shutdown class in the weblogic-application.xml of application: {0}.

Cause: The JAR URI is incorrect or the file does not exist or cannot be read.

Action: Correct the application based on the reported error.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160184: ERROR: Could not find JDBC module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JDBC module used in the resource-link was not found in the application package.

Action: Package the missing JDBC module as part of this application and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160185: ERROR: Could not find the JDBC resource named "{4}" of type "{5}" inside the JDBC module "{2}" that is specified in the resource-link named "{3}" in the "{1}" component named "{0}".

Cause: The JDBC resource used in the resource-link was not found in the application package.

Action: Create the missing JDBC resource in the corresponding JDBC module and retry.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160186: Compiling EAR module "{0}"

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160187: weblogic.appc failed to compile the application. Recompile with the -verbose option for more details about the issue.

Cause: Compilation can fail for many reasons. See the specific error message for details.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, please contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160188: {0}.

Cause: The application has library references that do not resolve.

Action: Ensure that the library references are accurate and that the required libraries are available.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160189: There are no modules in the application that match URIs: {0}. Note that for Web applications, you should specify the context-root rather than the web-uri.

Cause: The specified URIs were not found in the running application.

Action: Specify the correct URIs which are typically found in your application's META-INF/application.xml.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160191: While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter has been deprecated and will be removed

Cause: This is a deprecated parameter.

Action: Remove the deprecated parameter from the weblogic.xml deployment descriptor.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160192: While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter is unknown and will be removed

Cause: The parameter is not defined in the schema.

Action: Check the weblogic.xml deployment descriptor and remove the parameter.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160193: Error: The source file, ''{0}'', is not a valid RAR file. To be valid, it must contain a META-INF/ra.xml file.

Cause: The specified source file is not a valid RAR file.

Action: Ensure that the specified source file is a valid RAR file and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160194: The following modules cannot be started because they are already running: {0}.

Cause: The specified modules are already running.

Action: Remove the specified modules from the list of modules to partially stop.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160195: The application version lifecycle event listener {1} is ignored because the application {0} is not versioned.

Cause: The application is not a versioned application.

Action: If the application is deployed as a non-versioned application in error, undeploy the current application and deploy it as a versioned application. If the application version lifecycle listener is specified in error, remove it from the application or specify a non-versioned application lifecycle listener.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160196: Unable to find the jar-uri: {1} specified for the Singleton class in the weblogic-application.xml of application: {0}

Cause: The JAR URI is incorrect or the file does not exist or cannot be read.

Action: Correct the application based on the reported error.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160197: Unable to load descriptor {1} of module {0}. The error is {2}.

Cause: The descriptor is not valid.

Action: Correct the descriptor based on the reported error.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160198: Error: The ejb-ref "{3}" configured via an @EJB annotation in the module "{0}" is linked to the EJB "{1}". However, the EJB "{1}" does not declare the interface "{2}", as specified by the @EJB annotation. Ensure that the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.

Cause: The @EJB has an incorrect beanName (ejb-link) attribute or the target bean must implement the interface declared by the @EJB annotation.

Action: Ensure that the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160199: Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not have an ejb-link and the JNDI name of the target Bean has not been specified.

Cause: Attempts to automatically link the ejb-ref to its target Bean failed because multiple EJBs in the application were found to implement the "{3}" interface, including {4}.

Action: Specify a qualified ejb-link for this ejb-ref to indicate which EJB is the target of this ejb-ref.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160200: Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the "{3}" interface. Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.

Cause: See the error message for details.

Action: Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160201: Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref specifies an ejb-link but the target bean does not implement the interface "{3}" as specified in the ejb-ref declaration. Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.

Cause: See the error message for details.

Action: Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160202: You have specified a {1} setting in your configuration for persistence unit {0}. This setting will be ignored and all log messages will be sent to the WebLogic Server logging subsystem. Trace-level logging is controlled by the various JPA-specific debug settings in config.xml, or through the WebLogic Server Administration Console.

Cause: Persistence unit configuration specifies logging information, but WebLogic Server will ignore this information.

Action: Remove the {1} setting from persistence unit {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160203: You have specified a {1} setting in your configuration for persistence unit {0}. This value will be replaced with {1}.

Cause: The persistence unit configuration specifies ID information, but WebLogic Server will ignore this information.

Action: Remove the {1} setting from persistence unit {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160204: The ApplicationLifecycleListener "{1}" of application "{0}" has a run-as user configured with the principal name "{2}" but a principal of that name could not be found. Ensure that a user with that name exists.

Cause: The run-as principal configured for this ApplicationLifecycleListener does not exist in the security realm.

Action: Ensure that the user exists or choose another principal for the run-as configuration.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160205: The ApplicationLifecycleListener "{1}" of application "{0}" has a run-as user configured with the principal name "{2}" but a principal of that name has higher privileges than the user performing the deployment. As a result, this deployment user cannot perform the current deployment action. Try the deployment action with an administrative privileged user.

Cause: Higher run-as privileges are needed to deploy an ApplicationLifecycleListener in this situation.

Action: Try the deployment action with an administrative privileged user.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160207: Error autowiring ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not specify an interfaceName but multiple interfaces on the target bean were found. Specify a beanInterface to indicate which EJB is the target for ejb-ref "{0}".

Cause: There was a problem resolving the target of the specified ejb-ref.

Action: Specify a beanInterface to indicate which EJB is the target.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160210: ERROR: The moduleUri, "{0}", could not be found.

Cause: The moduleUri could not be found.

Action: Ensure that the specified moduleUri exists and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160211: Waiting for ExecuteQueue {0} to finish {1} pending requests

Cause: The server found pending requests in one of the execute queues while suspending. The server will wait for the requests to complete.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160212: This is an unexpected exception.

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160213: * This directory contains internal files used by the deployment system. * Contents of this directory should never be removed while the corresponding server is running. * Removing sub-directories when the server is down will slow down the subsequent deployment of the corresponding applications because these sub-directories need to be created again. * The individual sub-directories are removed when the corresponding application is undeployed.

Cause: TBD

Action: TBD
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160214: Output location exists {0}

Cause: The file pointed to by the output location already exists,

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160215: ERROR: The moduleUri, "{0}", is not Web module.

Cause: The moduleUri is not valid Web module.

Action: Ensure that the specified moduleUri is a valid Web module and try again.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160216: Unexpected errors occurred while sending deployment event {1} on behalf of application ''{0}''.

Cause: The deployment event listener(s) registered to receive deployment event caused unexpected exceptions when processing deployment event {1} on behalf of application ''{0}''.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160217: Unexpected errors occurred while sending a vetoable deployment event on behalf of application ''{0}''.

Cause: The deployment event listener(s) registered to receive vetoable deployment events caused unexpected exception(s) when processing deployment event {1} on behalf of application ''{0}''.

Action: Report this problem to My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160218: Filtering classloader configuration ignored for module {1} of application {0}

Cause: Filtering classloader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone Web applications). Such configuration is not supported in modules of an enterprise application.

Action: Remove the filtering classloader configuration from the deployment descriptor of module {1} of application {0}.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160219: The JPA persistence unit {0} will use the following configured default persistence provider: {1}

Cause: No provider element was specified in the associated persistence.xml file.

Action: No action is required unless you want a different JPA provider to be used for the given persistence unit, in which case you can specify the provider in the persistence.xml file or change the default provider for the domain.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160220: Compilation completed successfully.

Cause: The compilation task has completed successfully.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160221: env-entry for type java.lang.Character had length = 0.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160222: Could not create a new JMS ConnectionFactory for the application: {0}.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160223: The resource-env-ref ''{0}'' declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic proprietary descriptor or corresponding annotation.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160224: Encountered an error cleaning up references for application: ${0} - ${1}

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160225: A new JPA API method is being invoked against an older version of the persistence provider, in which the method is not supported yet. Update the application to use a compliant provider, or ensure that the application does not attempt to invoke unsupported methods that are not supported by the current provider.

Cause: A new JPA API method is being invoked against an older version of the persistence provider, in which the method is not supported yet.

Action: Update the application to use a compliant provider, or ensure that the application does not attempt to invoke unsupported methods that are not supported by the current provider.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160226: Ignoring the configuration file [{0}: {1}]. Only applications that use Kodo as the JPA provider can be configured with this file.

Cause: This file can configure only persistence units that use Kodo.

Action: Remove the configuration file or specify the information in persistence.xml; otherwise, one or more persistence units in this application use Kodo.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160227: The persistence unit "{0}" in "{1}" does not use Kodo as a JPA provider. Ignoring the configuration for this persistence unit found in persistence-configuration.xml.

Cause: The persistence-configuration.xml file cannot configure persistence units that do not use Kodo.

Action: Remove the persistence unit from the persistence-configuration.xml file or specify in persistence.xml, or otherwise, that the persistence unit uses Kodo.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160228: AppMerge failed to merge your application. If you are running AppMerge on the command-line, merge again with the -verbose option for more details. See the error message(s) below.

Cause: AppMerge can fail for many reasons. See the specific error message for details.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160229: Ignoring plan file {0} as does not exist.

Cause: Either the plan specified is not a file or the plan file does not exist.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: J2EE

BEA-160230: Created working directory: {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE

BEA-160231: Unable to identify application type for {0}

Cause: The source file type may not be supported.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160232: Unable to identify module type for {0}

Cause: The module specified in the application descriptor may not be supported.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160233: Unable to identify module type

Cause: A module specified in the application descriptor may not be supported.

Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160238: The message-destination {0} declared in the deployment descriptor or by annotation does not have a corresponding message-destination-descriptor element in the weblogic deployment descriptor or corresponding annotation. Alternatively, mapped-name or lookup-name of message-destination can be specified for the destination.

Cause: A declared message-destination is not mapped correctly.

Action: Map the declared message-destination to the actual message destination using the message-destination-descriptor element in the weblogic deployment descriptor, or specify mapped-name or lookup-name of message-destination.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160239: Conflicting environment entry {0}, name is {1}.

Cause: They have same environment entry name, but have different value.

Action: Make sure they have different environment entries names. Or have same names with identical values.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160240: The resource-ref ''{0}'' declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic proprietary descriptor or corresponding annotation.

Cause: See the error message body.

Action: See the error message body.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160241: Error: There are environment entries conflict in module {0}. Multiple environment entries are defined with the same name but different values. {1}

Cause: With an EJB in WAR files, it is possible that environment entries names may clash. Care must be taken by the deployer or application assembler to avoid these name collisions, as they can cause the application to fail.

Action: Make sure they have different environment entries names. Or have same names with identical values.
Level: 1

Type: ERROR

Impact: J2EE

BEA-160242: Warning: Data source definition {0} in interceptor {1} may have been overwritten by EJB component in module {2}, ignored.

Cause: EJB component may overwrite data source definitions in its interceptors. In this case, data source definitions in interceptors will be ignored.

Action:
Level: 1

Type: WARNING

Impact: J2EE

BEA-160243: A creating StoredProcedureQuery API method is being invoked on a container-managed and transaction-scoped EntityManager outside of a transaction, but the method is not supported yet. Update the application to start a transaction before creating the StoredProcedureQuery objects.

Cause: A creating StoredProcedureQuery API method is being invoked on a container-managed and transaction-scoped EntityManager outside of a transaction, but the mehtod is not supported yet.

Action: Update the application to start a transaction before creating the StoredProcedureQuery objects.
Level: 1

Type: ERROR

Impact: J2EE

BEA-169800: A PooledConnectionFactory object with an invalid external version of {0} was found.

Cause: The version of WebLogic Server that stored the PooledConnectionFactory object is not compatible with the version that is retrieving it.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169801: The JMS method {0} may not be called inside an EJB or servlet.

Cause: The application code has violated the J2EE specifications.

Action: Change the code to avoid calling the specified method.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169802: Cannot create a wrapped JMS connection using a username and password when the res-auth element is set to Container.

Cause: The application code is not using the J2EE APIs properly.

Action: Either remove the username and password, or set the res-auth element to Application.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169803: JNDI lookup of the JMS connection factory {0} failed

Cause: The remote JNDI server or JMS server is not available, or the name was incorrectly specified.

Action: Check that the server is running, and check the name in the deployment descriptor XML files.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169804: Cannot use a JMS connection factory because the object is of the wrong type.

Cause: Either the name of the connection factory in the deployment descriptor XML files is wrong, or the wrong object was bound into JNDI.

Action: Check the name in the XML files against what is actually registered in JNDI.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169805: A pooled JMS connection is being closed because an error was detected on the connection: {0}

Cause: The JMS server is unavailable or there is some other problem with it that makes it impossible to send or receive messages.

Action: Check the configuration parameters for the JMS server, and check that it is available on the network.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169806: Cannot use a JMS destination because the object is of the wrong type.

Cause: Change the application to use a valid destination type.

Action: Change the application to use a valid destination type.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169807: There was an error while making the initial connection to the JMS resource named {0} from within an EJB or a servlet. The server will attempt the connection again later. The error was {1}

Cause: See the error message from the JMS provider.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169808: There was an error while making the initial connection to the JMS resource named {0} from the EJB "{1}" inside application "{2}". The server will attempt the connection again later. The error was {3}

Cause: See the error message from the JMS provider.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169809: An error occurred while registering the JMS connection with JTA.

Cause: The JMS connection factory specified does not properly support XA or something is wrong with the transaction system.

Action: Check the linked exception and verify that the JMS provider properly supports XA.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169810: An error occurred while committing or rolling back a JTA transaction used for a JMS operation by the J2EE container

Cause: There was a problem with the transaction system.

Action: See the linked exception for more information.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169811: The JMS object may not be used because it has been closed.

Cause: The object has been closed.

Action: Fix the programming error.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169812: The pooled JMS session is enlisted in another transaction and may not be used elsewhere.

Cause: Check the application code to ensure that a pooled JMS session (retrieved from the JNDI java:comp/env/jms context) is not kept between transactions. It should be closed so that it is returned to the pool.

Action: Check the application code.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169813: There was an error while closing a JMS session pool or a pooled JMS connection: {0} The pool or object was forcibly closed.

Cause: See the linked exception for more information.

Action: No action is required.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169814: The JMS session pool has been disabled.

Cause: An administrative action was taken.

Action: Re-enable the session pool.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169815: A JMS session pool could not be created because the {0} property was not specified.

Cause: If the JMSSessionPool class is not being used directly by the user, then this is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169816: The JMS session pool is shutting down.

Cause: The pool is being shut down, possibly because of an error.

Action: Check for other errors that indicate why the pool is being shut down and retry the operation.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169817: The JMS connection factory resource {0} declared in the EJB "{1}" as part of application "{2}" does not support XA. It cannot be used inside a transaction context.

Cause: If the specified JMS connection factory is intended to be used inside a transaction context, then the EJB was configured improperly.

Action: If the specified JMS connection factory is intended for use inside a transaction context, then the connection factory used by the EJB must be changed so that it supports XA, or the EJB descriptor must be changed to point to a different connection factory. However, if the connection factory will never be used inside a transaction context, then no action is necessary.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169818: The JMS connection pool named "{0}" has a configured connection factory JNDI name of "{1}". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "{2}".

Cause: An object other than a ConnectionFactory is bound to the configured JNDI name of the connection pool.

Action: Either change the JNDI name of the JMS connection pool property or change the JNDI name of the object that is currently bound into JNDI.
Level: 1

Type: WARNING

Impact: JMSPool

BEA-169819: There was an error with a resource pool used to pool JMS sessions

Cause: There is a problem with the resource pool.

Action: See the linked exception for details.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169820: A JMS message consumer could not be created using a temporary queue or topic that was created using another connection.

Cause: This is an application programming error.

Action: Change the application code.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169821: Error creating or instantiating a wrapper for class {0}

Cause: There may be an error with the classpath or with the underlying JMS provider's code.

Action: Check the classpath. If this does not fix the problem, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169822: Unable to use a wrapped JMS session in the transaction because two-phase commit is not available.

Cause: The JMS connection factory specified does not support two-phase commit.

Action: For WebLogic Server JMS, two-phase commit may be enabled by setting the "UserTransactionsEnabled" flag on the JMS connection factory. For other JMS providers, you must specify a JMS connection factory that supports XA.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169823: Failure occured on createQueueConnection. Unexpected return type.

Cause: Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createQueueConnection() API. Some JMS providers do not support backward compatibility.

Action: Either change the API call to createConnection() or change the connection factory type to QueueConnectionFactory.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-169824: Failure occured on createTopicConnection. Unexpected return type.

Cause: Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createTopicConnection() API. Some JMS providers do not support backward compatibility.

Action: Either change the API call to createConnection() or change the connection factory type to TopicConnectionFactory.
Level: 1

Type: ERROR

Impact: JMSPool

BEA-170003: The DomainLogfile Handler is unable to open the domain logfile {0}. The domain logfile is disabled.

Cause: The filepath specified for the domain log is invalid or the server process cannot write to the domain log file.

Action: Specify a valid filepath for the domain log file.
Level: 1

Type: INTERNAL_ERROR

Impact: Log Management

BEA-170011: The LogBroadcaster on this server failed to broadcast log messages to the Administration Server. The Administration Server may not be running. Message broadcasts to the Administration Server will be disabled.

Cause: The Managed Server may not be able to reach the Administration Server. One of the possible causes could be that the Administration Server is shut down.

Action: To fix this problem, inspect the exception stack trace, and correct the problem. If the Administration Server is shut down, restart it to resume normal log broadcasting to the domain.
Level: 1

Type: WARNING

Impact: Log Management

BEA-170019: The server log file {0} is opened. All server side log events will be written to this file.

Cause: This message is for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170020: The server log file {0} could not be opened successfully.

Cause: The filepath configured for the server's log file is not valid.

Action: Please specify a valid filepath for the server's log file.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170022: Log4j failed to initialize for {0}. The default JDK Logging implementation will be used.

Cause: The Log4j libraries may not be in the server CLASSPATH.

Action: Take corrective action based on the stack trace details.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170023: The Server Logging is initialized with Java Logging API implementation.

Cause: This message is for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170024: The Server Logging is initialized with Apache's Log4j Logging API implementation.

Cause: This message is only for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170025: Initialized Domain Logging. Domain log events will be written to {0}.

Cause: This message is for informational purposes.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170027: The server has successfully established a connection with the Domain level Diagnostic Service.

Cause: The server has successfully established contact with the Domain Diagnostic Service.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170028: The remote handler is not available, so the trap notification information can not be sent.

Cause: The Managed Server may not be able to reach the Administration Server. One of the possible causes could be that the Administration Server is shut down.

Action: If the Administration Server is shut down, restart it to resume normal communication for the domain.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170029: The data gathering handler could not be initialized.

Cause: An error occurred while initializing the data gathering handler.

Action: Review the nested exception details for the cause.
Level: 1

Type: WARNING

Impact: Log Management

BEA-170030: There was an error initializing the global Log4j configuration.

Cause: The error could be due to incorrect configuration parameters in the log4j configuration file.

Action: Review the nested exception details for the cause.
Level: 1

Type: ERROR

Impact: Log Management

BEA-170031: The default Server Logging bridge has been initialized successfully.

Cause: This message is logged for informational purpose only.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-170032: The Server has detected ODL configuration for java.util.logging. The PlatformLoggerLevels attribute configuration on the LogMBean will be ignored.

Cause: This message is logged for informational purpose only.

Action: Users should specify the java.util.logging Logger Level configuration with ODL.
Level: 1

Type: NOTIFICATION

Impact: Log Management

BEA-171500: The embedded LDAP configuration file: {0} was not found, and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).

Cause: The embedded LDAP server cannot find the specified file. This file is installed as part of the installation process. Most likely, the default directory is not the server root directory and the lib subdirectory cannot be found.

Action: Set the default directory to the server root directory, or use the weblogic.EmbeddedLDAPConfigDirectory system property to set the location of the embedded LDAP server configuration files.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171503: The listen address for the Administration Server is obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property. None of these returned a listen address.

Cause: The listen address was null.

Action: Check if the listen address for the Administration Server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171507: The embedded LDAP replica file: {0} could not be written. The underlying exception was {1}.

Cause: An exception occurred when saving the replica properties to the replicas file.

Action: Verify that the file {1} can be written. Read the exception text for more information in diagnosing the problem.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171512: When attempting to clean up after a failed embedded LDAP replica initialization, the file {0} could not be deleted. The {1} directory and all its files must be deleted manually.

Cause: It is not always possible to delete files that are open by a process.

Action: Delete the {1} directory and all its files manually using the appropriate command for the operating system on which WebLogic Server runs.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171513: Could not schedule the trigger used for embedded LDAP timer activities. The underlying exception was {0}.

Cause: A TimeTrigger exception occurred when scheduling the trigger.

Action: See the exception text in {0} for more information on diagnosing the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171517: An error occurred while attempting to obtain exclusive access to the embedded LDAP data files directory: {0}. The exception that occurred is {1}.

Cause: An exclusive lock for the directory {0} could not be obtained because an exception occurred.

Action: Investigate the associated exception to determine why the exclusive lock failed.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171518: The following exception has occurred:

Cause: An error condition has occurred.

Action: Read the associated exception in the log. In general, a stack trace will help when debugging an existing problem.
Level: 1

Type: NOTIFICATION

Impact: EmbeddedLDAP

BEA-171519: Could not obtain an exclusive lock to the embedded LDAP data files directory: {0} because another WebLogic Server instance is already using this directory. Ensure that the first WebLogic Server instance is completely shut down and restart the server.

Cause: An exclusive lock for the directory {0} could not be obtained because another WebLogic Server is already using this directory.

Action: Ensure that the first WebLogic Server instance is shut down and try restarting the server.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171520: Could not obtain an exclusive lock for directory: {0}. Waiting for {1} seconds and then retrying in case the existing WebLogic Server instance is still shutting down.

Cause: An exclusive lock for the directory {0} could not be obtained because another WebLogic Server is already using this directory.

Action: If the server eventually boots, ignore this warning as the lock was obtained. If the server fails to boot, ensure that the first WebLogic Server is shut down and try restarting the server.
Level: 1

Type: WARNING

Impact: EmbeddedLDAP

BEA-171521: An error occurred while initializing the embedded LDAP server. The exception that occurred is {0}. This may indicate a problem with the data files for the embedded LDAP server. This Managed Server has a replica of the data contained on the master embedded LDAP server in the Administration Server. This replica has been marked invalid and will be refreshed on the next boot of the Managed Server. Try to reboot this server.

Cause: There may be a problem with either the embedded LDAP server configuration files or the data files.

Action: Investigate the associated exception to determine why the exception occurred. Try to reboot the server and see if the refresh of the replica data files solves the problem.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171522: An error occurred while initializing the embedded LDAP server. The exception that occurred is {1}. This may indicate a problem with the data files for the embedded LDAP server. If the problem is with the data files, and it cannot be corrected, backups of previous versions of the data files exist in {0}.

Cause: There may be a problem with either the embedded LDAP server configuration files or the data files.

Action: Investigate the associated exception to determine why the exception occurred. Try to reboot the server.
Level: 1

Type: INTERNAL_ERROR

Impact: EmbeddedLDAP

BEA-171523: Embedded LDAP server Credential unavailable: a credential value must be supplied for the embedded LDAP configuration.

Cause: The Credential attribute is invalid.

Action: Set the Credential attribute for the embedded LDAP server configuration.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171524: Cannot determine the listen address for the Administration Server. The Administration Server URI {0}, obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property, has invalid syntax.

Cause: The Administration Server URI has invalid syntax.

Action: Ensure that a valid listen address for the Administration Server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171525: Error loading initial replica file. Check the EmbeddedLDAP log for more details.

Cause: An error occurred during the loading of the initial replica file.

Action: Check the EmbeddedLDAP log for more details.
Level: 1

Type: ERROR

Impact: EmbeddedLDAP

BEA-171526: Error loading the initial replica file, attempting to reload.

Cause: An error occurred during the loading of the initial replica file.

Action: No action is required. The initial replica file will be loaded again.
Level: 1

Type: NOTIFICATION

Impact: EmbeddedLDAP

BEA-171527: Added all LDAP entries successfully for the initial replica.

Cause: An error occurred during the initial loading of the replica file.

Action: No action is required. The reload of the initial replica file was successful.
Level: 1

Type: NOTIFICATION

Impact: EmbeddedLDAP

BEA-180000: Start parsing the configuration MBean information.

Cause: All other initialization has completed, and this method is now ready to begin reading its own configuration information.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180001: WTC finished parsing the configuration MBean information.

Cause: All WTC configuration MBeans were parsed without any problems.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180002: Invalid attributes exception occurred while trying to create subcontext: {0}

Cause: An attempt was made to add an attribute set that has been specified incompletely or incorrectly.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180003: Naming exception error: {0}

Cause: The specified name could not be resolved.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180004: Name already bound error: {0}

Cause: The name used by the Tuxedo connection factory or Tuxedo CORBA connection factory already bonded to another object.

Action: Do not use the same name as the Tuxedo or Tuxedo CORBA connection factory.
Level: 1

Type: ERROR

Impact: WTC

BEA-180005: Invalid attributes exception when binding connection factory: {0}

Cause: An attempt was made to add an attribute set that has been specified incompletely or incorrectly.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180006: Naming exception error: {0}

Cause: The specified name could not be resolved.

Action: This is an internal error. Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180007: Unable to register the resource with transaction manager: {0}.

Cause: WebLogic Tuxedo Connector (WTC) was not running with the server transaction manager.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180008: A transaction identifier exists for a non-existent domain {0}.

Cause: The remote Tuxedo domain involved in the transaction is no longer in the WebLogic Tuxedo Connector (WTC) configuration.

Action: Manually correct the transaction. If the removal of the remote Tuxedo domain is intentional, temporarily add the remote Tuxedo domain back to the configuration and wait for the transaction to complete. Otherwise, add the Tuxedo domain back to the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180009: Could not complete the execution for the MBean named: {0}.

Cause: The definition contains input information that is not consistent with the usage model.

Action: Check the MBean definition to see if the individual attributes are consistent with the rest of the MBean definitions.
Level: 1

Type: ERROR

Impact: WTC

BEA-180010: Could not create a TDMLocalTDomain {0}.

Cause: The AccessPoint attribute definition for the WTCLocalTuxDom MBean was invalid.

Action: Check the AccessPoint attribute of the WTCLocalTuxDom MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180011: Could not create a TDMRemoteTDomain {0}.

Cause: The AccessPoint attribute definition for the WTCRemoteTuxDom MBean was invalid.

Action: Check the AccessPoint attribute of the WTCRemoteTuxDom MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180012: The LocalTDomain {0} is unknown.

Cause: The LocalAccessPoint attribute for the WTCRemoteTuxDom MBean is not a valid name for a LocalTDomain.

Action: Verify that the WTCRemoteTuxDom MBean definition has a valid name for the LocalAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180013: The LocalTDomain {0} is unknown.

Cause: The LocalAccessPoint attribute for the WTCExport MBean is not a valid name for a LocalTDomain.

Action: Verify that the WTCExport MBean definition has a valid name for the LocalAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180014: Could not create a TDMExport {0}.

Cause: The ResourceName attribute definition for the WTCExport MBean is invalid or the LocalTDomain is not usable.

Action: Check the ResourceName attribute of the WTCExport MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180015: The LocalTDomain {0} is not known.

Cause: The LocalAccessPoint attribute for the WTCImport MBean is not a valid name for a LocalTDomain.

Action: Confirm that the WTCImport MBean definition has a valid name for the LocalAccessPoint Attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180016: The RemoteTDomain {0} is unknown.

Cause: The RemoteAccessPointList attribute for the WTCImport MBean does not contain a valid name for a RemoteTDomain.

Action: Verify that the WTCImport MBean definition has valid names in a comma-separated list defined in the RemoteAccessPointList attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180017: Could not create a TDMImport {0}.

Cause: The ResourceName attribute definition for the WTCImport MBean is invalid. The LocalTDomain or the RemoteTDomains are not usable.

Action: Check the ResourceName attribute of the WTCImport MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180018: Missing {0} Password or PasswordIV information.

Cause: The Password or PasswordIV attribute is not set.

Action: Verify that the Password and PasswordIV attributes are valid.
Level: 1

Type: ERROR

Impact: WTC

BEA-180019: The LocalTDomain {0} is unknown.

Cause: The LocalAccessPoint attribute for the WTCPassword MBean is not a valid name for a LocalTDomain.

Action: Verify that the WTCPassword MBean definition has a valid name for the LocalAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180020: The RemoteTDomain {0} is unknown.

Cause: The RemoteAccessPoint attribute for the WTCPassword MBean is not a valid name for a RemoteTDomain.

Action: Verify that the WTCPassword MBean definition has a valid name for the RemoteAccessPoint attribute.
Level: 1

Type: ERROR

Impact: WTC

BEA-180021: Could not create a TDMPasswd {0}.

Cause: The LocalTDomain or the RemoteTDomain is not usable.

Action: Check the LocalAccessPoint and RemoteAccessPoint attributes of the WTCPassword MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180022: Could not set up the field table information for TDMResources: {0}.

Cause: The fully qualified name for any field table may be incorrect or could not be found.

Action: Check the FldTblClass definitions of the WTCResources MBean and verify that the fully qualified name is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.
Level: 1

Type: ERROR

Impact: WTC

BEA-180023: Commit of Xid failed with status {0}.

Cause: The transaction became a heuristic hazard, or the resource manager encountered an error.

Action: Correct the transaction manually if it became a heuristic hazard, or correct the resource manager problem.
Level: 1

Type: ERROR

Impact: WTC

BEA-180024: Unable to reply to unknown transaction with exception: {0}.

Cause: The connection to the remote Tuxedo domain was already terminated or an IOException occurred while writing to the network.

Action: If the TPException is TPEPROTO, try to reboot the remote Tuxedo domain. If the TPException is TPESYSTEM, check the network connection.
Level: 1

Type: ERROR

Impact: WTC

BEA-180025: Unknown field type requested {0}.

Cause: TypedFML32 data is possibly being used instead of TypedFML.

Action: Verify that the type of input data is correct.
Level: 1

Type: ERROR

Impact: WTC

BEA-180026: While trying to use FML data, this Ferror exception occurred: {0}

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180027: While trying to use FML data, an Unknown exception occurred: {0}

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180028: Unknown field type requested {0}.

Cause: Possibly, TypedFML data is being used instead of TypedFML32.

Action: Verify that the type of input data was correct.
Level: 1

Type: ERROR

Impact: WTC

BEA-180029: The Ferror exception: {0} occurred. Additional exception information found: {1}.

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180030: While trying to use FML32 data, an Unknown exception occurred: {0}

Cause: The data was not created correctly.

Action: Check the data that was passed into this method.
Level: 1

Type: ERROR

Impact: WTC

BEA-180031: XML argument is null.

Cause: The argument that was passed in was not initialized.

Action: Check the XML argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180032: The FldTbl[] input argument is null or an empty array.

Cause: The argument that was passed in was not initialized.

Action: Check the FldTbl[] argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180033: TypedFML argument is null.

Cause: The argument that was passed in was not initialized.

Action: Check the TypedFML argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180034: An error occurred while searching {0} for the document root element.

Cause: The input XML string was not formatted correctly.

Action: Check for other listed errors that should indicate what was unacceptable about the XML input.
Level: 1

Type: ERROR

Impact: WTC

BEA-180035: TypedFML32 argument is null.

Cause: The argument that was passed in was not initialized.

Action: Check the TypedFML32 argument that was passed in.
Level: 1

Type: ERROR

Impact: WTC

BEA-180036: XML input {0} caused the SAX parser exception {1}

Cause: The Document Object Model (DOM) parser did not accept the XML string that it received.

Action: Check the SAX exception information that was returned and the XML string that was entered.
Level: 1

Type: ERROR

Impact: WTC

BEA-180037: XML input {0} caused IOException {1}.

Cause: The XML string was not convertible to an InputSource() class.

Action: Check the IOException information that was returned and the XML string that was entered.
Level: 1

Type: ERROR

Impact: WTC

BEA-180038: XML input {0} caused an unknown exception {1}.

Cause: The XML string was not able to be parsed.

Action: Check the exception information that was returned and the XML string that was entered.
Level: 1

Type: ERROR

Impact: WTC

BEA-180039: The DOM parser returned a null value for input {0}.

Cause: The input may not be a valid XML string.

Action: Check the string that was passed to the parser.
Level: 1

Type: ERROR

Impact: WTC

BEA-180040: Could not obtain a top document element from input {0}.

Cause: The XML input did not have any elements defined.

Action: Verify that the input string has a proper definition for a root element.
Level: 1

Type: ERROR

Impact: WTC

BEA-180041: Could not obtain a tag name for the root element in XML input {0}.

Cause: The XML input does not have a tag name for the root element.

Action: Verify that the root element has a proper definition.
Level: 1

Type: ERROR

Impact: WTC

BEA-180042: Internal TypedFML data is null.

Cause: The internal data that is using the XMLtoFML() API was not initialized.

Action: Use XMLtoFML to initialize the internal data.
Level: 1

Type: ERROR

Impact: WTC

BEA-180043: XML element name is null.

Cause: The XML element information was not properly defined.

Action: Check the XML element definition.
Level: 1

Type: ERROR

Impact: WTC

BEA-180044: XML element value is null for the element name {0}.

Cause: The XML element information was not properly defined.

Action: Check the XML element definition.
Level: 1

Type: ERROR

Impact: WTC

BEA-180045: Internal TypedFML32 data is null.

Cause: The internal data that was using the XMLtoFML32() API was not initialized.

Action: Use XMLtoFML32 to initialize the internal data.
Level: 1

Type: ERROR

Impact: WTC

BEA-180047: The tBridge must have at least one redirect command.

Cause: The tBridge was not configured properly.

Action: At least one redirect command must be configured in the WTC_CONFIG for the tBridge section.
Level: 1

Type: ERROR

Impact: WTC

BEA-180048: The tBridge cannot find the TuxedoConnectionFactory.

Cause: The WebLogic Tuxedo Connector (WTC) was not properly configured.

Action: Review the WTC documentation and restart the WTC.
Level: 1

Type: ERROR

Impact: WTC

BEA-180049: The tBridge cannot locate the WLXT option for translation.

Cause: The WLXT package might not be loaded or might be in the proper CLASSPATH.

Action: Install the WLXT and properly configure the translator option.
Level: 1

Type: ERROR

Impact: WTC

BEA-180050: The tBridge internal FML-to-XML conversion failed.

Cause: The syntax of the incoming message could not be understood.

Action: Correct the message syntax and retry.
Level: 1

Type: ERROR

Impact: WTC

BEA-180052: Unable to cancel ON_STARTUP connection retry due to: {0}.

Cause: The timer service object for the ON_STARTUP connection policy could not be deleted during connection termination.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180053: Failure occurred during the token creating token: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support to report this problem with the token type information found in the log message.
Level: 1

Type: ERROR

Impact: WTC

BEA-180054: Failure occurred while reading the received domain security token: {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support to report this problem with the token type information found in the log message.
Level: 1

Type: ERROR

Impact: WTC

BEA-180055: Received an unexpected token type, error information({0}, {1}, {2}).

Cause: The cause could be that WTC communicates with a newer version of the TDomain protocol or an unknown alien protocol, or a breach of security attempt was detected.

Action: Verify who is trying to connect to this WTC and determine whether there is a security violation or a need to upgrade WTC to a newer version.
Level: 1

Type: ERROR

Impact: WTC

BEA-180056: atntd(1) crypto error: {0}

Cause: There was not enough free memory space to continue, or an internal error occurred.

Action: Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180057: Invalid return challenge

Cause: This is caused by an incorrect configuration and mismatched password.

Action: Correct the configuration and the password.
Level: 1

Type: ERROR

Impact: WTC

BEA-180058: atntd(3) I/O error: {0}

Cause: This is an internal system error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180059: atntd(2) crypto error: {0}

Cause: There is not enough free memory space to continue, or an internal error occurred.

Action: Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180063: Invalid handler address length: {0}.

Cause: The client did not talk to a valid listener.

Action: Check the listener address and correct the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180067: WSRPCRQ discriminator {0} is invalid.

Cause: The client is not talking to a valid handler.

Action: Check the configuration and correct the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180068: Invalid WSRPCRQ type {0}.

Cause: The client is not talking to a valid handler.

Action: Check the configuration and correct it.
Level: 1

Type: ERROR

Impact: WTC

BEA-180069: Unable to read {0}. The following exception occurred: {1}.

Cause: A general I/O exception occurred.

Action: Read the exception description to determine the actual cause and act accordingly.
Level: 1

Type: ERROR

Impact: WTC

BEA-180070: TypeFML32 received a pointer of unknown type {0}. Will replace with null.

Cause: The application was incorrectly written with an unknown data type.

Action: Correct the data type in the application.
Level: 1

Type: WARNING

Impact: WTC

BEA-180071: Invalid typed FML32 field {0}. Equals null.

Cause: The embedded FML32 buffer was incorrectly constructed in the FML32 buffer.

Action: Check the source of the embedded FML32 buffer, and correct the problem.
Level: 1

Type: WARNING

Impact: WTC

BEA-180074: The tpinit buffer was not received.

Cause: The server is likely talking to an invalid handler.

Action: Check the configuration and correct the problem.
Level: 1

Type: ERROR

Impact: WTC

BEA-180075: Invalid receive size {0}

Cause: The remote tuxedo domain gateway is not valid.

Action: Check the configuration of the remote Tuxedo domain and correct the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180076: Unable to format password. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check for system memory usage and see if force garbage collection is possible. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180077: Unable to close the domain socket. The following exception occurred: {0}.

Cause: An I/O error occurred while closing the socket.

Action: Check the network and system environment. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180078: Dropping OWS_AREPLY on ground.

Cause: The ACALL request already timed out.

Action: No action is required. This message is informational only.
Level: 1

Type: WARNING

Impact: WTC

BEA-180079: rsession.run read_tfmh failed.

Cause: The received message header is not properly formatted or it failed to decompress the data.

Action: Check the configuration of the remote Tuxedo domain and correct any problem in the configuration. Ensure that a supported version of the remote Tuxedo domain is being used. Also, check the network for possible network dropping of the packet. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180080: rsession.run tmmsg.ws was not provided.

Cause: There is no connection with a valid remote Tuxedo domain.

Action: Check the remote Tuxedo domain configuration and correct the problem.
Level: 1

Type: ERROR

Impact: WTC

BEA-180081: Unexpected close on rsession socket. The following exception occurred: {0}

Cause: An I/O error occurred while reading the message header from the input stream.

Action: Check the system memory usage and force garbage collection. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180082: Unable to close the WSH socket. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check the network and system configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180083: An unknown TCM type was received: {0}.

Cause: WebLogic Tuxedo Connector (WTC) is communicating with an unsupported Tuxedo version.

Action: Check the configuration and correct the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180084: Unable to write TCM. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check the system memory usage and force garbage collection.
Level: 1

Type: ERROR

Impact: WTC

BEA-180085: Unable to send an unsolicited acknowledgment. The following exception occurred: {0}.

Cause: An I/O error occurred.

Action: Check the system memory usage.
Level: 1

Type: ERROR

Impact: WTC

BEA-180086: Accepted connection from the remote domain {0}.

Cause: The connection request was received from a remote domain.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180087: Established a connection to a remote domain {0}.

Cause: The connection request to a remote domain was initiated.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180088: Error occurred while building {0} message.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180089: Error occurred while decoding {0} message.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180090: Remote domain {0} rejected the connection request.

Cause: An error exists in the configuration.

Action: Check both sides of the configuration, including the password, to see whether a mismatch exists in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180091: Rejected remote domain {0} connection request.

Cause: An error exists in the configuration.

Action: Check both sides of the configuration, including the password, to see whether a mismatch exists in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180092: Failed security validation with remote domain {0}.

Cause: An error exists in the configuraiton, resulting in unauthorized access.

Action: Check both sides of the configuration, including the password, to see if a mismatch exists in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180093: Naming exception occurred during the lookup of the administrator name: {0}.

Cause: The specified name could not be resolved.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180094: The tBridge failed to initialize the JMS targetName queue.

Cause: The JMS targetName queue does not exist or the JMS server was not running on the system.

Action: Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
Level: 1

Type: ERROR

Impact: WTC

BEA-180095: The tBridge could not initialize the JMS sourceName queue.

Cause: The sourceName queue cannot exist in JMS or the JMS server was not started.

Action: Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
Level: 1

Type: ERROR

Impact: WTC

BEA-180096: The tBridge could not initialize the wlsErrorDestination JMS queue.

Cause: The JMS wlsErrorDestination queue may not be properly configured in WebLogic Server.

Action: Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
Level: 1

Type: ERROR

Impact: WTC

BEA-180097: Due to a translation error, the tBridge has redirected the message to the wlsErrorDestination.

Cause: A translation error was detected from XML-to-FML or from FML-to-XML.

Action: Correct the message structure and resend the message.
Level: 1

Type: ERROR

Impact: WTC

BEA-180098: The tBridge failed to send the message to wlsErrorDestination.

Cause: The JMS wlsErrorDestination could be full or paused.

Action: Recover the message from the sourceName JMS queue and resend.
Level: 1

Type: ERROR

Impact: WTC

BEA-180099: The MinEncryptionBits is greater then the MaxEncryptionBits in {0} domain {1}.

Cause: There is a configuration error.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration so that it will use the correct values for the MinEncryptionBits and MaxEncryptionBits.
Level: 1

Type: ERROR

Impact: WTC

BEA-180100: Configuration error: {0}

Cause: There is a configuration error.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration so that it will use the correct values for the corresponding error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180102: Duplicated local domain ID {0} found.

Cause: Two local domains have the same ID.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration to use a unique ID for the local domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180103: There are two remote domains {0} with the same local domain {1}.

Cause: Two remote domains have the same local domain.

Action: Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration to remove the redundant entry or correct the configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180104: Unsupported JMS message type

Cause: A JMS Stream or Mapped message type was sent to the tBridge.

Action: Correct the JMS message type and resend.
Level: 1

Type: ERROR

Impact: WTC

BEA-180105: A message has been dropped.

Cause: The most common cause of this failure is that an unrecognized buffer type has been received by the WTC gateway.

Action: Modify the application to ensure that unknown buffer types are not sent to the WTC gateway.
Level: 1

Type: WARNING

Impact: WTC

BEA-180106: Unable to find a transaction manager. Transaction recovery will not continue.

Cause: A transaction manager could not be found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180107: While attempting to recover transactions, the recover method failed.

Cause: The recover method on the WebLogic Server XA sesource generated an exception.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180108: WebLogic Server rollback had a failure: {0}.

Cause: The rollback method on the WebLogic Server XA resource generated an exception.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180109: Internal FML to XML conversion failed.

Cause: The FML buffer that was received from Tuxedo contained field buffer names that were not provided to WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify that the field tables have been properly transfered as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180110: Internal FML32-to-XML conversion failed.

Cause: The FML32 buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify that the field tables have been properly transferred as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180111: Internal FML to XML conversion failed.

Cause: The FML buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify that the field tables have been properly transferred as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180112: Internal FML32 to XML conversion failed.

Cause: The FML32 buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.

Action: Verify the field tables have been properly transferred as described in the WTC documentation.
Level: 1

Type: ERROR

Impact: WTC

BEA-180115: The tBridge cannot parse the configuration MBeans: {0}.

Cause: The MBeans for the tBridge contain invalid attributes.

Action: Correct the attribute definitions for the tBridge MBeans.
Level: 1

Type: ERROR

Impact: WTC

BEA-180116: The specified field table type {0} is incorrect.

Cause: The WTCStartup.getFldTbls() method was called with an invalid argument.

Action: Verify that the Type argument for this is either fml16 or fml32.
Level: 1

Type: ERROR

Impact: WTC

BEA-180117: The encoding {0} is not supported. JVM default encoding is used.

Cause: Specified encoding name is not supported.

Action: Correct the encoding name and restart WebLogic Server.
Level: 1

Type: ERROR

Impact: WTC

BEA-180118: Failed to find TPUSR file: {0}.

Cause: The specified file TPUSR file does not exist.

Action: Correct the configuration by specifying the correct TPUSR file or create it before using the file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180119: The specified filename is not a valid file: {0}.

Cause: The WebLogic Tuxedo Connector (WTC) had the incorrect configuration.

Action: Correct the WTC TPUSR file configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180120: The file {0} is not readable.

Cause: The user does not have the read permission to read the configured TPUSR file.

Action: Change the permissions of the TPUSR file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180121: Cannot find file {0}.

Cause: The configured WebLogic Tuxedo Connector (WTC) TPUSR file does not exist.

Action: Correct the WTC TPUSR file configuration or create the file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180122: No permission to read the file {0}.

Cause: The user does not have the read permission to read the configured TPUSR file.

Action: Change the permissions of the TPUSR file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180123: File I/O error for file {0}, reason: {1}.

Cause: The file was corrupted or deleted.

Action: Correct the file corruption or use a new TPUSR file.
Level: 1

Type: ERROR

Impact: WTC

BEA-180124: The specified number is not in a valid number format: {0}.

Cause: The configured cache size was not in a valid number format.

Action: Correct the configuration in the WebLogic Tuxedo Connector (WTC) TpUsrFile.
Level: 1

Type: ERROR

Impact: WTC

BEA-180132: Custom AppKey generator class {0} not found.

Cause: The configured custom AppKey class full path name was incorrect.

Action: Ensure that the configuration is correct and that the custom class exists.
Level: 1

Type: ERROR

Impact: WTC

BEA-180133: AppKey plug-in initialization failed. Reason: {0}

Cause: The most likely reason is that the user database was not available or the initialization parameter was incorrect.

Action: Ensure that the user database is available and that the configuration is correct.
Level: 1

Type: ERROR

Impact: WTC

BEA-180134: Create new AppKey class {0} instance failed.

Cause: Either the class is not accessible, there is no permission to create a new instance of this class, or the class is not valid.

Action: Ensure that the class is accessible with the correct permission. Also, the class must be based on the weblogic.wtc.jatmi.AppKey interface.
Level: 1

Type: ERROR

Impact: WTC

BEA-180136: The {0} attribute on the {1} MBean is undefined but required.

Cause: The attribute value must be defined, but it was not defined.

Action: Check that the MBean attribute is set correctly.
Level: 1

Type: ERROR

Impact: WTC

BEA-180137: The {0} attribute on the {1} MBean is set incorrectly.

Cause: The attribute was defined improperly.

Action: Check that the MBean attribute is set correctly.
Level: 1

Type: ERROR

Impact: WTC

BEA-180138: The {0} MBean appears to contain previously defined import service information.

Cause: The attributes defined on this MBean have already been used to define and import a service.

Action: Check that the Resourcename,RemoteAccessPointList, and LocalAccessPoint attributes are not all duplicated in another import MBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180139: A {0} type MBean is not defined, but it is required to be defined.

Cause: An MBean was not defined, but it is required to be defined.

Action: Check that the MBean type specified is defined in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180141: Message header contains an invalid magic number, connection closed.

Cause: Either an invalid TDOMAIN protocol data unit was received, or the remote domain gateway did not have network encoding enabled.

Action: Ensure that the local access point is configured with the correct port number, and that the remote gateway does not have the same MTYPE configured for this TDOMAIN session.
Level: 1

Type: ERROR

Impact: WTC

BEA-180142: Local domain {0} in use and cannot be deleted.

Cause: The local domain was in use by another resource.

Action: Check for remote domains, imported or exported services, or passwords that use this local domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180143: Cannot find local domain {0}.

Cause: The local domain could not be found.

Action: Check the access point name.
Level: 1

Type: ERROR

Impact: WTC

BEA-180144: Duplicate remote domain {0}. Cannot add.

Cause: The access point name was duplicated.

Action: Check the access points and access point IDs for existing domains.
Level: 1

Type: ERROR

Impact: WTC

BEA-180145: Remote domain {0} in use. Cannot delete.

Cause: The remote domain is referenced by another resource or has an active connection.

Action: Shut down the connection to this remote domain. Check other resources that may reference this domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180146: Remote domain {0} cannot be found.

Cause: The specified remote domain cannot be found.

Action: Check the access point name for the remote domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180147: Cannot find imported service {0}.

Cause: The specified imported service could not be found.

Action: Check the name of the imported service.
Level: 1

Type: ERROR

Impact: WTC

BEA-180148: Cannot find exported service {0}.

Cause: The specified exported service could not be found.

Action: Check the name of the exported service.
Level: 1

Type: ERROR

Impact: WTC

BEA-180149: Cannot find password entry {0}.

Cause: The specified password entry could not be found.

Action: Check the local and remote access point names.
Level: 1

Type: ERROR

Impact: WTC

BEA-180150: Connection policy for {0} is INCOMING_ONLY.

Cause: The connection policy specified INCOMING_ONLY, so an outbound connection could not be started.

Action: Check the access point ID for the remote domain.
Level: 1

Type: ERROR

Impact: WTC

BEA-180151: Cannot modify resource {0} because it may be in use.

Cause: There is an active connection that may use this resource.

Action: Stop connections associated with this resource before attempting to delete the resource.
Level: 1

Type: INTERNAL_ERROR

Impact: WTC

BEA-180152: Registration of notification listeners for the configured MBeans has failed.

Cause: This is an internal system error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WTC

BEA-180153: No valid host Internet address for WTC remote access point {0}.

Cause: This is a configuration error.

Action: Correct the WTC remote access point's network address list.
Level: 1

Type: WARNING

Impact: WTC

BEA-180154: No valid listening address configured for local access point {0}.

Cause: This is an internal system error.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180155: No valid network address for TDomain session ({0}, {1}) to try to connect to.

Cause: Either there is a configuration error or the remote access point was not available and cannot be accessed using the configured information.

Action: Correct the configuration, or boot the remote access point.
Level: 1

Type: WARNING

Impact: WTC

BEA-180156: Failed to connect to remote access point(//{0}:{1}), try next address.

Cause: Either a configuration error exists or the remote access point was not available at the address specified.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180157: Failed to connect to remote access point(//{0}:{1}), no more address to try.

Cause: Either a configuration error exists or the remote access point was not available at the address specified.

Action: Correct the configuration or make the remote access point available.
Level: 1

Type: WARNING

Impact: WTC

BEA-180158: No more valid network addresses for the local access point {0} to listen.

Cause: There is a configuration error.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: WTC

BEA-180159: Failed to listen for local access point {0} on address (//{1}:{2}), try next address.

Cause: Either a configuration error exists or this was intended.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180160: Failed to create listening endpoint for local access point {0} on address (//{1}:{2}), no more addresses to try.

Cause: There is a configuration error.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: WTC

BEA-180161: Failed to find the imported service for QSpace {0}, so the tBridge has redirected the message to the wlsErrorDestination.

Cause: The WebLogic Tuxedo Connector (WTC) import was incorrectly configured.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180162: Cannot find imported service {0}, so the tBridge has redirected the message to the wlsErrorDestination.

Cause: There is a configuration error.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180163: The received Tuxedo reply uses the unsupported buffer type {0}, so the tBridge has redirected the message to the wlsErrorDestination.

Cause: The Tuxedo server returned a reply with an unsupported buffer type.

Action: Modify the Tuxedo server to return the reply with a WebLogic Tuxedo Connector (WTC) supported buffer type.
Level: 1

Type: ERROR

Impact: WTC

BEA-180164: Failed to send message to JMS, so the tBridge has redirected the message to the WLSErrorDestination.

Cause: The JMS replyQ is configured incorrectly.

Action: Correct the configuration of the JMS queue to be used for the tBridge reply queue.
Level: 1

Type: ERROR

Impact: WTC

BEA-180165: TDomain session ({0}, {1}) disconnected because no keep alive acknowledgement was received.

Cause: A network outage may have occurred.

Action: Check the network connection between the two gateways to determine if it is connected.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180166: The remote gateway does not support application level keep alive. This feature is disabled for the TDomain session ({0}, {1}).

Cause: The remote gateway does not support this application level keep alive feature.

Action: Update the remote gateway to a version of Tuxedo that supports the TDomain application level keep alive feature.
Level: 1

Type: WARNING

Impact: WTC

BEA-180167: The imported resource {0} uses a TDomain session ({1}, {2}) that does not exist.

Cause: The imported resource was not configured properly.

Action: Correct the configuration for the imported service.
Level: 1

Type: ERROR

Impact: WTC

BEA-180168: A connection cannot be established between local domain {0} and remote domain {1} due to a problem with the local or remote password used to authenticate the connections between these domains.

Cause: The domain passwords were not configured properly.

Action: Encrypt the correct local and remote passwords for the connection using the weblogic.wtc.gwt.genpasswd utility and use the results to configure a WTCPasswordMBean.
Level: 1

Type: ERROR

Impact: WTC

BEA-180169: XA.end() failed: {0}

Cause: The transaction may have been marked as ROLLBACK_ONLY.

Action: Inspect the application logic to determine the cause of the error.
Level: 1

Type: ERROR

Impact: WTC

BEA-180170: Unexpected exception while converting View {0} to XML: {1}

Cause: Refer to the exception details.

Action: Refer to the exception details.
Level: 1

Type: ERROR

Impact: WTC

BEA-180171: SSL null ciphers are not enabled and will be upgraded to the minimum 56 bits.

Cause: The null cipher suites were disabled by SSL configuration.

Action: This can be ignored because stronger encryption strength is allowed by WTC configuration and is also available by SSL. However, WTC configuration can be corrected to use only 56 bits and stronger cipher suites or SSL null ciphers can be enabled, if desired.
Level: 1

Type: WARNING

Impact: WTC

BEA-180172: SSL null ciphers are not enabled.

Cause: The null cipher suites were disabled by SSL configuration.

Action: Either the SSL null cipher suites must be explicitly enabled, or the WTC configuration must be updated to use stronger encryption cipher suites.
Level: 1

Type: ERROR

Impact: WTC

BEA-180173: Invalid private key for identity alias {0} from key store {1}, detected by {2}.

Cause: An invalid key store or the private key alias configuration does not exist in the key store, or an incorrect private key store passphrase was configured.

Action: Correct the key store or private key alias information in the configuration.
Level: 1

Type: ERROR

Impact: WTC

BEA-180174: Invalid private key store {0}, detected by {1}

Cause: The private key store configured does not exist or is corrupted.

Action: Correct the private key store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180175: Invalid trust certificate store {0}, detected by {1}

Cause: The private key store configured does not exist or is corrupted.

Action: Correct the private key store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180176: An error occurred while retrieving the trusted certificate from trust store {0}, detected by {1}.

Cause: The configured trust certificate was corrupted or an incorrect passphrase was configured.

Action: Correct the trust certificate store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180177: An error occurred while retrieving trusted certificates from WebLogic Server, detected by {0}.

Cause: The configured trust certificate was corrupted or an incorrect passphrase was configured.

Action: Correct the trust certificate store configuration information.
Level: 1

Type: ERROR

Impact: WTC

BEA-180178: The requested encryption strength of 256 bits of local access point {0} is not supported by LLE. Downgrade to 128 bits.

Cause: The configured encryption strength is not supported by LLE.

Action: Either change the encryption strength to the LLE supported strength or use SSL for connection privacy. LLE supports 0, 40, 56, and 128 bits encryption strength. SSL supports 0, 56, 128, and 256 bits encryption strength.
Level: 1

Type: NOTIFICATION

Impact: WTC

BEA-180179: When enabling access point {0} to support SDP, the SSL support setting for this access point was ignored.

Cause: When SDP is configured, SSL is not supported.

Action: No action is required if SDP support is expected. Otherwise, update the configuration to disable SDP support.
Level: 1

Type: WARNING

Impact: WTC

BEA-180180: An error occurred while trying to open class com.oracle.net.Sdp when WTC support for SDP was enabled.

Cause: The current JRE does not support SDP.

Action: Use the JRockit version of the JRE provided with this release of WebLogic Server.
Level: 1

Type: ERROR

Impact: WTC

BEA-190000: Initializing J2EE Connector Service.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190001: J2EE Connector Service initialized successfully.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190004: ConnectionFactory not found for jndiName {0}.

Cause: This warning can occur upon viewing the JNDI tree for the Managed Server on the Administration Console. The other likely cause for this error is that an incorrect JNDI name was specified for the desired resource adapter or that the resource adapter is not deployed.

Action: Ignore the warning if it occurs while viewing the JNDI tree of a Managed Server. Otherwise, check the deployed connectors in the Administration Console and verify the name that was used to access it.
Level: 1

Type: WARNING

Impact: Connector

BEA-190005: An error occurred while creating a connection factory for ManagedConnectionFactory with jndiName {0}.

Cause: The cause is unknown. Consult the resource adapter vendor documentation.

Action: Examine the exception in the log for more information about how to correct the problem. You may need to refer to the resource adapter vendor documentation to determine an appropriate course of action.
Level: 1

Type: ERROR

Impact: Connector

BEA-190008: An error occurred while {2} the connection instance {1} for {0} resource adapter. Exception is: {3}

Cause: This error occurs as the result of an attempt to call cleanup() or destroy() on a resource adapter managed connection. The resource adapter can generate a ResourceException if the operation fails. It can also generate an IllegalStateException if, for example, an attempt was made to clean up a connection when a transaction was in progress. A ResourceAdapterInternalException may be generated if an internal error condition is detected in the resource adapter.

Action: Examine the log for the exact type of exception that was generated. In the case of an IllegalStateException, report the error to My Oracle Support. In the case of a ResourceAdapterInternalException, report the error to the resource adapter vendor.
Level: 1

Type: ERROR

Impact: Connector

BEA-190009: No ConnectionRequestInfo was provided for Application Managed Security Context.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190010: Unable to determine resource principal for the container-managed security context.

Cause: Improper security principal map configuration for resource adapter.

Action: Check the resource adapter configuration.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190012: Component using JNDIName: {0} has {1} managed security.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190013: An error occurred while processing context: java:/comp/env/wls-connector-resref.

Cause: This is an internal WebLogic Server error.

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190019: < {0} > An error occurred when opening the log file {1} for the resource adapter.

Cause: The log file is either a directory rather than a regular file, or it could not be opened for some other reason.

Action: Check the log-filename configuration parameter in weblogic-ra.xml.
Level: 1

Type: ERROR

Impact: Connector

BEA-190020: < {0} > An error occurred while setting the log file to the resource adapter.

Cause: An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.

Action: Contact your resource adapter supplier about the ManagedConnectionFactory.setLogWriter() method.
Level: 1

Type: ERROR

Impact: Connector

BEA-190023: < {0} > Error invoking the ManagedConnectionFactory "set" method for the configuration property "{1}". Reason: {2}

Cause: The method required for setting the config-property could not be properly invoked.

Action: Check the config-property of the ra.xml file in the resource adapter and ensure that the indicated property is specified correctly.
Level: 1

Type: ERROR

Impact: Connector

BEA-190024: < {0} > Error making initial connections for pool. Reason: {1}

Cause: The backend system to which the resource adapter connects may be down, or the resource adapter may be misconfigured.

Action: Check the availability of the backend system, then confirm the correct configuration of the resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-190032: < {0} > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "{1} "

Cause: The cause should be evident from the exception. One likely cause is a misconfigured weblogic-ra.xml or ra.xml. The property(ies) specifying the connection information may not be correct.

Action: Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or the resource adapter documentation. You might also consult the resource adapter vendor support information or organization.
Level: 1

Type: WARNING

Impact: Connector

BEA-190033: < {0} > createManagedConnection returned a null ManagedConnection.

Cause: This generally is a resource adapter error. A resource adapter should never return a null managed connection.

Action: Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or the resource adapter documentation, or consult the resource adapter vendor support information or organization
Level: 1

Type: ERROR

Impact: Connector

BEA-190049: The connector service failed to initialize. ServiceMBean initialization error: {0}

Cause: This error should not occur under normal operations. Possible causes of this error could be low memory, file corruption, or machine instability.

Action: Try rebooting the machine and restarting the server again. If the problem persists, note the error details and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190050: An error occurred in the connector service shutdown. Error: {0}

Cause: The error occurred as a result of shutting down a connection pool or unregistering the ServiceMBean.

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190051: An error occurred while shutting down the connection pool with pool name: {0}. Reason: {1}

Cause: An error occurred while shutting down the connection pool. The error occurred while unregistering the ConnectionPoolRuntimeMBean. pool name:{0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190052: An error occurred while creating a connection pool Runtime MBean with pool name: {0}. Reason: {1}

Cause: An error occurred while creating a connection pool Runtime MBean. The error occurred while initializing the ConnectionPoolRuntimeMBean. pool name:{0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190053: An error occurred while creating a resource for a connection pool {0}. Reason: {1}

Cause: Error occurred while instantiating a ConnectionRuntimeMBean for the connection being created. Pool name: {0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190054: An error occurred while destroying a resource for a connection pool {0}. Reason: {1}

Cause: An error occurred while unregistering a ConnectionRuntimeMBean for the connection being destroyed. Pool name: {0}, Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190056: An error occurred while reserving a resource from a connection pool {0}. Reason: {1}

Cause: An error occurred while registering an XAResource for the connection being reserved with the transaction manager. Pool name:{0}. Reason: {1}

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190064: Access has been denied to {0}, Application: {1}, Module: {2}, EIS Type: {3}, while reserving a connection.

Cause: The entitlement check did not pass for the connection request to the connection pool with name: {0}.

Action: Check your entitlement configuration in the Administration Console.
Level: 1

Type: WARNING

Impact: Connector

BEA-190075: The resource adapter returned a null connection factory when createConnectionFactory was called for "{0}".

Cause: The resource adapter is not functioning according to the specification.

Action: Contact the resource adapter vendor.
Level: 1

Type: ERROR

Impact: Connector

BEA-190079: The descriptor element {0} has been replaced by {1}.

Cause: A deprecated descriptor element has been detected.

Action: Convert the old descriptor element to the replacement element.
Level: 1

Type: WARNING

Impact: Connector

BEA-190080: An inactive deprecated descriptor element {0} has been detected.

Cause: An inactive deprecated descriptor element has been detected.

Action: Refer to the connector documentation for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190081: Testing resource adapter "{0}" for viability of connection proxies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190082: Proxy test passed. WebLogic Server will use connection proxies for resource adapter "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190084: Unable to complete connection proxy test for "{0}" due to the following exception. WebLogic Server will attempt to use connection proxies for resource adapter "{0}" as usual.

Cause: WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190085: The linkref RAR {0} has been marked for late deployment since its base has not been deployed.

Cause: The base RAR that the linkref points to has not been deployed yet.

Action: Do not use the linkref until its base has been deployed.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190088: Trying to deploy a connector with a JNDI name that already exists {0}.

Cause: Trying to deploy a connector with a JNDI name that already exists {0}.

Action: Use a unique JNDI name while deploying the connector.
Level: 1

Type: ERROR

Impact: Connector

BEA-190089: Unexpected error occurred while processing a resource adapter JAR file.

Cause: The cause is unknown.

Action: Examine the stack trace for the cause and action.
Level: 1

Type: ERROR

Impact: Connector

BEA-190090: Call to implementation of ManagedConnection.getLocalTransaction in resource adapter with jndiName = {1} failed: {0}

Cause: Refer to the error message for more information.

Action: See the error message for more information. If it is still unclear, contact the resource adapter vendor or My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190091: Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = {1} failed: {0}

Cause: Refer to the error message for more information.

Action: Refer to the error message for more information. If still unclear, contact the resource adapter vendor or My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190092: An error occurred while reserving a resource from a connection pool {0}. Reason: {1}

Cause: An error occurred while registering a non-XAResource for the connection being reserved with the transaction manager. pool name:{0}. Reason: {1}

Action: Report this error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190097: Unable to complete the connection proxy test for "{0}" due to an exception. WebLogic Server will attempt to use connection proxies for resource adapter "{0}" as usual. Exception: {1}

Cause: WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190098: Trying to release a resource that has already been released for {0}.

Cause: Trying to release a resource that has already been released for {0}. It is possible that the connection was already released due to an error that occurred with the connection.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-190099: Attempting to close a connection that has already been closed for {0}.

Cause: An attempt was made to close a connection that has already been closed for {0}.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-190100: A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}

Cause: A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}. As per the 1.0 specification, a close() method is required on the connection handle.

Action: Implement a close() method for the connection handle.
Level: 1

Type: ERROR

Impact: Connector

BEA-190101: Linkrefs are deprecated for 1.0 resource adapters: {0}

Cause: Linkrefs are deprecated for 1.0 resource adapters.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Connector

BEA-190102: Failed to unregister the Diagnostic Image for the Connector Service.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190103: Failed to register the Diagnostic Image for the Connector Service.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190104: While configuring an object of type: {0} of Resource Adapter {1}, the following errors/omissions were found: {2}

Cause: Properties have been specified in a resource adapter deployment descriptor which are inconsistent with those defined by the resource adapter code. There may be properties specified in the descriptor that do no exist in the object or are of the wrong type.

Action: Check that the specified properties are spelled properly. Check with the resource adapter documentation or the vendor to determine whether or not these warnings can be ignored.
Level: 1

Type: WARNING

Impact: Connector

BEA-190105: Failed to initialize the AnonymousSubject.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190106: Failed to find the RuntimeMBean for the module: {0}

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190107: Failed to unregister the RuntimeMBean for the module: {0}

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190108: Failed to initialize the Jndi Subcontexts for the adapter: appId = {0}, {1}

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190109: Extracting file {0} to {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190110: Resource adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance or operation of WebLogic Server.

Cause: A resource adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server.

Action: Contact the resource adapter vendor and notify them of this warning condition.
Level: 1

Type: WARNING

Impact: Connector

BEA-190111: InvalidDyeException was generated: Module Name = {0}, {1}.

Cause: This is a WebLogic Server internal error.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190112: Failed to register the XAResource to be used for recovery: {0}

Cause: See the error description in the message body.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190113: Failed to Unregister the XAResource used for recovery: {0}

Cause: See the error description in the message body.

Action: See the stack trace and report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190114: Failed to apply dynamic pool changes: {0}

Cause: See the error description in the message body.

Action: See the error description in the message body.
Level: 1

Type: ERROR

Impact: Connector

BEA-190115: The ManagedConnectionFactory class does not implement the ResourceAdapterAssociation interface: {0}

Cause: See the error in the message body for information.

Action: Please contact the resource adapter vendor and notify them of this error condition.
Level: 1

Type: ERROR

Impact: Connector

BEA-190116: An invalid event was triggered on the XAResource used for recovery: {0}

Cause: This is a WebLogic Server internal error.

Action: Report the error to My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190117: Invocation of ManagedConnection.cleanup() failed: {0}

Cause: See the error in the message body for information.

Action: Examine the stack trace and error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190118: ConnectionErrorOccurred event was triggered: {0}

Cause: The adapter has indicated an error occurred on the exception.

Action: Examine the stack trace and error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190119: Invocation of ManagedConnection.destroy() failed: {0}

Cause: The implementation of the resource adapter's cleanup() method threw an exception.

Action: Examine the stack trace and error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190120: Invocation of ManagedConnection.getXAResource() returned null.

Cause: The implementation of the resource adapter's getXAResource() returned null.

Action: Please contact the resource adapter vendor to determine why getXAResource() returned null.
Level: 1

Type: ERROR

Impact: Connector

BEA-190121: Failed to dissociate the Connection Handles from a ManagedConnection: Adapter JndiName = {0}, {1}

Cause: See the message body and stack trace for more details.

Action: See the message body and stack trace for more details.
Level: 1

Type: ERROR

Impact: Connector

BEA-190122: The resource adapter passed a null ManagedConnection into WebLogic Server's implementation of ConnectionManager.lazyEnlist().

Cause: The resource adapter's implementation passed a null ManagedConnection into the lazyEnlist() method.

Action: Please notify the resource adapter's vendor about this error.
Level: 1

Type: ERROR

Impact: Connector

BEA-190123: Outbound adapter for jndiName = {0}, is using sharing scope = {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190124: Failed to deploy LinkRef Adapter, moduleName = {0}, baseRA = {1}, Exception: {2}

Cause: Refer to the message body and exception message for more information.

Action: Refer to the message body and exception message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190125: Internal error occurred, assertion failed: {0}

Cause: An internal consistency check failed, indicating a software defect.

Action: Please note the circumstances of the error, as well as any related log messages, and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-190126: anonymous

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190127: CloseCount

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190128: CreateCount

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190129: FreePoolSize

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190130: PoolSize

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190131: WaitingThreadCount

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190133: Number of times create was called on the connection pool

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190134: Number of connections in the pool that are free for use

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190135: Size of the connection pool

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190136: Number of threads in the waiting state

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190137: Never

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190138: <Unavailable>

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190139: Running

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190140: Suspended

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190141: New

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190142: Initialized

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190143: Prepared

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190144: Activated

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190145: Unknown

Cause: This message is used only for localization (internationalization) purposes.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Connector

BEA-190146: An error occurred while setting the log file to the resource adapter's ManagedConnectionFactory: {0}. The exception was "{1}" with cause "{2}".

Cause: An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.

Action: Examine the message and cause, or contact the resource adapter provider, or both.
Level: 1

Type: ERROR

Impact: Connector

BEA-190147: Profiling Record for Pool: PoolName = "{0}", Type = "{1}", Timestamp = "{2}", Properties : {3}

Cause: This message is informational. The Harvester logged this Profiling Record for debug purposes.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190148: The attempt to set the property "{1}" of type "{2}" of object "{0}" to value "{3}" failed with a PropertyVetoException generated by the resource adapter. The veto message was "{4}".

Cause: See the veto message for more information.

Action: See the veto message for more information. Contact the resource adapter provider if more assistance is needed.
Level: 1

Type: WARNING

Impact: Connector

BEA-190149: No JNDI Name has been specified for the resource adapter in module {0} of application {1}. Since this is an inbound resource adapter, <jndi-name> must also be specified in weblogic-ra.xml for endpoint activation by a message endpoint MDB to work.

Cause: There is a missing <jndi-name> element in weblogic-ra.xml.

Action: Specify the <jndi-name> in weblogic-ra.xml that corresponds to the JNDI name expected by the MDB that is using this inbound resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-190150: The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework. The resulting image may be incomplete.

Cause: The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework.

Action: Please investigate the contents of the log and Diagnostic Images for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190151: Parsing error, buildOutboundResourceAdapter() error in parsing ra.xml. While looking for connectionfactory-interface, failed to find: "{0}"

Cause: There is an error in the XML configuration for this adapter.

Action: Please contact the vendor to obtain a resource adapter with a valid configuration.
Level: 1

Type: ERROR

Impact: Connector

BEA-190152: Failed to create a new ConnectorInboundRuntimeMBeanImpl for "{0}", {1}

Cause: See the error in the logged message for more information.

Action: See the error in the logged message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-190153: Failed to close the logging stream for pool: "{0}", {1}

Cause: See the error in the logged message for more information.

Action: See the error in the logged message for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190154: Failed to create the logging stream for pool: "{0}", {1}

Cause: See the error in the logged message for more information.

Action: See the error in the logged message for more information.
Level: 1

Type: WARNING

Impact: Connector

BEA-190155: Compliance checking and validation of the resource adapter {0} resulted in the following warnings: {1}

Cause: The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.

Action: Correct the ra.xml, weblogic-ra.xml or the resource adapter archive.
Level: 1

Type: WARNING

Impact: Connector

BEA-190156: There were no compliance or validation errors found in the resource adapter {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190157: There were {1} critical compliance or validation error(s), {2} non-critical compliance or validation error(s), and {3} warning(s) found in the resource adapter {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190158: This is a link ref resource adapter for {0}. No validation can be done at this time.

Cause: Since there is no ra.xml in this resource adapter, validation of the adapter cannot be performed until it and the base adapter are deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190159: Connection Pool {0} has been reset.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-190160: Connection pool {0} is in use and cannot be reset. Try forceReset instead.

Cause: Since there are connections reservered from connection pool {0}, reset of the pool cannot be performed.

Action: Try forceReset instead.
Level: 1

Type: WARNING

Impact: Connector

BEA-190161: Failed to extract adapter {0} to server temporary directory due to exception {1}.

Cause: Extraction of the adapter {0} to server temporary directory failed due to the exception.

Action: Check the permissions on the server temporary directory or check the exception.
Level: 1

Type: ERROR

Impact: Connector

BEA-190162: Failed to create server temporary directory {1} while extracting adapter {0}.

Cause: Creation of the server temporary directory {1} failed while extracting the adapter {0}.

Action: Check the permissions on the server temporary directory.
Level: 1

Type: ERROR

Impact: Connector

BEA-199000: Only positive values are allowed for initial-capacity unless initial and max capacity are equal.

Cause: Refer to the message body and exception for more information.

Action: Refer to the message body and exception for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-199001: Zero value for max-capacity is allowed only for link-ref adapters.

Cause: The max-capacity is zero.

Action: Check the max-capacity and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199002: Negative values are not allowed for max-capacity.

Cause: The max-capacity is negative.

Action: Check the max-capacity and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199003: max-capacity should be greater than or equal to initial-capacity. {0}

Cause: The max-capacity is less than initial-capacity.

Action: Check the max-capacity and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199004: Only positive values are allowed for capacity-increment.

Cause: The capacity-increment is zero or negative.

Action: Check the capacity-increment and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199005: capacity-increment should be less than or equal to ( max_capacity-initial_capacity ). {0}

Cause: The capacity-increment is greater than max_capacity-initial_capacity.

Action: Check the capacity-increment and update it.
Level: 1

Type: ERROR

Impact: Connector

BEA-199006: Only positive values are allowed for shrink-frequency-seconds.

Cause: The shrink-frequency-seconds is zero or negative.

Action: Check the shrink-frequency-seconds.
Level: 1

Type: ERROR

Impact: Connector

BEA-199007: Only values greater than or equal to 0 are allowed for inactive-connection-timeout-seconds.

Cause: The value of inactive-connection-timeout-seconds must be positive.

Action: Please check the inactive-connection-timeout-seconds.
Level: 1

Type: ERROR

Impact: Connector

BEA-199010: No ra.xml or weblogic-ra.xml has been specified. The RAR is null and there is no alternate descriptor.

Cause: The deployment descriptor for this adapter cannot be found.

Action: Define the deployment descriptor in ra.xml or weblogic-ra.xml or an annotation.
Level: 1

Type: ERROR

Impact: Connector

BEA-199011: No ra.xml or weblogic-ra.xml has been specified.

Cause: The deployment descriptor for this adapter could not be found.

Action: Define the deployment descriptor in ra.xml or weblogic-ra.xml.
Level: 1

Type: ERROR

Impact: Connector

BEA-199012: Unable to find the schema.

Cause: The schema could not be found.

Action: Check the location of the schema for the XML file.
Level: 1

Type: ERROR

Impact: Connector

BEA-199013: Application {0} does not have any components in it.

Cause: The application does not contain any components.

Action: Add components in the application and define them in the deployment descriptor.
Level: 1

Type: ERROR

Impact: Connector

BEA-199014: Application {0} is a RAR file, but it contains more than 1 component.

Cause: The application contains multiple adapter components.

Action: Check the deployment descriptor or the annotation.
Level: 1

Type: ERROR

Impact: Connector

BEA-199015: Error occurred while trying to rollback the module: {0}

Cause: The module cannot be rolled back. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199016: Unable to create runtime MBean for connector: Module "{0}", {1}

Cause: The runtime MBean cannot be created. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199017: Error closing virtual JAR file for {0}, {1}

Cause: The virtual JAR file cannot be closed. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199018: Error creating virtual JAR file for {0}, {1}

Cause: The virtual JAR file cannot be created. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199019: Failed to initialize the connector-specific JNDI sub-contexts for the application, {0}, {1}

Cause: The connector-specific JNDI sub-contexts cannot be initialized. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199020: Failed to prepare changes for dynamic update, {0}, {1}

Cause: Changes for dynamic update cannot be prepared. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199021: JNDI name is null or empty.

Cause: The JNDI name must contain characters that are not spaces.

Action: Check the JNDI name.
Level: 1

Type: ERROR

Impact: Connector

BEA-199022: Unable to get InitialContext while attempting to verify JNDI name of a resource adapter object.

Cause: Failed to create the InitialContext.

Action: Check the environment properties of the InitialContext.
Level: 1

Type: ERROR

Impact: Connector

BEA-199023: ResourceLink is null or empty.

Cause: ResourceLink is null or empty.

Action: Check the ResourceLink.
Level: 1

Type: ERROR

Impact: Connector

BEA-199024: Unable to get InitialContext while attempting to verify resource link of resource adapter.

Cause: The InitialContext cannot be created.

Action: Check the environment properties of the InitialContext.
Level: 1

Type: ERROR

Impact: Connector

BEA-199028: Resource Adapter with JNDIName: {0} already deployed.

Cause: Multiple apdaters are deployed with the same JNDI name.

Action: Change the adapter's JNDI name in deployment descriptor.
Level: 1

Type: ERROR

Impact: Connector

BEA-199029: Bind operation failed: {0}, {1}

Cause: The JNDI name cannot be bound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199031: Failed to unbind the ConnectionFactory, {0}, {1}

Cause: The ConnectionFactory cannot be unbound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199032: Unable to getInitialContext() during unbindConnectionFactory, {0}

Cause: The getInitialContext() method cannot be called. See the reported exception for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199036: ResourceLink: {0} already bound into application-scoped JNDI tree.

Cause: The ResourceLink has been bound into the JNDI tree.

Action: Change the JNDI name of ResourceLink.
Level: 1

Type: ERROR

Impact: Connector

BEA-199037: Unable to bind to the app-scoped jndi tree: {0}#{1} : {2}

Cause: The ResourceLink cannot be bound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199038: NamingException while trying to unbind references during unbindAdminObject of resource adapter, {0}

Cause: AdminObjects cannot be unbound. See the reported error for the cause.

Action: Examine the exception in the log for more information about how to correct the problem.
Level: 1

Type: ERROR

Impact: Connector

BEA-199039: Unable to get the connection factory for {0}. Verify that the resource adapter has been deployed.

Cause: The connection factory cannot be found.

Action: Verify that the resource adapter has been deployed.
Level: 1

Type: ERROR

Impact: Connector

BEA-199041: An exception occurred while calling newInstance in the Resource Adapter, classname = {0}, Exception = {1}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199042: An exception occurred while trying to create the Connector Diagnostic Image, Exception = {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199043: Trying to prepare a resource adapter that has not been initialized.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199044: Trying to activate a resource adapter that has not been prepared. Current state : {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199045: Trying to rollback an RA that is in the ACTIVATED state

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199046: Unable to create the native lib directory.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199047: Bad resource adapter class specification for class "{0}": {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199048: Trying to version a resource adapter that is not versionable.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199049: Unable to populate the Work Manager during resource adapter initialization.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199050: Caught exception while starting the resource adapter : {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199051: Caught exception while creating the BootstrapContext : {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199052: Unable to version the resource adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199053: Unable to set up the work runtimer.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199054: Unable to introspect the object that was passed in. {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199055: Unable to get the setter method for the key: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199056: Unable to invoke the setter method for the key: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199065: An invalid type {0} has been specified for a key.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199066: For property "{0}", the type and value do not match. Type = {1}, Value = {2}, Exception: {3}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action accordingly.
Level: 1

Type: ERROR

Impact: Connector

BEA-199067: LoginException while trying to establish security identity for user "{0}" in weblogic-ra.xml element {2}: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199068: No deployed ResourceAdapter with adapter JNDI name = "{0}" was found.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199071: Unable to initialize ActivationSpec {0}. Cause unknown.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199072: Failed to instantiate class {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199073: {0} passed {1} of "{2}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199074: Required Configuration Properties Missing in ActivationSpec: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199075: Located a resource adapter with JNDI name = "{0}", but that adapter is not yet fully deployed and active.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199076: Could not locate a resource adapter with JNDI name = "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199077: The resource adapter with JNDI name = "{0}" does not have a <messagelistener> element with a <messagelistener-type> of "{1}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199089: The resource adapter does not have a <inbound-resourceadapter> element in ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199090: The resource adapter does not have a <messageadapter> element in ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199091: The resource adapter does not have any <messagelistener> elements in ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199092: Internal error occurred, Assertion Failed: {0}

Cause: An internal consistency check failed indicating a software defect.

Action: Please note the circumstances of the error as well as any related log messages and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-199093: setDyeBits failed because diagnostic contexts are not enabled.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199094: Invalid dye value specified, {0}. Value must be between 0 and 15 in order to fit within a 4-bit space.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199095: getDyeBits failed, moduleName = {0}: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199096: setDyeBits failed: Failed to obtain Diagnostic Context. ModuleName = {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199097: getDyeBits failed because Diagnostic Contexts are not enabled.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199098: This connection does not meet the criteria for manual deletion.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199099: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199100: Resource Adapter threw Non-ResourceException from its implementation of ManagedConnection.getLocalTransaction(), Pool = "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199101: Resource Adapter returned null from its implementation of ManagedConnection.getLocalTransaction(), Pool = "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199102: Unable to register NonXAResource, {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199103: Commit Failed: {0}, Stack Trace: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199104: Rollback Failed: {0}, Stack Trace: {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199105: Resource Adapter returned null from ManagedConnection.getXAResource() while trying to obtain XAResource for recovery.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199106: Resource Adapter threw non-ResourceException in call to ManagedConnection.getXAResource(): {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199107: Resource Adapter returned null from ManagedConnectionFactory.createManagedConnection() while trying to create ManagedConnection for recovery.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199108: Failed to initialize ManagedConnection for recovery: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199109: Connector Internal Error: Illegal type found during enlistResource.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199110: Connector Internal Error: Invalid type found in registerResource: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199111: Attempt to start an XA Transaction inside a Resource Adapter's Local Transaction is illegal.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199112: Failed to create managed connection: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199113: Failed to setup the ManagedConnection with WLS after successfully getting it from a call to the Resource Adapter's ManagedConnectionFactory.createManagedConnection method.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199114: Internal WLS Connector Error: Object Id is null.

Cause: Check the logs for the cause of this exception.

Action: Please contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-199116: Resource Adapter Error: getConnection method returned null from the adapter's ManagedConnection implementation in class "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199117: The resource adaptor has returned the same connection handle that was returned on a prior call to getConnection(). A new connection handle must be returned with every call to getConnection() as per the JCA specification.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199118: While testing connection, the adapter's implementation of getInvalidConnections() threw ResourceException: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199119: While testing connection, the adapter's implementation of getInvalidConnections() threw non-ResourceException: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199120: Connections should not be tested for a ManagedConnectionFactory that does not implement ValidatingManagedConnectionFactory.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199121: The ResourceAdapter with pool = "{0}" passed a null value to the Application Server's implementation of the lazyEnlist method for the ConnectionManager class.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199122: Access to resource adapter, with pool = "{0}", has been denied.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199123: Unable to get a connection for pool = "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199124: Pool "{0}" is disabled, cannot allocate resources to applications.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199125: The resource adapter's implementation of ManagedConnectionFactory returned null from the createConnectionFactory() method.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199126: Stack trace at connection create:

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199127: Local Transaction not supported for this Resource Adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199128: The connection handle has not been set for the connection closed event as per the JCA specification.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199129: Error preparing the pool with key : "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199130: Unable to resume the pool, {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199131: Unable to bind to the jndi tree : "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199132: Key = {0}, Message = {1}, Exception = {2}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199133: Unable to shut down the pool : Key = "{0}", Message = {1}, Exception = {2}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199134: Attempting to create a connection factory with a JNDI name that already exists: "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199135: Attempting to create a connection factory with a resource link that already exists: "{0}".

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199136: There was a problem verifying the JNDI name of the outbound connection: {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199137: The ManagedConnectionFactory class implementation "{0}" does not implement the ResourceAdapterAssociation interface and does not implement setResourceAdapter() and/or getResourceAdapter().

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199138: Unable to set the ResourceAdapter class for the mcf "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199139: Unexpected exception thrown by resource adapter's ManagedConnectionFactory implementation "{0}", {1}.

Cause: Check the logs for the cause of this exception.

Action: Take appropriate action based on the cause reported in the logs.
Level: 1

Type: ERROR

Impact: Connector

BEA-199140: Could not find the managed connection factory class "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199141: Failed to instantiate the resource adapter's implementation of the ManagedConnectionFactory class "{0}," {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199142: Unable to access the Resource Adapter' implementation of the ManagedConnectionFactoryClass "{0}", {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199143: Internal WebLogic Server Connector Error: Failed to get the connection pool for jndiName: "{0}".

Cause: Check the logs for the cause of this exception.

Action: Please contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Connector

BEA-199144: A resource adapter may only be accessed from within the same application from which it was deployed.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199145: Operation is not supported, {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199146: If only a weblogic-ra.xml has been specified for the resource adapter, it must be a linkref.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199147: The resource adapter only has a weblogic-ra.xml specified. It also needs the ra.xml.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199148: Error Creating Native Lib Directory: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199149: FileNotFoundException when creating native lib dir for {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199150: Failure while creating native library directory for {0}, {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199151: An error occurred while starting the pool: {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199152: test-frequency-seconds is set to non-zero.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199153: Connection testing cannot be enabled for a pool when the ManagedConnectionFactory does not implement ValidatingManagedConnectionFactory. The following invalid settings have been detected:

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199154: Work instance passed in to the Work Manager is null.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199155: The Work Manager is currently not accepting doWork() calls.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199156: The Work Manager is currently suspended. New work is not being accepted.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199157: Unable to establish Execution Context or enlist work in imported transaction, {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199158: Global tx id "{0}" not associated with specified Work instance.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199159: Global tx id "{0}" not registered with the Work Manager.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199160: The <security-principal-map> element was deprecated in WebLogic Server 7.0 and is no longer supported. Please remove the element from the weblogic-ra.xml for the Resource Adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199161: Work instance with global tx id "{0}" already active; conncurrent work disallowed.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199162: Bad ManagedConnectionFactory class specification for class "{0}" : {1}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199164: Unable to activate the pool, {0}

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199165: test-connections-on-create is set to true.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199166: test-connections-on-release is set to true.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199167: test-connections-on-reserve is set to true.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199168: Unable to force log rotation: The connection pool for "{0}" is configured to use the server log.

Cause: Log rotation cannot be forced for pools that are configured to use the server log.

Action: Change the pool's logging parameters to use a different log other than the server log.
Level: 1

Type: ERROR

Impact: Connector

BEA-199169: Failed to get the Connection Factory for the pool "{0}", {1}

Cause: See the details of the error message for more information.

Action: See the details of the error message for more information.
Level: 1

Type: ERROR

Impact: Connector

BEA-199170: For the setting {0}: "{1}" has higher privileges than the deployment user: "{2}".

Cause: The deployment user does not have the privileges to perform the current deployment action.

Action: Try the deployment action with a user account that has administrator privileges.
Level: 1

Type: ERROR

Impact: Connector

BEA-199171: The security-principal-map is not a valid element.

Cause: The security-principal-map is not a valid element. You will need to define the mapping using the Administration Console.

Action: Define the mapping using the Administration Console.
Level: 1

Type: ERROR

Impact: Connector

BEA-199172: The following error occurred in the ra.xml: {0}

Cause: Refer to the text of the message for the description of the problem and the likely cause.

Action: Correct the problem in the ra.xml file.
Level: 1

Type: ERROR

Impact: Connector

BEA-199173: The following error occurred in the weblogic-ra.xml file: {0}

Cause: Refer to the text of the message for the description of the problem and the likely cause.

Action: Correct the problem in the weblogic-ra.xml file.
Level: 1

Type: ERROR

Impact: Connector

BEA-199174: The resource adapter (RA) was deactivated previously when it was in "Suspended" state. The RA cannot be activated again since this will lead to inconsistent state. Redeploy the RA to bring it back to a normal state. Current state: {0}.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199175: This ManagedConnection is managed by a container for its transactional behavior and has been enlisted to a JTA transaction by a container; application/adapter must not call the local transaction begin/commit/rollback API. Reject event {0} from adapter.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199176: Unable to execute {1} on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to perform another lookup of the Connection Factory {0} from JNDI and get a new Connection Handle.

Cause: A stale Connection Factory or Connection Handle was used.

Action: Perform another lookup of the Connection Factory from JNDI and get a new Connection Handle.
Level: 1

Type: ERROR

Impact: Connector

BEA-199177: Trying to deserialize an obsolete ConnectionManager.

Cause: Check the logs for the cause of this exception.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: ERROR

Impact: Connector

BEA-199178: Deploy side-by-side versioning of resource adapter with JNDI name {0}; old version: {1}; new version: {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199179: This adapter will not be deployed as side-by-side versioning since there is no old version adapter instance deployed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199180: This application EAR is not deployed in side-by-side versioning style.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199181: Waiting complete callback from Side-by-side versioning adapter {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199182: The resource adapter with module name {0} version {1} called ExtendedBootstrapContext.complete() to indicate it is safe to undeploy.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199183: HintsContext: Ignore unknown hint name [{0}] and its value [{1}].

Cause: An unknown hint was used.

Action: Inspect the cause and take appropriate action.
Level: 1

Type: WARNING

Impact: Connector

BEA-199184: ManagedConnectionFactory of connection pool [{0}] implements javax.resource.spi.TransactionSupport interface. Will use runtime TransactionSupport value [{2}] and igore the value [{1}] configured in DD or annotation.

Cause: A new feature was used, see Section 7.13 of the Connector 1.6 specification.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199185: There is no META-INF/validation.xml file in the adapter archive {0}. The default Bean Validation configuration will be used.

Cause: No META-INF/validation.xml file was found in the RAR archive.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199186: Found META-INF/validation.xml in adapter archive {0}.

Cause: A META-INF/validation.xml file was found in the RAR archive.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199187: Found {2} constraint violation error(s) for {0} on instance [{1}]: {3}

Cause: Bean Validation failed and got constraint violation errors.

Action: Check the adapter configuration.
Level: 1

Type: WARNING

Impact: Connector

BEA-199188: Bean validation failed when validating for {0} on bean instance [{1}]. Exception: {2}

Cause: Bean validation failed.

Action: Check the adapter configuration and exception details.
Level: 1

Type: WARNING

Impact: Connector

BEA-199189: A long-running work submission has been rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.

Cause: A long-running work submission was rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.

Action: Check the adapter configuration and increase MaxConcurrentLongRunningRequests if necessary.
Level: 1

Type: WARNING

Impact: Connector

BEA-199190: The max-concurrent-long-running-requests limit was changed from {0} to {1}.

Cause: The configuration was changed or initialized.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199191: Warning: Caller application {2} defines a shareable resource reference {1} to outbound connection pool {0}, but the pool does not support share by its design either because its transaction support level is NOTransaction or the ManagedConnectionFactory class has the @Unshareable annotation. Will treat as unshareable.

Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.

Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1

Type: WARNING

Impact: Connector

BEA-199192: Warning: Caller application {2} defines a resource reference {1} to outbound connection pool {0} without defining SharingScope explicitly. The pool does not support share by its design either because its transaction support level is NOTransaction or the ManagedConnectionFactory class has the @Unshareable annotation. Will treat as unshareable.

Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.

Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1

Type: WARNING

Impact: Connector

BEA-199193: ManagedConnection {0} of connectionInfo {1} in Connection Pool {2} has been destroyed already. Previous destroy stacktrace: {3} New destroy stacktrace: {4}

Cause: The ManagedConnection was destroyed again.

Action: Check the server log.
Level: 1

Type: WARNING

Impact: Connector

BEA-199194: Resource adapter generated unexpected exception during work event notification for event {0}. Ignored. Exception: {1}

Cause: The resource adapter generated an unexpected exception during work event notification.

Action: Check the work event processing codes of the resource adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199195: Connector annotation scan: Ignored unexpected error [{2}] when processing annotations on {0} while {1}.

Cause: Check the error message and stacktrace to determine the cause.

Action: Check error message and stacktrace to determine the appropriate action to take.
Level: 1

Type: WARNING

Impact: Connector

BEA-199196: Ignore @javax.resource.Connector annotation on class {0} since ResourceAdapter Bean {1} is already specifed in ra.xml.

Cause: ra.xml already specifies the ResourceAdapter bean to use.

Action: No action is required if this behavior is expected.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199197: An exception occurred when removing admin object {0}. Exception is: {1}

Cause: This exception occurs as the result of an attempt to unbind the admin object from JNDI.

Action: Examine the log for the exact exception. Report the error to My Oracle Support.
Level: 1

Type: WARNING

Impact: Connector

BEA-199198: An exception occurred when invoking preDestroy on {0}: {1}. Exception is: {1}

Cause: This exception occurs as the result of the CDI container calling the preDestroy method.

Action: Examine the log for the exact exception. You may need to report the error the resource adapter vendor.
Level: 1

Type: WARNING

Impact: Connector

BEA-199199: The work was rejected because it has expired before WorkManager executed it.

Cause: The time value for the startTimeout argument is too short. The WorkManager cannot start the work within the specified time period.

Action: Increase the time value for the startTimeout argument and ensure that it is big enough for WarkManager to start the work.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199200: Annotation scan/process of the resource adapter {0} resulted in the following {1} warnings: {2}

Cause: The specified resource adapter failed to pass the annotation scan/process as indicated by the listed warnings.

Action: Check warning messages and fix the annotations that are involved.
Level: 1

Type: WARNING

Impact: Connector

BEA-199201: Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.

Cause: Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.

Action: Check the errors and fix them.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199202: Ignored unexpected exception [{1}] when unregistering runtime mbean {0}.

Cause: Check error message and stack trace to figure out the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199211: Compliance checking and validation of the resource adapter {0} resulted in the following non-critical errors: {1}

Cause: The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.

Action: Correct the ra.xml or weblogic-ra.xml files, or check the resource adapter archive.
Level: 1

Type: WARNING

Impact: Connector

BEA-199212: Failed to create connection pool [{0}] due to error: {1}

Cause: Check the reported error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: ERROR

Impact: Connector

BEA-199213: A new error occurred when trying to destroy a connection pool [{0}] that was previously in a failed state : the following new error will be ignored: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199214: The connection pool [{0}] was in a HEALTH_CRITICL state already, therefore this method call is not allowed.

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: NOTIFICATION

Impact: Connector

BEA-199215: The connection pool [{0}] will move to a HEALTH_CRITICAL state because the adapter is not in deploy-as-a-whole mode. This pool failed due to errors: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199216: An error occurred when performing action {2} on connection pool [{0}]. The following error will be ignored: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Take appropriate action based on the cause determined from the reported error message and stack trace.
Level: 1

Type: WARNING

Impact: Connector

BEA-199217: Connection pool [{0}] has validation errors and cannot be reset. Try to fix all validation errors and then do a dynamic update or redeploy this adapter.

Cause: Check the error message and stack trace to determine the cause.

Action: Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199218: Unable to determine whether properties were changed for Connection pool [{0}]. If there are changed properties, they may be ignored during a dynamic update: {1}

Cause: Check the error message and stack trace to determine the cause.

Action: Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
Level: 1

Type: WARNING

Impact: Connector

BEA-199219: Invalid shrink threshold value {0} specified for the system property weblogic.connector.cmm.shrinkThreshold. Value must be between 0 and 10 (inclusive).

Cause: The value of the system property weblogic.connector.cmm.shrinkThreshold is invalid.

Action: Check the value of the system property weblogic.connector.cmm.shrinkThreshold. Ensure that it is between 0 and 10 (inclusive). A value of 0 indicates that the connector will not take any action on any memory pressure level.
Level: 1

Type: ERROR

Impact: Connector

BEA-200000: Failed to initialize the messaging bridge service.

Cause: Most of the time, this results from configuration errors.

Action: Check the configuration file and reboot the system.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200001: The messaging bridge service has successfully shut down.

Cause: This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200002: Failed to deploy the messaging bridge "{0}" because the messaging bridge service is shut down.

Cause: This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.

Action: Reboot the system.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200003: Failed to deploy the messaging bridge "{0}" due to error: {1}.

Cause: This is likely due to configuration errors or an internal error as indicated in the message body.

Action: Check the configuration file, and reboot the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200004: The messaging bridge "{0}" has been successfully deployed.

Cause: This message indicates that the messaging bridge has been successfully deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200005: Failed to start messaging bridge "{0}" due to error: {1}

Cause: This is likely due to configuration errors or an internal error, as indicated in the message body.

Action: Check the configuration file, and reboot the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200008: Bridge "{0}" does not have a configured source destination.

Cause: This is likely due to configuration errors.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200009: Bridge "{0}" does not have a configured target destination.

Cause: This is likely due to configuration errors.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200011: The bridge "{0}" failed to find the adapter "{1}". The bridge will periodically retry to look up the adapter. If this message stops reappearing, it means that the bridge has finally successfully found the adapter.

Cause: One of the adapters was not deployed.

Action: Deploy the required adapters.
Level: 1

Type: WARNING

Impact: MessagingBridge

BEA-200012: Bridge "{0}" successfully found the adapters that are configured for it.

Cause: This message indicates that the bridge successfully found the adapters.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200013: Invalid properties are defined for the source destination of bridge "{0}".

Cause: The configuration was invalid.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200014: Invalid properties are defined for the target destination of bridge "{0}".

Cause: The configuration was invalid.

Action: Update the configuration, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200015: An error occurred in bridge "{0}" during the transfer of messages ({1}).

Cause: An error occurred on one of the bridge destinations.

Action: Check the system on both the source and target sides, and restart the server.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200020: Bridge "{0}" is stopped.

Cause: This message indicates that the messaging bridge has stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200021: Bridge "{0}" failed to get one of the adapters from JNDI ({1}).

Cause: At least one adapter was not deployed when the bridge started. It is also possible that the JNDI names configured in the bridge destinations do not match the ones in the adapter deployment descriptor file.

Action: Check to see if the adapter(s) required by the source and target destinations are deployed on the server where the bridge is configured. Ensure that the JNDI name in the adapter deployment descriptor file matches the one in the configuration of the bridge destinations. Otherwise, no action is required. The bridge will automatically try again later.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200022: Bridge "{0}" failed to obtain adapter metadata ({1}).

Cause: This is an internal error that should not occur.

Action: No action is required.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200024: Bridge "{0}" refused to obtain connections and transfer any messages, because it has been stopped, suspended, or is shutting down.

Cause: The administrator has shut down or stopped the bridge, or the bridge is suspended for migration.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200025: Bridge "{0}" failed to start because the quality of service configured ({1}) is unreachable. This is likely due to an invalid configuration or adapter limitations.

Cause: The configuration does not match the ability of the adapters and underlying systems.

Action: Change the configuration of the bridge with a reachable quality of service, or turn on the QOSDegrationAllowed boolean.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200026: Bridge "{0}" encountered problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception that occurred was {1})

Cause: There was a problem in receiving or sending messages to one of the sides of the bridge.

Action: No action is required.
Level: 1

Type: WARNING

Impact: MessagingBridge

BEA-200027: Bridge "{0}" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.

Cause: This may occur because the source destination is empty or because the connection to the source was stale and needs to be reestablished.

Action: Check the source system.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200028: The bridge "{0}" has started transferring messages.

Cause: This message indicates that the bridge has just started transferring messages.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200030: Bridge "{0}" is configured to work in "{1}" mode, but it is actually working in "{2}" mode.

Cause: This message reveals what quality of service the bridge is actually providing.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200031: Bridge "{0}" is configured to allow degradation of its quality of service in cases where the configured quality of service cannot be reached.

Cause: This message indicates that the quality of service of this bridge is allowed to be downgraded if the required one is unreachable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200032: Bridge "{0}" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.

Cause: This message indicates that the quality of service of the bridge is not allowed to be downgraded.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200033: Bridge "{0}" is obtaining connections to the two adapters.

Cause: This message indicates that the messaging bridge is obtaining connections to the two adapters.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200034: Bridge "{0}" is shut down.

Cause: This message indicates that the messaging bridge is shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200035: Bridge "{0}" has been started from the stopped mode.

Cause: This message indicates that the bridge was in stopped mode and has just been restarted.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200036: The started attribute of bridge "{0}" has been changed from "{1}" to "{2}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200037: The "{1}" attribute of bridge "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200038: Bridge "{0}" is inactive because it is configured to be stopped.

Cause: The bridge is configured to be stopped.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200039: Bridge "{0}" has the same destination as its source and target.

Cause: This is due to a configuration error.

Action: Update the configuration.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200040: Bridge destination {0}: connection URL cannot be null if the initial context factory is not weblogic.jndi.WLInitialContextFactory.

Cause: This is due to a configuration error.

Action: Update the configuration.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200041: Bridge destination {0}: a bridge destination for JMS must have a connection factory JNDI name and a destination JNDI name configured.

Cause: This is due to a configuration error.

Action: Update the configuration.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200042: Bridge {0} failed to connect to the source destination and will try again in {2} seconds. This could be a temporary condition unless the messages repeat several times. ({1})

Cause: An error occurred on the source destination of the bridge. The error may occur because the source destination does not exist or has not been active yet.

Action: Check the source system and its configuration. Ensure that the destination is configured in the system and the system is running.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200043: Bridge "{0}" failed to connect to the target destination and will try again in {2} seconds. This could be a temporary condition unless the messages repeat several times. ({1})

Cause: The error occurred on the target destination of the bridge. The error may occur because the target destination does not exist or has not been active yet.

Action: Check the target system and its configuration. Ensure that the destination is configured in the system and the system is running.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200044: The following exception has occurred:

Cause: An error condition has occurred.

Action: Look for the associated exception in the log or the program to see the results. In general, this stack trace will help in debugging an existing problem.
Level: 1

Type: ERROR

Impact: MessagingBridge

BEA-200045: Bridge "{0}" failed to start because it has been suspended or is shutting down.

Cause: The administrator has shut down the bridge, or the bridge is suspended for migration.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200046: The "{1}" attribute of bridge "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-200047: Bridge "{0}" failed to start because its migratable target has not been activated for this server.

Cause: The bridge is targeted to a migrable target that has not yet been activated on this server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MessagingBridge

BEA-220000: Web services startup

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220001: The server at {0} did not provide a valid HTTP response: {1}

Cause: The server may not be properly configured.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220002: The server at {0} did not provide a valid HTTP response: {1}

Cause: The HTTP header status length does not agree.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220003: The server at {0} did not provide a valid HTTP response: {1}

Cause: The server is not providing HTTP V1.0 or V1.1 protocol.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220004: The server at {0} did not provide a valid HTTP response: {1}

Cause: The returned server status code was not recognized.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220005: The server at {0} did not provide a valid HTTP response: {1}.

Cause: The server status code was given.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220006: Content-length was specified but no value was provided.

Cause: The content-length field must contain a value.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220007: The specified content-length {0} is invalid.

Cause: The provided content-length field is invalid.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220008: HTTP keep-alive was specified, but the content-length was not set.

Cause: The provided content-length field is invalid.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220009: Received EOF before reading the entire message from the server.

Cause: The server sent an EOF (end-of-file) before the entire message was received.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220010: A MIME-encoded SOAP response must include a content-type mime header specifying the MIME start and boundary.

Cause: The content-length was zero or the content-type was null. An attachment, however, was provided.

Action: Verify the server configuration and retry the request.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220011: A bad value was provided for {0} : {1}. The default value will be used: {2}.

Cause: The value was not correctly provided.

Action: Correct the system configuration and retry the request.
Level: 1

Type: WARNING

Impact: WebService

BEA-220012: The ID may not be null.

Cause: The XML stream may be corrupted.

Action: Check the content of the XML stream and retry the message.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220013: The ID referenced by {0} is unknown.

Cause: The XML stream is invalid or corrupted.

Action: The unknown ID must be resolved and the action retried.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220014: Incorrect XML stream open. Use open(XMLNode node) to open this stream.

Cause: The module was incorrectly called.

Action: Correct the program to use XMLNode. After doing so, retry the action.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220015: Incorrect XML stream open. Use open(XMLNode node) to open this stream.

Cause: The module was incorrectly called.

Action: Correct the program to use XMLNode. After doing so, retry the action.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220016: The start element was not found.

Cause: The XML stream is corrupted.

Action: Correct the XML stream and retry the task.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220017: Element {0} is not a start element.

Cause: The XML stream is corrupted.

Action: Correct the XML stream and retry the task.
Level: 1

Type: INTERNAL_ERROR

Impact: WebService

BEA-220018: The handler class:{0} issued an exception from its destroy method. This exception is ignored. The exception was: {1}.

Cause: A handler class issued an exception from its destroy method.

Action: Correct the handler Handler.destroy implementation.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220019: The Web services server responded with an empty HTTP response. The content-length of the response was 0.

Cause: The HTTP response had a content-length of 0.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220020: The Web services call to {0}://{1}:{2} received an unexpected end of file (EOF) after reading {3} bytes.

Cause: The HTTP response had an unexpected EOF.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220021: The Web services call to {0} received an unexpected HTTP version {1}.{2} in the response:{3}.

Cause: The HTTP response had an unexpected version.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220022: Error reading the response from: {0}. Please ensure that this is a valid SOAP response. The message was: {1}

Cause: The HTTP response had an unexpected version.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220023: Ignoring an exception in destroy() from Handler: {0}. The exception was: {1}.

Cause: An exception occurred in the handler destroy() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220024: Handler {0} issued an exception from its handleRequest method. The exception was: {1}.

Cause: An exception occurred in the handler handleRequest() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220025: Handler {0} issued an exception from its handleResponse method. The exception was: {1}.

Cause: An exception occurred in the handler handleResponse() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220026: Handler {0} issued an exception from its handleFault method. The exception was: {1}.

Cause: An exception occurred in the handler handleFault() method.

Action:
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220027: Web services reliable agents have been started on the server.

Cause: Web services reliable agents have been started on the server.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220028: Web services reliable agents are suspended.

Cause: Web services reliable agents are suspended.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220029: Web services reliable agents are shut down.

Cause: Web services reliable agents are shut down.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220030: Failed to create Web services reliable agents. {0}.

Cause: There is a configuration error Administration Server failure.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: WebService

BEA-220031: The server does not support reliable SOAP messaging.

Cause: The server does not support reliable SOAP messaging.

Action: Check the configuration.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220032: Failed to create MessageContext after a SOAP message was recovered from the storage. {0}.

Cause: There was an invalid format from the store or an error accessing the store.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebService

BEA-220033: Failed to access the store for reliable delivery. {0}.

Cause: There was a failure accessing JMS.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: WebService

BEA-220034: A stack trace associated with message {0} follows:

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220035: A naming exception occurred while obtaining the initial context.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220036: An exception occurred while obtaining the JMS connection factory.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220037: An exception occurred while obtaining the JMS initial context.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220038: An exception was issued from the onMessage JMS.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220039: A naming exception was issued from the JMS send message.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220040: An exception was issued from JMS while obtaining the initial factory.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220041: An exception was issued from JMS when sending to the destination.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220042: A naming exception was issued from JMS for this queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220043: An exception was issued from JMS obtaining the factory.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220044: An exception was issued from JMS locating this queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220045: An exception was issued getting the conversational state.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220046: A remote exception was issued when getting the conversational state.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220047: An exception was issued from callReceive in the Client Dispatcher.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220048: An exception was issued from the client handler sending a JAXM message.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220049: A SOAP exception was issued from the client conversation handler.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220050: A SOAP exception was issued from the server conversation handler.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220051: A SOAP exception was issued from the Invoke handler.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220052: The target endpoint is a malformed URL.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220053: An unexpected exception was caught in the SOAP Envelope InputStream.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220054: An unexpected exception was caught in the SOAP Envelope Reader.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220055: A parse exception was caught in the SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220056: A parse exception was caught in the get SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220057: A messaging exception was caught while processing MIME SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220058: A messaging exception was caught writing MIME SOAP Message content.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220059: A SOAP header exception was caught in setMustUnderstand.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220060: A SOAP header exception was caught in setActor.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220061: A Naming Exception was caught in the deployment descriptor verify.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220062: A Message Exception was caught in the Image Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220063: A IO Exception was caught in the Image Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220064: A Message Exception was caught in the XML Source Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220065: A IO Exception was caught in the XML Source Encoding Codec.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220066: An InvalidAttributeValue Exception was caught trying to create the JMS Queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220067: A JMS Exception was caught when the listener was being closed.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220068: An exception was caught when introspecting the component.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220069: A Naming Exception was caught trying to locate the JMS transport.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220070: A JMS Exception was caught trying to create the JMS queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220071: A SOAPException was caught in the onMessage listening to the JMS queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220072: An IOException was caught in the onMessage listening to the JMS queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220073: A SOAPException was caught in the servlet base unable to invoke the service.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220074: A SOAPException was caught in the servlet base unable to send to the client.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220075: A SOAPException was caught in the servlet base unauthorized to send to the client.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220076: An exception was caught in the Web services servlet initialization.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220077: An exception was caught while processing the Web services deployment descriptor.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220078: An exception was caught when configuring the Web services servlet.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220079: An Interrupt exception was caught while waiting to send mail from the queue.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220080: An error was reported from the SMTP gateway.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220081: An IOException was reported from the SMTP quit command.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220082: An IOException was reported from the SMTP process read command.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220083: An IOException was reported from the SMTP process close command.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220084: A Binding exception was issued while trying to generate the implementation class.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220085: A JAXRPC exception was issued while trying to generate the implementation class.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220086: A IOException was issued while trying to generate the implementation class.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220087: A Binding exception was issued while trying to generate the EJB implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220088: A JAXRPC exception was issued while trying to generate the EJB implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220089: An IOException was issued while trying to generate the EJB implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220090: A Binding exception was issued while trying to generate the client implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220091: A JAXRPC exception was issued while trying to generate the client implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220092: An IOException was issued while trying to generate the client implementation.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220093: A naming exception was issued while trying to check compliance of the given EJB.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220094: An IOException was issued while trying to access the WSDL at the given URL.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220095: An IOException was issued while converting the file to a string.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220096: A naming exception was issued from JMS for this queue.

Cause: An error condition was reported.

Action: Make sure that the queue can be accessed from this server.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220097: An exception was issued from JMS while obtaining the factory.

Cause: An error condition was reported.

Action: Make sure that the queue can be accessed from this server.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220099: Web service for Web application named {0} contextPath {1} with Web services {2} has been initialized.

Cause: This indicates a successful Web service deployment.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220100: An error occurred while registering this Web service for monitoring. Although this does not affect the Web service itself, monitoring information about it may be unavailable. The specific error was {0}.

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

BEA-220101: An error occurred while loading class {1} from handler-chain {0} in global handler configuration. Error is: {2}

Cause: The configured class is not present in the classpath.

Action: Check the classpath and try again.
Level: 1

Type: ERROR

Impact: WebService

BEA-220102: An error occurred while loading global handler chain. Error is: {0}

Cause: An error may have occurred while parsing the server-handler-chain.xml file.

Action: Check the server-handler-chain.xml file and ensure that the syntax is correct.
Level: 1

Type: ERROR

Impact: WebService

BEA-220103: Async Web service support is not fully configured. The async response Web service {0} for this server was not fully deployed because the JMS reliability queue was not defined/deployed: {1}. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async Web service applications. To completely disable async Web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.

Cause: The JMS queue JNDI name specified in the WebservicesMBean (or allowed to default) was not found on this server. The async response service requires this JMS queue in order to operate. To avoid obscure errors while processing Web service async responses, this service was not fully deployed. Not having this JMS queue available can indicate that Web services have not been configured/enabled for this domain. The server will periodically retry deploying the service, so there is no need to restart the server once the JMS queue is made available.

Action: If you do not intend to use async Web services in this domain, no action is required. To avoid seeing this message and completely disable async Web service support, set -Dweblogic.wsee.skip.async.response=true. If you intend to use async Web services in this domain, define a non-distributed JMS queue with the local JNDI name given in WebservicesMBean (which has a default value), and after a short delay, the async response service will be fully deployed to use the newly defined queue. Oracle recommends that the JMS queue be located on a JMS server that is targeted to the same server as the Web service. Note that you can easily add async response Web services support to an existing domain by extending your domain with the Configuration Wizard and applying the wls_webservice.jar extension template. For more information, see the WebLogic Server online documentation in the 'Web Services->Get Started Using JAX-RPC' section.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220104: Web services async response service {0} for this server was just deployed because the reliability queue was found: {1}

Cause: The queue specified in the WebservicesMBean (or allowed to default) was recently deployed to this server. The async response service requiring this queue is now deployed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220105: Web services async/reliable invocations for service {0} are NOT available because the async/reliability queue was not found: {1}

Cause: You have deployed a Web service that indicates it can use async/reliable features, but the queue for async/reliable invocations (specified in WebservicesMBean, @Buffer or @ReliabilityBuffer annotations, or allowed to default) is not deployed to the local server. Therefore, async and reliable invocations will fail if attempted. Standard synchronous invocations will still work correctly despite this problem.

Action: Remove any async or reliable features from the Web service (e.g. @AsyncResponse, @Buffer, @ReliabilityBuffer annotations or @Policy annotations specifying reliable policy) or properly configure this server for async/reliable invocations. See the WebLogic Server online documentation in the 'Web Services->Get Started Using JAX-RPC' section for help on fixing this configuration problem. Once you have defined the proper async/reliable resources, you must redeploy your application.
Level: 1

Type: WARNING

Impact: WebService

BEA-220106: OWSM Security requires that a WSDL be associated with the Web service.

Cause: You have deployed a Web service that does not have a WSDL associated with it.

Action: Associate a WSDL with the Web service. For example you can add a wsdlLocation attribute to a WebService or WebServiceProvider annotation.
Level: 1

Type: ERROR

Impact: WebService

BEA-220500: An unexpected error occurred: {0}

Cause: Unknown

Action: Contact Oracle support
Level: 1

Type: ERROR

Impact: WebService

BEA-220501: The service port {1} bound to https transport in service {0} is NOT available, the https address cannot be resolved because SSL is not enabled for the server. The service port definition will be removed from WSDL that is being accessed through {2}.

Cause: While a WSDL is being retrieved through http protocol, the server requires replacing the service port address in WSDL with the actual address for the server. For any web service which defines one or more service ports bound to https transport, if the domain does not enable SSL functionality then the service port address could not be replaced correctly because https address for the server cannot be resolved.

Action: Enable SSL functionality for the server.
Level: 1

Type: WARNING

Impact: WebService

BEA-220502: The Wsee Service is starting

Cause: This is an info message. No cause is needed

Action: No action required. This is an info message.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220503: The Wsee Service is stopping

Cause: This is an info message. No cause is needed

Action: No action required. This is an info message.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220504: The Wsee Service is halting

Cause: This is an info message. No cause is needed

Action: No action required. This is an info message.
Level: 1

Type: NOTIFICATION

Impact: WebService

BEA-220505: Implicit/generated Client Identity {0} has been used in multiple calls to Service.getPort()/createDispatch() where these calls have used different services and/or sets of features. Monitoring statistics for this client will include all these different usages. Validation failures were: {1}

Cause: WebLogic JAX-WS web service clients are assigned a unique identity that is intended to represent the business purpose of that client. This identity can be specified directly using weblogic.jws.jaxws.client.ClientIdentityFeature or it can be allowed to be implicit. Implicit identity is generated automatically based on environmental information at the point where a Port/Dispatch instance is created. Your code has received an implicit client identity that is getting used (again implicitly) across multiple services or sets of features. All statistics gathered for a given client instance are rolled up under the client instance's client identity. If client instances using different services and/or feature sets contribute statistics to the same client identity, this can be confusing. It is even possible for clients to behave incorrectly when more advanced web service features are used.

Action: Best practice is to create a specific client identity (with a name representing a logical business purpose) for the client and denote this identity by passing weblogic.jws.jaxws.client.ClientIdentityFeature to the call to Service.getPort/createDispatch. Further, it is recommended that you pass a single/global set of web service feature objects to that call (e.g. Create WebServiceFeature instances as static class members or in a method annotated with @PostConstruct for containers compatible with this annotation). The actual call to Service.getPort()/createDispatch() should still be made in any way that makes sense for your uses (e.g. calling getPort on demand in a web service method, with Service created as a static class member).
Level: 1

Type: WARNING

Impact: WebService

BEA-225010: Error starting the JMS listener {0} {1}

Cause: A connection to the JMS replyToQueue could not be made.

Action: Verify that the proper queue name is being used, and check the status of JMS queue.
Level: 1

Type: WARNING

Impact: WebService

BEA-225011: Error closing JMS connection {0} {1}

Cause: The JMS queue connection could not be closed.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

BEA-225012: JMS onMessage exception {0} {1}

Cause: An error condition was reported.

Action: No action is required.
Level: 1

Type: WARNING

Impact: WebService

BEA-240001: {0}

Cause: The Administration Console logs informational messages about console usage.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Console

BEA-240002: {0}

Cause: The Administration Console encountered an error that is potentially harmful.

Action: Review the warning message text to determine the appropriate action.
Level: 1

Type: NOTIFICATION

Impact: Console

BEA-240003: Administration Console encountered the following error: {0}

Cause: The Administration Console encountered an error, but the console may continue to run.

Action: Review the error message text to determine the appropriate action.
Level: 1

Type: ERROR

Impact: Console

BEA-240004: The Administration Console encountered the following error: {0}

Cause: The Administration Console encountered a critical error.

Action: Review the message text to determine the appropriate action.
Level: 1

Type: INTERNAL_ERROR

Impact: Console

BEA-240005: A Cross-site Request Forgery (CSRF) has been detected. Task={0}, address={1}, user={2}

Cause: The Administration Console encountered a CSRF.

Action: Take action based upon the provided exception details.
Level: 1

Type: INTERNAL_ERROR

Impact: Console

BEA-260000: WebLogic Local Deployment Manager

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260001: "{0}" does not identify a known Deployment Manager. The URI must be of the form: deployer:WebLogic:host:port. The host and port are required if attempting to acquire a connected Deployment Manager.

Cause: An invalid URI was provided when allocating a Deployment Manager.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260002: "{0}" is not a valid URI. The URI must be of the form: "deployer:WebLogic:protocol://host:port". The host and port are required if attempting to acquire a connected Deployment Manager. The protocol should be a well-known IP protocol.

Cause: Incorrect host/port used when attempting to allocate a Deployment Manager.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260003: Feature not available when in disconnected mode.

Cause: A deployment tool allocated a disconnected Deployment Manager or released it.

Action: Allocate a connected Deployment Manager.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260004: Locale, "{0}", is not supported.

Cause: The locale was incorrectly specified.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260008: J2EE version {0} not supported by this Deployment Manager.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260009: Exception caught for class "{0}" while attempting to create Deployment Manager: {1}

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260010: Unable to connect to "{0}" as user, "{1}". Error received: {2}

Cause: Authorization failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260012: No configured targets match provided target with name, "{0}", and type, "{1}"

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260013: The target array passed to Deployment Manager was null or empty.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260015: The "{0}" operation is not supported.

Cause: An invalid request was made; the operation is not supported.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260016: "{0}" does not exist.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260017: Unable to locate deployment task, "{0}"

Cause: The task was removed from the system.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260020: Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260021: Module {1} of application {0} failed to transition from {2} to {3} on server {4}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260022: {2} application {0} on server {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260023: Deployment task does not exist for ProgressObject

Cause: The deployment task was removed from the system.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260024: Connection errors occurred while reporting a progress event. The event was from application, {0}, module, {1}, on server {2}. The event was {3}. The error was {4}.

Cause: There was a deployment failure.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260026: Task failed for unknown reason. Task description is {0}

Cause: The cause is unknown.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260027: Non-root module, "{1}", is not supported for {0} operations. All modules must represent root modules.

Cause: All modules must represent root modules. This operation does not support embedded modules.

Action: Use DeploymentManager.enableModuleTargeting.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260028: No targeting information was provided for {0} operation.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260029: "{1}" is not part of application, "{2}". Only one application allowed for {0} operation.

Cause: Multiple applications were specified in the same operation. An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260030: Module, "{0}", is not part of any application.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260031: No action performed or required for {0} request.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260036: Module type, "{0}", is not supported.

Cause: The operation is unsupported.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260037: Encountered unexpected descriptor for module "{0}".

Cause: An invalid application descriptor was used in the EAR file.

Action: Fix the application descriptor.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260040: No files provided in {0} request.

Cause: At least one file must be specified for update.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260041: Unable to upload "{1}" to "{0}"

Cause: Check the log for further details. Requested files need to be uploaded to a remote Administration Server.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260050: "{0}" does not implement weblogic.deploy.api.spi.WebLogicDConfigBeanRoot, or cannot be instantiated: {1}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260052: null DConfigBeanRoot.

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260055: Unable to parse deployment plan: "{0}".

Cause: The document is invalid and could not be read or parsed during a deployment operation.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260056: MBean must be for Application or Component: "{0}".

Cause: An invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260061: Unable to recognize DDBean with xpath, "{0}".

Cause: Unable to restore configuration from an invalid descriptor; an invalid argument was used.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260067: Restored configuration for module, {0}

Cause: DeploymentConfiguration.restoreDConfigBean was invoked

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260068: Removed configuration for module, {0}

Cause: DeploymentConfiguration.removeDConfigBean was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260070: Saved configuration for module, {0}

Cause: DeploymentConfiguration.saveDConfigBean was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260071: Restored configuration for application, {0}

Cause: DeploymentConfiguration.restore was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260072: Saved configuration for application, {0}

Cause: DeploymentConfiguration.save was invoked.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260073: Unable to introspect on bean, "{0}".

Cause: This is an internal error.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260078: No DConfigBean is available for invalid module, "{0}": {1}.

Cause: Check the error message for the specific problem.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260080: Unable to define the application install directory at "{0}". Directory could not be created or is a file.

Cause: The directory could not be created or is a file.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260081: The descriptor at "{0}" could not be parsed.

Cause: The descriptor contains syntax errors and is invalid.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260082: A required descriptor, {0}, for a CMP bean is missing.

Cause: A descriptor file is missing.

Action: Place the necessary descriptor file in the archive file or its external configuration area.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260083: No plan document at "{0}"

Cause: The path for the plan may have been incorrectly specified. If this is the first time the application is being configured; this may not be a problem; the plan will be created.

Action: Specify the correct plan location as necessary.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260085: The configuration descriptor for "{0}" already exists ( {1} ), or was not modified ( {2} ), and will not be saved.

Cause: The descriptors do not need to be saved.

Action: No action is required.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260086: The descriptor information at {0} was saved to the configuration area.

Cause: The configuration was saved.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260087: The descriptor at "{0}" is missing the required {1} element for custom module with URI, "{2}", and provider, "{3}".

Cause: The named element is missing from the weblogic-extensions.xml descriptor.

Action: Correct the errors in the weblogic-extensions.xml descriptor.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260088: The {1} descriptor at "{0}" is missing.

Cause: The referenced JMS/JDBC descriptor is not present in the archive.

Action: Ensure that all of the descriptors are in place.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260091: Errors were detected when reading "{0}": {1}

Cause: Check the error message to determine the probable cause.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260094: Registering config module descriptor support with base URI, {0}, and configuration URI, {1}.

Cause: The weblogic-extensions descriptor specified custom configuration descriptor support.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260095: Unable to create archive for "{0}"

Cause: An attempt to name a file with the appropriate extension failed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260096: Unable to determine type of application for "{0}".

Cause: The archive does not contain standard descriptors.

Action: Ensure that the correct file was passed into the deployment operation.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260097: Unable to understand DDBeanRoot provided by deployer tool: "{0}".

Cause: The model API is not providing the expected information

Action: Resolve API problems in the class that implements javax.enterprise.deploy.model.DDBeanRoot.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260098: No descriptor type is registered for modules of type, {0}

Cause: The module type is not registered with a configurable descriptor.

Action: Register non-standard descriptors using the weblogic-extension.xml descriptor.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260099: No root element in {0} descriptor, {1} at {2}.

Cause: An invalid deployment descriptor was provided for the module.

Action: Either the wrong descriptor was specified or the module type is incorrect; take the appropriate actions to fix the problem.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260100: Invalid value for Security Model, {0}; Should be one of {1}.

Cause: An unrecognized security model was requested.

Action: Use a valid security model
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260101: Parameter "{0}" may not be null.

Cause: A null parameter was passed to the method.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260102: Type parameter, "{0}", provided to export method is invalid

Cause: An invalid export type parameter was used.

Action: Use a valid export type.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260103: The provided bean is not part of this configuration: "{0}".

Cause: An attempt was made to export bean properties against the wrong DConfigBeanRoot object

Action: Invoke export on the correct DConfigBeanRoot.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260104: {0} is not a changable property

Cause: One of the properties is not changeable.

Action: Remove the property that is not changeable from the list.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260106: Failed to parse descriptor at "{1}" for module "{0}": {2}.

Cause: The descriptor is not valid

Action: Ensure that the application is accessible and contains valid descriptors.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260107: Failed to write descriptor for module "{0}" configuration: {1}.

Cause: Either an I/O error prevented the save operation or the descriptor is missing some required elements.

Action: Depends on the specific error. See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260108: Failed to restore descriptors: {0}.

Cause: An I/O or parse error prevented the restore operation.

Action: The course of action depends on the specific error. See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260109: Failed to write deployment plan: {0}.

Cause: Either an I/O error prevented the save operation or the plan is missing some required elements.

Action: The course of action depends on the specific error; see the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260110: Failed to create configuration for module: {0}

Cause: The configuration artifacts for the application could not be processed. This could result from simple access errors, descriptor parsing failures, or basic application architecture problems.

Action: The course of action depends on the specific error. See the error message for details.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260111: Errors were detected while attempting to communicate with the Administration Server.

Cause: Depends on the specific error. The associated exception will contain the root exception.

Action: The course of action depends on the specific error. See the exception.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260112: Unable to determine application name from null or empty TargetModuleID list.

Cause: No TargetModuleID objects were provided.

Action: Resolve the client programming error by providing a list of TargetModuleID objects.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260113: Plan at "{0}" is a directory. A deployment plan is always an XML document.

Cause: Plan at "{0}" is a directory, not an XML document.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260114: Application root at "{0}" is not a directory.

Cause: An invalid root directory was specified.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260115: Must specify application to configure.

Cause: No application was specified for the configuration.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260116: Configuration is not initialized

Cause: SessionHelper.initialize() was not yet invoked.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260117: Unable to load factory, "{0}"

Cause: The factory is not in the classpath.

Action: Ensure that the factory is in the classpath.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260118: A null target was included in a deployment request.

Cause: The target list is invalid.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260119: The path provided, "{0}", does not represent a directory.

Cause: The first argument must be a directory.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260121: Initiating {0} operation for application, {1} [archive: {2}], to {3}.

Cause: A deployment operation is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260122: Initiating {0} operation for application, {1}, from stream to {2}.

Cause: A deployment operation is starting.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260123: Unable to determine targets for deployment request on application, {0}

Cause: No targets were specified for the new deployment.

Action: Specify the targets to which you want to deploy the application.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260124: configured targets

Cause: No targets were specified.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260125: Errors were detected when attempting to communicate with Administration Server: {0}

Cause: Depends on the specific error. The associated exception will contain the root exception.

Action: The course of action depends on the specific error. See the exception.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260126: Cannot override plan version, "{0}", with version from options, "{1}".

Cause: A plan version was specified in the deployment options, but the plan defines its own version.

Action: Avoid specifying the plan version.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260128: Changes not allowed to DTD based descriptors. The attempt to modify property "{0}" in {1} for module "{2}" will be vetoed if possible. The change will not be persisted in either case.

Cause: A property in a DTD based descriptor was modified.

Action: Upgrade the application with schema based descriptors.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260129: Export not allowed on DTD based descriptors. No properties for the {0} descriptor in module, "{1}", will be exported.

Cause: An attempt was made to export a DTD based descriptor.

Action: Upgrade the application with schema based descriptors.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260130: Shutting down Deployment Manager connection due to an internal error.

Cause: An internal error occurred.

Action: Allocate a new Deployment Manager.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260131: No URI was provided.

Cause: An attempt was made to create a Deployment Manager without providing an appropriate deployer URI.

Action: Provide an appropriate deployer URI.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260132: "{0}" is not a child of "{1}".

Cause: "{0}" is not a child of "{1}".

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260133: The descriptor at "{0}" could not be parsed due to error: {1}.

Cause: The named descriptor is invalid.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260134: Unable to identify application for {0} operation.

Cause: Insufficient information was provided to identify which application to deploy.

Action: Resolve the client programming error.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260137: Failures were detected while restoring the original plan file {0}. The current plan may not reflect the accurate state of the application. Either attempt to update the application again with the current plan, or make use of the backup plan "{1}".

Cause: Failures were detected while restoring the original plan file {0}. The current plan may not reflect the accurate state of the application.

Action: Either attempt to update the application again with the current plan or make use of the backup plan "{1}".
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260138: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.

Cause: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.

Action: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.
Level: 1

Type: WARNING

Impact: J2EE Deployment SPI

BEA-260139: Unchanged plan.xml was restored due to problems updating new plan {0}.

Cause: Unchanged plan.xml was restored due to problems updating new plan {0}.

Action: Unchanged plan.xml was restored due to problems updating new plan {0}.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260140: Unable to remove descriptor bean {0} due to "{1}". The remover should first check to see if the bean is removable in the deployment plan prior to removing it.

Cause: Unable to remove descriptor bean {0} due to {1}.

Action: The remover should first check to see if the bean is removable in the deployment plan prior to removing it.
Level: 1

Type: NOTIFICATION

Impact: J2EE Deployment SPI

BEA-260141: An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().

Cause: An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().

Action: Call close() on the SessionHelper instance, and avoid reusing the same instance.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-260142: The descriptor at "{0}" in module "{1}" is not recognized, and could not be parsed.

Cause: The descriptor was not recognized and could not be parsed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: J2EE Deployment SPI

BEA-280008: Opening the persistent file store "{0}" for recovery: directory={1} requestedWritePolicy="{2}" fileLockingEnabled={3} driver="{4}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280009: The persistent file store "{0}" ({1}) has been opened: blockSize={2} actualWritePolicy="{3}" explicitIOEnforced={4} records={5}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280012: Recovery is not yet complete.

Cause: This was caused by a programming error.

Action: Check the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280013: The specified store record is longer than the maximum length of {0} bytes.

Cause: This was caused by a programming error.

Action: Either change the code or increase the size of the record.
Level: 1

Type: ERROR

Impact: Store

BEA-280019: There was an error while writing to a storage.

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that there is enough space available for the storage area.
Level: 1

Type: ERROR

Impact: Store

BEA-280020: There was an error while reading from the storage.

Cause: See the detail message for the cause.

Action: Ensure that the hardware and operating system are functioning properly and that all the storage spaces are available online.
Level: 1

Type: ERROR

Impact: Store

BEA-280021: There was an error while opening the file store file "{0}".

Cause: Either the specified file does not exist, the server does not have permissions to open the file, or there is a hardware or operating system problem.

Action: Ensure that the file exists and that the directory name was specified correctly.
Level: 1

Type: ERROR

Impact: Store

BEA-280024: There was an error while creating a new file named "{0}" for the file store.

Cause: See the detail message. The disk may be full, or there may be a hardware or operating system problem.

Action: Ensure that there is enough disk space and that the hardware and operating system are working properly.
Level: 1

Type: ERROR

Impact: Store

BEA-280026: The primary or cache file "{0}" is not both readable and writeable.

Cause: The file permissions are incorrect, or the server is running under the wrong user ID.

Action: Fix the file permissions or run the server under the correct user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280029: The store record {0} could not be found.

Cause: This is caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280031: The store named "{0}" has not yet been opened.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280032: The store suffered a fatal error and it must be reopened.

Cause: A fatal error occurred previously.

Action: Restart the server.
Level: 1

Type: ERROR

Impact: Store

BEA-280035: Unable to access the store directory "{0}".

Cause: See the detail message.

Action: Check that the specified path name is correct, that it exists, and that the directory is readable and writeable by the server's user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280036: Missing the file store file "{0}" in the directory "{1}".

Cause: The file has been accidentially deleted or moved, or the wrong directory name was specified, or the server process does not have permissions to read and write the file.

Action: Ensure that the directory name is correct and that the server process has permissions to read and write the files. If necessary, create an empty file with the same name.
Level: 1

Type: ERROR

Impact: Store

BEA-280037: The file store has reached the maximum number of {0} files and no more files can be created.

Cause: There are too many records in the store.

Action: Delete data from the store and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280038: An error occurred while flushing the contents of a file store file.

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280039: The store handle {0} is not valid.

Cause: This is caused by a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280040: An invalid record was found in the store: Code={0}.

Cause: The store has been corrupted, possibly by a hardware or operating system error.

Action: For File store, Change the DirectIOMode or restore from backup if the problem persists.
Level: 1

Type: ERROR

Impact: Store

BEA-280041: A record was found in the store with an invalid version of {0}.

Cause: The store may have been used with an incompatible version of WebLogic Server.

Action: Restore from backup.
Level: 1

Type: ERROR

Impact: Store

BEA-280042: The file store primary or cache file "{0}" cannot be opened because it is actually a directory.

Cause: A directory was accidentially created in the file store's own main or cache directory, or the specified path is incorrect.

Action: Check that the file store path is correct.
Level: 1

Type: ERROR

Impact: Store

BEA-280044: The file store directory "{0}" does not exist.

Cause: The directory has not yet been created, or its filesystem is not available.

Action: Check that the directory path has been correctly specified, and create the directory if necessary.
Level: 1

Type: ERROR

Impact: Store

BEA-280045: The file store primary or cache directory "{0}" is not a directory.

Cause: The directory has not yet been created, or its filesystem is not available.

Action: Check that the directory path has been correctly specified, remove any file or directory that already exists in its place, and create the directory if necessary.
Level: 1

Type: ERROR

Impact: Store

BEA-280046: The directory "{0}" is not both readable and writeable.

Cause: The file permissions are incorrect, or the server is running under the wrong user ID.

Action: Fix the file permissions or run the server under the correct user ID.
Level: 1

Type: ERROR

Impact: Store

BEA-280051: The store was not able to create a new record.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Store

BEA-280052: The store was not able to read a record.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Store

BEA-280055: Invalid name for store write policy: "{0}".

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Store

BEA-280056: A store error occurred: {0}

Cause: See the description of the underlying exception.

Action: See the description of the underlying exception
Level: 1

Type: ERROR

Impact: Store

BEA-280057: The store named "{0}" is already open.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280059: "{0}" is not a valid store connection name.

Cause: This is a programming error.

Action: Fix the code and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280060: The store "{0}" encountered a fatal error, and it must be shut down: {1}

Cause: There was a serious I/O error, either with file I/O, replicated store IO or the JDBC connection to the database.

Action: Restart the server.
Level: 1

Type: INTERNAL_ERROR

Impact: Store

BEA-280061: The store "{0}" could not be deployed: {1}

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280062: The store "{0}" could not be shut down: {1}

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: WARNING

Impact: Store

BEA-280063: The "{0}" field value "{1}" in table reference "{2}" (format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.

Cause: This is a configuration error.

Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1

Type: ERROR

Impact: Store

BEA-280064: {0} (server="{1}" store="{2}" table="{3}")

Cause: See the exception text and the linked exception (if one exists).

Action: See the exception text and the linked exception (if one exists).
Level: 1

Type: ERROR

Impact: Store

BEA-280065: {0} (server="{1}" store="{2}" table="{3}"):(Linked Cause, "{4}")

Cause: See the exception text and the linked exception text.

Action: See the exception text and the linked exception text.
Level: 1

Type: ERROR

Impact: Store

BEA-280066: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).

Cause: This is a configuration error.

Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, make sure there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references.
Level: 1

Type: ERROR

Impact: Store

BEA-280067: JDBC store "{0}" did not find a database table at "{1}", so it created one using the commands in file "{2}".

Cause: The JDBC store did not find its backing table, so it created one.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280068: JDBC store failed to initialize. It did not find its database table and failed trying to create a new empty table using the commands in file "{0}".

Cause: See the linked exception text and the linked exception stack trace.

Action: See the linked exception text and the linked exception stack trace.
Level: 1

Type: ERROR

Impact: Store

BEA-280069: JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because the JDBC driver is unknown and/or unsupported. To force table creation with an unknown and/or unsupported driver, see the JDBC store "CreateTableDDLFile" configuration attribute. Driver information: database product name = "{0}", driver name = "{1}".

Cause: See the exception text and the exception stack trace.

Action: See the text exception text and the exception stack trace.
Level: 1

Type: ERROR

Impact: Store

BEA-280070: JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because it could not locate the configured DDL file "{0}".

Cause: The configured file is located in the server file path.

Action: For supported databases, consider the option of not configuring a custom DDL file. There is usually no need to configure a custom DDL file unless custom database-specific tuning commands have been added to the file. If a DDL file must be configured (perhaps because it is for an unsupported database), ensure that the configured file is located either in the server file path or server class path.
Level: 1

Type: ERROR

Impact: Store

BEA-280071: JDBC store "{0}" opened table "{1}" and loaded {2,choice,0#0 records|1#1 record|2#{0} records}. For additional JDBC store information, use the diagnostics framework while the JDBC store is open.

Cause: A JDBC store booted.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280072: JDBC store "{0}" failed to open table "{1}".

Cause: See the linked exception.

Action: See the linked exception.
Level: 1

Type: ERROR

Impact: Store

BEA-280073: The file store "{0}" could not be opened because it contained a file with an invalid version {1}. A file of version {2} was expected.

Cause: The file store has not been properly upgraded from a previous version of WebLogic Server, or the file has been corrupted on the disk.

Action: Ensure that the file store was upgraded using the weblogic.Upgrade tool.
Level: 1

Type: ERROR

Impact: Store

BEA-280074: The store "{0}" encountered an unresolvable failure while processing transaction "{1}". Shut down and restart to resolve this transaction. {2}

Cause: There was a serious I/O error, either with file I/O, replicated I/O or the JDBC connection to the database, or an unexpected exception occurred while processing a transaction.

Action: Restart the server.
Level: 1

Type: ERROR

Impact: Store

BEA-280075: JDBC store "{0}" failed to retain ownership of database table "{1}", either due to database access problems or due to concurrent accessors of the table. See the linked exception for more information.

Cause: Some other WebLogic server process or JDBC store has taken over ownership of the database table, or some database access error prevented this JDBC store from renewing ownership of the database table.

Action: The error message has information to identify potential owners in conflict.
Level: 1

Type: ERROR

Impact: Store

BEA-280076: Database table "{1}" for store "{0}" is currently owned by "{2}". Trying to wait for ownership.

Cause: Some other WebLogic Server process or JDBC store has ownership of the database table.

Action: The warning message has information to identify the current owner of the database table. If the current owner does not yield ownership within some time, this server will not be able to open the JDBC store and will log an error.
Level: 1

Type: WARNING

Impact: Store

BEA-280077: JDBC store "{0}" in this server is not the owner of database table "{1}". Unexpected current owner is "{2}", expected current owner is "{3}".

Cause: Some other WebLogic Server process or JDBC store has ownership of the database table.

Action: The error message has information to identify and resolve the owners in conflict.
Level: 1

Type: ERROR

Impact: Store

BEA-280078: The handle that was passed was created from a different store connection.

Cause: This is a programming error.

Action: Ensure that the correct connection was used.
Level: 1

Type: ERROR

Impact: Store

BEA-280079: An instance of the mSA PersistentStore

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280080: Number of create requests issued by this store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280081: Number of read requests issued by this store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280082: Number of update requests issued by this store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280083: Number of delete requests issued by this store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280084: Number of objects contained in the store.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280085: Number of times the store flushed its data to durable storage.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280086: An instance of an mSA PersistentStoreConnection

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280087: Number of create requests issued by this store connection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280088: Number of read requests issued by this store connection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280089: Number of update requests issued by this store connection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280090: Number of delete requests issued by this store connection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280091: Number of objects contained in the store connection.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280092: Specified value "{1}" of the property "{0}" is not a valid Integer system property. Using default value "{2}" instead.

Cause: The specified value is not valid.

Action: Check the Javadoc for the valid formats of Integer system properties: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Integer.html#decode(java.lang.String).
Level: 1

Type: WARNING

Impact: Store

BEA-280093: Block size "{1}" specified by the property {0} is outside the valid range from {2} to {3}. Using default value "{2}" instead.

Cause: The specified block size is outside the valid range.

Action: Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280094: The size "{1}" specified by the property {0} is not power of 2. Rounding down to "{2}" instead.

Cause: The specified size is not a power of 2.

Action: Refer to the Tuning WebLogic JMS chapter of the Tuning Performance of Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280095: Opening existing file store "{1}". The block size value specified by the property {0} is ignored because the block size of preexisting files cannot change.

Cause: The block size value cannot be changed.

Action: Refer to the Tuning WebLogic JMS chapter of the Tuning Performance of Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280096: Opening existing store "{2}". The direct IO mode "{1}" specified by the property "{0}" is invalid and will be ignored. Using the default value "{3}"

Cause:

Action: Use a valid direct I/O mode. The valid values are: "read-buffered", "single-handle-unbuffered", and "single-handle-buffered".
Level: 1

Type: WARNING

Impact: Store

BEA-280097: A file store failed to open file "{0}" in the Direct-Write read-buffered/write-unbuffered mode and is instead opening the file in a purely unbuffered mode. When there are high request loads, this may reduce file store performance. However, the store is still operating in a transactionally safe synchronous mode.

Cause:

Action: To fix this problem, configure a different synchronous write policy, or if using the Direct-Write policy, force the store into read-write-buffered mode using the AvoidDirectIO command line property documented in the Tuning JMS Store-and-forward chapter of the Tuning Performance of WebLogic Server guide.
Level: 1

Type: WARNING

Impact: Store

BEA-280101: The persistent file store "{0}" is forced to use buffered I/O because the Operating System or hardware environment does not support unbuffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the final write policy.

Cause: See the message body.

Action: Refer to the documentation for information about the store synchronous write policy configuration.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280102: The perisistent file store "{0}" must reinitialize its cache: recovery may take longer than usual. The signature in the cache file "{2}" for the persistent store file "{1}" could not be verified, or the cache file is missing. Ignore this Warning if this is the first time the store has ever booted. Possible causes include: first boot of store (potentially after using a write policy different from Direct-Write-With-Cache), store migration, unclean shutdown, off-line store compression, and manual removal of cache files.

Cause: The cache file is missing, or the signature stored in the cache file does not match the signature of the primary file.

Action: Make sure that the configuration is correct, do not delete cache files, and ensure a clean shutdown.
Level: 1

Type: WARNING

Impact: Store

BEA-280103: The persistent file store "{0}" will cache in {1}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280104: The persistent file store "{0}" will use buffered writes instead of direct IO because the configured block size "{2}" is not a multiple of the environment's direct IO alignment "{1}". When there are high request loads, this may reduce file store performance. The store is still operating in a transactionally safe synchronous mode.

Cause: Direct I/O requires the block size to be a multiple of directIO granularity.

Action: Reconfigure the store with a block size that is a multiple of the direct I/O alignment for your environment. If the store is not empty and contains useful data, use the store administration compact utility to change block size, otherwise make sure that all storage areas are removed before starting WebLogic Server again.
Level: 1

Type: WARNING

Impact: Store

BEA-280105: The persistent file store "{0}" cannot open file {1}.

Cause: An IOException occurred.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Store

BEA-280106: The persistent file store "{0}" cannot memory-map the locked file "{1}" and has to downgrade to explicit buffered IO. For example, in some NFS environments memory-mapping and locking are not compatible. Consider configuring a local cache directory.

Cause: See the message body.

Action: Consult your storage vendor and operating system documentation.
Level: 1

Type: ERROR

Impact: Store

BEA-280107: The store record {0}, connection "{1}", in the store named "{2}" does not exist because it has been deleted.

Cause: This was caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280108: The store record {0}, connection "{1}" already exists in the store named "{2}".

Cause: This was caused by a programming error.

Action: Ensure that the correct record ID was specified.
Level: 1

Type: ERROR

Impact: Store

BEA-280109: The JVM was unable to load the native wlfileio library for the store "{0}". File and paging stores will continue to function correctly. Specifically, file stores that are configured with a transactionally safe synchronous write policy will continue to operate safely and transactionally but may open with a different write-policy. Other store types may not be able to open.

Cause: See the message body.

Action: See file store open log messages for the requested and final file store write policies. See the documentation for file store synchronous write policy configuration.
Level: 1

Type: WARNING

Impact: Store

BEA-280110: The "{1}" attribute of Store "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280111: The "{1}" attribute of Store "{0}" has been changed from "{2}" to "{3}".

Cause: This is due to a configuration change.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280112: [StoreBootOnError] "{0}" Ignoring AssertionError on bootHandle: record type: {1}, handle:{2}, row: {3}

Cause: There is some corruption of the JDBC store.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Store

BEA-280113: The JDBC store "{0}" is initially pointing to RAC instance "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280114: The JDBC store "{0}" is configured with worker count as "{1}" but only started "{2}" workers as it is not able to acquire enough JDBC connections for the configured worker count.

Cause: The JDBC store was not able to acquire enough JDBC connections for the configured worker count.

Action: Modify the data source configuration.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280115: Replicated store "{0}": the daemon is approaching its shared memory limit and the store itself has used up to "{1}%" of its shared memory.

Cause:

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280116: Replicated store "{0}": the daemon is approaching its shared memory limit and the store itself has used up to "{1}%" of its shared memory. It will reject new JMS persistent messages.

Cause:

Action: Check if there are things that need to be cleaned up, for example, abandoned durable subscriptions. Consider restarting the daemon with a bigger limit.
Level: 1

Type: WARNING

Impact: Store

BEA-280117: Replicated store "{0}": the daemon has used up to "{1}%" of its shared memory limit.

Cause:

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280118: Replicated store "{0}": the daemon has used up to "{1}%" of its shared memory limit. It may take actions, including rejecting new JMS persistent messages or failing on creating any new stores or opening any recovered stores.

Cause:

Action: Check whether there are things that need to be cleaned up, for example, abandoned durable subscriptions. Consider restarting the daemon with a bigger limit.
Level: 1

Type: WARNING

Impact: Store

BEA-280119: Replicated store "{0}": the daemon used up to "{1}%" of its shared memory limit. It will fail when creating new stores or opening any recovered store.

Cause: The daemon has reached its shared memory limit.

Action: Check whether there are things that need to be cleaned up, for example, abandoned durable subscriptions. Consider restarting the daemon with a bigger limit.
Level: 1

Type: ERROR

Impact: Store

BEA-280120: Opening the Replicated store "{0}(Region Name={1})" for recovery: directory={2} driver="{3}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280121: The Replicated store "{0}(Region Name={1})" ({2}) has been opened: blockSize={3} records={4}.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Store

BEA-280122: Missing the region "{1}" from this replicated store(name="{0}").

Cause: The region has been accidentially deleted or moved, or the wrong name was specified, or the server process does not have permissions to read and write to the region.

Action: Ensure that the replicated Store name is correct and that the server process has permissions to read and write to the regions in the replicated store. If necessary, create an empty region with the same name.
Level: 1

Type: ERROR

Impact: Store

BEA-280123: The replicated store has reached the maximum number of {0} regions and no more region can be created.

Cause: There are too many records in the store.

Action: Delete data from the store and try again.
Level: 1

Type: ERROR

Impact: Store

BEA-280124: An error occurred while flushing the contents of a replicated store region.

Cause: See the detail message.

Action: See the detail message.
Level: 1

Type: ERROR

Impact: Store

BEA-280125: The replicated store "{0}(Region Name={1})" could not be opened because it contained a region with an invalid version {2}. A region of version {3} was expected.

Cause: The replicated store has not been properly upgraded from a previous version of WebLogic Server, or the region has been corrupted on the memory store.

Action: Ensure that the file store was upgraded using the weblogic.Upgrade tool.
Level: 1

Type: ERROR

Impact: Store

BEA-280126: Opening existing replicated store "{1}(Region Name={2})". The block size value specified by the property {0} is ignored because the block size of preexisting regions cannot change.

Cause:

Action: Refer to the Tuning WebLogic JMS chapter of the Tuning Performance of Oracle WebLogic Server guide for details of this setting.
Level: 1

Type: WARNING

Impact: Store

BEA-280127: The replicated store "{0}" cannot open region {1}.

Cause: An IOException occurred.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Store

BEA-281002: The SAF service has been started.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281003: The SAF service has been initialized.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281004: The SAF service has been suspended.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281005: The SAF service has been shut down.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281006: FailedMessage for store-and-forward: MessageId={0} > </FailedMessage.

Cause: A message expired before it was successfully forwarded by an SAF agent, and there is no error handling policy configured for the endpoint. The message ID was logged.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281007: SAF Agent "{0}" has been successfully prepared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281008: SAF Agent "{0}" has been successfully activated.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281009: SAF Agent "{0}" has been deactivated.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281010: SAF Agent "{0}" has been unprepared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281011: SAF Agent "{0}" failed to be prepared because of exception "{1}".

Cause: There was either an error in the configuration or an internal error.

Action: Check the agent's configuration and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281012: SAF Agent "{0}" failed to be started because of exception "{1}".

Cause: There was either an error in the configuration or an internal error.

Action: Check the agent's configuration and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281016: SAFAgent "{0}" byte threshold for the agent has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281017: SAFAgent "{0}" byte threshold for agent has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281018: SAFAgent "{0}" message threshold for the agent has been exceeded.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281019: SAFAgent "{0}" message threshold for the agent has cleared.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: INTERNAL_ERROR

Impact: SAFService

BEA-281020: SAF service has successfully connected to the remote endpoint "{0}".

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281021: SAF service failed to connect to the remote endpoint "{0}", because of {1}.

Cause: This is either due to a configuration error or a network failure, or the remote endpoint is temporarily unavailable.

Action: Check the configuration, the network connection, or the remote endpoint.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281022: SAF Agent "{0}" failed to resume because of exception "{1}".

Cause: There was either an error in the configuration or an internal error.

Action: Check the agent's configuration and contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SAFService

BEA-281025: SAFAgent "{0}" has been paused for incoming messages.

Cause: An Incoming Message Pause request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281026: SAFAgent "{0}" has been resumed for new incoming messages.

Cause: An Incoming Message Resume request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281027: SAFAgent "{0}" has been paused for forwarding

Cause: A Forwarding Pause request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281028: SAFAgent "{0}" has been resumed for forwarding.

Cause: A Forwarding Resume request was issued for the specified SAFAgent.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281029: RemoteEndpoint "{0}" has been paused for new incoming messages.

Cause: An Incoming Pause Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281030: RemoteEndpoint "{0}" has been resumed for new incoming messages.

Cause: An Incoming Resume Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281031: RemoteEndpoint "{0}" has been paused for forwarding.

Cause: A Forwarding Pause Request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-281032: RemoteEndpoint "{0}" has been resumed for forwarding.

Cause: A Forwarding Resume request was issued for the specified remote endpoint.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SAFService

BEA-282000: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.

Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {2}, then it is possible an attempt was made to access a newer version than the current version. Otherwise, a possible attempt has been made to interoperate with an unsupported older version.

Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions need to be supported, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282001: The messaging kernel {0} is beginning recovery of its persistent state.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282002: The messaging kernel {0} has recovered {1} persistent messages.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282003: The messaging kernel {0} will use up to {1} bytes of memory before paging begins.

Cause: This is normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Messaging

BEA-282004: Message redirection has failed in a non-recoverable way for the messaging kernel {0}. Restart the server in order to restart message redirection.

Cause: See the previous error messages, which should explain the cause.

Action: Restart the WebLogic Server.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282005: An error occurred while redirecting a message for the messaging kernel {0}: {1}.

Cause: See the attached detail message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282006: An error occurred while deleting an expired message for the messaging kernel {0}: {1}.

Cause: See the attached detail message.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282007: An error occurred in the transaction prepare phase of a message send operation for the messaging kernel {0}.

Cause: See the attached stack trace.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282008: A message send transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282009: A message receive transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282010: A sequence number update transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.

Cause: A server was shut down or a destination was removed while a transaction was in progress.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Messaging

BEA-282011: There was an error making a message visible after a delivery delay: {0}.

Cause: Most likely, a transient I/O error occurred.

Action: Consider restarting the server if the error persists. The message will not be lost.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282012: There was a failure while performing paging I/O.

Cause: Either a transient I/O error occurred, or the server did not have enough memory to complete the paging I/O request.

Action: Consider restarting the server if the error persists.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282013: Skipping unexpected null message encountered on store boot, {0}.

Cause: Message data corruption has occurred. The corrupted message will be skipped to allow data recovery on other non-corrupted messages.

Action: Report this issue to My Oracle Support.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282014: [StoreBootOnError] "{0}" Ignoring 2PC record for sequence={1}, queue={2}, type={3}, id={4}, xid={5}; message reference element cannot be found.

Cause: Potential message data corruption has occurred. A 2PC record was found in the store without an associated message reference element. The 2PC record will be ignored.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Messaging

BEA-282015: "{0}" An error occurred while writing a message to store: info={1}; null message body detected.

Cause: An error was detected while attempting to write a message to the persistent store.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Messaging

BEA-283002: Path Service has been started on server {0} with jndiName {1} with store {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: PathService

BEA-290001: Error occurred in the deployment service servlet. It received an unacceptable request of type "{0}" with content type "{1}".

Cause: An invalid request was made to the deployment service servlet.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290003: Deployment service servlet encountered an exception while handling request of type "{0}". Exception is: "{1}".

Cause: Error occurred while handling the deployment servlet request.

Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290006: Deployment service servlet received a request of type "{0}" with no application name.

Cause: An invalid deployment service servlet request was made.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290007: Deployment service servlet unable to find upload directory while handling request of type "{0}" for application "{1}".

Cause: The servlet was unable to find the upload directory.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290008: Deployment service servlet encountered an error while extracting uploaded file to directory "{0}". Exception is: "{1}".

Cause: An exception occurred while extracting the uploaded file.

Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290009: Deployment service servlet failed to get initialized due to unavailable security service.

Cause: The WebLogic Server security service is not present in the installation files.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290010: Deployment service servlet failed to get initialized due to privileged action violation. Exception is: "{0}".

Cause: An exception occurred while initializing the deployment service servlet.

Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290011: Unauthorized request of type "{0}" for user "{1}"

Cause: The user is unauthorized for downloading files.

Action: Check the user and try again with an authorized user.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290012: Deployment service servlet received jspRefresh request with no upload file name.

Cause: The request parameter upload file name was null.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290013: No user name or password provided for the request.

Cause: The user name or password in the request were null.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290014: Invalid user name or password.

Cause: The request contained an invalid user name or password.

Action: Try again with a valid user name and password.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290015: Domain wide secret mismatch

Cause: Thee was an invalid signature between the Administration Server and Managed Servers.

Action: This is an internal error. Verify that the Administration Server and Managed Servers have the same SerializedSystemIni.dat file.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290016: Access not allowed for server "{0}" on boot.

Cause: The user does not have boot permission for the specified server.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290020: Exceptions encountered while invoking application lifecycle listeners

Cause: A registered lifecycle listener detected an error and generated an exception.

Action: Refer to the exception message from the lifecycle listener and determine if the error can be corrected.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290021: {0} does not exist.

Cause: The file does not exist on the Administration Server.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290022: This request needs to be initiated through a start control.

Cause: This is an internal protocol error.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290024: Deployment type {0} has already been registered with the DeploymentService.

Cause: More than one deployment handler was registered for this deployment type.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290025: Cannot call "start()" when DeploymentRequest has already been started.

Cause: The start method was called more than once.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290026: Request "{0}" is in "{1}" state - request has already been cancelled.

Cause: More than one cancel request was received.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290027: Request "{0}" is in "{1}" state - it is too late to attempt cancelling it.

Cause: A cancel request was received while the request was being committed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290028: Deployment "{0}" has been cancelled.

Cause: The request was already cancelled.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290029: Deployment "{0}" timed out on Administration Server.

Cause: The request has timed out.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290030: No data handler registered for type "{0}".

Cause: A handler was not registered for the specified type.

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290031: No tasks associated with this deployment request that can be cancelled.

Cause: Tasks have already completed.

Action: No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290032: Data Transfer Handler exists for handler type: "{0}".

Cause: The handler type is already registered

Action: This is an internal error. No action is required.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290036: Deployment for request id "{0}" is deferred since target "{1}" is disconnected.

Cause: Target server "{1}" is disconnected.

Action: No action is required. When the server reconnects, the deployment will be performed.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290039: Unrecognized callback

Cause: The callback was not a supported type.

Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290040: The cancel call cannot be completed at this point because the deployment request "{0}" has already been partially committed.

Cause: A cancel was requested on a committed deployment task.

Action: Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290041: Commit failed message received for id: "{0}" that has no request. It may be completed or cancelled. Sending commit succeeded message anyway.

Cause: No corresponding request was found for the commit failure message.

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290042: Received a commit message call without a corresponding request. It may have been completed or cancelled. Sending commit failed message.

Cause: No corresponding request was found for the commit message.

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290043: Cancel failure encountered when attempting to cancel "{0}" due to optimistic concurrency violation.

Cause: A failure occurred during the cancel of the request.

Action: Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290044: {0} delivery

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290045: prepare

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290046: commit

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290047: cancel

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290048: Request with id "{0}" timed out.

Cause: The request timed out.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290049: Deploy failed for id "{0}" since no targets are reachable.

Cause: No targets were reachable.

Action: Ensure targeted servers are alive and available from the Administration Server.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290050: Failed to deliver commit message to the following targets "{0}".

Cause: An exception occurred while committing the deployment request.

Action: Ensure that targeted servers are alive and available from the Administration Server. Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290051: The commit message for the deployment "{0}" could not be completed because the deployment timed out.

Cause: The deployment timed out.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290052: {0} timeout

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290053: Request with id "{0}" timed out on the Administration Server.

Cause: The request timed out on the Administration Server.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290054: Deployment request "{0}" was explicitely cancelled.

Cause: Not applicable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290055: Deployment request "{0}" timed out on the Administration Server during "{1}".

Cause: The deployment request timed out.

Action: Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290056: indeterminate

Cause: Not applicable

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290057: Invalid DeploymentRequest: the object returned by the DeploymentService has been modified in an incompatible way.

Cause: The deployment request is not of the expected type.

Action: Check for a preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290058: There is no request corresponding to request ID "{0}" currently being processed. The request will be cancelled if it is received in the future.

Cause: The specified request ID is not active.

Action: Check that your task ID is the task that you would like to cancel.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290059: Operation "{0}" is not one of the supported types when creating a Change Descriptor.

Cause: An invalid change descriptor type was specified.

Action: This is an internal error. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290060: Duplicate registration for "{0}".

Cause: Two different deployment instances were registered for the same type.

Action: This is an internal error. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290061: UnrecognizedTypes: "{0}", "{1}"

Cause: A deployment type is invalid.

Action: This is an internal error. If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290062: The server configuration is out of date with the domain configuration and an attempt to synchronize with the Administration Server failed. This server needs to be restarted to enable it to synchronize with the domain configuration.

Cause: An attempt to synchronize with the Administration Server failed.

Action: Restart the server and if that does not resolve the problem, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1

Type: ERROR

Impact: DeploymentService

BEA-290063: Commit for request "{0}" will not proceed further since its requires restart flag is set.

Cause: The changes in the deployment request require a restart.

Action: Restart either the server or the system resource that is part of the request.
Level: 1

Type: NOTIFICATION

Impact: DeploymentService

BEA-290064: Deployment service servlet encountered an exception while handling the deployment service message for request id "{0}" from server "{1}". Exception is: "{2}".

Cause: Error occurred while handling the deployment service message request.

Action: This is an internal error. Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290065: Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "{0}" from server "{1}". Exception is: "{2}".

Cause: Error occurred while handling the deployment datatransfer request.

Action: This is an internal error. Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290066: Error occurred while downloading files from Administration Server for deployment request "{0}". Underlying error is: "{1}"

Cause: The connection used for the file download received an error.

Action: Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290067: Deployment request ''{0}'' was cancelled because servers: ''{1}'' were unreachable and the domain has cluster-constraints-enabled is set to true. To deploy to this cluster, either start the unreachable servers or remove the unreachable servers from the cluster, then reattempt the deployment. If this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the Administration Server. This allows you to deploy the application only to those servers that can be reached.

Cause: Not all the servers in the cluster are running and cluster-constraints-enabled is set to true.

Action: Start all the servers in the cluster and try deployment again, or if this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the Administration Server.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290068: A deployment service request has been received by this Managed Server that was intended for the Administration Server. The source of the request is "{0}".

Cause: The source Managed Server was started with a URL for the Administration Server that incorrectly identified this server.

Action: Start the source Managed Server with the correct URL for the Administration Server.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290069: Commit failed message received for id: "{0}", but exception details cannot be transported. Please look at target server log file for more details.

Cause: The send of the commit message failed.

Action: Check the exception details in the server log and determine if the failure can be corrected.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290070: Deployment service servlet encountered an exception while parsing the multipart/form-data request:"{0}". Exception is: "{1}".

Cause: The request is not an RFC 1867-compliant multipart/form-data request.

Action: This is an internal error. No action is required.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290071: Deployment service servlet failed when parsing the request or uploading the file.

Cause: The request is not an RFC 1867-compliant multipart/form-data stream.

Action: The request should comply with RFC 1867. Verify that the Administration Server and Managed Servers are running versions that interoperate.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290073: Deployment service servlet received a request of type "{0}" with an invalid application name: "{1}".

Cause: An invalid deployment service servlet request was made.

Action: Correct the application name and retry the request.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-290074: Deployment service servlet received file download request for file "{0}". The file may exist, but download of this file is not allowed.

Cause: The file to download is a security file or is outside of the domain root directory.

Action: Enter a valid file name for download.
Level: 1

Type: WARNING

Impact: DeploymentService

BEA-300037: The NodeManager at host {0} and port {1} seems to be down. Start the NodeManager and rerun the command.

Cause: The NodeManager is not running.

Action: Start the NodeManager and rerun the command.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300040: An I/O error occurred while writing a NodeManager status change message.

Cause: Possible causes are that the standard output stream has been closed or the NodeManager stopped monitoring.

Action: If this server requires monitoring, restart the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300043: NodeManager native library not found - server process ID not saved.

Cause: The NodeManager native library is not in the library search path or is unavailable on this platform.

Action: Ensure that the NodeManager native library is available and in the library search path.
Level: 1

Type: WARNING

Impact: NodeManager

BEA-300044: An I/O error occurred while writing the server PID file: "{0}".

Cause: The server PID file might be write protected.

Action: Ensure that the server PID file is not write protected. In addition, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300048: Unable to start the server {0} : {1}

Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration.

Action: Ensure that you can access the remote NodeManager. This may require setting up SSH permissions for the SSH-based NodeManager. In addition, ensure that the default PATH settings for the remote NodeManager are correct. See the NodeManager documentation for more information.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300049: An I/O error occurred while writing the server URL file: "{0}".

Cause: The server URL file might be write-protected.

Action: Ensure that the server URL file is not write-protected. In addition, check to see if the parent directory exists (it should have been created by the NodeManager server before starting the server).
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300051: An I/O error occurred while updating the startup properties for "{0}". This probably occurred because the NodeManager is unreachable. This could mean that the servers boot.properties or startup.properties file is out of date, and the next time NodeManager attempts to automatically restart the server on a failure, it will use out of date properties. To resolve this issue, either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.

Cause: An I/O error occurred while updating the startup properties for "{0}". This probably occured because the NodeManager is unreachable.

Action: Either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300053: A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP. Configure an appropriate floating listen address for the server.

Cause: A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP.

Action: Configure an appropriate floating listen address for the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300054: Could not find appropriate IP for ListenAddress "{0}" specified for a migratable server. Reason: "{1}". The NodeManager may not be able to bind the specified address and the server may not start without the available address. Configure an appropriate floating listen address for the server.

Cause: No appropriate IP was found for a migratable server's listen address. The NodeManager may not be able to bind the specified address and the server may not start without the available address.

Action: Configure an appropriate floating listen address for the server.
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300055: The NodeManagerMonitor add requires a non-null MachineMBean to monitor the active status of a NodeManager.

Cause: TBD

Action: TBD
Level: 1

Type: ERROR

Impact: NodeManager

BEA-300056: Could not execute the native output file rotation logic due to "{0}".

Cause: Could not execute the native output file rotation logic due to "{0}".

Action: Could not execute the native output file rotation logic due to "{0}".
Level: 1

Type: ERROR

Impact: NodeManager

BEA-310001: Subsystem {0} has failed. Setting server state to FAILED.

Cause: One of the critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: ERROR

Impact: Health

BEA-310002: {0}% of the total memory in the server is free.

Cause: The percentage of free memory in the server has changed.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Health

BEA-310003: Free memory in the server is {0} bytes. There is danger of receiving an OutOfMemoryError.

Cause: Free memory in the server is very low.

Action: Analyze heap memory usage for possible memory leak. Contact Oracle Support if the leak is in WebLogic server. If no memory leak is found, consider restarting server with a larger maximum heap size.
Level: 1

Type: WARNING

Impact: Health

BEA-310006: Critical subsystem {0} has failed. Setting server state to FAILED. Reason: {1}

Cause: One of the critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: INTERNAL_ERROR

Impact: Health

BEA-310007: Subsystem {0} has failed because of: {1} However, notification did not occur because {0} was not registered with the HealthMonitorService.

Cause: One of the subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure. MigratableTargets may need to be manually moved, since the automatic migration subsystem requires HealthMonitor notification to work properly.
Level: 1

Type: WARNING

Impact: Health

BEA-310008: Non-critical subsystem {0} has failed. Reason: {1}

Cause: One of the non-critical subsystems of the server has failed.

Action: Check the server log to determine the cause of the subsystem failure.
Level: 1

Type: INTERNAL_ERROR

Impact: Health

BEA-320000: The Diagnostics subsystem is initializing on Server {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320001: The ServerDebug service initialized successfully.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320002: The Diagnostics subsystem is stopping on Server {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320004: The following unexpected exception was thrown: {0}

Cause: An exception was thrown unexpectedly.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320005: Diagnostic monitor of unknown type {1} used in instrumentation scope {0}.

Cause: The Diagnostic Monitor library is probably out of date.

Action: Update the Diagnostic Monitor library.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320008: Error occurred while collecting diagnostic metrics:

Cause: An error occurred while constructing a Harvester instance.

Action: Ensure that all harvester configuration parameters are set appropriately.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320009: The elapsed time of the last snapshot of diagnostic metrics exceeded the configured sample period by the following number of milliseconds: {0}.

Cause: Harvested MBeans and/or DataSources are taking too long to return sampled attribute values.

Action: Increase the sample period window.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320010: An error occurred while generating a diagnostic image: {0}

Cause: Permissions were abruptly changed on the zip/directory. The file system does not have sufficient disk space to continue writing the image.

Action: Allocate sufficient disk space and provide the proper permissions to create the image zip file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320011: The following diagnostic image destination directory could not be created: {0}

Cause: You have not given write permissions to the absolute path for the default directory, or you have not allocated sufficient disk space for the directory to be created.

Action: You must give write permissions to the absolute path for the default directory if no configured destination directory is specified. You must also allocate sufficient disk space for the default directory to be created if no destination directory is specified.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320012: The following destination directory for diagnostic images could not be read or written to: {0}.

Cause: The directory was not created or directory read and write permissions were not given to the directory.

Action: Create the destination directory with the appropriate read and write permissions.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320013: Diagnostic image capture was attempted during a lockout period.

Cause: The ImageManager has locked image captures for a specified number of minutes.

Action: The lockout period must expire before a new image capture request is accepted.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320014: Lockout of {0} above allowed maximum lockout minutes for image captures.

Cause: The specified a number of minutes exceeds the maximum allowed lockout minutes.

Action: Specify a lockout period between the minimum and maximum.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320015: Lockout of {0} below allowed minimum lockout minutes for image captures.

Cause: The specified a number of minutes falls below the minimum allowed lockout minutes.

Action: Specify a lockout period between the minimum and maximum.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320016: Creating diagnostic image in {0} with a lockout minute period of {1}.

Cause: A FirstFailure has occurred, a diagnostic image notification handler was configured, or a capture image method was explicitly invoked on ImageManager.

Action: No action is required. The diagnostic image capture request will be scheduled and executed.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320018: Instrumentation engine configuration {0} could not be parsed due to: {1}

Cause: The instrumentation engine configuration is possibly malformed.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320019: Code generator class {1} for standard monitor {0} could not be found.

Cause: The standard monitor code generator was not on the class path.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320020: Code generator {1} for standard monitor {0} could not be instantiated.

Cause: The standard monitor code generator is missing the default constructor.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320021: The code generator {1} could not be accessed for standard monitor {0}.

Cause: The standard monitor code generator implementation has problems.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320022: An error was encountered while creating SerialVersionUID for class {0}.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320023: File {0} does not contain a valid Java class

Cause: The file does not contain a valid Java class.

Action: Make sure that the file being instrumented is a valid Java class file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320024: Class in file {0} could not be instrumented.

Cause: This can happen when the input file or output file cannot be read from or written to.

Action: Check the file permissions and disk space.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320025: Input file {0} for instrumentation engine cannot be found.

Cause: The input class file does not exist.

Action: Provide the correct path to the input class file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320026: Monitor {0} could not be found in instrumentation engine configuration.

Cause: The monitor name may be misspelled.

Action: Specify the correct monitor name on the command line.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320030: Delegating monitor {1} in scope {0} allows using action of type {2}, which does not exist.

Cause: A delegating monitor was not properly configured in the instrumentation engine configuration.

Action: Contact My Oracle support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320031: An attempt to add a monitor of type {1} to instrumentation scope {0} failed because the monitor already exists in the scope.

Cause: Instrumentation configuration was incorrect.

Action: Remove multiple monitor entries with same types from the instrumentation scope configuration.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320032: Attempt to add duplicate action {2} to monitor {1} in scope {0} failed.

Cause: Instrumentation scope configuration is incorrect. It has duplicate actions attached to the same monitor.

Action: Remove duplicate actions attached to the same monitor.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320033: Attempt to attach incompatible action of type {2} to a delegating monitor of type {1} in scope {0}.

Cause: Instrumentation configuration is incorect.

Action: Make sure that only compatible actions are used with delegating monitors.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320034: Instrumentation engine configuration {0} could not be parsed. {1}

Cause: The instrumentation configuration is malformed.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320035: Instrumentation configuration {0} could not be read.

Cause: The instrumentation configuration is missing or invalid.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320036: Instrumented method {1}{2} in class {0} exceeds size limit. Original method is preserved.

Cause: The original method is too large to begin with. The class to which it belongs is probably generated by a generator program.

Action: If possible, split the method into multiple methods. Exclude the class from instrumentation to speed up the instrumentation process.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320037: Class bytes for {0} do not conform to class format.

Cause: The class file is corrupt.

Action: Make sure that the class file is not corrupt.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320038: Could not instrument class {0}

Cause: This is a general instrumentation failure.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320039: Invalid class inclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.

Cause: Inclusion patterns are malformed.

Action: Specify inclusion patterns in the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320040: Invalid class exclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.

Cause: One or more exclusion patterns are malformed.

Action: Specify exclusion patterns in the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320041: Invalid lockout minutes {0} specified in image notification. Image capture was not performed.

Cause: The value is invalid.

Action: Recreate the notification with a valid lockout minutes value.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320042: Invalid diagnostic image location {0} specified in notification, exception message is {1}. Image capture was not performed.

Cause: The value is not a valid directory or file name.

Action: Recreate the notification with a valid image location. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320043: Image notification was not performed because the image capture was attempted before the lockout time expired. The exception message is {0}

Cause: An image capture was attempted before the lockout period expired.

Action: Recreate the image notification with a smaller value for lockout minutes. Optionally, use the watch alarm feature to ensure that the notification does not occur again before the lockout period has expired.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320044: Error occurred while performing a watch notification:

Cause: An error occurred while performing the operations required for the notification.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320047: Mail notification has not been sent due to an error that occurred while creating or sending a mail message:

Cause: An error occurred while performing the mail operations required for the notification.

Action: Verify the MailSession properties and email destination. Take appropriate action based on the Messaging exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320048: JMS notification message has not been sent due to an error that occurred while creating a JMS map message:

Cause: An error occurred while performing the JMS operation.

Action: Verify the JMS queue and connection factory configuration settings in the JMS notification. Take appropriate action based on the JMS exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320049: An exception occurred sending JMS notification message. Reinitializing JMS objects and retrying.

Cause: An error occurred while sending the JMS message.

Action: Look for additional error messages in the log from the reinitialization or resend of the message.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320052: An error occurred while initializing a SMTP notification:

Cause: The mail session is incorrectly configured or not available.

Action: Ensure that the mail session JNDI name is correct. Ensure that the mail session MBean properties are valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320053: The SNMP Agent is not configured. The trap for the SNMP Watch notification cannot be sent.

Cause: The SNMP Agent is not enabled.

Action: Enable the SNMP Agent using the console.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320054: An error occurred while sending an SNMP notification:

Cause: An exception occurred in the SNMP Agent when sending the SNMP trap to the configured trap destinations.

Action: Ensure that the trap destinations are configured correctly. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320055: Could not read or create index on log file {0}.

Cause: The drive may be full or the directory is not writable.

Action: Check whether the drive is full or the directory is not writable.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320056: Log index file {0} has an invalid magic number.

Cause: The index file is corrupt or invalid.

Action: Delete the corrupt index file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320057: Log index file {0} contents are inconsistent with its header.

Cause: The index file is corrupt or truncated.

Action: Delete the index file.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320058: Could not parse log record: {0}

Cause: The log record is malformed.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320063: An attempt to add watch {0} failed because the watch has already been defined.

Cause: Two different watch definitions have the same name.

Action: Remove one of the watch entries that has the same name.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320064: Watch {0} could not be created due to the following unexpected exception: {1}

Cause: An exception occurred unexpectedly.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320066: An attempt to add notification {0} failed because the notification has already been defined.

Cause: Two different notification definitions have the same name.

Action: Remove one of the notification entries with the same name.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320068: Watch "{0}" in module "{1}" with severity "{2}" on server "{3}" has triggered at {4}. Notification details: {5}

Cause: A configured watch has evaluated to true and has triggered.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320069: Watch {0} contains an invalid notification {1} that is not defined.

Cause: The notification does not exist.

Action: Define the notification or remove the notification from the watch.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320070: Error occurred while performing notification {1} for watch {0}. Notification may not have completed.

Cause: An exception occurred while performing the notification.

Action: Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320071: Error occurred while creating watch notification {0}. Notifications may not have completed for this watch.

Cause: An exception occurred while creating the watch notification.

Action: Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320073: Error while locating a record for timestamp {0} in the archive

Cause: There is a misconfigured or missing data archive for harvested data.

Action: Check that the harvested data archive exists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320074: Error while executing query.

Cause: Internal error

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320075: Error while reading a record from the archive

Cause: The harvested data archive may be corrupt due to internal error.

Action: Reconfigure the harvested data archive. Contact My Oracle Support to report this problem.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320076: Could not initialize index information for harvester data archive.

Cause: The harvested data archive may be corrupt due to an internal error.

Action: Reconfigure the harvested data archive. Contact My Oracle Support to report this problem.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320077: Initialized the Diagnostic Accessor Service.

Cause: This is a normal operation.

Action: No action is needed.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320078: Could not initialize the Diagnostic Accessor Service Runtime during server startup.

Cause: The exception message includes the details about the cause of this problem.

Action: Take corrective action based on the exception stack trace. Contact My Oracle Support if this problem persists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320079: Watch "{0}" rule expression evaluation failed with an exception. No notifications will be performed for this watch. The exception is:

Cause: An exception occurred during rule evaluation.

Action: Verify that the rule expression is valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320080: The log type {0} is unknown. Unable to lookup the DiagnosticDataAccessRuntimeMBean instance.

Cause: This message indicates that the logical name that was specified to look up the DiagnosticDataAccessRuntimeMBean is not correct.

Action: Verify that the log type is valid. Take appropriate action based on the exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320082: Configuration for diagnostic monitor {0} in instrumentation scope {1} has errors. The exception is:

Cause: An exception occurred while reading the configuration of a diagnostic monitor in a scope.

Action: Verify that the configuration for the diagnostic monitor is valid.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320083: Custom diagnostic monitor {0} in instrumentation scope {1} has missing or invalid location attribute.

Cause: There is a missing or invalid value of the "location" attribute of a custom diagnostic monitor.

Action: Verify that the "location" attribute of the custom monitor has a correct value.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320084: The user {0} does not have authorization to view the logs.

Cause: A user with insufficient authorization attempted to access the server logs.

Action: Ensure that the right users are granted access to view the logs.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320085: The diagnostic data is accessible only through https in Production mode.

Cause: An attempt to access the diagnostic data was made over a non-secure protocol in Production mode.

Action: Ensure that the SSL is enabled in Production mode and that the servlet is accessed only over a secure protocol.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320086: The monitor type {1} in scope {0} contains unacceptable characters.

Cause: The monitor type contains unacceptable characters. It must start with an alphabetic character, followed by alphanumeric or underscore characters.

Action: Fix the assigned monitor type, which must start with an alphabetic character, optionally followed by alphanumeric or underscore characters.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320087: The cursor {0} has timed out and is being removed from the registry of open cursors.

Cause: This message is emitted when a cursor has not been invoked and is being removed to free up the associated resources.

Action: Ensure that fetch is not called anymore on the closed cursor.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320088: The cursor with name {0} does not exist.

Cause: The cursor could have timed out or been closed by the user explicitly. Otherwise, or an invalid name has been provided.

Action: Invoke the fetch method with the name of a valid cursor.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320091: Attempt to use unknown action {1} in action group {0}

Cause: This is due to an incorrect or incomplete instrumentation engine configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320092: Monitor {0} used empty or non-existent action group {1}

Cause: This is due to an incorrect or incomplete instrumentation engine configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320093: Encountered problem while reading attributes of monitor {0}. Attributes: {1}

Cause: Possibly invalid attribute names were specified with the diagnostic monitor.

Action: Specify correct attributes for the diagnostic monitor.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320094: Could not initialize server instrumentation scope.

Cause: Internal error

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320096: Cannot create custom monitor {0} in server instrumentation scope.

Cause: Custom monitors can not be defined in the server instrumentation scope.

Action: Remove the custom monitor definition from the server instrumentation scope.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320097: Monitor {0} can be created only in an application instrumentation scope. It cannot be created in server instrumentation scope.

Cause: An attempt was made to create a monitor in the server scope, but it can only be created in the application scope.

Action: Remove the monitor definition from the server instrumentation scope.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320098: Monitor {0} can be created only in server instrumentation scope. It can not be created in application instrumentation scope {1}.

Cause: An attempt was made to create a monitor in the application scope, but it can only be created in the server scope.

Action: Remove the monitor definition from the application instrumentation scope.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320100: Configuration for JDBC-based diagnostic archives is invalid or incomplete. Using file based diagnostic archive.

Cause: The configuration for JDBC-based diagnostic archives is invalid or incomplete.

Action: Fix the configuration for JDBC-based diagnostic archives.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320101: Attempt to target more than one WLDFSystemResource to server {0}.

Cause: This error indicates that an invalid targeting was specified for a WLDFSystemResource.

Action: Ensure that only one WLDFSystemResource is targeted to a server.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320102: An error occcurred when trying to access the diagnostic data while executing the query expression {0}.

Cause: The query was not specified properly.

Action: Ensure that the query is valid.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320103: An error occurred while creating the DiagnosticDataRuntimeMBean instance with the given logical name {0}.

Cause: The logical name is not a valid parameter or an error occurred while reading the diagnostic data.

Action: Ensure that the logical name is valid and take corrective action based on the reported error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320104: An error occurrred when invoking the log4j operation while activating/deactivating log watch rules.

Cause: The log4j libraries may not be in the CLASSPATH.

Action: Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320105: The watch rule expression {0} is not valid.

Cause: The watch rule expression does not conform to the correct syntax.

Action: Specify a valid watch rule expression.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320106: The watch notification configuration already contains a notification with the given name {0}.

Cause: The name for the WLDFNotification you are adding is not unique.

Action: Specify a unique name for the notification.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320111: The elapsed time since the last Harvester cycle ({0} milliseconds) is unacceptably short. Skipping this cycle in order to smooth out the responses.

Cause: The previous Harvesting process consumed a large percentage of the sample period. This can happen for 3 reasons: 1) you requested that a very large amount of data be harvested, 2) the system is consistently slow for some reason, 3) an intermittent service caused the process to slow down temporarily (for example, for garbage collection).

Action: No action is required. The Harvester will compensate by skipping cycles that occur too soon. If this happens consistently, either because you are harvesting a large amount of data, or the Harvester is running on a slow system, you can either increase the samplePeriod or increase system resources.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320113: The type {0} is no longer being harvested.

Cause: This is caused by an earlier problem. Sufficient log messages should have been issued at the point of failure to allow the problem to be debugged. Note that the type will remain deleted until the Harvester configuration is reloaded. At that time, if the problem is not yet resolved, this message may be issued again.

Action: No action is required. Typically, this type of error will cause some of the requested data to not be harvested. It is advisable to fix the issue.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320114: Initializing the Diagnostics Harvester.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320115: The Harvester is configured to be disabled.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320116: Harvester type {0} is configured to be disabled. No harvesting will occur for this type.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320117: The Harvester is being disabled because there are no valid Harvestable types configured.

Cause: This may occur because you did not provide any type specifications, or, if type specifications were provided, none of the specified types were harvestable.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320118: The Harvester timer has been initiated for an interval of {0} milliseconds.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320119: The Harvester is now in a {0} state.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320122: Unable to harvest attribute {0} on item {1} due to errors. This attribute will no longer be harvested.

Cause: The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action: No action is required. Typically, this type of error will cause some of the requested data to not be Harvested. It is advisable to fix the issue.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320123: Could not add MBean instance {0} to the harvested instance list for type {1}: {2}.

Cause: The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action: No action is required. Typically, this type of error will cause some of the requested data to not be Harvested. It is advisable to fix the issue.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320124: The harvester has discovered a new instance of harvested type {1} named {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320125: Attention: {0}

Cause: This indicates a system error, not a user error. Further investigation is required to determine the cause.

Action: The user should contact Oracle support to debug this problem. It is often possible to turn on Harvester debug to obtain additional information.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320126: Reinitializing the Diagnostics Harvester.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320127: An error occurred while generating Image Source {0} as part of the diagnostic image zip file:

Cause: An unexpected error occurred while the subsystem was collecting or persisting the diagnostic image source information.

Action: Take appropriate action based on the unexpected exception message.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320128: The WLDFResourceBean is not found for the WLDFSystemResource {0}.

Cause: This error is caused by either a deleted or corrupt WLDF descriptor file.

Action: Ensure that the descriptor file exists for the WLDFSytemResource and that it conforms to the expected schema.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320129: Instrumentation module {0} created.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320130: Instrumentation module {0} is disabled.

Cause: This instrumentation module for server or application is disabled.

Action: No action is required.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320131: Instrumentation module {0} is configured, but disabled because a WLDF system resource is not targeted to the server, or its instrumentation component is not enabled.

Cause: There is no WLDF system resource targeted to the server, or its instrumentation component is disabled.

Action: Check if there is a WLDF system resource targeted to the server and its instrumentation component is enabled.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320132: Updating classes within scope {0} since its instrumentation configuration has changed.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320133: Could not instantiate one of the known accessors during server startup.

Cause: The exception message includes the details about the cause of this problem.

Action: Take corrective action based on the exception stack trace. Contact My Oracle Support if this problem persists.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320134: An internal error occurred while creating a domain log handler: {0}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320135: JDBC-based {0} archive could not be created. Falling back on persistent store based archive.

Cause: This happens when the JDBC data source to be used with the archive is misconfigured or unavailable, or database tables are not available.

Action: Ensure that the JDBC data source is correctly configured and available, and that database tables have been created prior to use.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320136: Class {0} could not be instrumented, due to reason: "{1}".

Cause: This can happen because the class may contain constructs that are unsafe to transform, for example, custom attributes.

Action: Ensure that class does not have custom attributes or other such constructs.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320137: Invalid class inclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.

Cause: There are malformed inclusion patterns in the instrumentation monitor.

Action: Specify inclusion patterns in the instrumentation monitor using the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320138: Invalid class exclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.

Cause: There are malformed exclusion patterns in the instrumentation monitor.

Action: Specify exclusion patterns in the instrumentation monitor using the correct format.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320139: Archive {0} is not found during a data retirement operation.

Cause: Data retirement may be configured for a custom archive that does not yet exist.

Action: Ensure that the custom archive is created, or disable or remove this retirement configuration.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320140: Scheduling data retirement tasks as per configuration.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320141: An error was encountered while performing age-based data retirement on archive {0}.

Cause: An error was encountered while performing age-based data retirement on the indicated archive.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320142: An error was encountered while performing size-based data retirement on archive {0}.

Cause: An error was encountered while performing size-based data retirement on the indicated archive.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320143: Scheduled {0} data retirement tasks as per configuration.

Cause: Finished processing the data retirement configuration.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320144: {0} operation started on archive {1}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320145: {0} operation completed on archive {1}. Retired {2} records in {3} ms.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: Diagnostics

BEA-320146: Failed to register dye {0} at index {1}.

Cause: A dye with the same name or index already exists.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320147: Instrumentation system is disabled because the instrumentation library is invalid.

Cause: The instrumentation engine configuration is corrupt or a required DyeInjection monitor cannot be found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320148: Required diagnostic monitor {0} is missing from the instrumentation library.

Cause: The instrumentation engine configuration is corrupt.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320149: The DomainRuntime MBeanServer was not available for harvesting.

Cause: The DomainRuntime MBeanServer could not be loaded by the Harvester.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320151: The instance name {0} in the Watch configuration {1} is invalid.

Cause: The instance name or instance-name pattern was not a valid JMX ObjectName or instance name pattern supported by the WLDF Watch and Notifications framework.

Action: Check that the instance name is a valid ObjectName, or an instance-name pattern as specified in the WLDF Watch and Notifications framework documentation.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320152: An unexpected exception occurred while removing the set of watched metrics "{0}" from the harvester: {1}

Cause: An attempt was made to delete a set of watched metrics from the harvester that has already been removed, or one that was never activated within the harvester.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320153: Instrumentation configuration for application "{0}" has changed. However, it will take effect only after redeploying the application, since hot-swap is not enabled.

Cause: Hot-swap is not enabled.

Action: Redeploy the application, or restart the server with the diagnostic agent on the command line to enable hot-swap.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320154: Class redefinition failed after instrumentation configuration was changed for application "{0}" : {1}

Cause: An unexpected exception occurred while redefining classes after the instrumentation configuration was updated.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320155: Inconsistent instrumentation handling information was specified in the same pointcut definition for {0} : {1} : {2}.

Cause: The instrumentation configuration contains a pointcut definition that specifies conflicting information for the method.

Action: Review the pointcuts that specify the method listed in the error, and verify that there are not multiple definitions for the methods with which they conflict. For example, one indicating an argument is not-sensitive while another indicates it is.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320156: The renderer class {0} could not be loaded due to {1}, the following renderer will be used instead: {2}.

Cause: The instrumentation configuration specified a renderer class that either was not found, is not accessible, or is not a renderer.

Action: Verify that the renderer class is correctly specified in the instrumentation configuration and that it is available to the server classloader.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320157: An error occurred when registering the log4j for data gathering operations.

Cause: The log4j libraries may not be in the CLASSPATH.

Action: Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320158: An error was detected while capturing the flight recorder image.

Cause: The specified exception provides details on the error that was encountered.

Action: Review the provided exception information to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320159: An error was detected while initializing the flight recording.

Cause: The specified exception provides details on the error that was encountered.

Action: Review the provided exception information to determine the cause and action to take.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320160: The type-based renderer class {0} for type {1} could not be loaded due to {1}, that type-based renderer will not be used.

Cause: The instrumentation configuration specified a type-based renderer class that either was not found, is not accessible, or is not a renderer. It may also be that the type itself was not found or loadable.

Action: Verify that the type-based renderer class and type class are correctly specified in the instrumentation configuration and that they are available to the server classloader.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320161: A legacy Spring instrumentation API was called for an unknown method {0}.

Cause: A legacy Spring instrumentation API was called for an unknown method {0}.

Action: Instrument Spring using the tools in the current release.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320162: A legacy Spring instrumentation API was called.

Cause: A legacy Spring instrumentation API was called.

Action: Legacy Spring features should function normally, but you should instrument Spring using the tools in the current release.
Level: 1

Type: WARNING

Impact: Diagnostics

BEA-320163: Wildcarded types are not allowed to be marked as being insensitive with %.

Cause: A % character was specified for a wildcarded type, such as an asterisk or ellipses. This is not allowed, as it could lead to inadvertantly exposing a type that should be treated as being sensitive.

Action: Review the pointcuts that specify the % character to ensure that it is not supplied for any types that are wildcarded using an asterisk or ellipses.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320164: Circular class load detected during stackmap frame computation for {0}.

Cause: An attempt was made to class load the class currently being instrumented. This is not supported.

Action: Do not instrument the class that encountered the cycle.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320165: Received an unexpected error dispatching an Instrumentation event for Watch rule processing: {0}

Cause: An exception occurred while dispatching a WLDF Instrumentation event for Watch rule processing.

Action: Check the server log for details on the error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320166: Received an unexpected error dispatching an logging event for Watch rule processing: {0}

Cause: An exception occurred while dispatching a WLDF log event for Watch rule processing.

Action: Check the server log for details on the error.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320167: Expected monitors were not instrumented : {0}

Cause: Monitors which were specified as being expected to be instrumented were not instrumented.

Action: Review the instrumentation configuration and the code being instrumented, and then verify that all dependencies are available in the classpath to allow the instrumentor to walk the class hierarchy for inheritance matches.
Level: 1

Type: ERROR

Impact: Diagnostics

BEA-320300: The WLS ServerRuntime MBeanServer was not available for harvesting; custom MBean harvesting will not be available.

Cause: This could be the result of a serious error in the OA&M infrastructure. Check for other error messages in the log in that area.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320301: The WLDF Harvester could not activate the Watch and Notifications framework due to an exception: {0}

Cause: During server startup, the Watch and Notifications activation is deferred until the WLDF Harvester is fully activated. The deferred activation encountered an unexpected exception, potentially impairing the Watch and Notifications functionality.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320303: The namespace {1} for the harvested type specification {0} can not be serviced by a Managed Server instance; it is valid only when targed to an Administration Server.

Cause: A harvested type specifying the DomainRuntime namespace was targeted to a Managed Server. A Managed Server can only service the ServerRuntime namespace.

Action: Correct the namespace declaration of the harvested type, or retarget the WLDF configuration to an Administration Server in order to service this type.
Level: 1

Type: WARNING

Impact: DiagnosticsHarvester

BEA-320304: The following errors were reported during the validation of the metrics for watched values {0}: {1}

Cause: Some of the configured harvested types may have errors, resulting in the harvester being unable to process them for collection.

Action: Correct any issues with the harvested type configuration.
Level: 1

Type: WARNING

Impact: DiagnosticsHarvester

BEA-320305: The instance name {0} is not a valid ObjectName or instance name pattern.

Cause: The instance name must be a valid JMX ObjectName, or a pattern conforming to the syntax supported by the WebLogic Diagnostics Framework.

Action: Correct the instance name in the harvested type.
Level: 1

Type: ERROR

Impact: DiagnosticsHarvester

BEA-320400: The log file {0} will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.

Cause: This event happens whenever the log file is about to be rotated based on either size or time rotation criterion.

Action: On certain platforms, if some application is tailing the log, the rotation fails. Stop the application tailing and reopen the tail after the rotation is complete.
Level: 1

Type: NOTIFICATION

Impact: LoggingService

BEA-320401: The log file has been rotated to {1}. Log messages will continue to be logged in {0}.

Cause: This event happens after the log file is rotated based on either size or time rotation criterion.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: LoggingService

BEA-320450: The DebugScope name {0} is not valid.

Cause: The DebugScope with the given name is not defined in the ServerDebugMBean interface.

Action: Configure the debug scope with a valid name.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320451: An error occurred while applying the DebugScopes configuration.

Cause: This may be due to an I/O error while reading the DebugScopes from the disk.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320452: An error occurred while adding PropertyChangeListener to bean {0}.

Cause: The debug configuration bean does not support PropertyChangeListeners.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320453: An error occurred while removing PropertyChangeListener from bean {0}.

Cause: The debug configuration bean does not support PropertyChangeListeners.

Action: Take action based on the error stack trace.
Level: 1

Type: ERROR

Impact: DebugModule

BEA-320500: The built-in WebLogic Diagnostics Framework resource descriptor ${0} for the selected level &quot;{1}&quot; could not be found; setting built-in resource to ${2}.

Cause: The WebLogic Diagnostics Framework resource descriptor for the desired built-in monitoring state could not be loaded due to either an issue with the WebLogic Server kit installation or an environmental issue in the domain configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsRuntimeControl

BEA-320800: Failed to cache the instrumentation engine configuration at {0} with exception {1}

Cause: The destination file may not be writable or some other I/O error occurred.

Action: Check to see if the destination file is writable.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320801: Failed to load instrumentation engine configuration {0}.

Cause: The instrumentation engine configuraion may be missing or corrupt.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320802: Missing the name attribute for the instrumentation engine configuration at {0}.

Cause: The engine configuration does not have the required name attribute.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320803: Duplicate instrumentation engine configuration {0} found.

Cause: A duplicate instrumentation engine configuration was found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320804: Invalid parent "{1}" for instrumentation engine configuration "{0}".

Cause: The instrumentation engine configuration has an incorrect parent configuration.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320805: Required root instrumentation engine configuration was not found.

Cause: The required root instrumentation engine configuration was not found.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320806: Found circular dependency with instrumentation engine configurations: {0}

Cause: The instrumentation engine configurations are invalid.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320807: Parent "{0}" for instrumentation engine configurations {1}.

Cause: The parent configuration for an instrumentation engine configuration cannot be located.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: DiagnosticsInstrumentor

BEA-320900: Agent will be unable to proxy for the agents specified due to Proxy initialization error.

Cause: Refer to exception message for cause of initialization failure.

Action: Take appropriate action based upon the specified exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320913: Failed to register Attribute Change listener {0} for MBean type {1} on server {2}.

Cause: This may be due to a misconfigured SNMPAttributeChange entry specification in config.xml. Please refer to the exception message for more specific cause information.

Action: Modify configuration of the SNMPAttributeChange entry or take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320918: Failed to add NotificationListener to logBroadcaster for SNMPLogFilter {0}.

Cause: Please refer to the exception message for more specific cause information.

Action: Take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320923: Error creating JMX Monitor {0} of type {1} for MBean {2}.

Cause: This may be due to a misconfigured Monitor entry specification. Please refer to the exception message for more specific cause information.

Action: Modify the configuration of the SNMPJMXMonitorMBean entry or take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320925: Failed to send Monitor trap for server {0} for type {1} for object {2}.

Cause: Please refer to the exception message for more specific cause information.

Action: Take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320927: SNMP agent is initializing.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320928: SNMP Agent initialization failed while accessing server information for the configured Domain.

Cause: Refer to earlier SNMP error log information for specific information on the cause of the problem.

Action: Take appropriate action based upon the specific exception message.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320929: SNMP agent initialization completed successfully.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320930: SNMP Agent Generic coldStart trap sent.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320931: The SNMP trap version is {0}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320937: Exception occurred sending SNMP message, {0}.

Cause: This is an internal error that occurred during the sending of an SNMP message using the TCP transport provider.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320938: SNMP Agent does not support setting values for MBean attributes through SNMP.

Cause: You attempted to set an MBean attribute using SNMP.

Action: Use JMX APIs to update the WLS configuration MBeans.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320939: An error occurred while adding a row to the SNMP table for MBean {1} of type {0}.

Cause: This could be due to a row already existing in the SNMP Agent for the MBean or an error condition in the SNMP Agent.

Action: Take appropriate action based on additional information in the error stack trace.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320940: An error occurred while deleting the row from the SNMP table for MBean {0}.

Cause: The specified MBean instance was not registered in SNMP or it could be due to an error condition in the SNMP Agent.

Action: Take appropriate action based on additional information in the error stack trace.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320941: An SNMP message was received over the default channel instead of the dedicated SNMP channel.

Cause: This occurs when a dedicated Network Access Point for SNMP traffic has been configured and activated and an SNMP request is received over the default server channel.

Action: Direct the SNMP request to the configured channel.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320942: The specified type name {0} is invalid.

Cause: The specified name is not recognized as a valid WebLogic Server MBean type.

Action: Please specify the correct name for a WebLogic Server Configuration or Runtime MBean type.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320943: The specified attribute name {1} is not valid for the given type {0}.

Cause: The specified attribute name that is not valid was specified as part of the configuration.

Action: Please specify the correct attribute name for the WebLogic Server Configuration or Runtime MBean type.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320944: The SecurityName attribute is not specified for the SNMPTrapDestination {0}.

Cause: The SNMP Agent's trap version is set to V3 and the SecurityName is not specified for the given SNMPTrapDestination.

Action: Please specify the SecurityName attribute for which the SNMP Agent will issue V3 traps.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320945: The SNMP Agent's TrapVersion needs to be V2 or higher to be able to send INFORM notifications.

Cause: The SNMPAgentMBean's SNMPTrapVersion attribute is set to V1.

Action: Set the SNMPTrapVersion to V2 or higher in the configuration.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320946: The SNMP Agent {0} is already deployed to server {1}.

Cause: An attempt was made to target multiple SNMPAgentDeploymentMBeans to the same WebLogic Server instance.

Action: Ensure that only one SNMPAgentDeploymentMBean is targeted to any Server in the domain.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320947: The AuthenticationProtocol for SNMP Agent {0} cannot be noAuth when PrivacyProtocol {1} is specified.

Cause: An invalid combination of authentication and privacy protocols was configured.

Action: Specify either MD5 or DES as the AuthenticationProtocol in combination with Privacy.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320948: The SNMPTrapDestinationMBean {0} has a higher SecurityLevel {1} than the SNMPAgent's SecurityLevel {2}.

Cause: An invalid combination of authentication and privacy protocols on the SNMPAgentMBean and security level on the SNMPTrapDestinationMBean has been configured.

Action: Specify the valid security level for the users and the trap destinations.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320949: SNMPAgent {0} is configured with a security level of {1}; the security level of {3} for proxy {2} must not exceed that of the SNMP agent.

Cause: A security level on the SNMP proxy was configured that exceeds the security level of the SNMP agent that corresponds to its configured authentication and privacy protocols.

Action: Configure a level of security on the proxy that is lower than the security level of the SNMP agent. For example, if the SNMP agent is configured with authentication but no privacy, configure the security level of NOAUTH_NOPRIV or AUTH_NOPRIV on the proxy.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320950: Failed to start the SNMP agent. If it failed to bind to the port, check if the port is available or the process has permission to bind to the port.

Cause: Binding to specified UDP and agentX ports is a common problem. The ports to which the agent binds may not be available. Also, on UNIX platforms, ports up to 1023 are protected and can be bound only by processes owned by root.

Action: Check whether the specified ports are available. On UNIX, the default UDP port (161) and master AgentX port (705) are protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320951: Failed to initalize the SNMP AgentX master subagent. One possible cause is the failure to bind the Master agentX port. If this is the case, check to see if the specified AgentX port is available, or ensure that the process has permissions to bind to the desired port.

Cause: A common problem is with binding to the specified agentX port. The port to which the agent binds may not be available. Also, on UNIX platforms, ports up to 1023 are protected and can be bound only by processes owned by root.

Action: Check whether the specified port is available. On UNIX, the default master AgentX port (705) is protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320952: Failed to send the SNMP trap or inform notification for trap OID {2}. Number of send attempts = {0}. Number of errors encountered = {1}. The detailed error message from the SNMP toolkit is {3}.

Cause: The SNMPTrapDestination(s) could be incorrectly configured or the SNMP Manager might not be running at the configured location.

Action: Ensure that the SNMP Manager is available at the configured SNMP TrapDestinations.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320953: The SNMP Agent has been started on port {0}.

Cause: The SNMP Agent tries to bind to the configured port. If this port is not available due to another SNMP Agent being deployed to the same machine on another WebLogic Server instance then the SNMP Agent tries to find the nearest port and binds to it.

Action: No action is needed. The port number is also reflected in the UDPListenPort attribute of the SNMPAgentRuntimeMBean interface on this Server.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320954: The SNMP Agent encountered an error while discovering Extensions {0}.

Cause: The SNMPAgent Extension provider implementations could not be loaded successfully.

Action: Take corrective action based on the exception details.
Level: 1

Type: ERROR

Impact: SNMP

BEA-320955: SNMP agent has been shut down.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: SNMP

BEA-320956: Error registering trap destination {0} for address {1}:{2}.

Cause: The host name specified in the SNMPTrapDestination configuraiton is not valid.

Action: Correct the configuration and start the SNMP agent again.
Level: 1

Type: ERROR

Impact: SNMP

BEA-340450: Descriptor {1} has no configuration-support in the weblogic-extension.xml file for application module {0}. JSR-88 updates will not be supported.

Cause: The configuration-support stanza was missing or has XML errors.

Action: Correct the weblogic-extension.xml file and redeploy the application.
Level: 1

Type: WARNING

Impact: CustomModule

BEA-340451: URI mismatch for base-URI ({2}) in the weblogic-extension.xml file for descriptor {1} in module {0}. Unpredictable results from JSR-88 updates are likely.

Cause: The custom-module URI does not match the configuration-support base-URI.

Action: Correct the base-URI in the configuration-support stanza of the weblogic-extension.xml file to match the custom-module URI and redeploy the application.
Level: 1

Type: ERROR

Impact: CustomModule

BEA-340452: Prepare to deploy descriptor {1} in application module {0}.

Cause: This is normal behavior.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CustomModule

BEA-340454: Prepare update for descriptor {1} in application module {0}.

Cause: This is normal behavior.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: CustomModule

BEA-400000: Initializing message interception service.

Cause: WebLogic Server starts the message interception service.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: messaging.interception

BEA-400200: Incorrect arguments. Expects 2 arguments.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400201: Migrating old security provider JARS from {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400204: No security provider JARs have been upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400205: Copying the upgraded security provider JAR to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400206: Completed upgrading of {0} old security provider JARs.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400207: Skipped converting {0} since it is a security provider JAR built with 9.0.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400208: No MDFs (.xmls) found in the old security provider JAR with name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400209: Created new security provider JAR {0} from {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400210: The XML file {0} is not a valid MDF, hence the upgrade tool will ignore this file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400211: Not upgrading {0} because either this is an out-of-the-box Oracle security provider JAR or this security provider JAR is already upgraded or this is not a valid archive file (may not be a .jar).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400212: Now processing {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400213: Could not convert from MDF {0}. This file may not be a valid MDF file; verify.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400214: Running the first phase of Security Provider Upgrade process on {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-400215: First phase successful, now running the second and last phase of security provider upgrade process on {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade-SecurityProviders

BEA-420000: The message interception service cannot bind "{0}" to the local JNDI.

Cause: The JNDI name was already used.

Action: Avoid using JNDI names starting with weblogic. Correct this problem then try again.
Level: 1

Type: WARNING

Impact: MIExceptions

BEA-420002: The addAssociation method encountered an input error due to "{0}".

Cause: There was an illegal usage of the addAssociation API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420003: The addAssociation method encounters some usage error due to "{0}".

Cause: The interception point type is unknown either due to typo or the registerInterceptionPointNameDescription method didn't register the expected interception point type first.

Action: If this is caused by an external application then fix the related code. Otherwise, contact the customer support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420004: The removeAssociation method encountered an input error due to "{0}".

Cause: There was an illegal usage of the removeAssociation API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420005: The registerInterceptionPointNameDescription method encountered an input error due to "{0}".

Cause: There was an llegal usage of the registerInterceptionPointNameDescription API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420006: The registerInterceptionPoint method encountered an input error due to "{0}".

Cause: There was an illegal usage of the registerInterceptionPoint API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420007: The registerInterceptionPoint method encountered a usage error due to "{0}".

Cause: The interception point type is unknown either due to a typo or the registerInterceptionPointNameDescription method did not register the expected interception point type first.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420008: The unRegisterInterceptionPoint method encountered an input error due to "{0}".

Cause: There was an illegal usage of the unRegisterInterceptionPoint API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420009: The registerProcessorType method encountered an input error due to "{0}".

Cause: There was an illegal usage of the registerProcessorType API.

Action: If this is caused by an external application, then fix the related code; Otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420010: The addProcessor method encountered an input error due to "{0}".

Cause: There was an illegal usage of the addProcessor API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420011: The addProcessor method encountered a usage error due to "{0}".

Cause: The processor type is unknown either due to a typo or the registerProcessorType method did not register the expected processor type first.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420012: The removeProcessor method encountered an input error due to "{0}".

Cause: There was an illegal usage of the removeProcessor API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420013: The getAssociationHandle method encountered an input error due to "{0}".

Cause: There was an illegal usage of getAssociationHandle API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420014: The getProcessorHandles method encountered an input error due to "{0}".

Cause: There was an illegal usage of the getProcessorHandles API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420015: The getProcessorHandle method encountered an input error due to "{0}".

Cause: There was an illegal usage of the getProcessorHandle API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420016: The registerInterceptionPointNameDescriptionListener method encountered an input error due to "{0}".

Cause: There was an illegal usage of the registerInterceptionPointNameDescriptionListener API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420017: The removeAssociation method encountered an input error due to "{0}".

Cause: There was an illegal usage of the removeAssociation API.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420019: The process method encountered a usage error due to "{0}".

Cause: The required processor for the given association was not created at the time. To send a message to a target that has the given association defined, the processor specified in the association needs to be added beforehand.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420020: The process method encountered a usage error due to "{0}".

Cause: The processor generated an illegal error.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420021: The process method encountered a usage error due to "{0}".

Cause: The processor generated an illegal runtime exception.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420025: The addAssociation method encountered a usage error due to "{0}".

Cause: The added association already exists.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420026: The unregisterInterceptionPoint method encountered a usage error due to "{0}".

Cause: The interception point has already been removed.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420027: The interception point name argument is invalid due to "{0}".

Cause: The interception point name argument is invalid for several possible reasons. For example, the total number of name element differs from what is being registered with the interception service or one name element is invalid by itself.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420028: The removeProcessor method encountered a usage error due to "{0}".

Cause: The processor has been removed.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420029: The registerProcessorType method encountered a usage error due to "{0}".

Cause: The processor factory class cannot be instantiated.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420030: The registerProcessorType method encountered a usage error due to "{0}".

Cause: The processor factory class cannot be instantiated.

Action: If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-420031: The process method encountered a usage error due to "{0}".

Cause: The processor is currently processing more intercepted messages than that the association's depth allows.

Action: Increase the depth on the association using the association handle object.
Level: 1

Type: ERROR

Impact: MIExceptions

BEA-1000000: The object to be used for reflection while looking up setter "{0}" is null.

Cause: The user may have passed null in as the object upon which to reflect.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000001: While attempting to find a setter on object "{0}", the name of the setter is null.

Cause: The user may have passed null in as the name of the setter.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000002: While attempting to find a setter on object "{0}", the type of the setter was null.

Cause: The user may have passed null in as the type of the setter.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000003: The filter passed into the registerDependencyWithFilter method is null.

Cause: The user passed null in as the filter to the method registerDependencyWithFilter.

Action: Modify the code such that it does not pass null in as the filter to the method registerDependencyWithFilter.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000004: The filter passed into the registerDependencyWithFilter method is null.

Cause: The user passed null in as the filter to the method registerDependency.

Action: Modify the code such that it does not pass null in as the filter to the method registerDependency.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000005: The ServiceHelper service has been closed.

Cause: While waiting for a service object the ServiceHelper was closed.

Action: Do not close the ServiceHelper while waiting for a service object.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000006: The timer expired while waiting for a service object with filter "{0}".

Cause: The service object corresponding to the given filter was not available within the specified timeout.

Action: Ensure the service is available in the timeout period.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000007: Not yet implemented.

Cause: Using an unimplemented API.

Action: Contact BEA Customer Support.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-1000008: Could not find a setter named "{0}" for type "{1}" on an object of type "{2}".

Cause: There was no method of the given name of the given type on the given class.

Action: Ensure the setter name is correct. Ensure the object upon which it is looking for such a method has the method.
Level: 1

Type: WARNING

Impact: ServiceHelper

BEA-2004000: An error occurred while loading the Kodo-Oracle message dictionary.

Cause: This can happen if the Kodo-Oracle message dictionary is not available. This dictionary should be located at {0}.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Kodo Integration

BEA-2004001: The Kodo-Oracle message dictionary was not found.

Cause: This can happen if the Kodo-Oracle message dictionary is not available. This dictionary should be located at {0}.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Kodo Integration

BEA-2004003: Kodo localization key {0} has already been registered in the Kodo-Oracle message ID dictionary. Original value: {1}. New value: {2}. New definition from URL: {3}. The original value will be used.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Kodo Integration

BEA-2011000: The bundle {0} has started successfully.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterAPI

BEA-2011099: The bundle {0} has been successfully stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterAPI

BEA-2011100: The bundle {0} has successfully started.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011101: An unexpected Exception occurred in harvester {0}. Logging it here and continuing processing... Context: {1}, Exception: {2}

Cause: An unexpected exception occurred during the harvesting process.

Action: You should attempt to uncover the reason for the underlying Exception.
Level: 1

Type: WARNING

Impact: HarvesterJMX

BEA-2011102: An unexpected condition was encountered in harvester {0}. Logging it here and continuing processing... Context: {1}

Cause: An unexpected condition occurred during the harvesting process.

Action: The user should attempt to uncover the reason for the problem.
Level: 1

Type: WARNING

Impact: HarvesterJMX

BEA-2011103: Service with name: {0} has been prepared.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011104: Service with name: {0} has been acivated.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011105: Service with name: {0} has been deactivated.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011199: The bundle {0} has successfully been stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterJMX

BEA-2011300: The bundle {0} has successfully started.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterUtils

BEA-2011399: The bundle {0} has successfully been stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HarvesterUtils

BEA-2012300: The bundle {0} has successfully started.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2012301: Processing {0} MBeans.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2012302: Processed {1} MBeans for MBean utility {0}.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2012303: The MBeanTypeUtil cannot process an MBean instance due to excp {0} on MBeanServer: {1} and MBean: {2} stack trace: {3} --- Retrying once...

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012304: The MBeanTypeUtil failed for a second time to process an MBean instance due to excp: {0} on MBeanServer: {1} and MBean: {2} stack trace: {3} --- Skipping this MBean...

Cause: This ia an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012305: The MBeanTypeUtil failed to process two distinct MBeans in a row. The most recent problem was on MBeanServer: {0} and MBean: {1} stack trace: {2} --- No further MBeans will be processed.

Cause: This is an internal error.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012306: {1} Unable to process the {2} of MBean: {0} due to internal errors. The managed process might be shutting down. Stack trace: {3}

Cause: The process is most likely shutting down, so it is safe to ignore this.

Action: If the process is known to be active, contact My Oracle Support to determine why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012307: {1} Unable to process the {2} of MBean: {0} due to internal errors. The managed process appears to be shutting down. Stack trace: {3}

Cause: The process is most likely shutting down, so it is safe to ignore this.

Action: If the process is known to be active, contact My Oracle Support to determine why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed.
Level: 1

Type: WARNING

Impact: MBeanTypingUtil

BEA-2012308: An uexpected error occurred while scheduling work for MBeanTypeUtil instance {0} with work manager {1}: {2}

Cause: Possibly no work manager was set, or the work manager was unable to queue the request.

Action: If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012309: An uexpected error occurred while communicating with the MBeanServer: {0}

Cause: The MBeanServer or host process may no longer be available. If the MBeanServer is remote, there may be network issues.

Action: If the problem persists, contact My Oracle Support.
Level: 1

Type: ERROR

Impact: MBeanTypingUtil

BEA-2012399: The bundle {0} has been successfully stopped.

Cause: This is a normal operation.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: MBeanTypingUtil

BEA-2150001: Validation of weblogic-pubsub.xml descriptor file failed. The error is {0}

Cause: There are errors in the weblogic-pubsub.xml descriptor file.

Action: Correct the error in weblogic-pubsub.xml according to the schema.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150002: No permission on channel operation: User {0} has no permission to create channel {1}

Cause: There are not sufficient privileges to create a channel.

Action: Check the PubSub server configuration security settings.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150003: No permission on channel operation: User {0} has no permission to delete channel {1}

Cause: There are not sufficient privileges to delete a channel.

Action: Check the PubSub server configuration security settings.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150005: Invalid persistent-client-timeout-secs: {0}.

Cause: The persistent-client-timeout-secs must be greater than the timeout-secs.

Action: Check the persistent-client-timeout in the PubSub server configuration
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150006: Invalid transport type: {0}

Cause: An invalid transport type was configured in the PubSub server configuration.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150007: Cannot find configuration for referenced message filter {0}; check message-filter in the PubSub server configuration.

Cause: There is a mismatch between the message filter name referenced in the channel setting and the message-filter setting.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150008: There is no message filter configured in the PubSub server configuration, but there is a message filter named {0} referenced in the channel setting.

Cause: The channel setting is requesting a message filter but the message filter was not specified in the PubSub server.

Action: Either specify the message-filter setting or remove the message-filter reference from the channel setting.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150009: Invalid message-filter configured: message-filter {0} is configured in PubSub server configuration, but its associated class {1} cannot be initialized correctly.

Cause: Class {1} associated with message filter {0} is incorrect.

Action: Check the message-filter-name and message-filter-class in the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150011: Action {1} on channel {0} is not allowed for any client.

Cause: The PubSub server configuration constraints do not allow this action on this channel. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150012: Client {0} is an anonymous user but channel {1} requests login.

Cause: Login is requested to perform this action. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150013: Client {0} is not allowed to perform action {2} on channel {1}.

Cause: The PubSub server configuration does not allow this action on this channel. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150014: Client {0} is allowed to perform action {2} on channel {1}

Cause: The PubSub server configuration is allowing this action to be performed on this channel. This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150015: Client {0} has no permission to subscribe channel {1}

Cause: Client {0} has no permission to subscribe channel {1}, either because the client configuration does not allow the client to access the channel, or the client is anonymous and the channel configuration only allows specific clients to access the channel.

Action: Check the PubSub server security constraint configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150016: Client {0} has no permission to publish on channel {1}

Cause: The client is not configured to publish on the channel or the client is anonymous and the channel is configured to only allow access to specific clients.

Action: Check the PubSub server security constraint configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150017: Failed to register MBean for Channel {0}

Cause: An exception occurred while registering the ChannelRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150018: Failed to unregister MBean for Channel {0}

Cause: An exception occurred while unregistering the ChannelRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150019: Initialize PubSub server {0}

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150020: Duplicate initialize PubSub server {0}

Cause: There are multiple servlet and servlet-mapping definitions for com.bea.httppubsub.servlet.ControllerServlet in the web.xml file.

Action: Check the web.xml file.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150021: Cannot initialize service channel {0}

Cause: An exception occurred when initializing the service channel.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150024: Unknown meta channel found from Bayeux message: {0}

Cause: An incoming message specifies a channel other than /meta/handshake, /meta/connect, /meta/reconnect, /meta/disconnect, /meta/subscribe, or /meta/unsubscribe.

Action: Check the Bayeux client and the incoming Bayeux message.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150025: System property {0} is not set to specify an MBeanManagerFactory implementation.

Cause: System property {0} is not set.

Action: Ensure that runtime MBeans are not necessary; otherwise, set system property {0} to a proper implementation of MBeanManagerFactory.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150026: Can not initialize instance of MBeanManagerFactory with class {0}

Cause: An exception occurred while initializing MBeanManagerFactory.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150027: Failed to register WebPubSubRuntimeMBean for PubSub server; the ContextPath is {0}

Cause: An exception occurred while registering WebPubSubRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150028: Failed to unregister WebPubSubRuntimeMBean for PubSub server; the ContextPath is {0}

Cause: An exception occurred while unregistering WebPubSubRuntimeMBean.

Action: Check the stack trace for more detailed information.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150029: ControllerServlet initialization failed: {0}

Cause: An exception occurred when ControllerServlet was initialized.

Action: Check the exception stack trace for details.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150030: Cannot fetch JSON message from incoming request

Cause: For long-polling request messages, messages are sent to the server as the body of a POST, encoded either as "application/x-www-form-urlencoded" or as "text/json". If sent as form encoded, the Bayeux messages are sent as the "message" parameter. For callback-polling request messages, messages are sent to the server either using POST requests as per long-polling transport or as the "message" URL parameter of a GET request.

Action: Check the incoming HTTP request and the Bayeux protocol specification.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150031: Cannot load properties from {0} in classpath.

Cause: The property file does not exist in the classpath.

Action: Check the classpath.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150032: Cannot find persistent store {0} specified to channel {1}; will use the default store.

Cause: The persistent store may not be configured properly.

Action: Check the configuration of the persistent store.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150033: Invalid client-timeout-secs: {0}.

Cause: Either a negative or a zero value was set for client-timeout-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150034: Invalid interval-millisecs: {0}.

Cause: A negative value was set for interval-millisecs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150035: Invalid multi-frame-interval-millisecs: {0}.

Cause: A negative value wass set for multi-frame-interval-millisecs.

Action: Check tue PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150036: Invalid persistent-client-timeout-secs: {0}.

Cause: Either a negative value or zero was set for persistent-client-timeout-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150037: Invalid max-persistent-message-duration-secs: {0}.

Cause: Either a negative value or zero was set for max-persistent-message-duration-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150038: Initializing channel authorization manager: {0}

Cause: This channel authorization manager will be used for authorizing channel actions.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server

BEA-2150039: Error initializing channel authorization manager.

Cause: The initialization of channel authorization manager failed.

Action: See the exception stack trace for details.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150041: Invalid channel {0}, cause is {1}.

Cause: An invalid channel field was found.

Action: Check the Bayeux client.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150042: A role {0} is being deployed implicitly without a pricipal mapping in the corresponding weblogic.xml.

Cause: There is no security-role-assignment for role {0}

Action: Create a security-role-assignment in weblogic.xml for role {0}
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150043: Security authorization has been disabled for the PubSub server.

Cause: PubSub server security has been disabled by an undocumented system property.

Action: If this property has not been set deliberately, verify all the system properties that begin with com.bea.httppubsub.security.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server

BEA-2150044: Invalid connection-timeout-secs: {0}.

Cause: Either a negative or a zero value was set for connection-timeout-secs.

Action: Check the PubSub server configuration.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150045: Incoming Bayeux message does not contain 'channel' field.

Cause: Incoming Bayeux message did not contain the 'channel' field.

Action: Turn on Bayeux message debug flag to check the Bayeux message sent by the client.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2150046: Invalid JSON format of a Bayeux message

Cause: A Bayeux message could not be recognized by the JSON parser.

Action: Turn on the Bayeux message debug flag to check the Bayeux message and exception for details.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server

BEA-2152001: Cannot create a default JmsProviderFactory instance.

Cause: The class loader could not find the default JmsProviderFactory class in the classpath or the default JmsProviderFactory class has no public non-argument constructor.

Action: No action is required.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152002: Cannot create JmsProviderFactory instance for given class name [{0}].

Cause: The class loader could not find {0} in the classpath or {0} has no public no-argument constructor.

Action: Ensure that the correct JmsProviderFactory class name is used.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152003: JmsProviderFactory [{0}] registered.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152021: Try to initialize JmsProvider using the following configurations: JmsProviderUrl -> [{0}]; ConnectionFactoryJndiName -> [{1}]; TopicJndiName -> [{2}].

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152022: Cannot retrieve ConnectionFactory or topic.

Cause: There were incorrect JMSHandler configurations in the weblogic-pubsub.xml file.

Action: Check the JMSHandler configurations in the weblogic-pubsub.xml file.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152041: Channel-Handler mapping: [{0}] -> [{1}]

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152042: No ChannelBeans are configured in the descriptor file, ignore JMS channel mapping initialization.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152043: Total [{0}] JMS handler mapping configuration(s) found.

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152044: JMS handler mapping: [{0}] -> [{1}]

Cause: This is an informational message.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: HTTP Pubsub Server JMS support

BEA-2152061: Cannot initialize JMS channel [{0}].

Cause: A JMS-related exception occurred.

Action: Ensure that the JMS configurations are correct and that the JMS server has been started.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152081: Cannot publish message to JMS topic.

Cause: A JMS-related exception occurred.

Action: No action is required.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server JMS support

BEA-2152082: Cannot initialize publish functionality for JMS channel.

Cause: A JMS-related exception occurred.

Action: Check the configuration for the JMS connection factory and topic.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152101: No permission to publish to channel {0}.

Cause: The security permission was not configured properly.

Action: Check the security configuration in the weblogic-pubsub.xml file.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server JMS support

BEA-2152102: Cannot initialize topic listener for JMS channel.

Cause: A JMS-related exception occurred.

Action: Check the configuration for the JMS connection factory and topic.
Level: 1

Type: ERROR

Impact: HTTP Pubsub Server JMS support

BEA-2152103: Error occurs when retrieving a message from the JMS topic.

Cause: A JMS-related exception occurred.

Action: Check the messages published to the JMS topic, and enable the JMS log for analysis.
Level: 1

Type: WARNING

Impact: HTTP Pubsub Server JMS support

BEA-2154000: Enabling FastSwap on application "{0}".

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154001: Starting FastSwap operation on application "{0}".

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154002: Finished FastSwap operation on application "{0}" with status {1}.

Cause: This message is for informational purposes only.

Action: No action is required.
Level: 1

Type: NOTIFICATION

Impact: FastSwap

BEA-2154003: FastSwap operation on application "{0}" failed: {1}.

Cause: One or more classes could not be redefined.

Action: Redeploy the application for updates to classes to take effect.
Level: 1

Type: ERROR

Impact: FastSwap

BEA-2156001: "config-root" {0} is not a directory.

Cause: The "config-root" may not have been set properly.

Action: Verify that the "config-root" is correct.
Level: 1

Type: WARNING

Impact: WebLogicDescriptorWL

BEA-2156002: Attribute "{0}": duration value "{1}" is not valid: {2}

Cause: The provided duration value was not a valid duration lexical representation.

Action: See the lexical rules for a javax.datatype.Duration, and ensure that the provided duration value is valid according to these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156003: Attribute "{0}": logical store name value "{1}" is not valid.

Cause: The provided logical store name value was not a valid name. Logical store names must be valid Java identifiers.

Action: See the lexical rules for a Java identifier, and ensure that the logical store name follows these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156004: Attribute "{0}": JNDI name value "{1}" is not valid.

Cause: The provided JNDI name value was not a valid name. JNDI names must be non-null and non-empty and meet the rules of the J2EE platform's JNDI implementation.

Action: See the lexical rules for a JNDI name, and ensure that the JNDI name follows these rules.
Level: 1

Type: ERROR

Impact: WebLogicDescriptorWL

BEA-2156200: Unable to load descriptor {1} of module {0}. The error is {2}.

Cause: The descriptor is not valid.

Action: Correct the descriptor.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156201: An error occurred while parsing descriptors: {0}.

Cause: Check the stack trace.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156202: References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.

Cause: The plan contained variable overrides.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156203: A version attribute was not found in element "{0}" in the deployment descriptor {1}. A version attribute is required, but this version of the WebLogic Server will assume that the latest version is used. Future versions of WebLogic Server will reject descriptors that do not specify the Java EE version. To eliminate this warning, add an appropriate "version=" to element "{0}" in the deployment descriptor.

Cause: The required version attribute was missing.

Action: Add the version attribute with the appropriate JEE version value.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156204: The root element {0} is missing in the descriptor file {1}.

Cause: The required root element was missing in the descriptor file.

Action: Add the root element to the descriptor file.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156205: Updating the configuration with the deployment plan overrides for module "{0}" with URI, "{1}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156206: No module overrides were found in the deployment plan for module "{0}" with URI, "{1}". If overrides were expected for this module, verify the deployment plan.

Cause: The plan contained no matching variable overrides.

Action: No action is required. This is an informational message. It may be an expected action.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156207: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.

Cause: The plan contained matching variable overrides.

Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156208: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.

Cause: The plan contained matching variable overrides.

Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156209: Applying the overrides from the deployment plan for module "{0}" with URI, "{1}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156210: Applying the override for variable "{0}" with XPath "{1}" and operation "{2}".

Cause: A deployment plan was specified for the application.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156211: After applying the overrides from the deployment plan, the descriptor "{0}" is: "{1}".

Cause: A deployment plan was specified for the application. The descriptor was updated.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156212: An error occurred while parsing the specifed XPath "{0}" : {1}.

Cause: The specified XPath value was invalid.

Action: Check the associated exception to determine the cause, and correct the XPath value.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156213: An error occurred while parsing the specifed XPath "{0}" : {1}.

Cause: The specified XPath value was invalid.

Action: Check the associated exception to determine the cause, and correct the XPath value.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156214: The XPath "{0}" specifies a key selection but the bean "{1}" does not have any keys defined.

Cause: The specified XPath value was invalid because no keys were defined for this element.

Action: Check the associated schema, and ensure that the element has the corresponding key.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156215: Removed the value matched by the deployment plan variable "{0}" with element name "{1}".

Cause: A deployment plan was specified for the application, and an element has been removed.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156216: The deployment plan operation failed because there was no method named "{0}" on the bean "{1}" corresponding to the element "{2}".

Cause: A deployment plan operation requires a corresponding destroy, remove, or set method. This method was not present.

Action: Contact My Oracle Support.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156217: An error occurred while performing the plan operation for variable "{0}" with element name "{1}" : {2}.

Cause: An unexpected exception occurred during the deployment plan operation.

Action: Check the associated exception to determine the cause, and correct the issue.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156218: Updated the element matched by the deployment plan variable "{0}" with element name "{1}" to have value "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been updated.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156219: Created the element matched by the deployment plan variable "{0}" with element name "{1}".

Cause: A deployment plan was specified for the application, and a matching element has been created.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156220: Created the element matched by the deployment plan variable "{0}" with element name "{1}" to have name "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been created.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156221: The remove operation for the deployment plan variable "{0}" with element name "{1}" specified an array index of "{2}" but the array was smaller, so no elements were removed.

Cause: The specified array index was larger than the size of the array.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156222: The variable "{0}" specifies a property "{1}" that is a primitive array but no index is specified in the XPath.

Cause: The specified XPath value was invalid since no array index was defined for this element.

Action: Check the XPath, and specify an index.
Level: 1

Type: ERROR

Impact: Munger

BEA-2156223: The variable "{0}" for the add operation does not specify a property in the XPath "{1}". This variable assignment has been ignored.

Cause: The specified XPath value was invalid since no property was specified for the add operation.

Action: Check the XPath, and specify a property.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156224: Added the element matched by the deployment plan variable "{0}" with element name "{1}" with value "{2}".

Cause: A deployment plan was specified for the application, and a matching element has been added.

Action: No action is required. This is an informational message.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156225: The XPath "{0}" contains a trailing invalid "/". It has been ignored. Remove it from the XPath expression.

Cause: The specified XPath value was invalid because it contained a trailing slash.

Action: Remove the trailing slash.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156226: Skipping the override for the deployment plan variable "{0}" and XPath "{1}" since the value is not set in the deployment plan.

Cause: A deployment plan did not contain a value for the variable.

Action: Add a variable value if one is desired, or remove the variable assignment if it is not needed.
Level: 1

Type: NOTIFICATION

Impact: Munger

BEA-2156227: The "{0}" deployment descriptor for the "{1}" module is in DTD format. Overrides from the deployment plan will NOT be applied since only deployment descriptors in XML Schema format are supported.

Cause: A deployment descriptor in DTD format exists in the application archive.

Action: Convert the deployment descriptor to an XML Schema format.
Level: 1

Type: WARNING

Impact: Munger

BEA-2156250: The value {1} is illegal for {0}. Legal value for this attribute is >= -1. Although the current release of WebLogic Server is accepting this value, future releases may reject the configuration.

Cause: The current WebLogic Server version accepts this value to support prior releases that allowed arbitrary negative values.

Action: Fix the configuration to specify a value for this parameter in the valid legal range.
Level: 1

Type: WARNING

Impact: WebLogicJavaEEDescriptorValidator

BEA-2156300: Coherence JAR is in the system classpath and there is more than one instance of CoherenceClusterSystemResourceMBean defined using {0}

Cause: Multiple instances of CoherenceClusterSystemResourceMBean were targeted.

Action: When the Coherence JAR is in the system classpath, only one CoherenceClusterSystemResourceMBean should be targeted to the server.
Level: 1

Type: NOTIFICATION

Impact: CacheProvider

BEA-2156301: Failed to shut down application {0} due to {1}

Cause: Failed to shut down application {0} due to {1}

Action: Examine the exception details and take corrective actions.
Level: 1

Type: ERROR

Impact: CacheProvider

BEA-2156302: Only one server can be a management proxy in a Coherence cluster. {0} has {1} and {2} set as management proxies

Cause: Only one server can be a management proxy in a Coherence cluster. {0} has {1} and {2} set as management proxies.

Action: Examine the CoherenceMemberConfig management proxy setting for each server.
Level: 1

Type: ERROR

Impact: CacheProvider

BEA-2156303: Invoking {0} on node {1} resulted in {2}.

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: CacheProvider

BEA-2156304: MBeanServerConnector not available at: {0}

Cause: TBD

Action: TBD
Level: 1

Type: WARNING

Impact: CacheProvider

BEA-2156400: The validation.xml file, located at {0}, does not conform to the JSR 303 specifications.

Cause: The file does not conform to the JSR 303 specification. This may be because the file is intended to configure another validation framework or because of a typo in the file.

Action: JSR 303 specifies the location of the validator descriptor as either WEB-INF for web applications or META-INF for all other cases. A validation.xml file at that location should only be used for the purpose of configuring javax.validation. If the purpose of the file is to configure another validation framework, consider using a different name or placing the file in a different location.
Level: 1

Type: WARNING

Impact: Weblogic-Validation

BEA-2156401: Invalid URL, {0}, because {1}.

Cause: This is an internal error.

Action: Contact My Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156402: Unable to process URL, {0}. It is from jar: {1} resourceDir: {2} resourcePath: {3}.

Cause: This is an internal error.

Action: Contact My Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156403: Unable to process URL, {0}, because {1}.

Cause: The cause of the error is contained in the error message.

Action: Carefully examine the error message to determine the cause of the error and to determine the best way to fix it.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156404: Unable to find a Validation Context. {0}

Cause: This is an internal error.

Action: Contact My Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2156405: Unable to read resource, {0}, because {1}.

Cause: An IOException has occurred.

Action: Ensure that the resource is available for read.
Level: 1

Type: ERROR

Impact: Weblogic-Validation

BEA-2159000: An exception occurred while the listener {1} processed event {0}. The error is {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159001: An exception occurred while initializing WLS internal event bus {0}. The error is {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1

Type: ERROR

Impact: InternalEventBus

BEA-2159002: An exception occurred while loading the listener class {0}. The error is {1}. This listener will not be registered.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159003: An exception occurred while instantiating an instance of listener class {0}. The error is {1}. This listener will not be registered.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159004: An exception occurred while registering listeners defined as resources. The error is {1}.

Cause: Refer to the embedded exception information for more details as to the probable cause of this error.

Action: Fix the issue related to the embedded root exception. If the listeners associated with the exception are Oracle listeners, contact My Oracle Support.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2159005: An error occurred while processing the WebLogic internal events "{0}". The error is {1}.

Cause: See the embedded root exception.

Action: Fix the issue related to the embedded root exception.
Level: 1

Type: WARNING

Impact: InternalEventBus

BEA-2160000: Context "{0}" is not a web context. Spring runtime MBeans cannot be created.

Cause: The WeblogicSpringApplicationListener bean was added to (or registered as a listener on) an ApplicationContext that is not a web application context.

Action: Use WeblogicSpringApplicationListener only with a WebApplicationContext.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2160001: WebAppComponentRuntimeMBean not found. Spring runtime MBeans cannot be created.

Cause: This is an internal error.

Action: Contact My Oracle Support. Please capture errors and send the server log files to support.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2160002: "{0}" is not a registered scope name.

Cause: The scope name supplied to a runtime mbean operation is not registered.

Action: Supply a registered scope name to the runtime mbean operation.
Level: 1

Type: WARNING

Impact: WeblogicSpring

BEA-2162200: No Main-Class defined in the manifest file of Java Module: {0}. This module will be treated as a utility JAR and subsequent initialization steps will be skipped.

Cause: See the message body.

Action: No action is required unless you believe that this should be a Java client module. In this case, you should specify Main_Class for this module in MANIFEST.MF.
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162206: Warning: Could not find an entry for javax.transaction.UserTransaction in the root context.

Cause: There is no entry for javax.transaction.UserTransaction in the root context.

Action: Contact My Oracle Support.
Level: 1

Type: WARNING

Impact: Application Client

BEA-2162210: No persistence unit named '{0}' is available in scope.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162224: No {0} was specified in your client-jar file: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Application Client

BEA-2162500: Class, {0}, was compiled with an incompatible version of Java. Make sure that all the classes needed by the application have been compiled with a compatible java version. {1}

Cause: Class compiled with an incompatible Java compiler version.

Action: Insure that this and other classes are compiled with a compiler that is compatible with the JVM used by the application server.
Level: 1

Type: ERROR

Impact: Class Loaders

BEA-2162501: Class bytes found, but couldn't define class, '{0}' due to the following error: {1}

Cause: Unknown.

Action: Contact Oracle Support for assistance.
Level: 1

Type: ERROR

Impact: Class Loaders

BEA-2162502: Ignoring manifest file for classpath entry '{0}'

Cause:

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162503: Not adding pre-processor class '{0}'

Cause:

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162504: Not adding pre-processor class '{0}'

Cause:

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162505: Skipping pre-processing using pre-processor '{0}' with description: {1}

Cause:

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2162506: Ignoring manifest during definition of class '{0}'

Cause:

Action: To fix this problem, inspect the exception stack trace, and correct the problem
Level: 1

Type: WARNING

Impact: Class Loaders

BEA-2163000: OSGi system {2} could not install bundle from file {0} due to {1}

Cause: The OSGi system failed to install a bundle from a file.

Action: Fix the problem that is indicated in the error message and then restart the server.
Level: 1

Type: WARNING

Impact: OSGi

BEA-2163001: OSGi system {2} could not advertise data source {0} due to {1}

Cause: The OSGi system failed to advertise a data source.

Action: Fix the problem that is indicated in the error message and then restart the server.
Level: 1

Type: WARNING

Impact: OSGi

BEA-2163002: OSGi system {0} could not install bundles from $WL_HOME/server/osgi-lib.

Cause: At least one bundle from the $WL_HOME/server/osgi-lib directory could not be installed.

Action: Examine the bundles that failed to install, fix them, and then restart the server.
Level: 1

Type: ERROR

Impact: OSGi

BEA-2163003: Started OSGi system {0}.

Cause: An OSGi system has started.

Action: Write modular code and deploy it onto your OSGi system.
Level: 1

Type: NOTIFICATION

Impact: OSGi

BEA-2163004: OSGi system {2} could not advertise work manager {0} due to {1}

Cause: The OSGi system failed to advertise a work manager

Action: Fix the problem that is indicated in the error message and then restart the server.
Level: 1

Type: WARNING

Impact: OSGi

BEA-2163005: An application could not be deployed because it had conflicting OSGi framework names in its metadata. The OSGi framework names {0} and {1} were found.

Cause: More than one OSGi system was referenced in the application metadata files.

Action: Modify the metadata files of the application such that the application references only one framework.
Level: 1

Type: ERROR

Impact: OSGi

BEA-2163006: An application could not be deployed because it had conflicting OSGi bundle symbolic names in its metadata. The bundle symbolic names {0} and {1} were found.

Cause: More than one OSGi bundle was referenced in the application metadata files.

Action: Modify the metadata files of the application such that the application references only one bundle.
Level: 1

Type: ERROR

Impact: OSGi

11 BIACM-00007 to BIACM-00082

BIACM-00007: Import initialization error, no data

Cause: An error occurred while reading data from the file provided

Action: Ensure the file to be imported has data in the proper format
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00008: File not found

Cause: No file present at the given location

Action: Ensure the file location and filename are proper
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00009: Not a directory

Cause: Given input was not of directory type

Action: Ensure that only directory is supplied as the input
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00010: Concurrent migrations going on

Cause: Another import/export detected in some other session

Action: Please wait for ongoing import/export to complete
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00011: Error while validating data source number, non-numeric type

Cause: An error occurred while validating the data source number value

Action: Ensure whether the input value is numeric
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00013: No data server selected

Cause: No selection of any data server for the data source to be registered

Action: Please check at least one data server for the data source to be registered
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00014: Error registering the data source

Cause: An error while registering the source system entered

Action: Modify the actionListener for registering the source system to handle the error
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00015: Error editing the data source

Cause: An error occurred while editing the source system entered

Action: Modify the actionListener for editing the source system to handle the error
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00016: Missing target domain

Cause: Target domain not specified in domain mapping pair task parameter

Action: Please specify target domain
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00017: Missing source domain

Cause: Source domain not specified in domain mapping pair task parameter

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00018: Missing domain mapping pair

Cause: No source to target domain mappings specified in task parameter

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00019: No valid task parameter received

Cause: Received invalid task parameters. Parameters list is empty or contains invalid values

Action: Unexpected error. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00051: Error adding new conformed domain member

Cause: Attempted to add a new conformed domain member {0}. "{0}" member code already exists

Action: Enter a new conformed domain member code
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00052: Error adding new conformed domain member

Cause: Attempted to add a new conformed domain member {0}. "{0}" member code already exists and is a reserved domain member

Action: Enter a new domain member code
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00053: Invalid data source

Cause: Invalid data source num id: {0}

Action: Ensure selected data source is valid
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00054: Error modifying domain member map

Cause: Could not find existing row with key "{0}"

Action: Unexpected exception. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00055: Unspecified view object

Cause: View object was not specified

Action: Unexpected exception. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00056: Unsupported operation

Cause: Adding new member map for non-range domain is not supported

Action: Verify that source domain's member type is a range. If not, it's a defect as operation is not supported
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00057: Error locating conformed domain code

Cause: The selected conformed domain code {0} was not found

Action: Unexpected exception. Please contact customer support
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00058: Invalid source instance

Cause: Unexpected source instance, selected index "{0}" was not valid

Action: Please verify and re-select a source instance
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00059: Invalid source instance

Cause: Source Instance was not specified

Action: Please specify a source instance
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00060: Invalid source domain member type

Cause: Invalid source domain member type: {0} was found

Action: Unexpected domain member type. Ensure that domain has valid member type: CODE, CODE_MULTI_COL, NUM_RANGE, or ALNUM_RANGE
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00061: Invalid member maps

Cause: Invalid member map(s) found for domain mapping {0} \u27A1 {1}:

Action:
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00062: Invalid member maps

Cause: One or more range value is invalid

Action: Please review and correct the invalid map(s)
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00063: Invalid member maps

Cause: Range start/end was empty

Action: Both start and end range values are required. Please enter both values
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00064: Invalid member range values

Cause: [{0}, {1}]: range end must be greater than range start

Action: Please check and correct the range value to ensure that it is valid
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00065: Invalid member range values

Cause: A gap or overlap between {0} and {1} ranges is not allowed for numeric ranges

Action: Please correct and verify that start value is smaller than end value in a range
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00066: Empty range members

Cause: [{0} \u27A1 {1}]: empty start/end range was not allowed

Action: Please specify both start and end range
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00067: Invalid member range values

Cause: Range start value of {0} range must be greater than range end of {1} range

Action: Please check and correct the range value to ensure that it is valid
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00068: You are updating the value of parameter {0} at a global level. The values of parameters with the same name associated with the Fact Groups or Dimension Groups shown below will also be updated

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00069: You are attempting to update the parameter value of a parameter that is defined as read only. Edit operation is not supported for this parameter

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00070: You are updating the value of parameter {0}. The value of this parameter must be the same for all parameters of the same name associated with the Fact Groups or Dimension Groups shown below. The value of each parameter associated with the Fact Groups or Dimension Groups shown below will be updated

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00071: Domain Code Not Found

Cause: Unexpected null domain code

Action: Check to ensure that current domain code is set internally
Level: 1

Type: WARNING

Impact: Configuration

BIACM-00072: For NUMBER Parameter Data Type (LIST Value Type)\: 1,2,3 For VARCHAR2 Parameter Data Type(LIST Value Type)\: abc,xyx,pqr For VARCHAR2 Parameter Data Type(SINGLE Value Type)\: abc

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00073: Free Form Entry. For Multi Value (List Type) Parameters seperate them with commas. e.g. 1,2,3 (NUMBER data type) and a,b,c (VARCHAR2 data type)

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00074: Enter Numeric Value only

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00075: Free Form Entry

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00076: A change of the Parameter Value requires a restart of the BI Server for the value to become effective

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

BIACM-00077: For NUMBER Parameter Data Type (LIST Value Type)\: 1,2,3 For VARCHAR2 Parameter Data Type(LIST Value Type)\: abc,xyx,pqr For VARCHAR2 Parameter Data Type(SINGLE Value Type)\: abc

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00078: The data source ID number you have entered is already in use by another data source

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00079: Invalid Sign In

Cause: Invalid user ID or password

Action: Try again using correct user ID and password. Letters in user ID and password must be typed using the correct case
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00080: Authorization Error

Cause: Access denied. You do not have permission to access Oracle BI Applications Configuration Manager

Action: Contact your help desk or system administrator to obtain authorization to access this application
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00081: Batch edit error

Cause: no row is selected for batch editing

Action: Please select at least a row and retry
Level: 1

Type: ERROR

Impact: Configuration

BIACM-00082: Sync To Source warning

Cause: Sync To Source will perform the following actions to the target member {0}: insert new target members from the source domain and auto generate 1-1 member maps.

Action: Click OK to continue
Level: 1

Type: WARNING

Impact: Configuration

12 CFGFWK-20836 to CFGFWK-69504

CFGFWK-20836: Test Successful!

Cause: JDBC connection test was successful.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20839: Database Load Successful!

Cause: Database load was successful.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20840: PointBase Server Started...

Cause: PointBase server was started successfully.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20841: PointBase Server Stopped...

Cause: PointBase server stopped.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20842: PointBase Server start up message.

Cause: The PointBase Server instance has been started in the background on port {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-20843: Operations cause server stop.

Cause: Navigating from the panel will cause PointBase server to stop.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24010: Template selected.

Cause: Selecting template {0}:{1} and all its prerequisites.

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24011: Template added.

Cause: Added template {0}:{1}.

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24012: Loaded cell configuration.

Cause: Cell configuration loaded successfully.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24013: Config object has been invalidated.

Cause: This config wrapper object from a previous session has been invalidated.

Action: Create new config object.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24014: Selected template names.

Cause: Currently selected templates are {0}

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24015: Registered Oracle Homes.

Cause: Successfully registered Oracle Homes.

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24016: Assigned successfully.

Cause: Successfully assigned {0}:{1} to {2}

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24017: Unassigned successfully.

Cause: Successfully unassigned {0}:{1} from {2}

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24018: WebSphere configuration saved.

Cause: Successfully saved changes to WebSphere configuration.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24019: Failure occurred in assignment.

Cause: The assign of {0}:{1} to {2} failed.

Action: Check the logs for more information.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24020: Failure occurred in unassignment.

Cause: The unassign of {0}:{1} from {2} failed.

Action: Check the logs for more information.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24021: OracleHelp loaded.

Cause: Successfully loaded OracleHelp.

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24022: Help command for Oracle modules.

Cause: For information on Oracle modules enter 'print OracleHelp.help()'

Action: Information message. No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24023: Applied templates.

Cause: Previously applied templates: {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-24024: Selected templates.

Cause: Currently selected templates: {0}

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

CFGFWK-40317: Invalid "Servers, Clusters and Machines" configuration.

Cause: The "Servers, Clusters and Machines" configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40318: Invalid or missing JDBC datasource connection parameters.

Cause: The JDBC datasource required parameters are invalid or missing.

Action: Correct the datasource connection parameters.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40319: Invalid "JMS" configuration.

Cause: The "JMS" configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40320: Invalid "Security" configuration.

Cause: The "Security" configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40321: Configuration port conflict.

Cause: Duplicate Server listen ports exist in your domain configuration: {0}

Action: Change conflicting ports.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40322: External port conflict.

Cause: Server listen ports in your domain configuration conflict with ports in use by active processes on this host: {0}

Action: Change conflicting ports.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40323: Invalid configuration.

Cause: A section of configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40324: Invalid "JMS" configuration.

Cause: JMSDestination's JNDI names are not unique in same target.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40325: Invalid "JDBC" configuration.

Cause: JDBC JNDI names are not unique in the same target.

Action: Correct the configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40865: The text in the file has changed.

Cause: This file has been modified in the editor, discard changes?

Action: Confirm to discard the changes.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40866: Discard previous changes.

Cause: Discard previously saved changes?

Action: Confirm to discard changes.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40867: Discard the changes.

Cause: Edited file has been modified, discard changes?

Action: Confirm to discard changes.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40868: No system component instance

Cause: You have not created any system component.

Action: Create a system component.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40891: A Custom directory doesn't contain valid JDK.

Cause: Unable to determine if the specified directory contains a valid JDK.

Action: Specify a directory with valid JDK.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40893: Invalid JDK Version.

Cause: The selected JDK version doesn't match the jdk version pattern.

Action: Select a different JDK.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40894: Invalid minimum JDK Version.

Cause: The recommended minimum JDK version doesn't match the JDK version pattern.

Action: Enter a valid JDK directory.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40895: Invalid JDK Version.

Cause: The selected JDK version is lower than recommended minimum version.

Action: Enter a valid JDK directory.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40905: Template exists.

Cause: A template already exists in that location. Do you want to overwrite it?

Action: Select the desired answer.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40906: Not recommended Node Manager configuration

Cause: Oracle recommends using per domain Node Manager configuration. Current selection will cause the configuration of Node Manager for the domain to be skipped.

Action: Continue configuration to skip the current node manager configuration.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40915: JMS system resource selected for conversion to a UDD

Cause: At least one JMS system resource has been selected for conversion to a Uniform Distributed Destination (UDD). This conversion will take place only if the JMS system resource is assigned to a cluster.

Action: Warning message. No action required.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40930: Oracle Home not set

Cause: Oracle Home is not set for the current configuration.

Action: Set Oracle Home.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40931: No domain information.

Cause: Unable to obtain information pertaining to current domain.

Action: Provide domain information.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40950: Reconfiguration template was not available for custom template, and original not found; start scripts may be incomplete

Cause: The custom template at {0} had no corresponding reconfiguration template, and the original template could not be found.

Action: Check start scripts and manually edit to add contributions from the custom template.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-40951: An application or library was not relocated to the new MW home.

Cause: Custom Applications were left in the original MW home and must be fixed manually: {0}

Action: Correct source path of the applications to refer to the new installation.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42001: Configuration conflicts detected.

Cause: Duplicate elements were found in configuration: {0}

Action: No action required. Elements from an incoming template will be discarded.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42057: No templates installed.

Cause: Installation contains no standard templates.

Action: Check installation or use custom template if available.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42061: Configuration component conflict detected.

Cause: The selected template contains a component already defined in the existing domain.

Action: Indicate how to resolve this conflict.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42062: Unable to select template.

Cause: The {0} template could not be selected because of the following: {1}.

Action: Fix the problems which prevented template selection, then try again.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42063: Unable to unselect template.

Cause: The {0} template could not be unselected because of the following: {1}.

Action: Fix the problems which prevented template unselection, then try again.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42064: Hidden selected templates.

Cause: One or more of the templates you selected are no longer visible in the list of Available Templates. To see all the templates you selected, select All Templates from the Template Categories menu.

Action: Select "All Templates" from the Template Categories menu.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42065: Missing driver classes.

Cause: The driver classes listed below were not found in the product installation: {0} A test will not be performed for any database connections using these drivers.

Action: Provide driver class.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42066: Missing driver class.

Cause: The driver class listed below was not found in the product installation: {0} A test will not be performed for any database connections using this driver.

Action: Provide driver class.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42067: The JDBC configuration test did not fully complete or completed with errors.

Cause: You can click "Next" to bypass the testing.

Action: Go back to the previous panels to fix the problems.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-42068: The schema component data are not bound or the binding operation is unsuccessful with errors.

Cause: Error message: {0}.

Action: Enter the correct database connection parameters.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44003: Oracle Products not found.

Cause: No Oracle Products found in WebSphere profile.

Action: Add Oracle Products in profile.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44004: No application server node.

Cause: Application server node not found in Deployment manager profile.

Action: Add server node.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44007: Configuration port conflict.

Cause: Duplicate Server listen ports exist in your cell configuration: {0}

Action: Change conflicting ports.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44008: External port conflict.

Cause: Server listen ports in your cell configuration conflict with ports in use by active processes on this host: {0}

Action: Change conflicting ports.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44009: JNDI name conflict.

Cause: Duplicate datasource JNDI names exist in the same scope: {0}

Action: Change conflicting names.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44010: Duplicate elements in the template.

Cause: The following duplicate elements exist in a configuration, discarding new elements from a incoming template: {0}

Action: No action required.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-44011: Application retargeting warning.

Cause: One or more assigned servers have applications targeted to them. The applications will be untargeted from the servers and targeted to the cluster.

Action: Proceed or cancel the operation.
Level: 1

Type: WARNING

Impact: Configuration

CFGFWK-60001: User name contains unsupported characters.

Cause: The user name contains commas, tabs, spaces, or any of the following characters: <>#|&?(){}

Action: Remove unsupported characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60005: Invalid password.

Cause: WebLogic domain requires the password to be minimum 8 characters

Action: Provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60052: Class name contains spaces.

Cause: Space characters are not allowed.

Action: Correct the class name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60055: Duplicated value.

Cause: The property "{0}" value is duplicated.

Action: Remove the duplicates.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60058: Invalid class name.

Cause: The class name must have the format "xxx.xxx.xxx.xxx".

Action: Correct the class name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60062: Additional address disallowed.

Cause: Invalid {0} of {1} "{2}". If "All Local Addresses" is selected, no additional address should be provided.

Action: Remove additional address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60063: No listen address is provided.

Cause: Invalid {0} of {1} "{2}". The list of address is empty.

Action: Provide at least one address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60064: Mismatched passwords.

Cause: The confirmation password does not match the entered password.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60150: Servers port conflict.

Cause: The server "{0}" has the same combination of listen address and port as server "{1}".

Action: Select different port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60151: SSL port conflict.

Cause: The server "{0}" has the same combination of listen address and SSL port as server "{1}".

Action: Select different SSL port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60152: Admin port conflict.

Cause: The server "{0}" has the same combination of listen address and port as admin server.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60153: Admin SSL port conflict.

Cause: The server "{0}" has the same combination of listen address and SSL port as admin server.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60154: Server port conflict.

Cause: The server "{0}" has the same port and SSL port.

Action: Set one of the ports to a different value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60155: Empty Listen Port.

Cause: Server "{0}" Listen Port is empty.

Action: Set Listen Port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60156: IP v6 address in a wrong format.

Cause: The IP address must have the proper v6 format like "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx" or "xxxx:xxxx:xxxx:xxx:xxx.xxx.xxx.xxx" or other supported format.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60157: IP address in a wrong format.

Cause: The IP address must have the format "xxx.xxx.xxx.xxx".

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60158: Invalid IP address segment.

Cause: Each segment of the IP address must contain an integer in the range of 0 to 255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60159: Invalid IP address segment.

Cause: Each segment of the IP address must contain an integer in the range of 0 to 255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60160: Multicast IP address out of range.

Cause: The IP multicast address must be in the range of 224.0.0.1 to 239.255.255.255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60161: Invalid host name.

Cause: The host name does not allow leading or trailing dot (.).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60162: Invalid host name.

Cause: The host name does not allow multiple dots (.).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60163: Invalid host name.

Cause: No member of the hostname may begin or end with a dash (-).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60164: Invalid host name.

Cause: The entered value is not a valid hostname. Please use only alphanumeric characters and dot (.) and dash (-).

Action: Correct the host name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60165: Invalid domain label.

Cause: The right most domain label can never start with a digit.

Action: Correct the domain label.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60166: Invalid address format.

Cause: Each entry must be expressed as <hostname> or <hostname>:<port>.

Action: Correct the hostname and port format.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60167: Invalid port.

Cause: The port number must be an integer.

Action: Correct the port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60168: Invalid port.

Cause: The port number must be an integer in the range of 1 to 65535.

Action: Correct the port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60169: Conflicting multicast ports.

Cause: The cluster has the same combination of multicast address and port as other cluster.

Action: Change address or port for one of the clusters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60170: Invalid multicast port.

Cause: Multicast port cannot be empty.

Action: Provide valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60171: Conflicting machine definitions.

Cause: The machine "{0}" has the same combination of listen address and port as other machine "{1}".

Action: Change one of machine definitions.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60172: Invalid listen port.

Cause: Listen port cannot be empty.

Action: Provide valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60173: Port conflict.

Cause: The admin server listen address "{0}" and port "{1,number,#}" conflicts with ports in use by existing processes on current host.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60174: SSL port conflict.

Cause: The admin server SSL listen address "{0}" and port "{1,number,#}" conflicts with ports in use by existing processes on current host.

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60175: Empty SSL Listen Port.

Cause: Server "{0}" SSL Listen Port is empty.

Action: Set SSL Listen Port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60176: Invalid IP address segment.

Cause: Invalid {0} of {1} "{2}". Please enter a valid hostname or IP address. Note that if you are entering a IP address, Each segment of the IP address must contain an integer in the range of 0 to 255.

Action: Correct the IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60177: System component type is not specified.

Cause: System component type can not be empty.

Action: Enter a valid system component type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60178: Only system component types "{0}" are supported.

Cause: Only system component types "{0}" are supported.

Action: Enter a valid system component type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60179: Invalid OHS instance name "{0}".

Cause: The following OHS instance names are not valid, regardless of lower or upper case: "mbeans", "domain_bak", "instances", "AdminServer", "AdminServerTag".

Action: Enter a valid OHS instance name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60180: Invalid OHS instance name "{0}".

Cause: OHS instance names must begin with an alphabetic character, contain only alpha-numerics, underscores, and hyphens, and be no more than 30 characters long.

Action: Enter a valid OHS instance name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60200: Invalid targeting for distributed destination.

Cause: The targets of the distributed destination should cover all the servers that host the members.

Action: Include the missing servers.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60201: The distributed topic is not deployed.

Cause: The distributed topic "{0}" that distributed topic member "{1}" belongs to is not deployed.

Action: Deploy the distributed topic.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60202: The JMS server is not deployed.

Cause: The JMS Server "{0}" that topic "{1}" belongs to is not deployed.

Action: Deploy the JMS server.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60203: The distributed queue is not deployed.

Cause: The distributed queue "{0}" that distributed queue member "{1}" belongs to is not deployed.

Action: Deploy distributed queue.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60204: The JMS server is not deployed

Cause: The JMS Server "{0}" that queue "{1}" belongs to is not deployed.

Action: Deploy the JMS server.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60205: Empty group with Admin role.

Cause: Group(s) assigned to "Admin" role must contain at least one user.

Action: Add user to group.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60206: Unassigned Admin role.

Cause: Admin role must be assigned at least one group or one user.

Action: Assign Admin role to a group or a user.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60209: JDBCConnectionPool undeployment failure.

Cause: The JDBCConnectionPool "{0}" could not be undeployed from target "{1}", because it is used by the JMSJDBCStore "{2}", which is used by the deployed JMSServer "{3}".

Action: Switch JMSJDBCStore to use a different JDBCConnectionPool.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60250: Duplicate JNDI name.

Cause: The JNDI name is duplicated in JMS server "{0}"

Action: Choose a different JNDI name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60300: Domain name missing.

Cause: Domain name is not specified.

Action: Specify the domain name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60301: Domain name conflict.

Cause: The name of the WebLogic domain and the server and cluster names within it must be unique. A server or cluster already exists with the WebLogic domain name you specified.

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60302: Domain already exists.

Cause: A domain already exists at the specified location.

Action: Change the domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60303: Domain directory is not empty.

Cause: The domain directory "{0}" you specified contains files. You may only create a domain in an empty directory.

Action: Pick a different domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60304: Applications directory is not empty.

Cause: The applications directory "{0}" that you specified contains files. Applications may only be written to an empty directory.

Action: Pick a different directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60305: Invalid domain name.

Cause: The specified domain name is invalid. It must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and contain at least one letter but must not start with a number.

Action: Correct the domain name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60306: Domain location contains spaces.

Cause: The domain location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60307: Domain location is missing.

Cause: The domain location is not be specified.

Action: Specify the domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60308: Domain location not writable.

Cause: The domain location does not have write permission.

Action: Correct permissions or select different domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60309: Applications location contains spaces.

Cause: The applications location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60310: Applications location missing.

Cause: The applications location is not specified.

Action: Specify applications location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60311: Applications location not writable.

Cause: The applications location does not have write permission.

Action: Correct permissions or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60312: Template name missing.

Cause: Template name is not specified.

Action: Specify the template name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60313: Invalid template name.

Cause: The specified template name is invalid. It must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and contain at least one letter or digit.

Action: Correct the template name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60314: Template location contains spaces.

Cause: The template location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60315: Template location missing.

Cause: The template location is not specified.

Action: Specify template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60316: Template location not writable.

Cause: The template location does not have write permission.

Action: Correct permissions or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60317: The name of the domain, server or cluster names must be unique.

Cause: A domain or cluster already exists with the Server name.

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60324: Location is not a directory.

Cause: The given location is not a directory.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60325: Invalid location.

Cause: The directory location is invalid.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60326: Invalid directory location.

Cause: The specified directory location is invalid. It must include only alphanumeric characters, hyphens ('-') or underscore characters ('_') and contain at least one letter or digit.

Action: Correct the location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60327: Location is missing.

Cause: Location is not provided.

Action: Specify the location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60328: Invalid applications directory.

Cause: The applications location is not a directory.

Action: Provide a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60329: Missing KeyStore password.

Cause: The following templates require entry of a KeyStore password:

Action: Set password for affected templates.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60330: KeyStore information missing.

Cause: Some of the added template require KeyStore information.

Action: Use the storeKeyStorePassword(template_location, password) command for each template listed above to enter required KeyStore passwords. The command must be entered after adding templates and before updating the domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60331: The domain location path is not absolute.

Cause: The path of the domain location field is not absolute.

Action: Correct path or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60332: The application location path is not absolute.

Cause: The path of the application location field is not absolute.

Action: Correct path or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60333: Node Manager location contains spaces.

Cause: The Node Manager location contains spaces.

Action: Remove space characters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60334: Node Manager location is missing.

Cause: The Node Manager location is not be specified.

Action: Specify the Node Manager location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60335: The Node Manager location path is not absolute.

Cause: The path of the Node Manager location field is not absolute.

Action: Correct path or select different location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60336: Location is not a directory.

Cause: The given location is not a directory.

Action: Provide a valid location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60337: Node Manager location not writable.

Cause: The Node Manager location does not have write permission.

Action: Correct permissions or select different domain location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60450: Attempt to delete admin user.

Cause: The default admin user could not be deleted.

Action: Operation aborted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60451: Attempt to add restricted groups.

Cause: Cannot add built-in groups "everyone" or "users".

Action: Operation aborted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60452: Missing roles.

Cause: Built-in roles "Admin" and "Anonymous" must be provided.

Action: Provide required roles.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60453: Password too short.

Cause: The supplied user password for "{0}" is too short.

Action: Provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60454: Password too short.

Cause: The supplied user password for "{0}" is too short.

Action: Provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60455: Invalid password.

Cause: The password must be at least 8 alphanumeric characters with at least one number or special character.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60456: Invalid or missing credentials configuration.

Cause: The credentials configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60457: Invalid or missing keystore configuration.

Cause: The keystore configuration in your domain is invalid.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60550: Script execution aborted.

Cause: Encountered error: "{0}". Error is logged to "{1}".

Action: See log for details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60600: Missing domain security.

Cause: Before booting this domain, it is necessary to run the SQL file located at {0} in order to initialize a domain security admin user in the database.

Action: Execute the SQL file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60707: Template already selected.

Cause: The template "{0}" is already selected.

Action: No action required. The template is ignored.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60800: Bad Template

Cause: There is a problem with the template

Action: Correct the template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60802: Mutually exclusive options.

Cause: "{0}" and "{1}" are exclusive options of {2}.

Action: Remove one of the mutually exclusive options.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60803: Node does not exist.

Cause: The node "{0}" does not exist.

Action: Provide valid node.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60804: Server already exists.

Cause: The server "{0}" already exists.

Action: Provide new server.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60805: Cell location failed.

Cause: Unable to locate cell.

Action: Provide valid cell location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60806: Error when generating log file

Cause: The Configuration Wizard was unable to generate the log file located at

Action: Check the log file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60807: Bus member creation failed.

Cause: Failed to create busMember {0}

Action: Check logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60808: Unsupported Domain

Cause: Only domains associated with Oracle Home {0} are eligible for update..

Action: Select a domain from the currently active middleware home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60809: Invalid Datasource.

Cause: Datasource provider was not found for {0}

Action: Provide valid Datasource.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60810: Server not found.

Cause: Deployment Manager server not found.

Action: Check the cell configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60811: Resource Adapter not found.

Cause: Relational Resource Adapter not found.

Action: Check logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60812: Copied operation failed.

Cause: Unable to copy Relational Resource Adapter to dmgr.

Action: Check logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60813: Server does not exist.

Cause: The server "{0}" does not exist.

Action: Provide valid server information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60814: Cluster does not exist.

Cause: The cluster "{0}" does not exist.

Action: Provide valid cluster information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60815: Unsupported property.

Cause: The property "{0}" is not a supported attribute of the {1} type.

Action: Correct the property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60825: Error in HTTP proxy Application

Cause: Unable to create HTTP proxy application(s)

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60826: Existing Proxy

Cause: You have chosen a managed server {0} which is already a proxy for a cluster.

Action: It is recommended that a managed server only proxy a single cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60827: Invalid Host name or IP address for managed Server

Cause: The managed server {0} chosen as a HTTP proxy for the cluster has an invalid Host name or IP address.

Action: The managed server should have a valid host name or an IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60828: Invalid Host name for Server

Cause: The server {0}, which is assigned to the cluster {1} has an invalid Host name or IP address.

Action: The Listen Address for all servers in a cluster with an HTTP proxy should be a valid host name or an IP address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60829: Invalid managed Server

Cause: The managed server with the server Name {0} chosen as a HTTP proxy for a cluster does not exist.

Action: The managed server should exist and be valid.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60830: No file to load.

Cause: There must be files to load.

Action: Provide file to load.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60831: No file selected.

Cause: You must select a file first.

Action: Select a file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60834: Invalid URL.

Cause: The URL entered may not end with forward slash ("/").

Action: Modify the URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60835: Invalid URL.

Cause: The URL entered was malformed: {0}

Action: Modify the URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60837: Test failed.

Cause: Test Failed!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60838: Error in connection.

Cause: Error getting connection information!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60839: Failed to load database.

Cause: Database Load Failed!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60840: Error in PointBase server startup.

Cause: Error encountered starting PointBase server or the server process was killed!

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60841: Log path.

Cause: For possible information regarding the error check the log located at:

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60842: Error in stopping PointBase server.

Cause: Error encountered stopping the PointBase server! Check log file:

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60843: Error in writing log file.

Cause: Error Writing Log File:

Action: Check the log.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60855: Invalid Template Name.

Cause: The Template Name is blank.

Action: Enter a valid Template Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60856: Invalid Template Version.

Cause: The Template Version is blank.

Action: Enter a valid Template Version.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60857: Invalid Template Version Number.

Cause: The Template Version Number is invalid. It should be in the format N.N.N.N.N or N.N.N.N where N is a whole number.

Action: Enter a valid Template Version Number.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60865: Can not edit the file.

Cause: This file type is not editable

Action: Provide writable permission to file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60870: Invalid start or end character for path.

Cause: Path cannot start or end with a path separator.

Action: Remove the path separator at the start or end
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60875: Invalid selection for removal

Cause: The selected directory is a representation of a location that will be selected by the user when using this configuration and cannot be removed.

Action: Select another file or directory to remove
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60876: Invalid selection for removal

Cause: You cannot remove the files in red or their parent directories because they comprise this configuration's applications.

Action: Select another file or directory to remove
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60877: No file selected to be removed

Cause: You must first select a file to remove.

Action: Select a file to be removed
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60878: Not selected Source file or directory

Cause: You must select a source file or directory on the left

Action: Select a valid source file or directory
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60879: Invalid destination location

Cause: You must select a destination location on the right

Action: Select a destination location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60880: Invalid selection

Cause: The selected directory is a representation of a location that will be selected by the user when using this configuration and files cannot be added.

Action: Select another destination file or directory
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60881: Invalid selection

Cause: The selected file cannot be added to your domain directory because it is a reserved file. This usually means that the file will be auto-generated by the configuration wizard and does not need to be added.

Action: Select a different file or directory
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60882: Error reading template location.

Cause: The template location {0} cannot be read due to an unexpected I/O error.

Action: Verify template location is a valid one.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60885: Error preparing the template

Cause: Error encountered preparing template from jar

Action: Check the jar file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60891: A Custom directory doesn't contain valid JDK.

Cause: Unable to determine if the specified directory contains a valid JDK. Do you want to proceed?

Action: Specify a directory with valid JDK.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60892: Invalid directory location

Cause: The specified directory does not exist.

Action: Enter a valid JDK directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60900: No file selected

Cause: No file was selected to be moved up

Action: Select a file to be moved up
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60901: No file selected

Cause: No file was selected to be moved down

Action: Select a file to be moved down
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60905: Password mismatch.

Cause: Password does not match.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60906: Empty field.

Cause: The field {0} cannot be empty.

Action: Provide field value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60907: Invalid field value.

Cause: The field {0} must be an integer.

Action: Provide integer value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60908: Empty password field.

Cause: The password/confirm password field is empty.

Action: Provide value for password/confirm password field.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60909: Password does not match.

Cause: The password entered should match the confirm password field.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60915: Invalid custom directory.

Cause: A Custom directory is not empty.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60916: Invalid node manager home

Cause: The node manager home is not a directory.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60918: Invalid user name

Cause: The user name can not be empty.

Action: Specify a valid user name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60919: Invalid SSL Listen Port.

Cause: SSL Listen Port of Server "{2}" is empty.

Action: Provide SSL Listen Port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60920: The name of the domain, server or cluster names must be unique.

Cause: A domain or server already exists with the Cluster name "{2}".

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60921: The name of the domain, server or cluster names must be unique.

Cause: A domain or cluster already exists with the Server name "{2}".

Action: Change the name of the domain, conflicting server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60922: Invalid port value.

Cause: The listen port value {3,number,#} of {1} "{2}" is out of range. It must be between 1 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60923: Invalid port value.

Cause: The SSL listen port value {3,number,#} of Server "{2}" is out of range. It must be between 1 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60924: Invalid value of "{0}" property.

Cause: Property "{0}" of {1} "{2}" is invalid. The name must not be null or empty and may not contain any : , = * ? % _cloned.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60925: Invalid port value.

Cause: The coherence listen port value {1,number,#} of cluster "{0}" is out of range. It must be between 0 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60926: Invalid port value.

Cause: The listen port value {3,number,#} of node manager for machine "{2}" is out of range. It must be between 1 and 65534.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60927: Invalid port value.

Cause: The coherence listen port value {1,number,#} of cluster "{0}" is invalid. It must be between 0 and 65535.

Action: Enter a valid port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60928: Invalid existing node manager home directory.

Cause: Existing node manager home directory does not exist or is not accessible.

Action: Specify a valid directory or check permissions if it is not accessible.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60930: Failed to select template. Please run with logging turned on.

Cause: There may be issues with the template(s) and/or with the template location(s).

Action: Fix template(s) and/or provide correct template location(s).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60931: Failed to process database information.

Cause: Failed to process database information.

Action: Fix db info in the template(s).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60932: Invalid listen port.

Cause: Port number must be between 1 and 65535, and different from SSL listen port and coherence port.

Action: Fix the listen port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60933: Invalid ssl port.

Cause: Port number must be between 1 and 65535, and different from listen port and coherence port.

Action: Fix the ssl port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60934: Invalid coherence port.

Cause: Port number must be between 1 and 65535, and different from listen port and SSL listen port.

Action: Fix the coherence port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60935: Failed to select template.

Cause: Please see the log file {0} for details.

Action: Fix template(s) and/or its location in the configuration file. Also check the validity of the configuration xml file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60950: Required template not found in new installation directory

Cause: A template that was required for the reconfiguration could not be found in the upgraded MiddleWare home: {0}

Action: Install the products containing the required template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60951: Failed to load reconfiguration template

Cause: The reconfiguration template {0} failed to load due to invalid meta-data

Action: Correct the template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60952: Failed to load replacement template

Cause: Unable to load the template {0}

Action: Correct the template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60953: An application or library was not relocated to the new MW home.

Cause: An error in the reconfiguration templates resulted in the following deployments being left in the original MW home: {0}

Action: Correct the reconfiguration templates
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60954: A reconfiguration template cannot be the replacement for another reconfiguration template

Cause: The reconfiguration template {0} specified another reconfiguration template {1} as its replacement. The replacement must be either an extension or domain template.

Action: Correct the reconfiguration template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60955: Unable to locate the WebLogic Server component.

Cause: The domain did not contain component references corresponding to known WebLogic Server components

Action: None; the domain cannot be reconfigured
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60956: Unable to locate the certifiate.

Cause: The certificate does not exist at given location {0}.

Action: Browse or provide the proper certificate location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60957: Unable to locate the private key file.

Cause: The private key file does not exist at given location {0}.

Action: Browse or provide the proper private key file location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60958: The empty password is not allowed.

Cause: The password is not provided.

Action: Provide the valid password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60959: Unable to locate the certifiate.

Cause: The certificate does not exist at given location {0}.

Action: Browse or provide the proper certificate location
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-60970: Reconfigured domain had template dependency conflicts

Cause: Invalid reconfiguration templates left the domain in an invalid state.

Action: Correct the reconfiguration templates
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61000: Failed to create CAM instance.

Cause: An error occured while generating a CAM instance.

Action: Check the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61001: Invalid system component schema with details

Cause: An error occurred while validating the schema for System Component. {0}

Action: Set all the required properties for system component.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61010: The entered Domain Frontend URL is invalid.

Cause: An error occured while validating the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61011: The Domain Frontend URLs could not be set in ConfigMapping

Cause: The Frontend host were not set in Config Mapping.

Action: Please check log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61012: The Schema entered for Domain Frontend URL is invalid.

Cause: An error occured while validating the Schema for the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61013: The entered Address for Domain Frontend URL is invalid.

Cause: An error occured while validating the Address for the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61014: The entered Port for Domain Frontend URL is invalid.

Cause: An error occured while validating the Port for the URL {0}

Action: Please enter a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61015: The url for the field cannot be null or empty

Cause: An error occured while validating the URL. The URL cannot be Null or empty.

Action: Please enter an URL.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61020: Frontend HTTP/HTTPS Port has been entered, but Frontend Host is missing.

Cause: Frontend Host is empty.

Action: Enter a valid Frontend Host address.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-61021: Frontend Host has been entered, but Frontend HTTP/HTTPS Port is missing.

Cause: Frontend HTTP/HTTPS Port is empty.

Action: Enter a valid Frontend HTTP/HTTPS Port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64001: Property value is not part of enumerated values.

Cause: According to the XML schema, the value for property {0} of {1} must be one of the following: {3}.

Action: Use one of the valid values.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64002: Invalid property value.

Cause: The value "{3}" for property "{0}" of {1} {2} did not pass XML schema validation: {4}.

Action: Provide valid value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64009: The "{0}" property is missing.

Cause: "{0}" is empty. It must be set on the {1} objects. The name must not be null or empty.

Action: Provide a name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64010: Invalid property value.

Cause: Property "{0}" of {1} "{2}" is invalid.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64012: Invalid property value.

Cause: Property "{0}" of {1} "{2}" is invalid. Space characters are not allowed.

Action: Provide valid property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64013: Internal representation conversion error.

Cause: The string cannot be converted.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64014: The required property is missing.

Cause: Invalid property "{0}" of {1}: value "{2}" is invalid. The property value is required.

Action: Provide property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64015: Duplicated property.

Cause: Invalid property "{0}" of {1}: value "{2}" is invalid. The property value is duplicated.

Action: Correct the property value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64016: Attempt to set disabled property.

Cause: The property "{0}" is disabled on type {1}.

Action: Internal error. No user actions available.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64017: Attempt to set unsupported property.

Cause: The property "{0}" is not supported on type {1}.

Action: Internal error. No user actions available.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64018: Mismatched password values.

Cause: The password value does not match the confirmation password.

Action: Correct password values.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64019: The "{0}" property is missing.

Cause: "{0}" is empty. It must be set on the {1} objects. The name must not be null or empty and should contain valid characters only.

Action: Provide a name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64020: The file "{0}" does not exist or is not a file.

Cause: "{0}" does not exist or is not a file.

Action: Provide a file name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64021: Fatal internal error.

Cause: An unexpected internal condition was detected: {0}. The wizard cannot continue.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64022: Unspecified error.

Cause: One of the subsystems generated an error: {0}

Action: Check error text for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64023: The file "{0}" does not have permission to read.

Cause: "{0}" does not have permission to read.

Action: Provide a read permission.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64024: The file "{0}" does not have permission to write.

Cause: "{0}" does not have permission to write.

Action: Provide a write permission.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64025: Maximum number of entries reached.

Cause: At most {0} entries can be created.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64026: Maximum number of entries reached.

Cause: At most 1 entry can be created.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64027: Minimum number of entries not reached.

Cause: At least {0} entries must be provided.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64028: Minimum number of entries not reached.

Cause: At least 1 entry must be provided.

Action: Operation aborted; no further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64029: Can not remove entry.

Cause: Disabled entry may not be removed.

Action: Removal aborted. No user actions available.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64030: The target file must be specified.

Cause: The target file must be specified.

Action: Provide a target file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64031: The service-id and service-type both are required for the service type "NEW".

Cause: The service-id and service-type both are required for the service type "NEW".

Action: Provide a service-id and service-type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64032: The output-date-target element must be specified.

Cause: The output-date-target element must be specified.

Action: Provide a output-date-target element.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64033: The invalid input-data-src type specified.

Cause: The invalid input-data-src type specified.

Action: Provide a valid input-data-src type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64034: The target xpath for a token bind or target-key for an xml bind is not applicable.

Cause: The target xpath for a token bind or target-key for an xml bind is not applicable.

Action: Provide a target-key for a token bind or target-xpath for an xml bind.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64035: Multiple assignment to target.

Cause: The {0} "{1}" could not be assigned to the target "{2}" since each target can have only one {0} assigned.

Action: Change the assignment.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64036: The invalid app-svc-name "{0}" is defined.

Cause: The invalid app-svc-name "{0}" is defined.

Action: Provide a valid app-svc-name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64037: The invalid FEHost Address type "{0}" is defined.

Cause: The invalid FEHost Address type "{0}" is defined.

Action: Provide a valid FEHost Address type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64038: The app-svc-name "{0}" must have target.

Cause: The app-svc-name "{0}" must have target.

Action: Provide a valid target.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64040: Invalid template location.

Cause: Specified template does not exist or is not a file: "{0}".

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64041: Invalid template.

Cause: Template "{0}" is not a valid jar file.

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64042: Invalid template.

Cause: Template "{0}" does not contain template-info.xml.

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64043: Invalid template.

Cause: template-info.xml could not be parsed: {0}

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64044: Invalid template.

Cause: XML schema validation failed for template-info.xml: {0}

Action: Provide a valid template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64045: Unable to save template-info.

Cause: Encountered error while saving template-info.xml: {0}

Action: Check generated exception for details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64050: Invalid location

Cause: No template was selected

Action: Select a valid template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64051: Invalid location.

Cause: The selected location does not contain WebLogic domain.

Action: Select a valid domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64052: Invalid configuration

Cause: This is not a valid configuration! Correct the following error in config.xml: {0}

Action: Correct config.xml
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64053: Domain loading error.

Cause: The Configuration Wizard encountered problems attempting to load the domain you selected: {0}.

Action: Select a different domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64054: Unsupported domain.

Cause: The domain in this directory is not a supported version.

Action: Select a different domain.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64055: Invalid template extension.

Cause: Template destination is not having a valid extension.

Action: Correct the template destination extension to .jar.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64056: Error adding templates.

Cause: The Configuration Wizard encountered problems attempting to add templates you selected: {0}.

Action: Verify template integrity or select different templates.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64058: Incompatible templates.

Cause: Some of the extension templates you have selected are incompatible with each other due to conflicting application and/or service names.

Action: Modify template selection.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64059: Unsatisfied conditions.

Cause: The template you selected cannot be applied because the following conditions have not been satisfied: {0}

Action: Select "Yes" to override these conditions (Not Recommended).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64062: Invalid template.

Cause: Domain template "{0}" could not be loaded: {1}

Action: Select a valid domain template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64063: Missing config.xml in template

Cause: The config.xml is invalid or missing in the template selected

Action: Select a valid template
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64064: No domain template in selection.

Cause: Selection must contain at least one domain template. Currently selected templates are defined as extension templates and do not express a dependency on a domain template.

Action: Include domain template into your selection.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64065: No templates added.

Cause: At least one template needs to be added to configuration.

Action: Add a template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64066: Template location is missing.

Cause: Template location is not provided.

Action: Specify template location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64067: Invalid template.

Cause: Only Oracle product templates from the Oracle Home already associated with this domain are eligible for selection.

Action: Select a template associated with the current Oracle Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64069: Missing template prerequisites.

Cause: The following prerequisites could not be satisfied: {0}

Action: Verify that prerequisite templates are present or change your selection.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64070: Template conflict.

Cause: The following templates are both prerequisites and conflicts for the current selection: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64071: Template conflict.

Cause: The selection conflicts with templates already present in the domain: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64072: Ambiguous prerequisite.

Cause: There are multiple matches for one of the prerequisites specified by a template. Resolve the ambiguity by preselecting one of the choices before attempting selection: {0}

Action: Select the desired prerequisite.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64073: Non-selectable template.

Cause: The template is not selectable in the current mode.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64074: Missing template.

Cause: The template is not available.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64075: Template is configured.

Cause: The template was previously configured.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64076: Template already selected.

Cause: The template is already selected.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64077: Template already unselected.

Cause: The template is already unselected.

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64078: Template selection error.

Cause: Encountered error during selection operation: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64079: Template conflict.

Cause: The selection requires tempaltes which conflicts with the current domain: {0}

Action: Selection is reverted. No further actions required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64085: Directory not selected.

Cause: A directory was not set.

Action: Select a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64100: Invalid help topic.

Cause: No such help topic exists.

Action: Provide valid help topic.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64101: Help is not configured

Cause: No Help configuration found.

Action: Configure help.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64102: Invalid help type.

Cause: Help type not supported.

Action: Provide the valid help type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64103: Failed to load help.

Cause: Errors occurred while loading Help.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64104: Low console width.

Cause: Value of console width is too low!

Action: Increase the console width.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64200: No common database driver.

Cause: The selected data sources do not share any common database drivers. The wizard will deselect data sources to allow selection of compatible drivers.

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64201: No common database driver.

Cause: The selected component schemas do not share any common database drivers. The wizard will deselect component schemas to allow selection of compatible drivers.

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64204: Validation errors.

Cause: Some more validation errors occurred.

Action: Correct validation errors.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64205: Unspecified property.

Cause: The {0} must be specified.

Action: Specify the property.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64206: Unspecified properties.

Cause: The following must be specified: {0}

Action: Provide missing properties.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64207: Mismatched passwords.

Cause: The {0} and {1} do not match.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64208: Invalid value.

Cause: The {0} must be an integer.

Action: Provide integer value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64209: Test Canceled!

Cause: You have cancelled the connection test.

Action: No further action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64210: Test Failed!

Cause: JDBC connection test failed.

Action: Check logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64211: Test Failed!

Cause: Error getting connection information!

Action: Provide connection details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64212: No rows returned.

Cause: A connection was established to the database but no rows were returned from the test SQL statement.

Action:
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64213: Test Successful!

Cause: JDBC connection test was successful.

Action: No action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64215: There are no data sources selected.

Cause: Detected that there are no data sources selected.

Action: Select the data sources that you want to test.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64216: Data source {0} connection test failed.

Cause: Error message: {0}

Action: Go to previous panels to fix the problem and test it again.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64217: JDBC data source validations failed.

Cause: Error message: {0}

Action: Go to previous panels to fix the problem and test it again.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64218: Server configuration validations failed.

Cause: For instance {0}, valid input value for {1} must be specified,

Action: Enter the required values.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64219: Failed to bind the schema component data

Cause: Error message: {0}.

Action: Enter the correct database connection parameters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64220: CopyFileDefinition validations failed.

Cause: The duplicate copy file definition name across multiple templates : {0}.

Action: Each copy file definition must be defined with an unique name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64221: DeleteFileDefinition validations failed.

Cause: The duplicate delete file definition name across multiple templates : {0}.

Action: Each delete file definition must be defined with an unique name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-64222: CopyFileDefinition source exists validations failed.

Cause: The source location does not exist for the copy definition.

Action: Correct the copy definition in the template to refer to a valid source location.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68001: Duplicate Server listen ports exist in the cell configuration.

Cause: Duplicate Server listen ports exist in the cell configuration.

Action: Remove Duplicate Server listen ports which exist in the cell configuration.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68004: Select a Profile.

Cause: No Profile is selected.

Action: Select a Profile.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68006: Common Host for all End Points is empty or left blank.

Cause: The common host for all end points can not be left blank.

Action: Specify common host for all end points.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68007: Port value is empty or left blank.

Cause: The port value can not be left blank.

Action: Specify a port value.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68008: Selected path should be an existing Path in WebSphere Home..

Cause: Selected Path not found.

Action: Select an existing Path in WebSphere Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68009: Selected Path should be a WebSphere Installation Folder.

Cause: Selected Path is not a WebSphere Installation Folder.

Action: Select a WebSphere Installation Folder.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68010: Invalid password.

Cause: The password must be at least 8 alphanumeric characters with at least one number or special character.

Action: Correct the password.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68011: Deployment Manager Administrator User Name is Empty.

Cause: Deployment Manager Administrator User Name was left blank.

Action: Enter a Deployment Manager Administrator User Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68012: Deployment Manager Administrator User Name is invalid.

Cause: Deployment Manager Administrator User Name was invalid.

Action: Enter a valid Deployment Manager Administrator User Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68013: Deployment Manager Administrator Password is Empty.

Cause: Deployment Manager Administrator Password was left blank.

Action: Enter a Deployment Manager Administrator Password. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68014: Deployment Manager Administrator Password is Invalid.

Cause: Deployment Manager Administrator Password must be at least 8 alphanumeric characters with at least one number or special character.

Action: Enter a valid Deployment Manager Administrator Password. It must be at least 8 alphanumeric characters with at least one number or special character.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68015: Deployment Manager Administrator Passwords mismatch.

Cause: Deployment Manager Administrator Passwords do not match.

Action: Deployment Manager Administrator Passwords should match.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68016: Deployment Manager Host Name is Empty.

Cause: Deployment Manager Host Name was left blank.

Action: Enter Deployment Manager Host Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68017: Deployment Manager Host Name is invalid.

Cause: Deployment Manager Host Name was invalid.

Action: Enter a valid Deployment Manager Host Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68018: Deployment Manager Port Name is Empty.

Cause: Deployment Manager Port Name was left blank.

Action: Enter Deployment Manager Port Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68019: Deployment Manager Port Name is invalid.

Cause: Deployment Manager Port Name was invalid.

Action: Enter a valid Deployment Manager Port Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68020: Unable to initialize Security related parameters.

Cause: Security related parameters could not be initialized.

Action: Initialize Security related parameters.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68021: Cell Name is Empty.

Cause: Cell Name was left blank.

Action: Enter a Cell Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68022: Cell Name is invalid.

Cause: Cell Name contains one or more invalid characters.

Action: Enter a valid Cell Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68023: Cell Name conflicts with existing profile in WebSphere Home.

Cause: Selected Cell Name conflicts with existing profile in WebSphere Home.

Action: Enter a Cell Name consistent with existing profile in WebSphere Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68024: Deployment Manager Profile Name is Empty.

Cause: Deployment Manager Profile Name was left blank.

Action: Enter a Deployment Manager Profile Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68025: Deployment Manager Profile Name is invalid.

Cause: Deployment Manager Profile Name contains one or more invalid characters.

Action: Enter a valid Deployment Manager Profile Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68026: Password encryption failed.

Cause: Unable to encrypt password:

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68027: Application Server Name is invalid.

Cause: Application Server Name contains one or more invalid characters.

Action: Enter a valid Application Server Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68028: Port value is out of range(0 to 65535).

Cause: The range of port value {0} is invalid.

Action: The port value must be in range of 0 to 65535.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68029: The port value is not an integer.

Cause: The port value {0} is invalid.

Action: The port value must be integer.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68030: Initialization failed.

Cause: Initialization error: {0}

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68031: Initialization failed.

Cause: The system wasn't initialized properly.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68032: No Python interpreter.

Cause: The python interpreter is not set.

Action: Configure the Python interpreter.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68033: Template catalog creation failed.

Cause: Unable to create template catalog.

Action: Possibly corrupted installation. See log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68034: Template not found.

Cause: Found no templates with {0} name and {1} version

Action: Select a different template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68035: Multiple matching templates.

Cause: Found {2} templates with {0} name and {1} version.

Action: Possibly corrupted installation. Check installation for correctness.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68036: Template loading failed.

Cause: Unable to load template from [{0}].

Action: Provide valid path.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68037: Cell configuration loading failed.

Cause: Unable to load cell configuration.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68038: Template already selected.

Cause: The template "{0}" is already selected.

Action: No action required. The template is ignored.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68039: Selected template conflict.

Cause: The following previously selected templates conflict with the new selection: {0}

Action: Change the template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68040: Templates are not compatible.

Cause: The selected templates are not compatible with each other.

Action: Change the template.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68041: Template addition failed.

Cause: Unable to add template with {0} name and {1} version: {2}.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68042: Failed to save configuration.

Cause: Unable to save configuration.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68043: Scope not found.

Cause: Unknown scope defined: {0}.

Action: Provide valid scope.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68044: File copied failed.

Cause: Unable to copy : {0}

Action: Provide vaild file path.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68045: Cell configuration not loaded.

Cause: Failed to load cell configuration.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68046: Fail to register Oracle home.

Cause: Unable to register Oracle home information : {0}

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68047: Template not selected.

Cause: No templates were selected!

Action: Select templates to load.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68048: Name or Type can not be null.

Cause: The name or type {1}:{0} can not be null.

Action: Provide value for Name or Type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68049: Type not supported.

Cause: The requested type {0} is not supported.

Action: Provide the supported type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68050: Name is not in scope.

Cause: The {0}:{1} was not found in a requested scope {2}.

Action: Provide the valid name or scope.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68051: Port conflict.

Cause: Duplicate Server listen ports exist in your cell configuration: {0}

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68052: Port conflict.

Cause: Server listen ports in your cell configuration conflict with ports in use by active processes on this host: {0}

Action: Select a different port.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68053: Can not modify the property.

Cause: The property {0} is not allowed to be modified.

Action: Use listAttributes() for supported types.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68054: Name not found.

Cause: The {0} with name {1} was not found.

Action: Provide valid name or type.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68055: Property is not supported.

Cause: The property {0} is not a supported type.

Action: Use listTypes() for supported types.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68056: Attribute not supported.

Cause: The property {0} is not a supported attributes.

Action: Use listAttributes() for supported types.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68057: Invalid property.

Cause: The property {0} is not valid.

Action: Use listAttributes() or listTypes() for supported attributes and types.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68059: Delete operation failed.

Cause: The requested {0}:{1} could not be deleted.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68060: Property is read-only.

Cause: The specified property {0} is read-only.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68061: Operation not supported.

Cause: The requested operation is not allowed here.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68062: Operation not supported.

Cause: The specified value {0} is not supported or is invalid!

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68063: Invalid path.

Cause: Path to deployment manager profile is not provided.

Action: Specify path to deployment manager profile.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68064: Invalid value.

Cause: The specified value {0} for {1} is of incompatible type or out of range.

Action: Correct validation error.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68065: JDBC validation failed.

Cause: JDBC datasource validation failed: {0}

Action: Correct validation error.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68066: Type is read-only.

Cause: The specified type {0} is read-only.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68067: Operation not supported.

Cause: The specified operation {0}:{1} is not supported for WebSphere STANDALONE Cell.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68068: Internal validation error.

Cause: Validation failed for: {0}

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68069: Unsupported assignment.

Cause: {0} assignment not supported.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68070: Deployment Manager Profile Name conflicts with existing profile in WebSphere Home.

Cause: Selected Deployment Manager Profile Name conflicts with existing profile in WebSphere Home.

Action: Enter a Deployment Manager Profile Name consistent with existing profile in WebSphere Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68071: Deployment Manager Node Name is Empty.

Cause: Deployment Manager Node Name was left blank.

Action: Enter a Deployment Manager Node Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68072: Deployment Manager Node Name is invalid.

Cause: Deployment Manager Node Name contains one or more invalid characters.

Action: Enter a valid Deployment Manager Node Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68073: Can not read the value.

Cause: The value of attribute {0} is not allowed to be read.

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68074: Exception encountered.

Cause: Error occurred in command execution.

Action: Run OracleMWConfig.dumpStack() to view the full Exception.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68075: Config-groups topology profile has already been set.

Cause: The config-groups topology profile has already been set for this WebSphere profile and cannot be modified.

Action: No action required.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68080: Option map is empty.

Cause: The options map for {0} can not be null.

Action: Provide required options.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68081: Missing option.

Cause: "{0}" is a required option of {1}.

Action: Provide required option.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68082: The IP address v6 format is invalid.

Cause: The v6 format of IP address is invalid.

Action: The IP address must have the proper v6 format like "xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx" or "xxxx:xxxx:xxxx:xxx:xxx.xxx.xxx.xxx" or other supported format.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68083: The IP address v4 format is invalid.

Cause: The v4 format of IP address is invalid.

Action: The IP address must have the proper v4 format like "xxx.xxx.xxx.xxx".
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68084: The integers in IP address are not in valid range.

Cause: The range of integers in IP address is invalid.

Action: Each segment of the IP address must contain an integer in the range of 0 to 255.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68085: The segments of IP address are invalid.

Cause: One or more segments of IP address is not integer.

Action: Each segment of the IP address must contain an integer in the range of 0 to 255.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68086: The IP multicast address is in the invalid range.

Cause: The IP multicast address is not in the valid range.

Action: The IP multicast address must be in the range of 224.0.0.1 to 239.255.255.255.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68087: A leading or trailing dot (.) is present in the host name.

Cause: The host name contains a leading or trailing dot (.).

Action: The host name does not allow leading or trailing dot (.).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68088: Multiple dots (.) are present in the host name.

Cause: The host name contains multiple dots (.).

Action: The host name does not allow multiple dots (.).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68089: Invalid host name.

Cause: One or more member of the hostname begins or ends with a dash (-).

Action: No member of the hostname may begin or end with a dash (-).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68090: The entered value is not a valid hostname.

Cause: The entered value is an invalid hostname.

Action: The entered value is not a valid hostname. Use only alphanumeric characters and dot (.) and dash (-).
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68091: A digit can never be present at the start of the right most domain label.

Cause: The right most domain label starts with a digit.

Action: The right most domain label can never start with a digit.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68092: Invalid hostname or IP address entered.

Cause: Entered hostname or IP address is invalid.

Action: Enter a valid hostname or IP address. Note that if an IP address is entered, each segment of the IP address must contain an integer in the range of 0 to 255.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68093: Deployment Manager Node Name conflicts with existing profile in WebSphere Home.

Cause: Selected Deployment Manager Node Name conflicts with existing profile in WebSphere Home.

Action: Enter a Deployment Manager Node Name consistent with existing profile in WebSphere Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68094: Application Server Name is Empty.

Cause: Application Server Name was left blank.

Action: Enter a Application Server Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68095: Application Server Name is invalid.

Cause: Application Server Name contains one or more invalid characters.

Action: Enter a valid Application Server Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68096: Application Server Name conflicts with existing profile in WebSphere Home.

Cause: Selected Application Server Name conflicts with existing profile in WebSphere Home.

Action: Enter an Application Server Name consistent with existing profile in WebSphere Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68097: Application Server Node Name is Empty.

Cause: Application Server Node Name was left blank.

Action: Enter an Application Server Node Name. It can not be left blank.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68098: Application Server Node Name is invalid.

Cause: Application Server Node Name contains one or more invalid characters.

Action: Enter a valid Application Server Node Name.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68099: Application Server Node Name conflicts with existing profile in WebSphere Home.

Cause: Selected Application Server Node Name conflicts with existing profile in WebSphere Home.

Action: Enter a Application Server Node Name consistent with existing profile in WebSphere Home.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68100: Failed to load OracleHelp.

Cause: Errors occurred while loading OracleHelp.

Action: Check log for details.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68110: Key not found.

Cause: Error obtaining key ({0}) from properties file.

Action: Add the key in property file.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-68111: Invalid prefix.

Cause: Invalid prefix obtained from properties file.

Action: Provide valid prefix.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69500: Command execution failed.

Cause: Attempt to execute command "{0}" in invalid state: {1}

Action: Check the logs for more information.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69501: Method not present.

Cause: The method "{0}" is not available.

Action: Provide valid method.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69502: Target not found.

Cause: Assignment Target not found for type: {0}

Action: Provide valid target.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69503: Target not found.

Cause: Could not find {0} : {1}

Action: Provide valid target.
Level: 1

Type: ERROR

Impact: Configuration

CFGFWK-69504: Invalid Target.

Cause: Invalid Target : {0}

Action: Provide valid target.
Level: 1

Type: ERROR

Impact: Configuration

13 CLONE-20200 to CLONE-92302

CLONE-20200: The clone option or argument is invalid.

Cause: The option or argument "{0}" was not supported by cloning.

Action: Provide a valid option or argument. Use the "-help" option for more information about cloning options and arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20201: The value for the argument is missing.

Cause: The argument "{0}" was provided, but its value was not provided.

Action: Provide the corresponding value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20202: Oracle Home is invalid.

Cause: This Oracle home was not registered with the OraInventory. Unable to find any Oracle home from the OraInventory.

Action: Provide valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20203: Invalid archive location.

Cause: There are six possible causes: 1. Archive path was not provided. 2. Archive path was not an absolute path. 3. Archive path did not exist. 4. Archive path did not point to a file. 5. Archive path did not have read permission. 6. Archive was a zero size file.

Action: Provide the absolute path of a valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20204: Oracle Home is invalid.

Cause: This Oracle home was not registered with the OraInventory. The Oracle homes registered with the OraInventory were : {0} .

Action: Provide valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20205: Oracle Home is invalid.

Cause: This Oracle home was not registered with the OraInventory specified in inventory pointer location file {0}. The Oracle homes registered with that OraInventory were : {1}

Action: Provide valid Oracle Home and make sure that Oracle Home is registered with the OraInventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20206: Invalid value for "{0}" option.

Cause: The provided value was not a Boolean value.

Action: Supported Boolean values are "true" or "false".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20207: Unable to update following property "{0}" in nodemanager.properties file.

Cause: Encryption was unsuccessful.

Action: Update the nodemanager.properties file manually to provide value of property "{0}" in clear text. Then start nodemanager to encrypt the value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20210: The archive file is invalid.

Cause: The archive file failed an internal consistency check.

Action: Make sure that the archive file is created using T2P operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20218: Cloning is not successful.

Cause: An internal operation failed.

Action: Check clone log and error file for detailed information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20219: Clone type is invalid.

Cause: Clone type was either empty or not supported.

Action: The clone type is either "{0}" or "{1}" or "{2}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20220: Parameters are missing.

Cause: Either archiveLocation or cloneType was empty. The values provided were archiveLocation : "{0}" cloneType : "{1}".

Action: Make sure that the correct values are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20221: Invalid clone type.

Cause: The clone type "{0}" did not match "{1}" or "{2}".

Action: The clone type should be either "{0}" or "{1}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20222: Parameters validation has failed.

Cause: Primary parameters validation for "{0}" failed.

Action: Check the clone log and error file and provide correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20223: Invalid Oracle Home.

Cause: There are four possible causes for an invalid Oracle Home "{0}": 1. It did not exist. 2. It was an empty directory. 3. It had invalid inventory pointer file (if operating system is other than Windows). 4. It had no top component or invalid top component version.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20225: Some configuration files have incorrect entry.

Cause: Following files have still reference to source Oracle Home {0} {1}

Action: Update those files with target Oracle Home path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20227: Error in validating T2P binary..

Cause: T2P binary had been compromised.

Action: Make sure that the T2P binaries are valid. Check the T2P documentation for more information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20228: Error in validating archive file.

Cause: Unable to find internal version pertaining to T2P operation from the archive.

Action: Make sure that archive file is valid and correct T2P binaries are used during copy and paste operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20229: Error in validating archive file.

Cause: Archive file had been compromised.

Action: Make sure that the archive file is valid. Check the T2P documentation for more information.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20230: Primary validation prior to clone operation has failed for {0}.

Cause: Parameter(s) were missing or some validation(s) failed.

Action: Check the clone log and error file for information about which parameter is missing or why validation failed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20231: Error in validating archive file.

Cause: The version of archive file and T2P binary were "{0}" and "{1}" respectively. The possible causes were: 1. The major version was mismatched. 2. The minor version of archive file is higher than the minor version of T2P binary used for paste operation.

Action: Make sure that correct T2P binary is used during copy and paste operation.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20232: Oracle Home configuration has failed.

Cause: Exception occurred while configuring Oracle Home.

Action: Check the oraInstaller, cloneAction log and error file for more details. Location of these files can be found from the clone log file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20235: Adding "{0}" to the archive has failed.

Cause: An internal operation failed.

Action: Check the clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20236: Archive creation has failed.

Cause: An internal operation failed.

Action: Check the clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20237: Restoring the sourceid "{0}" has failed.

Cause: An internal operation failed.

Action: Check the clone log for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20238: Restoring the sourceid "{0}" has not completed successfully.

Cause: An internal operation completed with warning.

Action: Check the clone log for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20239: Invalid archive file.

Cause: Either archive did not have sourceid file, or a sourceid was a zero size file.

Action: Make sure the correct archive file is provided, and check the extracted sourceid file whose path is "{0}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20240: Invalid archive file.

Cause: Either archive did not have "{0}" file, or archive was not created through copyConfig operation.

Action: Make sure that the correct archive file is provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20241: Permission of some of the files are not captured.

Cause: Permission of following files were not correct {0}.

Action: Correct permission either at source and run copyBinary again or at traget after pasteBinary.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20242: Permission of some of the files are not captured.

Cause: Permission of following files were not captured because their names were not calculated properly {0}.

Action: Correct permission of the files under those directories at traget after pasteBinary.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20243: Permission of some of the files are not captured.

Cause: Number of fileds in permission details was not {0} for following permission details. {1}.

Action: Correct permission of the files under those directories at traget after pasteBinary.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20245: Unable to include permission file to the archive.

Cause: Permission file creation failed.

Action: Check the clone log and error file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20247: Not all file permission operations are successful.

Cause: Either some files were missing from the Oracle Home {0} or some invalid entry in permission restore file {1}.

Action: Check the clone log file, permission restore log file {0} and permission file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20248: Execution of system prerequisites have failed.

Cause: The following system prerequisites failed : {0}.

Action: Check clone log for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20249: Execution of system prerequisites have completed with warnings.

Cause: The following system prerequisites completed with warnings : {0}.

Action: Check clone log for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20250: Execution of system prerequisites has completed without verifying some of the prerequisites.

Cause: The following system prerequisites were not verified : {0}.

Action: Check clone log for more details on prerequisites output and result.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20251: Execution of system prerequisites failed for some or all of the Oracle Homes.

Cause: Some of the system prerequisites were not completed successfully.

Action: Check the clone logs for more details on the prerequisite output and results. Re-execute the pasteBinary command after either fixing the failing prerequisites or by adding the '-executeSysPrereqs false' parameter to the command line.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20252: Invalid T2P action type.

Cause: The provided action type was "{0}". This action type was either empty or unsupported.

Action: The supported action types are "{0}".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20254: Cloning is not possible..

Cause: The Oracle Home {0} did not have supported binaries. The root causes were :{1}.

Action: Make sure that the Oracle has correct binaries.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20255: Cloning is not possible.

Cause: The Oracle Home name {0} provided in -ouiparam argument was already registered with the Oracle Inventory for Oracle home {1}.

Action: Either provide a different inventory location or provide a different Oracle Home name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20256: Unable to capture permission of all the files present under the Oracle Home.

Cause: Some of the files did not have proper permission.

Action: Check clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20257: Unable to clone the Oracle Home.

Cause: The Oracle Home name "{0}" was already registered with the Oracle Inventory for Oracle Home "{1}".

Action: Either provide a different inventory location or provide a different Oracle Home name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20261: Invalid Oracle Inventory.

Cause: There are six possible causes for an invalid inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.

Action: Provide a valid inventory pointer file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20262: Unable to clone the Oracle Home.

Cause: The Oracle Home "{0}" was already registered with the Oracle Inventory with the name "{1}".

Action: Either provide a different inventory location or provide a different location for the new Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20263: Invalid Oracle Inventory.

Cause: There are two possible causes for an invalid OraInventory "{0}". 1. Inventory was empty. 2. It did not have valid inventory.xml file.

Action: Provide a valid Oracle Inventory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20264: Default inventory pointer file is invalid.

Cause: There are six possible causes for the default inventory pointer file "{0}": 1. File did not exist. 2. File did not have read permission. 3. It was a zero size file. 4. File did not have any pointer to OraInventory. 5. Oracle Inventory found from file was not absolute. 6. Oracle Inventory specified in the inventory pointer file did not have write permission.

Action: Ensure that the default inventory pointer file is valid or provide a different, valid inventory Pointer file using the {0} argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20265: Invalid argument.

Cause: Either argument was an empty string or "null".

Action: Provide a valid argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20266: Loading of OUI and engine jar to system class loader was unsuccessful.

Cause: The possible causes are : {0}

Action: Check clone log and error file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20269: Setting Java library path has failed.

Cause: There are four possible causes: 1. The OUI library path {0} was empty. 2. Unable to find OUI library directory name. 3. The oraInstaller library path {1} was empty. 4. The oraInstaller library path {1} was corrupted.

Action: Make sure that OUI and the oraInstaller library are available.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20271: Invalid characters.

Cause: Command-line input {0} had some unsupported characters.

Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20272: Invalid path.

Cause: Path "{0}" was either not absolute or did not have valid characters.

Action: Supported characters are "{0}" but these three characters "_.-" are not allowed in the beginning of a string.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20275: Insufficient space to create {0}.

Cause: Minimum required space was at least "{0}" MB, but only "{1}" MB was available for use.

Action: Make sure that the minimum required space is available for use.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20276: Extracting is unsuccessful.

Cause: Either there was no space available or no write permission.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20277: Some files are missing.

Cause: After configuration, some files were removed.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20278: Oracle Home configuration is unsuccessful.

Cause: Some symbolic link(s) were either mismatching or were not present.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20279: Some of the files present under Oracle Home did not have proper permission.

Cause: Some of the files did not have proper permission.

Action: Check the file {0} which has expected and actual permission. Then update permission of those files.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20280: Oracle Home is not cloneable.

Cause: Some component(s) under the Oracle Home {0} were not cloneable.

Action: Make sure that all components in the Oracle Home are cloneable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20293: Oracle Home configuration is unsuccessful.

Cause: The OraInventory {0} from invPtrLoc file {1} did not match with OraInventory {2} from reference invPtrLoc file {3}.

Action: Check the clone log file and install CloneAction file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20294: Oracle Home configuration is unsuccessful.

Cause: Unable to find Oracle Home name from the inventory.xml file.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20295: Oracle Home configuration is unsuccessful.

Cause: Some "symbolic link" files were either not present or not properly linked where absolute path should be "{0}" and canonical path should be "{1}"

Action: Create those symbolic link.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20299: Oracle Home configuration is unsuccessful.

Cause: Some "no read permission" files were not present.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20305: Extracting is unsuccessful.

Cause: Some files were missing.

Action: Check the clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20318: Missing argument: {0}.

Cause: Required argument was not provided at command line or in the argument file.

Action: Provide a valid argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20324: Unsupported character sequence.

Cause: Input value "{0}" had some unsupported characters.

Action: Name must begin with an alphanumeric character; may only contain alphanumeric or underscore (_) or hyphen (-) characters; and must be 4 to 30 characters long.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20327: Invalid password file.

Cause: The {0} password file {1} did not exist or first line did not contain password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20328: Invalid domain port.

Cause: The domain port was invalid.

Action: Provide a valid port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20329: Error in validating "SERVER_CONFIG".

Cause: Value of the config property "{0}" for server "{1}" was "{2}" and was invalid.

Action: Support values are {0}.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20333: Error in validating "SERVER_CONFIG".

Cause: All password files specified in config property {0} of server "{1}" were not valid.

Action: Make sure that valid password files are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20334: Invalid Domain home location.

Cause: Path "{0}" was not writable.

Action: Provide valid absolute writable path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20335: Error in validating "SERVER_CONFIG".

Cause: All aliases specified in config property {0} of server "{1}" were not valid.

Action: Make sure that valid aliases are provided.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20336: The moveplan location is invalid.

Cause: There are three possible causes: 1. The path was not provided. 2. The moveplan was not readable. 3. The path was not an absolute path.

Action: Provide a valid absolute path for the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20337: Unable to persist the moveplan.

Cause: Make sure that the moveplan location is writable. {0}

Action: Check the logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20338: Error in examining Adapters.

Cause: Adapter examination failed.

Action: Make sure that all the specified values are correct and the domain configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20340: Error in validating "SERVER_CONFIG".

Cause: There was a mismatch between number of aliases and their keypass files specified in config property {0} and {1} of server "{2}" respectively.

Action: Make sure that number of aliases and keypass files are same.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20341: Error in copyConfig.

Cause: The AdminServer is down.

Action: Make sure that the AdminServer of the specified domain is started.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20342: Error in deploying Adapters.

Cause: Adapter deployment failed.

Action: Make sure that the deployment plan for {0} is valid or that it exists in the archive.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20343: Error in validating "SERVER_CONFIG".

Cause: Specified moveplan has more servers than in the source domain.

Action: Make sure that no new servers are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20344: Error in validating "SERVER_CONFIG".

Cause: Specified server {0} does not exist in the source domain.

Action: Make sure that no new servers are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20345: Error in validating "SERVER_CONFIG".

Cause: Value of the config property "{0}" for server "{1}" was not in "{2}" format.

Action: Make sure that you have provided correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20346: Error in validating "SERVER_CONFIG".

Cause: Specified {0} {1} is not valid.

Action: Make sure that valid port numbers are specified in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20347: Error in validating "DATASOURCE".

Cause: Specified moveplan has more data sources than in the source domain.

Action: Make sure that no new data sources are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20348: Error in validating "DATASOURCE".

Cause: Specified data source {0} does not exist in the source domain.

Action: Make sure that no new data sources are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20349: Error in validating "DATASOURCE".

Cause: Some of the required parameters of data source {0} are missing in the moveplan.

Action: Make sure that valid values are provided in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20350: Error in validating "MACHINE_CONFIG".

Cause: Specified moveplan has more machines than in the source domain.

Action: Make sure that no new machines are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20351: Error in validating "MACHINE_CONFIG".

Cause: Specified machine id {0} does not exist in the source moveplan.

Action: Make sure that no new machines are added to the moveplan and also make sure that "configProperty" id is not modified.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20352: Error in validating "MACHINE_CONFIG".

Cause: Specified port {0} is not valid.

Action: Make sure that valid port numbers are specified in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20353: Error in exporting metadata.

Cause: MDS Metadata export failed.

Action: Make sure all the servers are started in the specified domain.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20354: Server start failed.

Cause: MDS Metadata import failed. Could not start the server {0}

Action: Make sure that valid values are provided in the moveplan and the archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20355: Error in importing metadata.

Cause: MDS Metadata import failed.

Action: Make sure that valid values are provided in the moveplan and the archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20356: Error in validating "SERVER_CONFIG".

Cause: There was a mismatch in number of servers present under SERVER_CONFIG group of target moveplan and source moveplan(present inside archive).

Action: Make sure that no server is added or removed in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20357: Command-line parameters did not match the script.

Cause: The parameters used for this command were invoked by the wrong script.

Action: Use the '-help' option to see the allowed parameters.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20361: Error in executing WebLogic script for configuring adapter and application deployments.

Cause: Either the values specified in the moveplan are not correct or the end points are not configured correctly in adapter or application deployment plans.

Action: Check the t2P logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20362: Connection to AdminServer failed.

Cause: AdminServer start failed. Make sure that AdminServer parameters specified in the moveplan are correct.

Action: Check the AdminServer logs.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20363: Adapter deployment failed.

Cause: Adapter redeployment failed. Make sure that all values are specified correctly in the moveplans and "READ_ONLY" properties are not changed.

Action: Check the t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20364: OPSS data {0} failed.

Cause: OPSS data migration script execution failed.

Action: Check the t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20365: Error in executing WebLogic script for configuring server, cluster , datasource and authenticator.

Cause: Either the values specified in the moveplan are not correct or some "READ_ONLY" properties in the moveplans are modified or some internal error happened.

Action: Check the t2p logs for more details. Make sure that values in the moveplans are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20366: Domain unpack failed.

Cause: Make sure that values specified are correct.

Action: Check the t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20367: Move plan parsing failed.

Cause: Specified file is not a valid moveplan or the moveplan is corrupted.

Action: Make sure that the moveplan is a valid xml file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20368: Domain pack failed.

Cause: Make sure that values specified are correct.

Action: Check the t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20369: Invalid domain application directory.

Cause: Path "{0}" was not writable.

Action: Provide valid absolute writable path and make sure that the user executing the tool and the owner of the domain home directory is the same, for UNIX.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20370: Invalid domain application directory.

Cause: Directory "{0}" is not empty.

Action: Provide a valid non-existing or an empty directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20371: Invalid domain location.

Cause: Directory "{0}" is not empty.

Action: Provide a valid non-existing or an empty directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20372: Server port validation failed.

Cause: Ports of following servers - {0} - are not available.

Action: Provide valid free ports.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20373: The system temporary directory is inaccessible.

Cause: The system temporary directory "{0}" did not have write permission.

Action: Make sure that system temporary directory has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20374: Default domain application directory already exists and not empty.

Cause: Domain application directory was not provided. The default location "{0}" used by unpack process was not empty.

Action: Possible actions are : 1. If domain application directory is not provided, then its default location "{0}" should be non existing or an empty directory. 2. Provide different domain application directory via command line argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20375: Invalid Oracle Home.

Cause: Required files needed for cloning were not found in the Oracle Home {0}.

Action: Make sure that the Oracle Home has the required files for cloning.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20377: Error in stopping {0} managed server.

Cause: Either the credentials were not correct or the managed server was not running.

Action: Check the server logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20383: Invalid moveplan directory location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the moveplan directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20384: Mandatory parameter missing.

Cause: Parameter "planDirLoc(pdl)" missing for the extractMovePlan command.

Action: Provide parameter "planDirLoc(pdl)" for the extractMovePlan command.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20385: Error in validating "MACHINE_CONFIG".

Cause: Specified name {0} for machine {1} is not valid.

Action: Provide valid machine name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20386: Oracle Home is not cloneable.

Cause: Install.properties file from Oracle Home {0} did not have correct entries for cloning.

Action: Make sure that the install.properties has correct entries.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20387: Error in validating "CLUSTER_CONFIG".

Cause: Specified moveplan had more clusters than in source domain.

Action: Make sure that no new clusters are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20388: Error in validating "CLUSTER_CONFIG".

Cause: Specified cluster {0} did not exist in source moveplan.

Action: Make sure that no new clusters are added to the moveplan and "READ_ONLY" properties are not changed..
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20389: Error in validating "CLUSTER_CONFIG".

Cause: Specified name {0} for cluster was not valid.

Action: Provide valid machine name.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20390: Error in validating "CLUSTER_CONFIG".

Cause: Specified cluster type "{0}" for cluster {1} was not valid.

Action: Valid values are "unicast" and "multicast".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20391: Error in validating "CLUSTER_CONFIG".

Cause: Specified {0} {1} was not valid.

Action: Make sure that valid port numbers are specified in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20392: The domain home validation failed.

Cause: The following file {0} did not present under domain home.

Action: Provide a valid domain location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20393: Error in validating command-line parameter "{0}".

Cause: Path {0} was either not absolute or did not exist.

Action: Provide an absolute path for the command-line parameter "{0}"
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20394: Invalid Domain home location.

Cause: Path "{0}" was not absolute or an empty directory.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20395: Invalid Domain home location.

Cause: Path "{0}" was not readable.

Action: Provide a valid absolute path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20396: The domain home validation failed.

Cause: An attempt was made to perform T2P of "{0}" domain. The specified domain home "{1}" was not a "{0}" domain.

Action: Provide a valid domain location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20397: Error in validating "RDBMS Security Store".

Cause: RDBMS Security Store was not enabled in source domain

Action: Make sure that no new sections are added to the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20398: Error in validating "RDBMS Security Store".

Cause: {0} for RDBMS Security Store was not valid.

Action: Provide valid value for {0}.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20399: Unable to determine Oracle Home used by the domain home.

Cause: Oracle Home information was missing in "{0}" file present under domain home.

Action: Make sure that the specified domain home is associated with a valid Oracle home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20400: Source Oracle Home location validation failed.

Cause: The source Oracle Home "{0}" is not matching with the Oracle Home "{1}" used by the domain home "{2}" .

Action: Provide the Oracle home specified in "{0}" file present under domain home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20401: The domain location is invalid.

Cause: The file {0} did not exist.

Action: Provide a valid domain location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20402: The moveplan file is invalid.

Cause: The xml file was not a valid multi archive moveplan.

Action: Provide a valid xml file for multi archive moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20403: Unable to complete application deployment plan export.

Cause: Error in examining applications for custom deployment plan.

Action: Check logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20404: Error in deploying applications with custom deployment plan.

Cause: Application deployment failed.

Action: Make sure that the deployment plan for {0} is valid or exists in archive.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20405: Application deployment failed.

Cause: Application redeployment failed. Make sure that all values are specified correctly in the moveplans and "READ_ONLY" properties are not changed.

Action: Check the t2p logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20406: Invalid moveplan directory location.

Cause: Path {0} was either an empty string or not an absolute path.

Action: Provide an absolute path for the moveplan directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20407: Invalid moveplan directory location.

Cause: Move plan directory location was empty.

Action: Provide an absolute path for the moveplan directory.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20409: OPSS Configuration failed.

Cause: Specified LDAP details were either wrong or LDAP was not running.

Action: Make sure that LDAP details are correct and LDAP is up and running.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20410: The moveplan file is invalid.

Cause: The provided file was not a valid xml moveplan file.

Action: Provide a valid xml moveplan file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20412: Insufficient arguments.

Cause: An attempt was made to perform "{0}" operation. No argument was provided from the following supported arguments : "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20413: Unsupported command argument(s).

Cause: An attempt was made to perform "{0}" operation. Some of the arguments are not supported by this operation on this OS platform. The supported arguments are: "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20414: Unsupported command argument(s).

Cause: An attempt was made to perform "{0}" operation of "{1}". Some of the arguments are not supported by this operation. The supported arguments are :"{2}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20415: Insufficient arguments.

Cause: An attempt was made to perform "{0}" operation of "{1}". Following required arguments were missing: "{2}".

Action: Provide required arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20416: Arguments combination is invalid.

Cause: An attempt was made to perform "{0}" operation by providing parameters for "{1}" .

Action: Provide valid arguments for a particular type.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20417: Insufficient arguments to decide exact operation.

Cause: An attempt was made to perform "{0}" operation. Unable to decide type of operation from provided arguments. The supported arguments for this operation are: "{1}".

Action: Provide valid arguments.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20418: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero.

Action: Provide a valid path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20419: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a directory. 4. It was an empty directory. 5. The directory represented by the path did not have read permission. 6. If environment is UNIX, the directory represented by the path did not have executable permission.

Action: Provide a valid path.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20420: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are four possible causes: 1. The path was not an absolute path. 2. The path was already existing. 3. The parent directory did not have write permission. 4. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path and make sure that it does not exist and its parent directory is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20421: Invalid integer value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a valid positive integer.

Action: Provide a valid positive integer.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20422: Invalid boolean value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a boolean value.

Action: Provide either "true" or "false".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20423: Invalid password file.

Cause: The value provided for argument "{0}" was "{1}". There are six possible causes: 1. The path was not an absolute path. 2. The path did not exist. 3. The path did not represent a file. 4. The file did not have read permission. 5. The file size was zero. 6. The file did not carry first line as password.

Action: Provide a valid password file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20424: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not an empty directory. 3. The path was not existing. Unable to create all the non existing directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path of either a non existing or an existing empty directory and make sure that it is writable
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20425: Archive file is not provided.

Cause: An attempt was made to perform "{0}" operation. Archive file is a mandatory argument.

Action: Provide valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20426: Archive file is invalid.

Cause: This file was invalid for "{0}" operation. This archive was not created using T2P "{1}" operation.

Action: Provide valid archive file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20427: Oracle Home is invalid.

Cause: An attempt was made to run "{0}" operation of "{1}" domain. The following file {2} did not present under target Oracle Home.

Action: Provide a valid Oracle Home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20429: Oracle Home is invalid.

Cause: An attempt was made to run "{0}" operation of "{1}". The Oracle Home "{2}" was invalid.

Action: Provide a valid Oracle Home location.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20430: Invalid string value.

Cause: The value provided for argument "{0}" was "{1}" and it was not a valid string value.

Action: Provide a non-empty value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20432: Invalid path.

Cause: The value provided for argument "{0}" was "{1}". There are five possible causes: 1. The path was not an absolute path. 2. The path was existing. It was not a directory. 3. The path was not existing. Unable to create all the directories. 4. The path was existing. It did not have write permission. 5. If environment is UNIX, there was no executable permission on the existing directory.

Action: Provide absolute path of a directory and make sure that it is writable.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20434: Invalid target Oracle home name.

Cause: There are two possible causes for the target Oracle home name {0}:1. Length of the target Oracle home name was {1} and it was not within 2 to 128 characters long.2. target Oracle home name had contained unsupported characters.

Action: Target Oracle home name must begin with an alphanumeric character; may only contain alphanumeric or underscore (_) characters; and must be 2 to 128 characters long.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20444: Mismatch between archive file and multi archive moveplan.

Cause: The archive file used during this pasteConfig operation was not provided during execution of extractMovePlan command.

Action: Execute extractMovePlan command again by providing the archive file {0} along with other archive files created during copyConfig process.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20508: Invalid target Node Manager home location.

Cause: Path {0} exists but is not a directory.

Action: Provide an empty or non-existing directory location for the target Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20509: Invalid target Node Manager home location.

Cause: Path {0} exists but is not an empty directory.

Action: Provide an empty or non-existing directory location for the target Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20510: Move Plan does not contain any domain information.

Cause: Source Node Manager may not have been registered with any domain.

Action: Register source Node Manager with the available domains on the machine and run the t2p utility again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20511: Unable to retrieve AdminServer Password for domain{0}.

Cause: Either the password file {0} did not exist, or the AdminServer password was empty.

Action: Provide a valid password file for AdminServer Password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20512: Unable to determine AdminServer credentials for domain {0} from Move Plan.

Cause: Either one of AdminServer Listen Address, AdminServer Listen Port, AdminServer User Name or AdminServer Password for domain {0} was not provided in the MovePlan.

Action: Provide valid AdminServer credentials in the Move Plan and run the t2p utility again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20513: Unable to determine NodeManager credentials for domain {0} from Move Plan.

Cause: Either one of NodeManager User Name or NodeManager Password for domain {0} was not provided in the MovePlan.

Action: Provide valid NodeManager credentials in the Move Plan and run the t2p utility again.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20514: Unable to retrieve NodeManager Password for domain {0}.

Cause: Either the password file {0} did not exist, or the NodeManager password was empty.

Action: Provide a valid password file for NodeManager Password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20515: Unable to connect to AdminServer for domain(s) {0}.

Cause: The AdminServer for domains(s) {0} was not running.

Action: Bring up the AdminServer for each domain before running the t2p utility.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20516: Error while checking the available port for Node Manager.

Cause: The port {0} was not available for the Node Manager.

Action: Provide an available port for Node Manager in nodemanager.properties.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20517: Error while trying to start the Node Manager.

Cause: Operation timed out while trying to start the Node Manager.

Action: Check the nodemanager.log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20518: Error in trying to read password from file {0} .

Cause: File {0} does not exists.

Action: Provide an existing password file in which the first line is the password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20519: Error in retrieving password from file {0} .

Cause: The first line of file {0} does not contain a valid password.

Action: Provide an existing password file in which the first line is the password.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20520: Error in validating "SERVER_CONFIG".

Cause: Value of the config property "{0}" for server "{1}" was empty.

Action: Provide correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20521: Error in validating "Node manager config".

Cause: Value of the config property "{0}" was not in "{1}" format.

Action: Make sure that you have provided correct value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20522: Error in validating "Node Manager Config".

Cause: Value of the config property {0} in Node Manager Config cannot be changed.

Action: Make sure that you have not changed its value.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20523: Error in validating "SERVER_CONFIG".

Cause: The file {0} specified via config property {1} for server {2}, either did not exist or is of zero size or is non-readable.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20600: Unable to derive value of all config properties.

Cause: Could not derive values for some properties that had reference to other config properties.

Action: Check clone log file for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20601: Unable to derive frontend host.

Cause: The Listen address from OHS was not in proper format.

Action: The frontend host can be updated later from Weblogic console.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20602: Unable to derive frontend port.

Cause: The Listen address from OHS was not in proper format.

Action: The frontend port can be updated later from Weblogic console.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20603: Error in validating "SERVER_CONFIG".

Cause: Specified "{0}" file for server "{1}" was not valid.

Action: Make sure that "{0}" file is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20604: Error in validating command line parameters.

Cause: Some command line arguments may be missing or invalid or the archive provided may not be proper or valid

Action: Make sure that valid values are provided for all the required arguments and the archive is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20605: Invalid target domain directory name.

Cause: Provided target domain directory name "{0}" did not match with source domain directory name "{1}".

Action: Make sure target domain directory name is not changed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20606: Error in validating source environment.

Cause: Adminserver was down in the provided source environment. The "copyConfig" operation requires adminserver to be up and running.

Action: Make sure that adminserver is up and running.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20607: Error validating source environment.

Cause: Provided source domain is in edit mode.

Action: Activate all unsaved changes in source domain and re-run "copyConfig".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20608: Error reading composites.

Cause: Composite configuration plan "{0}" could not be read.

Action: Make sure that the file exists and has read permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20609: Error updating composites.

Cause: Composite configuration plan "{0}" could not be updated.

Action: Make sure that the file exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20610: Error validating source NodeManager Home.

Cause: Specified source NodeManager Home location is not valid. "nodemanager.properties" file is not present under NodeManager Home location.

Action: Make sure that source NodeManager Home location is correct and all required files are present.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20611: Error validating source NodeManager Home.

Cause: Specified source NodeManager Home location is not valid. "nodemanager.domains" file is not present under NodeManager Home location.

Action: Make sure that source NodeManager Home location is correct and all required files are present.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20612: Error in executing wlst script.

Cause: {0} did not exist.

Action: Make sure that specified Oracle Home is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20613: Listen port validation failed.

Cause: Specified port, {0} is either not valid or not available.

Action: Provide valid free port.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20614: NodeManager listen address validation failed.

Cause: Specified listen address was not configured on a local network interface.

Action: Provide a valid local listen address on which the NodeManager should come up.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20615: Source Oracle home location validation failed.

Cause: Specified domain is not registered with the source Oracle home.

Action: Make sure that specified domain home is registered in "domain-registry.xml" of source Oracle home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20616: Domain credentials validation failed.

Cause: Specified domain credentials were not of the source domain location.

Action: Make sure that specified source domain location and domain credentials are valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20617: Error reading MDM URL Resolver configuration.

Cause: MDM URL Resolver configuration file "{0}" could not be read.

Action: Make sure that the file exists and has read permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20618: Error updating MDM URL Resolver configuration.

Cause: MDM URL Resolver configuration file "{0}" could not be updated.

Action: Make sure that the file exists and has write permission.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20619: OPSS re-association failed.

Cause: Execution of reassociateSecurityStore to target environment failed.

Action: Check the T2P logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20620: AdminServer restart failed.

Cause: Could not restart AdminServer.

Action: Check the T2P logs and AdminServer logs for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20621: Data source creation failed.

Cause: Error in creating OPSS datasource.

Action: Check T2P logs for details. Make sure values provided in moveplan for "OPSS_CONFIG" are correct.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20622: OPSS Store is not migrated.

Cause: OPSS store is not migrated to target LDAP.

Action: Move LDAP data from source to target before running "pasteConfig".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20623: OPSS store configuration failed.

Cause: Modification of bootstrap credential failed.

Action: Check clone log file for error details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20624: Error in validating "Node Manager Config".

Cause: Config property name cannot be empty.

Action: Make sure config property names are not modified in moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20625: Unable to find Node Manager configuration.

Cause: Node Manager home location is empty.

Action: Make sure that the Node Manager configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20626: Unable to find Node Manager configuration.

Cause: Node Manager type is empty.

Action: Make sure that the Node Manager configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20627: Error in finding Node Manager configuration.

Cause: Node Manager is not configured correctly for the source domain.

Action: Make sure that the Node Manager configuration is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20628: Error in validating Custom Location Node Manager home.

Cause: Node Manager home location was not provided in the moveplan.

Action: Provide valid location for Node Manager home.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20629: Error in validating Custom Location Node Manager home.

Cause: Node Manager home location was not an empty directory.

Action: Provide valid location for Node Manager home. It should be either existing empty directory or non-existing.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20630: Error in validating "Node Manager Config".

Cause: Value of the config property {0} in Node Manager Config was not a valid file.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20631: Error in starting node manager.

Cause: Node Manager start failed.

Action: Check node manager log file, {0} for details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20632: Error in retrieving Node Manager configuration.

Cause: Internal error happened while validating Node Manager configuration.

Action: Make sure the archive provided is valid.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20633: Error in validating "Node Manager Config".

Cause: {0} for Node Manager Config was not valid.

Action: Provide valid value for {0}.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20634: Error in validating "Node Manager Config".

Cause: {0} was not valid config property for Node Manager.

Action: Make sure config property names are not modified in moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20635: OPSS data {0} failed.

Cause: Unable to find "{0} / {1} / {2}" at "{3}".

Action: Make sure these files exist and are accessible.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20636: OPSS data import failed.

Cause: Unable to seed the schema.

Action: Check clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20637: OPSS data import failed.

Cause: Unable to add ldap container.

Action: Check clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20638: OPSS data {0} failed.

Cause: Unable to update {0}.

Action: Check clone logs for more details.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20639: Connection to {0} failed.

Cause: There are four possible causes: 1. Server might be down. 2. Credentials provided might be wrong. 3. If only SSL mode is enabled, provide value of "-trustKeyStoreLoc" parameter. 4. Administration port was enabled and that port was not provided.

Action: Make sure server is running and credentials are valid. If SSL port is used, provide value of "trustKeyStoreLoc" and re-run "copyConfig".
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20640: OPSS data {0} failed.

Cause: Unable to find "{0}" at "{1}".

Action: Make sure this file exist and is accessible.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20641: An internal operation failed.

Cause: Component registration xml, {0} is not a valid xml file.

Action: Make sure that {0} is a valid component registration xml file and is not corrupted.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20642: Move plan comparison failed.

Cause: The moveplan xml passed in the argument does not contain the same meta data as the one present in archiveMeta data property "{0}" from argument moveplan is "{1}" Meta data property "{0}" from archive moveplan is "{2}"

Action: Make sure the moveplan is actually generated from the archive passed in the argument.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20643: Additional parameter format not valid. The value provided for argument "{0}" was "{1}"

Cause: There are three possible causes: 1. Parameter value may be null. 2. Parameter value is not a key-value pair. 3. If more than one key-value pair is passed, they may have not been seperated using ,(comma).

Action: Make sure additional parameter is following a proper syntax. Syntax : -additionalParams property1=value1,property2=value2 Example: -additionalParams server=orclSv1,port=8888 Note:','(comma) and '='(equal) characters cannot be directly used within the key or value. They can be used by replacing them with the escape character as mentioned below ','(comma) -> %2C '='(equal) -> %3D Example: -additionalParams server=srv1%2CfailoverServer%3Dsrv2,ports=8888%2C8881
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20644: Invalid passphrase file.

Cause: The passphrase file {0} specified via config property {1} for server {2}, either did not exist or first line did not contain passphrase.

Action: Provide a valid passphrase file.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20645: Mismatch between domain credentials and domain location.

Cause: The provided domain location "{0}" was different from the domain location "{1}" found from domain by using domain credentials.

Action: Make sure that specified source domain location and domain credentials are in sync.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20646: Target domain location validation failed.

Cause: Target domain directory name, {0} contain invalid characters.

Action: The specified domain directory name must include only alphanumeric characters, hyphens ('-') or underscore characters ('_'). The domain directory name must contain at least one letter or digit.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20647: {0} listen address validation failed.

Cause: Specified listen address, {0} is not a local machine address.

Action: "pasteConfig" is run on domain AdminServer machine. Specify valid local ip address for {0} listen address.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20648: Java vendor and version validation failed

Cause: The Java used in target location is different from the one being used on source location. The source environment was configured with following Java: {0}

Action: Make sure the Java used on target machine is from the same vendor and has the same major version. Example: Oracle Corporation 1.7
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20649: Invalid value.

Cause: The {0} value is empty.

Action: Provide a valid value for {0} property.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20650: Unable to identify the Node Manager home from Move Plan and hence skipping Node Manager configuration.

Cause: There are two possible causes: 1. The Node Manager home is empty. 2. The Node Manager home does not exist.

Action: There are two possible actions: 1. If the Node Manager home was left empty intentionally, then it is safe to ignore this warning message. 2. If the specified Node Manager home does not exist, it can be manually setup after the pasteConfig operation is completed.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20651: Node Manager configuration could not be retrieved and hence skipping Node Manager configuration.

Cause: There are two possible causes: 1. The Node Manager is not configured for this domain. 2. The Node Manager home could not be identified.

Action: There are two possible actions: 1. If the Node Manager is not configured for this domain, then it is safe to ignore this warning message. 2. If the Node Manager home could not be identified, it can still be configured for target domain by providing an existing Node Manager home in Move Plan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20652: Import keystores to kss is not successful.

Cause: Import operation failed.

Action: Check clone log file for exact cause.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20653: Moveplan is invalid.

Cause: Config group of type {0} is missing from the moveplan.

Action: Provide valid moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20654: Error in validating "DATASOURCE".

Cause: Unable to connect to datasource "{0}".

Action: Make sure that valid values are provided in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20655: Error in validating "DATASOURCE".

Cause: Invalid driver class "{0}" specified for datasource "{1}". Failed to load specified driver class.

Action: Make sure that correct driver class is provided in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20656: Error in validating server listen address.

Cause: The following servers: {0} are not having the same type of listen address as the other servers: {1}.

Action: All servers in the moveplan should have same type of listen address. Example: Hostname, IPV4 IP address or IPV6 IP address. There cannot be a mix of these three address types. Make sure that valid values are provided in the moveplan.
Level: 1

Type: ERROR

Impact: Cloning

CLONE-20904: Error happened while shutting down the managed servers. Check the t2p logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20905: OPSS store re-association from {0} to {1} is not supported. OPSS store will not be re-associated to {2}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20906: OPSS store re-association values are not provided. Source Domain OPSS store will be used for unpacked domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20907: {0} Details provided for OPSS configuration is same as source domain. Re-association will not be executed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20908: Deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20909: Application deployment plan ({0}) specified for {1} does not exist. {2} will not be added to the moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20910: Default Authenticator data export failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20911: Default Authenticator data import failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20913: {0} is not a valid configProperty for {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20914: Exception caught while creating Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20915: Exception occurred while trying to write FMWClonerBean to File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20916: Exception occurred while trying to write CopyArgBean to File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20917: Exception occurred while deserializing FMWClonerBean from File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20918: Exception occurred while deserializing CopyArgumentBean from File.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20919: Error in enrolling NodeManager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20920: NodeManager default startup script {0} does not exists.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20921: Unable to start the Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20923: Error in examining OWSM targets. Verify that OWSM targeting is fine post paste config.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20924: Unable to establish a connection to the MBean server to verify an active edit session. Make sure that an edit session is not active in the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20925: Error in validating RDBMS security store properties. Could not establish connection to the RDBMS security store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20928: "pasteConfig" operation of CAM standalone domain failed. Check clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20929: "copyConfig" operation failed for {0} plugin. Check clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20930: Found invalid "configProperty", {0} for {1} configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20931: Error occurred while adding default realm data to archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20932: Error occurred while extracting default realm data from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20933: optimizationHints argument is required during extract moveplan for multi archive mode. Use -optimizationHints (-opth) option to specify optimization hints.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20934: At least one valid optimization flag has to be specified. Flag(s) provided are : {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20935: "pasteConfig" operation of Node Manager failed. Correct the error before running the utility again. Also target Node Manager Home, {0} will be in an unusable state, so delete the directory before re-running "pasteConfig".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20936: "pasteConfig" operation failed for {0} plugin. Check clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20937: "pasteConfig" operation of J2EE domain failed. Check clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20938: Error occurred while handling component plan validation event handler. Message: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20939: Error at column {0}, line {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20940: Error occurred while handling moveplan validation event handler. Message: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20941: Unable to validate domain connection , and exception is = {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20942: The wlst error for configuring {0} is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20943: An error occurred while running the wlst offline command to update the server configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20944: An error occurred while running the wlst offline command to update the server administration port configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20945: An error occurred while running the wlst offline command to update the server frontend configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20946: An error occurred while running the wlst offline command to update the server default file store configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20947: An error occurred while running the wlst offline command to update the server custom identity keystore configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20948: An error occurred while running the wlst offline command to update the server custom trust keystore configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20949: An error occurred while running the wlst offline command to update the custom identity private key configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20950: An error occurred while running the wlst offline command to update the cluster configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20951: An error occurred while running the wlst offline command to update the datasource configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20952: An error occurred while running the wlst offline command to update the datasource configuration for OnsNodeList.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20953: An error occurred while running the wlst offline command to update the datasource configuration for OnsWalletFile.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20954: An error occurred while running the wlst offline command to update the authenticator configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20955: An error occurred while running the wlst command to reassociate security store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20956: An error occurred while running the wlst offline command to update the machine configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20957: An error occurred while running the wlst offline command to update the system component configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20958: An error occurred while running the wlst offline command to update the SSL configuration details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20959: An error occurred while running the wlst command to import default authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20960: An error occurred while running the wlst command to import application metadata.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20961: An error occurred while running the wlst command to export application metadata.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20962: An error occurred while running the wlst command to configure deployment plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20963: "copyConfig" operation of J2EE domain failed. Check clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-20964: "pasteConfig" operation of CAM standalone domain failed. Check clone log and error files for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21001: Domain {0} is a WebLogic managed domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21002: Domain {0} is a standalone domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21003: Execute "{0}" command using T2P script to know exact help message.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21004: Some files are missing. Check clone log file to see all the missing files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21006: Total time taken by T2P process was {0} seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21007: Cloning operation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21008: Cloning operation completed with warnings.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21009: Updating permission of files in Oracle home {0}, if required ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21010: Permissions of all files in Oracle home {0} are correct. Nothing to update.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21016: Adding Oracle Home "{0}" binaries to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21017: Adding Oracle Home binaries to the archive finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21018: Extracting Oracle Home binaries from the archive at "{0}" location started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21019: Extracting Oracle Home binaries from the archive finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21020: Configuration of Oracle Home is in progress ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21021: Configuration of Oracle Home completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21022: Applying permission for {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21023: Applying permission for {0} finished. Operation complete in "{1}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21024: A configuration script needs to be run as root at the end of clone operation. Run "{0}/oracleRoot.sh" as root.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21025: Validating permission of all files in new Oracle Home ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21026: Permission of all files in new Oracle Home are correct.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21028: Unable to find component detail from Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21029: Unable to find top component detail from Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21030: Adding "{0}" to the archive is successful.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21031: Time taken to add all the cloners to archive was "{0}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21032: Archive created successfully at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21035: Restoring the home finished successfully at {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21036: Restoring the component finished successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21037: Time taken to restore all cloners from archive was "{0}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21039: Gathering all sourceid(s) present in the archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21040: Oracle Home archive # {0}, home location {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21042: Component archive # {0}, instanceName@componentName {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21044: Unable to find JRockit JAVA HOME from registry.xml file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21045: Permission file created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21046: Permission file creation failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21047: Permission for new Oracle Home {0} is not set properly, and permissionFilePath relative to Oracle Home is {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21048: Adding all required files to the main archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21049: Canonical path of the following files did not exist, and their absolute path is:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21050: List of files without read permission:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21051: Adding permission file to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21052: Adding permission file to the archive finished. Operation completed in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21053: Total size of the file(s), to be included in the main jar from source location {0}={1} GB.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21054: Unable to read "{0}" file while adding files to the jar file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21056: Time taken for adding files to archive was {0} seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21057: Execution of system prerequisites started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21058: Execution of system prerequisites finished.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21059: Output of the process can be checked in the file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21060: No system prerequisites will be executed for the Oracle Home {0} as it is set to false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21061: No system prerequisites will be executed for the Oracle Home {0} as no system prerequisites files are available for this Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21071: Permission file created with warnings.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21081: Parsing moveplan to get component name and component type ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21082: Parsing multi archive moveplan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21083: Creating updated moveplan for component name "{0}" and component type "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21084: Checking whether any config property has still reference to other config property or not.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21085: Updating component specific moveplan from multi archive moveplan ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21086: Updating component specific moveplan from multi archive moveplan for "{0}" ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21087: No config property has any reference to other config property.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21092: For help on a particular command, use [ <path to java> -jar <path to cloningclient.jar> -help <command>]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21093: To proceed enter "yes", or any other text to abort:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21094: Clone operation was aborted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21095: Create archive for {0} started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21105: Archive is invalid as it has home(s) and component(s).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21106: Execution of system prerequisites has completed with warnings and/or to be verified. To proceed enter "yes", or any other text to abort:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21118: Adding symbolic link files detail to the archive started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21119: Adding symbolic link files detail to the archive finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21122: File "{0}" is missing.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21125: All the symbolic link files are present in the Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21126: Operation is {0}% complete, in "{1}" seconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21127: Performing inventory validation ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21128: Performing symbolic link files validation...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21129: Performing source Oracle Home reference validation ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21130: No file has any reference to source Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21131: Inventory validation is successful.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21141: CloningClient build label is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21142: CloningClient version is "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21143: Log File: "{0}". Error File: "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21144: Unable to create log directory {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21145: The message id "{0}" is invalid for message type {1}, It did not start with "CLONE", or it did not end with "-INFO" where message type=INFO or it did not end with "-TRC" where message type=TRACE or it did not end with "-SVR" where message type=SEVERE or it did not end with "-ERR" or "-CAUSE" or "-ACTION" where message type=ERROR or its length was not be equal to "{2}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21146: Oracle Home {0} is registered with the Oracle Inventory {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21147: Oracle Home {0} is registered by the name "{1}" with the Oracle Inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21148: Oracle Home {0} passed post validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21149: Oracle Home {0} failed post validation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21154: Checking for availability of {0} MB free space at {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21155: Required free space is available.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21156: Extracting OUI and engine binaries to temporary location ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21157: OUI and engine binaries are extracted to temporary location successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21158: Validating whether Oracle Home location is already registered with Oracle inventory ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21159: Oracle Home location is valid as it is not yet registered with the Oracle inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21160: Validating whether Oracle Home name "{0}" is already registered with Oracle inventory ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21161: Oracle Home name "{0}" is valid as it is not yet registered with the Oracle inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21163: Adding details regarding files without read permission to the archive, started ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21164: Adding details regarding files without read permission to the archive, finished. Operation complete in "{0}" milliseconds.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21165: In the source Oracle Home, some files have no read permission. Those files are not present in the cloned Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21166: Permission of all files in new Oracle Home is not correct and details can be found at {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21193: Error while parsing "{0}" password file: "{1}" for password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21196: The port "{0}" is free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21197: The port "{0}" is not free for use.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21198: Trying to use source port "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21199: Trying to get a new port between lower port {0} and higher port {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21200: Unable to calculate new port.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21201: New value for port "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21203: The {0} password file: "{1}", either does not exist or is zero size.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21204: ERROR

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21205: CAUSE

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21206: ACTION

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21207: {0} T2P Summary Begin{1}{2}{3}{4} T2P Summary End{5}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21208: Error Message

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21209: Warning Message

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21210: WARNING

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21216: Performing post operation, if any ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21217: Post operation completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21218: Post operation failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21221: SEVERE

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21223: Deleting half-created archive file...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21226: Creating Move Plan...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21227: Extracting moveplan and configplan(s) from archive(s)...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21228: Extracting plans from archive {0} under {1}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21229: Creating moveplan by merging moveplan(s)...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21230: Trying to derive OHS configuration from J2EE configuration...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21231: Trying to derive WebLogicCluster of OHS from J2EE configuration...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21232: Trying to derive OHS configuration within itself...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21233: Trying to find out component name and component type from archive ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21234: Laying down moveplan(s) and other plan(s) from archive...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21235: Updating location of composite, MDM url resolver and adapter in moveplan, if any...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21236: Move plan created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21237: Creating component specific updated moveplan from moveplan {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21238: Trying to derive nodemanager configuration properties...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21239: Optimizing J2EE domain configuration ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21240: Optimizing J2EE domain configuration for {0} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21241: Optimizing J2EE domain configuration for DataSource driverclass, jdbc url, schema name and password for all DB schema based on optimization hints ssn={0} ssp={1} sdt={2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21242: Flag {0} is provided to perform more optimization.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21243: No {0} config property will be populated in moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21245: Source domain had file based OPSS_SECURITY configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21246: Trying to find out whether user has changed OPSS configuration from file based to LDAP or DB based in moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21247: User has updated the OPSS configuration from file based to LDAP or DB based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21248: User has not changed the OPSS file based configuration, so OPSS configuration will be same as source.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21249: IN the archive, component name is "{0}" and component type is "{1}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21250: Updating composite configuration plans ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21251: ERROR: There is a reference for host and port to tpid "{0}", but unable to find values for these tpid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21252: ERROR: Config property having tpid "{0}" and value "{1}" is not in host:port pattern, but some other config properties depends upon it.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21253: ERROR: There is a reference to tpid "{0}", but unable to find values for these tpid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21254: ERROR: There is a reference for host to tpid "{0}" and for port to tpid "{1}", but unable to find values for these tpid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21255: ERROR: The reference tpid "{0}" is not in proper format.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21256: ERROR: Config property having tpid "{0}" and value "{1}" has no domain name, but some other config properties depends upon it.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21257: Unable to derive value for T2P unique id "{0}"

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21258: Updating application deployment plans ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21259: Unable to optimize host port value in composite configuration plan "{0}". Update this file before pasteConfig operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21260: All the host port values present in composite configuration plans of all the domains are optimized.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21261: Unable to optimize host port value in MDM URL Resolver file "{0}". Update this file before pasteConfig operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21262: All the host port values present in MDM URL Resolver file of all the domains are optimized.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21263: Updating MDM URL Resolver configuration ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21264: OPSS configuration complete. AdminServer will now be restarted.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21266: {0} does not appear to contain an obfuscated password. Assuming plaintext ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21267: Failed to create the deployment plan file at specified location for application "{0}". Copying the deployment plan file to "{1}"

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21268: Examining Node Manager configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21269: Validating Node Manager config properties.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21270: Configuring Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21271: Validation of node manager config properties failed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21272: {0} OPSS data...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21273: Examining Coherence Server configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21274: Examining Coherence Cluster configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21275: Validating and updating Coherence Server configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21276: Validating and updating Coherence Cluster configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21277: Failed to create the deployment plan file at specified location for adapter "{0}". Copying the deployment plan file to "{1}"

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21278: Warning: optimizationHints argument is not required during extract moveplan for single archive mode. Ignoring the argument.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21279: Warning: The following optimizationHints flag are not supported and hence ignoring - {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21280: Warning: -domainAdminPassword argument has been deprecated. Use -domainAdminPasswordFile instead.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21281: Ignoring the argument {0} for this operation

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21282: Warning: MDS Import of following applications failed. {0}. Check managed server and clone logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21283: Warning: MDS export of some applications failed. Check the following list of applications and verify that MDS data is not associated with these applications. {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21284: Warning: Java vendor information is missing from product.properties.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21285: Warning: Java version information is missing from product.properties.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21286: Warning: Unable to save Java vendor and version information into manifest file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21287: Warning: Exception occurred while fixing file {0} SRC : {1} TAR : {2}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21288: Warning: Invalid Oracle home as unable to find Oracle home name from inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21289: Warning: OUI major version is not 13.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21290: Warning: File {0} will not be archived as it is locked by other process.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21291: Warning: File {0} will not be archived as unable to read.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21292: Examining Server Template configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21293: Validating and updating Server Template configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-21294: Updating Node Manager username and password.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-22001: CreateClonerInfo object should not be empty at this point.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22002: Source type "{0}" was either empty or was not supported.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22003: The provided cloneType="{0}", is not matching with required clone type "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22004: ApplyClonerInfo object should not be empty at this point.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22005: Either cloneType="{0}" or visible sourceid="{1}" or actual sourceid="{2}" is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22008: During apply cloner object(s) build, all the sourceid(s) in the archive are {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22010: The archive entry point in the jar is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22017: No cloner object was found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22018: Setting actual sourceid for all cloner objects.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22019: Adding all sourceid(s) to the jar file started ...

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22020: Adding all sourceid(s) to the jar file finished.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22025: The content of the sourceid file is {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22040: The jar file path={0} is invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22041: Path represented by "{0}" was not a directory.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22042: Path represented by "{0}" did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22043: Path is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22044: Unable to create file "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22045: Directory {0} was not empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22046: File object is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22047: The specified path "{0}" is not a file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22048: The file "{0}" is of zero size.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22049: The file "{0}" is not a directory.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22052: Target location {0} is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22053: The jar output stream is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22054: The exclude pattern of the files which will not be included in archive={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22055: Generating exclude file pattern list, if any pattern is provided.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22057: Generating list of files to be included.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22058: The statistics of the files are: Total number of files={0}. Non-readable files={1}. symbolic link files={2}. Exclude pattern={3}. Exclude pattern actual={4}. Included files only={5}. Included empty folders only={6}. Nonempty folders={7}. Invalid absolute path whose canonical path does not exist={8}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22061: The archive entry point={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22062: Counter={0}, and excluded file through file pattern is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22063: The time taken for unarchiving the entry from main jar={0} milliseconds.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22064: Either jar file path or entryNameToBeExtracted or target location is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22065: The statistics of files whose permission will be handled:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22066: The number of files with root privilege={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22067: The number of symbolic link files={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22069: The root privilege files are:

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22071: File permission is invalid where visible permission is={0} and its calculated permission is={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22072: Permission file {0} was already existing, so it will be deleted.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22073: The command "ls -alR" is executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22074: The command "ls -alR" is not executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22075: Unable to generate document object from the xml file {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22076: The domainHost={0}, domainPort={1}, domainAdminUserName={2}, domainAdminPassword={3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22077: The Weblogic home "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22078: The Weblogic jar "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22079: The Oracle Home "{0}" was invalid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22085: No parameter(s) should be empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22088: The jmx_connector is valid.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22089: Connection obtained successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22090: Unable to get server connection.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22094: Under instance home {0}, the components present are {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22140: Parameter validation is complete. Sourceid is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22141: Parameter validation is complete. TargetLocation is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22142: Parameter validation is complete. Sourceid map is set to : "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22152: parent_of_prereq="{0}", path_upto_oui="{1}", libDir_for_oui="{2}", platform_for_prereq="{3}", oui_lib_dir="{4}", sPrereqDir="{5}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22153: Before setting system environment property, prereq_bootstrap_dir="{0}", bootstrap_dir="{1}", prereq_config_loc="{2}", prereq_log_dir="{3}", oracle_install_scratch_path="{4}", oracle_install_lib_loc="{5}", oracle_install_engine_mode="{6}", java_lib_path="{7}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22154: To run prerequisites, oui lib directory is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22156: To run prerequisites, platform_directory under prereq folder is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22157: Operating system name="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22158: No jar will be added to system class loader as jarlist is empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22159: Checking whether the following classes are already available in classpath or not. {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22160: Status of the availability of all above classes in classpath is "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22161: The following jars will be added to System class loader. {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22162: All jars added to System class loader successfully.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22163: All jars added to System class loader failed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22164: After loading jars to classpath, checking whether the following classes are available or not {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22165: Adding engine jars to system classloader from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22166: Status of adding engine jars to system classloader from Oracle Home {0} is="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22167: Adding oui jars to system classloader from {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22168: Status of adding oui jars to system classloader from {0} is="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22169: Adding both engine and oui jars to system classloader.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22170: Status of adding both engine and oui jars to system classloader is="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22171: Adding oui jars from Oracle Home {0} to system class loader to know Oracle Home details.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22172: Trying to retrieve the top component name from Oracle Home {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22174: Extracting prerequisites jars under {0} location.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22175: Invoking engine prerequisites launcher.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22176: Status of parsing command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22177: Status of first validation of command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22178: Status of second validation of command-line argument="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22183: Invalid entry for inventory_loc in inventory pointer file, and entry was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22184: List of all valid symbolic link files is as follows.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22185: In file description "{0}", the first character is not "l", but has String "->"; assume it is symbolic link file.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22188: Adding jars from {0} to system class loader.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22189: Status of adding jars from {0} to system class loader is "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22193: Updating file {0} where key={1} and value={2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22194: Status of updating file {0} where key={1} and value={2}, is {3}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22195: All inputs from command-line are: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22199: List of all symbolic link files is as follows.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22200: Setting invPtrLoc with InventoryManager with user input value {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22204: OraInstaller library path={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22206: Size of the home {0}={1} byte or "{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22207: For location {0}, free space required="{1}" MB, and the available free usable space="{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22209: Number of entries in the file, which will contain all valid symbolic link files detail={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22211: Validating existence of symbolic link file by checking absolute path and canonical path.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22212: The command "{0}" is not executed properly, and temporary file was {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22217: {0}, file "{1}" is missing.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22218: During file existence check, number of files present={0} and number of file absent={1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22224: For sourceid="{0}", the target location="{1}", and space required="{2}" MB.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22238: Rename status of source file {0} to target file {1} is {2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22239: Delete status for file {0} is {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22240: Before updating file, sourcefile="{0}", old value="{1}", new value="{2}" and temporary file="{3}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22241: Trying to overwrite the content of source file "{0}" into the target file "{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22242: All the Oracle Home location and corresponding name present in the inventory {0} is as follows: {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22244: Directory "{0}" was empty.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22245: Prereq execution result as follows: AllPrereqChecksCount ="{0}", prereqSuccessCount ="{1}", prereqFailedCount ="{2}", WarningsCount ="{3}", UserVerifyCount ="{4}", List of All Checks ="{5}", List of checks passed ="{6}", List of checks failed ="{7}", List of Warning checks ="{8}", List of checks to verify="{9}", List of checks to Retry ="{10}", Prereq Summery ="{11}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22247: Number of files with "no read access permission"={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22248: The file "{0}" was non-readable in the source Oracle Home, and now it is available in the cloned Oracle Home.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22249: ERROR, for the symbolic link path "{0}", the required canonical file {1} is not present.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22250: ERROR, the symbolic link path "{0}", did not exist.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22251: ERROR, for the symbolic link path "{0}", the absolute path {1} and canonical path {2} are same, which is incorrect.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22252: ERROR, for the symbolic link path "{0}", the canonical path {1} and required canonical path {2} are different, but should be same.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22253: Counter={0}, absolute path="{1}" and required canonical path="{2}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22254: The input from the user was="{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22257: Unable to set the permission of the file {0} to {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22260: Executing following command: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22262: Primary validation prior to clone operation is successful for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22263: Restoring for the sourceid "{0}" started at {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22264: Time taken to restore sourceid "{0}" is "{1}" milliseconds.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22265: Adding cloningclient.jar to Archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22266: "StartupMode" is not set in moveplan. Assuming PRODUCTION Mode.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22267: Extracted MDS metadata to {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22268: No MDS data found in archive. Skipping metadata import.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22269: Adapter deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22270: Commented OPSS_SECURITY "configGroup".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22271: OPSS_SECURITY "configGroup" commenting failed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22274: Setting Listen Address of {0} to localhost to start it locally.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22275: Setting Listen Address of {0} to {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22277: Removing frond end url setting for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22278: Setting frond end url setting for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22279: Failed to remove frontend host and port settings for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22280: Failed to set frontend host and port settings for {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22281: {0} start failed. Checked managed server logs for details.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22282: {0} start failed due to time out. Try again.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22283: Application deployment plan location is {0}. Make sure that configurable parameters specified in {1} deployment plan are correct.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22284: Adding Default Authenticator data to archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22285: Adding Node Manager files to archive.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22286: Derived WebLogic Server home to be {0} and Java Home to be {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22287: Loading Jar {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22288: Move Plan has no Node Manager movable component.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22289: Number of Node Manager Movable Components is {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22290: Mismatch in number of Movable Components of node manager from derived and visible.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22291: Deriving node manager properties of {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22292: Retargeting owsm application and data sources.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22293: Detected CommonDomain. Exporting Fusion Apps Global Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22294: Not detected as CommonDomain. Fusion Apps Global Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22295: Detected CommonDomain. Exporting ESS Global Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22296: Not detected as CommonDomain. ESS Global Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22297: Detected CommonDomain. Exporting ESS Internal Partition MDS docs..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22298: Not detected as CommonDomain. ESS Internal Partition MDS docs will not be exported..

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-22299: Export location for embedded LDAP data = {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Cloning

CLONE-23001: Copyright Â© 2004, 2013, Oracle and/or its affiliates. All rights reserved.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23002: Usage: Run {0} script with following parameters:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23003: Options(alias) with multiple names separated by comma:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23004: Absolute path of java home directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23005: T2P process cannot be executed without this.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23006: Absolute path of archive file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23007: The archive file should not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23008: Absolute path of Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23009: To create archive of this Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23010: Absolute path of inventory pointer loc i.e. oraInst.loc

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23011: This argument is ignored from 12.1.2.0.0. It is used to validate source Oracle Home. Internally it is calculated. In case of unix, it is ORACLE_HOME/oraInst.loc. In case of Windows this argument is not required.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23012: Absolute path of a directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23013: Cloning log and error file will be created under this directory. Default location is system temporary location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23014: Flag to run the T2P operation in a non-interactive mode. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23015: Flag for ignoring the results of free space check. Default value is false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23016: Description:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23017: To create an archive of Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23018: Example:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23019: Usecase-{0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23021: Command:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23022: Requirement

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23023: The movement scripts require a minimum of Java version of 1.6 However, for the exact JRE version certified for the product, please refer to the System Requirements and Supported Platforms document, which is located at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23024: Assumption:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23025: NOTE:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23030: Absolute path of the target Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23031: Absolute path of an existing archive file.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23032: This argument is mutually exclusive with "{0}" argument.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23033: Flag to execute system prerequisites before restoring the Oracle Home. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23034: Absolute path of inventory pointer file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23035: This flag is supported in UNIX platforms only. Default value is {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23036: This file has pointer to central inventory. Oracle Home will be registered with that central inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23037: The invPtrLoc should point to a file which contains the following information.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23038: Additional session variable for OUI runInstaller. Variables need to be passed as key=value pair.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23039: More than one session variable should be separated using comma (,).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23040: In Windows, provide whole value within double quote("").

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23041: Oracle Home name that will be used to register Oracle Home with the central inventory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23042: Flag to reconfigure an already existing Oracle Home(created using flexClone mechanism). Default value is false.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23043: Either to restore and configure the Oracle Home using an archive or reconfigure an Oracle Home created via flexClone mechanism.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23044: Make sure that the Oracle inventory has no entry for the target Oracle Home and target Oracle Home name.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23045: Restore Oracle Home from an archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23046: Archive was created using copyBinary script. Path specified for target Oracle Home need to be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23047: Reconfigure an already existing Oracle Home created using flexClone mechanism

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23048: The target Oracle Home is existing. Binaries are moved from source to target via flexClone mechanism.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23049: The target Oracle Home location cannot be inside another Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23060: WebLogic managed domain specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23061: Absolute path of source WebLogic Domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23062: To capture configuration of this domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23063: Source Domain Admin Server Host Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23064: Source Domain Admin Server Port

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23065: Source Domain Admin Server User Name

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23066: Absolute path of source domain Admin server user password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23067: Absolute path of Custom Trust KeyStore File

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23068: Additional parameters required for product specific operations. It need to be passed as key=value pairs.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23069: Multiple parameters should be passed by separating each key=value pair by a comma (,).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23070: In Windows, provide whole value within double quote("").

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23071: Standalone domain specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23072: Absolute path of source standalone Domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23073: Node Manager specific parameters

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23074: Absolute path of source nodemanager home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23075: If this argument is not provided, copyConfig utility will try to calculate the same.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23076: In case of failure to compute the argument, provide the argument explicitly.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23077: To create archive of a Weblogic managed domain or a standalone domain or a NodeManager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23078: This Oracle Home need to be associated with the domain specified via argument {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23081: To create archive of {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23085: Absolute path of an existing target Oracle Home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23086: Absolute path of the T2P MovePlan

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23087: Absolute path of the updated T2P MovePlan xml document (extracted during {0} operation).

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23088: Refer to the Chapter "Cloning Oracle Fusion Middleware" of Fusion Middleware Guide for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23089: Absolute path of target WebLogic managed domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23090: Path can be either a non existing or an existing empty directory.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23091: Absolute path of target domain Admin server user password file

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23092: Absolute path of target J2EE domain application directory

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23093: Absolute path of target Node Manager home

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23094: To restore the full archive containing a WebLogic managed domain or a standalone domain or a Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23095: To restore archive of {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23096: Absolute path of target Standalone domain

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23097: when additional parameters are required by some products to complete copyConfig operation.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23101: Absolute path of the existing archive files.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23102: If multiple archives are provided, provide them as a comma separated list. (In Windows, provide the comma separated list within double quotes)

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23103: Absolute path to directory where moveplan is to be extracted

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23104: The moveplan and/or multi archive moveplan will be extracted along with other J2EE Configuration Plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23105: Flags for optimization while creating multi archive moveplan

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23106: Provide the flags as a comma separated list. (In case of Windows, provide the comma separated list within double quotes)

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23107: The supported values are :{0} and the aliases for these flags are {1} respectively.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23108: Based on flag, specific optimization of multi archive moveplan will take place.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23109: Flag description:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23110: You need to provide this hint always. This simplifies the moveplans by setting other flags internally.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23111: The same password is used for all schemas associated with a particular database specified in {0} section of the moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23112: However, the passwords for APPID users are different. You are prompted to provide the password only once for each database.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23113: Therefore, you need to pass a separate password for each of the APPID users.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23114: The same password is used for all schemas associated with a particular database specified in {0} section of the moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23115: If {0} flag is provided, then automatically this flag will be set to true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23116: To extract moveplan or multi archive moveplan along with other J2EE configuration plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23117: The t2p moveplan or multi archive moveplan contains the endpoint configuration for J2EE and CAM Component configuration

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23118: For details on how to modify the t2p moveplan or multi archive moveplan, refer to T2P document.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23120: Updating machine, datasource configuration changes in the extracted domain template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23170: Invoking all CAM components which supports T2P.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23171: Following system components are configured in the domain: "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23172: No system components are configured in the domain.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23173: Following types system components support T2P : "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23174: There are no system components which support T2P.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23175: Following types of system components {0} are configured in the domain. T2P is not possible for following components types {1} as there is no T2P support for them.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23176: Following system components (COMPTYPE_COMPNAME Vs machineName) are configured in the domain "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23190: Find all CAM plugin PasteConfig implementations and apply the configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23265: Use the "-help" option for more information about cloning options and arguments.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23266: Connecting to runtime ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23267: Pack Domain - {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23268: Adding Packed Domain to archive

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23269: Successfully connected to runtime.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23270: Connecting to domain runtime ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23271: Trying to connect to {0}:{1} ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23272: Successfully connected to the Domain Runtime.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23273: Examining Servers.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23274: Examining Machines.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23275: Examining Clusters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23276: Examining Datasources.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23277: Examining Security Policy.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23278: Examining all J2EE plugin implementations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23279: Credential and Policy Store is LDAP type.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23280: Credential and Policy Store is File based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23281: Extracting packed domain from archive to temporary location.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23282: Reading extracted domain template and updating target server, machine, cluster, datasource and many more configuration changes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23283: Unpacking updated domain template to the target domain location ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23284: Starting AdminServer and pasting security policy configuration changes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23285: Find all J2EE plugin PasteConfig implementations and apply the configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23286: Pasting security policy configuration changes ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23287: Validating and updating Server configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23288: Validating and updating Cluster configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23289: Validating and updating DataSource configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23290: Validating and updating Machine configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23291: Validating and updating system component configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23292: Examining Adapters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23293: Examining Resource Adapters. The Resource Adapters with deployment plan will be added to moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23294: Adding Adapter {0} to moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23295: Warning: Found invalid attribute in Adapter "ConfigGroup". Valid Attributes are "Name" and "Deployment Plan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23296: Paste Adapter Configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23297: Warning: Neither LDAP nor DB details are specified in moveplan for the OPSS Security Store. Default Store will be used at the target.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23298: Re-associate security store with provided LDAP : {0}, {1}, {2}, {3}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23299: Domain template is updated successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23300: Configplans have been extracted at "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23301: ExtractMovePlan operation completed successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23302: Serialize and write bean to a temp file, then add that temp file to jar.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23303: Write archive file list to a temp file , then add that temp file to jar.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23304: ****************** PACK ******************

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23305: Details for Packing Domain...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23306: Oracle Home Source Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23307: Source Domain Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23308: Packed jar Location: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23309: Command to execute for pack: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23311: SEVERE: Specified adapter deployment plan {0} is not a valid file. Using the default plan from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23312: Examining LDAP Authenticators.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23313: Validating and updating LDAP Authenticator configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23314: Exporting metadata of applications. Make sure that all managed servers in the specified domain are started.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23315: Importing metadata of applications.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23316: Starting {0} to import MDS data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23317: Importing metadata of application {0} from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23318: Unpack of updated domain template to target domain location completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23319: Exporting metadata may take several minutes. Check the logs for monitoring the progress ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23320: Importing keystores of servers to KSS ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23321: Import of keystores of servers to KSS completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23322: Updating keystores of servers to {0} as keystore type was kss.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23323: Keystores of servers are updated.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23324: Importing keystores of NodeManager to KSS ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23325: Import of keystores of NodeManager to KSS completed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23326: Keystores for all servers set to "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23327: Keystore type for all servers set to "{0}".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23351: MDS data export flag is set to false. Skipping MDS configurations.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23352: [Deprecated - As of release 11.1.1.7.0, replaced by "-mdsDataExport|-mde"] Flag to execute MDS export/import. Default value is true.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23353: Error in validating "pasteConfig" parameters.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23356: Error in validating "SERVER_CONFIG" parameters in "moveplan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23357: {0} is already running on port {1}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23358: Stopping all managed servers.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23359: Credential and Policy Store is database based.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23360: Values for re-associating and migrating "OPSS_SECURITY" are not provided. Assuming File store for OPSS.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23361: Re-associate security store to database : {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23362: Examining RDBMS Security Store.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23363: Validating and updating RDBMS Security Store Configuration in the template ...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23374: Examining applications with custom deployment plans.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23375: Examining applications with custom deployment plans. The applications with a deployment plan will be added to the moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23376: Adding application {0} deployment plan to the moveplan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23377: Pasting application deployment plan configuration.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23378: Warning: Found invalid attribute in DEPLOYMENT_PLAN_CONFIG "ConfigGroup". Valid attributes are "Application Name" and "Deployment Plan".

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23379: SEVERE: Specified application deployment plan {0} is not a valid file. Using the default plan from archive.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23380: Exporting Default Authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23381: Importing Default Authenticator data.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23382: MDS export of some applications failed. Check the logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23383: MDS import of some applications deployed on {0} failed. Check the logs for details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23500: Error while archiving Node Manager. Check log for more details.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23502: Unarchiving Node Manager files at location {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23503: Target Oracle Home Location is either null or an empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23504: Unable to derive target WebLogic Server Home from the Oracle Home.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23505: Unable to derive Java Home from the target Oracle Home .

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23506: The file {0} does not exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23507: Updating file {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23508: Examining each domain to enroll Node Manager.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23509: Unable to retrieve properties of the domain from Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23510: Domain Name is either null or an empty string in the Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23511: Domain Location is either null or an empty string in the Move Plan.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23512: Incorrect format of AdminServer Listen Port for domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23513: Checking if the AdminServer for domain {0} is up...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23514: Could not connect to AdminServer for domain {0}. Make sure values provided are correct in moveplan. If "AdminServer Listen Port" is SSL port, provide value of "Custom Trust KeyStore File" of the domain if domain keystore type is Custom Trust.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23515: Enrolling NodeManager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23516: Successfully enrolled NodeManager with domain {0}.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23517: WebLogic Server Home value is either null or empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23518: Starting Node Manager from location {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23519: Node Manager ListenPort mentioned in nodemanager.properties is not valid.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23520: Checking if port {0} is available for Node Manager...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23521: Port is available.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23522: -targetNMHomeLoc is either null or an empty string.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23530: Re-associating security store...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23533: Absolute path of Custom Trust KeyStore File Location. Specify this property to specify the "CustomKeyStore" if SSL port is specified for AdminServer.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23534: The moveplan - {0} was not extracted using the archive - {1}. Please extract the moveplan once again using the archive - {1} and re-run the script.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23535: Warning: Starting of {0} is taking longer than expected. Check the server logs to make sure {1} start is in progress.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23536: Warning: Stopping of {0} is taking longer than expected. Check the server logs to make sure {1} shutdown is in progress.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23537: [Deprecated - As of release 11.1.1.7.0, replaced by"-domainAdminPasswordFile"]

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23538: Starting AdminServer...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23539: Stopping AdminServer...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23540: Starting managed server {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23541: Stopping managed server {0}...

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23542: Archive file {0} is either not a file or of zero size.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23543: No archive file is provided..

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23544: Number of moveplans and number of archives are not same.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23545: Unable to load prerequisites jars, proceeding without executing system prerequisites.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23546: The sameDBTopology flag is false. No optimization will happen for data source.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23547: Prereq will not be executed.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23548: Warning: Valid values are not provided for Custom Identity KeyStore configuration. Source configuration will be retained in the target.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23549: Warning: Following Node Manager properties are missing from moveplan: {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23550: AdminServer stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23551: Managed server {0} stopped successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23552: AdminServer started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23553: Managed server {0} started successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23554: Managed server {0} is already in shut down state.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23950: An empty file path was provided!

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23951: An empty password was provided!

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23952: An environment variable was provided as part of the path, but the environment variable doesn't exist or is empty.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23953: Password file successfully created at {0}

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23954: The path you've provided for the password file is a directory. Enter a valid filename that does not currently exist.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23955: Filename provided already exists. Provide a new filename

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23956: Unable to create password file. Ensure that the directory path exists and is writable

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23957: Object persisted successfully

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23958: Password to obfuscate:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23959: Path of password file to be created:

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-23960: Password file was not created successfully.

Cause:

Action:
Level: 1

Type: UNKNOWN

Impact: Cloning

CLONE-26001: OHS T2P property file is invalid.

Cause: Either property file did not exist or had invalid inputs.

Action: Make sure that the property file {0} has a valid entry.
Level: 1

Type: ERR

Impact: T2P

CLONE-26002: OHS cloning has failed.

Cause: OHS creation failed.

Action: Check the clone log file for more details.
Level: 1

Type: ERR

Impact: T2P

CLONE-26003: Error in validating listen host and port.

Cause: The causes were: {0}

Action: Make sure the listen host and port values provided are correct and the ports are free on the corresponding host.
Level: 1

Type: ERR

Impact: T2P

CLONE-26004: Moveplan validation failed for OHS component.

Cause: There was no movable component of type {0} and name {1} in the source moveplan.

Action: Make sure that the movable component type and name are not chnaged in the moveplan.
Level: 1

Type: ERR

Impact: T2P

CLONE-26005: Moveplan validation failed for OHS component.

Cause: The possible causes are: {0}

Action: Make sure that you have updated only values of READ_WRITE config properties of OHS component.
Level: 1

Type: ERR

Impact: T2P

CLONE-26101: Following OHS components are configured in the domain :{0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26102: Performing copyConfig operation for component {0} ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26103: CopyConfig operation for component {0} is completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26104: Capturing configuration in the moveplan ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26105: Captured configuration in the moveplan.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26106: Archiving configuration files ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26107: Archive of configuration files completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26108: Capturing WebGate configuration, if any ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26110: Validating config properties of config group {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26111: Config properties of config group {0} are validated and updated.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26113: Virtual port {0} is not in listen port list.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26114: Setting virtual port to {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26115: Virtual port is not in the new listen port list. Leaving this virtual host port as it is.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26116: Updating webgate specific configuration, if any ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26117: The port {0} is not free. Assigning new port {1}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26118: Archive of {0} files started, if any...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26119: Archive of {0} files finished.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26120: Restoring {0} files from the archive started ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26121: Restoring {0} files from the archive completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26122: Updating instance location, component name and Oracle Home ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26123: Instance location, component name and Oracle Home updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26124: Updating directive and container...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26125: Directive and container are updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26127: Performing validation of Listen and Virtualhost ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26128: Updating all xml files under {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26129: All xml files under {0} are updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26130: Updating all configuration files ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26131: All configuration files are updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26133: Configuration file {0} does not exist. Unable to run file fixer.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26134: In source environment, configuration file {0} was outside of the instance home. In target environment, trying to restore to same location.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26135: An attempt was made to restore configuration file at {0}, but this path already exists. So configuration file will not be restored again.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26136: Extracting configuration file under {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26137: Configuration file {0} is restored successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26138: An attempt was made to restore {0} directive at {1}, but this path already exists. So directive will not be restored again.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26139: Extracting directive files under {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26143: Obfuscating PLSQL database password, if exists.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26144: No configuration file carries PLSQL database password.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26145: Obfuscation of PLSQL database password did not happen.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26146: Configuration file {0} was not restored from the archive. Obfuscate will not be performed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26147: Configuration file {0} does not exist. Obfuscate will not be performed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26148: Updating password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26149: Unable to retrieve password for {0} from file {1}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26150: Unable to update password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26151: Password field is updated in the configuration file {0} successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26152: Obfuscating PLSQL database password...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26153: PLSQL database password obfuscated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26154: Unable to obfuscate PLSQL database password.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26155: Restoring permission of configuration files...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26156: Permission of configuration files are restored successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26157: Unable to restore permission of configuration files.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26158: Unable to update password field in the configuration file {0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26159: Validating move plan for OHS component "{0}" ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26160: From move plan, the name of the property is {0}, and its value is empty. Value cannot be empty.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26161: From move plan, the name of the property is {0}, and its value {1} is not a valid integer. It should be a valid integer.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26162: Updating oradav configuration file, if exists ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26163: Updating oradav configuration file ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26164: Obfuscating oradav password...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26165: Oradav password is obfuscated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26166: Unable to obfuscate oradav password.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26167: Oradav configuration file is updated successfully.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26168: Unable to update oradav configuration file.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26169: Updating webgate install directory, if present ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26170: Webgate install directory is updated successfully in configuration files.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26171: Validating config properties of config group {0}...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26172: Config properties of config group {0} are validated.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26181: Following OHS components are present in the moveplan :{0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26182: Executing pasteConfig for OHS component {0} started ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26183: Execution of pasteConfig for OHS component {0} completed.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26201: No OHS component is configured in the domain.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26202: Following OHS components are configured in the domain :{0}.

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26203: Restarting admin server so that configuration files will be in sync ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26205: Starting following components {0} as they were targeted for admin server in the src env and expecting that they are targeted for admin server in target env ...

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26207: OHS component {0} is started successfully..

Cause:

Action:
Level: 1

Type: INFO

Impact: T2P

CLONE-26301: Building OracleASComponent object for OHS component...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26302: OracleASComponent object is created successfully.

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26303: Building OracleASComponentProperties object for OHS component ...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26304: OracleASComponentProperties object is created successfully.

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26305: OHS parameters for pasteConfig operation are : {0}.

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26306: Printing {0} move plan ...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-26307: Updating configuration file {0} through file fixer ...

Cause:

Action:
Level: 1

Type: TRC

Impact: T2P

CLONE-74000: Exception checking for OSB application presence: {0}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74001: Exception intializing mbean connection: {0}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74002: Unexcpected exception: {0}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74003: Importing of OSB resources failed: {0}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74004: Discarding session: {0}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74005: Error discarding session: {0}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74006: Error creating OSB default configuration plan file

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74007: OSB specific configuration elements missing from the MovePlan specified

Cause: OSB specific configuration elements missing from the MovePlan specified

Action: Ensure that the OSB specific configuration elements are specified in the MovePlan
Level: 1

Type: ERROR

Impact: Other

CLONE-74008: Not a valid password file: {0}

Cause: Unable to retrieve the passphrase from the password file

Action: Ensure the passphrase is specified in the password file
Level: 1

Type: ERROR

Impact: Other

CLONE-74900: Error importing OSB resources

Cause: [probable] The passphrase file specified is not same as the one specified during "copyConfig" operation

Action: [probable] Specify the same passphrase as the one used during "copyConfig"
Level: 1

Type: ERROR

Impact: Other

CLONE-74901: Error applying the OSB configuration plan {1}: {0}

Cause: The OSB configuration plan file ({1}) is not valid

Action: Check the OSB configuration plan file, and apply it again using the OSB console
Level: 1

Type: ERROR

Impact: Other

CLONE-74902: Error getting the passphrase to export OSB resources

Cause: The value specified for the additionalParameter "{0}" is not a password file: {1}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74903: Error getting the passphrase to import OSB resources

Cause: The value specified for the configProperty "{0}" is not a password file: {1}

Action: Specify a valid password file for configProperty "{0}", OR ensure that "{1}" is a password file, OR do not specify a value for this configProperty (in which case resources will be imported assuming no protection)
Level: 1

Type: ERROR

Impact: Other

CLONE-74904: Error encountered during determining if wsm-pm application is active or not: {0}

Cause: wsm-pm application may not be targeted to any server.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-74905: Error in starting managed server

Cause: This is due to: {0}

Action: Please fix the issue
Level: 1

Type: ERROR

Impact: Other

CLONE-74906: Error in stoping managed server

Cause: This is due to: {0}

Action: Please fix the issue
Level: 1

Type: ERROR

Impact: Other

CLONE-74907: Error encountered during determining the installation of wsm-pm application: {0}

Cause: wsm-pm application may not be installed.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

CLONE-92100: In method doCopyConfigValidation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92101: In method doCopyConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92102: In method doPostCopyConfig..

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92103: In method doPasteConfigValidation.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92104: In method doPrePasteConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92105: In method doPasteConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92106: In method doPostPasteConfig.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92107: Download data for User Preferences.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92109: Extract driver configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92110: Extract configuration from {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92111: Value was null for property {0}. Skip.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92112: No UMS config found. Skip driver configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92113: Update configuration on {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92114: Upload data for User Preferences.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92115: UMS application not present in domain. Skip doCopyConfig (no-op).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92116: UMS application not present in domain. Skip doPasteConfig (no-op).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92117: Starting server {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92118: Stopping server {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92119: Handle User Preferences.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92120: Found User Preferences on {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92130: No DriverConfigExtractor found for driver type {0}. Skip.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

CLONE-92300: doCopyConfig failed. msg={0} stackTrace={1}

Cause: Failure during copyConfig.

Action: See log for details.
Level: 1

Type: ERROR

Impact: Process

CLONE-92301: doPasteConfig failed. msg={0} stackTrace={1}

Cause: Failure during pasteConfig.

Action: See log for details.
Level: 1

Type: ERROR

Impact: Process

CLONE-92302: Skipped corrupted ConfigGroup for {0}

Cause: Expected one ConfigProperty within ConfigGroup.

Action: Edit moveplan.xml or configure manually in the production system.
Level: 1

Type: ERROR

Impact: Process

14 CONF-30000 to CONF-35141

CONF-30000: Error creating Management Admin Server.

Cause: Oracle Instance directory {0} already exists.

Action: Provide a valid instance home path.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30001: Error creating Management Admin Server.

Cause: {0}

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30002: Error creating AS Component {0} of type {1}.

Cause: {0}

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30003: Error creating AS Component {0} of type {1}.

Cause: {0}

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30004: Error creating routing relationship to provider.

Cause: An internal error has occurred.

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30005: Error creating routing relationship to provider. Relation {0} already exists.

Cause: An internal error has occurred.

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30006: Timed out while waiting for Management Admin Server to start.

Cause: The process is taking more time or not listening at this time.

Action: See the log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30007: Management Admin Server appears to be unavailable.

Cause: {0}

Action: Make sure that the admin server is running and try again.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30008: Error creating routing relationship. Invalid user or provider components. User:{0}. Provider:{1}.

Cause: The user or provider components are not valid.

Action: Make sure that the user and providers are valid components.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30009: Cannot create Application Server. OracleInstance directory {0} already exists.

Cause: The oracle instance home exists

Action: Choose a different oracle instance home
Level: 1

Type: ERROR

Impact: Configuration

CONF-30010: An error occurred while provisioning an AS Instance (oracleInstance:{0} instanceName:{1}).

Cause: {0}

Action: See log for more information.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30011: Unable to access the Process Control Service.

Cause: Process Control Service is not available

Action: Try again after the process control service is available
Level: 1

Type: ERROR

Impact: Configuration

CONF-30012: Error occurred while starting {0} of type {1} in AS Instance {2}. See internal exception for details.

Cause: Internal error has happened.

Action: See log for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30013: Error occurred while stopping {0} of type {1} in AS Instance {2}. See internal exception for details.

Cause: Some internal error has happened

Action: See error logs for more options
Level: 1

Type: ERROR

Impact: Configuration

CONF-30014: An unknown exception was generated while executing the configuration workflow. See internal exception for more details.

Cause: Workflow internal exception

Action: See logs for more information
Level: 1

Type: ERROR

Impact: Configuration

CONF-30015: Operation to provision an AS Instance (Instance Name:{0} Instance Home: {1}) timed out.

Cause: Timeout exception has happened

Action: See logs for more information
Level: 1

Type: ERROR

Impact: Configuration

CONF-30016: Failed to start an AS Instance (oracle instance:{0}, oracle home:{1}).

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30017: Error creating routing relationship. Relationship details { User:{0} Provider:{1} RelationshipName:{2} }.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30018: Error creating AccessPoint {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30019: Unable to obtain the DeploymentManager. Deployment URI:{0}

Cause: Connected Deployment manager could not be found.

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30020: Error deploying a J2EE Application. See internal exception for details.

Cause: Internal Exception

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30021: Unable to locate the target for deployment.Target: {0}

Cause: The deployment target does not exist

Action: Make sure that the target exists
Level: 1

Type: ERROR

Impact: Configuration

CONF-30022: Error creating UnmanagedNetworkDevice {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30023: Error updating metric rule {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30024: Error Executing asctl command through ASconfig: {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30025: Unable to locate the endpoint - {0}.

Cause: The specified end point does not exist

Action: Specify a valid end point
Level: 1

Type: ERROR

Impact: Configuration

CONF-30026: Failed to start a MAS Transaction.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30027: Failed to commit a MAS Transaction.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30028: Failed to roll back a MAS Transaction.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30029: Failed to register an LDAP Server as an unmanaged topology node. LDAP Server name:{0} LDAP Server type:{1}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30030: Invalid LDAP Server Name. Specify a valid LDAP server name and try again.

Cause: Invalid LDAP server

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30031: Failed to register an LDAP Server as an unmanaged topology node.

Cause: Invalid LDAP Server Type {0}.

Action: Specify one of the following valid supported LDAP Server Types: \'UnmanagedLDAPServer\', \'UnmanagedOIDComponent\', \'UnmanagedActiveDirectory\'
Level: 1

Type: ERROR

Impact: Configuration

CONF-30032: Error while registering database schema {0} to MAS .

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30033: Error while calling configuration assistant {0}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30034: Error occurred while trying restart {0} of type {1} in AS Instance {2}. See internal exception for details.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30035: Failed to create a routing relationship to provider.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30036: Error generating Provisioning workflow

Cause: Invalid FarmName

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30037: Error updating Bootstrap Credentials for IDStore

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30038: Error updating Bootstrap Credentials for IDStore

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30039: Error creating a Synchronized Group {0}.

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30051: Error locating the ASInstance in the Farm with the given canonical path {0}

Cause: {0}

Action: Provide the correct canonical path for the ASInstance
Level: 1

Type: ERROR

Impact: Configuration

CONF-30052: Error locating the ASJ2EEApplication in the Farm with the given canonical path {0}

Cause: {0}

Action: Provide the correct canonical path for the ASJ2EEApplication
Level: 1

Type: ERROR

Impact: Configuration

CONF-30053: Error locating the SystemComponent in the Farm with the given canonical path {0}

Cause: {0}

Action: Provide the correct canonical path for the SystemComponent
Level: 1

Type: ERROR

Impact: Configuration

CONF-30054: Error obtaining InstanceHome location for {0}

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30055: Error obtaining the OracleHome associated with {}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30056: TopologyNode {0} does not exist in farm.

Cause: Invalid canonical path

Action: Provide a valid canonical path
Level: 1

Type: ERROR

Impact: Configuration

CONF-30057: An exception was generated while executing the provisioning workflow.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30060: Error while calling validation assistant {0}

Cause: {0}

Action: See log for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30090: The given node is not a valid MDS schema. {0}

Cause: Invalid MDS schema

Action: Provide a valid MDS Schema.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30091: Error deploying a J2EE Application. {0}

Cause: Internal Exception

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30092: The process has been interrupted

Cause: The process has been interrupted

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30093: The application archive could not be loaded as a deployable object

Cause: Some deployment Exception has happened

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30094: File not found. The specified file {0} is not found.

Cause: File is not present

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30095: Configuration Exception happened. See the embedded exception for more details.

Cause: Internal Exception

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30096: Unable to get the deployment configuration.

Cause: The application archive {0} is a invalid archive.

Action: Check the archive and try again.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30097: Unable to locate application archive. "{0}"

Cause: The location to archive is not correct.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30098: Unable to obtain the DeploymentManager. Deployment URI:{0}

Cause: Internal Exception

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30099: Unable to locate the target for deployment. Target: {0}

Cause: Invalid deployment target

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30100: Error creating an Oracle Load Balancer {0}.

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30101: Error associating ASInstance(s) with an Oracle Load Balancer {0}.

Cause: {0}

Action: Specify valid ASInstances.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30111: Error while registering unmanaged SSO Server to MAS .

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30112: Failed to stop an AS Instance (oracle instance:{0}).

Cause: {0}

Action: See logs for more details
Level: 1

Type: ERROR

Impact: Configuration

CONF-30113: See logs for more details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CONF-30114: See logs for more details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Configuration

CONF-30115: Error storing entries in Credential Store

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30116: Error retrieving entries from Credential Store

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30117: Error deleting entries from Credential Store

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-30121: Error assigning AccessPoint {0} to {1}

Cause: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35001: Invalid host value provided to config framework.

Cause: Invalid host value provided to config framework.

Action: Provide a valid host value to config framework
Level: 1

Type: ERROR

Impact: Configuration

CONF-35002: Invalid port value provided to config framework.

Cause: Invalid port value provided to config framework.

Action: Provide a valid port value to config framework
Level: 1

Type: ERROR

Impact: Configuration

CONF-35003: Error while creating the domain.

Cause: An internal operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35004: Error while creating Managed Server.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35005: Error while starting the domain.

Cause: An internal WLST operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35006: Unable to connect to the AdminServer.

Cause: An internal operation has failed:{0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35007: Error while setting control flag {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35009: Error while stopping the domain.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35010: Error while deploying the Application {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35011: Error while starting the Application {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35012: Error while stopping the Application {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35015: Error while creating Group {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35020: Error while creating DataSource {0} .

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35025: Error while creating JMSResource {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35030: Error while creating Authenticator {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35035: Error while executing WLS script located at {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35040: Error while creating Network Channel {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35075: Error creating ASInstance {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35076: Error creating ASComponent {0}.

Cause: An internal operation has failed: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35080: Error Applying template.

Cause: A WLST Error occurred: {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35081: Error Applying template.

Cause: Domain Home cannot be empty.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35082: Error creating Domain {0}.

Cause: A WLST Error occurred.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35085: Error creating Cluster {0}.

Cause: See logs for more details.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35090: Error while starting the domain.

Cause: Starting the Admin_Server timed out.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35091: Error while starting the domain.

Cause: An error occurred while starting the domain.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35092: Error Setting target for Startup class {0}.

Cause: An internal error has occurred.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35095: Error setting target for Shutdown class {0}.

Cause: An internal error has occurred.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35100: Error starting and enrolling Node Manager

Cause: An internal operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35105: Error Creating Multi Data Source {0}

Cause: An internal operation has failed

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35110: Error Extending Targets With JRF Template.

Cause: WLST Error. {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35111: Error Extending Targets With JRF Template.

Cause: Domain Home cannot be empty.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35115: Error Setting target to Managed Server {0}.

Cause: Check the logs for details.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35120: Error Starting Managed Server {0}.

Cause: An internal error has occurred : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35122: Number Format Exception thrown when trying to get nodemanager port.

Cause: The Nodemanager Listen port entry is not present in the nodemanager.properties file or it is not set to numeric value.

Action: Add the Nodemanager port (for example, ListenPort=5556) to the nodemanager.properties file and press Retry button to continue the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35124: Stage Modes 'EXTERNAL_STAGE' and 'NOSTAGE' cannot be set simultaniously.

Cause: Both stage modes 'EXTERNAL_STAGE' and 'NOSTAGE' have been set.

Action: Use only 'EXTERNAL_STAGE' or 'NOSTAGE' mode for deployment
Level: 1

Type: ERROR

Impact: Configuration

CONF-35126: Node Manager Listen Port is set to a negative number.

Cause: Node Manager Listen Port is set to a negative number.

Action: Add the Nodemanager port(Eg: ListenPort=5556) to the nodemanager.properties file and press Retry button to continue the configuration.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35128: Unable to set Attribute 'StartScriptEnabled'.

Cause: Unable to set Attribute 'StartScriptEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35130: Unable to set Attribute 'StartScriptEnabled'.

Cause: Unable to set Attribute 'StartScriptEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35132: Unable to set Attribute 'NativeVersionEnabled'.

Cause: Unable to set Attribute 'NativeVersionEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35134: Unable to set Attribute 'NativeVersionEnabled'.

Cause: Unable to set Attribute 'NativeVersionEnabled' since the NodeManager is already running.The installer needs to set it to 'true'

Action: Stop the Node Manager and retry the installer.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35136: Error while starting the Managed Server.

Cause: An interanal WLST operation has failed.

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35137: Managed Server {0} started in FAILED state.

Cause: An internal error has occured : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35140: Managed Server shutdown command Failed.

Cause: An internal error has occured : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

CONF-35141: Managed Server {0} shutdown timed out.

Cause: An internal error has occured : {0}

Action: See logs for more details.
Level: 1

Type: ERROR

Impact: Configuration

15 DFW-40000 to DFW-40210

DFW-40000: Diagnostic dump {0} has been registered as system scoped.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

DFW-40001: Diagnostic dump {0} has been registered scoped to application {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

DFW-40003: executing diagnostic dump {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

DFW-40004: The requested diagnostic dump {0} is unknown.

Cause: The diagnostic dump {0} has either not been registered or the given name is incorrect.

Action: Ensure that a valid dump name is specified.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40005: The mandatory dump argument {0} is not specified.

Cause: A request to execute a dump was made without specifying all mandatory arguments.

Action: Ensure that all mandatory arguments are specified.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40006: ignoring dump argument {0} as it is not defined for diagnostic dump {1}

Cause: The dump does not accept the specified argument.

Action: Ensure that only arguments defined by the dump are specified.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40007: The diagnostic dump argument {0} should be of type {1}.

Cause: The specified argument is of the wrong type.

Action: Ensure that arguments are of the correct type.
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40008: failed to execute diagnostic dump {0}

Cause: An error occurred during the execution of the dump.

Action: Check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40009: failure creating dump file

Cause: An error occurred creaing a dump file

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40010: failure registering Java Flight Recorder diagnostic dump

Cause: This could be due to JRockit or Java HotSpot not being used as the JVM.

Action: See the reported Exception for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40011: Dump {0} cannot be executed manually.

Cause: Dumps that are designed to be run synchronously during incident creation cannot be executed manually.

Action: No further action is required.
Level: 1

Type: WARNING

Impact: Process

DFW-40100: failed to create ADR Base directory {0}

Cause: An error occurred whilst attempting to create the ADR Base directory required to store captured diagnostics data. This may be due to file or process permissions.

Action: Check that the process has permission to create the directory.
Level: 1

Type: ERROR

Impact: Operating System

DFW-40101: An incident has been signalled with the incident facts: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40102: failure during incident rule processing of incident {0}

Cause: During the processing of the incident rules an error occurred.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40103: failed to execute dump during creation of incident {0}

Cause: An error occurred during the execution of a diagnostic dump.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Other

DFW-40104: incident {0} created with problem key "{1}"

Cause:

Action:
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DFW-40105: failed to execute dump {0} during creation of incident {1}

Cause: An error occurred during the execution of the dump.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40106: failed to load diagnostic rules schema {0}

Cause: The diagnostic rules schema could not be loaded.

Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Process

DFW-40107: failed to parse diagnostic rules

Cause: The diagnostic rules do not conform to the schema.

Action: Fix the diagnostic rules XML to make the rules valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40108: invalid diagnostic rules document

Cause: The diagnostic rules document has invalid content.

Action: See base error for root cause and check process logs for more information.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40109: failed to write and register incident {0} readme file with ADR

Cause: An issue occurred during the registration of the readme file. This does not impact the associated diagnostic dump data.

Action: Check that the process writing the readme file has sufficient privileges.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40110: failure parsing ADRCI XML output

Cause: The XML returned by the ADRCI show incidents command could not be parsed.

Action: Check the process logs for more information.
Level: 1

Type: NOTIFICATION

Impact: Other

DFW-40111: failed to determine incident id and path from adrci output "{0}"

Cause: There was an error executing the command to create an incident using ADRCI.

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Data

DFW-40112: failed to execute the adrci commands "{0}"

Cause: There was an error executing adrci commands; the following errors have been found "{0}"

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40113: failed to execute adrci commands; adrci returned "{0}"

Cause: There was an error executing adrci commands.

Action: Ensure that command line tool "adrci" can be executed from the command line.
Level: 1

Type: ERROR

Impact: Other

DFW-40114: The ADR Product ID exceeds the maximum length {0}.

Cause: The given ADR Product ID is too long.

Action: The ADR Product ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40115: The ADR Instance ID exceeds the maximum length {0}.

Cause: The given ADR Instance ID is too long.

Action: The ADR Instance ID will automatically be truncated. No further action is required.
Level: 1

Type: WARNING

Impact: Files

DFW-40116: failure creating incident

Cause: An error occurred during the creation of an incident.

Action: See base error for root cause anc check process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40117: Invalid fact name "{0}" specified for rule "{1}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

DFW-40118: ADR incident creation is disabled; incident not created.

Cause: Diagnostics Framework was unable to initialize ADR, resulting in ADR creation being disabled.

Action: Check the process logs for more information on why ADR could not be initialized.
Level: 1

Type: NOTIFICATION

Impact: Process

DFW-40119: file {0} cannot be added to incident {1} as it exceeds the maximum filename length of {2} characters

Cause: The specified filename length exceeds the maximum allowed by ADR.

Action: Specify a filename whose length does not exceed the maximum alloweed length.
Level: 1

Type: WARNING

Impact: Files

DFW-40120: failure initializing incident detection log filter

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

DFW-40121: failure creating incident from WLDF notification

Cause: An error occurred whilst attempting to create an incident.

Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40122: incident {0} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40123: file {0} is not registered with incident {1}

Cause: The specified filename is not associated with the incident

Action: Specify the name of a file that is registered with the incident
Level: 1

Type: NOTIFICATION

Impact: Programmatic

DFW-40124: failure adding file {0} to incident {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40125: incident flood controlled with Problem Key "{0}"

Cause: The specified Problem Key is under flood control, due to the volume of incidents with that Problem Key exceeding the maximum incident count.

Action: Inspect the reason for the creation of incidents with the specified Problem Key and resolve the issue.
Level: 1

Type: WARNING

Impact: Other

DFW-40126: incident with Problem Key "{0}" could not be created due to lack of available disk space for incidents; configured maximum is {1} bytes and used is {2} bytes

Cause: The incident with the specified Problem Key could not be created due to lack of available disk space allocated for incidents.

Action: Purge old incidents or increase the maximum allowed disk space for incidents in dfw_config.xml.
Level: 1

Type: WARNING

Impact: Other

DFW-40127: incident filtered with Problem Key "{0}"

Cause: The specified Problem Key is configured to be filtered.

Action: If the problem key should not be filtered modify the DFW configuration to remove the appropriate filter.
Level: 1

Type: WARNING

Impact: Other

DFW-40128: invalid Problem Key filter pattern "{0}"

Cause: The specified Problem Key filter pattern is invalid.

Action: See the base error for the specific error and fix the pattern
Level: 1

Type: WARNING

Impact: Other

DFW-40129: failed to parse incident query "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DFW-40130: failed to load custom rules file "{0}": {1}

Cause: The specified custom rules file could not be loaded.

Action: See the reported exception message for further details.
Level: 1

Type: WARNING

Impact: Other

DFW-40131: the version of the ADR binaries in use are not compatible with the existing ADR data files; backing up existing data from {0} to {1}

Cause: The Windows 64bit ADR binaries cannot read/write ADR data created with the Windows 32bit ADR binaries.

Action: The 32bit ADR data has been backed up. To read/write the backed up data you must use the 32bit ADR binaries.
Level: 1

Type: WARNING

Impact: Other

DFW-40200: failed to load diagnostics configuration schema {0}

Cause: The diagnostics configuration schema could not be loaded. See base exception for root cause

Action: Check that the specified schema exists and is readable.
Level: 1

Type: WARNING

Impact: Configuration

DFW-40201: failed to parse diagnostics configuration

Cause: The diagnostics configuration document does not conform to the schema.

Action: Fix the diagnostic configuration XML to make the configuration valid.
Level: 1

Type: WARNING

Impact: Process

DFW-40202: failed to create diagnostics configuration XML

Cause:

Action:
Level: 1

Type: TRACE

Impact: Process

DFW-40203: failure initializing diagnostics security context

Cause: An error occurred initializing the internal Diagnostic Framework security context.

Action: See the base exception for details, and check the process logs for more information.
Level: 1

Type: WARNING

Impact: Process

DFW-40204: invalid ADR Home path {0}

Cause: The specified ADR Home is not a valid path.

Action: Specify a valid ADR Home path of the form diag/<productType>/<productId>/<instanceId>
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40205: failure loading diagnostic framework configuration file {0}; the default configuration will be used.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40206: failure registering diagnostic rules file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40207: Failure getting WebSphere Cell name for use as ADR Product Id; defaulting it to 'cell'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

DFW-40208: failure setting default uncaught exception handler

Cause:

Action:
Level: 1

Type: WARNING

Impact: Files

DFW-40209: SYNCHRONOUS dump {0} cannot be configured for sampling

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DFW-40210: Not allow to configure {0} for sampling

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

16 DISCMAN-00100 to DISCMAN-90002

DISCMAN-00100: Invalid input parameter.

Cause: Error encountered while processing input parameter.

Action: Check if input parameter is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-00100: Invalid input parameter.

Cause: Error encountered while processing input parameter.

Action: Check if input parameter is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-00101: Invalid {0} input parameter.

Cause: Error encountered while processing input parameter.

Action: Check if input parameter is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-00101: Invalid {0} input parameter.

Cause: Error encountered while processing input parameter.

Action: Check if input parameter is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-10001: ODL message for id ={0} isn't found. "ODL" is "Oracle Diagnostic Logging"

Cause: Failed to get error message by id.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10001: ODL message for id ={0} isn't found. "ODL" is "Oracle Diagnostic Logging"

Cause: Failed to get error message by id.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10003: Full mapping fact is not found, id={0}

Cause: Selected item is inconsistent.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10003: Full mapping fact is not found, id={0}

Cause: Selected item is inconsistent.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10004: Instance Preview (US GAAP taxonomy used: {0}; Use SEC viewer: {1}) {0}, {1} are true or false values; "US GAAP" is "Generally Accepted Accounting Principles (United States)", "SEC" is "Securities and Exchange Commission"

Cause: Showing XBRL report.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10004: Instance Preview (US GAAP taxonomy used: {0}; Use SEC viewer: {1}) {0}, {1} are true or false values; "US GAAP" is "Generally Accepted Accounting Principles (United States)", "SEC" is "Securities and Exchange Commission"

Cause: Showing XBRL report.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10005: Creating US GAAP Instance Transformer (instance path: {0}; taxonomy path: {1}) "US GAAP" is "Generally Accepted Accounting Principles (United States)"

Cause: Initialization US GAAP viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10005: Creating US GAAP Instance Transformer (instance path: {0}; taxonomy path: {1}) "US GAAP" is "Generally Accepted Accounting Principles (United States)"

Cause: Initialization US GAAP viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10006: Creating Generic Viewer transformer (instance path: {0}; generic report path: {1})

Cause: Initialization generic viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10006: Creating Generic Viewer transformer (instance path: {0}; generic report path: {1})

Cause: Initialization generic viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10007: Creating XBRL transformer (instance path: {0}) "Xbrl" is "eXtensible Business Reporting Language"

Cause: Initialization XBRL report viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10007: Creating XBRL transformer (instance path: {0}) "Xbrl" is "eXtensible Business Reporting Language"

Cause: Initialization XBRL report viewer.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10008: Error occurred when retrieving doclet range. Ranges count is not equal to 1: ({0})

Cause: Selected doclet is inconsistent.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10008: Error occurred when retrieving doclet range. Ranges count is not equal to 1: ({0})

Cause: Selected doclet is inconsistent.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10009: Web Service failed to remove mapping with id={0}

Cause: Failed to remove mapping on server side.

Action: Check if mapping exists, probably it was removed by another user.
Level: 32

Type: ERROR

Impact:

DISCMAN-10009: Web Service failed to remove mapping with id={0}

Cause: Failed to remove mapping on server side.

Action: Check if mapping exists, probably it was removed by another user.
Level: 32

Type: ERROR

Impact:

DISCMAN-10010: Mapping to concept '{0}' failed. Document is associated with taxonomy '{1}' but concept belongs to taxonomy '{2}'

Cause: Failed to create mapping for other taxonomy.

Action: Change taxonomy for document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10010: Mapping to concept '{0}' failed. Document is associated with taxonomy '{1}' but concept belongs to taxonomy '{2}'

Cause: Failed to create mapping for other taxonomy.

Action: Change taxonomy for document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10011: Could not create mapping object. Unknown mapping object type {0}.

Cause: Failed to create mapping object for this type.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10011: Could not create mapping object. Unknown mapping object type {0}.

Cause: Failed to create mapping object for this type.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10012: Could not create web service. Unknown web service type {0}.

Cause: Failed to create web service.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10012: Could not create web service. Unknown web service type {0}.

Cause: Failed to create web service.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10013: Exception occurred when querying document mappings, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method QueryDocumentMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10013: Exception occurred when querying document mappings, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method QueryDocumentMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10014: Exception occurred when querying grid mappings, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method QueryGridMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10014: Exception occurred when querying grid mappings, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method QueryGridMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10015: Exception occurred when generating instance, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method Generate).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10015: Exception occurred when generating instance, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method Generate).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10016: Exception occurred when removing mapping, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method RemoveMapping).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10016: Exception occurred when removing mapping, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method RemoveMapping).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10017: Exception occurred when changing mappings taxonomy, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method ChangeMappingsTaxonomy).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10017: Exception occurred when changing mappings taxonomy, {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method ChangeMappingsTaxonomy).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10018: Updating tuple information failed.

Cause: Failed to update TupleInfos.

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10018: Updating tuple information failed.

Cause: Failed to update TupleInfos.

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10019: Try to map abstract element "{0}:{1}."

Cause: You cannot map abstract element.

Action: Select not abstract element.
Level: 32

Type: WARN

Impact:

DISCMAN-10019: Try to map abstract element "{0}:{1}."

Cause: You cannot map abstract element.

Action: Select not abstract element.
Level: 32

Type: WARN

Impact:

DISCMAN-10020: Adding dimension failed.

Cause: Failed to call MappingToolView (method documentMap.addXbrlDimension).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10020: Adding dimension failed.

Cause: Failed to call MappingToolView (method documentMap.addXbrlDimension).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10021: Updating review information failed.

Cause: Failed to call MappingToolView (method registerDocumentMaps).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10021: Updating review information failed.

Cause: Failed to call MappingToolView (method registerDocumentMaps).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10022: Updating contexts failed.

Cause: Failed to call MappingToolView (method setContexts).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10022: Updating contexts failed.

Cause: Failed to call MappingToolView (method setContexts).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10023: Updating tuples information failed.

Cause: Failed to call MappingToolView (method SetTupleInstanceContext).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10023: Updating tuples information failed.

Cause: Failed to call MappingToolView (method SetTupleInstanceContext).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10024: Updating virtual contexts failed.

Cause: Failed to call MappingToolView (method setVirtualContexts).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10024: Updating virtual contexts failed.

Cause: Failed to call MappingToolView (method setVirtualContexts).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10025: Updating units failed.

Cause: Failed to call MappingToolView (method setUnits).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10025: Updating units failed.

Cause: Failed to call MappingToolView (method setUnits).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10026: Updating footnotes failed.

Cause: Failed to call MappingToolView (method setFootnotes).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10026: Updating footnotes failed.

Cause: Failed to call MappingToolView (method setFootnotes).

Action: Reload client and try again.
Level: 32

Type: WARN

Impact:

DISCMAN-10027: Disclosure Management main menu item was not created.

Cause: Client initialization failed (main menu item is not created).

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10027: Disclosure Management main menu item was not created.

Cause: Client initialization failed (main menu item is not created).

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10029: Could not create document UI: unknown native document type.

Cause: Document initialization failed (unknown native document type).

Action: Select other document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10029: Could not create document UI: unknown native document type.

Cause: Document initialization failed (unknown native document type).

Action: Select other document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10030: Document is not a standalone Disclosure Management document.

Cause: You need standalone DiscMan Document for this operation.

Action: Select other document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10030: Document is not a standalone Disclosure Management document.

Cause: You need standalone DiscMan Document for this operation.

Action: Select other document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10031: Only Word Document can be converted to Master Document.

Cause: You need MS Word Document for this operation.

Action: Select MS Word document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10031: Only Word Document can be converted to Master Document.

Cause: You need MS Word Document for this operation.

Action: Select MS Word document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10032: Failed to convert to Master document. Could not connect to security service.

Cause: Failed to connect to security web service (creating Master Document).

Action: Check if Authorization system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10032: Failed to convert to Master document. Could not connect to security service.

Cause: Failed to connect to security web service (creating Master Document).

Action: Check if Authorization system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10033: Expected resources not found. The following files are required: {0}, {1}, {2}.

Cause: Failed to get resource from server.

Action: Check server-side configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10033: Expected resources not found. The following files are required: {0}, {1}, {2}.

Cause: Failed to get resource from server.

Action: Check server-side configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10034: Failed to generate instance preview. Path to SEC viewer source files is invalid. "SEC" is "Securities and Exchange Commission"

Cause: SEC View path is not defined.

Action: Open client Options and configure SEC View path.
Level: 32

Type: ERROR

Impact:

DISCMAN-10034: Failed to generate instance preview. Path to SEC viewer source files is invalid. "SEC" is "Securities and Exchange Commission"

Cause: SEC View path is not defined.

Action: Open client Options and configure SEC View path.
Level: 32

Type: ERROR

Impact:

DISCMAN-10035: {0}

Cause: Error SEC View module.

Action: Check SEC View configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10035: {0}

Cause: Error SEC View module.

Action: Check SEC View configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10036: Global template is not installed. Customization will work with Normal.dot.

Cause: Client initialization failed (cannot created global template).

Action: Check MS Office configuration.
Level: 32

Type: WARN

Impact:

DISCMAN-10036: Global template is not installed. Customization will work with Normal.dot.

Cause: Client initialization failed (cannot created global template).

Action: Check MS Office configuration.
Level: 32

Type: WARN

Impact:

DISCMAN-10037: DiscManDocument.CheckMappingDocumentId: generated new MappingDocumentId value = \"{0}\".

Cause:

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10037: DiscManDocument.CheckMappingDocumentId: generated new MappingDocumentId value = \"{0}\".

Cause:

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10038: Doclet storage is already initialized.

Cause: Client initialization failed (doclet storage is already initialized).

Action: Restart client.
Level: 32

Type: ERROR

Impact:

DISCMAN-10038: Doclet storage is already initialized.

Cause: Client initialization failed (doclet storage is already initialized).

Action: Restart client.
Level: 32

Type: ERROR

Impact:

DISCMAN-10039: Publishing excel doclet failed. Worksheet name is not defined.

Cause: Worksheet name is not defined.

Action: Select correct worksheet before operation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10039: Publishing excel doclet failed. Worksheet name is not defined.

Cause: Worksheet name is not defined.

Action: Select correct worksheet before operation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10040: Error occurred when retrieving doclet subdocument.

Cause: Document initialization failed (subdocument not found).

Action: Reopen document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10040: Error occurred when retrieving doclet subdocument.

Cause: Document initialization failed (subdocument not found).

Action: Reopen document.
Level: 32

Type: ERROR

Impact:

DISCMAN-10041: A primary item mapping must exist prior to domain or member mapping.

Cause: Cannot create dimension mapping without concept mapping.

Action: Create concept mapping before dimension mapping.
Level: 32

Type: ERROR

Impact:

DISCMAN-10041: A primary item mapping must exist prior to domain or member mapping.

Cause: Cannot create dimension mapping without concept mapping.

Action: Create concept mapping before dimension mapping.
Level: 32

Type: ERROR

Impact:

DISCMAN-10042: Highlight is impossible in locked document.

Cause: Cannot highlight mapping inside read only Doclet.

Action: Open Doclet separately.
Level: 32

Type: ERROR

Impact:

DISCMAN-10042: Highlight is impossible in locked document.

Cause: Cannot highlight mapping inside read only Doclet.

Action: Open Doclet separately.
Level: 32

Type: ERROR

Impact:

DISCMAN-10043: Unrecognized Office Application {0}

Cause: Unsupported MS Office application.

Action: See documentation for supported MS Office applications.
Level: 32

Type: ERROR

Impact:

DISCMAN-10043: Unrecognized Office Application {0}

Cause: Unsupported MS Office application.

Action: See documentation for supported MS Office applications.
Level: 32

Type: ERROR

Impact:

DISCMAN-10044: Version: {0}

Cause: Client version.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10044: Version: {0}

Cause: Client version.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10045: Expected Smart View Version: {0} (Build {1}) or higher.

Cause: SmartView version.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10045: Expected Smart View Version: {0} (Build {1}) or higher.

Cause: SmartView version.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10046: Disclosure Management Smart View Extension is shut down.

Cause: Client shutdown.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10046: Disclosure Management Smart View Extension is shut down.

Cause: Client shutdown.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10047: Disclosure Management Smart View Extension is started up.

Cause: Client startup.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10047: Disclosure Management Smart View Extension is started up.

Cause: Client startup.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10048: Cannot get id for message={0}.

Cause: Failed to parse message id.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10048: Cannot get id for message={0}.

Cause: Failed to parse message id.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10049: Failed to replace new page section break with the section break in new doclet. Exception: {0}

Cause: Resources leak.

Action: Restart workstation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10049: Failed to replace new page section break with the section break in new doclet. Exception: {0}

Cause: Resources leak.

Action: Restart workstation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10050: Failed to align table to left. Exception: {0}

Cause: Resources leak.

Action: Restart workstation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10050: Failed to align table to left. Exception: {0}

Cause: Resources leak.

Action: Restart workstation.
Level: 32

Type: ERROR

Impact:

DISCMAN-10051: Failed to add a subdocument to the document. Exception: {0}

Cause: A document of a part of the document is read-only.

Action: Choose the right place in the document for doclet adding.
Level: 32

Type: ERROR

Impact:

DISCMAN-10051: Failed to add a subdocument to the document. Exception: {0}

Cause: A document of a part of the document is read-only.

Action: Choose the right place in the document for doclet adding.
Level: 32

Type: ERROR

Impact:

DISCMAN-10052: Error occurred when connecting to the mapping tool web service. Please check your settings or server state.

Cause: Failed to connect to mapping tool web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10052: Error occurred when connecting to the mapping tool web service. Please check your settings or server state.

Cause: Failed to connect to mapping tool web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10053: Updating review information failed. Exception: {0}

Cause: Failed to call MappingToolView (method registerDocumentMaps).

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10053: Updating review information failed. Exception: {0}

Cause: Failed to call MappingToolView (method registerDocumentMaps).

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10054: Web Service failed to remove mapping with id={0}. Exception: {1}

Cause: Failed to remove mapping on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10054: Web Service failed to remove mapping with id={0}. Exception: {1}

Cause: Failed to remove mapping on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10055: Failed to keep alive session. Exception: {0}

Cause: Failed to update session.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10055: Failed to keep alive session. Exception: {0}

Cause: Failed to update session.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10056: Repository: {0} failed. Exception: {1} {0} is method's name which generated exception

Cause: Failed to call repository session.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10056: Repository: {0} failed. Exception: {1} {0} is method's name which generated exception

Cause: Failed to call repository session.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10057: Excel's Doclet publish failed. Exception: {0}

Cause: Failed to publish Excel's Doclet.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10057: Excel's Doclet publish failed. Exception: {0}

Cause: Failed to publish Excel's Doclet.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10058: Failed to change mappings taxonomy {0}. Exception: {1}

Cause: Failed to update server-side information.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10058: Failed to change mappings taxonomy {0}. Exception: {1}

Cause: Failed to update server-side information.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10059: Common View is not initialized.

Cause: Client initialization failed.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10059: Common View is not initialized.

Cause: Client initialization failed.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10060: Mapping Tool Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create mapping tool web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10060: Mapping Tool Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create mapping tool web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10061: Unpacking Instance Package failed. Exception: {0}

Cause: Failed to extract data from package.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10061: Unpacking Instance Package failed. Exception: {0}

Cause: Failed to extract data from package.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10062: Validation failed. Exception: {0}

Cause: Failed to validate report.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10062: Validation failed. Exception: {0}

Cause: Failed to validate report.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10063: Deletion of {0} failed. Exception: {1} {0} is mapping document name

Cause: Failed to delete file.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10063: Deletion of {0} failed. Exception: {1} {0} is mapping document name

Cause: Failed to delete file.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10064: Writing of {0} failed. Exception: {1} {0} is report name

Cause: Failed to write file.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10064: Writing of {0} failed. Exception: {1} {0} is report name

Cause: Failed to write file.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10065: Export failed. Exception: {0}

Cause: Failed to export report.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10065: Export failed. Exception: {0}

Cause: Failed to export report.

Action: Reload client and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10066: Failed to query document mappings (DocumentId={0}). Exception: {1}

Cause: Failed to get server-side mappings.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10066: Failed to query document mappings (DocumentId={0}). Exception: {1}

Cause: Failed to get server-side mappings.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10067: URL is inconsistent. Exception: {0}

Cause: Failed to create url.

Action: Check your settings and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10067: URL is inconsistent. Exception: {0}

Cause: Failed to create url.

Action: Check your settings and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10068: Report Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create report web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10068: Report Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create report web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10069: Create Doclet failed. Exception: {0}

Cause: Failed to create doclet on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10069: Create Doclet failed. Exception: {0}

Cause: Failed to create doclet on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10070: Create Report failed. Exception: {0}

Cause: Failed to create report on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10070: Create Report failed. Exception: {0}

Cause: Failed to create report on server side.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10071: Repository Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create repository web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10071: Repository Web Service initialization failed (URL={0}). Exception: {1}

Cause: Failed to create repository web service.

Action: Check your settings and server state.
Level: 32

Type: ERROR

Impact:

DISCMAN-10072: Security: {0} failed. Exception: {1} {0} is processing operation

Cause: Failed to call security service.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10072: Security: {0} failed. Exception: {1} {0} is processing operation

Cause: Failed to call security service.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-10073: Failed to create US GAAP report. Exception: {0} "US GAAP" is "Generally Accepted Accounting Principles (United States)"

Cause: Error SEC View module.

Action: Check SEC View configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10073: Failed to create US GAAP report. Exception: {0} "US GAAP" is "Generally Accepted Accounting Principles (United States)"

Cause: Error SEC View module.

Action: Check SEC View configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10074: Word Add-In cannot work with user selection.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10074: Word Add-In cannot work with user selection.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10075: Logon failed. {0} {0} is occurred exception

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10075: Logon failed. {0} {0} is occurred exception

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10076: Mapping {0} contains unsupportable characters and was reduced to '{1}'. {1} is new string without unsupportable characters

Cause: Mapping data contains unsupportable characters.

Action: Remove unsupportable characters.
Level: 32

Type: WARN

Impact:

DISCMAN-10076: Mapping {0} contains unsupportable characters and was reduced to '{1}'. {1} is new string without unsupportable characters

Cause: Mapping data contains unsupportable characters.

Action: Remove unsupportable characters.
Level: 32

Type: WARN

Impact:

DISCMAN-10077: Query View converted. Server: '{0}' App: '{1}' Base: '{2}' Provider: '{3}'.

Cause: Query View converted from Smart View format to Disclosure Management format.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10077: Query View converted. Server: '{0}' App: '{1}' Base: '{2}' Provider: '{3}'.

Cause: Query View converted from Smart View format to Disclosure Management format.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10078: Provider id mapped from value: '{0}' to value: '{1}'.

Cause: Data source provider id was found in mapping table and converted.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10078: Provider id mapped from value: '{0}' to value: '{1}'.

Cause: Data source provider id was found in mapping table and converted.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10079: Full mapping fact with the same id already exists: {0} ({1}:{2}).

Cause: Error at loading review information.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10079: Full mapping fact with the same id already exists: {0} ({1}:{2}).

Cause: Error at loading review information.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10080: SmartView Data Point (col={0}, row={1}, POV={2}, value='{3}', custom data='{4}') does not have view's object. "POV" is "Point Of View"

Cause: SmartView data contains unconsistent record.

Action:
Level: 32

Type: WARN

Impact:

DISCMAN-10080: SmartView Data Point (col={0}, row={1}, POV={2}, value='{3}', custom data='{4}') does not have view's object. "POV" is "Point Of View"

Cause: SmartView data contains unconsistent record.

Action:
Level: 32

Type: WARN

Impact:

DISCMAN-10081: Trying to get a session using a token from connection URL: {0}.

Cause: Trying to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10081: Trying to get a session using a token from connection URL: {0}.

Cause: Trying to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10082: SSO authentication failed. URL: {0}.

Cause: Failed to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10082: SSO authentication failed. URL: {0}.

Cause: Failed to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10083: SSO authentication succeded. URL: {0}.

Cause: Succeded to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10083: SSO authentication succeded. URL: {0}.

Cause: Succeded to get a session using a token.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10084: New data source connection established. URL: {0}. Last connection: {1}.

Cause: New data source connection established.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10084: New data source connection established. URL: {0}. Last connection: {1}.

Cause: New data source connection established.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10085: Data source connection is broken. URL: {0}. Last connection: {1}.

Cause: Data source connection breaked.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10085: Data source connection is broken. URL: {0}. Last connection: {1}.

Cause: Data source connection breaked.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10086: Last successful Disclosure Management connection: {0}.

Cause: Last successful Disclosure Management connection is changed.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10086: Last successful Disclosure Management connection: {0}.

Cause: Last successful Disclosure Management connection is changed.

Action:
Level: 32

Type: INFO

Impact:

DISCMAN-10087: Word doclet publish failed. Exception: {0}.

Cause: Failed to publish Word Doclet.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10087: Word doclet publish failed. Exception: {0}.

Cause: Failed to publish Word Doclet.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10088: Doclet post publish steps failed. Exception: {0}.

Cause: Failed to run post publish steps during a doclet adding.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10088: Doclet post publish steps failed. Exception: {0}.

Cause: Failed to run post publish steps during a doclet adding.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10089: Copying variables from doclet failed. Exception: {0}.

Cause: Failed to copy variables from a doclet to a master document.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10089: Copying variables from doclet failed. Exception: {0}.

Cause: Failed to copy variables from a doclet to a master document.

Action: Restart workstation and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10090: Doclets subdirectory {0} could not be created. Exception: {1}.

Cause: Failed to create a subdirectory.

Action: Check a user's permitions and the new directory parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-10090: Doclets subdirectory {0} could not be created. Exception: {1}.

Cause: Failed to create a subdirectory.

Action: Check a user's permitions and the new directory parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-10091: Failed to copy the file {0} to destination path {1}. Exception: {2}.

Cause: Failed to copy a file.

Action: Check a user's permitions and the new path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10091: Failed to copy the file {0} to destination path {1}. Exception: {2}.

Cause: Failed to copy a file.

Action: Check a user's permitions and the new path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10092: Unexpected error occurred during the duplication of the report. Exception: {0}.

Cause: Unexpected error during the report cloning.

Action: Restart the client application and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10092: Unexpected error occurred during the duplication of the report. Exception: {0}.

Cause: Unexpected error during the report cloning.

Action: Restart the client application and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10093: Doclets copies subdirectory {0} could not be created. Exception: {1}.

Cause: Failed to create a subdirectory.

Action: Check a user's permitions and the new directory parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-10093: Doclets copies subdirectory {0} could not be created. Exception: {1}.

Cause: Failed to create a subdirectory.

Action: Check a user's permitions and the new directory parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-10094: Failed to duplicate a report with id {0} on the server. Exception: {1}.

Cause: Report service failed to duplicate a report.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10094: Failed to duplicate a report with id {0} on the server. Exception: {1}.

Cause: Report service failed to duplicate a report.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10095: Failed to link mapping {0} with range '{1}', it already linked with range '{2}'. {0} is mapping id; {1}, {2} range's information

Cause: Document contains inconsistent mapping information.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10095: Failed to link mapping {0} with range '{1}', it already linked with range '{2}'. {0} is mapping id; {1}, {2} range's information

Cause: Document contains inconsistent mapping information.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10096: Report Service failed to add a unit. Report Id: {0}. Unit properties: {1}. Exception: {2}.

Cause: Report service failed to add a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10096: Report Service failed to add a unit. Report Id: {0}. Unit properties: {1}. Exception: {2}.

Cause: Report service failed to add a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10097: Report Service failed to remove a unit. Report Id: {0}. Unit Id: {1}. Exception: {2}.

Cause: Report service failed to remove a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10097: Report Service failed to remove a unit. Report Id: {0}. Unit Id: {1}. Exception: {2}.

Cause: Report service failed to remove a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10098: Report Service failed to update a unit. Report Id: {0}. Unit properties: {1}. Exception: {2}.

Cause: Report service failed to update a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10098: Report Service failed to update a unit. Report Id: {0}. Unit properties: {1}. Exception: {2}.

Cause: Report service failed to update a unit.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10099: Report Service failed to get units. Report Id: {0}. Exception {1}.

Cause: Report service failed to get units.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10099: Report Service failed to get units. Report Id: {0}. Exception {1}.

Cause: Report service failed to get units.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10100: Report Service failed to add a context. Report Id: {0}. Context properties: {1}. Exception: {2}.

Cause: Report service failed to add a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10100: Report Service failed to add a context. Report Id: {0}. Context properties: {1}. Exception: {2}.

Cause: Report service failed to add a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10101: Report Service failed to remove a context. Report Id: {0}. Context Id: {1}. Exception: {2}.

Cause: Report service failed to remove a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10101: Report Service failed to remove a context. Report Id: {0}. Context Id: {1}. Exception: {2}.

Cause: Report service failed to remove a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10102: Report Service failed to update a context. Report Id: {0}. Context properties: {1}. Exception: {2}.

Cause: Report service failed to update a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10102: Report Service failed to update a context. Report Id: {0}. Context properties: {1}. Exception: {2}.

Cause: Report service failed to update a context.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10103: Report Service failed to get contexts. Report Id: {0}. Exception {1}.

Cause: Report service failed to get contexts.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10103: Report Service failed to get contexts. Report Id: {0}. Exception {1}.

Cause: Report service failed to get contexts.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10104: Migration process failed to create a backup of a document {0} to {1}. Exception: {2}

Cause: Migration process failed to create a backup of a document.

Action: Check a user's permitions.
Level: 32

Type: ERROR

Impact:

DISCMAN-10104: Migration process failed to create a backup of a document {0} to {1}. Exception: {2}

Cause: Migration process failed to create a backup of a document.

Action: Check a user's permitions.
Level: 32

Type: ERROR

Impact:

DISCMAN-10105: Failed to clone mappings on the server. Old document id: {0}. New document Id: {1}. Application id: {2}. New report name: {3}. Exception: {4}.

Cause: Failed to clone mappings on the server.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10105: Failed to clone mappings on the server. Old document id: {0}. New document Id: {1}. Application id: {2}. New report name: {3}. Exception: {4}.

Cause: Failed to clone mappings on the server.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10106: Mapping Tool web service failed to generate XBRL data. Exception: {0}.

Cause: Mapping Tool web service failed to generate XBRL data.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10106: Mapping Tool web service failed to generate XBRL data. Exception: {0}.

Cause: Mapping Tool web service failed to generate XBRL data.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10107: Mapping Tool web service failed to generate IXBRL data. Exception: {0}.

Cause: Mapping Tool web service failed to generate IXBRL data.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10107: Mapping Tool web service failed to generate iXBRL data. Exception: {0}.

Cause: Mapping Tool web service failed to generate IXBRL data.

Action: Check a mapping tool service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10108: Doclet publish process failed to copy the file {0} to destination path {1}. Exception: {2}.

Cause: Failed to copy a file during a doclet publishing.

Action: Check a user's permitions and the new path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10108: Doclet publish process failed to copy the file {0} to destination path {1}. Exception: {2}.

Cause: Failed to copy a file during a doclet publishing.

Action: Check a user's permitions and the new path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10109: Doclet publish process failed to delete the file {0}. Exception: {1}.

Cause: Failed to delete a file during a doclet publishing.

Action: Check a user's permitions and the path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10109: Doclet publish process failed to delete the file {0}. Exception: {1}.

Cause: Failed to delete a file during a doclet publishing.

Action: Check a user's permitions and the path value.
Level: 32

Type: ERROR

Impact:

DISCMAN-10110: Failed to update a report with id {0} on the server. Exception: {1}.

Cause: Report service failed to update a report.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10110: Failed to update a report with id {0} on the server. Exception: {1}.

Cause: Report service failed to update a report.

Action: Check a report service configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-10111: Detailed Tagging turns off (MS Office 2003 Standard Edition doesn't support it).

Cause: MS Office 2003 Standart Edition doesn't support detailed tagging.

Action: Use MS Office 2007 or MS Office 2003 Professional Edition.
Level: 32

Type: WARN

Impact:

DISCMAN-10111: Detailed Tagging turns off (MS Office 2003 Standard Edition doesn't support it).

Cause: MS Office 2003 Standart Edition doesn't support detailed tagging.

Action: Use MS Office 2007 or MS Office 2003 Professional Edition.
Level: 32

Type: WARN

Impact:

DISCMAN-10112: Overlapped cells have been detected. Cannot process XBRL mappings in row {0} of worksheet {1}.

Cause: Excel's doclet contains not properly formated rows with mappings.

Action: Set Wrap Text property for corresponding cells or use Merge for reformatting row.
Level: 32

Type: ERROR

Impact:

DISCMAN-10112: Overlapped cells have been detected. Cannot process XBRL mappings in row {0} of worksheet {1}.

Cause: Excel's doclet contains not properly formated rows with mappings.

Action: Set Wrap Text property for corresponding cells or use Merge for reformatting row.
Level: 32

Type: ERROR

Impact:

DISCMAN-10113: Exception occurred when geting a taxonomy list {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method getTaxonomyList).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10113: Exception occurred when geting a taxonomy list {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method getTaxonomyList).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10114: Exception occurred when previewing a data source mappings duplication. Exception: {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method previewDSMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10114: Exception occurred when previewing a data source mappings duplication. Exception: {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method previewDSMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10115: Exception occurred when duplication data source mappings. Exception: {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method cloneDSMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10115: Exception occurred when duplication data source mappings. Exception: {0}. {0} is occurred exception

Cause: Failed to call MappingTool web service (method cloneDSMappings).

Action: Check if the MappingTool Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-10116: Change taxonomy failed. Exception: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10116: Change taxonomy failed. Exception: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10117: GetTuples for Report Id: {0} tuple descriptor '{1}' failed. Exception: {2}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10117: GetTuples for Report Id: {0} tuple descriptor '{1}' failed. Exception: {2}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-10118: Reduce table width and try again. Exception: {0} {0} is occurred exception

Cause: Failed to align MS Word's table.

Action: Reduce table width and try again.
Level: 32

Type: ERROR

Impact:

DISCMAN-10119: Failed to update MS Excel table alignment. Exception: {0} {0} is occurred exception

Cause: Failed to apply MS Excel table alignment.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-10120: Word doclet: accept Track Changes failed. Exception: {0}. {0} is occurred exception

Cause: Failed to accept Track Change in MS Word's doclet.

Action: Accept Track changes manually in MS Word and Refresh doclet.
Level: 32

Type: ERROR

Impact:

DISCMAN-10121: Failed get Track Changes state in document. Exception: {0}. {0} is occurred exception

Cause: Failed to get Track Changes state in MS Word's document.

Action: Update client version.
Level: 32

Type: ERROR

Impact:

DISCMAN-20201: Failed to parse doclet mapping storage XML.

Cause: Failed to parse doclet mapping storage XML.

Action: Check if doclet storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-20201: Failed to parse doclet mapping storage XML.

Cause: Failed to parse doclet mapping storage XML.

Action: Check if doclet storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-20202: Failed to read doclet mapping storage file.

Cause: Error encountered during reading doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20202: Failed to read doclet mapping storage file.

Cause: Error encountered during reading doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20203: Doclet mapping storage file must be writable.

Cause: Error encountered during writing doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20203: Doclet mapping storage file must be writable.

Cause: Error encountered during writing doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20204: Failed to save doclet mapping.

Cause: Error encountered during writing doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20204: Failed to save doclet mapping.

Cause: Error encountered during writing doclet mapping storage file.

Action: Check if mapping storage file is exixts and accessible.
Level: 32

Type: ERROR

Impact:

DISCMAN-20210: Failed to generate doclet local identifier.

Cause: Error encountered during generating doclet identifier.

Action: Check if database is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20210: Failed to generate doclet local identifier.

Cause: Error encountered during generating doclet identifier.

Action: Check if database is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20211: Specified doclet has not been found.

Cause: Error encountered during checkOut doclet.

Action: Check if database is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20211: Specified doclet has not been found.

Cause: Error encountered during checkOut doclet.

Action: Check if database is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20212: Failed to check in doclet.

Cause: Error encountered during checkIn doclet.

Action: Check if database is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20212: Failed to check in doclet.

Cause: Error encountered during checkIn doclet.

Action: Check if database is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20213: Cannot check in doclet. It must be checked out first.

Cause: Error encountered during checkIn doclet.

Action: Check if report is shecked out.
Level: 32

Type: ERROR

Impact:

DISCMAN-20213: Cannot check in doclet. It must be checked out first.

Cause: Error encountered during checkIn doclet.

Action: Check if report is shecked out.
Level: 32

Type: ERROR

Impact:

DISCMAN-20214: Checking in user has to be same user who checked out the doclet.

Cause: Error encountered during checkIn doclet.

Action: Check if user are allowed to check in.
Level: 32

Type: ERROR

Impact:

DISCMAN-20214: Checking in user has to be same user who checked out the doclet.

Cause: Error encountered during checkIn doclet.

Action: Check if user are allowed to check in.
Level: 32

Type: ERROR

Impact:

DISCMAN-20215: Failed to check out doclet.

Cause: Error encountered during checkOut doclet.

Action: Check if repository is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20215: Failed to check out doclet.

Cause: Error encountered during checkOut doclet.

Action: Check if repository is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20216: The doclet has never been checked in. There is no corresponding content in the repository.

Cause: Error encountered during getting doclet content.

Action: Check if repository is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20216: The doclet has never been checked in. There is no corresponding content in the repository.

Cause: Error encountered during getting doclet content.

Action: Check if repository is up and if doclet is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20217: The doclet has already been checked out.

Cause: Error encountered during checkOut doclet.

Action: Check if doclet is already checked out.
Level: 32

Type: ERROR

Impact:

DISCMAN-20217: The doclet has already been checked out.

Cause: Error encountered during checkOut doclet.

Action: Check if doclet is already checked out.
Level: 32

Type: ERROR

Impact:

DISCMAN-20218: Failed to get content of doclet.

Cause: Error encountered during getting doclet content.

Action: Check if repository is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20218: Failed to get content of doclet.

Cause: Error encountered during getting doclet content.

Action: Check if repository is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-20219: Bad doclet id.

Cause: Error encountered during getting doclet content. Doclet id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20219: Bad doclet id.

Cause: Error encountered during getting doclet content. Doclet id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20220: Bad unit id.

Cause: Passed unit or report id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20220: Bad unit id.

Cause: Passed unit or report id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20221: Bad context id.

Cause: Passed context or report id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20221: Bad context id.

Cause: Passed context or report id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-20222: Specified context has not been found.

Cause: Error encountered during checkout context.

Action: Check if database is up and if context is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20222: Specified context has not been found.

Cause: Error encountered during checkout context.

Action: Check if database is up and if context is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20223: Specified unit has not been found.

Cause: Error encountered during checkout unit.

Action: Check if database is up and if unit is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20223: Specified unit has not been found.

Cause: Error encountered during checkout unit.

Action: Check if database is up and if unit is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-20224: Bad footnote id.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-20225: Specified footnote has not been found.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-30201: Failed to parse report storage XML.

Cause: Error encountered during parsing report storage XML.

Action: Check if report storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-30201: Failed to parse report storage XML.

Cause: Error encountered during parsing report storage XML.

Action: Check if report storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-30202: Failed to read report storage file.

Cause: Error encountered during reading report storage XML.

Action: Check if report storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-30202: Failed to read report storage file.

Cause: Error encountered during reading report storage XML.

Action: Check if report storage XML is well formed.
Level: 32

Type: ERROR

Impact:

DISCMAN-30203: Report storage file must be writable.

Cause: Error encountered during writing report storage XML.

Action: Check if report storage XML has writable permisssion.
Level: 32

Type: ERROR

Impact:

DISCMAN-30203: Report storage file must be writable.

Cause: Error encountered during writing report storage XML.

Action: Check if report storage XML has writable permisssion.
Level: 32

Type: ERROR

Impact:

DISCMAN-30204: Failed to save report.

Cause: Error encountered during saving report.

Action: Check if Repository Web Service is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-30204: Failed to save report.

Cause: Error encountered during saving report.

Action: Check if Repository Web Service is up.
Level: 32

Type: ERROR

Impact:

DISCMAN-30206: Report with the specified id has not been found.

Cause: Error encountered during creating master document.

Action: Check if database is up and if report is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-30206: Report with the specified id has not been found.

Cause: Error encountered during creating master document.

Action: Check if database is up and if report is created.
Level: 32

Type: ERROR

Impact:

DISCMAN-30207: Failed to log audit record.

Cause: Error encountered during auditing.

Action: Check if Audit Web Service is up.
Level: 32

Type: INFO

Impact:

DISCMAN-30207: Failed to log audit record.

Cause: Error encountered during auditing.

Action: Check if Audit Web Service is up.
Level: 32

Type: INFO

Impact:

DISCMAN-30208: Bad report id.

Cause: Report id is in bad format or is not specified.

Action: The error is in the web service client. It should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30208: Bad report id or report properties.

Cause: Report id is in bad format or is not specified.

Action: The error is in the web service client. It should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30209: Disclosure Management reports: database access error.

Cause: Disclosure Management reports: database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-30209: Disclosure Management reports: database access error.

Cause: Disclosure Management reports: database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-30210: Context name for given report already exists

Cause: Disclosure Management reports: duplicate context name.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30210: Context name for given report already exists

Cause: Disclosure Management reports: duplicate context name.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30211: Unit name for given report already exists

Cause: Disclosure Management reports: duplicate unit name.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30211: Unit name for given report already exists

Cause: Disclosure Management reports: duplicate unit name.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30212: Context name does not comply xbrl standard

Cause: Disclosure Management reports: context name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30212: Context name does not comply xbrl standard

Cause: Disclosure Management reports: context name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30213: Unit name does not comply xbrl standard

Cause: Disclosure Management reports: wrong unit name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30213: Unit name does not comply xbrl standard

Cause: Disclosure Management reports: wrong unit name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30214: Footnote name does not comply xbrl standard

Cause: Disclosure Management reports: wrong footnote name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30214: Footnote name does not comply xbrl standard

Cause: Disclosure Management reports: wrong footnote name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30215: Footnote name must be unique

Cause: Disclosure Management: footnote name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30215: Footnote name must be unique

Cause: Disclosure Management: footnote name violation.

Action: Client should choose another name.
Level: 32

Type: ERROR

Impact:

DISCMAN-30216: Failed to get mappings for report

Cause: Report Service: failed to process mappings for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30216: Failed to get mappings for report

Cause: Report Service: failed to process mappings for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30217: Failed to encode report object

Cause: Report Service: failed to encode information for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30217: Failed to encode report object

Cause: Report Service: failed to encode information for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30218: Failed to decode report object

Cause: Report Service: failed to decode information for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30218: Failed to decode report object

Cause: Report Service: failed to decode information for report.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30219: Specified counter has not been found

Cause: Report Service: passed counter id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30219: Specified counter has not been found

Cause: Report Service: passed counter id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30220: Specified application id could not be null

Cause: Report Service: Specified application id could not be null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30220: Specified application id could not be null

Cause: Report Service: Specified application id could not be null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30221: Specified category has not been found

Cause: Report Service: passed category id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30221: Specified category has not been found

Cause: Report Service: passed category id is invalid or null.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30222: Passed report should have only one doclet

Cause: Report Service: Passed report should have only one doclet.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30222: Passed report should have only one doclet

Cause: Report Service: Passed report should have only one doclet.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30223: Specified doclet part has not been found

Cause: Report Service: Specified doclet part has not been found.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30223: Specified doclet part has not been found

Cause: Report Service: Specified doclet part has not been found.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30224: Bad doclet part id

Cause: Report Service: Bad doclet part id.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30224: Bad doclet part id

Cause: Report Service: Bad doclet part id.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30225: Failed to change taxonomy

Cause: Report Service: Failed to change taxonomy.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30225: Failed to change taxonomy

Cause: Report Service: Failed to change taxonomy.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30226: Failed to clone tuples

Cause: Report Service: Failed to clone tuples.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30226: Failed to clone tuples

Cause: Report Service: Failed to clone tuples.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30227: The report (id:{0}, name:{1}, version:{2}) has already been migrated.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-30228: Xml data should be in valid format

Cause: Report Service: Xml data should be in valid format.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30229: Entity manager should be initialized first

Cause: Report Service: Entity manager should be initialized first.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30230: Failed to load the destination taxonomy.

Cause: Report Service: Failed to load the destination taxonomy.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-30231: Failed to parse rollover rule with source {0} and target {1}

Cause: Report Service: Failed to parse rollover rule.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-40201: Authentication system is unavailable.

Cause: Error encountered during Authentication system configuration.

Action: Check if Authentication system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40201: Authentication system is unavailable.

Cause: Error encountered during Authentication system configuration.

Action: Check if Authentication system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40202: No session state with given id was found.

Cause: Error encountered during Authentication system configuration.

Action: Check if Authentication system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40202: No session state with given id was found.

Cause: Error encountered during Authentication system configuration.

Action: Check if Authentication system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40210: The user name or password is incorrect.

Cause: Error encountered during login.

Action: Check if CSS is up and if input parameter credentials is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-40210: The user name or password is incorrect.

Cause: Error encountered during login.

Action: Check if CSS is up and if input parameter credentials is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-40220: Authorization failed. You have no or limited access to Disclosure Management application.

Cause: Error encountered during authorization.

Action: Check if Authorization system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40220: Authorization failed. You have no or limited access to Disclosure Management application.

Cause: Error encountered during authorization.

Action: Check if Authorization system is configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40301: No session state with given id was found.

Cause: No state with given id was found.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-40301: No session state with given id was found.

Cause: No state with given id was found.

Action: Web service client error. Should be addressed by support or development.
Level: 32

Type: ERROR

Impact:

DISCMAN-40302: Disclosure Management state service: database access error.

Cause: Database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40302: Disclosure Management state service: database access error.

Cause: Database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40303: Disclosure Management state service: failed to get session from database.

Cause: Failed to get session from database.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40303: Disclosure Management state service: failed to get session from database.

Cause: Failed to get session from database.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40304: Disclosure Management state service: failed to get role from database.

Cause: Failed to get role from database.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40304: Disclosure Management state service: failed to get role from database.

Cause: Failed to get role from database.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-40305: Session was expired.

Cause: Session was expired.

Action: Login again.
Level: 32

Type: ERROR

Impact:

DISCMAN-40305: Session was expired.

Cause: Session was expired.

Action: Login again.
Level: 32

Type: ERROR

Impact:

DISCMAN-50000: Failed to initialize XBRL Processor.

Cause: XBR not initialized properly.

Action: Check if resources are present for the XBRL Processing Engine.
Level: 32

Type: ERROR

Impact:

DISCMAN-50000: Failed to initialize XBRL Processor.

Cause: XBR not initialized properly.

Action: Check if resources are present for the XBRL Processing Engine.
Level: 32

Type: ERROR

Impact:

DISCMAN-50001: Failed to shut down XBRL Processor.

Cause: Failed to close the xbrl instance.

Action: Shut down the processor externally.
Level: 32

Type: ERROR

Impact:

DISCMAN-50001: Failed to shut down XBRL Processor.

Cause: Failed to close the xbrl instance.

Action: Shut down the processor externally.
Level: 32

Type: ERROR

Impact:

DISCMAN-50002: Failed to load the taxonomy.

Cause: Failed to load taxonomy.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50002: Failed to load the taxonomy.

Cause: Failed to load taxonomy.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50003: Failed to generate the tree structure for this taxonomy.

Cause: Failed to walk the node.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50003: Failed to generate the tree structure for this taxonomy.

Cause: Failed to walk the node.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50004: Failed to get the tree node detail information.

Cause: Failed to load detail information for node.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50004: Failed to get the tree node detail information.

Cause: Failed to load detail information for node.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50005: Failed to build ADF tree model.

Cause: Failed build the tree model for taxonomy.

Action: Check taxonomy structure.
Level: 32

Type: ERROR

Impact:

DISCMAN-50005: Failed to build ADF tree model.

Cause: Failed build the tree model for taxonomy.

Action: Check taxonomy structure.
Level: 32

Type: ERROR

Impact:

DISCMAN-50006: Failed to get all links for taxonomy.

Cause: Failed to get all Links for taxonomy.

Action: Check taxonomy all Link definition is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50006: Failed to get all links for taxonomy.

Cause: Failed to get all Links for taxonomy.

Action: Check taxonomy all Link definition is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50007: Failed to get tree node information for this taxonomy.

Cause: Failed to get dimension member for taxonomy.

Action: Check taxonomy dimension data is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50007: Failed to get tree node information for this taxonomy.

Cause: Failed to get dimension member for taxonomy.

Action: Check taxonomy dimension data is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50008: Error occurred executing request for mapping tool. See Error logs for details.

Cause: Error occurred executing request for mapping tool.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50008: Error occurred executing request for mapping tool. See Error logs for details.

Cause: Error occurred executing request for mapping tool.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50009: Failed to load property file mappingtool.properties.

Cause: Cannot find property file.

Action: Check if mappingtool.properties is exist.
Level: 32

Type: ERROR

Impact:

DISCMAN-50009: Failed to load property file mappingtool.properties.

Cause: Cannot find property file.

Action: Check if mappingtool.properties is exist.
Level: 32

Type: ERROR

Impact:

DISCMAN-50010: Set up DISCMAN_HOME in server first.

Cause: DISCMAN_HOME doesn't exist.

Action: Please specify setting for DISCMAN_HOME.
Level: 32

Type: ERROR

Impact:

DISCMAN-50010: Set up DISCMAN_HOME in server first.

Cause: DISCMAN_HOME doesn't exist.

Action: Please specify setting for DISCMAN_HOME.
Level: 32

Type: ERROR

Impact:

DISCMAN-50011: Incorrect number of parameters was passed. Expecting {0}, found {1}.

Cause: Incorrect number of parameters was passed.

Action: Please check number of parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-50011: Incorrect number of parameters was passed. Expecting {0}, found {1}.

Cause: Incorrect number of parameters was passed.

Action: Please check number of parameters.
Level: 32

Type: ERROR

Impact:

DISCMAN-50012: Error occurred in generating XBRL instance. Check server logs for details.

Cause: Error occurred in generating XBRL instance.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50012: Error occurred in generating XBRL instance. Check server logs for details.

Cause: Error occurred in generating XBRL instance.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50013: Invalid date argument was passed.

Cause: Invalid date argument was passed.

Action: Specify correct arguments.
Level: 32

Type: ERROR

Impact:

DISCMAN-50013: Invalid date argument was passed.

Cause: Invalid date argument was passed.

Action: Specify correct arguments.
Level: 32

Type: ERROR

Impact:

DISCMAN-50014: Can't convert FR query to grid descriptor.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50015: Error occurred in parsing the XML.

Cause: Error occurred in parsing the XML.

Action: Check XML structure.
Level: 32

Type: ERROR

Impact:

DISCMAN-50015: Error occurred in parsing the XML.

Cause: Error occurred in parsing the XML.

Action: Check XML structure.
Level: 32

Type: ERROR

Impact:

DISCMAN-50016: Invalid argument was passed in the generation of XBRL Instance. The taxonomy name is null or empty.

Cause: The client passed an invalid parameter.

Action: Check if the document has mappings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50016: Invalid argument was passed in the generation of XBRL Instance. The taxonomy name is null or empty.

Cause: The client passed an invalid parameter.

Action: Check if the document has mappings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50017: Error was encountered in the querying of Grid mappings.

Cause: Error encountered while searching for context.

Action: Check if the database server is up or the database connection. Check if the XML query is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50017: Error was encountered in the querying of Grid mappings.

Cause: Error encountered while searching for context.

Action: Check if the database server is up or the database connection. Check if the XML query is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50018: Error was encountered in the querying of Document mappings.

Cause: Error encountered while searching for context.

Action: Check if the database server is up or the database connection. Check if the XML query is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50018: Error was encountered in the querying of Document mappings.

Cause: Error encountered while searching for context.

Action: Check if the database server is up or the database connection. Check if the XML query is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50019: Invalid Argument was passed when retrieving the taxonomy concept.

Cause: Invalid Argument was passed.

Action: Check if Argument is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50019: Invalid Argument was passed when retrieving the taxonomy concept.

Cause: Invalid Argument was passed.

Action: Check if Argument is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50020: Unknown application id was passed.

Cause: Unknown application id was passed.

Action: Check if applicationID is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50020: Unknown application id was passed.

Cause: Unknown application id was passed.

Action: Check if applicationID is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-50021: No reference was specified in the context.

Cause: No reference was specified in the context.

Action: Check context.
Level: 32

Type: ERROR

Impact:

DISCMAN-50021: No reference was specified in the context.

Cause: No reference was specified in the context.

Action: Check context.
Level: 32

Type: ERROR

Impact:

DISCMAN-50022: No entity was specified in the context.

Cause: No entity was specified in the context.

Action: Check context.
Level: 32

Type: ERROR

Impact:

DISCMAN-50022: No entity was specified in the context.

Cause: No entity was specified in the context.

Action: Check context.
Level: 32

Type: ERROR

Impact:

DISCMAN-50023: Failed to generate the dimension member tree for selected primary item.

Cause: XBRL Processing Error.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50023: Failed to generate the dimension member tree for selected primary item.

Cause: XBRL Processing Error.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50024: Failed to generate the tuple group tree.

Cause: Failed to create the empty tuple instance tree model.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50024: Failed to generate the tuple group tree.

Cause: Failed to create the empty tuple instance tree model.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50025: Unable to create explicit dimension mapping for dimension name {0} with dimension value {1}.

Cause: Unable to create explicit dimension mapping.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50025: Unable to create explicit dimension mapping for dimension name {0} with dimension value {1}.

Cause: Unable to create explicit dimension mapping.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50026: Unable to create typed dimension mapping for dimension name {0} with dimension value {1}.

Cause: Unable to create typed dimension mapping.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50026: Unable to create typed dimension mapping for dimension name {0} with dimension value {1}.

Cause: Unable to create typed dimension mapping.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50027: Failed to export errors.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50028: No XBRL concept mappings was found. Cannot generate XBRL instance.

Cause: No mapping was passed to the instance generator.

Action: Make sure at least one mapping is present when generating an instance.
Level: 32

Type: ERROR

Impact:

DISCMAN-50028: No XBRL concept mappings was found. Cannot generate XBRL instance.

Cause: No mapping was passed to the instance generator.

Action: Make sure at least one mapping is present when generating an instance.
Level: 32

Type: ERROR

Impact:

DISCMAN-50030: Failed to load the taxonomy file list.

Cause: Failed to read the taxonomy file list.

Action: Check to make sure property file exist.
Level: 32

Type: ERROR

Impact:

DISCMAN-50030: Failed to load the taxonomy file list.

Cause: Failed to read the taxonomy file list.

Action: Check to make sure property file exist.
Level: 32

Type: ERROR

Impact:

DISCMAN-50032: Failed to create UBMatrixTaxoAdapter object.

Cause: Failed create ubmatrixAdapter object.

Action: Check to see if process engine configured properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50032: Failed to create UBMatrixTaxoAdapter object.

Cause: Failed create ubmatrixAdapter object.

Action: Check to see if process engine configured properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50033: Failed to close XBRL Processor.

Cause: Failed to close the xbrl instance.

Action: Close the processor externally.
Level: 32

Type: ERROR

Impact:

DISCMAN-50033: Failed to close XBRL Processor.

Cause: Failed to close the xbrl instance.

Action: Close the processor externally.
Level: 32

Type: ERROR

Impact:

DISCMAN-50034: Failed to build the XBRL Query.

Cause: Failed to building XBRL Query.

Action: Check taxonomy file is valid..
Level: 32

Type: ERROR

Impact:

DISCMAN-50034: Failed to build the XBRL Query.

Cause: Failed to building XBRL Query.

Action: Check taxonomy file is valid..
Level: 32

Type: ERROR

Impact:

DISCMAN-50035: Failed to get the concept label.

Cause: Failed to get label for concept.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50035: Failed to get the concept label.

Cause: Failed to get label for concept.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50036: Failed to get the concept.

Cause: Failed to get concept from fullName.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50036: Failed to get the concept.

Cause: Failed to get concept from fullName.

Action: Check taxonomy concept is valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50039: Failed to validate instance document

Cause: Failed to validate instance document.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50039: Failed to validate instance document

Cause: Failed to validate instance document.

Action: Check processing engine configured properly and taxonomy file is also valid.
Level: 32

Type: ERROR

Impact:

DISCMAN-50040: Failed to execute DTS query.

Cause: Failed to generate HTML instance report from instance document.

Action: Check that instance document is proper and valid one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50040: Failed to execute DTS query.

Cause: Failed to generate HTML instance report from instance document.

Action: Check that instance document is proper and valid one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50041: Failed to generate HTML instance report from DTS object.

Cause: Failed to generate HTML instance report from DTS object.

Action: Check that DTS object is proper and valid one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50041: Failed to generate HTML instance report from DTS object.

Cause: Failed to generate HTML instance report from DTS object.

Action: Check that DTS object is proper and valid one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50042: Failed to generate HTML instance report from instance file.

Cause: Failed to execute DTS query.

Action: Check the query syntax and other details passed.
Level: 32

Type: ERROR

Impact:

DISCMAN-50042: Failed to generate HTML instance report from instance file.

Cause: Failed to execute DTS query.

Action: Check the query syntax and other details passed.
Level: 32

Type: ERROR

Impact:

DISCMAN-50043: No mappings with specified id were found.

Cause: No mappings with specified id were found.

Action: Check the query syntax and other details passed.
Level: 32

Type: ERROR

Impact:

DISCMAN-50043: No mappings with specified id were found.

Cause: No mappings with specified id were found.

Action: Check the query syntax and other details passed.
Level: 32

Type: ERROR

Impact:

DISCMAN-50045: Target taxonomy cannot be found.

Cause: Target taxonomy cannot be found.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50045: Target taxonomy cannot be found.

Cause: Target taxonomy cannot be found.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50046: Failed to change taxonomy.

Cause: Failed to change taxonomy.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50046: Failed to change taxonomy.

Cause: Failed to change taxonomy.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50047: Error was encountered when registering the Document mappings.

Cause: Error was encountered when registering the Document mappings.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50047: Error was encountered when registering the Document mappings.

Cause: Error was encountered when registering the Document mappings.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50048: Mapping already exists.

Cause: Mapping already exists.

Action: Choose another one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50048: Mapping already exists.

Cause: Mapping already exists.

Action: Choose another one.
Level: 32

Type: ERROR

Impact:

DISCMAN-50049: Unable to create mapping.

Cause: Unable to create mapping.

Action: Check your document state.
Level: 32

Type: ERROR

Impact:

DISCMAN-50049: Unable to create mapping.

Cause: Unable to create mapping.

Action: Check your document state.
Level: 32

Type: ERROR

Impact:

DISCMAN-50050: Failed to obtain data type of cache from DTS: {0} for concept: {1}.

Cause: General failure while trying to find if the concept is numeric.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50050: Failed to obtain data type of cache from DTS: {0} for concept: {1}.

Cause: General failure while trying to find if the concept is numeric.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50051: Data type of cache is 'null' for DTS: {0} and concept: {1}.

Cause: Data type cache is unavailable for the Discoverable Taxonomy Set.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50051: Data type of cache is 'null' for DTS: {0} and concept: {1}.

Cause: Data type cache is unavailable for the Discoverable Taxonomy Set.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50052: Data type of concept:{1} not found in DTS: {0}.

Cause: Can't find type for the concept.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50052: Data type of concept:{1} not found in DTS: {0}.

Cause: Can't find type for the concept.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50053: Invalid data type was passed (null) when checking inheritance for base type {0}.

Cause: Data Type for the concept can not be categorized.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50053: Invalid data type was passed (null) when checking inheritance for base type {0}.

Cause: Data Type for the concept can not be categorized.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50054: Failed to find an XBRL Domain object for the concept: {0}.

Cause: Concept cannot be found in the taxonomy.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50054: Failed to find an XBRL Domain object for the concept: {0}.

Cause: Concept cannot be found in the taxonomy.

Action: Check if taxonomies are correctly configured. Restart Server.
Level: 32

Type: ERROR

Impact:

DISCMAN-50055: Failed to check if data type:{1} from DTS: {0} is inherited from data type: {2}.

Cause: Failed to execute DTS query.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50055: Failed to check if data type:{1} from DTS: {0} is inherited from data type: {2}.

Cause: Failed to execute DTS query.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50056: Failed to get XBRL Domain object for data type: {1} from DTS {0}.

Cause: Failed to get XBRL Domain object.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50056: Failed to get XBRL Domain object for data type: {1} from DTS {0}.

Cause: Failed to get XBRL Domain object.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50057: Failed to find fact in the instance document for mapping: {0}

Cause: Failed to find fact in the instance document.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50057: Failed to find fact in the instance document for mapping: {0}

Cause: Failed to find fact in the instance document.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50058: Failed to get value for XBRL unit's measure: {0}

Cause: Failed to get value for XBRL unit's measure.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50058: Failed to get value for XBRL unit's measure: {0}

Cause: Failed to get value for XBRL unit's measure.

Action: Check app server running properly.
Level: 32

Type: ERROR

Impact:

DISCMAN-50059: Failed to find namespace URI for measure prefix: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50059: Failed to find namespace URI for measure prefix: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50060: Failed to extract 'period' element for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50060: Failed to extract 'period' element for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50061: Failed to extract 'end-date' element for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50061: Failed to extract 'end-date' element for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50062: Failed to get dates values for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50062: Failed to get dates values for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50063: 'identifier' element has not been found for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50063: 'identifier' element has not been found for XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50064: Failed to extract identification information from XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50064: Failed to extract identification information from XBRL context: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50065: Failed to get prefixes for dimension/member pair: {0}/{1}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50065: Failed to get prefixes for dimension/member pair: {0}/{1}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50066: Failed to execute DTS query: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50066: Failed to execute DTS query: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50067: XBRL fact {0} has no 'id' attribute. Skipped.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50067: Failed to execute DTS query: {0} for object: {1}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50068: Failed to create temporary directories.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50068: Failed to create temporary directories.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50069: Failed to deflate source archive to the temporary directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50069: Failed to deflate source archive to the temporary directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50070: Inline XBRL entry point file has not been found: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50070: Inline XBRL entry point file has not been found: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50071: Failed to initialize XML processor.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50071: Failed to initialize XML processor.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50072: Failed to parse XML file: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50072: Failed to parse XML file: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50073: Failed to get content of the directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50073: Failed to get content of the directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50074: Failed to copy file from {0} to {1}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50074: Failed to copy file from {0} to {1}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50075: Failed to create archive for directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50075: Failed to create archive for directory: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50076: Failed to open XML file for writing: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50076: Failed to open XML file for writing: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50077: Failed to save XML file: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50077: Failed to save XML file: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50078: Failed to close XML file after content has been written: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50078: Failed to close XML file after content has been written: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50079: Custom date transformation is required for value {0}, but no custom pattern has been specified.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50079: Custom date transformation is required for value {0}, but no custom pattern has been specified.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50080: Custom numeric transformation is required for value {0}, but no custom parameters have been specified.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50080: Custom numeric transformation is required for value {0}, but no custom parameters have been specified.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50081: 'dash-to-zero' transformation required for value {0} is applicable only for value: \'-\'.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50081: 'dash-to-zero' transformation required for value {0} is applicable only for value: \'-\'.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50082: Failed to parse numeric value {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50082: Failed to parse numeric value {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50083: Failed to parse date value {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50083: Failed to parse date value {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50084: Due to failure of parsing original value will be used: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50084: Due to failure of parsing original value will be used: {0}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50085: The mapping for Inline XBRL has not been found: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50085: The mapping for Inline XBRL has not been found: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50086: The fact for Inline XBRL has not been found in instance document: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50086: The fact for Inline XBRL has not been found in instance document: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50087: xhtml:body element has not been found in the main document. The ix:header won't be generated.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50087: xhtml:body element has not been found in the main document. The ix:header won't be generated.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50088: Unknown DMHTML element found in Inline XBRL template (only "http://oracle/discman/ixbrl:mapping" and "http://oracle/discman/ixbrl:footnote" are expected).

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50088: Unknown DMHTML element found in Inline XBRL template (only "http://oracle/discman/ixbrl:mapping" and "http://oracle/discman/ixbrl:footnote" are expected).

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50089: Mapping id has not been specified for mapping in Inline XBRL template.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50089: Mapping id has not been specified for mapping in Inline XBRL template.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50090: Can't get extension for file: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50090: Can't get extension for file: {0}

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50091: Can't find MIME type for file: {0}. Content can't be embedded.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50091: Can't find MIME type for file: {0}. Content can't be embedded.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50092: Can't encode file: {0}. Content can't be embedded.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50092: Can't encode file: {0}. Content can't be embedded.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50093: The path: {0} has to be relative.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50093: The path: {0} has to be relative.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50094: The file: {0} has to be within directory: {1}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50094: The file: {0} has to be within directory: {1}.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50095: The file: {0} does not exist or cannot be read.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50095: The file: {0} does not exist or cannot be read.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50096: Can't set schema reference in generated XBRL instance document.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50096: Can't set schema reference in generated XBRL instance document.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50097: Null DTS Instance was detected.

Cause: Null DTS Instance was detected.

Action: Check server config settings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50097: Null DTS Instance was detected.

Cause: Null DTS Instance was detected.

Action: Check server config settings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50098: Null DTS Taxonomy was detected.

Cause: Null DTS Taxonomy was detected.

Action: Check server config settings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50098: Null DTS Taxonomy was detected.

Cause: Null DTS Taxonomy was detected.

Action: Check server config settings.
Level: 32

Type: ERROR

Impact:

DISCMAN-50099: Errors detected while initializing XBRL.

Cause: Errors detected while initializing XBRL.

Action: Enable debug level and do the use case again. Check server logs after that.
Level: 32

Type: ERROR

Impact:

DISCMAN-50099: Errors detected while initializing XBRL.

Cause: Errors detected while initializing XBRL.

Action: Enable debug level and do the use case again. Check server logs after that.
Level: 32

Type: ERROR

Impact:

DISCMAN-50100: Failed to create xml query for datasource mappings.

Cause: Failed to create xml query for datasource mappings.

Action: Enable debug level and do the use case again. Check server logs after that.
Level: 32

Type: ERROR

Impact:

DISCMAN-50100: Failed to create xml query for datasource mappings.

Cause: Failed to create xml query for datasource mappings.

Action: Enable debug level and do the use case again. Check server logs after that.
Level: 32

Type: ERROR

Impact:

DISCMAN-50101: Failed to clone datasource mappings.

Cause: Failed to clone datasource mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50101: Failed to clone datasource mappings.

Cause: Failed to clone datasource mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50102: Failed to query report level mappings.

Cause: Failed to query report level mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50102: Failed to query report level mappings.

Cause: Failed to query report level mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50103: Failed to delete report level mappings.

Cause: Failed to delete report level mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50103: Failed to delete report level mappings.

Cause: Failed to delete report level mappings.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50104: Failed to save XBRL Context.

Cause: Failed to save XBRL Context.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50104: Failed to save XBRL Context.

Cause: Failed to save XBRL Context.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50105: No calculation trace done because of duplicate errors. Duplicate count is {0}. Duplicate count but not equal is {1}.

Cause: No calculation trace done because of duplicate errors.

Action: Fix duplicate mappings first so that calculation trace can be done.
Level: 32

Type: ERROR

Impact:

DISCMAN-50105: No calculation trace done because of duplicate errors. Duplicate count is {0}. Duplicate count but not equal is {1}.

Cause: No calculation trace done because of duplicate errors.

Action: Fix duplicate mappings first so that calculation trace can be done.
Level: 32

Type: ERROR

Impact:

DISCMAN-50106: XBRL fact {0} has no 'id' attribute. Skipped.

Cause: XBRL fact has no 'id' attribute. Skipped.

Action: Check server-side log.
Level: 32

Type: WARN

Impact:

DISCMAN-50107: No calculation trace done because of bad format warnings.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-50108: Failed to create XBRL fact for concept {0}.

Cause: Failed to create XBRL fact for concept.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-50109: Failed to parse text block types xml.

Cause: Failed to parse text block types xml.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53001: Failed initiate the taxonomy cache cleaner

Cause: Failed initiate the taxonomy cache cleaner

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53001: Failed initiate the taxonomy cache cleaner

Cause: Failed initiate the taxonomy cache cleaner

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53002: Error was encountered when working with mapping storage

Cause: Error was encountered when working with mapping storage

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53002: Error was encountered when working with mapping storage

Cause: Error was encountered when working with mapping storage

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53003: Error was encountered when working with annotation storage

Cause: Error was encountered when working with annotation storage

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53003: Error was encountered when working with annotation storage

Cause: Error was encountered when working with annotation storage

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53004: Failed to get concept from taxonomy

Cause: Failed to get concept from taxonomy

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53004: Failed to get concept from taxonomy

Cause: Failed to get concept from taxonomy

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53005: Error was encountered when trying to suppress explicit fact

Cause: Error was encountered when trying to suppress explicit fact

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53005: Error was encountered when trying to suppress explicit fact

Cause: Error was encountered when trying to suppress explicit fact

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53006: Passed parameter {0} can't be null

Cause: Passed parameter can't be null

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53006: Passed parameter {0} can't be null

Cause: Passed parameter can't be null

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53007: Concept id in tuple and concept id itself should be equals

Cause: Concept id in tuple and concept id itself should be equals

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53007: Concept id in tuple and concept id itself should be equals

Cause: Concept id in tuple and concept id itself should be equals

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53008: Can not get namespace for taxonomy

Cause: Can not get namespace for taxonomy

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53008: Can not get namespace for taxonomy

Cause: Can not get namespace for taxonomy

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53009: The concept {0} from taxonomy {1} has already been associated with the selected data point.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-53009: The concept {0} from taxonomy {1} has already been associated with the selected data point.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-53010: A dynamic fact is expected. Explicit fact has been found instead.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-53011: Failed to delete a fact.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-53012: Data source context mapping with global scope has been created.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-53013: Data source unit mapping with global scope has been created.

Cause:

Action:
Level: 32

Type:

Impact:

DISCMAN-53014: Failed to load rollover rules xml.

Cause: Failed to load rollover rules xml.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-53015: Failed to parse rollover rules xml.

Cause: Failed to parse rollover rules xml.

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56001: Passed parameter {0} can't be null

Cause: Passed parameter can't be null

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56001: Passed parameter {0} can't be null

Cause: Passed parameter can't be null

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56002: Can't find {0} with id {1}

Cause: Can't find item with passed id

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56002: Can't find {0} with id {1}

Cause: Can't find item with passed id

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56003: Mapping Storage: database access error

Cause: Database access error

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-56003: Mapping Storage: database access error

Cause: Database access error

Action: Check server-side log.
Level: 32

Type: ERROR

Impact:

DISCMAN-70200: Error occurred in the Audit Web Service.

Cause: Error encountered while working with Audit Web Service.

Action: Check if the Audit Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-70200: Error occurred in the Audit Web Service.

Cause: Error encountered while working with Audit Web Service.

Action: Check if the Audit Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-70209: Disclosure Management audit: database access error.

Cause: Disclosure Management audit: database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-70209: Disclosure Management audit: database access error.

Cause: Disclosure Management audit: database access error.

Action: Check database configuration.
Level: 32

Type: ERROR

Impact:

DISCMAN-70210: Error occurred when operating with storage.

Cause: Error encountered while operating with storage.

Action: Check if the storage server is up or the storage connection.
Level: 32

Type: ERROR

Impact:

DISCMAN-70210: Error occurred when operating with storage.

Cause: Error encountered while operating with storage.

Action: Check if the storage server is up or the storage connection.
Level: 32

Type: ERROR

Impact:

DISCMAN-80200: Error occurred in the Repository Web Service.

Cause: Error encountered while working with Repository Web Service.

Action: Check if the Repository Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-80200: Error occurred in the Repository Web Service.

Cause: Error encountered while working with Repository Web Service.

Action: Check if the Repository Web Service is configured correctly.
Level: 32

Type: ERROR

Impact:

DISCMAN-80210: Error occurred when operating with storage.

Cause: Error encountered while operating with storage.

Action: Check if the storage server is up or the storage connection.
Level: 32

Type: ERROR

Impact:

DISCMAN-80210: Error occurred when operating with storage.

Cause: Error encountered while operating with storage.

Action: Check if the storage server is up or the storage connection.
Level: 32

Type: ERROR

Impact:

DISCMAN-80211: Error occurred when connecting to the repository.

Cause: Error encountered while connecting to the repository.

Action: Check user credetials.
Level: 32

Type: ERROR

Impact:

DISCMAN-80211: Error occurred when connecting to the repository.

Cause: Error encountered while connecting to the repository.

Action: Check user credetials.
Level: 32

Type: ERROR

Impact:

DISCMAN-80212: Repository item does not exist at the specified path.

Cause: Error encountered while getting item from the repository.

Action: Check if item exists.
Level: 32

Type: ERROR

Impact:

DISCMAN-80212: Repository item does not exist at the specified path.

Cause: Error encountered while getting item from the repository.

Action: Check if item exists.
Level: 32

Type: ERROR

Impact:

DISCMAN-80213: Error occurred when reading input content.

Cause: Error encountered while reading input content.

Action: Check if input content is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-80213: Error occurred when reading input content.

Cause: Error encountered while reading input content.

Action: Check if input content is correct.
Level: 32

Type: ERROR

Impact:

DISCMAN-90001: Error occurred when extracting error message.

Cause: Can't find error message

Action: Add error message
Level: 32

Type: ERROR

Impact:

DISCMAN-90001: Error occurred when extracting error message.

Cause: Can't find error message

Action: Add error message
Level: 32

Type: ERROR

Impact:

DISCMAN-90002: Unknown error.

Cause:

Action:
Level: 32

Type:

Impact:

17 DMS-50700 to DMS-58075

DMS-50700: initialization error

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50701: security error

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the appropriate permission has been granted.
Level: 1

Type: ERROR

Impact: Security

DMS-50702: The DMS Java class "{0}" could not be found.

Cause: (See message)

Action: Review the classpath of the application and ensure that the class is available in a jar file or directory listed therein.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50703: The LogWriter name "{0}" is reserved.

Cause: (See message)

Action: Use a different name.
Level: 1

Type: ERROR

Impact: Logging

DMS-50704: unable to create a new LogWriter: {0}

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Logging

DMS-50705: attempting to create a concrete LogWriter instance with an invalid class ({0})

Cause: (See message)

Action: Correct the declaration for the LogWriter to use a valid class.
Level: 1

Type: ERROR

Impact: Logging

DMS-50706: invalid configuration property: name = "{0}", value = "{1}"

Cause: (See message)

Action: Remove the property or correct its name or value to comply with the set of supported property names. If the property value is at fault then reviewing the base exception may provide more information on the manner of the fault (e.g. missing class, invalid directory name).
Level: 1

Type: WARNING

Impact: Configuration

DMS-50707: unable to load configuration file "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the configuration file exists and the permissions on the file permit it to be read.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50708: unable to parse metric rule document

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50709: The metric rule resource {0} could not be read. Aggregation is off.

Cause: (See message)

Action: Check that the resource is available and if necessary correct the content of the classpath.
Level: 1

Type: WARNING

Impact: Files

DMS-50710: duplicated table "{1}" in metric table "{0}"

Cause: (See message)

Action: Remove the <Union> or <Select> table from the metric table (it is already in use therein).
Level: 1

Type: WARNING

Impact: Other

DMS-50711: Value "{1}" is invalid for attribute "{0}".

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute.
Level: 1

Type: WARNING

Impact: Other

DMS-50713: invalid metric rule syntax

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to the metric rule documentation.
Level: 1

Type: WARNING

Impact: Other

DMS-50714: no DMS Archiver found

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50715: no ONS found

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50716: unable to create DMS ONS RPC server

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50717: unable to create DMS Publisher "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50719: unable to connect to the server and retrieve metrics at "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure that the server starts up.
Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50720: unable to retrieve DMS metrics

Cause: The HTTP server failed to handle the metric request.

Action: Make sure the HTTP server is able to handle metric requests.
Level: 1

Type: WARNING

Impact: Other

DMS-50722: unable to parse DMS metric document

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: WARNING

Impact: Other

DMS-50723: The reference to table {0} for aggregating DMS metrics is invalid.

Cause: Columns from tables created by select and union elements are not valid in this context.

Action: Correct the aggregation statement in the metric rules.
Level: 1

Type: WARNING

Impact: Other

DMS-50725: unable to bind to port "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and make sure port is free.
Level: 1

Type: ERROR

Impact: Ports

DMS-50726: The metric configuration resource {0} could not be read.

Cause: (See message)

Action: Check that the resource is available and if necessary correct the content of the classpath.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50727: invalid metric configuration syntax

Cause: (See message)

Action: Refer to XML schema "metric_config.xsd" and correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

DMS-50728: No writable metric repository directory "{0}" is available. The default metric archiving is off.

Cause: (See message)

Action: Make sure that a writable metric repository exists.
Level: 1

Type: WARNING

Impact: Files

DMS-50730: The repository directory "{0}" is not readable.

Cause: (See message)

Action: Make sure that a readable metric repository exists.
Level: 1

Type: WARNING

Impact: Files

DMS-50731: invalid value type "{0}" for column "{1}"

Cause: (See message)

Action: Refer to the metric rule documentation for valid value types.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50732: invalid value type for "Concat" operation: should be string

Cause: (See message)

Action: Refer to the metric rule documentation for valid value types.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50733: Arithmetic expression cannot be string type.

Cause: (See message)

Action: Refer to the metric rule documentation for details of defining metrics.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50734: missing value type for column <{0} Name="{1}">

Cause: (See message)

Action: Refer to the metric rule documentation and add an explicit value type to the column.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50735: invalid system function <Function Name="{0}">

Cause: (See message)

Action: Refer to the metric rule documentation for a list of valid system functions.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50736: missing an argument in <Expression> for column "{0}"

Cause: (See message)

Action: Refer to the metric rule documentation and add an argument for the expresstion.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50737: circular dependency found on aggregated metric tables {0}

Cause: (See message)

Action: Remove circular dependency among aggregated tables.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50738: invalid operation "{0}"

Cause: (See message)

Action: Refer to the metric rule documentation for a list of valid operations.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50742: Exception occurred while performing individual refresh operation for metric "{0}".

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50743: Exception occurred while performing group refresh operation for metric "{0}". This failed refresh may have affected other metrics too.

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50744: illegal argument values passed to method: {0}

Cause: This is in internal error: a set of arguments have been passed to a method within the DMS component that are not appropriate for that method. This state should not have occurred and is indicative of a series of conditions that were not anticipated during development.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50745: illegal program state detected: {0}

Cause: This is in internal error: a program state has been detected within the DMS component that is unexpected or contradictory.

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

DMS-50747: attempt to read an older metric rule document "{0}"

Cause: Metric rule document "{0}" was older than the one currently used in the system.

Action: Make sure the version of the metric rules is equal to or higher than the one currently used in the system.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50748: attempt to read an metric rule document "{0}" that is equal to or older than the one currently used in the system

Cause: The version of the metric rule document "{0}" was equal to or older than the one currently used in the system.

Action: Make sure the version of the metric rules is higher than the one currently used in the system.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50749: OPMN is down.

Cause: (See message)

Action: Start OPMN.
Level: 1

Type: WARNING

Impact: Requests/Responses

DMS-50750: Metric parameter is null.

Cause: (See message)

Action: Pass in a non-null metric.
Level: 1

Type: WARNING

Impact: Data

DMS-50751: Metric "{0}" passed in does not belong to "{1}".

Cause: (See message)

Action: Pass in an appropriate metric.
Level: 1

Type: WARNING

Impact: Data

DMS-50752: One of the parameters for "{0}" is null or empty: {1}

Cause: (See message)

Action: Do not pass in null or empty parameters.
Level: 1

Type: WARNING

Impact: Data

DMS-50753: wrong value type

Cause: (See message)

Action: Pass in value with appropriate type.
Level: 1

Type: WARNING

Impact: Data

DMS-50754: One of the parameters for "{0}" has unexpected value "{1}".

Cause: (See message)

Action: Pass in correct values.
Level: 1

Type: WARNING

Impact: Data

DMS-50755: server unavailable: {0}

Cause: (See message)

Action: Specify valid server or cluster names.
Level: 1

Type: WARNING

Impact: Data

DMS-50756: invalid value for property "{0}": "{1}"

Cause: (See message)

Action: Specify a valid property value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50757: Property "{0}" cannot have null or empty value.

Cause: (See message)

Action: Specify a valid property value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50758: Invalid configuration value for metric caching: "{0}"

Cause: (See message)

Action: Specify a valid configuration value.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50759: invalid property: "{0}"

Cause: (See message)

Action: Specify a valid property.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50760: DMS startup class is not started. DMS runs with reduced functionality.

Cause: (See message)

Action: Make sure to start DMS startup class.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50761: Could not derive a translation using key {0} and locale {1} for parameter descriptor {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-50762: No NounDescriptor found for anonymous phase.

Cause: An anonymous phase has been started or aborted but there is no NounDescriptor associated with this phase. Some derived data, such as trace data, may be incomplete or partially corrupted.

Action: Correct the code that starts or aborts the anonymous phase.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50763: Attempt to create pre-existing noun {0}, of type {1}, with a conflicting type {2}.

Cause: An attempt has been made to create a noun that already exists and has a type that is different from the current attempt to create it.

Action: Correct the code responsible for creating this noun.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50903: Metric aggregation is off due to errors.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50904: unable to parse metric rule document: {0}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50905: missing name for metric table

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50906: conflicting table space for metric table: {0}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50907: Metric table "{0}" will not be built due to exception.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50908: Name attribute is invalid in <ColumnDef> for metric table "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50909: duplicated <ColumnDef Name="{1}"> for metric table "{0}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50910: Type attribute is invalid in <ColumnDef Name="{1}"> for metric table "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50911: Duplicated metric table. Metric table {0} will be ignored.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50915: wrong value type "{2}" for column "{1}" in metric table "{0}". Expect value type "{3}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50916: Column "{0}" is missing in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Make sure to match <ColumnDef> with <Column>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50917: Name attribute is empty in <ColumnGroup>.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50918: Type attribute is invalid in <ColumnGroup Name="{1}">.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50919: empty group member in <ColumnGroup Name="{1}">

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50920: Attribute "{3}" of <{0}> is invalid in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50921: Column "{0}" is not defined in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50922: Attribute "{4}" of <{3} Name="{0}"> is invalid in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50923: Number of arguments for column "{3}" in <Expression> is "{0}" in table "{1}" for metric table "{2}", which is less that expected.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: (See message)

Action: Make sure to have at least two arguments.

DMS-50924: Arguments for column "{2}" in <Expression> are missing in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50925: unexpected <Aggregation> in <Where> in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50926: Metric table "{2}" should not reference column "{0}" defined in table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50927: duplicated <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50928: missing <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50929: unexpected <{0}> in <Union Name="{1}"> for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50930: unable to resolve column "{2}" in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50932: The value of attribute "{0}", "{1}", is less then the minimum "{2}".

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50933: unable to convert the value of attribute "{0}", "{1}", to a number

Cause: (See message)

Action: Review the documentation for the correct use of the specific attribute and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50934: Sampling is not enabled for metric table "{0}".

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50935: unable to convert value "{0}" to a number

Cause: (See message)

Action: Refer to log files for the cause and, if possible, correct the problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50938: duplicated <{3} Name="{0}"> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50940: The value of Attribute "Name" for <OrderBy> fails to match one of column names in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50941: unable to convert the value of <RowRetained>, "{0}", in table "{1}" to a number for metric table "{2}"

Cause: (See message)

Action: Review the documentation for the correct use of the specific element and give a valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50942: Only two tables can be referred to in outer join in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50943: Some of the values of <Column Name="{0}"> from metric table "{1}" contained by <Select Name="{2}"> inside <Table Name="{3}"> will be lost after aggregation. It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.

Cause: (See message)

Action: It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50944: Some of the values of <Column Name="{0}"> from metric table "{1}" contained inside <Having> by <Select Name="{2}"> inside <Table Name="{3}"> will be lost after aggregation. It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.

Cause: (See message)

Action: It is recommended to use <Aggregation Name="{0}"> or <GroupBy Name="{0}">.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50945: missing <And>, <Or>, <Not>, or <Condition> in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50946: invalid <{0}> in table "{1}" for metric table "{2}"

Cause: (See message)

Action: Specify one of <And>, <Or>, <Not>, or <Condition>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50947: Number of arguments for condition is "{0}" in table "{1}" for metric table "{2}", which is less that expected.

Cause: (See message)

Action: Make sure to have at least two arguments.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50948: missing condition argument in table "{0}" for metric table "{1}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50949: <Null> is not valid when operator is "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50950: Exception occurred while retrieving metrics from metric repository.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50951: wrong number of tokens in auto aggregation table name "{0}"

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50952: invalid auto aggregation table name "{0}"

Cause: (See message)

Action: Make sure that auto aggregation table names follow the patterns of <prefix>/<opcode>//<table_name> or <prefix>/<opcode>/groupby/<column_name1>/.../<column_nameN>//<table_name>.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50953: invalid aggregation operation "{1}" in auto aggregation table name "{0}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50954: invalid metric cache size "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric cache size in megabytes.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50955: invalid metric prefetch interval "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric prefetch interval in seconds.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50956: invalid metric prefetch removal cycle "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the metric prefetch removal cycle.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50957: Value of column "{1}" in table "{0}" is not a number.

Cause: (See message)

Action: Review the documentation for the correct use of the specific element and make sure to give valid value.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50958: invalid DMS queue timeout interval "{0}"

Cause: (See message)

Action: Make sure to give a valid value for the DMS queue timeout in seconds.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50959: invalid DMS queue maximum size "{0}"

Cause: (See message)

Action: Make sure to give a positive value for the DMS queue maximum size.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50960: Column <{2}> should not be type "{3}" in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50961: Operation "{2}" should be type "{3}" in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50962: Arithmetic expression should not be String type in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50963: Column "{0}" expects a number.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50964: Column <{2} Name="{3}"> is missing value type in table "{0}" for metric table "{1}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50965: <Function Name="{0}"> has invalid function name in table "{1}" for metric table "{2}".

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50966: Metric table "{0}" has no key column. It will not be collected.

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50967: invalid Object Name "{0}" in dms_config.xml

Cause: (See message)

Action: Make sure to give an valid Object Name.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50968: Missing Object Name in dms_config.xml

Cause: (See message)

Action: Make sure to give an valid Object Name.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50973: Caught Exception.

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50976: The use of one or more of the following deprecated properties [{0}] has been detected.

Cause: (See message)

Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50977: a potentially conflicting use of properties. The use of one or more of the following deprecated properties [{0}] has been detected.

Cause: (See message)

Action: Cease use of the deprecated properties and use one or more of these properties [{1}] instead. The deprecated properties will be ignored.
Level: 1

Type: WARNING

Impact: Configuration

DMS-50978: Exception occurred while registering metric rules "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-50980: Exception occurred while looking up runtime mbean server by JNDI name "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.

DMS-50981: Exception occurred while reading metric rules "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50982: Exception occurred while reading metric dump server configuration file "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50983: Exception occurred while reading metric configuration file "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50984: no data available for streaming.

Cause: (See message)

Action: Modify input parameters and try again.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50985: Exception occurred while retrieving metrics from address "{0}" with query string "{1}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50986: Task rejected because the collector queue reaches maximum size.

Cause: (See message)

Action: Allocate or free up more resources and try again later.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50989: Exception occurred while retrieving metrics from address "{0}".

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50990: Unable to register MBean "{0}"

Cause: (See message)

Action: Review the exception chain in log files for the cause and correct the specific problem.
Level: 1

Type: NOTIFICATION

Impact: Other

DMS-50991: metric rule file "{0}" has the following XML parsing error: {1}

Cause: (See message)

Action: Review the content of the metric rule document and check it for errors with respect to standard XML syntax rules and the metric rule documentation.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50992: Invalid Java system property "{0}"

Cause: (See message)

Action: Specify a valid Java system property "{0}".
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50993: invalid metric dump interval "{0}"

Cause: (See message)

Action: Make sure to give a valid metric dump interval in seconds.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-50994: invalid maximum size for the metric dump "{0}"

Cause: (See message)

Action: Make sure to give a valid maximum size in megabytes for the metric dump.
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

DMS-57001: Failed to update WorkContextMap.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57002: Exception raised while attempting to reset WorkContextMap in order to resolve a previous exception raised when updating WorkContextMap.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57003: Failed to process the serialized DMS execution context {0} sent by {1} (user-agent: {2}) when requesting the resource {3}.

Cause: By scrutinizing the incoming HTTP request DMS has attempted to detect and, if appropriate, make use of a wrapped execution context. That process has failed. This should not affect the processing of the servlet handling the request, but the ability to correlate the processing of this request with others to which it may related will have been adversely affected. A DMS execution context is an object that contains context information about the piece of work being performed at a particular moment in time. The type of context information carried by the DMS execution context may include the URL of the http request, the unique correlation key (ECID) assigned to that piece of work, etc - information that is useful for tracking requests though the system. The execution context does not carry user names, passwords or general application parameters. The DMS execution context should not be confused with application specific context objects, such as ADF-context or Faces-context, which are vital to the accurate execution of the application concerned.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57004: Failed to initialize the DMS trace to be associated with DMS execution context {0}, that itself is associated with a request of resource {1}.

Cause: A problem has occurred in the initialization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.

Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

DMS-57005: Failed to terminate the DMS trace associated with DMS execution context {0}, that itself is associated with a request of resource {1}.

Cause: A problem has occurred in the finalization of the trace system for this request. This should not affect the processing of the servlet handling the request but will be a problem if the trace (aggregate, debug or triggered) data was of value to the system's administrator.

Action: If the trace of this request was important, and has been affected by this error, then contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Other

DMS-57006: Failed to deactivate the DMS execution context, {0}, associated with a request of resource {1}.

Cause: A problem has occurred in the termination of the DMS execution context in place during the processing of the HTTP request. This should not affect the servlet handling the request, but may result in an invalid execution context being in place for the processing of future requests and possibly prevent accurate trace data from being gathered.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57007: Failed to url-decode a serialized execution context ({0}) due to a problem in the decoding process itself: {1}

Cause: A problem has occurred while trying to url-decode a wrapped execution context found as a url-parameter. The consequence is that the execution context being passed from client to server can not be used. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57008: The execution context put in place at the start of the request, {0}, is not the execution context in place at the end of the request, {1}. The request is as follows: {2}

Cause: When enabled to do so DMS associates an execution context with the resources (typically a thread) assigned to process an incoming request. In this case the context that DMS assigned at the start of the processing is not the one in place at the end of the processing. At some point during the processing the context has been changed. This could result in the loss of the ability to correlate the work performed across the complete request lifecycle for this request. A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57009: An error prevented selection of an appropriate execution context implementation for this environment - the feature will be disabled.

Cause: At the point of initialization DMS needs to determine the environment in which it is operating in order to select the most appropriate implementation of the execution context feature. An unexpected error has occurred during that process. The DMS execution context feature will be disabled.

Action: Review the error to see if it can be resolved and then restart the server.
Level: 1

Type: ERROR

Impact: Other

DMS-57010: Failed to select appropriate execution context implementation for this environment - the feature will be disabled.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

DMS-57011: Unexpected program state detected: {0}

Cause: The component has detected a state or behaviour that it can not accomodate or rectify.

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57012: WorkContextMap access failed for execution context {0}.

Cause: DMS delegates certain operations to the WLS WorkContextMap. On this occasion the operation has failed, and therefore DMS can not complete this operation.

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57013: WorkContextMap is not available for execution context {0}.

Cause: DMS delegates certain operations to the WLS WorkContextMap, but the WorkContextMap is not available, and therefore DMS can not complete this operation.

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57014: ExecutionContext activation has failed - the incumbant context may not be the one expected.

Cause: (See message)

Action: A failure in the DMS execution context feature does not generally result in a complete failure of the system or application making use of it, but it can result in misleading trace output or misleading correlation keys (ECID) in log messages: generally only the administrator will be aware of such changes in the behavior of an affected application.
Level: 1

Type: WARNING

Impact: Other

DMS-57015: The size of the proposed value for context parameter {0} is {1} and exceeds the permitted size of {2} for that parameter.

Cause: The execution context does not permit the storing of arbitrarily large context values; an attempt has been made to store a value which is longer that declared maximum size for that value.

Action: Determine if there is any code in the system that integrates with the Oracle DMS Context API (java package oracle.dms.context) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code, and if necessary contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

DMS-57016: The setting that controls the eager fetching of some types of execution context data has been set to {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-57030: Execution context being decoded has invalid ECID or RID ({0}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57031: The version of the serialized string is not supported ({0}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-57032: Decoding process failed for serialized string {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58002: Could not create trace output directory ({0}) - Disabling {1} traces.

Cause: An attempt to create a file system directory, into which trace files were to be written, has failed. Consequently no trace information can be saved and therefore, to save unnecessary burden on the system, trace information will not be collected.

Action: Check that the system user that owns the process has permissions to create such a directory. Check that the system has sufficient disk space to create a new directory.
Level: 1

Type: WARNING

Impact: Files

DMS-58005: ignoring exception: {0}

Cause: An unanticipated problem has occurred for which the runtime code can not take automatic remedial action.

Action: Refer to the base exception to see if there is a problem with the system that can be addressed (e.g. run low in disk space, run out of memory, etc).
Level: 1

Type: WARNING

Impact: Other

DMS-58006: Problem encountered while removing old files from trace output directories.

Cause: DMS was attempting to remove old files from the trace output directories but for some reason (see base exception) has failed.

Action: The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released. Refer to the base exception to see if the problem can be addressed, and consider deleting unrequired files manually (DMS no longer needs these old files so any or all of them can be removed).
Level: 1

Type: WARNING

Impact: Files

DMS-58007: Problem encountered when closing file and associated streams.

Cause: As part of the termination of a normal read or write operation on a file the file could not be closed.

Action: If a file can not be properly closed then the operating system's file-handle associated with that file may not be properly released. An operating system can manage only a finite number of file-handles and if they are not released then new file-handles can not be created. One consequence of a depletion of file-handles is that file input/outpt on the machine concerned may be forced to come to a stop. It is more likely, however, that this is a one-off problem and that Java will tidy up the file-handle internally. This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Files

DMS-58008: error writing trace data to disk

Cause: DMS has failed to create or use the objects required to write trace output to disk. The output intended to be written will be discarded.

Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Other

DMS-58013: Problem encountered aggregating trace: {0}.

Cause: DMS has failed to perform the aggregation process on the trace data collected during the handling of this particular task or servlet request. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58014: Failed to handle REQUEST_BEGIN for {0}. The trace will not be aggregated.

Cause: DMS did not find the trace event that marks the start of the series of trace events to be associated with an HTTP request. Without that particular trace event DMS can not be sure that the set of collected trace events will accurately represent the actions performed during that HTTP request and consequently will not process them further. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Review exception details and the log for any seemingly related messages. If the problem has come from the JVM itself: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs. Otherwise the problem is with the code written to run on the JVM: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58015: Can not get the current task's execution context and therefore the trace events that occurred during this task's lifecycle can not be used to contribute to the aggregate trace associated with the task's URL.

Cause: In order to perform the process of trace aggregation for a completed task the execution context for that task is required. In this case the execution context could not be found; without the execution context object the trace aggregation process can not be performed. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58016: Can not get the URI associated with the current thread's recent activities.

Cause: In order to perform the process of trace aggregation for a completed task the URI associated with that task is required. In this case the URI could not be found; without the URI the trace information collected cannot be aggregated. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI. Failure to perform the aggregation processing for this task will mean that the summary data for the URI concerned will not be accurate.

Action: Determine if there is any code in the system that that integrates with the Oracle DMS Trace API (java package oracle.dms.trace) but was not produced by Oracle. If there is no such code then contact Oracle Support Services. Otherwise scrutinize and test the non-Oracle code in order to isolate the problem.
Level: 1

Type: WARNING

Impact: Other

DMS-58017: The maximum number of allowed aggregates has already been reached. Traces referring to URLs not already being aggregated will not contribute to aggregate information.

Cause: In order to prevent too much memory being consumed by the DMS trace system the current request will not be added to the aggregate trace set because the maximum number of URIs for which trace data will be aggregated has already been reached. A DMS trace is composed of a series of DMS trace events that represent an operation performed within DMS. Examples of trace events are: a sensor update, the start and end of an HTTP request. An aggregate trace is the result of aggregating trace data for tasks (typically HTTP requests) associated with the same URI.

Action: If aggregate trace information is not required for this request there is no action required. Otherwise please review the value of the system property oracle.dms.trace.maxAggregates.
Level: 1

Type: WARNING

Impact: Other

DMS-58018: Cannot delete old trace file: {0}.

Cause: An attempt to delete a file system file has failed (the deletion attempt was intended to keep files organized and their number manageable). The system is unlikely to fail as a consequence of this error, but disk space will be used that would otherwise have been released.

Action: This type of problem suggests a problem with either the JVM, the operating system or the state of the machine on which they are running. Review the base exception to see if the issue can be resolved (e.g. memory issues, disk space issues, file access issues, etc.). In order to understand the scale of the problem continue to monitor the system for similar or related issues. If necessary stop and start the product to fully reinitialize the JVM on which it runs.
Level: 1

Type: WARNING

Impact: Files

DMS-58019: Cannot generate aggregate trace data because the trace system failed initialization.

Cause: (See message)

Action: Review the log files for reports of other problems relating to initialization failure. Where possible correct those other problems and restart the system. Failure of the trace subsystem should not affect the ability of the system to execute, but will prevent traces from being produced.
Level: 1

Type: WARNING

Impact: Other

DMS-58020: failure writing DMS configuration file {0}

Cause: An error occurred attempting to save the DMS configuration file.

Action: Check that the process has permission to write the configuration file. Review log files for more information on this issue.
Level: 1

Type: WARNING

Impact: Files

DMS-58021: failure loading DMS configuration file {0}

Cause: An error occurred attempting to load the DMS configuration file.

Action: Check that the process has permission to read the configuration file, and the file exists. Review log files for more information on this issue.
Level: 1

Type: WARNING

Impact: Files

DMS-58022: failure registering DMS configuration MBean {0}

Cause: An error occurred attempting to register the DMS configuration MBean.

Action: Check that the J2EE container is up. Review log files for more information.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58023: There has been a failure activating the DMS configuration. Failed to close the event configuration file for server "{0}".

Cause: An error occurred attempting to activate the DMS configuration.

Action: Review the log files for more information.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58025: cannot instantiate class {0} for destination with id = {1}

Cause: A Destination could not be created at runtime.

Action: Check that the Destination has been configured correctly.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58026: cannot not set property {0} on an instance of class {1} for destination with id = {2}

Cause: The configuration of a destination specified one or more properties to be set on the destination before the destination was used. A problem was encountered trying to set the property listed in the message the precise details of which are also shown in the message.

Action: Verify that the property exists on the class being instantiated as the destination, and that the value is legal for that property.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58028: will not associate filter {0} and destination {1} - one or both are null or have null IDs.

Cause: (See message)

Action: Check the configuration of the filter and destination, and search the log file for other messages that may report problems creating instances of the filter or destination.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58029: initialization error when calling initDestination on destination with id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58030: Can not disassociate filter {0} and destination {1} - no matching eventRoutes were found.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58031: shutdown error when calling shutdownDestination on destination with id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58032: Can not remove a filter using a null or empty filter ID.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58033: Can not associate a destination, id={0}, with a filter, id={1} if the filter declares that it will not pass any events.

Cause: An instance of a filter should declare the set of event types in which it has an interest. In this particular case the set is empty and thus the filter is apparently interested in no events at all. Such a filter serves no sensible purpose and therefore will be ignored.

Action: Check the log file for other error relating to this filter to see if there were problems in its construction. Also verify the configuration of the filter and its associated destination (some filters are created implicitly to cooperate with a destination, so the configuration may only specify details of the destination).
Level: 1

Type: WARNING

Impact: Configuration

DMS-58034: Error detected while sending DMS internal http request start or stop notification.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58035: The required Java Flight Recorder classes can not be found. The JFRDestination can not function without them.

Cause: The Java Flight Recorder classes are not available on all JVMs.

Action: Check that the system is running using a JVM that has this feature.
Level: 1

Type: WARNING

Impact: Other

DMS-58036: An exception was encountered while creating a JFR Dynamic Event to which DMS events would have been reported: eventTypeName="{0}", eventTypeDescription="{1}", eventTypePath="{2}", exception="{3}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58037: An exception was encountered while creating a JFR Dynamic Value for nouns of type "{1}" using a value-id of "{2}" and value-name "{3}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58038: An exception was encountered while creating a JFR Producer using the producer name "{0}", and producer path "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58041: The FlightRecorder class is declaring that it is not active and thus DMS will not use it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

DMS-58042: The DMS configuration file is invalid, and may not be viewed. No updates are allowed until the file has been fixed manually.

Cause: The DMS configuration file is invalid. No updates are allowed until the file has been fixed.

Action: Review the log files for more information, and correct the problem in the configuration file
Level: 1

Type: WARNING

Impact: Configuration

DMS-58043: The destination with id={0} has failed shutdown or initialization as part of the process of associating it with filter id={1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58045: DMS classic tracing will not be performed because the DMS context manager is disabled.

Cause: The classic trace features of DMS are dependent upon the DMS context manager being enabled. The DMS context manager is not enabled, and therefore the classic trace features can not operate.

Action: Review the java startup parameters to see if the DMS context manager has been disabled (check for properties with a prefix of 'oracle.dms.context')
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-58046: Classic tracing of all types (debug, triggered and aggregate) is disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

DMS-58047: Classic tracing is already statically configured. It is not possible to reconfigure it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58048: Classic tracing has been dynamically configured. It is not possible to configure it statically.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58049: Classic tracing has been dynamically configured. It is not possible to add another dynamic configuration. The incumbant configuration should be removed first.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58050: The directory {0} does not exist and therefore can not be used to save {1} trace data.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58051: The value {0} is not a valid integer and can not be applied to {2}. It will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58052: Too many flight recorder destination instances

Cause: There can be at most one active flight recorder destination executing in the system at any one time (because there can be at most one DMS recording being written to the flight recorder at any one point in time).

Action: Remove the current flight recorder instance from active service (e.g. disable all related event routes in the DMS configuration) before attempting to make active the new or modified configured instance.
Level: 1

Type: WARNING

Impact: Configuration

DMS-58053: The filter with id={0} is invalid in the dms configuration file, and will be ignored, and may be removed from the configuration file during the next update.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58054: The event route with filter id={0} and destination id={0} is invalid in the dms configuration file, and will be ignored, and may be removed from the configuration file during the next update.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

DMS-58074: Unable to instantiate DiagnosticsFramework. The DMSTraceProvider will not be able to add traced data to incidents.

Cause: A problem with the DiagnosticsFramework has prevented it from being used.

Action: Check log files for any reference to failures or errors in the DiagnosticsFramework, and if possible correct them.
Level: 1

Type: WARNING

Impact: Other

DMS-58075: Failed to create a logger to which DMS trace events can be logged.

Cause: A problem has been encountered creating a logger that is required by the DMSTraceProvider.

Action: Review the exception that prevented the logger from being created, and if possible correct it.
Level: 1

Type: WARNING

Impact: Other

18 DVT-02012 to DVT-26021

DVT-02012: Column {0} exceeds boundary {1}.

Cause: The specified column number was greater than the total number of columns.

Action: Get the total number of columns, by calling the getColumnCount method of the graph or of the column header in the pivot table. Then specify a column that does not exceed the total number of columns.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02013: Row {0} exceeds boundary {1}.

Cause: The specified row number was greater than the total number of rows.

Action: Get the total number of rows, by calling the getRowCount method of the graph or of the column header in the pivot table. Then specify a row that does not exceed the total number of rows.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02015: Slice {0} exceeds boundary {1}.

Cause: The specified slice number was greater than the total number of slices.

Action: Specify a slice that does not exceed the total number of slices.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02016: Layer {0} exceeds boundary {1}.

Cause: The specified layer was greater than the total number of layers that are available on the given edge.

Action: Specify a layer that does not exceed the total number of layers.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02017: Series {0} exceeds boundary {1}.

Cause: The specified series was greater than the total series that is available in the graph.

Action: Specify a zero-based series index that does not exceed the total series. The Graph.getDisplaySeries method should provide the number of series that are displayed in the graph. Or, if Graph.isDataRowShownAsASeries returns true, then Graph.getRowCount returns the number of series that can be displayed. If Graph.isDataRowShownAsASeries returns false, then Graph.getColumnCount returns the total number of series that can be displayed.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02018: Edge {0} exceeds boundary {1}.

Cause: The specified edge was greater than the total number of edges that are available on the given edge. Valid edges for methods that require an edge are: DataDirector.COLUMN_EDGE, DataDirector.ROW_EDGE, and DataDirector.PAGE_EDGE.

Action: Specify a valid edge constant.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02019: Current DataSource does not support required type: {0}.{1}.

Cause: The DataSource did not support the required type of data in its DataMap. For example, the view requested DataMap.DATA_GROUPSORT information, and the DataSource that the view uses did not supply group sort information.

Action: Request support for the required data types in the DataSource, or use a different DataSource.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-02020: DTD file cannot be found.

Cause: The specified DTD could not be found. The XML parser needed the DTD in order to validate XML files.

Action: Ensure that the specified DTD file exists, or disable XML validation. DTDs for Data Visualization components are in their respective packages. To turn off validation, call Dataview.setXMLValidated(false);.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-03000: No Mergeable object is provided.

Cause: No default Mergeable object was provided to resolve rules.

Action: Provide at least one default Mergeable object, so that rules can be resolved. For more information about Mergeable objects, see the Javadoc for the oracle.dss.rules.Mergeable interface.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-03001: attempt to call merge(Mergeable) on an incompatible Mergeable class

Cause: An attempt was made to merge incompatible Mergeable classes. Only Mergeable objects of the same class can be merged. For example, ViewStyle objects can be merged, but a ViewStyle cannot be merged with a ViewFormat.

Action: Merge two classes that are compatible. For more information, see the Javadoc for the oracle.dss.rules.RuleBundle class.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-06000: unexpected data error from Pivot Table data model

Cause: An unexpected exception was thrown by the Pivot Table's data model.

Action: Log a bug against the application. Verify that the Pivot Table's data model is configured properly.
Level: 1

Type: ERROR

Impact: Data

DVT-06001: no Converter for data type {0} during Pivot Table text formatting

Cause: The application could not create a Converter for a specific data type. The most likely reason was that a Converter was not registered for that data type.

Action: Log a bug against the application. Verify that the application can create a default Converter for all data types rendered by the Pivot Table.
Level: 1

Type: TRACE

Impact: Configuration

DVT-07001: cannot create Graph image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-08000: unexpected data error from Data Model

Cause: An invalid operation was performed by Data Model.

Action: Log a bug against the application. Verify that the Data model is configured properly.
Level: 1

Type: ERROR

Impact: Data

DVT-22004: cannot create Gauge image

Cause: Under heavy loads, there was not enough memory to create the BufferedImage, or the Graphics instance from the BufferedImage. Therefore, the generated image file is empty.

Action: Reduce the memory load; for example, reduce the image size or allocate more memory to the JVM.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23000: End date cannot be earlier than start date.

Cause: The end date specified for the Gantt chart was earlier than the specified start date.

Action: Specify a correct start date and end date for the Gantt chart.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23001: The time unit in the major axis must be greater than the time unit in the minor axis.

Cause: The time unit specified in the major axis was not greater than the time unit specified in the minor axis. For example, if "days" was specified as the time unit for the minor axis, then the time unit specified in the major time axis must be greater than "days", such as "months", and not anything less, such as "hours".

Action: Ensure that the time unit in the major axis is greater than the time unit in the minor axis.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23002: An invalid time scale is specified.

Cause: The specified time scale in the major or minor axis was not recognized.

Action: Specify a valid time scale for the axis.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23003: End date of a task cannot be earlier than its start date. Start date: {0}, End date: {1}

Cause: The end date specified for the task was earlier than its start date.

Action: Check the data to ensure that the start date and end date are loaded correctly.
Level: 1

Type: WARNING

Impact: Data

DVT-23004: No tooltip keys or labels are specified.

Cause: No tooltip keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the tooltip to ensure that the tooltip is not empty.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23005: No legend keys or labels are specified.

Cause: No legend keys or labels were specified in the Gantt tag.

Action: Specify keys and labels for the legend to ensure that the legend is not empty.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23006: The number of tooltip keys does not match the number of tooltip labels.

Cause: The number of tooltip keys did not match the number of tooltip labels specified in the Gantt tag.

Action: Ensure that the number of tooltip keys specified in the Gantt tag (tooltipKeys attribute) matches the tooltip labels specified in the Gantt tag (tooltipLabels attribute).
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23007: The number of legend keys does not match the number of legend labels.

Cause: The number of legend keys did not match the number of legend labels specified in the Gantt tag.

Action: Ensure that the number of legend keys specified in the Gantt tag (legendKeys attribute) matches the legend labels specified in the Gantt tag (legendKeyLabels attribute).
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23008: The start date of the task is out of range. Value: {0}

Cause: The start and end date of a task was outside of the time range specified for the Gantt chart.

Action: No action necessary, if it is okay not to show the task. Otherwise, verify data is correct or specify a wider time range for the Gantt chart (using the startTime and endTime attributes)
Level: 1

Type: WARNING

Impact: Data

DVT-23009: cannot find format for type {0}; skipping task: {1}

Cause: No format for type {0} was registered.

Action: Register a TaskbarFormat with the TaskbarFormatManager for the type indicated.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23010: The specified day of the week is invalid. Value: {0}

Cause: The day of the week specified was not recognized.

Action: Specify a value for the day of the week that is one of these seven constants from the java.util.Calendar class: Calendar.SUNDAY, Calendar.MONDAY, Calendar.TUESDAY, Calendar.WEDNESDAY, Calendar.THURSDAY, Calendar.FRIDAY, Calendar.SATURDAY.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23011: The value specified for alignment is invalid. Task ID: {0}

Cause: The alignment value specified for the label or icon was invalid.

Action: Specify a value for alignment that is one of these three constants from the oracle.adf.view.faces.bi.component.gantt.GanttConstants class: GanttConstants.LEFT, GanttConstants.RIGHT, GanttConstants.INSIDE.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23012: GanttDropTarget can only be attached to a Gantt component.

Cause: The GanttDropTarget tag was added as a child of a non-Gantt component.

Action: Ensure that the GanttDropTarget tag is a child tag of either a Project Gantt or Scheduling Gantt component.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-23013: The start date of a task is null.

Cause: The start date of a task was null.

Action: Check the data to ensure that the start date is not null.
Level: 1

Type: WARNING

Impact: Data

DVT-23014: The task ID is null.

Cause: The task ID or split task ID was null.

Action: Check the data to ensure that the task ID or split task ID is not null.
Level: 1

Type: WARNING

Impact: Data

DVT-23015: The next date cannot be earlier than the previous date.

Cause: The next date returned by custom timescale was earlier than the previous date.

Action: Specify a correct next date.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-23016: The value supplied for the attribute is returning a wrong type.

Cause: The value supplied for the attribute is returning a wrong type.

Action: Chech the attribute and modify to return correct type.
Level: 1

Type: WARNING

Impact: Data

DVT-23017: The taskID is not unique in the resource. resourceID: {0}, taskID: {1}

Cause: The taskID is not unique in the resource.

Action: Check the data to ensure that the task ID is unique.
Level: 1

Type: WARNING

Impact: Data

DVT-26000: unable to find connection in {0}

Cause: Either the map configuration was not valid, or connection information was missing.

Action: Check the map configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26001: theme \"{0}\" cannot be displayed: missing value property

Cause: The value attribute of the theme was null.

Action: Check the value attribute of the theme.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26002: theme \"{0}\" cannot be displayed: invalid row key at row {1}

Cause: The specified row either did not have a row key, or the row id in the row key was null.

Action: Check the key and row id for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26004: theme \"{0}\" cannot be displayed: row {1} with id={2} does not have a data value

Cause: The specified row did not have a data value.

Action: Check the data value for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26005: theme \"{0}\" cannot be displayed: row {1} with id={2} does not have a location value

Cause: The specified row did not have a location value.

Action: Check the location value for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26006: Labels for one or more rows of theme \"{0}\" are missing.

Cause: Some rows in the theme did not have a location label.

Action: Check the location labels in the theme.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-26008: Theme \"{0}\" does not have any data.

Cause: The specified theme did not return any rows.

Action: Check whether the specified theme is correctly returning no data.
Level: 1

Type: WARNING

Impact: Data

DVT-26009: unable to geocode data at row {0} of theme \"{1}\": {2}

Cause: The specified data could not be geocoded.

Action: Change the location value for the specified row.
Level: 1

Type: WARNING

Impact: Data

DVT-26010: The mouse click behavior of {0} is to render a popup, but there is no popup facet in the map.

Cause: The map had no popup facet, but the leftClickBehavior property was specified to render a popup.

Action: Check whether the mouse click behavior is correct.
Level: 1

Type: WARNING

Impact: Data

DVT-26011: The right-click behavior of {0} is to render a popup, but there is no popup facet in the map.

Cause: The map had no popup facet, but the rightClickBehavior property was specified to render a popup.

Action: Check whether the right-click behavior is correct.
Level: 1

Type: WARNING

Impact: Data

DVT-26012: The number of labels specified in legendLabels does not match the number of buckets. Legend labels: {0}, Buckets: {1}

Cause: The number of legend labels and buckets did not match.

Action: Check the number of legend labels.
Level: 1

Type: WARNING

Impact: Data

DVT-26013: unable to geocode the theme data: no Geocoder URL specified in {0}

Cause: Either the map configuration was not valid, or connection information for the Geocoder was missing.

Action: Check the map configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26014: unable to show all theme data for theme \"{0}\": multiple data values for {1} are specified but only the first data value is shown

Cause: Duplicate location data values were found.

Action: Check the data for duplicate location values.
Level: 1

Type: WARNING

Impact: Programmatic

DVT-26015: theme \"{0}\" cannot be displayed: no longitude data at row {1}

Cause: The specified row did not have a longitude value.

Action: Check the longitude for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26016: theme {0} cannot be displayed: no latitude data at row {1}

Cause: The specified row did not have a latitude value.

Action: Check the latitude for the specified row.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26017: unable to connect to MapViewer at {0}

Cause: A MapViewer server was not found at the specified map URL.

Action: Check whether the connection URL is correct and the MapViewer servlet can accept new requests.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26018: unable to connect to Geocoder at {0}

Cause: The component was unable to connect to the Geocoder at the specified URL.

Action: Check whether the connection URL is correct and the Geocoder can accept new requests.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26019: unable to find a map of id {0} for mapToolbar {1}

Cause: The mapId attribute of the specified mapToolbar was not correct.

Action: Check the mapId attribute of the specified mapToolbar.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26020: A map tag cannot have more than one mapOverview tag.

Cause: There were more than one mapOverview tags in the map tag.

Action: Remove any extra mapOverview tags.
Level: 1

Type: ERROR

Impact: Programmatic

DVT-26021: A map tag cannot have more than one mapLegend tag.

Cause: There were more than one mapLegend tags in the map tag.

Action: Remove any extra mapLegend tags.
Level: 1

Type: ERROR

Impact: Programmatic

19 EDQ-03400 to EDQ-00651

EDQ-03400: Error buffering image from url "{0}" : {1}

Cause: Error buffering image from url "{0}" : {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03401: Unable to load icon for {0} with icon {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06200: No content in XML

Cause: No content in XML

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06201: Unsupported type: {0}

Cause: Unsupported type: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06202: An error occurred loading resource: {0}

Cause: An error occurred loading resource: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06203: An error occurred loading resource by key: {0}

Cause: An error occurred loading resource by key: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06205: {0} Exception creating writer for metric {1}

Cause: {0} Exception creating writer for metric {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06207: {0} Exception writing metric {1}

Cause: {0} Exception writing metric {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06208: {0} Exception writing classification view by attribute

Cause: {0} Exception writing classification view by attribute

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06209: {0} Exception writing classification view metric

Cause: {0} Exception writing classification view metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06210: {0} Exception writing reclassification dependent rules view

Cause: {0} Exception writing reclassification dependent rules view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06211: {0} Exception writing reclassification rules patterns view

Cause: {0} Exception writing reclassification rules patterns view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06212: {0} Exception writing pre-selection patterns metric

Cause: {0} Exception writing pre-selection patterns metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06213: {0} Exception writing resolution rule view

Cause: {0} Exception writing resolution rule view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06214: {0} Exception writing results view

Cause: {0} Exception writing results view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06215: {0} Exception writing selection view metric

Cause: {0} Exception writing selection view metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06216: {0} Exception writing token frequency by decision

Cause: {0} Exception writing token frequency by decision

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06217: {0} Exception writing tokenisation view metric

Cause: {0} Exception writing tokenisation view metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06218: {0} Exception writing unclassified token by attribute detail view

Cause: {0} Exception writing unclassified token by attribute detail view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06219: {0} Exception writing unclassified tokens by attribute view

Cause: {0} Exception writing unclassified tokens by attribute view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06220: Unknown type of source for source id = {0}. Type of source specified = {1}

Cause: Unknown type of source for source id = {0}. Type of source specified = {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06221: Could not parse source id = {0}

Cause: Could not parse source id = {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06222: {0} Parser configuration does not accept attribute {1}

Cause: {0} Parser configuration does not accept attribute {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06223: {0} An error occurred parsing XML document: {1}

Cause: {0} An error occurred parsing XML document: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06224: {0} Invalid parser configuration

Cause: {0} Invalid parser configuration

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06225: {0} Checker ({1}) has not been implemented

Cause: {0} Checker ({1}) has not been implemented

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06226: {0} Found reclassification circular dependency at: {1}

Cause: {0} Found reclassification circular dependency at: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06227: {0} Security exception when trying to load class: {1}

Cause: {0} Security exception when trying to load class: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06228: {0} Illegal argument exception when creating metric handler instance for: {1}

Cause: {0} Illegal argument exception when creating metric handler instance for: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06229: {0} Instantiation exception when creating metric handler instance for: {1}

Cause: {0} Instantiation exception when creating metric handler instance for: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06230: {0} Illegal access exception when creating metric handler instance for: {1}

Cause: {0} Illegal access exception when creating metric handler instance for: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06231: {0} Invocation target exception when creating metric handler instance for: {1}

Cause: {0} Invocation target exception when creating metric handler instance for: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03500: Error opening dialog : {1}

Cause: Error opening dialog : {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02700: Notification error: {0}

Cause: Notification error: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02701: EventLogManager: User not found for id {0}

Cause: EventLogManager: User not found for id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02702: EventLogManager: Project not found for id {0}

Cause: EventLogManager: Project not found for id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02703: Error logging event: {0}

Cause: Error logging event: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09100: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09101: Error deleting staged data

Cause: Error deleting staged data

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09102: Error importing data for node: {0}

Cause: Error importing data for node: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09103: Error creating staged data: {0}

Cause: Error creating staged data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09104: Failed to decode staged data data profile

Cause: Failed to decode staged data data profile

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09105: Failed to encode staged data profile

Cause: Failed to encode staged data profile

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09106: Failed to decode staged data attributes

Cause: Failed to decode staged data attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09107: Failed to encode staged data attributes

Cause: Failed to encode staged data attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09108: Error during staged data configuration analysis

Cause: Error during staged data configuration analysis

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09110: Error retrieving known providers for staged data in project id {0}

Cause: Error retrieving known providers for staged data in project id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09111: Purging staged data: {0}

Cause: Purging staged data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09112: Deleting staged data: {0}

Cause: Deleting staged data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09113: Error optimizing staged data for browsing: {0}

Cause: Error optimizing staged data for browsing: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09114: Error deleting staged data in project

Cause: Error deleting staged data in project

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09115: Unable to get attributes for staged data Id: {0}

Cause: Unable to get attributes for staged data Id: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09116: Error refreshing data profile for staged data from database

Cause: Error refreshing data profile for staged data from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09117: Error closing staged data writer: {0}

Cause: Error closing staged data writer: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09118: Error updating data profile for staged data: {0}

Cause: Error updating data profile for staged data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06700: Failed to convert gui data for process model: {0}

Cause: Failed to convert gui data for process model: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06701: Process model not found in list of config docs!

Cause: Process model not found in list of config docs!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06702: Reference Processor update aborted. Non-composite '{0}' has incorrect dependency '{1}'

Cause: Reference Processor update aborted. Non-composite '{0}' has incorrect dependency '{1}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06703: Reference Processor update aborted. Reference Processor '{0}' has wrong processor count: {1}

Cause: Reference Processor update aborted. Reference Processor '{0}' has wrong processor count: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06704: Reference Processor update aborted. Reference Processor '{0}' is wrong type: {1}

Cause: Reference Processor update aborted. Reference Processor '{0}' is wrong type: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06705: Error loading process: id = '{0}'

Cause: Error loading process: id = '{0}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06707: Process cannot be saved

Cause: Process cannot be saved

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06708: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06709: Last run process cannot be saved

Cause: Last run process cannot be saved

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06710: Cannot load data interfaces for process model {0}

Cause: Cannot load data interfaces for process model {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06711: Failed to start transaction

Cause: Failed to start transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06712: Process model '{0}': cannot delete

Cause: Process model '{0}': cannot delete

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06713: Process model '{1}': cannot purge

Cause: Process model '{1}': cannot purge

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06714: Error exporting process to file '{0}'

Cause: Error exporting process to file '{0}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06715: IO error {0}

Cause: IO error {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06716: Error exporting process

Cause: Error exporting process

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06717: Invalid processor type {0}

Cause: Invalid processor type {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06718: Failed to convert xml property

Cause: Failed to convert xml property

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06719: The following XML failed validation against schema '{0}':{1}

Cause: The following XML failed validation against schema '{0}':{1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06720: Process import file '{0}' not found

Cause: Process import file '{0}' not found

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06721: Process import failed during parse

Cause: Process import failed during parse

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06722: Process import no content found in input

Cause: Process import no content found in input

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06723: Process import invalid version: {0}

Cause: Process import invalid version: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06724: Failed validation against schema: {0}

Cause: Failed validation against schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06725: Error loading document for promulgation: {0}

Cause: Error loading document for promulgation: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06726: Failed to clean DI records for model {0}: {1}

Cause: Failed to clean DI records for model {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06727: Widget type not allowed: {0}

Cause: Widget type not allowed: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06728: Attribute in composite graph outputs but not in composite: {0}

Cause: Attribute in composite graph outputs but not in composite: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06729: Error copying composite processor graph

Cause: Error copying composite processor graph

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06730: Cannot remove processor - does not exist in this graph: {0}

Cause: Cannot remove processor - does not exist in this graph: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06731: WidgetInfo not found: {0}

Cause: WidgetInfo not found: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06732: Processor not visible at process model level: {0}

Cause: Processor not visible at process model level: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06733: Attempting to add an invalid pipe

Cause: Attempting to add an invalid pipe

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06734: Cannot remove pipe because from processor not visible at process model level: {0}

Cause: Cannot remove pipe because from processor not visible at process model level: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06735: Error creating widget facade

Cause: Error creating widget facade

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06736: Cannot find xsl resource: {0}

Cause: Cannot find xsl resource: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06737: Cannot configure transformer with stylesheet: {0}

Cause: Cannot configure transformer with stylesheet: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06738: Cannot perform transform with stylesheet: {0}

Cause: Cannot perform transform with stylesheet: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06739: Failed to encode process data interfaces

Cause: Failed to encode process data interfaces

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06740: Failed to decode process data interfaces

Cause: Failed to decode process data interfaces

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06741: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06742: Failed to decode process display info

Cause: Failed to decode process display info

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01700: DashboardExport: Undefined process id

Cause: DashboardExport: Undefined process id

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01701: DashboardExport: Publish failed: {0}

Cause: DashboardExport: Publish failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01702: DashboardExport: Publish failed: {0}

Cause: DashboardExport: Publish failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01703: DashboardExport: Finished export job

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-01704: DashboardExport: Problem with XML subsystem configuration {0}

Cause: DashboardExport: Problem with XML subsystem configuration {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01705: DashboardExport: Problem getting list of projects.

Cause: DashboardExport: Problem getting list of projects.

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01706: DashboardExport: Problem getting list of projects.

Cause: DashboardExport: Problem getting list of projects.

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01707: DashboardExport: Problem getting spigot count

Cause: DashboardExport: Problem getting spigot count

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05700: An error occurred cancelling task: {0}

Cause: An error occurred cancelling task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05701: An error occurred running task: {0}

Cause: An error occurred running task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05702: An error occurred releasing locks: {0}

Cause: An error occurred releasing locks: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05703: An error occurred storing event log for task: {0}

Cause: An error occurred storing event log for task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05704: Error during mission diff

Cause: Error during mission diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05706: thread limit is: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05707: streaming is allowed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05708: streaming is not allowed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05709: Mission Manager expiry date is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05710: An error occurred cancelling task immediately: {0}

Cause: An error occurred cancelling task immediately: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05711: No trigger found for {0}

Cause: No trigger found for {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05712: Error constructing event message: {0}

Cause: Error constructing event message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05713: Error archiving progress information: {0}

Cause: Error archiving progress information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05714: Error parsing XML document: {0}

Cause: Error parsing XML document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05715: Error creating new transformer for outputting match process: {0}

Cause: Error creating new transformer for outputting match process: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05716: Error transforming match process to XML: {0}

Cause: Error transforming match process to XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05717: Error creating XML parser for outputting match process: {0}

Cause: Error creating XML parser for outputting match process: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05718: A problem occurred retrieving application purge rules: {0}

Cause: A problem occurred retrieving application purge rules: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05719: An error occurred running the purging thread: {0}

Cause: An error occurred running the purging thread: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05720: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Cause: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05721: A error occurred running trigger: {0}

Cause: A error occurred running trigger: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05722: Task factory for task type {0} is being replaced

Cause: Task factory for task type {0} is being replaced

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05723: A problem occurred deleting results for job {0} with runlabel "{1}": {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05724: Job {0} with runlabel "{1}" was successfully deleted

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05725: Purge Rules are invalid and can not be saved

Cause: Purge Rules are invalid and can not be saved

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10100: Processor library: {0} not found in processor file {1}

Cause: Processor library: {0} not found in processor file {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10101: Processor library: read error verifying processor file {0}: {1}

Cause: Processor library: read error verifying processor file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10102: Processor library: verification error in processor file {0}: {1}

Cause: Processor library: verification error in processor file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10103: Processor library: {0} in {1} cannot be verified

Cause: Processor library: {0} in {1} cannot be verified

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10104: Processor library: error reading from processor file {0}: {1}

Cause: Processor library: error reading from processor file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10105: Processor library: verification error reading from processor file {0}: {1}

Cause: Processor library: verification error reading from processor file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10106: Processor library: error generating processor transmission data: {0}

Cause: Processor library: error generating processor transmission data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10107: Processor library: reloading processors because of change in licences or jar list

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10108: Processor library: processor bean {0} reported as failed: {1}

Cause: Processor library: processor bean {0} reported as failed: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10109: Processor library: exception initializing processor bean {0}: {1}

Cause: Processor library: exception initializing processor bean {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10110: Processor library: exception deactivating processor bean {0}: {1}

Cause: Processor library: exception deactivating processor bean {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10111: Processor library: duplicate processor {0} detected in {1} - ignored

Cause: Processor library: duplicate processor {0} detected in {1} - ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10112: Processor library: skipping processor {0} because of bean creation problem

Cause: Processor library: skipping processor {0} because of bean creation problem

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10113: Processor library: exception calling {0} on {1} in processor {2}: {3}

Cause: Processor library: exception calling {0} on {1} in processor {2}: {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10114: Processor library: error creating a {0} bean: {1}

Cause: Processor library: error creating a {0} bean: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10115: Processor library: reading error during XML parsing in {0}: {1}

Cause: Processor library: reading error during XML parsing in {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10116: Processor library: failed to parse XML in {0}: {1})

Cause: Processor library: failed to parse XML in {0}: {1})

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10117: Processor library: skipping {0} due to errors in XML

Cause: Processor library: skipping {0} due to errors in XML

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10118: Processor library: no content in XML in {0}

Cause: Processor library: no content in XML in {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10119: Processor library: all processors in {0} rejected by available test

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10120: Processor library: permissions entry not allowed in unsigned jar {0} - skipping

Cause: Processor library: permissions entry not allowed in unsigned jar {0} - skipping

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10121: Processor library: failed to parse permissions element in {0}: {1}

Cause: Processor library: failed to parse permissions element in {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10122: Processor library: error reading permissions entry in {0}: {1}

Cause: Processor library: error reading permissions entry in {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10123: Processor library: regex error in {0} in {1}: {2}

Cause: Processor library: regex error in {0} in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10124: Processor library: error parsing {0} in {1}: {2}

Cause: Processor library: error parsing {0} in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10125: Processor library: error reading {0} in {1}: {2}

Cause: Processor library: error reading {0} in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10126: Processor library: no <processor> or <munger> elements in {0}

Cause: Processor library: no <processor> or <munger> elements in {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10127: Processor library: invalid available expression "{0}" on <{1}> element in {2}: {3}

Cause: Processor library: invalid available expression "{0}" on <{1}> element in {2}: {3}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10128: Processor library: processor bean class {0} could not be found

Cause: Processor library: processor bean class {0} could not be found

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10129: Processor library: bean class {0} must implement ICustomizableProcessorBean to use parameters

Cause: Processor library: bean class {0} must implement ICustomizableProcessorBean to use parameters

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10130: Processor library: untrusted bean class {0} is not allowed to inject server objects

Cause: Processor library: untrusted bean class {0} is not allowed to inject server objects

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10131: Processor library: injection errors in bean class {0}: {1}

Cause: Processor library: injection errors in bean class {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10133: Processor library: no resource named {0} in jar {1}

Cause: Processor library: no resource named {0} in jar {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10134: Processor library: problem reading resource {0} from {1}: {2}

Cause: Processor library: problem reading resource {0} from {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10135: Processor library: error during XML parsing: {0}

Cause: Processor library: error during XML parsing: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10136: Processor library: error during XML parsing at {0}: {1}

Cause: Processor library: error during XML parsing at {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10137: Processor library: fatal error during XML parsing: {0}

Cause: Processor library: fatal error during XML parsing: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10138: Processor library: fatal error during XML parsing at {0}: {1}

Cause: Processor library: fatal error during XML parsing at {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10140: Processor library: processor {0} in {1} rejected by available test

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10141: Processor library: processor {0} in {1} rejected by licence

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10145: Processor library: {0}: cannot load processor class {0}

Cause: Processor library: {0}: cannot load processor class {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10158: Processor library: reading processor {0}: completed with errors

Cause: Processor library: reading processor {0}: completed with errors

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10159: Processor library: invalid structureguid "{0}" in {1}

Cause: Processor library: invalid structureguid "{0}" in {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10160: Processor library: could not verify signers: {0}

Cause: Processor library: could not verify signers: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10161: Processor library: could not verify certificates: {0}

Cause: Processor library: could not verify certificates: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10162: Processor library: invalid X.500 signer name "{0}"

Cause: Processor library: invalid X.500 signer name "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10163: Processor library: failed to load trust data from stream: {0}

Cause: Processor library: failed to load trust data from stream: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10164: Processor library: problem opening jar {0}: {1}

Cause: Processor library: problem opening jar {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10165: Processor library: problem closing jar {0}: {1}

Cause: Processor library: problem closing jar {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10166: Processor library: problem reading data for jar entry {0} in file {1}: {2},

Cause: Processor library: problem reading data for jar entry {0} in file {1}: {2},

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10167: Processor library: unsupported class version for jar entry {0}{ in file {1}

Cause: Processor library: unsupported class version for jar entry {0}{ in file {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10168: Processor library: error getting stream for resource {0} from {1}: {2}

Cause: Processor library: error getting stream for resource {0} from {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10169: Processor library: getWidgets: Server indicated cache hit but cache did not return parcel

Cause: Processor library: getWidgets: Server indicated cache hit but cache did not return parcel

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10170: Processor library: problem reading from WidgetsParcel: {0}

Cause: Processor library: problem reading from WidgetsParcel: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10171: Processor library: problem with class in WidgetsParcel: {0})

Cause: Processor library: problem with class in WidgetsParcel: {0})

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10172: Processor library: unhandled error in call to {0}.{1} on {2}: {3}

Cause: Processor library: unhandled error in call to {0}.{1} on {2}: {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10500: Processor library: {0}: no property corresponding to ''derivedfrom'' attribute "{1}" in input ID {2}

Cause: Processor library: {0}: no property corresponding to ''derivedfrom'' attribute "{1}" in input ID {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10501: Processor library: {0}: error in metric ID {1} expression "{2}": {3}

Cause: Processor library: {0}: error in metric ID {1} expression "{2}": {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10502: Processor library: {0}: output name is required if cardinality is n:1

Cause: Processor library: {0}: output name is required if cardinality is n:1

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10503: Processor library: {0}: visibility and metadata attributes may not be used together

Cause: Processor library: {0}: visibility and metadata attributes may not be used together

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10504: Processor library: {0}: output type may not be ''match'' with N:M cardinality

Cause: Processor library: {0}: output type may not be ''match'' with N:M cardinality

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10505: Processor library: {0}: output type may not be ''match'' with more than one input

Cause: Processor library: {0}: output type may not be ''match'' with more than one input

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10506: Processor library: {0}: widget with derived output must have custom info class

Cause: Processor library: {0}: widget with derived output must have custom info class

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10507: Processor library: {0}: widget with user defined output must have custom UI class

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10508: Processor library: {0}: output ID {1}: ''multiple'' must be used with type=derived or type=userdefined

Cause: Processor library: {0}: output ID {1}: ''multiple'' must be used with type=derived or type=userdefined

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10509: Processor library: {0}: no output id available for filter

Cause: Processor library: {0}: no output id available for filter

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10510: Processor library: {0}: in filter: no output with id {1}

Cause: Processor library: {0}: in filter: no output with id {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10511: Processor library: {0}: type of output attribute used in filter must be number or string

Cause: Processor library: {0}: type of output attribute used in filter must be number or string

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10512: Processor library: {0}: bad filter value "{1}" for numeric output

Cause: Processor library: {0}: bad filter value "{1}" for numeric output

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10513: Processor library: {0}: ''multiple'' output attribute cannot be used in filter

Cause: Processor library: {0}: ''multiple'' output attribute cannot be used in filter

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10514: Processor library: {0}: child elements not allowed in <options> with ref= attribute

Cause: Processor library: {0}: child elements not allowed in <options> with ref= attribute

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10515: Processor library: {0}: no <options> element matching ref="{0}"

Cause: Processor library: {0}: no <options> element matching ref="{0}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10516: Processor library: {0}: property options allowed with text properties only

Cause: Processor library: {0}: property options allowed with text properties only

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10517: Processor library: {0}: bad default for number property "{0}" ("{1}")

Cause: Processor library: {0}: bad default for number property "{0}" ("{1}")

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10518: Processor library: {0}: bad default for integer property "{0}" ("{1}")

Cause: Processor library: {0}: bad default for integer property "{0}" ("{1}")

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10519: Processor library: {0}: non-editable property {1} should not have an enabledif condition

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10520: Processor library: {0}: property expression "{1}" does not return a number

Cause: Processor library: {0}: property expression "{1}" does not return a number

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10521: Processor library: {0}: error in property expression "{1}": {2}

Cause: Processor library: {0}: error in property expression "{1}": {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10522: Processor library: {0}: range constraint must be used with a numeric property

Cause: Processor library: {0}: range constraint must be used with a numeric property

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10523: Processor library: {0}: length constraint must be used with a text property;

Cause: Processor library: {0}: length constraint must be used with a text property;

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10524: Processor library: {0}: format constraint must be used with a string property

Cause: Processor library: {0}: format constraint must be used with a string property

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10525: Processor library: {0}: source {1} and derivation {2} attributes must match in datum {3}

Cause: Processor library: {0}: source {1} and derivation {2} attributes must match in datum {3}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10526: Processor library: {0}: metric datum type must be specified if source is omitted

Cause: Processor library: {0}: metric datum type must be specified if source is omitted

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10527: Processor library: {0}: bad datum type for {1}

Cause: Processor library: {0}: bad datum type for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10528: Processor library: {0}: datum type derivation must match source

Cause: Processor library: {0}: datum type derivation must match source

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10529: Processor library: {0}: datum type derivation must match derivation

Cause: Processor library: {0}: datum type derivation must match derivation

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10530: Processor library: {0}: meteoric derivation cannot be used with multiple attributes and multiple sets

Cause: Processor library: {0}: meteoric derivation cannot be used with multiple attributes and multiple sets

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10531: Processor library: {0}: datum {1} with element attribute is not derived from multiple attributes

Cause: Processor library: {0}: datum {1} with element attribute is not derived from multiple attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10533: Processor library: {0}: destid, source and destype not allowed on datdrill with nested datamatch elements

Cause: Processor library: {0}: destid, source and destype not allowed on datdrill with nested datamatch elements

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10534: Processor library: {0}: metricdrill target {1} does not exist in metric {2}

Cause: Processor library: {0}: metricdrill target {1} does not exist in metric {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10535: Processor library: {0}: dest and source not allowed on metricdrill with nested metricmatch elements

Cause: Processor library: {0}: dest and source not allowed on metricdrill with nested metricmatch elements

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10536: Processor library: {0}: metricdrill view "{1}" does not exist in metric {2}

Cause: Processor library: {0}: metricdrill view "{1}" does not exist in metric {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10537: Processor library: {0}: anonymous drilldown in metric {1} not allowed with default specified

Cause: Processor library: {0}: anonymous drilldown in metric {1} not allowed with default specified

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10538: Processor library: {0}: anonymous drilldown in metric {1} must be first in list

Cause: Processor library: {0}: anonymous drilldown in metric {1} must be first in list

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10540: Processor library: {0}: no input corresponding to {1} in metric {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10541: Processor library: {0}: input:N attribute type may not be an array

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10545: Processor library: {0}: metricdrill dest {1} does not exist in metric {2}

Cause: Processor library: {0}: metricdrill dest {1} does not exist in metric {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10558: Processor library: {0}: <summaryrecords> element not allowed with variable format metric {1}

Cause: Processor library: {0}: <summaryrecords> element not allowed with variable format metric {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10559: Processor library: {0}: unknown metric {1} in <summaryrecords> in metric {2}

Cause: Processor library: {0}: unknown metric {1} in <summaryrecords> in metric {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10560: Processor library: {0}: metric with <summaryrecords> may not have additional data items

Cause: Processor library: {0}: metric with <summaryrecords> may not have additional data items

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10561: Processor library: {0}: <variablerecords> element not allowed with fixed format metric {1}

Cause: Processor library: {0}: <variablerecords> element not allowed with fixed format metric {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10562: Processor library: {0}: in <variablerecords> one of keyval and key must be used but not both

Cause: Processor library: {0}: in <variablerecords> one of keyval and key must be used but not both

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10563: Processor library: {0}: <variablerecords> input keyval must be of string type

Cause: Processor library: {0}: <variablerecords> input keyval must be of string type

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10564: Processor library: {0}: <variablerecords> output keyval must be of string type

Cause: Processor library: {0}: <variablerecords> output keyval must be of string type

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10565: Processor library: {0}: <variablerecords> key datum {1} does not exist in metric {2}

Cause: Processor library: {0}: <variablerecords> key datum {1} does not exist in metric {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10566: Processor library: {0}: variablerecords input:N reference must allow single attribute only

Cause: Processor library: {0}: variablerecords input:N reference must allow single attribute only

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10567: Processor library: {0}: <variablerecords>: source attribute omitted on datum "{1}" in metric {2}

Cause: Processor library: {0}: <variablerecords>: source attribute omitted on datum "{1}" in metric {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10568: Processor library: {0}: view "{1}" in default list does not exist

Cause: Processor library: {0}: view "{1}" in default list does not exist

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10569: Processor library: {0}: view "{1}" repeated in default list

Cause: Processor library: {0}: view "{1}" repeated in default list

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10570: Processor library: {0}: unknown metric {1} used in view {2}

Cause: Processor library: {0}: unknown metric {1} used in view {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10571: Processor library: {0}: metricid is required on variable type view

Cause: Processor library: {0}: metricid is required on variable type view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10572: Processor library: {0}: unknown column "{1}" in sortby string "{2}"

Cause: Processor library: {0}: unknown column "{1}" in sortby string "{2}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08300: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08301: Failed to decode results publishing job option XML string: {0}

Cause: Failed to decode results publishing job option XML string: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08302: Result publish info cannot be saved

Cause: Result publish info cannot be saved

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08303: Failed to start transaction

Cause: Failed to start transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08304: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08305: Error loading results publishing info for process: id = '{0}'

Cause: Error loading results publishing info for process: id = '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06800: Error importing bucket

Cause: Error importing bucket

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06801: Error during source view diff

Cause: Error during source view diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06802: Provider {0} auto-realize failed: {1}

Cause: Provider {0} auto-realize failed: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06803: Consumer {0} auto-realize failed: {1}

Cause: Consumer {0} auto-realize failed: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06804: Error loading Xitem {0}/{1}: {2}

Cause: Error loading Xitem {0}/{1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06805: Error loading old realizations: {0}

Cause: Error loading old realizations: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06807: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06808: Virtual bucket not realized for reading

Cause: Virtual bucket not realized for reading

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06809: Virtual bucket not realized for writing

Cause: Virtual bucket not realized for writing

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06810: No mapping for real attribute {0} in writer

Cause: No mapping for real attribute {0} in writer

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06811: No mapping for virtual attribute {0} in writer

Cause: No mapping for virtual attribute {0} in writer

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06812: Unknown virtual attribute {0} in realization

Cause: Unknown virtual attribute {0} in realization

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06813: Unknown real attribute {0} in realization

Cause: Unknown real attribute {0} in realization

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06814: Types of virtual attribute {0} and real attribute {1} do not match

Cause: Types of virtual attribute {0} and real attribute {1} do not match

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06815: Failed to open virtual bucket configuration file {0}

Cause: Failed to open virtual bucket configuration file {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06816: Failed to decode realizations string: {0}

Cause: Failed to decode realizations string: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06817: Bucket deposition failed

Cause: Bucket deposition failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06818: Bucket update failed

Cause: Bucket update failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06819: Problem whilst deleting {0} buckets for {1}: {2}

Cause: Problem whilst deleting {0} buckets for {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06820: Bucket transaction refused

Cause: Bucket transaction refused

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06821: Problem querying XTree for type {0}: {1}

Cause: Problem querying XTree for type {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06822: Error retrieving %s XTree data {0}: {1}

Cause: Error retrieving %s XTree data {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06823: Failed to write XML to '{0}'

Cause: Failed to write XML to '{0}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06824: Failed to load labels from '{0}': {1}

Cause: Failed to load labels from '{0}': {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06825: Failed to save labels from '{0}': {1}

Cause: Failed to save labels from '{0}': {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06826: CodePointClassifier: bad character code definition '{0}'

Cause: CodePointClassifier: bad character code definition '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06827: CharacterClassifier: bad character code definition '{0}'

Cause: CharacterClassifier: bad character code definition '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06828: Failed to deposit {0} store '{1}'

Cause: Failed to deposit {0} store '{1}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06829: Failed to update {0} store '{1}'

Cause: Failed to update {0} store '{1}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06830: Error deleting dependencies for {0} {1}: {2}

Cause: Error deleting dependencies for {0} {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06831: Failed to remove {0} store '{1}'

Cause: Failed to remove {0} store '{1}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06832: Error deleting {0} dependencies for project {1}: {2}

Cause: Error deleting {0} dependencies for project {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06833: Error writing %s dependencies for {0}: {1}

Cause: Error writing %s dependencies for {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06834: Failed to open filters configuration document {0}

Cause: Failed to open filters configuration document {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06835: Bad decimal format '{0}'

Cause: Bad decimal format '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06836: Bad date format '{0}'

Cause: Bad date format '{0}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06837: Bad default value '{0}' for {1}

Cause: Bad default value '{0}' for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06838: Failed to open filing cabinet configuration file {0}

Cause: Failed to open filing cabinet configuration file {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06839: Array types not supported for file input

Cause: Array types not supported for file input

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06840: Recordid element may not be used more than once

Cause: Recordid element may not be used more than once

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06841: Could not open '{0}'

Cause: Could not open '{0}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06842: Error reading file

Cause: Error reading file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06843: Failed to read randomator configuration {0}

Cause: Failed to read randomator configuration {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06844: {0}: undefined shared range {1}

Cause: {0}: undefined shared range {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06845: {0} : types do not match in copy with source {1}

Cause: {0} : types do not match in copy with source {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06846: {0} : <{1}> cannot return {2} values

Cause: {0} : <{1}> cannot return {2} values

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06847: {0} : fixed should not include both value attribute and content

Cause: {0} : fixed should not include both value attribute and content

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06848: {0} : bad fixed numeric value '{0}'

Cause: {0} : bad fixed numeric value '{0}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06849: {0} : invalid nested copy reference to {1}

Cause: {0} : invalid nested copy reference to {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06850: {0} : bad decimal format '{1}'

Cause: {0} : bad decimal format '{1}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06851: Dictionary and resource cannot both be used in randomwords

Cause: Dictionary and resource cannot both be used in randomwords

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06852: {0} : differing word sets in same group '{1}'

Cause: {0} : differing word sets in same group '{1}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06853: Bad date {0}

Cause: Bad date {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06854: Bad time {0}

Cause: Bad time {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06855: {0} : bad date format '{1}'

Cause: {0} : bad date format '{1}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06856: Could not find dictionary resource {0}

Cause: Could not find dictionary resource {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06857: Error reading from dictionary file

Cause: Error reading from dictionary file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06858: Could not open resource {0} : {1}

Cause: Could not open resource {0} : {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06859: Could not query resource {0} : {1}

Cause: Could not query resource {0} : {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06860: {0}: range {1} defined more than once

Cause: {0}: range {1} defined more than once

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06861: {0}: multi-level range %s is not supported

Cause: {0}: multi-level range %s is not supported

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06862: DataPump: Unable to make thread wait: {0}

Cause: DataPump: Unable to make thread wait: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06863: starting execution of data batch {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06864: data batch {0} terminated by exception

Cause: data batch {0} terminated by exception

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06865: failed to encode Realizations: {0}

Cause: failed to encode Realizations: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03600: Initialising...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03601: Locale: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03602: Management port: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03603: Closing down...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03604: Finished.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03605: Error storing login preferences

Cause: Error storing login preferences

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03606: Error storing user guid preference

Cause: Error storing user guid preference

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03607: Accessing preferences to reset session ports: {0}

Cause: Accessing preferences to reset session ports: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03608: An error has occurred: {0}

Cause: An error has occurred: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03609: Attempting to handoff to existing port: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03610: Handoff accepted on port: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03611: Handoff refused on port: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03612: Error logging in

Cause: Error logging in

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03613: Aborting after timeout

Cause: Aborting after timeout

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03614: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03615: Login to "{0}" as "{1}" successful

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03616: Login to "{0}" as "{1}" failed: {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03617: Logging out from server: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03618: Error in thread {0}

Cause: Error in thread {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07400: Error loading native library: {0}

Cause: Error loading native library: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07401: QAS Batch Error Code: {0}

Cause: QAS Batch Error Code: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01100: CaseMigration: SMD decode: rendering hint not recognised: {0}

Cause: CaseMigration: SMD decode: rendering hint not recognised: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01000: CaseManagement: Invalid set attribute name {0}

Cause: CaseManagement: Invalid set attribute name {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01001: CaseManagement: Invalid get attribute name {0}

Cause: CaseManagement: Invalid get attribute name {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01002: CaseManagement: Bulk update error

Cause: CaseManagement: Bulk update error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01003: CaseManagement: Truncated value error

Cause: CaseManagement: Truncated value error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01004: CaseManagement: Bulk update transaction error: {0}

Cause: CaseManagement: Bulk update transaction error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01005: CaseManagement: Bulk update failed: {0}

Cause: CaseManagement: Bulk update failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01006: CaseManagement: Case Aggregator setup failed

Cause: CaseManagement: Case Aggregator setup failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01007: CaseManagement: Case Aggregator failed

Cause: CaseManagement: Case Aggregator failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01008: CaseManagement: Case Aggregator wait for threads failed

Cause: CaseManagement: Case Aggregator wait for threads failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01009: CaseManagement: Case creation worker failed

Cause: CaseManagement: Case creation worker failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01010: CaseManagement: Batch Match case creator failed

Cause: CaseManagement: Batch Match case creator failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01011: CaseManagement: String truncated to: {0}

Cause: CaseManagement: String truncated to: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01012: CaseManagement: Error in case export to landing area

Cause: CaseManagement: Error in case export to landing area

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01013: CaseManagement: Error in case export to temporary file

Cause: CaseManagement: Error in case export to temporary file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01014: CaseManagement: Error in case import from landing area

Cause: CaseManagement: Error in case import from landing area

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01015: CaseManagement: Error in case import from temporary file

Cause: CaseManagement: Error in case import from temporary file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01016: CaseManagement: Failed to load filter document schema: {0}

Cause: CaseManagement: Failed to load filter document schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01017: CaseManagement: Failed to load filter export document schema: {0}

Cause: CaseManagement: Failed to load filter export document schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01018: CaseManagement: Failed to load filter schema: {0}

Cause: CaseManagement: Failed to load filter schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01019: CaseManagement: Schema {0} load failed!

Cause: CaseManagement: Schema {0} load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01020: CaseManagement: Flag restriction Regex ''{0}'' is not valid. This will not be applied as a restriction

Cause: CaseManagement: Flag restriction Regex ''{0}'' is not valid. This will not be applied as a restriction

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01021: CaseManagement: Case History indexer failed

Cause: CaseManagement: Case History indexer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01022: CaseManagement: Case indexer failed

Cause: CaseManagement: Case indexer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01023: CaseManagement: Case Transition indexer failed

Cause: CaseManagement: Case Transition indexer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01024: CaseManagement: Case Comments indexer failed

Cause: CaseManagement: Case Comments indexer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01025: CaseManagement: No metadata for case {0}

Cause: CaseManagement: No metadata for case {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01026: CaseManagement: Supplementary Data indexer failed

Cause: CaseManagement: Supplementary Data indexer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01027: CaseManagement: Close index writer failed

Cause: CaseManagement: Close index writer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01028: CaseManagement: Reopen index writer failed

Cause: CaseManagement: Reopen index writer failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01029: CaseManagement: Deleting documents from index failed

Cause: CaseManagement: Deleting documents from index failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01030: CaseManagement: Deleting source ''{0}'' documents from index failed

Cause: CaseManagement: Deleting source ''{0}'' documents from index failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01031: CaseManagement: Deleting case documents from index failed

Cause: CaseManagement: Deleting case documents from index failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01032: CaseManagement: Indexing thread failed

Cause: CaseManagement: Indexing thread failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01033: CaseManagement: Index {0} submitting {1} requests

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-01034: CaseManagement: Index submitter failed

Cause: CaseManagement: Index submitter failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01035: CaseManagement: Indexing commit failed

Cause: CaseManagement: Indexing commit failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01036: CaseManagement: Reindexing already running

Cause: CaseManagement: Reindexing already running

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01037: CaseManagement: Attempt to commit all indexes failed

Cause: CaseManagement: Attempt to commit all indexes failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01038: CaseManagement: Escalte case thread failed

Cause: CaseManagement: Escalte case thread failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01039: CaseManagement: Case escalation failed

Cause: CaseManagement: Case escalation failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01040: CaseManagement: Lock error when deleting cases for source {0} : {1}

Cause: CaseManagement: Lock error when deleting cases for source {0} : {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01041: CaseManagement: Deleting cases for source {0} failed

Cause: CaseManagement: Deleting cases for source {0} failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01042: CaseManagement: Error reloading sources

Cause: CaseManagement: Error reloading sources

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01043: CaseManagement: n. Report Info: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-01044: CaseManagement: Case group {0} does not exist in creator map

Cause: CaseManagement: Case group {0} does not exist in creator map

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01045: CaseManagement: Failed to get derived states for cases

Cause: CaseManagement: Failed to get derived states for cases

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01046: CaseManagement: Failed to get metadata renderer

Cause: CaseManagement: Failed to get metadata renderer

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01047: CaseManagement: Search execution failed

Cause: CaseManagement: Search execution failed

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01048: CaseManagement: Parameter selection function failed for parameter {0}

Cause: CaseManagement: Parameter selection function failed for parameter {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01049: CaseManagement: Failed to create source {0}

Cause: CaseManagement: Failed to create source {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01050: CaseManagement: Source Workflow schema ''{0}'' load failed!

Cause: CaseManagement: Source Workflow schema ''{0}'' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01051: CaseManagement: Failed to decode source

Cause: CaseManagement: Failed to decode source

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01052: CaseManagement: Failed to encode source

Cause: CaseManagement: Failed to encode source

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01053: CaseManagement: Failed to load SMD schema: {0}

Cause: CaseManagement: Failed to load SMD schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01054: CaseManagement: SMD decode: rendering hint {0}

Cause: CaseManagement: SMD decode: rendering hint {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01055: CaseManagement: Failed to load Display schema: {0}

Cause: CaseManagement: Failed to load Display schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01056: CaseManagement: Case Notification trigger failed

Cause: CaseManagement: Case Notification trigger failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01057: CaseManagement: Case Type schema ''{0}'' load failed!

Cause: CaseManagement: Case Type schema ''{0}'' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01058: CaseManagement: Failed to decode case types

Cause: CaseManagement: Failed to decode case types

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01059: CaseManagement: Script error in transition: {0} with message {1}

Cause: CaseManagement: Script error in transition: {0} with message {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01060: CaseManagement: Workflow Schema ''%s'' load failed!

Cause: CaseManagement: Workflow Schema ''%s'' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01061: CaseManagement: Failed to decode workflow

Cause: CaseManagement: Failed to decode workflow

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01062: CaseManagement: Failed to encode workflow

Cause: CaseManagement: Failed to encode workflow

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01063: CaseManagement: Error decoding workflow from database: {0}

Cause: CaseManagement: Error decoding workflow from database: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01064: CaseManagement: Cannot find workflows config directory: {0}

Cause: CaseManagement: Cannot find workflows config directory: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01065: CaseManagement: Cannot load case management workflows

Cause: CaseManagement: Cannot load case management workflows

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01066: CaseManagement: Cannot load workflow file: {0}

Cause: CaseManagement: Cannot load workflow file: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01067: CaseManagement: Cannot save workflow from file: {0}

Cause: CaseManagement: Cannot save workflow from file: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-01068: CaseManagement: Error with waiting for bulk indexing

Cause: CaseManagement: Error with waiting for bulk indexing

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01069: Error collating supplementary data: {0}

Cause: CaseManagement: Error collating supplementary data

Action:
Level: 1

Type: ERROR

Impact: Other

EDQ-03700: Error creating action

Cause: Error creating action

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03701: Error loading xml: {0}

Cause: Error loading xml: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03702: Runtime Error

Cause: Runtime Error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03703: Server Error

Cause: Server Error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03704: Error

Cause: Error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07300: Bad port number {0} - net promulgation disabled

Cause: Bad port number {0} - net promulgation disabled

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07301: Client key {0} cleared by death of session {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07302: Promulgation server bound to port {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07303: Setting select timeout to avoid promulgation deadlocks

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07304: Failed to set up promulgation listener

Cause: Failed to set up promulgation listener

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07305: Problem closing

Cause: Problem closing

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07306: Error in select

Cause: Error in select

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07308: Error accepting socket

Cause: Error accepting socket

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09900: Error loading source view node after import

Cause: Error loading source view node after import

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09901: Error importing source view

Cause: Error importing source view

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08600: Error deleting run

Cause: Error deleting run

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08601: Error accessing run information

Cause: Error accessing run information

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08602: Error purging results for job with id {0}

Cause: Error purging results for job with id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08603: Marking runs for deletion failed

Cause: Marking runs for deletion failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08604: Error getting runs for job with id {0}

Cause: Error getting runs for job with id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08605: Error deleting job results with id {0}

Cause: Error deleting job results with id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08606: Error deleting job results for run label {0}

Cause: Error deleting job results for run label {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08607: Error cleaning up for project {0}

Cause: Error cleaning up for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08608: Error deleting job results for project {0} with run label

Cause: Error deleting job results for project {0} with run label

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08609: Error deleting job results for job {0} with run label

Cause: Error deleting job results for job {0} with run label

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03200: Error getting default JPS Context: {0}

Cause: Error getting default JPS Context: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03210: Error querying reading credential using map {0} and key {1}: {2}

Cause: Error querying reading credential using map {0} and key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03211: Access error querying credential using map {0} and key {1}: {2}

Cause: Access error querying credential using map {0} and key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03212: Error reading credential using map {0} and key {1}: {2}

Cause: Error reading credential using map {0} and key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03213: Access error reading credential using map {0} and key {1}: {2}

Cause: Access error reading credential using map {0} and key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03214: Credential at map {0} and key {1} is not a PasswordCredential

Cause: Credential at map {0} and key {1} is not a PasswordCredential

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03215: Error setting credential using map {0} and key {1}: {2}

Cause: Error setting credential using map {0} and key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03216: Access error setting credential using map {0} and key {1}: {2}

Cause: Access error setting credential using map {0} and key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03220: Error getting keystore {0} from stripe {1}: {2}

Cause: Error getting keystore {0} from stripe {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03221: Access error getting keystore {0} from stripe {1}: {2}

Cause: Access error getting keystore {0} from stripe {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03230: Error getting EDQ JPS auditor: {0}

Cause: Error getting EDQ JPS auditor: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03231: Permission denied getting EDQ JPS auditor: {0}

Cause: Permission denied getting EDQ JPS auditor: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03232: Error generating user audit event: {0}

Cause: Error generating user audit event: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03233: Error generating X audit event: {0}

Cause: Error generating X audit event: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03240: Error lookup up system MBean server at "{0}": {1}

Cause: Error lookup up system MBean server at "{0}": {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03241: Error making MBean ObjectName "{0}": {1}

Cause: Error making MBean ObjectName "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03242: Error registering MBean "{0}": {1}

Cause: Error registering MBean "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02200: Augment {0}: species {1}: table does not have any columns!!

Cause: Augment {0}: species {1}: table does not have any columns!!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02201: Augment {0} for species {1}: database error: {2}

Cause: Augment {0} for species {1}: database error: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02202: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02203: Failed to decode data source

Cause: Failed to decode data source

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02204: Failed to encode data source

Cause: Failed to encode data source

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02205: Error during data source diff

Cause: Error during data source diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02206: There was a problem deleting the data sources for project {0}

Cause: There was a problem deleting the data sources for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02207: Cannot retrieve data source for id: {0} in project: {1}

Cause: Cannot retrieve data source for id: {0} in project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02208: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02209: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02210: RmiJdbc server bound to registry

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02211: Failed to register RmiJdbcServer: {0}

Cause: Failed to register RmiJdbcServer: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02212: RmiJdbc server unbound from registry

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06400: Error loading performance stats

Cause: Error loading performance stats

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09400: Trigger configuration: bad default trigger level "{0}"

Cause: Trigger configuration: bad default trigger level "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09401: Trigger configuration: bad trigger override pattern "{0}": {1}

Cause: Trigger configuration: bad trigger override pattern "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09402: Trigger configuration: bad trigger override level "{0}"

Cause: Trigger configuration: bad trigger override level "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09403: Trigger manager: problem reading schema file: {0}

Cause: Trigger manager: problem reading schema file: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09404: Trigger file {0}: error opening as jar file: {1}

Cause: Trigger file {0}: error opening as jar file: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09405: Trigger file {0}: {1} not found - skipping file

Cause: Trigger file {0}: {1} not found - skipping file

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09406: Trigger file {0}: error reading contents: {1}

Cause: Trigger file {0}: error reading contents: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09407: Trigger file {0}: cannot open: {1}

Cause: Trigger file {0}: cannot open: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09408: Trigger file {0}: error reading: {1}

Cause: Trigger file {0}: error reading: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09409: Trigger file {0}: root element of {1} must be ''triggers''

Cause: Trigger file {0}: root element of {1} must be ''triggers''

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09410: Trigger file {0}: no path provided for type {1}

Cause: Trigger file {0}: no path provided for type {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09411: Trigger file {0}: bad path regex "{1}": {2}

Cause: Trigger file {0}: bad path regex "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09412: Trigger file {0}: error in filter expression "{1}": {2}

Cause: Trigger file {0}: error in filter expression "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09413: Trigger file {0}: argument class {1} not found

Cause: Trigger file {0}: argument class {1} not found

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09414: Trigger file {0}: class {1} not found

Cause: Trigger file {0}: class {1} not found

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09415: Trigger file {0}: class {1} does not implement ITrigger

Cause: Trigger file {0}: class {1} does not implement ITrigger

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09416: Trigger file {0}: class {1} does not have a zero-arg constructor

Cause: Trigger file {0}: class {1} does not have a zero-arg constructor

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09417: Trigger file {0}: error creating {0} instance: {1}

Cause: Trigger file {0}: error creating {0} instance: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09418: Trigger file {0}: error constructing {1} instance: {2}

Cause: Trigger file {0}: error constructing {1} instance: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09419: Trigger file {0}: error injecting class {1}: {2}

Cause: Trigger file {0}: error injecting class {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09420: Trigger file {0}: error loading script from resource {1}: {2}

Cause: Trigger file {0}: error loading script from resource {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09421: Trigger file {0}: script not defined

Cause: Trigger file {0}: script not defined

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09422: Trigger file {0}: error reading script: {1}

Cause: Trigger file {0}: error reading script: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09423: Trigger file {0}: no path specified by trigger script

Cause: Trigger file {0}: no path specified by trigger script

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09424: Trigger file {0}: invalid path regex "{1}": {2}

Cause: Trigger file {0}: invalid path regex "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09425: Trigger file {0}: no loader provider named {1}

Cause: Trigger file {0}: no loader provider named {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09426: Trigger file {0}: runtime loader {1} not available: pending initialization

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-09427: Trigger file {0}: invalid loaderprovider attribute "{1}"

Cause: Trigger file {0}: invalid loaderprovider attribute "{1}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09428: Trigger file {0}: error reading icon file {1}: {2}

Cause: Trigger file {0}: error reading icon file {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09429: Triggers reloaded from {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-09430: Triggers: arguments not compatible with trigger for path {0}

Cause: Triggers: arguments not compatible with trigger for path {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09431: Trigger on path {0} failed: {1}

Cause: Trigger on path {0} failed: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09432: Triggers: no action runner for type {0}

Cause: Triggers: no action runner for type {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09433: Triggers: invalid action configuration object for type {0}

Cause: Triggers: invalid action configuration object for type {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09434: Triggers: action type {0} failed with unchecked exception: {1}

Cause: Triggers: action type {0} failed with unchecked exception: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09435: Trigger file {0}: failed to create script engine: {1}

Cause: Trigger file {0}: failed to create script engine: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09436: Trigger file {0}: error importing script trigger classes: {1}

Cause: Trigger file {0}: error importing script trigger classes: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09437: Trigger file {0}: failed to open script: {1}

Cause: Trigger file {0}: failed to open script: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09438: Trigger file {0}: failed to open script: missing class {1}

Cause: Trigger file {0}: failed to open script: missing class {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09439: Trigger file {0}: ''runtrigger'' and ''run'' functions missing in script

Cause: Trigger file {0}: ''runtrigger'' and ''run'' functions missing in script

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09440: Trigger file {0}: error calling ''getPath'' in script trigger: {1}

Cause: Trigger file {0}: error calling ''getPath'' in script trigger: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09450: JMS trigger instance {0}: InitialContext failed: {1}

Cause: JMS trigger instance {0}: InitialContext failed: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09451: JMS trigger instance {0}: connection factory "{1}" lookup failed: {2}

Cause: JMS trigger instance {0}: connection factory "{1}" lookup failed: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09452: JMS trigger instance {0}: failed to create connection: {1}

Cause: JMS trigger instance {0}: failed to create connection: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09453: JMS trigger instance {0}: error looking up source "{1}": {2}

Cause: JMS trigger instance {0}: error looking up source "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09454: JMS trigger instance {0}: error creating session for reception: {1}

Cause: JMS trigger instance {0}: error creating session for reception: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09455: JMS trigger instance {0}: error creating message consumer: {1}

Cause: JMS trigger instance {0}: error creating message consumer: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09456: JMS trigger instance {0}: bad poll interval "{1}": ignored

Cause: JMS trigger instance {0}: bad poll interval "{1}": ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09457: JMS trigger instance {0}: bad max work value "{1}": ignored

Cause: JMS trigger instance {0}: bad max work value "{1}": ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09458: JMS trigger instance {0}: unknown message header "{1}": ignored

Cause: JMS trigger instance {0}: unknown message header "{1}": ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09459: JMS trigger instance {0}: error starting connection: {1}

Cause: JMS trigger instance {0}: error starting connection: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09460: JMS trigger instance {0}: error looking up destination "{1}": {2}

Cause: JMS trigger instance {0}: error looking up destination "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09461: JMS trigger instance {0}: error creating session for transmission: {1}

Cause: JMS trigger instance {0}: error creating session for transmission: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09462: JMS trigger instance {0}: error creating message producer: {1}

Cause: JMS trigger instance {0}: error creating message producer: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09463: JMS trigger instance {0}: error closing connection: {1}

Cause: JMS trigger instance {0}: error closing connection: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09464: JMS trigger instance {0}: error closing initial context: {1}

Cause: JMS trigger instance {0}: error closing initial context: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09465: JMS trigger instance {0}: message reception error: {1}

Cause: JMS trigger instance {0}: message reception error: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09466: JMS trigger instance {0}: error retrieving header {1}: {2}

Cause: JMS trigger instance {0}: error retrieving header {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09467: JMS trigger instance {0}: error getting message text: {1}

Cause: JMS trigger instance {0}: error getting message text: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09468: JMS trigger instance {0}: non text message ignored

Cause: JMS trigger instance {0}: non text message ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09469: JMS trigger instance {0}: error closing message consumer: {1}

Cause: JMS trigger instance {0}: error closing message consumer: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09470: JMS trigger instance {0}: error closing message consumer session: {1}

Cause: JMS trigger instance {0}: error closing message consumer session: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09471: JMS trigger instance {0}: error creating text message: {1}

Cause: JMS trigger instance {0}: error creating text message: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09472: JMS trigger instance {0}: unknown header ''{1}'' for new message

Cause: JMS trigger instance {0}: unknown header ''{1}'' for new message

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09473: JMS trigger instance {0}: value "{1}" is not suitable for header {2}

Cause: JMS trigger instance {0}: value "{1}" is not suitable for header {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09474: JMS trigger instance {0}: error setting header {1}: {2}

Cause: JMS trigger instance {0}: error setting header {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09475: JMS trigger instance {0}: error sending message: {1}

Cause: JMS trigger instance {0}: error sending message: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09476: JMS trigger instance {0}: error closing message producer: {1}

Cause: JMS trigger instance {0}: error closing message producer: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09477: JMS trigger instance {0}: error closing message producer session: {1}

Cause: JMS trigger instance {0}: error closing message producer session: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06100: Column indexing interrupted: {0}

Cause: Column indexing interrupted: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06101: An error occurred indexing columns: {0}

Cause: An error occurred indexing columns: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06102: An error occurred retrieving staged data definition: {0}

Cause: An error occurred retrieving staged data definition: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10000: Web Services: Unknown authentication method "{0}"

Cause: Web Services: Unknown authentication method "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10001: Web Services: no valid web services authentication methods configured

Cause: Web Services: no valid web services authentication methods configured

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10002: Web Services: failed to publish web service with id {0}: {1}

Cause: Web Services: failed to publish web service with id {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10003: Web Services: error republishing on project change: {0}

Cause: Web Services: error republishing on project change: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10004: Web Services: error during web service diff: {0}

Cause: Web Services: error during web service diff: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10005: Web Services: problem opening jar file {0}: {1}

Cause: Web Services: problem opening jar file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10006: Web Services: {0} missing in {1}

Cause: Web Services: {0} missing in {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10007: Web Services: {0} missing in {1}

Cause: Web Services: {0} missing in {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10008: Web Services: error reading {0} from {1}: {2}

Cause: Web Services: error reading {0} from {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10009: Web Services: error reading {0} from {1}: {2}

Cause: Web Services: error reading {0} from {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10010: Web Services: skipping services in {0} because it contains a service with duplicate local name {1}

Cause: Web Services: skipping services in {0} because it contains a service with duplicate local name {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10011: Web Services: error reading {0} from {1}: {2}

Cause: Web Services: error reading {0} from {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10012: Web Services: error decoding XML in {0} from {1}: {2}

Cause: Web Services: error decoding XML in {0} from {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10013: Web Services: problem creating URI for wsdl: {0}

Cause: Web Services: problem creating URI for wsdl: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10014: Web Services: error creating binding definitions for {0}: {1}

Cause: Web Services: error creating binding definitions for {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10015: Web Services: error during publish for {0}: {1}

Cause: Web Services: error during publish for {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10016: Web Services: problem loading web service data: {0}

Cause: Web Services: problem loading web service data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10017: Web Services: could not find project {0}

Cause: Web Services: could not find project {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10018: Web Services: failed to encode WSDLInfo: {0}

Cause: Web Services: failed to encode WSDLInfo: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10019: Web Services: package name missing with {0} binding

Cause: Web Services: package name missing with {0} binding

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10020: Web Services: failed to decode webservices XML: {0}

Cause: Web Services: failed to decode webservices XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10021: Web Services: error handing sccs item creation: {0}

Cause: Web Services: error handing sccs item creation: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10022: Web Services: error handing sccs item update: {0}

Cause: Web Services: error handing sccs item update: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10023: Web Services: {0} xitems for webservice {1} in project {2}

Cause: Web Services: {0} xitems for webservice {1} in project {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10024: Web Services: problem opening form mappings file {0}: {1}

Cause: Web Services: problem opening form mappings file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10025: Web Services: problem parsing form mappings XML file {0}: {1}

Cause: Web Services: problem parsing form mappings XML file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10026: Web Services: invalid project pattern "{0}" in {1}: {2}

Cause: Web Services: invalid project pattern "{0}" in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10027: Web Services: invalid service pattern "{0}" in {1}: {2}

Cause: Web Services: invalid service pattern "{0}" in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10028: Web Services: invalid page pattern "{0}" in {1}: {2}

Cause: Web Services: invalid page pattern "{0}" in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10029: Web Services: form mapping file {0}: failed to create JS engine: {1}

Cause: Web Services: form mapping file {0}: failed to create JS engine: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10030: Web Services: form mapping file {0}: error importing {1}: {2}

Cause: Web Services: form mapping file {0}: error importing {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10031: Web Services: form mapping file {0}: failed to open script: {1}

Cause: Web Services: form mapping file {0}: failed to open script: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10032: Web Services: form mapping file {0}: failed to open script: missing class {1}

Cause: Web Services: form mapping file {0}: failed to open script: missing class {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10033: Web Services: form mapping file {0}: ''map'' function missing in script mapper

Cause: Web Services: form mapping file {0}: ''map'' function missing in script mapper

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10040: Web Services: error publishing endpoint: {0}

Cause: Web Services: error publishing endpoint: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07200: Error doing processor validation

Cause: Error doing processor validation

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07201: Error loading all projects

Cause: Error loading all projects

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07202: Error loading project {0}

Cause: Error loading project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07203: Error deleting project {0}

Cause: Error deleting project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07204: Error saving project {0} {1}

Cause: Error saving project {0} {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07205: Error deleting doc {0}

Cause: Error deleting doc {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07206: Error saving doc {0} {1}

Cause: Error saving doc {0} {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07208: Error publishing template {0}

Cause: Error publishing template {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07209: Error deleting composite {0}

Cause: Error deleting composite {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07210: Error loading node: {0} {1}

Cause: Error loading node: {0} {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07211: Error loading compound processors

Cause: Error loading compound processors

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07212: There is no document version for process '{0}'

Cause: There is no document version for process '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07213: Error getting runtime process model for {0}

Cause: Error getting runtime process model for {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07214: Error loading process {0}

Cause: Error loading process {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07215: Project exception whilst formulating dependency message

Cause: Project exception whilst formulating dependency message

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07216: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07217: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07218: Failed load published processor: {0} Project: {1}

Cause: Failed load published processor: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07219: {0} XStore items found in import file: {1} {2} {3}

Cause: {0} XStore items found in import file: {1} {2} {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07220: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07221: Error inserting note

Cause: Error inserting note

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07222: Error updating note

Cause: Error updating note

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07223: Error deleting note

Cause: Error deleting note

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07224: Error loading notes

Cause: Error loading notes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00700: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Cause: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00701: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Cause: BusinessRules: Loading XLS Business Rules ''{0}'': {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00702: BusinessRules: Failed to encode Business Rules processor config document

Cause: BusinessRules: Failed to encode Business Rules processor config document

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00703: BusinessRules: Failed to decode Business Rules processor config document

Cause: BusinessRules: Failed to decode Business Rules processor config document

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00704: BusinessRules: Error opening/reading ref data

Cause: BusinessRules: Error opening/reading ref data

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04000: Failed to find cleaning task named: {0}

Cause: Failed to find cleaning task named: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04001: Cleaning task named: {0} isn't actually a cleaning task

Cause: Cleaning task named: {0} isn't actually a cleaning task

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04002: Failed to parse housekeeping configuration

Cause: Failed to parse housekeeping configuration

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04003: Failed to read housekeeping configuration file

Cause: Failed to read housekeeping configuration file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04004: Failed to parse start time for {0} defaulting to now

Cause: Failed to parse start time for {0} defaulting to now

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04005: Failed to find cleaning task named: {0}

Cause: Failed to find cleaning task named: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05000: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05001: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05002: Failed to decode user data attributes

Cause: Failed to decode user data attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09600: Problem getting known providers

Cause: Problem getting known providers

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09601: There was a problem deleting the user data for project {0}

Cause: There was a problem deleting the user data for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09602: Unable to delete user data table for imported user data whose definition has not been successfully created {0}

Cause: Unable to delete user data table for imported user data whose definition has not been successfully created {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09603: Error getting user data when validating lookup {0}

Cause: Error getting user data when validating lookup {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09604: Error closing user data writer to user data table with id {0}

Cause: Error closing user data writer to user data table with id {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09605: Error updating user data profile for user data {0}, when closing user data writer

Cause: Error updating user data profile for user data {0}, when closing user data writer

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09606: Error creating user data data: {0}

Cause: Error creating user data data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09607: Error creating staged data for user data: {0}

Cause: Error creating staged data for user data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09608: Failed to decode user data data profile

Cause: Failed to decode user data data profile

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09609: Failed to decode user data attributes

Cause: Failed to decode user data attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09610: Failed to encode user data attributes

Cause: Failed to encode user data attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09611: Failed to encode user data data profile

Cause: Failed to encode user data data profile

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09612: Error initialising data base table {0} to import user data {1}

Cause: Error initialising data base table {0} to import user data {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09613: Error closing data base table during import of user data {0}

Cause: Error closing data base table during import of user data {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03000: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03001: More than one tree item found for externalized property

Cause: More than one tree item found for externalized property

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03002: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05400: failed to decode iostreamingconfiguration string: {0}

Cause: failed to decode iostreamingconfiguration string: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05401: failed to encode ExportWriterMaps: {0}

Cause: failed to encode ExportWriterMaps: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05402: Skipping job with xml {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05403: Invalid xml, did not conform to xsd schema for jobs to be migrated: {0}: {1}

Cause: Invalid xml, did not conform to xsd schema for jobs to be migrated: {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05404: Property values different

Cause: Property values different

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02300: Data upload is cancelled so returning from data insert without inserting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02301: Total number of snapshot rows loaded for table {0} is {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02302: Cancelling queue for table {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02303: Error cancelling upload

Cause: Error cancelling upload

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02500: Error during diff

Cause: Error during diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06900: problem dropping temp counter table {0}

Cause: problem dropping temp counter table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06901: problem dropping temp stuffer table {0}

Cause: problem dropping temp stuffer table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06902: problem dropping temp record dump table {0}

Cause: problem dropping temp record dump table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06905: {0} : Error loading last process model for job {0} process {1}: {2}

Cause: {0} : Error loading last process model for job {0} process {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06907: {0} : failed to write process statistics

Cause: {0} : failed to write process statistics

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06908: {0} : failed to write last process model

Cause: {0} : failed to write last process model

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06909: {0} : problem saving basic run information: {0}

Cause: {0} : problem saving basic run information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06910: {0} : problem updating run information: {0}

Cause: {0} : problem updating run information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06911: {0} : error during cloud preparation

Cause: {0} : error during cloud preparation

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06912: {0} : absolutely nothing to do

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06913: {0} : [{1}] batch {2} terminated by exception: {3}

Cause: {0} : [{1}] batch {2} terminated by exception: {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06914: {0} : error during process preparation

Cause: {0} : error during process preparation

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06915: {0} : error during {1} preparation: {2}

Cause: {0} : error during {1} preparation: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06916: {0} : [{1}.{2}] batch {3} terminated by exception: {4}

Cause: {0} : [{1}.{2}] batch {3} terminated by exception: {4}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06917: {0} : started execution

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06918: {0} : finished execution in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06919: {0} : runtime process terminated uncleanly: {1}

Cause: {0} : runtime process terminated uncleanly: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06920: {0} : Failed to build new interval cloud: {1}

Cause: {0} : Failed to build new interval cloud: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06921: job {0}: invalid {1} option {2}

Cause: job {0}: invalid {1} option {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06922: job {0}: error loading process by name {1}

Cause: job {0}: error loading process by name {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06923: job {0}: process {1} loaded but is not valid

Cause: job {0}: process {1} loaded but is not valid

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06924: job {0}: unknown execution mode {1}

Cause: job {0}: unknown execution mode {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06925: job {0}: preparation and interval modes both set

Cause: job {0}: preparation and interval modes both set

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06926: job {0}: interval mode specified but no interval defined

Cause: job {0}: interval mode specified but no interval defined

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06927: job {0}: interval mode specified but interval is zero

Cause: job {0}: interval mode specified but interval is zero

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06928: job {0}: process {1}: '{2}' mode is not licensed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06929: job {0}: invalid {1} option {2} for item {3}

Cause: job {0}: invalid {1} option {2} for item {3}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06930: job {0}: process {1} item {2}: '{3}' mode is not licensed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06931: job {0}: process {1}: ignoring 'force run' because interval mode is set

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06932: job {0}: process {1}: removing interval mode

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06933: job {0}: process {1}: error creating runtime process

Cause: job {0}: process {1}: error creating runtime process

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06934: unknown interface attribute {0} in mapping

Cause: unknown interface attribute {0} in mapping

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06935: unknown real attribute {0} in mapping

Cause: unknown real attribute {0} in mapping

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06936: types of virtual attribute {0} and real attribute {1} do not match

Cause: types of virtual attribute {0} and real attribute {1} do not match

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06937: {0}: expression property missing for output {1}

Cause: {0}: expression property missing for output {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06938: {0}: error in expression '{1}': {2}

Cause: {0}: error in expression '{1}': {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06939: Preparing cloud for interval {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06940: Switching execution to interval {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06941: finished execution in {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06942: could not retrieve RunInformaiton for runId {0}: {1}

Cause: could not retrieve RunInformaiton for runId {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06943: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06944: Failed to encode processor runtime

Cause: Failed to encode processor runtime

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06945: Failed to decode processor runtime

Cause: Failed to decode processor runtime

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06946: data mode name {0} not recognised

Cause: data mode name {0} not recognised

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06947: error importing process {0}

Cause: error importing process {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06948: error creating munger result writer

Cause: error creating munger result writer

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06949: error closing result writer

Cause: error closing result writer

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06950: error preparing persister

Cause: error preparing persister

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06951: error opening resource {0}

Cause: error opening resource {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06952: error creating result writer

Cause: error creating result writer

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06953: error closing record source: {0}

Cause: error closing record source: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06954: Error cleaning up results publishing

Cause: Error cleaning up results publishing

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02100: Unknown interface attribute {0} in mapping

Cause: Unknown interface attribute {0} in mapping

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02101: Unknown real attribute {0} in mapping

Cause: Unknown real attribute {0} in mapping

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02102: Types of virtual attribute {0} and real attribute {1} do not match

Cause: Types of virtual attribute {0} and real attribute {1} do not match

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02103: Error parsing xml

Cause: Error parsing xml

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02104: Error encoding {0} "{1}"

Cause: Error encoding {0} "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02105: Data interface "{0}", mapping "{1}": {2}

Cause: Data interface "{0}", mapping "{1}": {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02106: Error loading {0} "{1}": {2}

Cause: Error loading {0} "{1}": {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02107: Error loading {0} "{1}"

Cause: Error loading {0} "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02108: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02109: Failed to decode interface

Cause: Failed to decode interface

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02110: Error encoding interface

Cause: Error encoding interface

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02111: Failed to get the Data Interface for Dependency Object: {0}, Project: {1}

Cause: Failed to get the Data Interface for Dependency Object: {0}, Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02112: Failed to decode interface mapping

Cause: Failed to decode interface mapping

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02113: Error encoding interface mapping

Cause: Error encoding interface mapping

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02114: Error creating staged data: {0}

Cause: Error creating staged data: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02115: Error during data interface diff

Cause: Error during data interface diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09300: Error during copy/paste: {0}

Cause: Error during copy/paste: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09301: Failed to export to file ''{0}''

Cause: Failed to export to file ''{0}''

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09302: Error importing from server

Cause: Error importing from server

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09303: Error importing from file

Cause: Error importing from file

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09304: Error loading associated nodes for ''{0}''

Cause: Error loading associated nodes for ''{0}''

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00500: JSJMS: InitialContext failure: {0}

Cause: JSJMS: InitialContext failure: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00501: JSJMS: failed to lookup connection factory ''{0}'': {1}

Cause: JSJMS: failed to lookup connection factory ''{0}'': {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00502: JSJMS: failed to lookup destination ''{0}'': {1}

Cause: JSJMS: failed to lookup destination ''{0}'': {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00503: JSJMS: failed to create connection: {0}

Cause: JSJMS: failed to create connection: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00504: JSJMS: failed to create session: {0}

Cause: JSJMS: failed to create session: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00505: JSJMS: failed to message producer: {0}

Cause: JSJMS: failed to message producer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00506: JSJMS: error closing producer: {0}

Cause: JSJMS: error closing producer: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00507: JSJMS: error closing session: {0}

Cause: JSJMS: error closing session: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00509: JSJMS: error closing initial context: {0}

Cause: JSJMS: error closing initial context: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00510: JSJMS: error sending message: {0}

Cause: JSJMS: error sending message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00511: JSJMS: error creating text message: {0}

Cause: JSJMS: error creating text message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00512: JSJMS: error creating map message: {0}

Cause: JSJMS: error creating map message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00513: JSJMS: error setting field {0} in map message: {1}

Cause: JSJMS: error setting field {0} in map message: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08000: Starting execution of results export {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-08001: Error running results export {0} : result set is null

Cause: Error running results export {0} : result set is null

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08002: Export error : {0}

Cause: Export error : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08003: Finished execution in {0}s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-08004: Cancelling job

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-08005: Interrupted while waiting: {0}

Cause: Interrupted while waiting: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08006: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08007: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08009: Failed to decode result set export

Cause: Failed to decode result set export

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08010: Failed to encode result

Cause: Failed to encode result

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08011: Error getting result set export : {0}

Cause: Error getting result set export : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08012: Error deleting result set export

Cause: Error deleting result set export

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08013: Error importing result set export: {0}

Cause: Error importing result set export: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08014: Prepare error: {0}

Cause: Prepare error: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08015: There was a problem deleting the result set exports for project {0}

Cause: There was a problem deleting the result set exports for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08016: Error retrieving details of result set export for dependencies

Cause: Error retrieving details of result set export for dependencies

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08017: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08018: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06500: Error in schema while loading permissions

Cause: Error in schema while loading permissions

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06501: LoadPerms: {0} missing in file "{1}"

Cause: LoadPerms: {0} missing in file "{1}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06502: LoadPerms: error parsing {0} in file "{1}"

Cause: LoadPerms: error parsing {0} in file "{1}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06503: LoadPerms: error reading file "{0}"

Cause: LoadPerms: error reading file "{0}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06504: Failed to load schema file {0}: {1}

Cause: Failed to load schema file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06505: Error looking up /WEB-INF/{0}: {1}

Cause: Error looking up /WEB-INF/{0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06506: Error looking up /META-INF/{0}: {1}

Cause: Error looking up /META-INF/{0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06507: Error parsing actions configuration file at {0}: {1}

Cause: Error parsing actions configuration file at {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06508: Error reading from actions configuration file at {0}: {1}

Cause: Error reading from actions configuration file at {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06600: Runtime exception in phrase profiler: {0}

Cause: Runtime exception in phrase profiler: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04500: Error loading issue list for xtree

Cause: Error loading issue list for xtree

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04501: [retrieveProjectIssues] Invalid parameters for dao method

Cause: [retrieveProjectIssues] Invalid parameters for dao method

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04502: [retrieveAllIssuesByAssginedTo] Invalid parameters for dao method

Cause: [retrieveAllIssuesByAssginedTo] Invalid parameters for dao method

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04503: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to insert issue data. The message was {0}

Cause: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to insert issue data. The message was {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04504: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Cause: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04505: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Cause: DNInvalidQueryParametersException. Invalid parameters for dao method. Unable to update issue data. The message was {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08700: SCCS workspace is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-08701: SCCS scan failed: {0}

Cause: SCCS scan failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08702: SCCS: Configuration database is not compatible with workspace: {0}

Cause: SCCS: Configuration database is not compatible with workspace: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08703: SCCS: Scan request for unrecognized file "{0}": ignored

Cause: SCCS: Scan request for unrecognized file "{0}": ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08704: SCCS: File system commit/rollback failed: CHECK CONSISTENTY!

Cause: SCCS: File system commit/rollback failed: CHECK CONSISTENTY!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08705: SCCS: State query failed: {0}

Cause: SCCS: State query failed: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08706: SCCS RevsionStore: diff with empty path and no local file: ignored

Cause: SCCS RevsionStore: diff with empty path and no local file: ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08707: SCCS: Clear dependencies for {0} failed: {1}

Cause: SCCS: Clear dependencies for {0} failed: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08708: SCCS: Error during project delete: {0}

Cause: SCCS: Error during project delete: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08709: VCS: system version property not set on workspace

Cause: VCS: system version property not set on workspace

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08710: VCS: Incorrect system version on workspace: "{0}" found, "{1}" expected

Cause: VCS: Incorrect system version on workspace: "{0}" found, "{1}" expected

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08711: VCS: Invalid server credentials mode "{0}": ignored

Cause: VCS: Invalid server credentials mode "{0}": ignored

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08712: SCCS meta-data migrated to database: directory {0} is no longer required

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-08750: SCCS: SVNKit commit error: {0}

Cause: SCCS: SVNKit commit error: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08751: SCCS: SVNKit error reverting "{0}" after failed commit: {1}

Cause: SCCS: SVNKit error reverting "{0}" after failed commit: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08752: SCCS: GSS exception using delegated credentials: {0}

Cause: SCCS: GSS exception using delegated credentials: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08760: SCCS: JavaHL commit error: {0}

Cause: SCCS: JavaHL commit error: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04600: Schema '{0}' load failed!

Cause: Schema '{0}' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04601: Failed to decode job

Cause: Failed to decode job

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04602: Cannot find option transcoder for option "{0}"

Cause: Cannot find option transcoder for option "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04603: Error during job diff {0}

Cause: Error during job diff {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04604: Error encoding job: {0}

Cause: Error encoding job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04605: Database error creating job: {0}

Cause: Database error creating job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04606: Error adding dependencies when creating job: {0}

Cause: Error adding dependencies when creating job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04607: Error encoding job: {0}

Cause: Error encoding job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04608: Database error saving job: {0}

Cause: Database error saving job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04609: Error replacing dependencies when saving job: {0}

Cause: Error replacing dependencies when saving job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04610: Database error renaming job: {0}

Cause: Database error renaming job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04611: Database error deleting job: {0}

Cause: Database error deleting job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04612: Error deleting dependencies when deleting job: {0}

Cause: Error deleting dependencies when deleting job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04613: A database error occurred loading XTree nodes: {0}

Cause: A database error occurred loading XTree nodes: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04614: A database error occurred loading an XTree node: {0}

Cause: A database error occurred loading an XTree node: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04615: A database error occurred loading a job: {0}

Cause: A database error occurred loading a job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04616: An error occurred decoding job: {0}

Cause: An error occurred decoding job: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04617: Error, job id: {0} could not be loaded

Cause: Error, job id: {0} could not be loaded

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04618: Unknown task type: {0}

Cause: Unknown task type: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04619: A database error occurred retrieving node for dependency subject: {0}

Cause: A database error occurred retrieving node for dependency subject: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04620: A database error occurred retrieving node for dependency object: {0}

Cause: A database error occurred retrieving node for dependency object: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04621: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04622: An error occurred retrieving trigger names: {0}

Cause: An error occurred retrieving trigger names: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05300: Unable to parse BulkReview XML record: {0}

Cause: Unable to parse BulkReview XML record: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05301: Failed to load xml with error {0}

Cause: Failed to load xml with error {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05302: Failed to create Bulk Review schema: {0}

Cause: Failed to create Bulk Review schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05303: Failed to save bulk review details with error {0}

Cause: Failed to save bulk review details with error {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05304: Failed to delete bulk review details xml with error {0}

Cause: Failed to delete bulk review details xml with error {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05305: Failed to read column ordering xml with error {0}

Cause: Failed to read column ordering xml with error {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05306: Failed to create and configure schema {0}

Cause: Failed to create and configure schema {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05307: Unable to read custom decisions xml: {0}

Cause: Unable to read custom decisions xml: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05308: Unable to read decision statistics xml: {0}

Cause: Unable to read decision statistics xml: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05309: Unable to read review statistics xml: {0}

Cause: Unable to read review statistics xml: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05310: Unable to read match statistics xml: {0}

Cause: Unable to read match statistics xml: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05311: Match relationships output contains references to unknown flag: {0}

Cause: Match relationships output contains references to unknown flag: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05312: Unable to parse Match document xml: {0}

Cause: Unable to parse Match document xml: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05313: Failed to add transformation to comparison: {0}

Cause: Failed to add transformation to comparison: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05314: Failed to move transformation up in the list: {0}

Cause: Failed to move transformation up in the list: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05315: Failed to move transformation down in the list: {0}

Cause: Failed to move transformation down in the list: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05316: Failed to add decision detail to document: {0}

Cause: Failed to add decision detail to document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05317: Unable to initialise helper: {0}

Cause: Unable to initialise helper: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05318: Unable to add attribute: {0}

Cause: Unable to add attribute: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05319: There was a problem reading from makeBundle

Cause: There was a problem reading from makeBundle

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05320: Match library has no search path configured

Cause: Match library has no search path configured

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05321: Match library has no configuration Jars to load

Cause: Match library has no configuration Jars to load

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05322: Error exporting decisions

Cause: Error exporting decisions

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05323: Search groups, error accessing results database

Cause: Search groups, error accessing results database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05324: Data access error selecting group IDs when clearing search: {0}

Cause: Data access error selecting group IDs when clearing search: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05325: Results database error selecting group IDs when clearing search: {0}

Cause: Results database error selecting group IDs when clearing search: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05326: Data access error selecting group IDs when caching groups: {0}

Cause: Data access error selecting group IDs when caching groups: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05327: Results database error selecting group IDs when caching groups: {0}

Cause: Results database error selecting group IDs when caching groups: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05328: Unable to retrieve match process: {0}

Cause: Unable to retrieve match process: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05330: Results database error retrieving records for group: {0}

Cause: Results database error retrieving records for group: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05331: I/O error retrieving records for group: {0}

Cause: I/O error retrieving records for group: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05332: Data access error retrieving records for group: {0}

Cause: Data access error retrieving records for group: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05333: Process failed when retrieving records for group: {0}

Cause: Process failed when retrieving records for group: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05334: Data access error when adding a comment: {0}

Cause: Data access error when adding a comment: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05335: Results Database error when adding a comment: {0}

Cause: Results Database error when adding a comment: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05336: Failed to delete comment, since it wasn't found in db

Cause: Failed to delete comment, since it wasn't found in db

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05337: Data access error when deleting a comment: {0}

Cause: Data access error when deleting a comment: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05338: Results Database error when deleting a comment: {0}

Cause: Results Database error when deleting a comment: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05339: Data access error in review decision: {0}

Cause: Data access error in review decision: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05340: Process failed in review decision: {0}

Cause: Process failed in review decision: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05341: Results Database error in review decision: {0}

Cause: Results Database error in review decision: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05342: Data access error in querying review group state: {0}

Cause: Data access error in querying review group state: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05343: Results Database error querying review group state: {0}

Cause: Results Database error querying review group state: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05344: Data access error retrieving comment history: {0}

Cause: Data access error retrieving comment history: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05345: Results Database error retrieving comment history: {0}

Cause: Results Database error retrieving comment history: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05346: Data access error retrieving decision history: {0}

Cause: Data access error retrieving decision history: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05347: Results Database error retrieving decision history: {0}

Cause: Results Database error retrieving decision history: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05348: Manual decisions deleted by {0} on {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05349: An error occurred updating statistics when deleting decisions: {0}

Cause: An error occurred updating statistics when deleting decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05350: Error dropping table when deleting decisions: {0}

Cause: Error dropping table when deleting decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05351: Error creating match review incident when deleting decisions: {0}

Cause: Error creating match review incident when deleting decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05352: Realtime review tables deleted by {0} on {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05353: Unable to drop table when deleting realtime review records: {0}

Cause: Unable to drop table when deleting realtime review records: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05354: Error creating match review incident when deleting real-time review records: {0}

Cause: Error creating match review incident when deleting real-time review records: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05356: Unknown comparison '{0}'

Cause: Unknown comparison '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05357: Unknown attribute '{0}' on identifier '{0}'

Cause: Unknown attribute '{0}' on identifier '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05358: Unknown identifier '{0}'

Cause: Unknown identifier '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05359: Unknown selection '{0}'

Cause: Unknown selection '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05360: Unknown transformation '{0}'

Cause: Unknown transformation '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05362: {0} groups of size {1}

Cause: {0} groups of size {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05363: Error while importing decisions: {0}

Cause: Error while importing decisions: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05364: Invalid incoming decision record: {0}

Cause: Invalid incoming decision record: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05365: Error migrating comments: {0}

Cause: Error migrating comments: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05366: Error migrating decisions: {0}

Cause: Error migrating decisions: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05367: Exception occurred reading output decisions: {0}

Cause: Exception occurred reading output decisions: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05368: A problem occurred reading relationship sets from the database: {0}

Cause: A problem occurred reading relationship sets from the database: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05369: A problem occurred reading relationships from the database: {0}

Cause: A problem occurred reading relationships from the database: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05370: A problem occurred reading cluster records from the database: {0}

Cause: A problem occurred reading cluster records from the database: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05371: A problem occurred processing clusters: {0}

Cause: A problem occurred processing clusters: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05372: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Cause: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05373: Unable to read case '{0}'

Cause: Unable to read case '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05374: Unable to read case issues:

Cause: Unable to read case issues:

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05375: A Problem occurred reading clusters as output groups: {0}

Cause: A Problem occurred reading clusters as output groups: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05376: A Problem occurred reading records grouped by issue: {0}

Cause: A Problem occurred reading records grouped by issue: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05377: A Problem occurred reading output groups: {0}

Cause: A Problem occurred reading output groups: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05378: Migrating decisions

Cause: Migrating decisions

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05379: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Cause: Relationship found with records not in the same group. Ensure that working records share group option is selected if comparing against self.

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05380: Unable to read case '{0}'

Cause: Unable to read case '{0}'

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05381: Unable to read case issues:

Cause: Unable to read case issues:

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05382: A problem occurred processing issue group: {0}

Cause: A problem occurred processing issue group: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05383: A problem occurred processing review group: {0}

Cause: A problem occurred processing review group: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05385: A data related error occurred in clear up: {0}

Cause: A data related error occurred in clear up: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05386: Process aborted on clear up: {0}

Cause: Process aborted on clear up: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05387: An XML parse error occurred importing decisions: {0}

Cause: An XML parse error occurred importing decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05388: A data error occurred importing decisions: {0}

Cause: A data error occurred importing decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05389: A transfer error occurred importing decisions: {0}

Cause: A transfer error occurred importing decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05390: An I/O error occurred importing decisions: {0}

Cause: An I/O error occurred importing decisions: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05392: A data related error occurred in clear up: {0}

Cause: A data related error occurred in clear up: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05393: Process aborted on clear up: {0}

Cause: Process aborted on clear up: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05395: Real-time buckets, there was a problem closing a writer: {0}

Cause: Real-time buckets, there was a problem closing a writer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05396: Unable to create table {0} as it already exists

Cause: Unable to create table {0} as it already exists

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05397: Unable to close decision audit migration data writer: {0}

Cause: Unable to close decision audit migration data writer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05398: Unable to close bulk review data writer: {0}

Cause: Unable to close bulk review data writer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05399: Unable to close bulk review persistent record writer: {0}

Cause: Unable to close bulk review persistent record writer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10600: Error creating group table for match process, process id {0} processor num {1} : {2}

Cause: Error creating group table for match process, process id {0} processor num {1} : {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10601: New decision Id: {0} has an unrecognised match type and will be ignored. The allowed match types are {match, nomatch, possiblematch, pending}

Cause: New decision Id: {0} has an unrecognised match type and will be ignored. The allowed match types are {match, nomatch, possiblematch, pending}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10602: New decision Id: {0} replaces a default decision but has a different Match Type. This is not allowed and so will be ignored

Cause: New decision Id: {0} replaces a default decision but has a different Match Type. This is not allowed and so will be ignored

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10603: Reference to unknown formal attribute in cluster "{0}"

Cause: Reference to unknown formal attribute in cluster "{0}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10604: Reference to unknown source attribute in cluster "{0}"

Cause: Reference to unknown source attribute in cluster "{0}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10605: A problem occurred adding a formal attribute to a cluster configuration: {0}

Cause: A problem occurred adding a formal attribute to a cluster configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10606: A problem occurred loading result band configuration: {0}

Cause: A problem occurred loading result band configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10607: A problem occurred loading decisions output attribute configuration: {0}

Cause: A problem occurred loading decisions output attribute configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10608: Formal attribute {0}.{1} contains mapping from unknown source object {2}

Cause: Formal attribute {0}.{1} contains mapping from unknown source object {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10609: A problem occurred processing source attribute: {0}

Cause: A problem occurred processing source attribute: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10610: A problem occurred loading groups output attribute configuration: {0}

Cause: A problem occurred loading groups output attribute configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10611: A problem occurred loading identifier configuration: {0}

Cause: A problem occurred loading identifier configuration: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10612: A problem occurred loading input configuration: {0}

Cause: A problem occurred loading input configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10613: A problem occurred loading merged output configuration: {0}

Cause: A problem occurred loading merged output configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10614: A problem occurred loading merged output configuration: {0}

Cause: A problem occurred loading merged output configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10615: A problem occurred loading input configuration in persistent input loader: {0}

Cause: A problem occurred loading input configuration in persistent input loader: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10616: A problem occurred loading relationship output configuration: {0}

Cause: A problem occurred loading relationship output configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10617: A problem occurred loading rule configuration: {0}

Cause: A problem occurred loading rule configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10618: Merged attribute "{0}" contains reference to unknown source attribute "{1}"

Cause: Merged attribute "{0}" contains reference to unknown source attribute "{1}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10619: A problem occurred loading a transformation set configuration: {0}

Cause: A problem occurred loading a transformation set configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10620: Unable to create new cluster: {0}

Cause: Unable to create new cluster: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10621: Unable to add formal attribute: {0}

Cause: Unable to add formal attribute: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10622: Unable to add transformation to attribute: {0}

Cause: Unable to add transformation to attribute: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10623: Transformation lists are not equivalent

Cause: Transformation lists are not equivalent

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10624: Unable to move transformation up: {0}

Cause: Unable to move transformation up: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10625: Unable to move transformation down: {0}

Cause: Unable to move transformation down: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10626: Unable to replace old attribute list with new one: {0}

Cause: Unable to replace old attribute list with new one: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10627: Unable to swap attributes: {0}

Cause: Unable to swap attributes: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10628: Transformation lists are not equivalent

Cause: Transformation lists are not equivalent

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10630: Unable to automatically map identifiers: {0}

Cause: Unable to automatically map identifiers: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10631: A problem occurred mapping a source attribute to a formal attribute instance: {0}

Cause: A problem occurred mapping a source attribute to a formal attribute instance: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10632: A problem occurred adding an identifier: {0}

Cause: A problem occurred adding an identifier: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10633: A problem occurred adding multiple identifiers: {0}

Cause: A problem occurred adding multiple identifiers: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10634: A problem occurred reordering attributes: {0}

Cause: A problem occurred reordering attributes: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10635: A problem occurred when setting up the match process inputs: {0}

Cause: A problem occurred when setting up the match process inputs: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10636: A problem occurred updating persistent inputs with new information: {0}

Cause: A problem occurred updating persistent inputs with new information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10637: A problem occurred parsing the results comparison default element: {0}

Cause: A problem occurred parsing the results comparison default element: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10638: Unable to parse attribute XML when reading identifier definition: {0}

Cause: Unable to parse attribute XML when reading identifier definition: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10639: Unable to parse identifier definition XML: {0}

Cause: Unable to parse identifier definition XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10640: Identifier definition '{0}' has no formal attributes

Cause: Identifier definition '{0}' has no formal attributes

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10641: Import Match Library: Match library file '{0}' not found in '{1}'

Cause: Import Match Library: Match library file '{0}' not found in '{1}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10642: Import Match Library: Match Library: In file '{0}': {1}

Cause: Import Match Library: Match Library: In file '{0}': {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10643: Import Match Library Mappings: Match library file '{0}' not found in '{1}'

Cause: Import Match Library Mappings: Match library file '{0}' not found in '{1}'

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10644: Import Match Library Mappings: Match Library: In file '{0}': {1}

Cause: Import Match Library Mappings: Match Library: In file '{0}': {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10645: Parse Match Library: Unable to parse identifier definition XML: {0}

Cause: Parse Match Library: Unable to parse identifier definition XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10646: Parse Match Library: Unable to parse comparison default result XML: {0}

Cause: Parse Match Library: Unable to parse comparison default result XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10647: Parse Match Library Mappings: Unable to parse identifier comparison mapping XML: {0}

Cause: Parse Match Library Mappings: Unable to parse identifier comparison mapping XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10648: The match configuration is null.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10649: The match configuration is null, unable to obtain a process.

Cause: The match configuration is null, unable to obtain a process.

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10650: Unable to load lookup information for checking dependencies : {0}

Cause: Unable to load lookup information for checking dependencies : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10651: Match encountered a record from an unknown connection {0}

Cause: Match encountered a record from an unknown connection {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10652: Match encountered a message from an unknown connection {0} on port {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10653: A failure occurred in the mission manager: {0}

Cause: A failure occurred in the mission manager: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10654: An error occurred copying table

Cause: An error occurred copying table

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10656: Using record count of 0 due to error: {0}

Cause: Using record count of 0 due to error: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10657: Unable to read case issues:

Cause: Unable to read case issues:

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10658: Error creating table {0} for writing relationship comments

Cause: Error creating table {0} for writing relationship comments

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10659: Error creating table {0} for writing relationship decisions

Cause: Error creating table {0} for writing relationship decisions

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10660: Error creating the merged comment table {0}

Cause: Error creating the merged comment table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10662: Error creating the merged decision details table {0}

Cause: Error creating the merged decision details table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10663: Error creating the merged output status table {0}

Cause: Error creating the merged output status table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10664: Unable to read case issues:

Cause: Unable to read case issues:

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10665: Error creating merge decision table {0}

Cause: Error creating merge decision table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10666: Error creating merge decision detail table {0}

Cause: Error creating merge decision detail table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10667: Error creating merge comment table {0}

Cause: Error creating merge comment table {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10668: Unable to read case issues:

Cause: Unable to read case issues:

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04400: Job analysis daemon interrupted: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-04401: Unable to start process: {0}

Cause: Unable to start process: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04402: Unable to parse CPU statistics line

Cause:

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04403: Unable to parse device statistics line

Cause: Unable to parse device statistics line

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04404: Unexpected line in iostat output: {0}

Cause: Unexpected line in iostat output: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04405: Error processing iostat line: {0}

Cause: Error processing iostat line: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04406: Unexpected termination of process. {0}

Cause: Unexpected termination of process. {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04407: Creating appropriate system reporter for {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-04408: No appropriate system report available for OS

Cause: No appropriate system report available for OS

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04409: Unable to start process: {0}

Cause: Unable to start process: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04410: Unexpected termination of process. {0}

Cause: Unexpected termination of process. {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04411: Failed to validate XML document: {0}

Cause: Failed to validate XML document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04412: Configuration error encoding job analysis bean: {0}

Cause: Configuration error encoding job analysis bean: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04413: Error transforming XML to result: {0}

Cause: Error transforming XML to result: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04414: Parser configuration error encoding job analysis bean: {0}

Cause: Parser configuration error encoding job analysis bean: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04415: Stopping instrumentation analysis streamer: {0}

Cause: Stopping instrumentation analysis streamer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04416: Thread interrupted

Cause: Thread interrupted

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04417: Could not find JobInformation for {0} {1}

Cause: Could not find JobInformation for {0} {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04418: Error storing job statistics

Cause: Error storing job statistics

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04419: Expecting device tag

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-08200: An error has occurred : {0}

Cause: An error has occurred : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08100: Error retrieving data

Cause: Error retrieving data

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08101: Error loaading resultset {0} in project {1}: {2}

Cause: Error loaading resultset {0} in project {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08102: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08103: Provider error: {0}

Cause: Provider error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08104: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08105: Failed to load view definition

Cause: Failed to load view definition

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08106: Schema '{0}' load failed

Cause: Schema '{0}' load failed

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08107: Failed to decode result

Cause: Failed to decode result

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08109: Unable to retrieve process id from name while migrating results book

Cause: Unable to retrieve process id from name while migrating results book

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08110: Unable to retrieve run information while migrating results book

Cause: Unable to retrieve run information while migrating results book

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08111: Unable to retrieve staged data definition id from name while migrating results book

Cause: Unable to retrieve staged data definition id from name while migrating results book

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08112: Unable to find results item from previous xml definition

Cause: Unable to find results item from previous xml definition

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08113: Unable to match results book page mapping columns from previous xml definition for {0}. This view will be reconstructed

Cause: Unable to match results book page mapping columns from previous xml definition for {0}. This view will be reconstructed

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-08114: Unable to find candidate from previous xml definition, the id was: {0}

Cause: Unable to find candidate from previous xml definition, the id was: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08115: Error retrieving result set: {0}

Cause: Error retrieving result set: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08116: Error deleting result set: {0}

Cause: Error deleting result set: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08118: There was a problem deleting the results books for project {0}

Cause: There was a problem deleting the results books for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08119: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Object: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-08120: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Cause: Failed to get the XTreeNode for Dependency Subject: {0} Project: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10200: Error storing zip file in database

Cause: Error storing zip file in database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10201: Error deleting zip file from database

Cause: Error deleting zip file from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10202: Error loading zip {0} from database

Cause: Error loading zip {0} from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10203: Error listing entries in zip {0}

Cause: Error listing entries in zip {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10204: Error getting entry from zip {0}

Cause: Error getting entry from zip {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10205: Error storing zip file in database

Cause: Error storing zip file in database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10206: Error in zip servlet

Cause: Error in zip servlet

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07900: Table remover error : {0}

Cause: Table remover error : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07901: Work unit error: {0}

Cause: Work unit error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07902: Explain error: {0}

Cause: Explain error: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07903: Unable to index table '{0}' : {1}

Cause: Unable to index table '{0}' : {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07904: Unable to analyse table '{0}' : {1}

Cause: Unable to analyse table '{0}' : {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07905: Index error: {0}

Cause: Index error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07906: Malformed UUID in {0}/{1}/{2}

Cause: Malformed UUID in {0}/{1}/{2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07907: Error while dropping table '{0}' : {1}

Cause: Error while dropping table '{0}' : {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07908: There was an error inserting entry for {0} and processId {1} into the DNProcessOwnedDataTable table because it exists already

Cause: There was an error inserting entry for {0} and processId {1} into the DNProcessOwnedDataTable table because it exists already

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07909: There was an error retrieving existing tables for processId {0} from the processowneddata table

Cause: There was an error retrieving existing tables for processId {0} from the processowneddata table

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07910: Table did not exist {0} although the processowneddata table indicates that it should for process with id {1}

Cause: Table did not exist {0} although the processowneddata table indicates that it should for process with id {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07911: There was an error deleting table entries from DNRunOwnsResultsTable for process {0}

Cause: There was an error deleting table entries from DNRunOwnsResultsTable for process {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07912: Could not get the properties for the results database

Cause: Could not get the properties for the results database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07913: Not inserting value into dn_identity table for dn_runinformation as it already exists

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07914: SQLException when trying to enter value into dn_identity table for dn_runinformation

Cause: SQLException when trying to enter value into dn_identity table for dn_runinformation

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07915: There was an error retrieving existing tables for processId {0} from the DNProcessOwnsResultTable table

Cause: There was an error retrieving existing tables for processId {0} from the DNProcessOwnsResultTable table

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10700: {0} Error writing summary metric

Cause: {0} Error writing summary metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10701: {0} Patternmap resource missing

Cause: {0} Patternmap resource missing

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10702: {0} Bad preprocess parameter "{1}"

Cause: {0} Bad preprocess parameter "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10703: {0} Error writing counter metric

Cause: {0} Error writing counter metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10704: {0} Invalid number format "{1}"

Cause: {0} Invalid number format "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10705: {0} Invalid date format "{1}"

Cause: {0} Invalid date format "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10706: {0} Unknown postprocess option {1}

Cause: {0} Unknown postprocess option {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10707: {0} Expression missing

Cause: {0} Expression missing

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10710: {0} Invalid band minimum "{1}"

Cause: {0} Invalid band minimum "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10711: {0} Invalid format "{1}"

Cause: {0} Invalid format "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10712: Regex Match expression is invalid "{0}"

Cause: Regex Match expression is invalid "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10713: {0} The regular expression entered is invalid: {1}

Cause: {0} The regular expression entered is invalid: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10714: {0} Resource {1} contains an invalid pattern "{2}"

Cause: {0} Resource {1} contains an invalid pattern "{2}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10715: {0} {1} resource missing

Cause: {0} {1} resource missing

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10716: {0} Resource query error

Cause: {0} Resource query error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10717: {0} Resource count error

Cause: {0} Resource count error

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10718: Issued non blocking call - waiting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10719: Wait complete

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00200: Address Doctor calculate error: {0}

Cause: Address Doctor calculate error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00201: Address Doctor Initialised

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00300: Could not get the properties for the database

Cause: Could not get the properties for the database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00301: Autorun dbscript chore failed to run. No database script file at {0}

Cause: Autorun dbscript chore failed to run. No database script file at {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00302: SQL error while processing dbscript chore in file {0}. Error: {1}

Cause: SQL error while processing dbscript chore in file {0}. Error: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00303: AutoRun: file {0} already exists. Aborting package!

Cause: AutoRun: file {0} already exists. Aborting package!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00304: {0} node "{1}" not found in autorun package export

Cause: {0} node "{1}" not found in autorun package export

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00305: Schema ''{0}'' load failed!

Cause: Schema ''{0}'' load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00306: Failed to encode chores {0}

Cause: Failed to encode chores {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00307: Failed to decode chores {0}

Cause: Failed to decode chores {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00308: AutoRun: file does not exist: {0}

Cause: AutoRun: file does not exist: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00309: AutoRun: Executing file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00310: AutoRun: File does not exist, event though previously checked {0}

Cause: AutoRun: File does not exist, event though previously checked {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00311: AutoRun: error reading file: {0}

Cause: AutoRun: error reading file: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00312: Invalid chores xml

Cause: Invalid chores xml

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00313: AutoRun: {0}

Cause: AutoRun: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00314: AutoRun: has nothing to do!

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00315: AutoRun: Package export complete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00316: AutoRun: file {0} already exists. Aborting download {1}

Cause: AutoRun: file {0} already exists. Aborting download {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00317: AutoRun: From url: {0}, To file: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00318: AutoRun: Download complete: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00319: AutoRun: Package import: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00320: AutoRun: Package import: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00321: AutoRun: Cannot run job - project {0} not found

Cause: AutoRun: Cannot run job - project {0} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00322: AutoRun: Cannot run job - job {0} not found

Cause: AutoRun: Cannot run job - job {0} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00900: Capscan: Bad Connection: {0}

Cause: Capscan: Bad Connection: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00901: Capscan: Failed to get pool info for pool {0} with error {1}

Cause: Capscan: Failed to get pool info for pool {0} with error {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00902: Capscan: Capscan failed to connect to server: {0}, pool: {1}

Cause: Capscan: Capscan failed to connect to server: {0}, pool: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00903: Capscan: Failed to switch to pool {0} on {1}

Cause: Capscan: Failed to switch to pool {0} on {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09000: Error ending transaction

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09001: Unsupported data type {0} from external database

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09002: Error closing data uploader for staged data id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09003: Error closing results

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09004: Error closing query

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09005: Error updating snapshot data profile and optimizing for browsing

Cause: Error occurred accessing the configuration database while writing the snapshot data profile.

Action: Check the server logs for errors.
Level: 1

Type: ERROR

Impact: Other

Cause: Error occurred submitting the optimize for browsing task for execution

Action: Check the server logs for errors.

EDQ-09006: {0} XStore items found in import file: {1}, {2}, {3}

Cause: The package (DXI) file is incomplete or corrupt.

Action: Create a new copy of the package file.
Level: 1

Type: ERROR

Impact: Other

EDQ-09007: {0} staged data XTree nodes found in import file: {1}, {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09008: Attribute defns not found for snapshot {0}

Cause: The package (DXI) file is incomplete or corrupt.

Action: Create a new copy of the package file
Level: 1

Type: ERROR

Impact: Other

EDQ-09009: {0} externalized property XTree nodes found in import file: {1}, {2}

Cause: The package (DXI) file is incomplete or corrupt.

Action: Create a new copy of the package file.
Level: 1

Type: ERROR

Impact: Other

EDQ-09010: Error importing snapshot

Cause: The package (DXI) file is incomplete or corrupt.

Action: Create a new copy of the package file.
Level: 1

Type: ERROR

Impact: Other

Cause: Error occurred accessing the configuration database while writing the imported snapshot.

Action: Contact support.

EDQ-09011: Failed to decode snapshot

Cause: The XML document for the snapshot was invalid.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09012: Failed to encode snapshot

Cause: The generated XML did not conform to the schema or there was an XML configuration error

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09013: Error purging project snapshots

Cause: Error removing snapshot tables from the results database.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09014: Snapshot executing: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-09015: Error preparing optimize task during snapshot execution

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09016: Snapshot ending execution immediately

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-09017: Error uploading snapshot data

Cause: Failed while loading data into the results database.

Action: Check the logs for errors and contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09018: Error ending upload of snapshot data

Cause: Failed while loading data into the results database.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09019: Error during snapshot execution: {0}

Cause: Failed while running a snapshot.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09020: Snapshot {0} finished execution in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-09021: Error during snapshot configuration analysis

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09022: Error getting snapshot

Cause: Error occurred loading the snapshot definition from the configuration data store.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09023: Error deleting staged data

Cause: Error occurred deleting the snapshot definition from the configuration data store.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09024: Problem retrieving snapshot providers

Cause: Error occurred loading the snapshot definitions from the configuration data store.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09025: There was a problem updating the local flag on snapshots dependent on data source

Cause:

Action:
Level: 1

Type: WARNING

Impact:

EDQ-09026: There was a problem deleting the snapshots for project {0}

Cause: Error occurred deleting the snapshot definitions for the project from the configuration data store.

Action: Contact support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03100: Processing resource jars

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03101: Failed to parse schema: {0}

Cause: Failed to parse schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03103: {0} not found in resources file {1}

Cause: {0} not found in resources file {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03104: Could not parse {0} in {1}: {2}

Cause: Could not parse {0} in {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03105: No resources listed in {0}

Cause: No resources listed in {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03106: Cannot locate resource class {0} in {1}

Cause: Cannot locate resource class {0} in {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03107: Cannot initialize resource class {0} in {1}: {2}

Cause: Cannot initialize resource class {0} in {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03108: Resource class {0} in {1} does not extend {2}

Cause: Resource class {0} in {1} does not extend {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03109: Error creating a {0}: {1}

Cause: Error creating a {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03110: Configure failed for {0} in {1}: {2}

Cause: Configure failed for {0} in {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03111: Error reading from resources file {0}: {1}

Cause: Error reading from resources file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03112: Invalid database species type for resource: {0}

Cause: Invalid database species type for resource: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03113: Error initialising external database resource handle: {0}

Cause: Error initialising external database resource handle: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03114: Error querying datastore {0}: {1}

Cause: Error querying datastore {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03115: Failed to encode external lookup xml

Cause: Failed to encode external lookup xml

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03116: Failed to decode external lookup xml

Cause: Failed to decode external lookup xml

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03117: DataSourceException trying to retrieve data source {0} for lookup {1}

Cause: DataSourceException trying to retrieve data source {0} for lookup {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03118: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03119: Failed to load external resource configuration: {0}

Cause: Failed to load external resource configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03120: Failed to encode external resource

Cause: Failed to encode external resource

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03121: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03122: Starting migration of file {0} as current version is less than file version.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03123: Could not convert file {0} as the resource structure is different from the existing user data.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03124: Finished migration of file. Migrated {0} rows.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03125: Starting migration of file {0} as no current version found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03126: Failed to create/update User Data {0} where migrating file

Cause: Failed to create/update User Data {0} where migrating file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03127: Failed to create Lookup {0} when migrating file

Cause: Failed to create Lookup {0} when migrating file

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03128: Failed to save User Data data for {0}

Cause: Failed to save User Data data for {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03129: Failed to save User Data data for {0}, unable to get lock

Cause: Failed to save User Data data for {0}, unable to get lock

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03130: Failed to save User Data data for {0}, insufficient permission: {1}

Cause: Failed to save User Data data for {0}, insufficient permission: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03131: There was a problem deleting the lookup for project {0}

Cause: There was a problem deleting the lookup for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03132: Unable to get dependencies for lookups based on : {0}

Cause: Unable to get dependencies for lookups based on : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03133: Unable to get data profile for lookup based upon underlying with name {0}

Cause: Unable to get data profile for lookup based upon underlying with name {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03134: Error when updating node with id {0}

Cause: Error when updating node with id {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03135: Error during lookup diff: {0} --- {1}

Cause: Error during lookup diff: {0} --- {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03136: Error trying to retrieve staged data underlying {0} for lookup {1}

Cause: Error trying to retrieve staged data underlying {0} for lookup {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03137: Error initialising staged data resource handle: {0}

Cause: Error initialising staged data resource handle: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03138: Error initialising staged data resource

Cause: Error initialising staged data resource

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03139: Error trying to retrieve user data underlying {0} for lookup {1}

Cause: Error trying to retrieve user data underlying {0} for lookup {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03140: Error initialising user data resource handle: {0}

Cause: Error initialising user data resource handle: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03141: Discarded cache entry for ID {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03142: Cache clear for {0} [{1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-04300: Failed to decode image from {0}

Cause: Failed to decode image from {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04301: Failed to decode images

Cause: Failed to decode images

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04302: Failed to encode image

Cause: Failed to encode image

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04303: Error loading image {0} from database

Cause: Error loading image {0} from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04304: Error storing image in database

Cause: Error storing image in database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04305: Permission error storing image:

Cause: Permission error storing image:

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04306: Error storing image in database

Cause: Error storing image in database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04307: Permission error updating image:

Cause: Permission error updating image:

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04308: Error storing image in database

Cause: Error storing image in database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04309: Error updating image in database

Cause: Error updating image in database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04310: Error deleting image from database

Cause: Error deleting image from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04311: Permission error deleting image:

Cause: Permission error deleting image:

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04312: Error deleting image from database

Cause: Error deleting image from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04313: Error loading image xtree node from database

Cause: Error loading image xtree node from database

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04314: This error will not affect normal operation. Image data for: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07500: Realtime functional pack enabled

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07501: Realtime messenger type {0} not supported

Cause: Realtime messenger type {0} not supported

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07502: Realtime messenger type {0} does not support synchronous mode

Cause: Realtime messenger type {0} does not support synchronous mode

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07503: Realtime: incoming configuration must include <incoming>

Cause: Realtime: incoming configuration must include <incoming>

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07504: Realtime: outgoing configuration must include <outgoing>

Cause: Realtime: outgoing configuration must include <outgoing>

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07505: Realtime: could not convert {0} to a duration: {1}

Cause: Realtime: could not convert {0} to a duration: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07506: Realtime: error creating payload demolisher for {0} messages: {1}

Cause: Realtime: error creating payload demolisher for {0} messages: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07507: Realtime: {0} record read failed: {1}

Cause: Realtime: {0} record read failed: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07508: Realtime: error closing {0} receiver: {1}

Cause: Realtime: error closing {0} receiver: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07509: Realtime: error finishing {0} receiver: {1}

Cause: Realtime: error finishing {0} receiver: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07510: Realtime: error creating payload builder for {0} messages: {1}

Cause: Realtime: error creating payload builder for {0} messages: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07511: Realtime: synchronous output message must contain a single record (has {0})

Cause: Realtime: synchronous output message must contain a single record (has {0})

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07512: Realtime: error transmission failed: {0}

Cause: Realtime: error transmission failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07513: Realtime: error transmitting packet to {0}: {1}

Cause: Realtime: error transmitting packet to {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07514: Realtime: error transmitting {0} terminator: {1}

Cause: Realtime: error transmitting {0} terminator: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07515: Realtime: error closing {0} transmitter: {1}

Cause: Realtime: error closing {0} transmitter: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07516: Realtime: error on {0} messenger close: {1}

Cause: Realtime: error on {0} messenger close: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07520: Realtime: error in XPath expression "{0}": {1}

Cause: Realtime: error in XPath expression "{0}": {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07521: Realtime: error parsing XML from message: {0}

Cause: Realtime: error parsing XML from message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07522: Realtime: error evaluating record XPath {0}: {10}

Cause: Realtime: error evaluating record XPath {0}: {10}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07523: Realtime: error evaluating string XPath {0}: {1}

Cause: Realtime: error evaluating string XPath {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07524: Realtime: error evaluating array XPath {0}: {1}

Cause: Realtime: error evaluating array XPath {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07525: Realtime: bad value "{0}" for attribute {1}

Cause: Realtime: bad value "{0}" for attribute {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07526: Realtime: xmltemplate must contain exactly one child element

Cause: Realtime: xmltemplate must contain exactly one child element

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07527: Realtime: '} missing after $'{ in expansion document

Cause: Realtime: '} missing after $'{ in expansion document

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07528: Realtime: unknown $'{...'} attribute {0}

Cause: Realtime: unknown $'{...'} attribute {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07529: Realtime: error parsing XSL template: {0}

Cause: Realtime: error parsing XSL template: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07530: Realtime: bean set exception for {0} on {1}: {2}

Cause: Realtime: bean set exception for {0} on {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07531: Realtime: bean get exception for {0} on {1}: {2}

Cause: Realtime: bean get exception for {0} on {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07532: Realtime: bean create exception for {0} on {1}: {2}

Cause: Realtime: bean create exception for {0} on {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07540: Realtime: failed to get JNDI credentials: {0}

Cause: Realtime: failed to get JNDI credentials: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07541: Realtime: failed to get JMS connection credentials: {0}

Cause: Realtime: failed to get JMS connection credentials: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07542: Realtime: failed to create JNDI InitialContext: {0}

Cause: Realtime: failed to create JNDI InitialContext: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07543: Realtime: failed to lookup ConnectionFactory {0}: {1}

Cause: Realtime: failed to lookup ConnectionFactory {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07544: Realtime: failed to lookup destination {0}: {1}

Cause: Realtime: failed to lookup destination {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07545: Realtime: failed to create JMS connection: {0}

Cause: Realtime: failed to create JMS connection: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07546: Realtime: JMS autoacknowledge option "{0}" should be ''true'' or ''false''

Cause: Realtime: JMS autoacknowledge option "{0}" should be ''true'' or ''false''

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07547: Realtime: bad value "{0}" for JMS maxpendingmessages

Cause: Realtime: bad value "{0}" for JMS maxpendingmessages

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07548: Realtime: bad value "{0}" for JMS maxpendingtime

Cause: Realtime: bad value "{0}" for JMS maxpendingtime

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07549: Realtime: error closing JMS connection: {0}

Cause: Realtime: error closing JMS connection: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07550: Realtime: failed to create JMS session: {0}

Cause: Realtime: failed to create JMS session: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07551: Realtime: failed to create JMS message producer: {0}

Cause: Realtime: failed to create JMS message producer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07552: Realtime: failed to create {0} JMS message: {1}

Cause: Realtime: failed to create {0} JMS message: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07553: Realtime: failed to send {0} JMS message: {1}

Cause: Realtime: failed to send {0} JMS message: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07554: Realtime: failed to create JMS message consumer: {0}

Cause: Realtime: failed to create JMS message consumer: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07555: Realtime: could not start JMS connection: {0}

Cause: Realtime: could not start JMS connection: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07556: Realtime: error receiving JMS message: {0}

Cause: Realtime: error receiving JMS message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-07560: Realtime: problem stopping WS listener for {0}/{1}: {2}

Cause: Realtime: problem stopping WS listener for {0}/{1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07561: Realtime: no registry available, RMI messenger will not be visible

Cause: Realtime: no registry available, RMI messenger will not be visible

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07562: Realtime: RMI messenger bound to registry with name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07563: Realtime: Failed to bind RMI messenger to registry: {0}

Cause: Realtime: Failed to bind RMI messenger to registry: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-07564: Realtime: RMI messenger unbound from registry with name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-07565: Realtime: Failed to unbind RMI messenger from registry: {0}

Cause: Realtime: Failed to unbind RMI messenger from registry: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06300: EDQP server at {0}:{1} appears to be alive

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-06301: EDQP server at {0}:{1} does not appear to be alive

Cause: EDQP server at {0}:{1} does not appear to be alive

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06302: Bad EDQP batchsize property "{0}"

Cause: Bad EDQP batchsize property "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06303: Error getting DSA information from datalens server at {0}:{1}: {2}

Cause: Error getting DSA information from datalens server at {0}:{1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06304: DSA {0} not found on server when getting output step names

Cause: DSA {0} not found on server when getting output step names

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06305: DSA {0} not found on server when getting output value names

Cause: DSA {0} not found on server when getting output value names

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06306: Output step {0} not found in DSA {1} when getting output value names

Cause: Output step {0} not found in DSA {1} when getting output value names

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-06307: Failed to get deployed DSA names from server

Cause: Failed to get deployed DSA names from server

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-06308: Failed to get output names for a DSA from server

Cause: Failed to get output names for a DSA from server

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05800: {0} is not a valid subfolder of landing area {1}

Cause: {0} is not a valid subfolder of landing area {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05801: URL is malformed: {0}

Cause: URL is malformed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05802: Download task {0} starting to download from {1} to {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05803: Download task {0} failed to fetch data from {1}

Cause: Download task {0} failed to fetch data from {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05804: Download task {0} finished in {1} seconds

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05806: A security violation occurred during download: {0}

Cause: A security violation occurred during download: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05807: An I/O occurred reading log output from external task: {0}

Cause: An I/O occurred reading log output from external task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05808: Error running external task: {0}

Cause: Error running external task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05809: Setting working directory to {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05810: Executing {0} {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05811: finished execution in {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05812: External task failed with exit status {0}

Cause: External task failed with exit status {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05813: An I/O error occurred running external task {0}

Cause: An I/O error occurred running external task {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05814: Error canonicalizing command area file '{0}': {1}

Cause: Error canonicalizing command area file '{0}': {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05815: Error canonicalizing config command area '{0}': {1}

Cause: Error canonicalizing config command area '{0}': {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05816: {0} XStore items found in import file: {1}, {2}, {3}

Cause: {0} XStore items found in import file: {1}, {2}, {3}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05817: Error during external task diff

Cause: Error during external task diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05818: An error occurred retrieving XTreeNode for dependency object: {0}

Cause: An error occurred retrieving XTreeNode for dependency object: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05819: An error occurred retrieving XTreeNode for dependency subject: {0}

Cause: An error occurred retrieving XTreeNode for dependency subject: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05820: An database error occurred deleting all external tasks for project: {0}

Cause: An database error occurred deleting all external tasks for project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05821: An error occurred deleting all external tasks for project: {0}

Cause: An error occurred deleting all external tasks for project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05822: An error occurred cancelling task: {0}

Cause: An error occurred cancelling task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05823: An error occurred run task: {0}

Cause: An error occurred run task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05824: Handle returned that we didn't know about

Cause: Handle returned that we didn't know about

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05825: An error occurred saving run process model: {0}

Cause: An error occurred saving run process model: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05826: An error occurred retrieving mission for run identifier: {0}

Cause: An error occurred retrieving mission for run identifier: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05827: An error occurred renaming missions for document: {0}

Cause: An error occurred renaming missions for document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05828: A database error occurred renaming missions for document: {0}

Cause: A database error occurred renaming missions for document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05829: An error occurred running a mission: {0}

Cause: An error occurred running a mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05830: An error occurred cleaning up mission: {0}

Cause: An error occurred cleaning up mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05831: Error purging project {0}

Cause: Error purging project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05832: Error {0} creating job for process {1}

Cause: Error {0} creating job for process {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05833: Error {0} deleting jobs for document {1}

Cause: Error {0} deleting jobs for document {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05834: Error {0} deleting jobs for project {1}

Cause: Error {0} deleting jobs for project {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05835: Error storing log for {0} (taskExecId {1}): {2}

Cause: Error storing log for {0} (taskExecId {1}): {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05836: Error loading log for exec id {0}: {1}

Cause: Error loading log for exec id {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05837: Error deleting stats for {0}:{1}: {2}

Cause: Error deleting stats for {0}:{1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05838: Error storing stats for {0}:{1}: {2}

Cause: Error storing stats for {0}:{1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05839: Error loading stats for {0}:{1}: {2}

Cause: Error loading stats for {0}:{1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05841: An error occurred running an ops mission: {0}

Cause: An error occurred running an ops mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05842: An error occurred loading override properties: {0}

Cause: An error occurred loading override properties: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05843: A database error occurred inserting task status information: {0}

Cause: A database error occurred inserting task status information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05844: An error occurred inserting task status information: {0}

Cause: An error occurred inserting task status information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05845: A database error occurred retrieving task status information: {0}

Cause: A database error occurred retrieving task status information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05846: A database error occurred retrieving run mission labels: {0}

Cause: A database error occurred retrieving run mission labels: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05847: A database error occurred finding task status information: {0}

Cause: A database error occurred finding task status information: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05848: A database error occurred loading mission by ID: {0}

Cause: A database error occurred loading mission by ID: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05849: A database error occurred loading mission: {0}

Cause: A database error occurred loading mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05850: A database error occurred loading missions for project: {0}

Cause: A database error occurred loading missions for project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05851: A database error occurred loading nodes for project: {0}

Cause: A database error occurred loading nodes for project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05852: A database error occurred updating tables while saving mission: {0}

Cause: A database error occurred updating tables while saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05853: An error occurred updating tables when saving mission: {0}

Cause: An error occurred updating tables when saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05854: A permissions error occurred updating tables when saving mission: {0}

Cause: A permissions error occurred updating tables when saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05855: A database error occurred inserting new entries when saving mission: {0}

Cause: A database error occurred inserting new entries when saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05856: An error occurred inserting new entries when saving mission: {0}

Cause: An error occurred inserting new entries when saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05857: A database error occurred saving mission: {0}

Cause: A database error occurred saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05859: A permissions error occurred saving mission: {0}

Cause: A permissions error occurred saving mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05860: A database error occurred deleting a mission: {0}

Cause: A database error occurred deleting a mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05861: An error occurred deleting dependencies when deleting a mission: {0}

Cause: An error occurred deleting dependencies when deleting a mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05862: A permissions error occurred deleting mission: {0}

Cause: A permissions error occurred deleting mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05863: An error occurred deleting external properties when deleting a mission: {0}

Cause: An error occurred deleting external properties when deleting a mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05865: An error occurred deleting dependencies when deleting missions for a document: {0}

Cause: An error occurred deleting dependencies when deleting missions for a document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05866: A permissions error occurred deleting missions for a document: {0}

Cause: A permissions error occurred deleting missions for a document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05867: An error occurred deleting external properties when deleting missions for a document: {0}

Cause: An error occurred deleting external properties when deleting missions for a document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05868: A database error occurred deleting missions for a project: {0}

Cause: A database error occurred deleting missions for a project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05869: An error occurred deleting dependencies when deleting missions for a project: {0}

Cause: An error occurred deleting dependencies when deleting missions for a project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05870: A permissions error occurred deleting missions for a document: {0}

Cause: A permissions error occurred deleting missions for a document: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05871: An error occurred deleting external properties when deleting missions for a project: {0}

Cause: An error occurred deleting external properties when deleting missions for a project: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05872: A database error occurred renaming a mission: {0}

Cause: A database error occurred renaming a mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05873: A permissions error occurred renaming a mission: {0}

Cause: A permissions error occurred renaming a mission: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05874: A database error occurred loading XTree node for dependency object: {0}

Cause: A database error occurred loading XTree node for dependency object: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05875: A database error occurred loading XTree node for dependency subject: {0}

Cause: A database error occurred loading XTree node for dependency subject: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05876: Error during purge: {0}

Cause: Error during purge: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05877: Task factory for task type : {0} is being replaced

Cause: Task factory for task type : {0} is being replaced

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05878: No queueable task factory for: {0}

Cause: No queueable task factory for: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05879: No queueable task executor defined for: {0}

Cause: No queueable task executor defined for: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05880: An error occurred running task: {0}

Cause: An error occurred running task: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05881: Error occurred with system task {0} : {1}

Cause: Error occurred with system task {0} : {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05882: Failed to load schedules!

Cause: Failed to load schedules!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05883: Error executing scheduled job : {0}

Cause: Error executing scheduled job : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05884: Permissions error executing scheduled job : {0}

Cause: Permissions error executing scheduled job : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05885: An error occurred updating schedule: {0}

Cause: An error occurred updating schedule: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05886: Error executing schedule : {0}

Cause: Error executing schedule : {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05887: Failed to delete schedule

Cause: Failed to delete schedule

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05888: Mission scheduler executing startup schedules

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05889: Runtime exception in scheduler thread

Cause: Runtime exception in scheduler thread

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05890: Error importing data for node: {0}

Cause: Error importing data for node: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05891: Failed to decode MissionStatement XML string: {0}

Cause: Failed to decode MissionStatement XML string: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05892: Failed to encode MissionBean: {0}

Cause: Failed to encode MissionBean: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02400: Error initialising asset tree for asset type: {0}

Cause: Error initialising asset tree for asset type: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02401: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02402: Asset type "{0}" ignored. {1} is wrong type

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02403: Asset type "{0}" ignored. {1} cannot be instantiated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02404: Error executing script: {0}

Cause: Error executing script: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02405: Error loading asset tree: {0}

Cause: Error loading asset tree: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02406: Error loading asset tree

Cause: Error loading asset tree

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02407: Cannot create java script engine

Cause: Cannot create java script engine

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02408: Error deleting object with zero dependency references

Cause: Error deleting object with zero dependency references

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02409: Message from diff: {0}

Cause: Message from diff: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02410: Error performing diff

Cause: Error performing diff

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02411: Diff complete in {0}ms

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02412: Malformed UUID in {0}/{1}/{2}

Cause: Malformed UUID in {0}/{1}/{2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02413: Updating xtree cache

Cause: Updating xtree cache

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02414: XTree data does not have a version 0: nodeId: {0}, nodeType: {1}, ver:{2}

Cause: XTree data does not have a version 0: nodeId: {0}, nodeType: {1}, ver:{2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02415: Error loading the source (xml) for: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02416: Data bean creation for type {0} on {1} failed: {2}

Cause: Data bean creation for type {0} on {1} failed: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02417: Failed to encode xtree node data

Cause: Failed to encode xtree node data

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02418: Failed to decode processor runtime

Cause: Failed to decode processor runtime

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02800: Schema "{0}" load failed!

Cause: Schema "{0}" load failed!

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02801: Failed to decode snapshot

Cause: Failed to decode snapshot

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02802: Failed to encode export

Cause: Failed to encode export

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02803: Error retrieving export: {0}

Cause: Error retrieving export: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02804: There was a problem deleting the exports for project {0}

Cause: There was a problem deleting the exports for project {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02805: Error formulating message: {0}

Cause: Error formulating message: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02806: Error during export diff

Cause: Error during export diff

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02807: Reopened export writer on attempt {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02808: Error ending transaction

Cause: Error ending transaction

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02809: There was an error retrieving exports for projectId {0} returning no export streaming consumers

Cause: There was an error retrieving exports for projectId {0} returning no export streaming consumers

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02810: Finished execution in {0}s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02811: Error running export task

Cause: Error running export task

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02812: Non-numeric found expected for column {0} in export {1} (table {2})

Cause: Non-numeric found expected for column {0} in export {1} (table {2})

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02813: Insert error for {0}: {1}

Cause: Insert error for {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02814: Unable to close results read: {0}

Cause: Unable to close results read: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02815: Execution thread notifying cancel thread that job is ended.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02816: Problem closing db inserter to table {0}

Cause: Problem closing db inserter to table {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02817: Problem closing db insertion creator to table {0}

Cause: Problem closing db insertion creator to table {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02818: Starting execution of export batch {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02819: Export batch {0} terminated by exception

Cause: Export batch {0} terminated by exception

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02820: Export batch {0} complete

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02821: Numeric value expected for column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Cause: Numeric value expected for column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02822: Date value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Cause: Date value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02823: Time value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Cause: Time value expected for date type column {0} in export {1} to table {2} but was {3}. Setting column value to null.

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02824: Cancelling job

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-03300: {0} Error getting given name cultures: {1}

Cause: {0} Error getting given name cultures: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03301: {0} Error getting surname cultures: {1}

Cause: {0} Error getting surname cultures: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03302: {0} Error getting name cultures: {1}

Cause: {0} Error getting name cultures: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03303: {0} Error writing summary metric

Cause: {0} Error writing summary metric

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-03304: {0} Error getting given name culture: {1}

Cause: {0} Error getting given name culture: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03305: {0} Error getting surname culture: {1}

Cause: {0} Error getting surname culture: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-03306: {0} Error getting name culture: {1}

Cause: {0} Error getting name culture: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02000: Databases: system landing area directory is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02001: Databases: error canonicalizing landing area path "{0}": {1}

Cause: Databases: error canonicalizing landing area path "{0}": {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02002: Databases: error canonicalizing landing area file "{0}": {1}

Cause: Databases: error canonicalizing landing area file "{0}": {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02003: Databases: problem opening local definition file {0}: {1}

Cause: Databases: problem opening local definition file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02004: Databases: problem reading database XML file {0}: {1}

Cause: Databases: problem reading database XML file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02005: Databases: {0}: database type {1}: must include url or drivers element

Cause: Databases: {0}: database type {1}: must include url or drivers element

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02006: Databases: {0}: database type {1}: cannot use driver/url and drivers element

Cause: Databases: {0}: database type {1}: cannot use driver/url and drivers element

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02007: Databases: {0}: database type {1}: driver {2} rejected because {3} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02008: Databases: {0}: database type {1}: driver {2} rejected because no files matched pattern {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02009: Databases: {0}: database type {1} has no valid drivers

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-02010: Databases: {0}: database type {1}: fields ignored if configuration class is used

Cause: Databases: {0}: database type {1}: fields ignored if configuration class is used

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02011: Databases: {0}: unknown choice default "{1}" in field {2}

Cause: Databases: {0}: unknown choice default "{1}" in field {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02012: Databases: {0}: bad numeric default {1} for field {2}

Cause: Databases: {0}: bad numeric default {1} for field {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02013: Databases: error reading option properties file {0}: {1}

Cause: Databases: error reading option properties file {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02014: Databases: error loading option properties file {0}: {1}

Cause: Databases: error loading option properties file {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02015: Databases: {0}: invalid regex "{1}" in {2}: {3}

Cause: Databases: {0}: invalid regex "{1}" in {2}: {3}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02016: Databases: {0}: invalid expression "{1}" in {2}: {3}

Cause: Databases: {0}: invalid expression "{1}" in {2}: {3}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02017: Databases: {0}: bad ''invalid'' character set "{1}" for {2}: {3}

Cause: Databases: {0}: bad ''invalid'' character set "{1}" for {2}: {3}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02018: Databases: species {0} not found: mapping to zombie

Cause: Databases: species {0} not found: mapping to zombie

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02019: Databases: {0} not found in database jar {1} - skipping file

Cause: Databases: {0} not found in database jar {1} - skipping file

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02020: Databases: error scanning species jar {0}: {1}

Cause: Databases: error scanning species jar {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02021: Databases: bad OS match regex {0}: {1}

Cause: Databases: bad OS match regex {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02022: Databases: {0}: cannot load driver class {1}

Cause: Databases: {0}: cannot load driver class {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02023: Databases: Error creating instance of driver class {0}: {1}

Cause: Databases: Error creating instance of driver class {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02024: Databases: failed to get columns for "{0}": {1}

Cause: Databases: failed to get columns for "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02025: Databases: could not retrieve primary key information for {0} table {1}: {2}

Cause: Databases: could not retrieve primary key information for {0} table {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02026: Databases: unknown column {0} in index {1}

Cause: Databases: unknown column {0} in index {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02027: Databases: could not retrieve index information for {0} table {1}: {2}

Cause: Databases: could not retrieve index information for {0} table {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02028: Databases: error getting local db file {0}: {1}

Cause: Databases: error getting local db file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02029: Databases: local db file {0} no longer exists

Cause: Databases: local db file {0} no longer exists

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02030: Databases: error in expression "{0}": {1}

Cause: Databases: error in expression "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02031: Databases client: failed to get initial database type list: {0}

Cause: Databases client: failed to get initial database type list: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02032: Databases client: species {0} not found: mapping to zombie

Cause: Databases client: species {0} not found: mapping to zombie

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02033: Databases client: recreating database of species {0} because of generation change: {1} -> {2}

Cause: Databases client: recreating database of species {0} because of generation change: {1} -> {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02034: Databases client: error recreating {0} database: {1}

Cause: Databases client: error recreating {0} database: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02035: Databases client: failed to write local jar {0}: {1}

Cause: Databases client: failed to write local jar {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-02036: Databases client: no loader for jarkey {0} in species {1}: ignoring

Cause: Databases client: no loader for jarkey {0} in species {1}: ignoring

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02037: Databases JDBC: invalid fetchsize parameter {0}

Cause: Databases JDBC: invalid fetchsize parameter {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02038: Databases JDBC: failed to set fetchsize to {0}: {1}

Cause: Databases JDBC: failed to set fetchsize to {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02039: Databases JDBC: bad batchsize setting {0}

Cause: Databases JDBC: bad batchsize setting {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02040: Databases XML: {0}: cannot find xsllist resource {1}

Cause: Databases XML: {0}: cannot find xsllist resource {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02041: Databases XML: {0}: incorrect number of fields in xsllist line "{1}"

Cause: Databases XML: {0}: incorrect number of fields in xsllist line "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02042: Databases XML: {0}: XML template resource {1} not found

Cause: Databases XML: {0}: XML template resource {1} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02043: Databases XML: {0}: XML template is required with JS decoder {1}

Cause: Databases XML: {0}: XML template is required with JS decoder {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02044: Databases XML: {0}: element path is required with JS decoder {1}

Cause: Databases XML: {0}: element path is required with JS decoder {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02045: Databases XML: {0}: XSL resource {1} not found

Cause: Databases XML: {0}: XSL resource {1} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-02046: Databases XML: {0}: error reading xsllist: {1}

Cause: Databases XML: {0}: error reading xsllist: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-04700: loadLicence error: {0}

Cause: loadLicence error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-04701: Error reading licence file {0}: {1}

Cause: Error reading licence file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01800: Error in database operation: {0}

Cause: Error in database operation: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01801: Error executing SQL {1} on database: {0}

Cause: Error executing SQL {1} on database: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01802: Next exception: {0}

Cause: Next exception: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-01803: {0}.class not in {1}

Cause: {0}.class not in {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05200: Error storing local remote object {0}: {1}

Cause: Error storing local remote object {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05201: Problem managing {0} object

Cause: Problem managing {0} object

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05202: Bean at {0} already registered

Cause: Bean at {0} already registered

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05203: Error registering {0} bean

Cause: Error registering {0} bean

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05204: Invalid ObjectName {0}: {1}

Cause: Invalid ObjectName {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05205: ObjectName {0} not found in server when unregistering

Cause: ObjectName {0} not found in server when unregistering

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05206: Error unregistering bean: {0}

Cause: Error unregistering bean: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05207: MBeanServer at JNDI name {0} not found: {1}

Cause: MBeanServer at JNDI name {0} not found: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05208: Problem registering a platform bean: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-05209: Bad value "{0}" for ssl clientauth property

Cause: Bad value "{0}" for ssl clientauth property

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05210: Error creating key manager for JMX SSL: {0}

Cause: Error creating key manager for JMX SSL: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05211: Error creating SSL server socket factory: {0}

Cause: Error creating SSL server socket factory: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05212: Error creating registry for JMX SSL: {0}

Cause: Error creating registry for JMX SSL: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05213: Problem exporting management remote objects: {0}

Cause: Problem exporting management remote objects: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05214: Problem creating the RMI registry on port {0}: {1}

Cause: Problem creating the RMI registry on port {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05216: Problem reading {0} managed beans XML file: {1}

Cause: Problem reading {0} managed beans XML file: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05217: Cannot load bean class {0}

Cause: Cannot load bean class {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05218: Notifier class {0} is not a public interface

Cause: Notifier class {0} is not a public interface

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05219: Cannot load notifier class {0}

Cause: Cannot load notifier class {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05220: <notification> element in {0} ignored because no notifier interface

Cause: <notification> element in {0} ignored because no notifier interface

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05221: Problem creating the JMXConnectorServer URL {0}: {1}

Cause: Problem creating the JMXConnectorServer URL {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05222: Problem creating JMXConnectorServer with URL {0}: {1}

Cause: Problem creating JMXConnectorServer with URL {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05223: Problem starting the JMXConnectorServer with URL {0}: {1}

Cause: Problem starting the JMXConnectorServer with URL {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05224: Bean class {0}: attribute {1} is not known

Cause: Bean class {0}: attribute {1} is not known

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05225: Bean class {0}: read-only attribute {1} does not have a getter

Cause: Bean class {0}: read-only attribute {1} does not have a getter

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05226: Bean class {0}: write-only attribute {1} does not have a setter

Cause: Bean class {0}: write-only attribute {1} does not have a setter

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05227: Bean class {0}: read-write attribute {1} does not have getter and setter

Cause: Bean class {0}: read-write attribute {1} does not have getter and setter

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05228: Bean class {0}: unknown operation {1}

Cause: Bean class {0}: unknown operation {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05230: Bean class {0}: unknown notification method {1}

Cause: Bean class {0}: unknown notification method {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05250: System management: name script file {0} not found

Cause: System management: name script file {0} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05251: System management: error loading script from file {0}: {1}

Cause: System management: error loading script from file {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05252: System management: name maker class {0} not found

Cause: System management: name maker class {0} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05253: System management: name maker class {0} does not implement {1}

Cause: System management: name maker class {0} does not implement {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05254: System management: name maker class {0} does not have zero arg constructor

Cause: System management: name maker class {0} does not have zero arg constructor

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05255: System management: error creating name maker class {0}: {0}

Cause: System management: error creating name maker class {0}: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05256: System management: failed to create namer script engine: {0}

Cause: System management: failed to create namer script engine: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05257: System management: failed to set namer script root object: {0}

Cause: System management: failed to set namer script root object: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05258: System management: failed to open namer script: {0}

Cause: System management: failed to open namer script: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05259: System management: failed to open namer script: missing class {0}

Cause: System management: failed to open namer script: missing class {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05260: System manaegment: ''{0}'' function missing in namer script

Cause: System manaegment: ''{0}'' function missing in namer script

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05261: System management: ''{0}'' namer script call failed: {1}

Cause: System management: ''{0}'' namer script call failed: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05900: Call made to transport before login/after logout: {0}

Cause: Call made to transport before login/after logout: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05901: Unknown throwable class returned: {0}

Cause: Unknown throwable class returned: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05902: Problem instantiating output when calling {0}

Cause: Problem instantiating output when calling {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05903: Transport exception

Cause: Transport exception

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05904: Serializing 'Output' object

Cause: Serializing 'Output' object

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05905: Transport: Error invoking method on server

Cause: Transport: Error invoking method on server

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-09500: Realm {0}: realm name not set

Cause: Realm {0}: realm name not set

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09501: Realm {0}: creation error: {1}

Cause: Realm {0}: creation error: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09502: Realm {0}: ldap.profile or auth not set

Cause: Realm {0}: ldap.profile or auth not set

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09503: Realm {0}: invalid LDAP profile: {0}

Cause: Realm {0}: invalid LDAP profile: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09504: Realm {0}: LDAP profile "{1}" not found

Cause: Realm {0}: LDAP profile "{1}" not found

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09505: Realm {0}: error crearing GSS configuration: {1}

Cause: Realm {0}: error crearing GSS configuration: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09506: Realm {0}: error in matching regex: {1}

Cause: Realm {0}: error in matching regex: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09507: Realm {0}: error querying DNS for LDAP servers in domain {1}: {2}

Cause: Realm {0}: error querying DNS for LDAP servers in domain {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09508: Realm {0}: no LDAP servers defined

Cause: Realm {0}: no LDAP servers defined

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09509: Realm {0}: unknown Sasl qop setting {1}

Cause: Realm {0}: unknown Sasl qop setting {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09510: Realm {0}: unknown security option {1}

Cause: Realm {0}: unknown security option {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09511: Realm {0}: invalid credential lifetime {1}

Cause: Realm {0}: invalid credential lifetime {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09512: Realm {0}: error getting canonical SPN: {1}

Cause: Realm {0}: error getting canonical SPN: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09513: Realm {0}: error getting credentials for LDAP server: {1}

Cause: Realm {0}: error getting credentials for LDAP server: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09514: Realm {0}: LDAP user or password not specified

Cause: Realm {0}: LDAP user or password not specified

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09515: Realm {0}: unknown LDAP server authentication method: {1}

Cause: Realm {0}: unknown LDAP server authentication method: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09516: Realm {0}: error creating LDAP server: {1}

Cause: Realm {0}: error creating LDAP server: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09517: Realm {0}: invalid basedn "{1}": {2}

Cause: Realm {0}: invalid basedn "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09518: Realm {0}: basedn not specified;

Cause: Realm {0}: basedn not specified;

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09519: Realm {0}: error creating {1} authenticator: {2}

Cause: Realm {0}: error creating {1} authenticator: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09520: Realm factory class {1} not found

Cause: Realm factory class {1} not found

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09521: Realm factory class {1} does not implement RealmFactory

Cause: Realm factory class {1} does not implement RealmFactory

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09522: Error creating RealmFactory {0}: {1}

Cause: Error creating RealmFactory {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09523: Error attempting client Kerberos login: {0}

Cause: Error attempting client Kerberos login: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09524: Error performing server Kerberos login with SPN {0}: {1}

Cause: Error performing server Kerberos login with SPN {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09525: Error getting KRB5 server credentials: {0}

Cause: Error getting KRB5 server credentials: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09526: Error getting SPNEGO server credentials: {0}

Cause: Error getting SPNEGO server credentials: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09530: Failed to load login configuration: {0}

Cause: Failed to load login configuration: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09531: Error running filter for {0}: {1}

Cause: Error running filter for {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09532: Error creating GSS accept context: {0}

Cause: Error creating GSS accept context: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09533: Error accepting GSS token: {0}

Cause: Error accepting GSS token: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09534: Error querying GSS client identity: {0}

Cause: Error querying GSS client identity: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09535: Sessions: error looking up user {0}: {1}

Cause: Sessions: error looking up user {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09536: Sessions: error getting history for last {0} days: {1}

Cause: Sessions: error getting history for last {0} days: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09537: Sessions: error getting history: {0}

Cause: Sessions: error getting history: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09538: User cache persistence initialization failed: {0}

Cause: User cache persistence initialization failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09539: Realm {0}: error retrieving user list: {1}

Cause: Realm {0}: error retrieving user list: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09540: Realm {0}: error retrieving users in group with key {1}: {2}

Cause: Realm {0}: error retrieving users in group with key {1}: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09541: Password checker: script call failed: {0}

Cause: Password checker: script call failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09542: User Management: filter call failed: {0}

Cause: User Management: filter call failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09543: User Management: failed to create filter instance: {0}

Cause: User Management: failed to create filter instance: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09544: LDAP password compare failed: {0}

Cause: LDAP password compare failed: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-09545: Invalid DN "{0}" in member list for "{1}": {2}

Cause: Invalid DN "{0}" in member list for "{1}": {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-10400: All realms rejected - falling back to internal realm

Cause: All realms rejected - falling back to internal realm

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10401: Bad certificate checker for internal realm: {0}

Cause: Bad certificate checker for internal realm: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10402: Realm {0}: no LDAP servers found in DNS lookup in domain {1}

Cause: Realm {0}: no LDAP servers found in DNS lookup in domain {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10403: Login configuration: bad boolean value "{0}"

Cause: Login configuration: bad boolean value "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10404: Bad sessionlimit value: "{0}"

Cause: Bad sessionlimit value: "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10410: User {0} rejected by filter

Cause: User {0} rejected by filter

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10411: GSS handshake complete: client identity is {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10412: No delegated credentials available for {0}

Cause: No delegated credentials available for {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10413: Failed to get delegated credentials for {0}: {1}

Cause: Failed to get delegated credentials for {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10414: GSS successful, but no realm matching {0}

Cause: GSS successful, but no realm matching {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10415: Identity {0} not found in realm {1}

Cause: Identity {0} not found in realm {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10416: Negotiate: createContext failed: {0}

Cause: Negotiate: createContext failed: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10417: Negotiate: realm not found for identity {0}

Cause: Negotiate: realm not found for identity {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10418: Negotiate: user {0} not found in realm {1}

Cause: Negotiate: user {0} not found in realm {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10419: Negotiate: delegation reported but no credentials returned

Cause: Negotiate: delegation reported but no credentials returned

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10420: Negotiate: delegation reported but credentials failed: {0}

Cause: Negotiate: delegation reported but credentials failed: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10421: Negotiate: error getting user info: {0}

Cause: Negotiate: error getting user info: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10422: Negotiate: context not established after single accept

Cause: Negotiate: context not established after single accept

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10423: Negotiate: accept failed: {0}

Cause: Negotiate: accept failed: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10424: No realm matching identity {0}

Cause: No realm matching identity {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10425: Invalid number "{0}" in session retention

Cause: Invalid number "{0}" in session retention

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10426: Unknown unit in retention setting "{0}"

Cause: Unknown unit in retention setting "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10427: Bad permissions expression "{0}": {1}

Cause: Bad permissions expression "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10428: Session for user {0} rejected by {1} limit

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10429: Account for {0} blocked due to repeated login failures

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-10430: LDAP user search failed: {0}

Cause: LDAP user search failed: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10431: Realm {0}: bad maxPwdAge attribute "{1}"

Cause: Realm {0}: bad maxPwdAge attribute "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10432: Realm {0}: error getting maxPwdAge: {1}

Cause: Realm {0}: error getting maxPwdAge: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10433: Realm {0}: unparseable userAccountControl value "{1}"

Cause: Realm {0}: unparseable userAccountControl value "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10434: Realm {0}: unparseable pwdLastSet value "{1}"

Cause: Realm {0}: unparseable pwdLastSet value "{1}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10435: Realm {0}: error getting pwdLastSet for {1}: {2}

Cause: Realm {0}: error getting pwdLastSet for {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10436: Invalid ADS password policy pattern "{0}": {1}

Cause: Invalid ADS password policy pattern "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10437: Bad duration value "{0}" for property {1}

Cause: Bad duration value "{0}" for property {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10438: Realm {0}: user identity {1} not valid

Cause: Realm {0}: user identity {1} not valid

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10439: Realm {0}: user key {1} not valid

Cause: Realm {0}: user key {1} not valid

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10440: Realm {0}: group key {1} not valid

Cause: Realm {0}: group key {1} not valid

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10441: Realm {0}: default user group {1} not found

Cause: Realm {0}: default user group {1} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10442: Realm {0}: no user search filter

Cause: Realm {0}: no user search filter

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-10443: Realm {0}: group {1} not found

Cause: Realm {0}: group {1} not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05600: Application helper: bad file pattern {0}: {1}

Cause: Application helper: bad file pattern {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05601: ServerConnector: error looking up management bean "{0}": {1}

Cause: ServerConnector: error looking up management bean "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05602: ServerConnector: error invoking name mapper on management bean: {0}

Cause: ServerConnector: error invoking name mapper on management bean: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05603: Operation queue: [{0}]: operation {1} failed: {2}

Cause: Operation queue: [{0}]: operation {1} failed: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05604: SQL operation {0} failed: {1}

Cause: SQL operation {0} failed: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05605: Property set: error calling {0} on a {1}: {2}

Cause: Property set: error calling {0} on a {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05606: Bad boolean property "{0}" for {1}

Cause: Bad boolean property "{0}" for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05607: Bad boolean value "{0}"

Cause: Bad boolean value "{0}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05608: Bad integer property "{0}" for {1}

Cause: Bad integer property "{0}" for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05609: Bad numeric property "{0}" for {1}

Cause: Bad numeric property "{0}" for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05610: Bad date property "{0}" for {1}

Cause: Bad date property "{0}" for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05611: Key provider error: {0}

Cause: Key provider error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05612: Cannot allocate cipher using algorithm {0}

Cause: Cannot allocate cipher using algorithm {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05613: Key loading error: {0}

Cause: Key loading error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05614: Error generating security key using algorithm {0}: {1}

Cause: Error generating security key using algorithm {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05615: Key store error: {0}

Cause: Key store error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05616: {0} encryption failed: {1}

Cause: {0} encryption failed: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05618: SSLTrustManagement: error opening certificate URL {0}: {1}

Cause: SSLTrustManagement: error opening certificate URL {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05619: SSLTrustManagement: error loading certificate in {0}: {1}

Cause: SSLTrustManagement: error loading certificate in {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05620: Native library manager: error opening {0} as jar: {1}

Cause: Native library manager: error opening {0} as jar: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05621: Native library manager: error getting CRC of {0}: {1}

Cause: Native library manager: error getting CRC of {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05622: Native library manager: error copying jar entry {0} to {1}: {2}

Cause: Native library manager: error copying jar entry {0} to {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05623: Property evaluation: Error in expression "{0}": {0}

Cause: Property evaluation: Error in expression "{0}": {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05624: Transactions: commit failed on non-critical activity {0}: {1}

Cause: Transactions: commit failed on non-critical activity {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05625: Transactions: rollback failed on non-critical activity {0}: {1}

Cause: Transactions: rollback failed on non-critical activity {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05626: XML: cannot find schema file "{0}"

Cause: XML: cannot find schema file "{0}"

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05627: XML: error on line {0} when parsing schema: {1}

Cause: XML: error on line {0} when parsing schema: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05628: XML: error parsing schema: {0}

Cause: XML: error parsing schema: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05629: XML: IO error during XML parsing: {0}

Cause: XML: IO error during XML parsing: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05630: XML: failed to parse XML: {0}

Cause: XML: failed to parse XML: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05631: XML: error during document validation: {0}

Cause: XML: error during document validation: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05632: XML: error during parsing: {0}

Cause: XML: error during parsing: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05633: XML: error at {0} during parsing: {1}

Cause: XML: error at {0} during parsing: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05634: XML: fatal error during parsing: {0}

Cause: XML: fatal error during parsing: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05635: XML: fatal error at {0} during parsing: {1}

Cause: XML: fatal error at {0} during parsing: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05636: XML: warning during parsing: {0}

Cause: XML: warning during parsing: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05637: XML: warning at {0} during parsing: {1}

Cause: XML: warning at {0} during parsing: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05638: Stax: unthrowable exception in StAXTrAXFilterFactory.Reader.haxNext

Cause: Stax: unthrowable exception in StAXTrAXFilterFactory.Reader.haxNext

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05660: Credentials provider error: {0}

Cause: Credentials provider error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05661: Error loading credentials for prefix "{0}": {1}

Cause: Error loading credentials for prefix "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05670: Keystore provider error: {0}

Cause: Keystore provider error: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-05680: WLS support: error lookup in runtime MBean server: {0}

Cause: WLS support: error lookup in runtime MBean server: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05681: WLS support: object "{0}" at {1} is not an MBeanServer

Cause: WLS support: object "{0}" at {1} is not an MBeanServer

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05682: WLS support: error querying MBeans at {0}: {1}

Cause: WLS support: error querying MBeans at {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05683: WLS support: got {0} MBeans for {1}

Cause: WLS support: got {0} MBeans for {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05684: WLS support: error querying initial value of "{0}" on "{1}": {2}

Cause: WLS support: error querying initial value of "{0}" on "{1}": {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-05685: WLS support: error adding listener to "{0}": {1}

Cause: WLS support: error adding listener to "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00600: Blueprints: problem reading blueprints schema file: {0}

Cause: Blueprints: problem reading blueprints schema file: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00601: Blueprints: problem opening local blueprint definition file {0}: {1}

Cause: Blueprints: problem opening local blueprint definition file {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00602: Blueprints: file {0} : problem parsing XML definition: {1}

Cause: Blueprints: file {0} : problem parsing XML definition: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00603: Blueprints: file {0} : root element must be {1}

Cause: Blueprints: file {0} : root element must be {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00604: Blueprints: file {0} : unknown from item "{1}" in wire

Cause: Blueprints: file {0} : unknown from item "{1}" in wire

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00605: Blueprints: file {0} : unknown to item "{1}" in wire

Cause: Blueprints: file {0} : unknown to item "{1}" in wire

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00606: Blueprints: file {0} : filter element should contain type and/or payload attributes

Cause: Blueprints: file {0} : filter element should contain type and/or payload attributes

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00607: Blueprints: file {0} : invalid isolation in wire from "{1}" to "{2}"

Cause: Blueprints: file {0} : invalid isolation in wire from "{1}" to "{2}"

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00608: Blueprints: file {0} : unexpected item type {1}

Cause: Blueprints: file {0} : unexpected item type {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00609: Blueprints: file {0} : constraints should be omitted for root or splitpane item

Cause: Blueprints: file {0} : constraints should be omitted for root or splitpane item

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00610: Blueprints: file {0} : constraints element for gridbag layout must be gbc, not {1}

Cause: Blueprints: file {0} : constraints element for gridbag layout must be gbc, not {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00611: Blueprints: file {0} : constraints element for border layout must be brc, not {1}

Cause: Blueprints: file {0} : constraints element for border layout must be brc, not {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00612: Blueprints: file {0} : constraints element for split pane must be spc, not {1}

Cause: Blueprints: file {0} : constraints element for split pane must be spc, not {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00613: Blueprints: file {0} : constraints element for internal layout must be plain, not {1}

Cause: Blueprints: file {0} : constraints element for internal layout must be plain, not {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00614: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Cause: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00615: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Cause: Blueprints: file {0} : unexpected error getting value of gbc value {1}: {2}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00616: Blueprints: file {0} : failed to open link script: {1}

Cause: Blueprints: file {0} : failed to open link script: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00617: Blueprints: file {0} : link script: missing class {1}

Cause: Blueprints: file {0} : link script: missing class {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00618: Blueprints: file {0} : failed to create {1} link script engine: {2}

Cause: Blueprints: file {0} : failed to create {1} link script engine: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00619: Blueprints: file {0} : error setting importing link script root: {1}

Cause: Blueprints: file {0} : error setting importing link script root: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00620: Blueprints: file {0} : ''getLink'' function missing in link script

Cause: Blueprints: file {0} : ''getLink'' function missing in link script

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00621: Blueprints: file {0} : {1} not found - skipping file

Cause: Blueprints: file {0} : {1} not found - skipping file

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00622: Blueprints: file {0} : error scanning jar: {1}

Cause: Blueprints: file {0} : error scanning jar: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00623: Blueprints: reloaded blueprints from {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact:

EDQ-00624: Blueprints: Failed to get blueprints list: {0}

Cause: Blueprints: Failed to get blueprints list: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00625: Blueprints: Failed to get blueprint {0}: {1}

Cause: Blueprints: Failed to get blueprint {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00626: Blueprints: bph: failed to write local jar {0}: {1}

Cause: Blueprints: bph: failed to write local jar {0}: {1}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00627: Blueprints: bph: no loader for jarkey {0} in blueprint {1}: ignoring

Cause: Blueprints: bph: no loader for jarkey {0} in blueprint {1}: ignoring

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00628: Blueprints: error in wire filter type pattern "{0}": {1}

Cause: Blueprints: error in wire filter type pattern "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00629: Blueprints: payload class {0} in wire filter not found

Cause: Blueprints: payload class {0} in wire filter not found

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00630: Blueprints: null source in update command state

Cause: Blueprints: null source in update command state

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00631: Blueprints: unknown update command state payload from {0}: {1}

Cause: Blueprints: unknown update command state payload from {0}: {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00632: Blueprints: command {0} when not active

Cause: Blueprints: command {0} when not active

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00633: Blueprints: svg transcoder exception: {0}

Cause: Blueprints: svg transcoder exception: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00634: Blueprints: svg was {0}

Cause: Blueprints: svg was {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00635: Blueprints: No handler class declared for type {0}

Cause: Blueprints: No handler class declared for type {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00636: Blueprints: Handler class {0} not found for type {1}

Cause: Blueprints: Handler class {0} not found for type {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00637: Blueprints: Missing class ({0}) when loading handler for type {1}

Cause: Blueprints: Missing class ({0}) when loading handler for type {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00638: Blueprints: Handler class {0} does not implement {1}

Cause: Blueprints: Handler class {0} does not implement {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00639: Blueprints: Access error creating handler of class {1}

Cause: Blueprints: Access error creating handler of class {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00640: Blueprints: Error creating handler of class {1}

Cause: Blueprints: Error creating handler of class {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00641: Blueprints: error calling {0}({1} function: {2}

Cause: Blueprints: error calling {0}({1} function: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00642: Blueprints: error calling {0}({1} function: {2}

Cause: Blueprints: error calling {0}({1} function: {2}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00643: Blueprints: SVG: no source object named {1}

Cause: Blueprints: SVG: no source object named {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00644: Blueprints: SVG: source object {0} is not a text generator

Cause: Blueprints: SVG: source object {0} is not a text generator

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00645: Blueprints: SVG: failed to create SVG document: {0}

Cause: Blueprints: SVG: failed to create SVG document: {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00646: Blueprints: No tab with name {0}

Cause: Blueprints: No tab with name {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00647: Blueprints: No tab template with name {0}

Cause: Blueprints: No tab template with name {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00648: Blueprints: Tab with name {0} already exists

Cause: Blueprints: Tab with name {0} already exists

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00649: Blueprints: Failed to create new tab contents: {0}

Cause: Blueprints: Failed to create new tab contents: {0}

Action: Contact Support.
Level: 1

Type: ERROR

Impact: Other

EDQ-00650: Blueprints: No dynamic tab with name {0}

Cause: Blueprints: No dynamic tab with name {0}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

EDQ-00651: Blueprints: bad webroot url "{0}": {1}

Cause: Blueprints: bad webroot url "{0}": {1}

Action: Contact Support.
Level: 1

Type: WARNING

Impact: Other

20 EM-02801 to EM-02804

EM-02801: Problem getting general metric information while rendering home page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

EM-02802: Problem getting graph metric information while rendering home page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

EM-02803: Problem getting metric information while rendering configure page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

EM-02804: Problem accessing mbean attributes while rendering configure page for target {0}.

Cause: Admin server down, unreachable, or credential problems.

Action: Ensure the admin server is up, reachable, and that the login credentials are correct.
Level: 1

Type: WARNING

Impact: Requests/Responses

21 EPMBPMUI-00101 to EPMBPMUI-01804

EPMBPMUI-00101: Initializing configuration factory

Cause: The application is initializing its configuration factory at application startup.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00102: Terminating configuration factory

Cause: The application is shutting down its configuration factory at application shutdown.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00201: Parameter "{0}" has value "{1}"

Cause: Reports the value of a configuration factory parameter during startup.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00204: Failed to initialize the class {0} with its default constructor.

Cause: The configuration factory could not create a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00205: Failed to instantiate the class {0}

Cause: The configuration factory could not create a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00206: Failed to initialize the configuration class.

Cause: The configuration factory could create, but could not initialize, a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00207: Failed to resolve the class {0}

Cause: The configuration factory could not find a named class definition to create.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00208: Failed to initialize the configuration class.

Cause: The configuration factory could create, but could not initialize, a configuration class.

Action: Consult the application configuration log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00209: Configuration class application parameter "{0}" was not specified in web.xml

Cause: A required parameter for the configuration factory was not specified in the application configuration.

Action: Verify that the named parameter is present in the file web.xml, and that any customizations of this file did not remove it.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00210: The configuration Factory's configuration instance was null. There was an initialization error during application startup.

Cause: Due to previous errors, the configuration factory was not able to create a configuration instance.

Action: Consult the application configuration logs for previous errors.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00211: There was an error during configuration instance termination.

Cause: The configuration factory was unable to terminate a configuration instance.

Action: This error is not immediately fatal, but may result in a memory leak over time if repeated.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00212: The Configuration instance was not initialized. Ensure the context parameter "{0}" is set correctly, and check for errors during application startup.

Cause: The configuration factory could not initialize its configuration instance due to a missing parameter in web.xml.

Action: Verify that the named parameter is present in the file web.xml, and that any customizations of this file did not remove it.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00402: There was an error getting the context configuration parameter: {0}.

Cause: The application was unable to load the path to its context configuration from the configuration parameter BpmContextConfig.

Action: Verify that application configuration completed successfully, and that any customizations to this application did not remove this parameter.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00403: There was an error getting the common install version number.

Cause: The application was unable to determine the version number of the common installer.

Action: Verify that the file EPM_ORACLE_HOME/common/config/11.1.2.0/installer_version.xml exists, is accessible, and is a valid XML file.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00501: Failed to load and parse {0}

Cause: The configuration class failed to load the named file.

Action: Consult the application configuration log for further errors.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00502: Failed to initialize the authentication helper

Cause: The configuration class could not initialize the security system due to previous errors.

Action: Consult the application security log for previous errors.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00503: The property "{0}" has value "{1}"

Cause: Reports the named property and value.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00601: Loaded properties from {0}

Cause: Reports that the configuration class loaded its application properties from the named EPM Registry component.

Action: No action is requred.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00602: Failed to load properties from {0}

Cause: The configuration class could not load its configuration properties from the named EPM Registry component.

Action: Verify connection to the EPM Registry and EPM Registry contents.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00603: Loaded properties from {0}[{1}={2}]

Cause: Reports that the configuration class loaded its application properties from the named EPM Registry component.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00701: There was an error during authentication.

Cause: Reports a generic error during authentication. This message is a generic message for the user interface which obscured the actual security system error.

Action: Consult the application security log for the full error details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00702: Intercepting request for authentication: {0}

Cause: The security system is intercepting the named request for an authentication check.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00703: Intercepting with static logon page: {0}

Cause: The security system is using the named logon page to prompt for user credentials.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00801: Redirecting request for authentication: {0}

Cause: The security system is redirecting the named request to the main application logon page.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00901: Logon bean class name was not specified in web.xml.

Cause: The name of a security class implementation was not found in the application configuration.

Action: This is not a fatal error; a default implementation will be used.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00902: Using the default logon bean implementation.

Cause: The security system will use a default security class implementation.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00903: There was an error instantiating the logon bean.

Cause: The security system was unable to instantiate the security class implementation.

Action: Consult the application security log for previous errors from the security API
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00904: The Logon bean class does not have a default public constructor.

Cause: The security class implementation does not have a required constructor.

Action: Verify that the application deployment is not damaged and that all service fixes were applied properly.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00905: Logon bean Java class is not resolvable.

Cause: The security system could not resolve the class name of the security class implementation.

Action: Verify that any customizations to web.xml did not remove or damage this parameter.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00906: Failed to initialize the logon bean.

Cause: The security system could not initialize the security class implementation.

Action: Consult the application security log for prior errors from the security API.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-00907: There was an error during logon bean initialization.

Cause: The security system could not initialize the security class implementation.

Action: Consult the application security log for prior errors from the security API.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01001: Blocking request: {0}

Cause: The named request has been blocked by the security system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01201: The CSS mode is: {0}

Cause: Reports the deployment mode of the security system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01202: Failed to determine CSS mode. Will use EPM mode.

Cause: Indicates that the security system could not determine its deployment mode and is using the default mode.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01203: Initializing security framework

Cause: Indicates that the security class is initializing the security API/

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01204: Security framework was initialized successfully.

Cause: Indicates that the security class initialized the security API without error.

Action: No action was required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01205: There was an error initializing security framework.

Cause: Indicates that the security class failed to initialize the security API.

Action: Consult the application security logs for prior error messages.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01207: This session will be invalidated.

Cause: Indicates that an already-extant session is being invalidated during logon to be replaced with a new session.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01208: Logging on user {0} at {1}

Cause: Records a successful user logon for the named user at the given time.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01210: There was an error determining if direct logon is permitted. Direct logons will be denied.

Cause: The security system was unable to determine if direct logons are permitted even if an SSO agent is enabled. Such logons will be disallowed.

Action: Verify that the application was deployed correctly and that any customization to its configuration did not remove any parameters.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01211: User's password is about to expire.

Cause: Informative message at logon indicating the the current user's password will soon expire.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01212: Failed to store user in session

Cause: The security system failed to create a session for an authenticated user.

Action: Consult the application security log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01213: Failed to retrieve user from session

Cause: The security system could not verify a user from an existing sesison.

Action: Consult the application security log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01214: Terminating session for user: {0}

Cause: Indicates that a user session is terminated.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01216: Session created at: {0}

Cause: Gives the creation time of a terminated user session.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01217: There was an error during Fusion logon:

Cause: Reports an error from the Fusion Middleware logon system.

Action: Consult the application security log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01301: Attempt to create a J2EE session on an unauthorized request path. The attempt was blocked. The request path was: {0}

Cause: An unauthorized request attempted to create an application session and was blocked in the attempt.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01501: read parameter name: {0} value: {1}

Cause: Indicates a preferences system configuration value read during startup.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01502: There was an error during preferences system initialization.

Cause: Reports an error during preferences initialization.

Action: Consult the application preferences log for further details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01503: Preferences servlet initialized

Cause: Indicates that the preferences servlet is initialized.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01504: There was an error saving preferences.

Cause: Indicates an error saving preferences for a given user.

Action: Consult both the application security and applicaion preferences logs for more details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01505: There was an error saving preferences for multiple users.

Cause: Indicates an error saving preferences for multiple users.

Action: Consult both the application security and applicaion preferences logs for more details.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01506: Ther was an error during preferences system shutdown.

Cause: Reports an error during preference system shutdown during application shutdown.

Action: The application has shut down, so no action is possible.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01801: There was an error checking the client debug setting: all requests blocked.

Cause: The security system was unable to determine if client debugging requests are permitted; these requests will be blocked by default.

Action: Verify that application configuration completed successfully, and that any customizations to this application did not remove this parameter.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01802: Permitting request: {0}

Cause: The security system is permitting the named client debugging request.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01803: Blocking request: {0}

Cause: The security system is blocking the named client debugging request.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMBPMUI-01804: You do not have access to see this page because client debugging is disabled. Contact your system administrator.

Cause: This message indicates that the request was blocked because client debugging is enabled. A system administrator must enable this setting for the application.

Action: Contact your system administrator.
Level: 32

Type: ERROR

Impact:

22 EPMFR-00001 to EPMFR-00356

EPMFR-00001: Duplicate arc exists in the linkbase. From: ({0}) to: ({1})

Cause: Duplicate arc nodes were provided for a linkbase.

Action: Ensure that the taxonomy does not use duplicate arc nodes.
Level: 32

Type: ERROR

Impact:

EPMFR-00002: Error while trying to get content at URL: ({0}). Trying path: ({1}) instead.

Cause: The taxonomy's relative path was used instead of the URL location.

Action: Ensure that the taxonomy's URL location is properly formed.
Level: 32

Type: WARNING

Impact:

EPMFR-00003: URL: ({0}) missing

Cause: The URL for the taxonomy was not found.

Action: Ensure that the taxonomy exists at the given location. Also ensure that the given taxonomy's URL is properly formed.
Level: 32

Type: WARNING

Impact:

EPMFR-00004: {0} <element> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized taxonomy element attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized element attributes.
Level: 32

Type: ERROR

Impact:

EPMFR-00005: {0} <schema> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized schema attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized schema attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00006: Linkbase:{0} <linkbaseRef> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized linkbase attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized linkbase attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00007: processImportAttributes:{0} <import> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized import attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized import attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00008: {0} <include> attribute: {1} will not be processed. It is not recognized by the parser.

Cause: An unrecognized include attribute was found by the taxonomy parser. It will be ignored.

Action: Ensure that the taxonomy being parsed does not use unrecognized include attributes.
Level: 32

Type: WARNING

Impact:

EPMFR-00009: Error writing binary data to file: ({0})

Cause: Write permissions to file may be denied due to user permission settings or disk space limitations.

Action: Ensure that the user has write permissions to the file and there is enough disk space.
Level: 32

Type: ERROR

Impact:

EPMFR-00010: Error reading binary data from file: ({0})

Cause: File is missing or not accessible at this time.

Action: Verify that the file exists and is available, or try later.
Level: 32

Type: ERROR

Impact:

EPMFR-00011: Cannot load bursting file: {0}. Internal unique identifier of this file is: [{1}].

Cause: The file that was accessed does not exist.

Action: Select a file that exists and rerun.
Level: 32

Type: ERROR

Impact:

EPMFR-00012: Cannot load bursting file: {0}. Internal unique identifier of this file is: [{1}].

Cause: The file that was accessed does not exist.

Action: Select a file that exists and rerun.
Level: 32

Type: ERROR

Impact:

EPMFR-00013: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.

Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 32

Type: WARNING

Impact:

EPMFR-00014: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.

Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 32

Type: WARNING

Impact:

EPMFR-00015: GIF no longer supported

Cause: An unsupported Graphic Interchange Format (GIF) file was encountered as a report image.

Action: Convert the GIF file to a Bitmap (BMP) file and reload.
Level: 32

Type: WARNING

Impact:

EPMFR-00016: Batches run successfully will be cleaned up after {0} milliseconds.

Cause: The batches were run successfully and will be cleaned up.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00017: The thread which cleans up scheduled batches will wake up every {0} milliseconds.

Cause: The thread that cleaned the scheduled batches occurs every number of milliseconds.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00019: Cannot not find binary file: {0}

Cause: The reported file could not be found and may result in missing data, text, or images.

Action: Ensure that the selected .BES file is correct and corresponds to the loaded .DES file.
Level: 32

Type: ERROR

Impact:

EPMFR-00021: Attempted to cancel job, but could not find JobId: {0}

Cause: The selected job no longer exists.

Action: Check if the job already completed or was removed by another user.
Level: 32

Type: ERROR

Impact:

EPMFR-00022: Unable to open connection to data source. Failure result: {0}.

Cause: Either a connection to the data source was not established, or the user credentials for the data source were incorrect.

Action: Verify that the connectivity to the data source and verify that the user credentials for the data source are accurate.
Level: 32

Type: ERROR

Impact:

EPMFR-00023: Cannot find job definition {0}

Cause: The selected batch job was not found.

Action: Refresh the display and verify that the requested batch exists, then try again.
Level: 32

Type: WARNING

Impact:

EPMFR-00026: Key '{0}' already exists for {1}

Cause: The given extended link was not added to the element because it already exists.

Action: Ensure that the taxonomy does not attempt to add duplicate extended links to the same element.
Level: 32

Type: WARNING

Impact:

EPMFR-00027: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00028: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00029: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00030: Unable to load error message for key: {0}

Cause: The resource for the error message was not found.

Action: An error message or translated message is missing from the resource file. Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00031: Class '{0}' must extend from the ReportAddOn class

Cause: This is custom code in which the AddOn class did not extend the ReportAddOn class.

Action: The Java class in the Reports AddOn needs to extend the ReportAddOn class.
Level: 32

Type: ERROR

Impact:

EPMFR-00032: Error executing batch: {0}

Cause: The Reports Web Server was not available, the report to be run was not located, or there were no correct user credentials supplied for the batch routine.

Action: Verify the availability of the Reports Web Server, that the report in the batch exists, and that the user credentials for the batch routine are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00033: Type {0} of a service on {1} is shutting down.

Cause: A service on the noted server was shut down and removed from the registry.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00034: Type {0} of a service on {1} is started.

Cause: A service on the noted server was started and added to the registry.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00035: Initializing Financial Reporting Analytic Data Model Service

Cause: The Financial Reporting Analytic Data Model Service was about to initialize.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00036: Failure to initialize Financial Reporting Analytic Data Model Service

Cause: There was most likely an installation or configuration error that caused the initialization error.

Action: Check the installation and configuration logs for more information.
Level: 32

Type: ERROR

Impact:

EPMFR-00037: Stopping Financial Reporting Analytic Data Model Service

Cause: The Financial Reporting Analytic Data Model Service was stopping.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00038: Failure to stop Financial Reporting Analytic Data Model service

Cause: There most likely was a memory issue on the system.

Action: Check the system hardware for memory usage issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00039: Initializing Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service was initializing.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00040: Failure to start Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service failed to initialize.

Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00041: Stopping Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service Service stopped.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00042: Failure to stop Financial Reporting Printing Service

Cause: The Financial Reporting Printing Service failed to stop.

Action: Check the logs for print jobs running. Also, check the system for memory errors or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00043: Initializing and starting Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service initialized.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00044: Failure to start Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service failed to initialize due to one of a few possible reasons.

Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00045: Stopping Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service has stopped.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00046: Failure to stop Financial Reporting Reporting Service

Cause: The Financial Reporting Reporting Service failed to stop.

Action: Check the logs for running reports, batch jobs, or any other running report process. Also, check the system for memory errors or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00047: Financial Reporting Scheduler Service initialized

Cause: The Financial Reporting Scheduler Service was initializing.

Action: No action is required
Level: 32

Type: INFORMATION

Impact:

EPMFR-00048: Failure to start Financial Reporting Scheduler Service

Cause: The Financial Reporting Scheduler Service failed to initialize.

Action: Look at the installation and configuration logs for possible errors; check the system for memory errors, disk space, or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00049: The Financial Reporting Scheduler Service stopped

Cause: The Financial Reporting Scheduler Service has stopping.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00050: Failure to stop Financial Reporting Scheduler Service

Cause: The Financial Reporting Scheduler Service failed to initialize.

Action: Check the logs for scheduled jobs that may have failed. Also, check the system for memory errors or other system-related issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00051: Returning HsServer from machine {0}

Cause: The Reports server was successfully selected from the registry.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00052: Cannot get Report Server object

Cause: Failed to get the Report Server object from the registry. There may be an access or connectivity issue.

Action: Verify that the registry, RMI, and Reports Servers are all operational and that there are no network issues. Also verify all user credentials. Contact Oracle Support Services if this issue cannot be resolved.
Level: 32

Type: ERROR

Impact:

EPMFR-00053: Unable to find Print Server

Cause: Failed to get the print server object from the registry; possible access or connectivity issue.

Action: Verify that the registry, RMI, and Reports Servers are all operational and that there are no network issues. Also verify all user credentials. Contact Oracle Support Services if this issue cannot be resolved.
Level: 32

Type: ERROR

Impact:

EPMFR-00054: Cannot connect to server on {0}

Cause: Failure to connect to the specified server is most likely due to an RMI (Remote Method Invocation) issue.

Action: Verify that the RMI (Remote Method Invocation) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00055: Could not connect to server on {0}

Cause: Failed to connect to the specified server most likely due to an RMI issue.

Action: Verify the RMI (Remote Method Invocation) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00056: Cannot obtain report server list from server.

Cause: Failed to get a report server list because the Hyperion Registry is not accessible.

Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00057: Cannot obtain print server list from server

Cause: Failed to get a print server list because the Hyperion Registry is not accessible.

Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00058: Cannot obtain scheduler server from server

Cause: Failed to get a scheduler server list because the Hyperion Registry is not accessible.

Action: Verify that the Hyperion Registry is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00059: Invalid login: ({0})

Cause: The login security credentials for a given data source were invalid.

Action: Provide data source credentials to view the portlet content.
Level: 32

Type: ERROR

Impact:

EPMFR-00060: Invalid report: ({0})

Cause: The specified Financial Reports report failed to be generated by the portlet.

Action: Ensure that the specified report exists or can be run using the Financial Reports Web preview.
Level: 32

Type: ERROR

Impact:

EPMFR-00061: Cannot retrieve Row & Column Template [{0}] into Grid '{1}'. The template may have been moved, renamed or deleted from the repository.

Cause: A reference to a Row and Column template was not found in the repository.

Action: Ensure that the template exists in the expected folder within the repository. It could have been renamed, moved, or deleted. But it needs to exist in the specified path.
Level: 32

Type: ERROR

Impact:

EPMFR-00062: Error adding incompatible Row & Column template [{0}] to Grid '{1}'. The template and/or grid may have been modified such that they are no longer compatible. The insert error code is {2}.

Cause: Dimensions on row or column have changed making the Row & Column template invalid for the grid.

Action: No action is required. The invalid Row & Column template was removed.
Level: 32

Type: ERROR

Impact:

EPMFR-00063: The maximum calculation limit of {0} has been reached. Further processing of this cell calculation will not occur

Cause: The report contained unevaluated cells due to reaching the maximum calculations limit.

Action: Update the MaximumCalculationIterations setting. Refer to the documentation for instructions.
Level: 32

Type: ERROR

Impact:

EPMFR-00064: Error while opening connection for user: {0} to the datas source: {1}:{2}

Cause: An error occurred when attempting to establish a connection with a selected data source.

Action: Ensure that the data source exists and is available. Also, verify user credentials to selected data source are accurate.
Level: 32

Type: ERROR

Impact:

EPMFR-00065: Financial Management server {0} is not responding

Cause: A connection could not be made to the Financial Management server. The Financial Management server is either offline or has been reconfigured.

Action: Verify the Financial Management connection information and ensure that the server or cluster is online.
Level: 32

Type: ERROR

Impact:

EPMFR-00066: Attempting to cancel Essbase report script for ID: {0}

Cause: User issued a cancel request for the essbase report script.

Action: No action is required. The Essbase report script will be canceled if possible.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00067: Canceling run for job with instanceId: {0}

Cause: The job with the associated ID was canceled.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00068: Invalid attempt to access controlled file: {0}

Cause: The file path was incorrect.

Action: Enter the correct file location and try again.
Level: 32

Type: ERROR

Impact:

EPMFR-00069: START: JobId: {0}; User: {1}; Name: {2}

Cause: The START time of the associated job with the given ID was marked.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00070: END: JobId: {0}

Cause: The END time of the associated job with the given ID was marked.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00071: Custom Socket Factories loaded successfully

Cause: The sockets connecting to the RMI server were successfully established.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00072: Unable to establish port within established range

Cause: The established range of ports selected to access the RMI server were unavailable.

Action: Either reestablish a different range with available ports, or, stop nonessential processes that are occupying the port range, and then retry.
Level: 32

Type: FATAL

Impact:

EPMFR-00073: User preferences or ReportServer object are not properly initialized. Unable to save User Preferences.

Cause: The connection to the server possibly was disrupted.

Action: Log out and try again.
Level: 32

Type: ERROR

Impact:

EPMFR-00074: User preferences or ReportServer object are not properly initialized. Unable to save User Preferences.

Cause: The connection to the server possibly was disrupted.

Action: Log out and try again.
Level: 32

Type: ERROR

Impact:

EPMFR-00075: Cannot connect to Related Content destination. status = {0}.

Cause: The Related Content destination was not available.

Action: Verify that the Related Content destination exists and that the calling object has it set correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00076: Substituting related content attributes. Reference String is: [{0}]

Cause: The related content attributes were substituted.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00077: Error exporting file: {0}

Cause: The file may have been deleted.

Action: Refresh the browser and try the operation again.
Level: 32

Type: ERROR

Impact:

EPMFR-00078: Error exporting file: {0}

Cause: The file may have been deleted.

Action: Refresh the browser and try the operation again.
Level: 32

Type: ERROR

Impact:

EPMFR-00079: Error getting folder: {0}

Cause: The folder may have been deleted.

Action: Refresh the browser and retry the operation.
Level: 32

Type: ERROR

Impact:

EPMFR-00080: Error retrieving report or snapshot: {0}

Cause: The book contains a report or snapshot that was not found.

Action: Ensure that the report or snapshot exists in the book.
Level: 32

Type: ERROR

Impact:

EPMFR-00081: Connected to server: {0}

Cause: A successful connection was made to the Report Server.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00082: Unable to stop job {0}

Cause: The selected data source was not responding to the cancel request.

Action: Verify that the selected data source is accessible and operating. Check the logs of the data source for any other issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00083: Unable to delete job: {0}

Cause: The Report Server could not be accessed.

Action: Verify that the Report Server is running and verify that the user has permissions to delete the scheduled job.
Level: 32

Type: ERROR

Impact:

EPMFR-00084: Error executing member selection: [{0}]

Cause: Either the member selection was not valid or the data source connection failed.

Action: Check connection to the data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00085: Error executing member selection: [{0}]

Cause: Either the member selection was not valid or the data source connection failed.

Action: Check the connection to the data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00086: HFM (Hyperion Financial Management) indicates that either data or metada has changed.

Cause: HFM (Hyperion Financial Management) indicates that either data or metada had changed.

Action: The current connection needs to be discarded and a new connection acquired, then rerun the book or report.
Level: 32

Type: WARNING

Impact:

EPMFR-00087: Error in setting up the 'Org By Period Filter'

Cause: Either the member selection was not valid or the data source connection failed.

Action: Check connection to the data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00088: External authentication successful for user: [{0}] succeeded in {1} ms.

Cause: The user logon was successful in the associated time in milliseconds.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00089: user [{0}] has no access to Financial Reporting.

Cause: A user without any Financial Reporting roles tried to access Financial Reporting.

Action: Review the user's credentials for security purposes.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00090: Failure to initialize ADM

Cause: The Financial Reporting Server did not initialize the ADM component for data source communication.

Action: A configuration issue is the likely cause, so verify that the ADM is specified within the classpath or path.
Level: 32

Type: ERROR

Impact:

EPMFR-00091: Starting Report Server and modules

Cause: The Report Server and associated modules were started.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00092: Error starting Report Server

Cause: The report server did not start.

Action: Check a variety of possible failures including: Port conflicts or other configuration issues, system hostname incorrectly configured, and that the RMI registry is available.
Level: 32

Type: ERROR

Impact:

EPMFR-00093: Successful start for Financial Reporting Authentication, Repository and Reports modules.

Cause: The Financial Reporting Authentication, Repository and Reports modules started successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00094: Error during datasource connection cleanup

Cause: Another request to close the datasource connections may have been issued previous to the current request.

Action: Check the list of active sessions and retry, closing any existing sessions.
Level: 32

Type: ERROR

Impact:

EPMFR-00095: Invalid command line parameters

Cause: The number of command line parameters was incorrect.

Action: Ensure that the correct number of parameters are entered when starting from the command line.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00096: Error while writing the binary data of the report object to file: ({0})

Cause: An error occurred while writing the binary data of the report object to the specified file.

Action: Verify that the user has permission to write to the file and ensure that there is enough disk space.
Level: 32

Type: ERROR

Impact:

EPMFR-00097: Removing annotation on existing snapshot as duplicate annotation is generated: {0}

Cause: The annotation on the existing snapshot was a duplicate and was removed.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00098: Retrieving annotations from repository: {0}

Cause: Annotations were retrieved from the repository

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00099: In method Instance.createDuplicateAnnotationsForSnapshot() annotation count: {0}

Cause: In method Instance.createDuplicateAnnotationsForSnapshot() annotation count: {0}

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00100: Creation of duplicate annotations for snapshot successful: {0}

Cause: Duplicate annotations for snapshot were completed: {0}

Action: No Action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00101: Not expecting Context Value; Finding: {0}; Expected: {1}

Cause: An invalid Context Value was received and might not exist in the repository.

Action: Verify that the instance exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00102: Error in sending e-mail: {0}

Cause: An error occurred while sending an e-mail and can be caused by network issues or invalid information.

Action: Verify the e-mail address and check if mail server is available.
Level: 32

Type: ERROR

Impact:

EPMFR-00103: Error while getting dimension: {0}

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.

Action: Verify that the data source is running and accessible, and then retry. Otherwise, check the data source logs for any data access issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00104: Error while getting dimension: {0}

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.

Action: Verify that the data source is running and accessible, and then retry. Otherwise check the datasource logs for any data access issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00105: Error while getting member selections

Cause: The datasource connection was either lost or not established. Otherwise an internal error in the data source occurred.

Action: Verify that the data source is running and accesible, and then retry. Otherwise check the datasource logs for any data access issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00106: Failure in exporting user session for use in static HTML generation

Cause: Access to the Report Server connection might have been lost.

Action: Verify the Remote Method Invocation (RMI) service is operational and the same with the Report Server. Ensure that all communication routes between the services are also available. Contact Oracle Support Services if all services and comunication routes are operational.
Level: 32

Type: ERROR

Impact:

EPMFR-00107: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00108: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00109: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00110: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00111: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00112: Error while storing PDF with the instance: {0}

Cause: The PDF file was not stored, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, or the print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00113: Cannot find the static book template root directory

Cause: The static book template root directory within the scheduler properties was not found.

Action: Check if there are any product configuration issues within the config logs. Check if the SchedulerTemplate is defined in fr_scheduler.properties.
Level: 32

Type: ERROR

Impact:

EPMFR-00114: Error creating zip file. File does not exist: {0}.

Cause: The specified file and path did not exist.

Action: Verify that the file and path specified exist.
Level: 32

Type: WARNING

Impact:

EPMFR-00115: Data source names to validate: {0}

Cause: A status message lists the data sources that were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00116: Data source names to validate: {0}

Cause: A status message that lists the data sources that were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00117: Connecting to Report Server: {0}

Cause: The Report Server was connected for validation.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00118: Users to validate: {0}

Cause: Users were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00119: Users to validate: {0}

Cause: User were validated.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00120: Finding {0} match(es).

Cause: A status message was provided with the data source information from the user's point of view.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00121: This action will delete {0} POVs

Cause: A status message was provided that stated the number of POVs that were deleted.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00122: Not finding POVs

Cause: A status message was provided that stated that no POVs were found.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00123: User POV import LoginID = {0}

Cause: A status message was provided that listed the user ID while importing a user POV.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00124: Not finding user: {0}

Cause: There was an unforseen condition where user information could not be extracted from security.

Action: Generally this error should not happen. An extreme condition where this may occur is if security were to intermittently fail. Check the foundation services and the network for possible issues. Contact Oracle Support Services if unable to be resolved.
Level: 32

Type: WARNING

Impact:

EPMFR-00125: Member missing: {0}

Cause: The member name was not found within the data source because it either did not exist or could not be seen by the current user. It will not be imported.

Action: By default, the member name is skipped. However, if the member name is needed, then it must be made available either by adjusting the datasource security access for the user, or by entering the member name into the data source.
Level: 32

Type: WARNING

Impact:

EPMFR-00126: No DATASOURCE_NAME in XML file

Cause: The XML file being imported for user POV information was missing a datasource name.

Action: Supply a valid datasource name in the XML file.
Level: 32

Type: ERROR

Impact:

EPMFR-00127: Error loading config file: {0}

Cause: The specified config file did not exist or was not accessible.

Action: Supply a valid and accessible file name as a parameter.
Level: 32

Type: ERROR

Impact:

EPMFR-00128: Missing AdminUser

Cause: The configuration file did not have an administrative user (AdminUser) specified.

Action: In the configuration file, specify a user (AdminUser) with Administrator access.
Level: 32

Type: ERROR

Impact:

EPMFR-00129: No AdminPassword

Cause: The configuration file did not have an administrator password (AdminPassword) specified.

Action: In the configuration file, specify an administrator password (AdminPassword) for the user.
Level: 32

Type: ERROR

Impact:

EPMFR-00130: No ImportFileName

Cause: The configuration file did not have a user POV import file name (ImportFileName).

Action: Specify a valid import file name (ImportFileName) when running in import mode.
Level: 32

Type: ERROR

Impact:

EPMFR-00131: ImportFileName missing: {0}

Cause: The specified user POV import file name (ImportFileName) was invalid.

Action: Specify a valid import file name (ImportFileName)when running in import mode.
Level: 32

Type: ERROR

Impact:

EPMFR-00132: Error while reading the ImportFile

Cause: An error occurred while reading the import file. This could be caused by a file access issue or any other error while processing the import file.

Action: Verify that the file is still accessible and readable to the user. Look for other issues within both the Report Server and connecting data sources for other possible causes. Contact Oracle Support Services for additional assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00133: Error while reading the ImportFile

Cause: An error occurred while reading the import file. This could be caused by a file access issue or any other error while processing the import file.

Action: Verify that the file is still accessible and readable to the user. Look for other issues within both the Report Server and connecting data sources for other possible causes. Contact Oracle Support Services for additional assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00134: No ExportFileName

Cause: The user POV export file name (ExportFileName) was not specified.

Action: Specify a valid user POV export file name (ExportFileName).
Level: 32

Type: ERROR

Impact:

EPMFR-00135: No ReportServer

Cause: A valid and working Report Server (ReportServer) was not specified.

Action: Specify a valid and working Report Server (ReportServer).
Level: 32

Type: ERROR

Impact:

EPMFR-00136: Starting Hyperion Financial Reporting ManageUserPOV Utility at: {0}

Cause: A status message indicating the ManageUserPOV utility has started and accompanied by a time stamp to monitor the time lapse.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00137: Ending Hyperion Financial Reporting ManageUserPOV Utility at: {0}

Cause: The ManageUserPOV utility was ended and accompanied by a time stamp to mark the end of the time lapse.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00138: Usage: ManageUserPov Mode ConfigFile\tMode = import | export | delete\tConfigFile = configuration file name such as ManageUserPov.properties

Cause: An instruction about how to use the ManageUserPov utility was provided.

Action: Follow the instructions of the message.
Level: 32

Type: ERROR

Impact:

EPMFR-00139: Data source does not exist: {0}, A new one will be created.

Cause: The data source was not previously configured but the utility attempted to create a connection with the specified data source automatically.

Action: No action is required unless a new data source cannot be created automatically.
Level: 32

Type: WARNING

Impact:

EPMFR-00140: Creating data source: {0}

Cause: The data source was created successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00141: Exception: {0} in loading locale strings for locale: {1}

Cause: The file that contains the translated messages either was not found or the file contained errors.

Action: Look at the installation and configuration logs for possible errors. Contact Oracle Support Services for additional assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00142: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, an invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00143: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00144: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00145: Error while storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00146: Error storing PDF

Cause: The PDF file was not stored properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00147: Error storing PDF.

Cause: The PDF file was was not stord properly, likely due to: The central repository was not available or access was revoked, An invalid file name was specified, The print server was not available.

Action: Verify that the central repository is accessible and that everything is configured with the correct credentials. Also, ensure that the print server is available and that the file name to be saved has a valid file name.
Level: 32

Type: ERROR

Impact:

EPMFR-00148: Start of print server job

Cause: print server job, like printing of report or book, was started.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00149: Completed printing of book or report

Cause: The book or report printing was completed.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00150: Cannot get page number count for instance '{0}'. Continuous page numbers may not be correct.

Cause: There was no page count for instance '{0}'. Continuous page numbers may be applied incorrectly.

Action: Verify that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00152: Cannot find BookTOCPrintTemplate {0} entry in properties file. Cannot generate Book TOC.

Cause: The specified BookTOCPrintTemplate entry was not found in the properties file. The Book TOC was not generated.

Action: Verify that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00153: Cannot print report '{0}' within Book '{1}'

Cause: The specified report was not printed within the specified book.

Action: Ensure that all external object links in the book are correct, that the book is valid, and that the report exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00157: Cannot obtain page count from file '{0}'. The file type is not supported for printing.

Cause: The page count was not obtained from the specified file. The file type is not supported for printing.

Action: Verify that all the external links are satisfied and the instance runs correctly in HTML.
Level: 32

Type: ERROR

Impact:

EPMFR-00160: Cannot retrieve the document file: '{0}'

Cause: The specified document file was not retrieved.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00161: Error generating print for report instance '{0}'. Return code: {1}

Cause: There was an error when trying to generate a printing of the specified report instance.

Action: Verify that the instance runs correctly in HTML and if it has attachments, that the links are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00162: Start of run for {0} job {1}

Cause: The specified print job was started.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00163: End of run for {0} end

Cause: The specified print job ended.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00164: Cannot print using printer '{0}'. The printer is either not available to the Print Server or not configured for the host computer's services.

Cause: The specified printer was not used because either it was not available to the print server, or it was not configured for the host computer's services.

Action: Ensure that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00165: Error when printing an instance

Cause: There was an error generated when the instance was printing.

Action: Verify that the instance runs correctly in HTML and if it has attachments, that the links are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00166: No page count for the table of contents in book '{0}'

Cause: The page count for the table of contents in the specified book was not obtained.

Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00167: No table of contents in book '{0}'

Cause: The table of contents in the book was not produced.

Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00168: Cannot merge PDF file '{0}'. The file does not exist.

Cause: The specified PDF file was not merged because the file did not exist.

Action: Verify that the print server is installed correctly and Ghostscript is there.
Level: 32

Type: ERROR

Impact:

EPMFR-00169: Error in merging PDF file ({0})

Cause: The attempt to merge the specified PDF file generated an error.

Action: Verify that the print server is installed correctly and that Ghostscript is there.
Level: 32

Type: ERROR

Impact:

EPMFR-00170: Cannot get page number count for instance '{0}'. Continuous page numbers may not be correct.

Cause: There was no page count or continues page numbers because the print server might be installed incorrectly.

Action: Verify that all external object links in the book are correct and that the book is valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00171: Cannot print instance: '{0}'. The PostScript file for the instance does not exist.

Cause: The specified instance was not printed. The PostScript file for the instance did not exist.

Action: Ensure that Ghostscript is installed.
Level: 32

Type: ERROR

Impact:

EPMFR-00172: Cannot print instance: '{0}'. The PostScript file for the instance does not exist.

Cause: The specified instance was not printed. The PostScript file for the instance did not exist.

Action: Ensure that Ghostscript is installed.
Level: 32

Type: ERROR

Impact:

EPMFR-00173: Error generating the bookmark outline for '{0}'

Cause: The bookmark outline for the specified PDF file generated an error.

Action: Ensure that the iText version is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00174: Error generating the book table of contents for '{0}'

Cause: The book table of contents for the specified PDF file generated an error.

Action: Verify that the iText version is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00175: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00176: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00177: Cannot obtain page count from file '{0}'. The file type is not supported for printing.

Cause: The page count was not obtained from the specified file. The file type is not supported for printing.

Action: Ensure that the file type is supported by print server.
Level: 32

Type: ERROR

Impact:

EPMFR-00178: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00179: Error reading external PDF file '{0}'. It will not be included in the PDF output.

Cause: There was an error when reading the specified external PDF file.

Action: Verify that iText has the correct version.
Level: 32

Type: ERROR

Impact:

EPMFR-00180: Cannot retrieve the document file: '{0}' The returned error code is: {1}, Last error: {2}

Cause: The specified document files was not retrieved.

Action: Verify that the external object's link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00181: Cannot produce the PDF output for the external document '{0}'

Cause: The specified external document file did not produce PDF output.

Action: Verify that external link in the print object is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00182: Cannot produce the PDF output for the book or instance '{0}'. The returned error code is: {1}, Last error: {2}

Cause: The specified book or instance did not produce PDF output.

Action: Ensure that the HRDocumentPrinting.dll file is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00183: Cannot print instance or book: '{0}'. The print file is not produced.

Cause: The specified instance or book was not printed. The print file was not produced.

Action: Verify that Ghostscript is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00184: Cannot send output to system printer. No printer specification.

Cause: Because no printer was specified, the output was not sent to the system printer.

Action: Verify that the physical printer is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00185: Cannot send instance output to system printer ('{0}'). No instance retrieval.

Cause: The instance was not retrieved because the instance output was not sent to the system printer.

Action: Ensure that the server which has the repository is up and the object is running.
Level: 32

Type: ERROR

Impact:

EPMFR-00186: Cannot send book output to system printer ('{0}'). No book retrieval.

Cause: The book was not retrieved because the book output was not sent to the system printed.

Action: Ensure that the server which has the repository is up and the book is running.
Level: 32

Type: ERROR

Impact:

EPMFR-00187: Invalid object type '{0}'. Cannot send output to system printer('{1}')

Cause: Due to an invalid file type, the output was not sent to the specified system printer.

Action: Verify that the file type is supported by the print server.
Level: 32

Type: ERROR

Impact:

EPMFR-00188: Successful printing '{0}' on system printer '{1}'

Cause: The specified document was successfully printed on the specified system printer.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00189: FRExecute has invalid cell reference '{0}'

Cause: FRExecute referenced an invalid cell.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00190: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00191: Cannot replace FRExecute function with the result.

Cause: The FRExecute function could not be replaced with the result.

Action: Verify that Microsoft Word is installed on the machine where the print server is located.
Level: 32

Type: ERROR

Impact:

EPMFR-00192: Cannot load Ghostscript or Distiller.

Cause: Ghostscript or Distiller could not be loaded.

Action: Ensure that a supported version of Ghostscript or Distiller is properly installed on the print server.
Level: 32

Type: ERROR

Impact:

EPMFR-00193: Error by Ghostscript in converting to PostScript.

Cause: A supported vesion of Ghostscipt may not be installed on the print server.

Action: Ensure that a supported version of Ghostscript is installed on the print server. If the problem persists, please contact Oracle Support Services.
Level: 32

Type: ERROR

Impact:

EPMFR-00194: PDF root directory is {0}

Cause: The cited directory name was the root directory of the PDF file.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00195: The report: [{0}] not cancelling

Cause: The specified report failed to cancel.

Action: Verify that the Print Server or Network is not down.
Level: 32

Type: ERROR

Impact:

EPMFR-00196: Printer {0} not accessible on print server: {1}

Cause: Printer {{0}} was not accessible on print server: {1}.

Action: Verify that the print server is running and that the printer is available.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00198: ERROR: duplicate member in a prompt. Duplicate member will be removed.

Cause: A duplicate member was found during member selection from the data source.

Action: No action is required. A duplicate member was removed from the member selection display.
Level: 32

Type: ERROR

Impact:

EPMFR-00199: Over 50 dimensions in the data source. Removing the following dimensions which are set to the default member:

Cause: An SAP data source with more then 50 dimensions was found. The SAP BAPI driver does not support accessing a data source with more then 50 dimensions.

Action: Reduce the number of dimensions in the data source or use a different data source.
Level: 32

Type: ERROR

Impact:

EPMFR-00200: Error while setting POV:

Cause: There was probably a connection error with the data source while setting the POV.

Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 32

Type: WARNING

Impact:

EPMFR-00201: Exception while getting dimension {0}

Cause: There were datasource access issues or an internal error in the data source.

Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00202: Exception while getting dimension {0}

Cause: There were datasource access issues or an internal error in the data source.

Action: Verify that the selected data source is available, access credentials are correct, or review the logs from the data source for other possible issues.
Level: 32

Type: ERROR

Impact:

EPMFR-00203: Using Enterprise Scheduling Services for scheduling

Cause: The Enterprise Scheduling Service was used.

Action: No is action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00205: Scheduler not ready to publish itself. Retry in {0} minutes.

Cause: No Report servers were running.

Action: Ensure that the Report Server is running. Retry in the specified minutes.
Level: 32

Type: WARNING

Impact:

EPMFR-00206: Successful start of Scheduler Server

Cause: The Scheduler Server was started successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00207: Scheduler cannot contact any Report Server. Exiting.

Cause: The Scheduler did not start because it did not contact any Report Server.

Action: Check on the availablilty of configured Reports Servers.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00208: Cannot start scheduler service:

Cause: An unexpected error occurred while the Scheduler Service was binding to the Report Server.

Action: Contact Oracle Support Services for assistance.
Level: 32

Type: ERROR

Impact:

EPMFR-00210: Scheduler Server stopped

Cause: The Scheduler Server was stopped.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00213: Batch Job file: {0} not found. Error reported:

Cause: The specified scheduled batch job file was not found. The file may have been deleted or moved to another location.

Action: Verify that the specified file exists in the expected location and rerun the job.
Level: 32

Type: ERROR

Impact:

EPMFR-00215: Schema '{0}' missing. Attempting to create a new one.

Cause: The given schema was not previously loaded. An attempt to load it occurred.

Action: Ensure that the given schema is valid and can be loaded. Look for additional warnings.
Level: 32

Type: WARNING

Impact:

EPMFR-00216: Error while parsing a new schema:{0}

Cause: The given error was produced while attempting to parse a schema.

Action: Ensure that the schema is valid and complies with the XBRL 2.1 specification.
Level: 32

Type: ERROR

Impact:

EPMFR-00217: Schema: '{0}' missing. Cannot delete it.

Cause: The given schema was not found.

Action: Ensure that the given schema exists and can be removed from the file system.
Level: 32

Type: WARNING

Impact:

EPMFR-00218: Schema: '{0}' missing. Cannot delete it.

Cause: The given schema was not found.

Action: Ensure that the given schema exists and can be removed from the file system.
Level: 32

Type: WARNING

Impact:

EPMFR-00219: Error during the auto-update of Schemas:{0}

Cause: The error occurred while attempting to auto-update the schemas in the file system.

Action: Ensure that the schema exists, is valid and complies to the XBRL 2.1 specification.
Level: 32

Type: ERROR

Impact:

EPMFR-00220: Error attempting to create a row and column template

Cause: An unexpected error occurred while attempting to add a row and column template into a grid.

Action: Review the Report Server log file for details on the error.
Level: 32

Type: ERROR

Impact:

EPMFR-00221: Error attempting to add a row or column from a template.

Cause: An unexpected error occurred while attempting to add a row or column from a template into a grid.

Action: Review the Report Server log file for details on the error.
Level: 32

Type: ERROR

Impact:

EPMFR-00233: Error while getting content at: ({0}). Trying ({1}/{2}) instead.

Cause: The path for the taxonomy was not found.

Action: Ensure that the taxonomy exists for the given path.
Level: 32

Type: WARNING

Impact:

EPMFR-00234: Unknown linkbase role: {0} found. Linkbase will not be included.

Cause: The given linkbase could not be added as a reference from a taxonomy.

Action: Ensure that the given linkbase is valid and can be added as a reference to a taxonomy.
Level: 32

Type: ERROR

Impact:

EPMFR-00235: The presentation linkbase '{0}' is empty. A flat taxonomy tree may display.

Cause: The taxonomy's presentation linkbase was empty, which typically causes a flat taxonomy tree to be rendered.

Action: Provide a presentation linkbase for the given taxonomy.
Level: 32

Type: WARNING

Impact:

EPMFR-00236: TaxonomyElement: {0} not found.

Cause: The presentation linkbase had a reference to a taxonomy element that could not be found.

Action: Ensure that the presentation linkbase has references to valid taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00237: Taxonomy Element Node: {0} not found

Cause: A taxonomy element node could not be obtained referenced by the given element ID.

Action: Ensure that the taxonomy element exists with the taxonomy.
Level: 32

Type: WARNING

Impact:

EPMFR-00238: Taxonomy element '{0}' already exists.

Cause: The given taxonomy element had already been processed. The taxonomy seemed to have a duplicate element declaration.

Action: Ensure that the taxonomy does not contain duplicate taxonomy element declarations.
Level: 32

Type: WARNING

Impact:

EPMFR-00239: The taxonomy element {0} was not mapped, as it is an abstract type.

Cause: The given element could not exist within an instance document. Typically, this is because an abstract element was mapped.

Action: Ensure that only mappable taxonomy elements are mapped within a report. Do not map abstract elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00240: Element specified in the locator: {0} {1} not found

Cause: The given taxonomy element could not be found from the given locator.

Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00241: Element specified in the locator: {0} {1} not found

Cause: The given taxonomy element could not be located from the given locator.

Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00242: Error in TextCell {0} Col {1} Row {2} Formula: '{3}'\t Error: {4}

Cause: There was a syntax error in the function.

Action: Fix the syntax error that is described in the error message.
Level: 32

Type: ERROR

Impact:

EPMFR-00243: Error in TextObject Formula: '{0}'\t Error: {1}

Cause: There was a syntax error in the function.

Action: Fix the syntax error that is described in the error message.
Level: 32

Type: ERROR

Impact:

EPMFR-00244: Report Server Initializing

Cause: The Report Server initialized.

Action: No action is required
Level: 32

Type: INFORMATION

Impact:

EPMFR-00245: Report Server started

Cause: The Report Server initialized and started successfully.

Action: No action is required
Level: 32

Type: INFORMATION

Impact:

EPMFR-00246: Error while starting the Report Server

Cause: The Report Server failed to initialize.

Action: Check a variety of possible failures including: Port conflicts or other configuration issues, incorrect system hostname configuration, and availability of the Remote Method Invocation (RM0).
Level: 32

Type: ERROR

Impact:

EPMFR-00247: Hyperion Financial Management reports that either Metadata or Data has changed. Discarding the current connection and reconnecting.

Cause: Possible metadata or data load was performed on the Hyperion Finacial Management (HFM) server.

Action: Rerun the book or report.
Level: 32

Type: WARNING

Impact:

EPMFR-00248: Book contains reports not found: {0}

Cause: The book contained reports which could not be found.

Action: Ensure that the contained report(s) exists.
Level: 32

Type: ERROR

Impact:

EPMFR-00249: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00250: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.

Action: Verify that data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00251: Cannot not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00252: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00253: Cannot find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00254: Cannot not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00255: Cannot find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source name.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00256: Cannot find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: Could not make a connection to the data source by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00257: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00258: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00259: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00260: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00261: Could not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00262: Schema '{0}' not found. Attempting to create a new one.

Cause: The given schema was not previously loaded. An attempt to load it occurred.

Action: Ensure that the given schema is valid and can be loaded. Look for additional subsequent warnings.
Level: 32

Type: WARNING

Impact:

EPMFR-00263: XBRL Schema Manager not properly initialized

Cause: The XBRL Schema Manager was not properly configured.

Action: Reconfigure the XBRL Schema Manager.
Level: 32

Type: ERROR

Impact:

EPMFR-00264: XBRL Schema Manager not properly initialized

Cause: The XBRL Schema Manager was not properly configured.

Action: Reconfigure the XBRL Schema Manager.
Level: 32

Type: ERROR

Impact:

EPMFR-00265: Schema {0} was not found attempting to create a new one

Cause: The given schema was not previously loaded. An attempt to load it occurred.

Action: Make sure the given schema is valid and can be loaded. Look for subsequent warnings.
Level: 32

Type: WARNING

Impact:

EPMFR-00266: Taxonomy '{0}' does not have any namespace

Cause: The given taxonomy did not declare a namespace and was not be processed.

Action: Ensure that the given taxonomy declares a valid namespace.
Level: 32

Type: WARNING

Impact:

EPMFR-00267: Taxonomy '{0}' does not have any namespace

Cause: The given taxonomy did not declare a namespace and was not processed.

Action: Ensure that the given taxonomy declares a valid namespace.
Level: 32

Type: ERROR

Impact:

EPMFR-00268: Error while creating directories for emails:

Cause: The Schedule Server attempted to create a directory for e-mails but failed, most likely due to a system disk access issue.

Action: Verify that the disk is not full and that the user has both read and write access to the drive.
Level: 32

Type: ERROR

Impact:

EPMFR-00269: XBRL Footnote error retrieving report value. Report: {0}. Invalid Row ({1}) and Column ({2})

Cause: An error occurred while retrieving the report value. Invalid row and/or column reference were given.

Action: Ensure that the mapped footnote has valid row and column references to a grid.
Level: 32

Type: ERROR

Impact:

EPMFR-00270: XBRL No language definition in footnote

Cause: A footnote in the report did not provide a valid language definition.

Action: Assign a language to every footnote.
Level: 32

Type: ERROR

Impact:

EPMFR-00271: Report using unsupported version of XBRL. XBRL data is ignored.

Cause: The report had embedded XBRL data. However the version was unrecognized and could not be processed.

Action: Ensure that the XBRL data in the report definition is saved with the proper Financial Reports version.
Level: 32

Type: ERROR

Impact:

EPMFR-00272: Instance generation failed. File name specified: {0} is invalid.

Cause: The specified filename for the instance report was null or invalid. The instance document was not generated.

Action: Provide a valid file name for the instance document.
Level: 32

Type: ERROR

Impact:

EPMFR-00273: XBRL Footnote for '{0}' not properly set up

Cause: The XBRL footnote had a reference to an invalid report object.

Action: Ensure that all XBRL footnotes have valid references to a report object (grid or text).
Level: 32

Type: ERROR

Impact:

EPMFR-00274: Taxonomy element '{0}' is linked to an unregistered taxonomy '{1}'

Cause: The given taxonomy element belongs to an unregistered taxonomy.

Action: Ensure that the taxonomy used within a report is registered in the taxonomy repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00275: Taxonomy element '{0}' has no context defined. It will not be persisted in the instance document.

Cause: A taxonomy element was mapped to data in a report, but there was no XBRL context associated with it. The element was ignored and not added to the instance document.

Action: Ensure that all mapped taxonomy elements in a report have a corresponding mapped context.
Level: 32

Type: ERROR

Impact:

EPMFR-00276: Taxonomy element '{0}' has no associated report object. It will not be persisted in the instance document.

Cause: A mapped taxonomy element was mapped to an invalid report object (grid or text).

Action: Ensure that all taxonomy elements are mapped to a valid report object.
Level: 32

Type: ERROR

Impact:

EPMFR-00277: Taxonomy element '{0}' has an unregistered taxonomy ('{1}'). It will not be persisted in the instance document.

Cause: A mapped taxonomy element belonged to an unregistered taxonomy. The element was ignored and not added to the instance document.

Action: Ensure that all mapped taxonomy elements in a report belong to a taxonomy that is registered in the Financial Reports system.
Level: 32

Type: ERROR

Impact:

EPMFR-00278: Cannot connect to server on {0}

Cause: Connection to the specified server failed, most likely due to an Remote Method Invocation (RMI) issue.

Action: Verify that the Remote Method Invocation (RMI) service is running without errors. Also look for possible network issues. Contact Oracle Support Services if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00279: Unable to find appropriate Service at {0}

Cause: Connection to the specified server failed, most likely due to an Remote Method Invocation (RMI) issue.

Action: Verify that the Remote Method Invocation (RMI) service is running without errors. Also look for possible network issues. Contact Oracle Service Support if additional assistance is needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00280: Large imported file denied by the annotation UI

Cause: A file exceeding the AttachedFileMaxSize property limit was loaded.

Action: Reduce the file size or increase the AttachedFileMaxSize property.
Level: 32

Type: ERROR

Impact:

EPMFR-00281: Cannot create a Remote Method Invocation (RMI) registry on port: {0}

Cause: Another Remote Method Invocation (RMI) registry was running at the specified port number.

Action: Verify the configuration for the Remote Method Invocation (RMI) registry to avoid conflicts.
Level: 32

Type: ERROR

Impact:

EPMFR-00282: RMI (Remote Method Invocation) registry created on port: {0}

Cause: The Remote Method Invocation (RMI) regsitry was created on the specified port.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00283: Unable to create registry

Cause: An error occurred while attempting to establish a connection with the Remote Method Invocation (RMI) registry.

Action: Verify the configuration of the Remote Method Invocation (RMI) registry and ensure that it is running without errors.
Level: 32

Type: ERROR

Impact:

EPMFR-00284: Financial Reporting Print Server started

Cause: The print server started successfully.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00285: Print server not started

Cause: An error occurred while attempting to establish a connection with the Remote Method Invocation (RMI) registry.

Action: Verify the configuration of the Remote Method Invocation (RMI) registry and ensure that it is running without errors.
Level: 32

Type: ERROR

Impact:

EPMFR-00292: Element specified in the locator: {0} {1} not found.

Cause: The given taxonomy element could not be located from the given locator.

Action: Ensure that the taxonomy's locators have valid references to taxonomy elements.
Level: 32

Type: WARNING

Impact:

EPMFR-00293: Cannot initialize XBRL Schema Collection

Cause: Most likely, there were no schemas in the specified XBRL Location.

Action: This message is harmless if you do not intend to use XBRL. If you do, ensure that you have created the appropriate schemas in the specified location.
Level: 32

Type: WARNING

Impact:

EPMFR-00294: Invalid attempt accessing server controlled properties

Cause: The client side code tried to access a server-only controlled property.

Action: No action needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00295: Unable to extract OBIEE session

Cause: Attempt to get administration level session failed.

Action: Verify the administrator user configuration in OBIEE.
Level: 32

Type: ERROR

Impact:

EPMFR-00297: Initialization of CredentialStore failed

Cause: The credential store could not be located or could not be initialized.

Action: Ensure that the credential store is properly configured.
Level: 32

Type: ERROR

Impact:

EPMFR-00298: Failed obtaining credentials from security store for {0}

Cause: Expected credentials could not be retrieved from credential store.

Action: Verify the credentials stored in credential store.
Level: 32

Type: ERROR

Impact:

EPMFR-00299: Failed obtaining credentials from security store for {0}

Cause: Expected credentials could not be retrieved from credential store.

Action: Verify credentials stored in credential store.
Level: 32

Type: ERROR

Impact:

EPMFR-00300: Attempt to get an undefined configuration property ({0})

Cause: A property was not defined or set. A default property was not available.

Action: Contact Oracle Support Services to obtain the correct default property value and instructions to configure it.
Level: 32

Type: ERROR

Impact:

EPMFR-00301: Attempt to get undefined configuration property ({0})

Cause: A property was not defined or set. A default property was not available.

Action: Contact Oracle Support Services to obtain the correct default property value and instructions to configure it.
Level: 32

Type: ERROR

Impact:

EPMFR-00303: Invalid attempt to authenticate with elevated user credentials

Cause: The configured elevated user credentials caused exception when trying to authenticate.

Action: Check the configured elevated user credentials.
Level: 32

Type: ERROR

Impact:

EPMFR-00304: Error while setting the POV for data source ID: {0}

Cause: There was a problem storing the current POV.

Action: Verify access to the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00305: PDFRootDirectory {0} not created. PDFs not generated.

Cause: The folder required to create the PDF files could not be created.

Action: Create the requird folder on the Print Server.
Level: 32

Type: FATAL

Impact:

EPMFR-00306: getObjectsById:Objects requested={0}, but objects returned is {1}

Cause: Some of the objects were not accessible.

Action: No action is required.
Level: 32

Type: WARNING

Impact:

EPMFR-00307: Cannot print using printer '{0}'. The printer is either not available to the Print Server or not configured for the host computer's services.

Cause: The specified printer was not used because either it was not available to the print server, or it was not configured for the host computer's services.

Action: Ensure that the print server is installed correctly.
Level: 32

Type: ERROR

Impact:

EPMFR-00308: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00309: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00310: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00312: Invalid attempt accessing server controlled properties

Cause: The client side code tried to access a server-only controlled property.

Action: No action needed.
Level: 32

Type: ERROR

Impact:

EPMFR-00313: Invalid attempt to authenticate with elevated user credentials

Cause: The configured elevated user credentials caused exception when trying to authenticate.

Action: Check the configured elevated user credentials.
Level: 32

Type: ERROR

Impact:

EPMFR-00314: Financial Reports is configured to use Classic Print Engine. Please start the Print Server separately

Cause: This is a status message stating that the Financial Reporting Printing Service is configured to use the Classic Print Engine.

Action: Start the Print Server separately.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00315: Invalid user defined prefered date format ({1})

Cause: User defined date format contains Invalid date format characters

Action: Update user preferences with valid a date format
Level: 32

Type: ERROR

Impact:

EPMFR-00316: Custom Socket Factories loaded successfully

Cause: A status message stating that the sockets connecting to the RMI Server has successfully been established.

Action: No action is required.
Level: 32

Type: INFORMATION

Impact:

EPMFR-00317: Unable to establish port within established range

Cause: The established range of ports selected to access the RMI server are all unavailable.

Action: Either reestablish a different range with available ports, or, stop nonessencial processes that are occupying the port range and then retry.
Level: 32

Type: FATAL

Impact:

EPMFR-00318: Custom Socket Factories could not be loaded

Cause: The configured socket factory classes could not be loaded.

Action: Check the configuration for the Socket classes and ensure the entries are correct.
Level: 32

Type: FATAL

Impact:

EPMFR-00319: Book contains reports not found: {0}

Cause: Book contains reports which could not be found.

Action: Ensure that the contained report(s) exists.
Level: 32

Type: ERROR

Impact:

EPMFR-00323: FRExecute has invalid cell reference '{0}'

Cause: FRExecute referenced an invalid cell.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00324: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00325: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00326: FRExecute cannot generate an image for component '{0}'

Cause: FRExecute could not generate an image for the specified component.

Action: Verify that the FRExecute function's parameters are valid.
Level: 32

Type: ERROR

Impact:

EPMFR-00327: Cannot replace FRExecute function with the result.

Cause: The FRExecute function could not be replaced with the result.

Action: Verify that Microsoft Word is installed on the machine where the print server is located.
Level: 32

Type: ERROR

Impact:

EPMFR-00329: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: There was an error when writing the specified external file.

Action: Verify that the PDF output location is correct in the property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00330: Error writing external file '{0}'. It will not be included in the PDF output.

Cause: Error writing the specified external file. It will not be included in the PDF output.

Action: Verify that the pdf output location is correct in property file.
Level: 32

Type: ERROR

Impact:

EPMFR-00331: Cannot print document file: '{0}' \tError code: {1}, Last Error was: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00332: Cannot print document file: '{0}' \tError code: {1}, Last Error was: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00333: Cannot print report '{0}' within Book '{1}'. Make sure the report exists in the repository.

Cause: The specified report was not printed within the specified book.

Action: Ensure that all external object links in book are correct, that the book is valid, and that the report exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00334: Cannot print report '{0}' within Book '{1}'. Make sure the report exists in the repository.

Cause: The specified report was not printed within the specified book..

Action: Ensure that all external object links in book are correct, that the book is valid, and that the report exists in the repository.
Level: 32

Type: ERROR

Impact:

EPMFR-00336: Could not find data source ID: {0} {1}. Attempting to find data source with same name.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00337: Could not find data source ID: {0} {1}. Creating a new data source.

Cause: A connection to the data source could not be made by using the stored data source ID.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: WARNING

Impact:

EPMFR-00338: Could not find data source ID: {0} {1}. Failed to create a new data source for it.

Cause: A connection to the data source could not be made by using the stored data source ID or name, and failed to create a new data source automatically for it.

Action: Verify that the data source is started or restored, and the credentials are correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00339: Usage: ManageUserPov Mode ConfigFile\tMode = import | export | delete\tConfigFile = configuration file name such as ManageUserPov.properties

Cause: An instruction about how to use the ManageUserPov utility was provided.

Action: Follow the instructions of the message.
Level: 32

Type: ERROR

Impact:

EPMFR-00340: Error loading config file: {0}

Cause: The specified config file did not exist or was not accessible.

Action: Supply a valid and accessible file name as a parameter.
Level: 32

Type: ERROR

Impact:

EPMFR-00341: Missing AdminUser

Cause: The configuration file did not have an administrative user (AdminUser) specified.

Action: In the configuration file, specify a user (AdminUser) with Administrator access.
Level: 32

Type: ERROR

Impact:

EPMFR-00342: Cannot print document file: '{0}' \tError code: {1}, Last Error: {2}

Cause: The specified document file was not printed.

Action: Verify that the external document link is correct.
Level: 32

Type: ERROR

Impact:

EPMFR-00343: Financial Reporting server is set to use embedded Print Server. Remote print servers will not register with the Financial Reporting server.

Cause: Financial Reporting server is set to use embedded printing

Action: If you would like to use this external print server, please disable embedded printing in the Financial Reporting server
Level: 32

Type: ERROR

Impact:

EPMFR-00344: Setting BaseWebApp in HIT registry to: "

Cause:

Action:
Level: 32

Type: INFORMATION

Impact:

EPMFR-00345: Setting BaseWebApp in HIT registry to: "

Cause:

Action:
Level: 32

Type: INFORMATION

Impact:

EPMFR-00346: Could not get version information from file system

Cause: version.xml could not be loaded or error parsing the file

Action: Make sure version.xml exists under common/epmstatic/wspace/SmartView/ on server
Level: 32

Type: INFORMATION

Impact:

EPMFR-00347: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00348: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00349: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00350: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00351: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00352: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00353: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00354: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00355: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

EPMFR-00356: The system cannot access the Print Server at this time. Try again later or confirm the print server name.

Cause: The specified Print Server is not accessible

Action: Check the configuration for the correct Print Server name, if the Print Server is running, and if the connection to the Print Server is accessible
Level: 32

Type: WARNING

Impact:

23 EPMWKSP-00101 to EPMWKSP-02508

EPMWKSP-00101: Found application registration with ID "{0}" and name "{1}".

Cause: Indicates the application registration which was found and is recognized by Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00102: Failed to generate context XML.

Cause: Context information is invalid or could not be retrieved from the registry.

Action: Verify products have been properly configured by running Config Tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00103: Initializing Workspace Configuration.

Cause: Workspace is initializing the system using information from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00104: There is an error detecting application ID for role checking.

Cause: An application ID could not be retrieved for CSS role checking.

Action: Verify in the registry that all registered products have a valid value for property applicationId.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00105: Default Application ID for role checking is {0}.

Cause: Indicates the application ID that will be used for CSS role checking.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00106: There was an error determining the URL.

Cause: The logical webapp URL could not be obtained or is invalid.

Action: Verify that the logical webapp URLs specified in the registry for all registered products are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00107: There was an error determining the context.

Cause: The logical webapp context could not be obtained or is invalid.

Action: Verify that the logical webapp context specified in the registry for all registered products are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00108: There was an error parsing file {0}.

Cause: The xml in WSProducts.xml could not be parsed or is invalid.

Action: Verify the file exists and that the xml is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00109: There was an error initializing system registry: {0}.

Cause: The system registry was not properly installed or configured.

Action: Verify connection to the registry is valid and re-run the config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00110: Registry default properties: failed to check and set property {0}.

Cause: The default properties could not be set.

Action: Verify the default registry properties file exists and that the values are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00111: There was an error loading product configuration data: {0}

Cause: The configuration file for at least one product could not be loaded.

Action: Check the Workspace configuration log for further error details.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00112: Failed to initialize the BPMUI authentication class: {0}

Cause: The class could not be found or initialization failed.

Action: Verify that the class is accessible and the entry in web.xml is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00113: There was an error loading product configuration data: {0}

Cause: The configuration file for at least one product could not be loaded.

Action: Check the Workspace configuration log for further error details.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00114: Workspace initialization complete.

Cause: Workspace has initialized and processed the information from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00115: Workspace is running normally.

Cause: No errors were detected during initialization.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00116: Parsing the product file generated the following warnings:

Cause: Indicates the start of the list of possible issues encountered while parsing Workspace's Product file.

Action: Verify the Workspace's Products file exists and that the entries are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00117: Workspace may not function properly unless these are fixed: {0} {1}

Cause: Indicates the xml may not comply with the dtd.

Action: Resolve the issue specified in the warning.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00118: End of warning messages.

Cause: Indicates the end of the list of possible issues encountered while parsing Workspace's Product file.

Action: Verify all warnings are resolved or inconsequential.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00119: Product file parsed without errors.

Cause: The Workspace's Product file was successfully processed.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00120: Attempting registry connection using:{0}{1}{2}{3}

Cause: Indicates the registry information is being obtained to initialize Workspace.

Action: No action required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00122: Looking for the Workspace Product component (type: {0})

Cause: Indicates the Product that is currently being validated and processed as one of the installed products in Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00123: Found component object: {0}

Cause: Indicates the Workspace component that was discovered in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00124: Could not find the Workspace Product component. Check Registry connection and content.

Cause: The registry connection or content may be invalid.

Action: Check Registry connection and content.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00125: Looking for Workspace Logical Webapp (child of Workspace Product, type: {0})

Cause: Indicates that Workspace is searching the EPM Registry for its Logical Webapp.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00126: Could not find the Workspace logical webapp. Check Registry contents.

Cause: The registry connection or content may be invalid.

Action: Check Registry contents.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00127: Could not find the Workspace Web Server component.

Cause: Workspace was not configured properly.

Action: Check the web server is running and configured. Run config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00128: Could not find the logical webapp as a child of the Workspace product node. Check Registry contents.

Cause: Workspace was not properly registered.

Action: Check Registry contents. Run config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00129: Workspace product node has multiple logical webapps. Check Registry contents.

Cause: Workspace should have exactly one component of type LOGICAL_WEB_APP in the EPM Registry.

Action: Verify Registry contents and check configuration tool logs for deployment errors.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00130: Could not find the Workspace Web Server component as a child of the Workspace product node.

Cause: Workspace was not properly configured.

Action: Check Registry contents. Run config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00131: Found {0} webapps plugged in to the HTTP proxy at {1}:{2}

Cause: Indicates the webapps using the HTTP proxy.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00132: Found webapp: {0}

Cause: Indicates the webapp that is under the HTTP proxy.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00133: Web application type: {0}

Cause: Indicates the type of a webapp found while scanning the EPM Registry for products.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00134: This is the web application for EPM Workspace.

Cause: Indicates that a webapp discovered during a registry scan is EPM Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00135: Checking for Workspace configuration file(s)

Cause: Indicates if Workspace configuration file(s) were found.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00136: Checking for configuration file named: {0}

Cause: Indicates the specific configuration file being located.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00137: Found configuration file.

Cause: Indicates that the configuration file is found and accessible.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00138: ERROR: configuration file does not declare sharedServicesId. Product cannot be identified or loaded from product file.

Cause: The configuration file does not contain a node with sharedServicesId as an attribute.

Action: Verify that the product file being loaded is valid and has shreadServicesId declared.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00139: Loaded product with name {0}

Cause: Indicates the product was successfully loaded.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00140: Static file configuration matches version {0}; discarding registry file.

Cause: Indicates that Workspace's Product file has a configuration which matches a configuration in the registry and the configuration found in the Workspace's Product file will be used.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00141: Product not in static configuration file, initializing.

Cause: Indicates that a product's configuration information is being loaded from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00142: Static file configuration is for version(s): {0} but registered product version is {1}

Cause: Indicates that there is a different version of a configuration for the same registered product specified in Workspace's product file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00143: Discarding static configuration.

Cause: Indicates that the product configuration from the registry will be used instead of the one found in Workspace's product file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00144: NOTE: Product version for display is {0}

Cause: Indicates the product version to display in the Help->About.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00145: Skipping integration for this product.

Cause: The version for the product failed the version test.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00146: Product file configuration matches version {0}

Cause: Allow integration of product since it passes the version test.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00147: NOTE: Product version for display is {0}

Cause: The product version was found in the product configuration information.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00148: Skipping integration for this product.

Cause: The product configuration information could not be found in registry or in the Workspace's product file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00149: Product not in static configuration file. Initializing product.

Cause: The product's configuration information was found in the registry but not in the Workspace's product file. Product will be configured with information from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00150: Product file configuration matches version {0}

Cause: Indicate the supported version.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00151: Product file configuration is for version(s): {0} but registered product version is {1}

Cause: Versions between product file configuration version and registered product version are mismatched.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00152: Discarding old configuration.

Cause: A more recent configuration was found and used.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00153: Setting product to use external configuration.

Cause: Indcates that a product does not have a configuration loaded from Workspace's static configuration files, and that the product configuration will be loaded from the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00154: NOTE: Product version for display is {0}

Cause: Indicates the product version that is displayed in Workspace.

Action: No action is required.
Level: 32

Type:

Impact:

EPMWKSP-00155: Product {0}-{1} was not registered. Deactivating product.

Cause: The product may be not supported with the current Workspace version.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00156: Product {0} has been explicitly disabled. Deactivating product.

Cause: The products configuration has specified the disabled attribute.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00157: Product {0} was forcibly enabled and set at version {1}, but the internal configuration is valid for versions {2}.

Cause: The products configuration has the forceEnabled attribute set but the versions set may not be compatible with the current Workspace version.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00159: Setting product to use external configuration.

Cause: Indcates that a product does not have a configuration loaded from Workspace's static configuration files, and that the product configuration will be loaded from the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00162: There was an error building the sorted product list.

Cause: Workspace was unable to determine the correct order in which to display integrated products.

Action: Consult Workspace logs for preceeding error messages. This is likely a consequence of prior errors while scanning the registry.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00163: There was an error refreshing display version for product {0} {1}.

Cause: Workspace could not determine a version number for a product.

Action: This error is not fatal, but product version numbers will be incorrect. Consult Workspace configuration log for further error messages.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00164: Read {0} bytes from the registry.

Cause: Indicates the number of bytes of data successfully processed from the registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00165: Missing product context {0}

Cause: The products context configuration information may be missing or invalid.

Action: Verify the products registration file is valid or run the config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00166: Found and loaded context for {0}

Cause: A product's context was successfully loaded.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00167: Could not find product context for {0}. This product will not load.

Cause: A product's context could not be loaded.

Action: Verify the products configuration has a valid context configuration or run the config tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00168: Failed to parse HSS response for product {0}

Cause: The response may contain an invalid content type or the xml may be invalid.

Action: Verify the response is xml content type and that the xml is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00169: Failed to connect and retrieve info for product {0}

Cause: The product's webapp may not be started, the url to the config xml may be invalid or the config xml is returning an invalid response.

Action: Verify the product's webapp is running, is properly configured and is returning a valid response.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00170: Failed to connect and retrieve info for product {0}

Cause: The product's webapp may not be started, the url to the config xml may be invalid or the config xml is returning an invalid response.

Action: Verify the product's webapp is running, is properly configured and is returning a valid response.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00171: Product file reports the following parse problems.

Cause: The xml is invalid and cannot be parsed.

Action: Try to resolve the reported parse problems.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00172: Workspace may not function properly unless these are fixed:{0} {1}

Cause: The xml couuld not be parsed.

Action: Try to resolve the reported issues.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00173: End of warning messages.

Cause: Indicates the end of the warning messages that needs attention.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00174: Product file parsed without errors.

Cause: Indicates the product file was valid.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00175: Checking HSS with product code {0}

Cause: Information is being retrieved from HSS for this product.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00176: Recovered {0} bytes from HSS.

Cause: The query to HSS was successful.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00177: Failed to recover configuration from HSS.

Cause: Information on this product could not be retrieved from HSS.

Action: Verify HSS connection is valid and the product is properly configured.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00178: There was an error loading default registry properties.

Cause: File was not found or could not be accessed.

Action: Verify file exists and is accessible.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00179: Parsing product file: {0}

Cause: Product file is parsed.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00180: Looking for Workspace Web Server (child of Workspace product with type: {0})

Cause: Indicates the Workspace Web Server.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00181: Found {0} HTTP proxy instance(s).

Cause: Indicates the number of HTTP proxy instances discovered when scanning the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00182: File not found. Ending search.

Cause: Indicates that a product did not have a Workspace configuration file in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00183: EPM System Common Install Version: {0}

Cause: Indicates the version of the Common Installer.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00184: Checking product version numbers:

Cause: Product versions numbers must be compatible.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00185: Version number mismatch between the Workspace and BPMUI components detected. All version numbers must be at the same patchset level (first four parts of the the version number).

Cause: Workspace and BPMUI versions are mismatched.

Action: Locate a patch that is compatible with the current version.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00186: All versions are at the same patchset level.

Cause: System was patched correctly.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00187: Version number check skipped due to missing version numbers.

Cause: The version number was not specified in the configuration information.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00188: Checking Registry version numbers:

Cause: Indicate the current registry version numbers.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00189: Compiled against Registry version: {0}

Cause: Indicates the version of the EPM Registry API against which Workspace was compiled.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00190: WORKSPACE component version: {0}

Cause: Indicates the Workspace build number.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00191: LOGICAL_WEB_APP component version: {0}

Cause: Indicates the component version of Workspace's Logical Webapp component in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00192: WEB_SERVER component version: {0}

Cause: Indicates the component version of Workspace's Web Server component in the EPM Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00193: Version number mismatch between the Workspace and registry components detected. All version numbers must be at the same release level (first three parts of the the version number).

Cause: Workspace and registry components are not on the same release level.

Action: Install and configure the matching Workspace and registry components.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00194: All version numbers are at the same release level.

Cause: Version numbers are from the same release.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00195: WARNING: Product registry version does not match Workspace registry version. Skipping integration for this product.

Cause: Product failed the version test.

Action: No action is required as it may be the product configuration is left over from an upgrade.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00196: Product {0} has at least one string bundle that is not statically loaded. Deactivating product.

Cause: The product's webapp is not running or the files are not there.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00197: BPMUI Java: {0}

Cause: Reports the version number of the BPMUI Java library.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00198: BPMUI Web: {0}

Cause: Reports the version number of the BPMUI shared web application.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00199: Workspace Java: {0}

Cause: Reports the version number of the Workspace Java library.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00201: Property "{0}" is not in the Registry. Default value is used.

Cause: Mentioned property is absent in the Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00202: Message cache was cleared by admin request.

Cause: Admin user has changed server settings related to messaging system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00203: Message cache expired. The message will be reread from the Registry.

Cause: Time of cache expiration has passed

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00204: Empty message is stored in the Registry.

Cause: No message is stored in the Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00205: Can't find the file with name "{0}" in the Registry.

Cause: No message is stored in the Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00206: There was an error reading message from the Registry.

Cause: Unexpected error occurred during reading message from the Registry.

Action: Verify HSS connection.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00301: Product "{0}" has been excluded from the list of SmartView providers.

Cause: Product is in list of excluded products.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00302: There was an error loading the list of products excluded from the list of SmartView providers.

Cause: The file with list of excluded products is corrupted or absent.

Action: Verify the file with list of excluded products.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00401: Error getting Workspace configuration instance.

Cause: System is not properly initialized.

Action: Verify system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00402: There was an error during authentication.

Cause: User has entered wrong credentials.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00403: No credentials provided in the SmartView request.

Cause: User has not entered credentials.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00404: There was an error during processing:

Cause: Unexpected error occurred.

Action: Verify system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00405: There was an error parsing the request.

Cause: Invalid request was sent

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00406: There was an error building handshake response.

Cause: Unexpected error occurred.

Action: Check log details and verify that system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00408: There was an error building response.

Cause: Unexpected error occurred.

Action: Check log details and verify that system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00507: There was an error determining the instanced product list.

Cause: Workspace was unable to determine the list of products that use per-instance provisioning.

Action: This is usually caused by an error when loading product configuration info. Check the Workspace configuration logs for other errors.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00508: There was an error determining the provisioned application list.

Cause: Workspace was unable to determine the list of applications for which the current user is provisioned.

Action: Check the Workspace security log for detailed errors from the security API.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00509: There was an error fetching an application registration

Cause: Workspace cannot fetch an application registration from Hyperion Shared Services and/or the EPM Registry.

Action: The Workspace configuration or security logs will contain further errors. Verify the registration of the product and application in Hyperion Shared Services.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00510: Fetching registration for product {0} application {1}

Cause: Indicates the product registration for an application is being retrieved.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00511: Fetched {0} bytes from HSS.

Cause: Indicates that the product registration information for an application has been retrieved from HSS successfully.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00512: Parsing the instance file caused the following warnings:

Cause: Indicates a list of warnings generated when parsing the application's registration file.

Action: These issues may cause the application to not function properly in Workspace. Verify the product registration in Shared Services.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00513: Instance may not function properly unless these are fixed:{0}{1}

Cause: Indicates a list of warnings generated when parsing the application's registration file.

Action: These issues may cause the application to not function properly in Workspace. Verify the product registration in Shared Services.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00514: End of warning messages.

Cause: Indicates all the warning messages has been listed.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00515: Instance file parsed without errors.

Cause: An application instance file was successfully processed by Workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00601: Log on failed: error while checking user roles.

Cause: The user attempting to log on does not have the necessary role requirements for log on.

Action: Verify the user is properly provisioned to log on.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00602: Log on failed: error while checking user preferences.

Cause: The user preferences repository could not be accessed.

Action: Verify the connection to the user preferences repository is valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00603: There was an error while creating the Reporting and Analysis security token.

Cause: Workspace could not obtain a Reporting and Analysis security token.

Action: Verify the Reporting and Analysis webapp and services is running.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00604: There was an error determining user accessibility settings.

Cause: Obtaining accessibility mode setting from request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie may have failed.

Action: Verify accessibility mode settings is valid and in request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00605: There was an error determining user theme settings.

Cause: Obtaining theme settings from request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie may have failed.

Action: Verify theme settings is valid and in request parameter, CSS Session (Fusion), User Preference (EPM) or extant cookie.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00606: There was an error determining user locale settings.

Cause: There was an error obtaining the locale from the CSS session or request parameter.

Action: Verify the local is valid and in the CSS session or request parameter.
Level: 32

Type: ERROR

Impact:

EPMWKSP-00607: There was an error validating user theme selection.

Cause: The theme selection does not match one of the supported themes.

Action: Verify the user theme selection is one of the supported themes.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01301: Could not resolve role: {0}

Cause: Workspace was unable to verify the existence of the named role.

Action: Verify the user provisioning and product registration in Shared Services. The named role will not be used by Workspace.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01302: Exception while checking user roles

Cause: Workspace was unable to check a user's provisioned roles.

Action: Check the Workspace security log for further errors from the security API
Level: 32

Type: ERROR

Impact:

EPMWKSP-01401: There was an error while parsing {0}

Cause: Workspace was unable to parse its own role definition file.

Action: Verify that the Workspace deployment has not been corrupted. Contact technical support for further guidance.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01402: Mapping role name {0} to role ID {1}

Cause: Indicates that a role has been successfully matched to a Shared Services LDAP ID or a Reporting and Analaysis GUID.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01501: Searching for users matching '{0}' as user {1}

Cause: Indicates a search request for users conducted by an administrator.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01502: Found {0} result(s).

Cause: Indicates the number of users found by an administrative search for users.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01503: Invalid user/group search filter '{0}' specified.

Cause: Indicates that an administrative search for users included an invalid search specification.

Action: Use a valid search string. Search strings for user names are Unicode alphabet character strings preceeded or followed with '*' as a wildcard.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01601: The value for parameter "{0}" was invalid.

Cause: Specified parameter's value is invalid.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01602: Validating parameter "{0}" with value "{1}".

Cause: Parameter is being validated

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01603: Loading list of supported locales from default configuration.

Cause: Default list of supported locales is loaded

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01604: There was an error loading default list of supported locales.

Cause: System is not properly initialized.

Action: Verify system is properly initialized.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01701: There was an error evaluating product-level Constraints for {0}. Deactivating product.

Cause: There was an issue with one of the product-level constraints.

Action: Verify the product-level constraints are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01702: There was an error generating product path

Cause: The direct-access URL, non-proxied path to the product could not be obtained.

Action: Verify the product's webapp is running and correctly configured.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01801: Redirecting From Url: {0}

Cause: This is the URL before the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01802: Redirecting To Url: {0}

Cause: This is the URL after the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01803: Get Logical WebApp Info.

Cause: This is the information retrieved on the logical webapp.

Action: Registration may have failed. Try re-registering the products by running the configuration tool.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01804: Get Logical WebApp Info for workspace failed, using default.

Cause: The logical webapp information for Workspace could not be retrieved. Assuming the context is /workspace.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01805: Current Context Path: {0}

Cause: Indicates the current context path before the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01806: Redirect Context Path: /{0}

Cause: Indicates the context path after the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01807: Form Post Redirect

Cause: Indicates that redirect was handled by performing a form post.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01808: Send Redirect with Cookie {0}: {1}

Cause: Indicates the redirect was handled by a send redirect. Cookies are included in the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01809: The servlet failed, invalid token or url.

Cause: Indicates the URL or token may be invalide which caused the redirect to fail.

Action: Verify the URL is valid and user is properly provisioned.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01810: The servlet failed, bad redirect url or token: {0}

Cause: User is not authenticated.

Action: Verify the user is properly provisioned.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01811: Processed {0} urls to redirect using form post.

Cause: Indicates the URLs that must be redirected using a form post.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01812: The servlet failed to initialize the form post list: {0}

Cause: An error was encountered while attempting to retrieve information on the URLs.

Action: Verify in the web.xml under the redirect servlet node that the entries for FormPostList are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01813: Processed {0} parameters to omit from redirect.

Cause: Indicates the number of parameters that were found and should be omitted from the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01814: The servlet failed to initialize the param omit list: {0}

Cause: An error was encountered while attempting to retrieve the list of parameters to omit from the redirect.

Action: Verify in the web.xml under the redirect servlet node that the entries for ParamOmitList are valid.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01815: isFormPostUrl: {0} in {1} {2}

Cause: Indicates if the current URL should be redirected with a form post.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01816: isParamOmit: {0}

Cause: Indicates if the current parameter should be omitted from the redirect.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01901: The "{0}" persistence unit is already open

Cause: Indicates that while attempting to initialize the persistence, a previous attempt to terminate failed.

Action: This unexpected state should be reported, although the code will continue on and not attempt to initialize the persistence.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01902: Initializing persistence with the connection configured in "{0}"

Cause: Indicates that an attempt is being made to initialize the persistence with the connection information in the specified file.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01903: Loading the "{0}" persistence unit

Cause: Indicates that an attempt is being made to load the specified persistence unit.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01904: Unloading the "{0}" persistence unit

Cause: Indicates that an attempt is being made to unload the specified persistence unit.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01905: The "{0}" persistence unit is not open

Cause: Indicates that while attempting to terminate the persistence, a previous attempt to initialize failed.

Action: This unexpected state should be reported, although the code will continue on and not attempt to terminate the persistence.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01906: Started the migration

Cause: Indicates that the migration has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01907: Ended the migration

Cause: Indicates that the migration has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01908: Started the migration initialization

Cause: Indicates that the migration initialization has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01909: Ended the migration initialization

Cause: Indicates that the migration initialization has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01910: Started the migration termination

Cause: Indicates that the migration termination has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01911: Ended the migration termination

Cause: Indicates that the migration termination has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01912: Started the migration to Talleyrand

Cause: Indicates that the migration to the Talleyrand release has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01913: Couldn't find the user with identity "{0}"

Cause: Indicates that the identity of an existing user could not be located in the security system.

Action: The specified identity should be recorded to see why they are no longer in the security system (such as leaving the company, or a name change that affects the identity).
Level: 32

Type: ERROR

Impact:

EPMWKSP-01914: User={0}, Properties={1}

Cause: Indicates a user and their properties that are being migrated

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01915: Ended the migration to Talleyrand

Cause: Indicates that the migration to the Talleyrand release has ended.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01916: Started the connection acquisition for component type "{0}"

Cause: Indicates that the connection acquisition for the specified component type has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01917: JdbcDriver={0}

Cause: Indicates the JDBC driver that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01918: JdbcUrl={0}

Cause: Indicates the JDBC URL that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01919: JdbcUserName={0}

Cause: Indicates the JDBC username that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01920: JdbcPassword={0}

Cause: Indicates the JDBC password that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01921: JdbcDataSourceName={0}

Cause: Indicates the JDBC data source name that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01922: JndiName={0}

Cause: Indicates the JNDI name that is being used for the connection acquisition.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-01923: Ended the connection acquisition for component type "{0}"

Cause: Indicates that the connection acquisition for the specified component type has started.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02101: An empty search term was passed into Dynamic Help. The client search pages filter for this, so the submission may be from a source other than the search form.

Cause: An empty search term was passed in.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02102: No topics matched the search criteria.

Cause: Indicates that no topics matched the user's search criteria.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02103: Exact phrase search - add quotes to set term string as {0}

Cause: Indicates the user specified an exact phrase search.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02104: query string: {0}

Cause: Logs the search query string.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02105: parsed query: {0}

Cause: Logs the parsed query.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02106: Dynamic Help could not create the Lucene query parser:

Cause: Unknown cause.

Action: Verify that the Lucene search engine .jars are available.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02107: Version number not returned from Workspace. The path to the Lucene index thus cannot be resolved for module: {0}

Cause: Could not obtain the product's version number from the Workspace Registry for an unknown reason.

Action: Try the search again. If the same issue occurs, validate that the product is correctly registered with Workspace.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02108: adding Lucene index path {0}

Cause: Logging the search engine index location for the product.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02109: The Lucene index for the {0} module was not found in {1}

Cause: The search engine index for the product and locale may be missing, or the EPM_ORACLE_HOME system variable may not be properly set.

Action: If the logged index path begins with null, the EPM_ORACLE_HOME system variable is not set; if so, set it. Otherwise, check whether the search index for the product and locale is installed in the specified location.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02110: The Lucene search index could not be found, so no search was conducted.

Cause: No search engine indices were found.

Action: Check whether the search index for the product and locale is installed in the specified location. Also, make sure the EPM_ORACLE_HOME system variable is correctly set.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02111: parsed CJK query: {0}

Cause: Logging the parsed query for an Asian locale.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02112: Dynamic Help could not create the Lucene CJK query parser:

Cause: Unknown cause.

Action: Verify that the Lucene search engine .jars are available.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02113: I18N QueryFilter: {0}

Cause: Logging the query filter for an Asian locale.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02114: internationalized query: {0}

Cause: Logging the query for searches on multiple locales.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02115: Dynamic Help could not execute search

Cause: Search cannot be executed for an unknown reason.

Action: Try searching again. If the same issue occurs, a component help depends upon may be mis-configured or unavailable.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02201: Error in setting tools context ID data.

Cause: Could not obtain data from the Workspace Registry for the Reporting and Analysis Framework products' help.

Action: Validate that the Registry entries for the Reporting and Analysis Framework products are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02202: Error in setting IR help path.

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02203: Error in setting SQR help path.

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02204: Error in adding IR help paths:

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02205: Error in adding SQR help paths:

Cause: Unknown cause.

Action: Make sure that the Workspace Registry Dynamic Help entries for the tools context are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02206: Error in adding IR launch pages:

Cause: Unknown cause.

Action: No action is required; minor issue.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02207: Error in adding SQR launch pages:

Cause: Unknown cause.

Action: No action is required; minor issue.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02208: Workspace Registry returned no name for the product code {0}. Dynamic Help will display the product code as a fallback.

Cause: The product's displayName Workspace Registry attribute may not be set.

Action: Set the displayName attribute.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02301: UPK URL is an empty string.

Cause: The UPK URI obtained from Workspace is an empty string.

Action: Make sure that a valid UPK URI is set in the Workspace Server Settings dialog.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02302: UPK URL is null.

Cause: Workspace is indicating that UPK should be displayed, but the UPK URI value is not available.

Action: Make sure that a valid UPK URI is set in the Workspace Server Settings dialog.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02303: Exception trying to redirect to UPK:

Cause: For an unknown reason, an error occurred when forwarding to UPK.

Action: Verify that a valid UPK URI is set in the Workspace Server Settings dialog, then try accessing UPK again. If that does not work, as a workaround try accessing UPK through the UPK toolbar icon in help.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02401: Error testing for string in array:

Cause: Unknown cause.

Action: If help is not displaying in the correct locale, try accessing help again.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02501: There was an error getting version number for module {0}.

Cause: Could not obtain the product's version number from the Workspace Registry.

Action: Validate the product's Workspace Registry entry.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02502: There was an error in getting the product name for product {0}.

Cause: An Exception occurred for unknown reasons when help tried to obtain a product name from the Workspace Registry.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02503: The help system path is: {0}

Cause: Logging the path to the help system.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02504: There was an error setting the help system path for module: {0} guide: {1} locale: {2}

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02505: There was an error retrieving registered Workspace products.

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02506: Dynamic help could not create array of products and guides.

Cause: Unknown cause.

Action: Validate that the products' Workspace Registry entries are correctly defined.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02507: There was an error getting the launch page.

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

EPMWKSP-02508: There was an error getting the language for the help guide. Using English.

Cause: Unknown cause.

Action: No action is required.
Level: 32

Type: ERROR

Impact:

24 HELP-00001 to HELP-40001

HELP-00001: Error when creating HelpXmlPullParser due to XmlPullParserException for location: {0}

Cause: An XmlPullParserException was thrown while running _processDocument in the HelpXmlPullParser contructor.

Action: Verify that the location of the JavaHelp-format file exists.
Level: 1

Type: WARNING

Impact: Logging

HELP-00002: Error when creating HelpXmlPullParser due to IOException for location: {0}

Cause: An IOException was thrown when running Process Document in the HelpXmlPullParser contructor.

Action: Verify that the location of the JavaHelp-format file exists
Level: 1

Type: WARNING

Impact: Logging

HELP-00003: Error when executing search in SearchModel.

Cause: SearchModel threw a SearchException when starting the search.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

HELP-00004: View passed to SearchModel does not contain data in QueryHandler format.

Cause: The view object passed to SearchModel did not contain data in the expected QueryHandler format.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-00005: Unexpected exception occurring in Help Share.

Cause: An unexpected exception occurred in the code.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-00006: Error when parsing document using XML parser

Cause: An XMLParseException was thrown when processing the XML document.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

HELP-10001: Unexpected exception occurring in OHW Share.

Cause: An unexpected exception occurred in the code.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10002: Adding book {0} to library fails because of LibraryException.

Cause: A LibraryException was thrown.

Action: Log a bug against the application.
Level: 1

Type: WARNING

Impact: Logging

HELP-10003: encountering severe exception when parsing locale from file

Cause: A ConfigParseException was thrown when creating PerLocaleInfo from file.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10004: class name attribute is required on [localeFromProvider]

Cause: The class attribute was missing for the localeFromProvider tag.

Action: Add the class name attribute.
Level: 1

Type: ERROR

Impact: Logging

HELP-10005: error in loading per locale provider {0}

Cause: An unexpected exception was caught when loading the per locale provider.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10006: unrecognized tag {0} in {1} section

Cause: There was an unrecognized tag in the configuration section.

Action: Check the configuration file for unrecognized tags in the configuration section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10007: no [locale] section in [locales]

Cause: The required [locale] section was missing in [locales].

Action: Check the help configuration file to ensure that [locales] has at least one child [locale].
Level: 1

Type: ERROR

Impact: Logging

HELP-10008: error in loading custom protocol class: {0}

Cause: An unexpected exception was caught when loading the Custom Protocol class.

Action: Verify that the Custom Protocol class is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10009: error in loading branding provider: {0}

Cause: An unexpected exception was caught when loading the Branding Provider class.

Action: Verify that the Branding Provider class is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10010: configuration file is empty

Cause: The Help configuration file was empty.

Action: Verify that the Help configuration file exists and contains content.
Level: 1

Type: ERROR

Impact: Logging

HELP-10011: {0} attribute is required on [helpConfiguration]

Cause: The version attribute was not available on the [helpConfiguration] section.

Action: Add the version attribute to the [helpConfiguration] section of the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10012: Version {0} is not a recognized version. Accepted versions are: {1}

Cause: The version provided was not recognized as an accepted version.

Action: Verify that an accepted version is used in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10013: duplicate {0} section in the Help configuration file

Cause: There was a duplicate section in the Help configuration file.

Action: Check the Help configuration file for duplicate sections and remove them.
Level: 1

Type: ERROR

Impact: Logging

HELP-10014: tag {0} is not recognized

Cause: Unrecognized tags were found in the Help configuration file.

Action: Remove all unrecognized tags from the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10015: no {0} section found

Cause: A required section was not found in the Help configuration file.

Action: Add the required section to the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10016: Expecting: {0}. Finding: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10017: The {0} attribute is missing in [customProtocol].

Cause: The attribute was missing in the Custom Protocol definition.

Action: Add the required attribute to the Custom Protocol definition.
Level: 1

Type: ERROR

Impact: Logging

HELP-10018: The attribute {0} is missing in [alias].

Cause: The required attribute was missing from the navigator alias definition.

Action: Add the required attribute to the navigator alias definition.
Level: 1

Type: ERROR

Impact: Logging

HELP-10019: Text or image source attribute is required in [branding].

Cause: The text or image attribute was missing from the [branding] section of the Help configuration file.

Action: Ensure that the text or image attribute is non-empty and points to a valid location.
Level: 1

Type: ERROR

Impact: Logging

HELP-10020: The {0} attribute on the [branding] tag cannot be empty.

Cause: The required attribute was missing from the [branding] section.

Action: Add the required attribute to the [branding] section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10021: Text key or image source key attribute is required in [brandingFromResource].

Cause: The text key or image source attribute was missing from [brandingFromResource].

Action: Ensure that the text or image attribute is non-empty and points to a valid location.
Level: 1

Type: ERROR

Impact: Logging

HELP-10022: The {0} attribute is required on [brandingFromResource].

Cause: The required attribute was missing from the [brandingFromResource] section.

Action: Add the required attribute to the [brandingFromResource] section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10023: The {0} attribute is required on [brandingFromProvider]

Cause: The required attribute was missing from the [brandingFromProvider] section.

Action: Add the required attribute to the [brandingFromProvider] section.
Level: 1

Type: ERROR

Impact: Logging

HELP-10024: error finding configuration file at: {0}

Cause: The configuration file was not found at the specified location.

Action: Verify that the location of the configuration file is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10025: The view {0} with base path {1} passed to the SearchDispatcher does not contain a valid QueryHandler.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10026: trying to access site with invalid path: {0}

Cause: There was an attempt to access a file through an invalid path.

Action: Verify that the file path is correct.
Level: 1

Type: ERROR

Impact: Logging

HELP-10027: missing or empty {0} attribute in [localeFromFile]

Cause: A required attribute was missing or empty in the [localeFromFile] section.

Action: Add the required attribute to the Help configuartion file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10028: Location of locale file is not valid.

Cause: The location of the locale file was not valid.

Action: Supply a valid location for the locale file in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10029: Locale file is empty.

Cause: The locale file has no content.

Action: Supply a valid locale file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10030: The locale file cannot be found.

Cause: The locale file was not available at the location specified in the Help configuration file.

Action: Verify that the locale file exists at the location specified in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10031: The {0} locale is not allowed without a corresponding country section.

Cause: The locale was used without an accompanying country section.

Action: Add a country section for this locale.
Level: 1

Type: ERROR

Impact: Logging

HELP-10032: unrecognized book: {0}

Cause: An unrecognized book tag was found in the Help configuration file.

Action: Check the Help configuartion file for helpSet or helpBook tags and remove or correct the unrecognized book tag.
Level: 1

Type: ERROR

Impact: Logging

HELP-10033: no books in [books] section

Cause: There was no book child in the books parent tag in the Help configuration file.

Action: Add a book child element to the books parent tag.
Level: 1

Type: ERROR

Impact: Logging

HELP-10034: Attribute {0} is missing in helpSet.

Cause: The required attribute was missing from the helpSet tag.

Action: Add the required attribute to the helpSet tag.
Level: 1

Type: ERROR

Impact: Logging

HELP-10035: duplicate helpSet or helpBook {0} : {1}

Cause: A duplicate helpSet or helpBook attribute was encountered.

Action: Remove the duplicate entry from the helpset configuartion file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10036: Location of {0} is not valid.

Cause: The location of the file was not valid.

Action: Ensure that the location of the file is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-10037: Attribute {0} is missing in helpBook.

Cause: The required attribute was missing from the helpBook tag.

Action: Add the required attribute to the helpBook tag in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10038: Attribute {0} is missing in contentLocation tag.

Cause: The required attribute was missing from the contentLocation tag.

Action: Add the required attribute to the contentLocation tag in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10039: Content location is not valid.

Cause: The content location path was invalid.

Action: Ensure that the Help configuration file contains a valid content location base URI.
Level: 1

Type: ERROR

Impact: Logging

HELP-10040: duplicate {0} attribute {1} for content location

Cause: There was a duplicate attribute for the content location.

Action: Remove the duplicate entry from the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10041: Content location is missing or malformed.

Cause: The content location was missing or malformed

Action: Verify that the content location path exists, and that it is a valid path.
Level: 1

Type: ERROR

Impact: Logging

HELP-10042: no known locales

Cause: There was no known locale information available.

Action: Verify that the Help configuration file contains a known locale.
Level: 1

Type: ERROR

Impact: Logging

HELP-10043: CustomProtocolName and converter must not be null.

Cause: The custom protocol name and the converter were not valid.

Action: Verify that the custom protocol name and the converter are not null in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-10044: PerLocaleConfiguration cannot be used in unloaded state.

Cause: The PerLocaleConfiguration was not loaded into memory before an attempt was made to use it.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10045: error creating book information for id: {0}

Cause: There was an error while creating the book information.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10046: passed null per locale configuration

Cause: A null PerLocaleConfiguartion object was passed.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10047: calling init method for a second time in navigator manager

Cause: The init method was called a second time in AbstractNavigatorManager.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10048: FastMessageFormat supports only numeric arguments.

Cause: The FastMessageFormat method was passed non-numeric arguments.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10049: end of pattern symbol not found

Cause: The end of pattern symbol was not found.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10050: FastMessageFormat: empty argument - {}.

Cause: An empty argument was passed to FastMessageFormat.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10051: The operation {0} is not supported.

Cause: The execution of this method was not supported.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-10052: Search for {0} yielding {1} number of results.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

HELP-10053: Search for {0} yields no results.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

HELP-10054: invalid topic id link: {0} reported from {1}

Cause: An invalid topic id was found.

Action: Review the help topic map file and the topic content file and correct the invalid topic id.
Level: 1

Type: WARNING

Impact: Logging

HELP-10055: trying to access invalid topic id {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10056: Topic {0} does not have a target that can be followed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10057: discovery of a null topic in the Help files

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-10058: (Debug Mode: {0} Missing Helpsets)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20001: cannot find global configuration with URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20002: cannot find required servlet context parameter: {0}

Cause: The required servlet context parameter was not found.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20003: critical error in OHW configuration

Cause: There was a critical error in the Help configuration file.

Action: Verify the correctness of the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-20004: unrecognized view type {0} is ignored

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20005: cannot instantiate navigator of type: {0}

Cause: The navigator could not be instantiated.

Action: Verify the correctness of this navigator type in the Help configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-20006: cannot update auto sync component

Cause: There was a failure when updating the auto sync UI component.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20007: no topic id or topic file for linkHelp=false

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20008: failure when creating tree model in Rich TOC Navigator

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20009: failure when trying to index tree model for TOC navigator

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-20010: cannot find required ohwConfigFileURL

Cause: OHW Help Provider requires an OHW configuration file, but this file was not found.

Action: Ensure that the path points to a valid OHW configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-20011: unable to create global configuration

Cause: The global configuration object could not be created.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20012: unexpected exception when trying to get embedded content for Rich Help Provider

Cause: An unexpected exception was caught when trying to get the embedded content for Rich Help Provider.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-20013: The file protocol suggests that the OHW Config file is not located on local file system.

Cause: OHW Config file is not located on local file system.

Action: Please make sure that the OHW Config file is located on local file system.
Level: 1

Type: WARNING

Impact: Logging

HELP-30001: cannot find required servlet init parameter {0}

Cause: The required init parameter for the Help servlet was not found.

Action: Check the Help servlet definition in the web.xml file of the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-30002: critical error in OHW configuration: {0}

Cause: There was a critical error in the OHW configuration file that caused a MalformedURLException.

Action: Correct the OHW configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-30003: Critical error in OHW configuration. Config URL: {0}

Cause: There was a critical error in the OHW configuration file.

Action: Correct the OHW configuration file.
Level: 1

Type: ERROR

Impact: Logging

HELP-30004: failing to load UIX file

Cause: There was a failure when loading the UIX file.

Action: Ensure that the UIX file is valid.
Level: 1

Type: ERROR

Impact: Logging

HELP-30005: failure to parse {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-30006: cannot find UIX path {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-30007: OHW is encountering an unexpected error.

Cause: There was an unexpected error in OHW-UIX.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-30008: cannot instantiate navigator of type {0}

Cause: The specified navigator could not be instantiated.

Action: Log a bug against the application.
Level: 1

Type: ERROR

Impact: Logging

HELP-30009: cannot load class alias of type {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

HELP-40001: error when loading icon: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

25 J2EE HTTPC-00004 to J2EE HTTPC-12011

J2EE HTTPC-00004: Unable to parse header value: name={0}, value="{1}".

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-00015: Unable to read response for method={0}, path+query="{1}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-00016: Unable to read response for input stream hashcode={0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-00017: Socks: V4 request failure: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01000: Unable to register built-in AuthenticationScheme {0}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01001: Unable to register AuthenticationScheme {0} for scheme name {1}.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01002: Unable to add NTLM credentials. The AuthorizationHandler does not implement the AuthenticationSchemeRegistryHolder interface.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01004: Unable to add NTLM credentials. NTLM AuthenticationScheme was not found in the AuthorizationHandler''s AuthenticationSchemeRegistry.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01010: AuthM: Handling deferred authorization challenge.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01011: AuthM: Sending request with Authorization = "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01012: AuthM: Sending request with Proxy-Authorization = "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01013: AuthM: Preemptively sending Proxy-Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01014: AuthM: Preemptively sending Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01015: AuthM: Server refused the given Authorization info {0} times, aborting request.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01016: AuthM: Status {0} not handling - request has an output stream.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01017: AuthM: Deferring handling of status {0} due to use of an output stream.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01018: AuthM: Handling status: {0} "{1}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01019: AuthM: Resending request with Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01020: AuthM: Resending request with Proxy-Authorization "{0}".

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01021: AuthM: Not handling status {0} because finding no Authorization information.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01022: AuthM: Parsing {0} challenges:

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-01023: AuthM: Challenge {0}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02001: ContentEncMod: pushing gzip-input-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02002: ContentEncMod: pushing inflater-input-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02003: ContentEncMod: pushing uncompress-input-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02004: ContentEncMod: ignoring "identity" token

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-02005: ContentEncMod: Unknown content encoding "{0}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-03000: ContentMD5Mod: Received digest: "{0}" - pushing md5-check-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-03001: ContentMD5Mod: Expecting digest in trailer - pushing md5-check-stream

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-03003: ContentMD5Mod: successfully verifying hash

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04006: Cookie: Bad Set-Cookie header: "{0}". Finding no equal sign(=) for token starting at position {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04007: Cookie: Ignoring cookie: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04008: Cookie: Bad Set-Cookie header: "{0}", invalid date "{1}"

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04009: Bad Set-Cookie header: ''{0}'', Max-Age ''{1}'' is negative.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04011: Cookie: Bad Set-Cookie header: "{0}", domain is empty - ignoring domain.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04012: Cookie: Bad Set-Cookie header: "{0}", current domain "{1}" does not match given parsed "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04013: Cookie: Bad Set-Cookie header: "{0}", domain attribute "{1}" is not .local and does not have at least two dots.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04014: Cookie: Bad Set-Cookie header: "{0}", domain attribute "{1}" is more than one level below current domain {2}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04015: Cookie2: Bad Set-Cookie2 header: "{0}", path "{1}" is not a prefix of the request URI "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04016: Cookie2: Bad Set-Cookie2 header: "{0}", domain "{1}" is not ".local" and does not contain two "."s.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04017: Cookie2: Bad Set-Cookie2 header: "{0}", domain "{1}" does not match current host "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04018: Cookie2: Bad Set-Cookie2 header: "{0}", domain "{1}" is more than one dot(.) away from host "{2}".

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04019: Cookie2: Bad Set-Cookie2 header: "{0}", port list does not include current port {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-04020: Cookie: TLD, "{0}", does not start with ".", so it was removed from extendedTLDs.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-05000: Not handling status {0} {1} because exceeding maximum number of retries.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-05001: IOE closing InputStream for status 411: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-09000: HTTPConnection instance {0} has chunking enabled: {1}.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-09001: HTTPConnection instance {0} has chunk size set to {1}.

Cause:

Action:
Level: 32

Type: TRACE

Impact: Requests/Responses

J2EE HTTPC-12000: Setting Maximum Authorization retries to {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12001: ''{0}'' is enabled

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12002: ''{0}'' is disabled

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12003: Version: {0}

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12004: Enabling deferred handling of responses to streamed requests.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12005: Setting Socket Idle Timeout to {0} seconds.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12006: Adding module {0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12007: Adding module {0} to {1} list.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12008: Removing module {0} from {1} list.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12009: Default HTTP proxy set to {0}:{1,number,0}.

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12010: Setting Socket Connection Timeout to {0} milliseconds

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

J2EE HTTPC-12011: Setting Socket Read Timeout to {0} milliseconds

Cause:

Action:
Level: 16

Type: NOTIFICATION

Impact: Requests/Responses

26 J2EE JMX-46000 to J2EE JMX-47006

J2EE JMX-46000: It is not possible to start a state-manageable instance while it is being stopped.

Cause: A resource that was being stopped was asked to start.

Action: Wait until the resource is fully stopped before attempting to restart it.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46001: A state-manageable object is not started. The reason is "{0}".

Cause: A resource could not be started.

Action: Correct the root cause cited in the generated message.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46002: It is not possible to stop a state-manageable instance while it is being started.

Cause: A resource that was being started was asked to stop.

Action: Wait until the resource is fully started before attempting to stop it.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46003: A state-manageable object is not stopped. The reason is "{0}".

Cause: A resource could not be stopped.

Action: Correct the root cause cited in the generated message.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46004: The Notifications and Notification annotations cannot be used together.

Cause: An MBean interface was annotated with both the @Notification and @Notifications annotations.

Action: Use either @Notification or @Notifications to annotate the MBean interface, but not both.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46005: The Notifications and Notification annotations cannot be used on both the management and implementation classes.

Cause: The @Notification or @Notifications annotation was used on both the MBean interface and MBean implementation class. Only the MBean interface should be annotated with @Notification or @Notifications.

Action: Remove the conflicting annotation from the implementation class.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46006: Could not find MBean operation "{0}" for MBean registered under "{1}" and implemented by "{2}"

Cause: Operation signature might not match

Action: Verify operation signature against MBean metadata or MBean implementation class
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46007: Error getting MBeanServer for Config MBean "{0}" implemented by "{1}"

Cause: Internal error.

Action: No action is required. The default MBeanServer association will be used.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46008: Error initializing the JMX FRamework SPI "{0}"

Cause: Internal error. See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46009: Error loading the JMX FRamework SPI "{0}"

Cause: Internal error. See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46010: JMX Portable Framework initialized with platform SPI "{0}"

Cause: The message is informational only.

Action: No action is required.
Level: 1

Type: TRACE

Impact: Programmatic

J2EE JMX-46011: The @Inject annotation can be used only on a method that exposes a single parameter whose type is the type of the resource to be injected.

Cause: The JMX MBean @Inject annotation was used on a method that did not have a single parameter with the proper type.

Action: Change the associated MBean method to have a single parameter with the proper type or replace the @Inject annotation.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46012: Error registering MBean whose ObjectName is "{0}" and implementation class is "{1}"

Cause: See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46013: The {0} argument cannot be null.

Cause: An argument was passed a null value, which is invalid. The name of the argument is specified as part of the generated message.

Action: Change the argument value to be a valid non-null value.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46014: A notification listener for MBean "{0}" cannot be added.

Cause: The MBean did not declare that it sends notifications.

Action: Change the MBean code to declare that it sends notifications or remove the code that attempts to register a notification listener for the MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46015: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on attribute "{2}" of MBean "{3}" cannot be found.

Cause: The resource defined by the Description annotation that was associated with an MBean attribute was missing. The generated message specified the MBean, attribute, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46016: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on operation "{2}" of MBean "{3}" cannot be found.

Cause: The resource defined by a Description annotation that was associated with an MBean operation was missing. The generated message specified the MBean, operation, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46017: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on parameter "{2}" of operation "{3}" of MBean "{4}" cannot be found.

Cause: The resource defined by a Description annotation that was associated with an MBean operation parameter was missing. The generated message specified the MBean, operation, parameter name, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46018: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on MBean "{2}" cannot be found.

Cause: The resource defined by a Description annotation that was associated with an MBean interface was missing. The generated message specified the MBean, resource key and resource bundle.

Action: Ensure that the Description annotation includes the correct resourceBundleBaseName key and that the default resource bundle exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46019: The resource with key "{0}" and bundle "{1}" declared in the Description annotation on feature "{2}" of MBean "{3}" cannot be found.

Cause: A resource that was defined in one of the MBean descriptors properties (descriptionResourceKey or descriptionResourceBundleBaseName) was missing. The generated message specified the MBean, resource key and resource bundle.

Action: Add the resource or change the MBean descriptor property.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JMX-46020: No PersistenceManager is declared for MBean "{0}".

Cause: The PersistenceManagers were missing.

Action: When PMCompositeConfigMBeanSupport is used, specify a shared PersistenceManager or specify individual PersistenceManagers for the two config files (use injection-name 'file1' and 'file2' in mbeans.xml).
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46021: The Persistable for MBean "{0}" is not defined.

Cause: The expected Persistable for the MBean was missing.

Action: Provide the Persistable for the MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46022: A resource bundle name must be specified in order to use message localization methods.

Cause: The resource bundle name was missing.

Action: Define the resource bundle name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46023: A shared PersistenceManager and an individual PersistenceManager cannot both be declared for MBean "{0}".

Cause: Both a shared and an individual PersistenceManager were declared for the MBean.

Action: When PMCompositeConfigMBeanSupport is used, specify either one shared persistence manager with no injection name, or two persistence managers with injection names "file1" and "file2", in mbeans.xml.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46024: At least one configuration object used by MBean "{0}" for type "{1}" is not registered.

Cause: At least one of the configuration objects used by a Composite ConfigMBean was not registered.

Action: Register the appropriate configuration object.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46025: The type "{1}" used for MBean "{0}" is not valid for either configuration object "{2}" or "{3}".

Cause: The type used for a configuration object for the MBean was not valid.

Action: Use the correct type for the configuration object.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46026: The configuration file with injection name "{1}" for MBean "{0}" cannot be found.

Cause: The configuration file is missing or the injection name is incorrect.

Action: Verify that the injection name and the configuration file path are properly specified.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46027: The configuration at URI "{0}" cannot be loaded.

Cause: The value for location in the configuration file was invalid.

Action: Verify that the value of location in the configuration file is properly specified.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46028: MBean "{0}" cannot be registered,

Cause: An MBean was already registered with the same name. It should have been removed when the application was either stopped or undeployed.

Action: Examine and correct the errors that resulted when the application was stopped or undeployed, and repeat the stop or undeployment operation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46029: The configuration file "{0}" for MBean "{1}" cannot be found.

Cause: The value for location in the configuration file was invalid.

Action: Verify that the value of location in the configuration file is properly specified.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46030: failure to register MBean "{0}" during application initialization.

Cause: Registering the MBean during application initialization caused an error.

Action: Use the information from the exception stack trace to determine the cause of the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46031: failure to unregister MBean "{0}" during application shutdown.

Cause: Unregistering the MBean during application shutdown caused an error.

Action: Use the information from the exception stack trace to determine the cause of the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46032: The RequiredApplicationPermission or RequiredSystemPermission annotation is incorrect.

Cause: The RequiredApplicationPermission or RequiredSystemPermission annotation did not specify a nonempty action array.

Action: Specify a nonempty action array.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46033: The Description annotation on method "{0}" of class "{1}" is incorrect.

Cause: The Description annotation resourceKey was null.

Action: Ensure that the resourceKey for the Description annotation is not null for the method cited in the error message.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46034: No annotation should be put on attribute mutator parameter "{0}".

Cause: The mutator parameter for an attribute has an annotation.

Action: Remove all annotation from the attribute's mutator parameter.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46035: The Description annotations on the mutator and accessor of attribute "{0}" are in conflict.

Cause: Both the mutator and the accessor were annotated. Ideally, only the mutator should be annotated. The message key and the message bundle were not identical on both the mutator and the accessor, and must be if both are annotated.

Action: Either remove the annotation on the accessor or ensure that the message key and the message bundle are identical on both the accessor and the mutator.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46036: OpenType "{0}" cannot be converted to a Class<?> instance.

Cause: The OpenType was not an instance of Class or ParameterizedType or GenericArrayType, and it must be.

Action: Ensure that the OpenType is an instance of Class or ParameterizedType or GenericArrayType.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46037: The class "{0}" cannot be converted to OpenType.

Cause: The custom type was wrong.

Action: Use a custom type that can be converted to OpenType.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46038: There is an OpenType conversion error "{0}".

Cause: An OpenType conversion resulted in an error.

Action: See the information cited within the error message for details about the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46039: The ModelMBeanInfo for class "{0}" does not have a Descriptor.

Cause: The ModelMBeanInfo did not have a Descriptor.

Action: Add a Descriptor to the ModelMBeanInfo.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46040: A key for the resource bundle "{0}" cannot be null.

Cause: The key for the message was null.

Action: Provide a resource bundle key that is not null.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46041: The resource for bundle "{0}" with key "{1}" cannot be found.

Cause: There was no resource found in the resource bundle for the given key.

Action: Add the key to the resource bundle.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46042: The resource in bundle "{0}" for key "{1}" is not a String.

Cause: The resource found for the given key was not a String.

Action: Ensure that the resource is a String.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46043: The JMX Config Session instance passed to the Config MBean Factory is null.

Cause: The JMX Config Session instance passed to the Config MBean Factory was null.

Action: Associate the MBean creation with a valid JMX Config Session instance.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46044: Resource bundle "{0}" cannot be found.

Cause: The resource bundlle was missing.

Action: Provide the resource bundle.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46045: An error occurred while processing MBeanInfo for MBean "{0}".

Cause: The MBeanInfo was not correct.

Action: Use the error information to correct the MBeanInfo.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46046: The ConfigMBean PersistenceManager is not of type DualDataSourcePersistenceManager.

Cause: The PersistenceManager was not of type DualDataSourcePersistenceManager.

Action: Correct the type of the PersistenceManager.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46047: The method "{0}" required by DualDataSourcePersistenceManager cannot be found.

Cause: The required method was missing.

Action: Add the method to the MBean.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46200: federation error: "{0}"

Cause: A federation operation resulted in an error from the federated target.

Action: See the remote exception cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46201: The federation namespace "{0}" cannot be found.

Cause: A Namespace that did not exist was specified during a federation operation.

Action: Use a valid federated namespace name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46202: The domain of ObjectName "{0}" does not start with "{1}".

Cause: An improper domain was used during federation ObjectName processing.

Action: Use the expected federation domain: oracle.as.jmx.federation
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46203: federation namespace handler registration error: "{0}".

Cause: An error occurred while registering a new federation namespace handler.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46204: namespace handler unregistration error: "{0}".

Cause: An error occurred while unregistering a federation namespace handler.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46205: error closing connection for "{0}": "{1}".

Cause: An error occurred while closing a federation JMX connector.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46206: The "{0}" parameter cannot be null.

Cause: A required method parameter was null.

Action: Provide a non-null parameter to the method.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46207: Removing the federation namespace from "{0}" results in an invalid ObjectName.

Cause: Removing the federation prefix resulted in an invalid ObjectName.

Action: Correct the specified ObjectName.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46208: A federated object is not serializable.

Cause: A nonserializable object was encountered during federation serialization.

Action: Make the object serializable.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46209: A federated object is not serializable because a class cannot be found: "{0}".

Cause: A class needed by federation serialization cannot be found.

Action: Verify that the class can be found using the class path.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46210: The object that is being federated is not serializable: "{0}".

Cause: A nonserializable object was encountered during federation serialization.

Action: Make the object serializable.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46211: The FederationMBeanServerImpl constructor is being called incorrectly.

Cause: The constructor for FederationMBeanServerImpl was called more than once, which is not allowed.

Action: Call the constructor for FederationMBeanServerImpl only once.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46212: The operation "{0}" is not supported for namespace "{1}".

Cause: The operation that was invoked is not supported by the namespace.

Action: Change the calling code so that the operation is not invoked.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46213: The remote namespace handler constructor is being called incorrectly.

Cause: The connection information for the remote MBean server was not correct.

Action: Correct the connection information.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46214: Namespace "{0}" cannot be found.

Cause: A namespace that did not exist was specified during a federation operation.

Action: Use a valid federated namespace name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46215: ObjectName "{0}" is invalid.

Cause: An ObjectName was created with an invalid constructor argument.

Action: Correct the ObjectName constructor argument.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46216: Error unregistering MBean whose ObjectName is "{0}" and implementation class is "{1}"

Cause: See nested exception.

Action: Based on nested exception root cause.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46218: An error occurred while persisting the state for the Config MBean registered under "{0}" and implemented by "{1}"

Cause: See associated exception

Action: Fix issue described by the associated exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46219: No registered mapper can convert: "{0}" to an Open MBean Type

Cause: Needed mapper could not be found

Action: Add the required mapper
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46220: Cannot map nongeneric collections to Open MBean Type: "{0}"

Cause: Cannot map nongeneric collections to Open MBean Type

Action: Fix collection type
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46221: JMXFrameworkStateFactory is not initialized. JMXStateFactoryImpl.init() should have been called prior to calling this method

Cause: JMXFrameworkStateFactory in not initialized.

Action: JMXStateFactoryImpl.init() should have been called prior to calling this method.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46222: No such property "{0}" in "{1}"

Cause: Attempted to set a nonexistent property.

Action: Check the name of the property begin set.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46223: Failed to set property "{0}" to value "{1}".

Cause: Could not set the given property.

Action: Check the exception.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46224: No setter for property.

Cause: Could not find the necessary setter method.

Action: Add the needed setter method.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46225: #params for setter != 1.

Cause: Invalid number of parameter for setter method.

Action: Correct the parameter list of the setter call.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46226: Conversion to type "{0}" failed.

Cause: Type conversion failed.

Action: Check the exception.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46227: Cannot find the Config MBeans declaration file {0} in the application.

Cause: The required META-INF/mbeans.xml file is missing from the application.

Action: Add the META-INF/mbeans.xml in the application
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46228: Error processing MBeans associated with mbeans.xml located at: "{0}"

Cause: Format issue, or missing class

Action: Check the exception.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46229: Only one of two security annotations OperationRequiredGlobalSecurityRole and OperationRequiredCustomSecurityGroup can be applied to MBean operation {0}.{1}

Cause: Two security annotations on the MBean operation

Action: Apply only one or none security annotation the the MBean operation
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46230: The following security Annotation(s) cannot be applied to MBean operation {0}.{1}: {2}

Cause: Invalid security annotation(s) on MBean operation

Action: Remove invalid security annotation(s)
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46231: Only one of two security annotations AttributeGetterRequiredGlobalSecurityRole and AttributeGetterRequiredCustomSecurityGroup can be applied to MBean Attribute Getter {0}.{1}

Cause: Two security annotations on the MBean attribute getter

Action: Apply only one or none security annotations to the MBean attribute getter.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46232: The following security Annotation(s) cannot be applied to MBean attribute getter {0}.{1}: {2}

Cause: Invalid security annotation(s) on MBean attribute getter

Action: Remove invalid security annotation(s)
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46233: Only one of two security annotations AttributeSetterRequiredGlobalSecurityRole and AttributeSetterRequiredCustomSecurityGroup can be applied to MBean Attribute Setter {0}.{1}

Cause: Two security annotations on the MBean attribute setter

Action: Apply only one or none security annotations to the MBean attribute setter.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46234: The following security Annotation(s) cannot be applied to MBean attribute setter {0}.{1}: {2}

Cause: Invalid security annotation(s) on MBean attribute setter

Action: Remove invalid security annotation(s)
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46235: Only one of two security annotations MBeanRequiredGlobalSecurityRole and MBeanRequiredCustomSecurityGroup can be applied to MBean interface {0}

Cause: Two security annotations on the MBean interface

Action: Apply only one or none security annotations to the MBean interface.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46236: Do not know how to map nonserializable type: "{0}" to Open MBean Type.

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46237: Error while executing ServletContextListener initialization

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46238: Cannot map nonserializable type "{0}" to Open MBean Type for mbean interface {1}, attribute {2}.

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46239: Cannot map nonserializable type "{0}" to Open MBean Type for mbean interface {1}, the return type of operation {2} .

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46240: Cannot map nonserializable type "{0}" to Open MBean Type for mbean interface {1}, parameter {2} of operation {3}.

Cause: A type that does not implement Serializable cannot be mapped by the jmx framework

Action: Implement Serializable
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46241: Error while delivering JMX notification "{0}" to listener "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46242: Cannot load class "{0}" for MBean operation "{1}" using ClassLoader "{2}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46243: Cannot find method "{0}" for attribute "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46244: Error converting annotation "{0}" to descriptor. Could not get value for "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46245: Error creating ConstraintValidator "{0}" with ClassLoader "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46246: Error mapping java array or collection of type "{0}" to open type array. Individual element mapping resolved to "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46247: Cannot load class "{0}" using ClassLoader "{1}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46248: Error mapping java Map of type "{0}" to open type TabularData. Key mapping resolved to "{1}", and Value mapping resolved to "{2}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46249: Error mapping java Map entry of TabularType "{0}". Mapped Key instance is {1}", and mapped Value istance is "{2}"

Cause: See embedded root exception

Action: Fix issue related with embedded root exception
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46250: Internal error: the setPersistable() invoked twice on config mbean

Cause: internal error

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Programmatic

J2EE JMX-46251: The MBean is no longer registered so no notification is delivered.

Cause: The mbean has been unregistered.

Action: The notification is no longer delivered.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46252: Error during {0} for MBean {1}

Cause: See nested exception for root cause.

Action: Fix root cause, to ensure that the MBean gets registered.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46253: Fail to get MBeanCustomSecurityPlugin instance from factory {0}

Cause: See nested exception for root cause.

Action: Fix root cause, to ensure that factory can return right MBeanCustomSecurityPlugin instance.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46300: Class "{0}" is not compatible with the annotation on method "{1}" of class "{2}".

Cause: When a MinValue, MaxValue or LegalValues annotation was used, the class that the annotation applied to did not have either a public static valueOf(String) method or a public constructor with only a String parameter.

Action: Change the class that the MinValue, MaxValue or LegalValues annotation applies to so that it either has a public static valueOf(String) method or a public constructor with only a String parameter.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46301: An object cannot be obtained for the minimum value for "{0}" for method "{1}" of class "{2}".

Cause: An instance of the class that a MinValue annotation applied to was not constructed. The associated IllegalArgumentException indicates the reason.

Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46302: An object cannot be obtained for the maximum value for "{0}" for method "{1}" of class "{2}".

Cause: An instance of the class that a MaxValue annotation applied to was not constructed. The associated IllegalArgumentException indicates the reason.

Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46303: An object cannot be obtained for the valid value "{0}" for method "{1}" of class "{2}".

Cause: An instance of the class that a LegalValues annotation applied to was not be constructed. The associated IllegalArgumentException indicates the reason.

Action: Examine the associated IllegalArgumentException information to determine what action to take.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46304: The parameters being validated for method "{0}" of class "{1}" based on annotations do not match the method parameter types.

Cause: A constraint declared using the MinValue, MaxValue or LegalValues annotation was being enforced, but the number of arguments passed to the method was wrong.

Action: Change the code that has the call to the method to have the correct number of arguments.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46305: Parameter "{0}" of method "{1}" of class "{2}" is less than the MinValue.

Cause: The value for an attribute or parameter that was annotated with the MinValue annotation failed the minimum value constraint test.

Action: Change the value so that it does not fail the minimum value constraint test or change the annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46306: Parameter "{0}" of method "{1}" of class "{2}" is greater than the MaxValue.

Cause: The value for an attribute or parameter that was annotated with the MaxValue annotation failed the maximum value constraint test.

Action: Change the value so that it does not fail the maximum value constraint test or change the annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46307: Parameter "{0}" of method "{1}" of class "{2}" cannot be compared to the MinValue annotation value.

Cause: The class to which the MinValue annotation applied did not implement the Comparable interface.

Action: Use a different class that implements the Comparable interface or modify the existing class so that it implements the Comparable interface.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46308: Parameter "{0}" of method "{1}" of class "{2}" cannot be compared to the MaxValue annotation value.

Cause: The class to which the MaxValue annotation applied did not implement the Comparable interface.

Action: Use a different class that implements the Comparable interface or modify the existing class so that it implements the Comparable interface.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46309: Parameter "{0}" of method "{1}" of class "{2}" does not match any value in the LegalValues annotation.

Cause: The value for an attribute or parameter that was annotated with the LegalValues annotation did not match any valid value.

Action: Change the value so that it is one of the valid values, or change the annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46310: Parameter "{0}" of method "{1}" of class "{2}" violates the constraint that the LegalValues annotation cannot be used with a MinValue or MaxValue annotation.

Cause: The LegalValues annotation was used at the same location with either a MaxValue or MinValue annotation.

Action: Either use the LegalValues annotation, or use the MaxValue or MinValue annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46311: The value of the MinValue annotation is greater than the value of the MaxValue annotation for parameter "{0}" of method "{1}" of class "{2}".

Cause: The value used for the MinValue annotation was greater than the value used for the MaxValue annotation.

Action: Change the annotations so that the value used for MinValue annotation is less than the value used for the MaxValue annotation.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46312: The type used for parameter "{0}" of method "{1}" of class "{2}" is improper.

Cause: The value passed to an attribute or method parameter that was annotated with the MinValue or MaxValue annotation was not compared with an instance of the class used for the annotation because the type of the value was incorrect.

Action: Use the correct value for the attribute or method call, or change the annotation type.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46313: The delegate MBeanServerConnection cannot be null.

Cause: A PatternBaseDelegationHandler was being constructed without the required MBeanServerConnection argument.

Action: Change the code to supply the required MBeanServerConnection argument.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46314: No handler for ObjectName "{0}" is registered.

Cause: No handler existed for the object name being used.

Action: Register a handler that is appropriate for the object name that is used, or use a different object name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46315: There is no registered handler to instantiate class "{0}".

Cause: No handler was found to instantiate the class for the object name being used.

Action: Register a handler that is appropriate for the object name that is used, or use a different object name.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46318: An error occurs when registering an MBean with the ObjectName "{0}" and the implementation class "{1}".

Cause: An error occurred when the MBean was being registered.

Action: See the associated Throwable exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46319: An error occurs when unregistering an MBean with the ObjectName "{0}" and implementation class "{1}".

Cause: An error occurred when the MBean was being unregistered.

Action: See the associated Throwable exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46320: An error occurs when parsing an mbeans.xml file.

Cause: The mbeans.xml file had incorrect XML syntax.

Action: Correct the XML syntax in the mbeans.xml file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46324: The MBeanServer object parameter for the MBeanServerForwarder is null, or it is equal to the MBeanServerForwarder, or an MBeanServer object is already set.

Cause: The MBeanServer argument was not valid.

Action: Correct the MBeanServer argument.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46329: Error when parsing {0}.

Cause: The META-INF/mbeans.xml is empty or has syntax error.

Action: Correct the META-INF/mbeans.xml with the correct syntax.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46330: Cannot find any jmx config mbeans in parsed mbeans.xml file

Cause: No config mbeans declared in META-INF/mbeans.xml in the application.

Action: Declare the config mbeans class, interface, config files in META-INF/mbeans.xml.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46331: The numbers of configuration files and persistence managers for the mbean {0} in mbeans.xml do not match

Cause: The injectNames for configuration files and persistence managers in mbeans.xml is inconsistent.

Action: Update the mbeans.xml to use correct configuration files and persistence managers.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46332: MBean "{0}" cannot be registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46333: Cannot find config file {0} in the application for mbean {1}

Cause: The location of config file is not correct or the config file is missing in the application.

Action: Fix the application.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46334: This helper class "{0}" only supports a single config file per MBean. However the MBean "{1}" specifed "{2}" config files.

Cause: Only one confile file par MBean is supported from this helper class

Action: Fix the calling code
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46335: MBean attribute access denied. MBean: {0} {1} for attribute {2} Detail: {3}

Cause: Security check failed.

Action: Access the MBean attribute with the user in right role or group.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46336: MBean operation access denied. MBean: {0} Operation: {1} Detail: {2}

Cause: Security check failed.

Action: Access the MBean operation with the user in right role or group.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46337: RegisterMBean denied: MBean: {0} Detail: {1}

Cause: Security check failed.

Action: RegisterMBean is allowed to the user ADMIN role.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46338: DeregisterMBean denied: MBean: {0} Detail: {1}

Cause: Security check failed.

Action: DeegisterMBean is allowed to the user ADMIN role.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46339: Cannot find any jmx runtime mbeans in parsed mbeans.xml file

Cause: No runtime mbeans declared in META-INF/mbeans.xml in the application.

Action: Declare the config mbeans class, interface, config files in META-INF/mbeans.xml.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46340: EntityResolver "{0}" failed to retrieve mbeans.xml xsd "{1}"

Cause: Either XSD is invalid, or proper Java Security Permissions have not been granted to JMX Framework jars if Security Manager is turned on.

Action: Verify xsd in mbeans.xml file, and ensure proper Security Permissions are granted to JMX Framework jars if Security Manager is turned on.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46341: Failed to create application stripe Id. Missing key: {0}, MBean: {1}

Cause: The key is missing from MBean ObjectName.

Action: Check MBean interface security annotation, make sure the key is available.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46342: Failed to remove old backup of config file {0}

Cause: unknown.

Action: regular backup config directory may help in this case.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46343: Failed to rename old config file {0} to backup file {1}

Cause: unknown.

Action: regular backup config directory may help in this case.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46344: Access denied. Current subject: {0}; Required app roles: {1}

Cause: Current user is not member of any required application roles.

Action: Try again with the user that is member of any of required application roles.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46345: Internal error: invalid security object. type {0}, value {1}

Cause: unknown.

Action: Contact support.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46346: EntityResolver "{0}" failed to retrieve the JMX Framework configuration xsd "{1}"

Cause: Either XSD is invalid, or proper Java Security Permissions have not been granted to JMX Framework jars if Security Manager is turned on.

Action: Verify xsd in JMX Framework configuration file, and ensure proper Security Permissions are granted to JMX Framework jars if Security Manager is turned on.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46347: An error occurs when parsing the JMX Framework configuration file.

Cause: The JMX Framework configuration file had incorrect XML syntax.

Action: Correct the JMX Framework configuration file XML syntax.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46348: Unexpected xml tag {0}, when parsing the JMX framework configuration file.

Cause: Invalid JMX Framework configuration file.

Action: Make sure your JMX Framework Configuration file is valid.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46349: Missing JMX Framework configuration file

Cause: Cannot find the JMX Framework configuration file.

Action: Ensure that you either specify a valid configuration location, or that the default configuration is included in jmxspi.jar under the META-INF directory
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46350: Error parsing JMX Framework Configuration. Invalid value "{0}" for attribute "{1}" defined in XML element "{2}".

Cause: The value for the attribute is not valid

Action: Please correct the value in the JMX Framework configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46351: Invalid ID "{0}". No internal MBean interceptor is associated with that ID.

Cause: The wrong value was specified.

Action: Please correct the value in the JMX Framework configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46352: Invalid URL for custom MBean interceptor "{0}" jar location "{1}"

Cause: The wrong value was specified in the JMX Framework configuration file for the MBean interceptor jar location.

Action: Please correct the value in the JMX Framework configuration file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46353: Custom MBean interceptor "{0}" jar file cannot be found at the specified location "{1}"

Cause: Missing jar file, or incorrect location specified in the JMX Framework configuration file.

Action: Please correct the value in the JMX Framework configuration file, or make sure the jar file is present
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46354: An error was raised while instantiating the JMX Framework MBean interceptor chain.

Cause: See root exception.

Action: Please correct the issue associated with the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46355: An error occured while initializing the JMX Framework MBean level logging interceptor.

Cause: See root exception.

Action: Please correct the issue associated with the root exception.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46356: Logging prior to call getAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46357: Call to getAttribute for MBean "{0}" and attribute "{1}" was successful and returned "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46358: Error while calling getAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46359: Call to preRegister for MBean "{0}" was successful. Original MBean name was "{1}". MBean was registered in MBeanServer "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46360: Call to postRegister for MBean "{0}" was successful. Registration status was "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46361: Error while calling preRegister for MBean "{0}" and MBeanServer "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46362: Calling postDeregister for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46363: Error while calling preDeregister for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46364: Call to preDeregister for MBean "{0}" was successful.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46365: Error while calling postRegister for MBean "{0}" with registration status "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46366: Error while calling postDeregister for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46367: Logging prior to call getAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46368: Call to getAttributes for MBean "{0}" and attributes "{1}" was successful and returned "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46369: Error while calling getAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46370: Logging prior to call setAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46371: Call to setAttribute for MBean "{0}" and attribute "{1}" was successful.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46372: Error while calling setAttribute for MBean "{0}" and attribute "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46373: Logging prior to call setAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46374: Call to setAttributes for MBean "{0}" and attributes "{1}" was successful and returned "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46375: Error while calling setAttributes for MBean "{0}" and attributes "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46376: Logging prior to calling operation "{0}" for MBean "{1}" and parameters "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46377: Call to operation "{0}" for MBean "{1}" and parameters "{2}" was successful and returned "{3}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46378: Error while calling operation "{0}" for MBean "{1}" and parameters "{2}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46379: Logging prior to calling getMBeanInfo for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46380: Call to getMBeanInfo for MBean "{0}" was successful and returned "{1}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46381: Error while calling getMBeanInfo for MBean "{0}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46382: JMX Framework MBean Logging interceptor intialized with log level "{0}", MBean pattern "{1}", call trace set to "{2}" and dump MBeanInfo set to "{3}".

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Programmatic

J2EE JMX-46383: Error while merging configuration for files "{0}" and "{1}" with ConfigMerger instance {2}.

Cause: See nested exception for root cause.

Action: Fix root cause.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46384: Error registering the Configuration Session Manager MBean.

Cause: An error occurred while registering Configuration Session Manager MBean.

Action: See the base exception for details.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46400: The Config MBean jar file "{0}" does not exist.

Cause: The configuration MBeans jar file specified in the "location" attribute of the "config-mbeans" tag did not exist

Action: Correct the path to the configuration MBeans jar file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46401: Attribute "{0}" is unexpected.

Cause: An unexpected attribute was encountered in the MBeans XML file.

Action: Remove the unexpected attribute.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46402: Tag "{0}" is unexpected.

Cause: An unexpected tag was encountered in the MBeans XML file.

Action: Remove the unexpected tag.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46403: Tag "{0}" is missing the required attribute "{1}"

Cause: A required attribute was missing from the MBeans XML file.

Action: Add the missing attribute.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46404: Tag "{0}" is missing the required tag "{1}"

Cause: A required tag is missing from the MBeans XML file.

Action: Add the missing tag.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46406: Class "{0}" does not exist.

Cause: A jmx-config-mbean class or management-interface specified in the MBeans XML file did not exist.

Action: Correct the class reference.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46407: Multiple persistence managers are not allowed for single configuration file.

Cause: Multiple persistence managers were specified for a single configuration file.

Action: Specifiy only one persistence manager.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46408: An invalid location is defined in mbeans.xml for the config file: "{0}"

Cause: An invalid jmx-config-mbean config-file path was encountered in the MBeans XML file.

Action: Correct the path to the configuration file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46409: The Runtime MBean jar file "{0}" does not exist.

Cause: The Runtime MBeans jar file specified in the "location" attribute of the "runtime-mbeans" tag did not exist

Action: Correct the path to the Runtime MBeans jar file.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46410: When specifying multiple "{0}" elements, the injection-name attribute is required

Cause: Your MBean must include a name as part of the @Injection annotations to match resources defined in mbeans.xml

Action: Correct the @Inject annotations in your MBean to reference resources defined in your mbeans.xml
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46411: Error initializing MBean "{0}", declared in "{1}".

Cause: An error occurred while creating or registering a dynamically created MBean.

Action: See the base exception for details.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46412: Error dynamically unregistering MBean "{0}", declared in "{1}".

Cause: An error occurred while dynamically unregistering a Config MBean in the context of an Edit Session.

Action: See the base exception for details.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46413: Error instantiating ObjectName "{0}" while parsing JMX Framework mbeans.xml file: "{1}" as part of EditSession activate.

Cause: See the base exception for details.

Action: See the base exception for details.
Level: 1

Type: WARNING

Impact: Files

J2EE JMX-46414: Error processing JMX Framework mbeans.xml file: "{0}" as part of EditSession activate.

Cause: See the base exception for details.

Action: See the base exception for details.
Level: 1

Type: WARNING

Impact: Files

J2EE JMX-46502: internal session error: "{0}".

Cause: A session operation resulted in an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Other

J2EE JMX-46503: The "{0}" call to the MBean with ObjectName "{1}" is not made in the context of a JMX configuration session.

Cause: The call that was made needed to be made in the context of a JMX configuration session.

Action: Create a JMX configuration session and then make the call.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46504: A call to commit or roll back the sesssion is not made by the owner of the JMX configuration session.

Cause: The call was not made by the owner of the JMX configuration session.

Action: This call must be made by the owner of the JMX configuration session.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46505: The Config MBean implementation object "{0}" for ObjectName "{1}" does not implement MBeanServerSupport.

Cause: The Config MBean implementation did not implement MBeanServerSupport.

Action: Correct the Config MBean implementation so that it implements MBeanServerSupport.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46506: The parent MBean for "{0}" cannot be found.

Cause: The MBean specified a parent MBean that was missing.

Action: Correct the MBean implementation so that it specifies the correct parent.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46507: The ObjectName "{0}" is specified when adding or removing a notification listener in a JMX configuration session.

Cause: Specifying ObjectName when adding or removing a notification listener is not supported in a JMX configuration session.

Action: Add or remove the notification listener without specifying ObjectName.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46508: The createMBean method is called for the ObjectName "{0}".

Cause: An attempt was made to create a ConfigMBean using the createMBean method.

Action: Use the registerMBean method.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46509: MBean custom persistence method error for ObjectName"{0}": "{1}"

Cause: An MBean custom persistence operation resulted in an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46510: JAXB persistence method error: "{0}"

Cause: An MBean JAXB Persistence operation resulted in an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46511: MBean validation error prior to committing for ObjectName"{0}": "{1}"

Cause: An error occurred during validation of an MBean before committing it.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46512: MBean session life-cycle callback error for ObjectName "{0}": "{1}"

Cause: This error occurred when the MBean session life-cycle callback was called.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46513: unexpected error: "{0}"

Cause: An unexpected error occurred.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Other

J2EE JMX-46514: An MBean of type "{0}" implements Persistable directly or implements an unknown subclass of Persistable.

Cause: The MBean must not implement Persistable directly and must not implement an unknown subclass of Persistable.

Action: Remove the use of Persistable.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46515: A configuration session already exists.

Cause: A configuration session was started when one was already active.

Action: Do not attempt to start a second configuration session. Use the prevously started configuration session.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46516: configuration session start error: "{0}".

Cause: There was a failure to start the JMX configuration session due to an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46517: configuration session commit error: "{0}".

Cause: There was a failure to commit the JMX configuration session due to an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46518: configuration session roll back error: "{0}".

Cause: There was a failure to roll back the JMX configuration session due to an error.

Action: See the base exception information cited within the error message for details on the error.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46519: cannot lock MBean: "{0}"

Cause: The MBean was in special domain oracle.as.jmx or was a delegate MBean.

Action: Provide an MBean whose object name is not in the special domain oracle.as.jmx and is not a delegate MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46520: MBean "{0}" cannot be found in the session MBean server.

Cause: The MBean was not registered in the session MBean server.

Action: Register the MBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46600: The groupby attribute "{0}" is invalid.

Cause: The groupby attribute or property specified did not exist.

Action: Ensure that the groupby attribute specified refers to an MBean attribute or property.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46601: An aggregation attribute or property such as groupbyAttrs, aggOps, or aggAttrs is null.

Cause: An aggregation attribute or property was null.

Action: Ensure that the specified aggregation attribute or property exists.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46602: The aggregation operation "{0}" is invalid.

Cause: An invalid aggregation operator was specified.

Action: Verify that the aggregation operator specified is among OPERATION_AVG through OPERATION_GROUPBY defined in oracle.as.jmx.framework.bulkoperations.BulkOperationsMBean.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46603: The groupby key "{0}" cannot be used for aggregation.

Cause: Aggregation was incorrectly specified on a groupby attribute or property.

Action: Specify either aggregation key or groupby key, but not both, on the attribute or property.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-46604: BulkOperationsMBean NamespaceHelper instance creation error: "{0}"

Cause: The provided MBean server is invalid.

Action: Correct the MBean server that is being provided. See the base exception information cited within the error message for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46605: Parameter count ("{0}") does not match mbean count ("{1}")

Cause: The number of parameter arrays passed in does not match the number of mbeans that should be invoked

Action: Ensure that the correct number of parameter arrays are being passed.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46606: non-numeric attribute {0} in aggregation

Cause: BukpOperationMBean Aggregation operation requires all attributes to have numeric values

Action: Do not use attributes with non-numeric values when using the aggregation operation provided by the BulkOperationMBean
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46607: In BukpOperationMBean Aggregation operation, aggOps and aggAttrs need to be the same length

Cause: In BukpOperationMBean Aggregation operation, aggOps and aggAttrs need to be the same length

Action: Ensure that aggOps and aggAttrs are the same length
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-46608: A "null" value was passed to a BulkOperationsMBean method as part of an ObjectName[] parameter. We will ignore that value, as it would cause all MBeans to be selected. If this is the intended behavior use new ObjectName("*:*") in place of null

Cause: This could be due to some user code logic error, and not intended.

Action: If this is the intended behavior use new ObjectName("*:*") in place of null
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JMX-47000: Property "{0}" is not set.

Cause: The expected property was not set.

Action: Add the expected property to the mbeans.xml file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47001: A JAXB error occurred during unmarshalling of "{0}".

Cause: Some data in the xml file is invalid.

Action: Use the JAXB error information to correct the xml file.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47002: A JAXB error occurred during marshalling of "{0}".

Cause: Some data to be marshalled is invalid.

Action: Correct the data to be marshalled.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47003: An error occurred during initializion of the JAXB context using the contextpath "{0}"

Cause: The contextpath in the mbeans.xml file is invalid.

Action: Correct the contextpath.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JMX-47004: The JAXB Object "{0}" has been loaded

Cause:

Action:
Level: 16

Type: TRACE

Impact: Programmatic

J2EE JMX-47005: THE JAXB Object "{0}" has been persisted.

Cause:

Action:
Level: 16

Type: TRACE

Impact: Programmatic

J2EE JMX-47006: Persistance manager "{0}" does not implement "{1}".

Cause: Persistance manager implementation inheritance incorrect.

Action: Correct the persistance manager implementation.
Level: 1

Type: WARNING

Impact: Programmatic

27 J2EE JSP-00002 to J2EE JSP-00302

J2EE JSP-00002: an internal JSP error occurred. Additional information follows: {0}.

Cause: JSP encountered an unexpected situation. This may be a bug in the JSP servlet.

Action: Contact Oracle Support Services. Oracle Support Services may recommend increasing the log level to FINER to help understand the situation.
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00003: unable to fully process the TLD cache for the following reason: {0}.

Cause: An error occured while the Tag Library Descriptor cache was created or accessed.

Action: Check the TLD for validity and fix the TLD, or remove it if it is not used in the application. If the logging level is set to FINER more information should be available in the exception contained in the error message.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00005: unable to send the following error in the response. Response code: {0} Error message: {1}.

Cause: An exception occurred that prevented the error status from being sent in the response.

Action: See the exception cited in the error message. It may be necessary to increase the logging level to FINER to see the exception.
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00006: unable to prepare or access an auxiliary object: {0} {1}.

Cause: The auxiliary object required for tracking JSP page dependencies was not read in or created.

Action: Recompile the page after checking factors that impact file reading such as disk corruption, permissions, and file handles.
Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00007: cannot find the message resource file, {0}, in the server to report error messages.

Cause: Due to a missing error message resource bundle, the underlying error message was not presented.

Action: Contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Installation

J2EE JSP-00008: unable to dispatch JSP page: {0}.

Cause: An error prevented the dispatching of the JSP page.

Action: Correct the error described in this logged message.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

J2EE JSP-00009: unable to return the following error in the response: {0}.

Cause: An input-output error occurred while trying to write an error message to the servlet response stream.

Action: The logged message contains the error message that could not be returned in the response, and the associated exception. It may be necessary to increase the logging level to FINER to see the exception. Scan the log files for additional error messages that may reveal the root cause of this problem.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00010: building the cache named {0}.

Cause: Started building the Tag Library Descriptor persistent cache.

Action: none
Level: 1

Type: NOTIFICATION

Impact: Deployment

J2EE JSP-00011: Invalid JSP tag library location. {0} does not exist or is not a directory.

Cause: An invalid or nonexistent directory name was supplied as a tag library location.

Action: Correct the directory name and insure that it is available.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00012: obtaining application resources.

Cause: Finished obtaining current Tag Library Descriptors for this application.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00013: the initialization of TLD cache is complete.

Cause: Initialization of the Tag Library Descriptor persistent cache is completed.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00014: the number of listeners in TLDs visible to this application is {0}

Cause: The number of listener elements found in the Tag Library Descriptors visible to the applications was reported.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00015: starting to read the persistent TLD cache named {0}.

Cause: The Tag Library Descriptor persistent cache was read.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00016: completing cache update

Cause: Updating the Tag Library Descriptor persistent cache was completed.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00017: inserting TLD at: {0}

Cause: The TLD at the given URL was inserted into the TLD persistent cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00018: applying update to TLD at: {0}

Cause: The TLD at the given URL was updated in the TLD persistent cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00019: completing processing of TLD persistent cache

Cause: The processing of this TLD persistent cache is finished.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00020: writing TLD persistent cache to file system

Cause: Finished writing out the Tag Library Descriptor Persistent Cache.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00021: URL for entry is {0}.

Cause: Processed a TLD at the following given URL.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00022: loading external TLD with uri element, {0}, from JAR {1}.

Cause: Loaded TLD from the location external to the application given in the message text.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00023: loading application TLD with uri element, {0}, from location {1}.

Cause: Loaded TLD from the application location given in the message text.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00024: loading TLD accessible via the name, {0}, from {1}

Cause: Loaded tag library descriptor at the following location for access via file or jar name.

Action: See error message.
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00025: finding listener, {0}, in TLD

Cause: The name of a listener element found in a Tag Library Descriptor visible to the application is supplied.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00026: missing required uri element in external TLD: {0}

Cause: Encountered a Tag Library Descriptor with an invalid or missing uri-element where one is required. For example, global tag libraries and those extrenal to the application must have URI elements.

Action: Supply the URI element in the TLD file or move the tag library to the application level.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00027: unable to parse TLD file: {0}

Cause: The TLD at the given location could not be parsed.

Action: Check for invalid XML syntax, especially unbalanced angle brackets or start and end tags.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00028: duplicate URI element, {0}, in TLD, {1}, and TLD, {2}

Cause: More than one tag library descriptor encountered using the same URI element. URI elements visible to the application must be unique.

Action: Change one of the uri element values or exclude one of the tag libraries from the this application.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00029: unable to obtain cache key: {0}

Cause: A corrupted cache key was encountered in the TLD cache.

Action: Stop the server, delete the TLD cache files from the application's persistence directory and from the global directory, tldcache and restart the application server. Contact Oracle Support Services if this problem persists.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00030: unable to obtain the JSP parameters

Cause: A unknown problem was encountered when attempting to initialize JSP configuration parameters.

Action: Verify the XML syntax in orion-web.xml, especially in the attributes of ojsp-init element if used. Verify the syntax of any init-parameters supplied to the JspServlet in web.xml or global-web-applications.xml. Then redeploy the application. If that fails, or if errors were found in the global-web-applciation.xml, restart the server. If the problem persists contact Oracle Support Services
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00031: refreshing the cache named {0}.

Cause: Started refreshing the Tag Library Descriptor cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00032: looking for global resource at {0}.

Cause: The global Tag Library Descriptors were sought in the location or locations cited in the error message.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00033: unable to process an invalid or unsupported TLD version: {0}

Cause: An invalid or unsupported value of the taglib element's attribute, version, element was supplied.

Action: The taglib element is the root element for all TLD's. The element's attribute, version, must be either 2.0 or 2.1.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00034: loading cachedConfigTable from persistent cache

Cause: The internal configuration data structure was loaded from the persistent Tag Libary Descriptor cache.

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00035: unable to load changeAwareClassLoader class. Shared libraries from web-app and enclosing app will not be scanned for TLDs

Cause: Loading of ChangeAwareClassLoader failed

Action: none
Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00036: unbable to obtain Tag Library listeners: {0}

Cause: An error was encountered while obtaining Tag Library listeners during the parsing of Tag Library Descriptors.

Action: Verify that classes given in the listener-classes element are available in the application's class path. Check for general XML syntax (i.e., unmatched quotes or start/end tags) in the application's TLD's.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00037: cannot load tag library {0} specified in web.xml

Cause: A tag library defined in the application's web.xml file was not loaded.

Action: Verify that the taglib-uri and taglib-location are correctly formatted and point to valid values, and that the tag library implementations classes are available to the application.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00038: error preparing dependency file for tag file:

Cause: An error was encountered while writing or preparing the dependency file for a tag file.

Action: Recompile the page that accesses the tag file after checking factors that impact file writing such as disk space, permissions, and file handles.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00039: invalid tag file: {0}. File must end with .tag or .tagx and start with /WEB-INF/tags or /META-INF/tags.

Cause: Encountered a tag file path that is an invalid or non-existent location.

Action: Correct the tagfile-path element value by ensuring that it ends with either .tag or .tagx, and starts with either /WEB-INF/tags or /META-INF/tags.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00040: duplicate tag name : {0}. TLD is invalid

Cause: A tag name that was used in more than one Tag Library Descriptor was visible to the application and caused an error.

Action: Tag names must be unique. Change the duplicate name in that tag or tag file element.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00041: The value {0} is invalid for main mode.

Cause: An invalid value for the main mode was detected.

Action: Valid values for the main mode are recompile, reload and justrun.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00042: The value {0} is invalid for debug.

Cause: An invalid JSR45 debug parameter was specified.

Action: Valid values for debug are none, file and class.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00043: The value {0} is invalid for tags reuse.

Cause: An invalid tags reuse parameter was specified.

Action: Valid values for tag resuse are compiletime, compiletime-with-release and none.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00044: error invoking the following JSP tag life-cycle method: {0}

Cause: An internal error occured. The JSP runtime failed to execute a method provided by the Oracle JSF Injection Provider. The JSP page in which the error occured will not be serviced.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00045: unable to scan annotation for tag {0}: {1}

Cause: The tag implementation class given in the error text could not be scanned for annotations.

Action: See the error cited in the error message to determine what action is required.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00046: Unable to load class {0} while scanning for annotated JSP tags.

Cause: The tag class for annotations cited in the error message was not scanned. The class appeared to be missing, or was unloadable.

Action: Make sure that the missing class is available in the application class path. Verify that the class file was generated with a jdk version that supports annotations.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00047: unable to scan annotation {0}. It is not a JSP tag.

Cause: The class to be scanned does not implement the JspTag interface or cannot be loaded.

Action: Make sure the class is available in the application classpath and that it implements the javax.servlet.jsp.tagext.JspTag interface.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00048: annotation scanning is incomplete: {0}

Cause: Scanning for annotations in the Tag Library Descriptors, visible to the application, was not completed.

Action: Verify that the class is availble in the applications classpath. If so, check application server log files for problems such as out of memory, file permissions, network access.
Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00049: reading implicit.tld file at {0}

Cause:

Action:
Level: 16

Type: TRACE

Impact: Files

J2EE JSP-00050: Parameter {0} is no longer supported as of Oracle Containers for J2EE 11g. The parameter is ignored.

Cause: An application attempted to use the parameter cited in the error message that was desupported as of release 11G.

Action: You can avoid this message by removing the given parameter.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00051: unable to write an auxiliary object during the page compilation: {0} {1}.

Cause: The auxiliary object required for tracking the JSP page dependencies could not be written to a file.

Action: Recompile the page after investigating the factors that impact file writing such as disk space, permissions, and file handles.
Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00052: Using the ProviderURI {0} that is returned from custom provider for processing requests.

Cause: An application-specific provider was registered and used.

Action: none
Level: 1

Type: TRACE

Impact: Configuration

J2EE JSP-00053: The value {0} is an invalid value for generic servlet mode.

Cause: An invalid parameter for the generic servlet mode was specified.

Action: Use a valid parameter value. They include shared, single, none, and single_and_persist.
Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00054: Unable to retrieve HttpApp object through ThreadState.

Cause: An application that did not use the default OC4J HttpApplication object failed to supply its own application context object.

Action: Supply the application context or allow the use of the default one.
Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00055: Setting JSP:Config parameter {0} = {1}

Cause: The JSP:Config parameter cited in the message was set.

Action: none
Level: 32

Type: TRACE

Impact: Configuration

J2EE JSP-00056: The web.xml at {0} is version 2.3 but has a <jsp-config> element. Ignoring <jsp-config> element.

Cause: Web.xml version 2.3 does not include support for <jsp-config>

Action: Either remove the <jsp-config> element or upgrade the web.xml to version 2.4 or higher
Level: 1

Type: WARNING

Impact: Other

J2EE JSP-00057: unable to determined the last-modified date of the file at path, {0}.

Cause: This is usually caused by an IO error. However this error may related to something that happened before this instanceof OC4J started. This has been known to happen if at some point two processes attempted to write to the same file at the same time. This error can also occur if the file was last modified within one second of EPOCH (at 0 hour on January 1, 1970), in this case it should be ignored.

Action: Verify that the file is not corrupted. If it is not, this error can be ignored. You may use the touch command, in unix, to update the last modified date of the file to prevent subsequent logging of this error. If the file is corrupted attempt to determine the cause of the corruption and fix it, or Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

J2EE JSP-00058: error attemping to parse web.xml at {0}.

Cause: Error parsing the web.xml file located at the path location listed in the log message.

Action: Attempt to fix the error in the web.xml file base on the information contained in the log message.
Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00059: unable to inject a resource.

Cause: The exception cited in the error message occurred when the JSP page was processed.

Action: Read the exception cited in the error message to understand the cause. If no exception is shown, increase the log level to FINER.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00060: unable to parse the tld with the following url: {0}. Error details follow: {1}.

Cause: Failed to parse the tag specified in the error message.

Action: Read the error details cited in the error message and attempt to fix the offending tag, or remove it is it is not needed.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00061: there is a JSP error in file {0} at line {1}. The error is: {2}, in {3}.

Cause: A JspParse Exception was encountered.

Action: Examine the content of the error message which indicates the nature and location of the error. Then fix the error.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00062: unable to get the TLD document associated to file {0} at line {1}. The error is: {3}.

Cause: Internal error. Inconsistent gathering of performance statistics

Action: Examine the content of the error message which indicates the nature and location of the error. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00063: unable to read the jar file named {0}.

Cause: An input-ouput exception occured while attempting to read the jar file specified in the message.

Action: Examine the content of the error message which indicates the nature and location of the error. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00064: unable to obtain URI because of an XML parsing exception in file, {0} at element, {1}.

Cause: An exception occured in the XML parser while parsing for a URI.

Action: Examine the content of the error message which contains at least the name of the relevant file and most likely the name of the relevant XML element. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00065: unable to process the file at {0} due to an input-ouput exception.

Cause: An input-output exception prevented the processing of the file named in the log message.

Action: Examine the content of the error message which indicates the nature of the error as well as the location of the file involved. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00066: unable to find class named {0} in resource {1}.

Cause: The JSP runtime could not find the class specified in the message in the resource also specified in the message.

Action: Verify the resource in question and attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00067: unable to read optional data.

Cause: The JSP runtime encountered a java.io.OptionalDataException.

Action: Read the full error message and consult the Javadoc on OptionalDataException to understand the problem and attempt to fix it. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00068: invalid taglib uri: {0}, unless non taglib namespace was intended in a JSP document.

Cause: An invalid taglib uri was specified.

Action: Fix the taglib attributes in your jsp.
Level: 1

Type: NOTIFICATION

Impact: Configuration

J2EE JSP-00069: Name space, {0}, also known as {1} will override name space {2}

Cause: The namespace definition in the last tld defining the namespace overrided any previous definition of that namespace.

Action: See error message.
Level: 1

Type: WARNING

Impact: Other

J2EE JSP-00070: an unlikely, but generally harmless, situation has been detected. Additional information follows: {0}.

Cause: JSP encountered an rare situation. This should not cause any adverse effect on yor application.

Action: If this occurs in the absence of other errors, this is most likely a benign situation, if accompanied by other error messages, this may held diagnose the root cause of the problem reported by the other error messages. You may Contact Oracle Support Services to help us improve the product in future releases. Oracle Support Services may recommend increasing the log level to FINER to help understand the situation.
Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00071: Error loading third-party EL library specified in the init-param of the Oracle JSP servlet {0}: {1}

Cause: The JSP runtime could not load the EL factory class specified in the init-param of the Oralce JSP servlet.

Action: Verify the third party EL library specified in init-param 'el_expression_factory' and attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00072: Unable to process third-party EL library specified in the init-param of the Oracle JSP servlet {0}: {1}

Cause: The JSP runtime could not process the EL factory class specified in the init-param of the Oralce JSPservlet.

Action: Verify the third party EL library specified in init-param 'el_expression_factory' and attempt to fix the error. Check the specified factory class for validity; for example, the constructor for the specified factory class should be public. If all fails, contact the third-party for support.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00073: Unable to look up JRF helper API to query Exalogic optimization: {0}

Cause: The JSP runtime could not look up JRF helper API to query Exalogic optimization flag.

Action: Currently JRF supports only JBoss and WebSphere, other platforms are yet supported.
Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00074: Adding jar name {0} to the global cache with tlds {1}

Cause: Global cache with init-param 'global_app_taglib_jars' is enabled for this application. We will add the jar/tlds to the global cache.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00075: Found jar name {0} in the global cache with tlds {1}

Cause: Global cache with init-param 'global_app_taglib_jars' is enabled for this application. We will use the jar/tlds previously cached from the global cache.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00101: Inconsistent use of the DMS (statistics aggregation) framework. The problem occured in application, {0}, for this uri: {1}. {2}

Cause: Internal error. Inconsistent gathering of performance statistics

Action: Examine the error message to determine which statistics are inconsistent; those statistics should not be trusted. Contact Oracle Support Services and give them the full error message.
Level: 1

Type: ERROR

Impact: Performance

J2EE JSP-00111: the Oracle DMS framework is unavailable.

Cause: The JSP servlet could not find the Oracle DMS classes.

Action: If using a third-party application server, the DMS functionality will simply not be available. If using an Oracle Application Server, this message indicates that there is something wrong with the installation. In that case, contact Oracle Support Services and give them the full error message.
Level: 1

Type: WARNING

Impact: Installation

J2EE JSP-00300: unable to access osgi.syspath, {0}, even though it exists.

Cause: There is a problem with the path corresponding to System property osgi.sypath.

Action: Check that the path is valid, unlocked, and that WebSphere has read/write permissions for it.
Level: 1

Type: ERROR

Impact: Files

J2EE JSP-00301: unable to extract the local classpath field.

Cause: There is a problem extracting the local class path from the WebSphere class loader.

Action: Contact Oracle Support Services and ask for a patch if this prevents ojsp.next from functioning normally.
Level: 1

Type: ERROR

Impact: Programmatic

J2EE JSP-00302: unable to determine the osgi pluggin classpath.

Cause: There is a problem assembling the osgi plugin class path.

Action: Contact Oracle Support Services and ask for a patch if this prevents ojsp.next from functioning normally.
Level: 1

Type: ERROR

Impact: Programmatic

28 JBO-24000 to JBO-80008

JBO-24000: no JAAS Context. Permission information is not available.

Cause: An error occurred while initializing the Java Authentication and Authorization Service (JAAS).

Action: Make sure that the JAAS configuration is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24001: Role {0} is not found.

Cause: An error occurred while retrieving the role.

Action: Make sure that the role information is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24002: User {0} is not found.

Cause: An error occurred while retrieving the user.

Action: Make sure that the user information is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24003: Attribute {2} in entity {1} is not updatable.

Cause: An attempt was made to update the attribute, but the user did not have permission or the attribute was not updatable.

Action: Make sure that the user permission and updatable setting for the attribute are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24004: Rows cannot be removed from entity {0}.

Cause: An attempt was made to remove the row, but the user did not have permission or the entity was read-only.

Action: Make sure that the user permission and read-only setting for the entity are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24005: Rows cannot be created in entity {0}.

Cause: An attempt was made to create a row, but the user did not have permission or the entity was read-only.

Action: Make sure that the user permission and read-only setting for the entity are correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24006: The entity already has permission defined.

Cause: The entity already has permission defined.

Action: Modify permission def is not allowed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-24007: Unable to get system property {0} when security manager is enable.

Cause: The property is not defined.

Action: Get property value is not allowed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25000: SQL type {0} is invalid.

Cause: An attempt was made to generate a null value for a domain with an invalid SQL type.

Action: Provide a valid SQL type name for the domain. Examples include VARCHAR, CHAR and NUMBER. See oracle.jbo.server.OracleTypeMapEntries for a full list.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25001: Object {1} of type {0} already exists.

Cause: An attempt was made to load a business component with the same name and type as another business component already loaded by the application module.

Action: Provide a different name for the business component. If a null value or null string is provided for the name, the framework will create a unique name within the scope of the application module.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25002: Definition {1} of type {0} is not found.

Cause: A definition object with the given name could not be found.

Action: Provide a correct name for the business component definition (using the format 'packagename.objectname') and ensure that the definition is available on the classpath. This error can also occur if there is a case conflict, as when the database expects 'DEPTNO' and receives 'Deptno' instead.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25003: Object {1} of type {0} is not found.

Cause: A business component object with the given name could not be found in the application module.

Action: Provide a different name for the business component object or create a new business component with the given name.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25004: Definition name {1} of type {0} is invalid.

Cause: An attempt has been made to load an invalid definition name or associate a definition name with a type for which it is not valid.

Action: Ensure that the name is a valid Java identifier with no spaces or punctuation, and conforms to the format 'packagename.objectname'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25005: Object name {1} of type {0} is invalid.

Cause: An attempt has been made to associate a business component name with an object for which it is not valid.

Action: Ensure that the name is a valid Java identifier with no spaces or punctuation, and conforms to the format 'packagename.objectname'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25006: Value {2} passed as parameter {1} to method {0} is invalid: {3}.

Cause: An attempt was made to invoke a business components method with an invalid parameter value.

Action: Pass a correct value for the parameter. To determine the allowed values for a given parameter, check the Javadoc for the method that throws this exception. For example, Javadoc indicates that the 'DBTransactionImpl.executeCommand' method throws this exception when the 'command' parameter is empty.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25007: The validation flag cannot be reset for a default iterator.

Cause: An attempt was made to reset the row validation flag for the default iterator of a rowset or view object.

Action: Reset the row validation flag for the rowset or view object instead. This will create a secondary iterator to allow the rowset or viewobject to navigate to another row without validating.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25008: Object {0} cannot be removed because it is referenced by object {1}.

Cause: An attempt was made to remove a view object that is participating in a view link.

Action: Remove the view link before removing the view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25009: Cannot create an object of type:{0} from type:{2} with value:{1}

Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain constructor threw an unexpected exception.

Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25010: A validation failure has occurred while creating a domain with value {0}.

Cause: Validation failed with the given value in a domain constructor. This exception is thrown in the domain type 'validate()' method.

Action: Provide a valid value for the domain type.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25011: Rowset {0} is forward only.

Cause: An attempt was made to invoke an invalid navigation method on a forward-only view object or rowset.

Action: Either remove the forward-only setting for the view object or rowset, or do not invoke navigation methods other than 'next()' on the forward-only view object or rowset.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25012: View object {0} does not have entity {1} as its primary base.

Cause: The client attempted to locate a view row that has the given entity row as its primary entity row. However, the entity row's entity definition does not match the entity definition of the view object's primary entity object base.

Action: Ensure that the entity row used to locate view rows is based on the same entity definition as the view object's primary entity object base.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25013: Too many objects match the primary key {0}.

Cause: An attempt was made to add a newly fetched or created entity to the cache, but the new entity has the same primary key as an existing entity. The primary key must be unique for this entity type.

Action: Add more attributes to the key definition for the entity type, so that each row for this entity is uniquely identifiable. Or fix the primary key value so that this entity has a unique key identifier.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25014: Another user has changed the row with primary key {0}.

Cause: The database value does not match the cached value for this entity object. This could happen when another user or operation has committed modifications to the same entity row in the database. This exception can also be thrown if the 'equals' method on one of the domain type attributes in the entity fails.

Action: Choose from the following options: 1. Verify that another user or operation has not modified the same row in the database. If this entity has attributes of a domain type verify that the <code>equals()</code> method on these domains do not fail when comparing the existing cached value with the newly fetched value. 2. For any attributes/columns that are updated by the database, modify the entity attribute definition by selecting 'Refresh after update' on the Attribute Settings page of the Entity Object Wizard. 3. Use 'view.executeQuery()' frequently, especially after any operations that result in data being changed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25015: Query collection {0} is closed.

Cause: An attempt was made to execute a query or access a row from a closed or removed view object or rowset.

Action: Verify that the view object or rowset is not removed or closed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25016: View object {0} is read-only.

Cause: An attempt was made to modify data for a view object which is declared to be read-only. This includes creating a new row for this view object, removing a row, or modifying attributes of a view row for this view object.

Action: Create a view object with the read-only flag set to 'false' in order to modify data.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25017: New entity row of type {0} cannot be created.

Cause: An unexpected exception occurred while creating a new entity instance.

Action: Ensure that the entity has a public default constructor. Fix the cause of the InstantiationException or IllegalAccessException that appears in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25018: New view row of type {0} cannot be created.

Cause: An unexpected exception occurred while creating a new view row instance.

Action: Ensure that the view row has a public default constructor. Fix the cause of the InstantiationException or IllegalAccessException that appears in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25019: Entity row with key {1} is not found in {0}.

Cause: An attempt was made to lock a nonexistent row in the database. This could occur when the cache has an entity which was subsequently deleted from the database by another user or operation.

Action: Remove the current entity from the entity cache by calling 'remove'. Or, synchronize the cache with the database by rolling back the current transaction or by committing the existing set of changes and then dropping the entity cache.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25020: View row with key {1} is not found in {0}.

Cause: An attempt to find a referenced entity in the view row failed due to a changed foreign key value.

Action: Provide a valid foreign key value or remove the current one.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25021: Domain object type {0} cannot be created.

Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain constructor threw an unexpected exception.

Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25022: A view link {0} already exists between source view object {1} and destination view object {2}.

Cause: An attempt was made to set the master rowset for this rowset more than once.

Action: Do not invoke 'setMasterRowSetIterator' more than once on a rowset.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25023: Operation {0} on domain value {1} of class {2} cannot be performed.

Cause: An unexpected domain exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25024: Method {0} is obsolete.

Cause: An attempt was made to use an obsolete type map constructor.

Action: Verify that the type map is compatible with this version of the framework. See example type maps in 'oracle.jbo.server.OracleTypeMapEntries'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25025: Rowset with XML tag {0} cannot be loaded.

Cause: An error occurred while reading the XML data for a view object. This exception might contain other ReadXMLExceptions.

Action: Fix the contained row-level or attribute-level exceptions in the details for this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25026: Row {1} with XML tag {0} cannot be loaded.

Cause: An error occurred while reading the XML data for a view row. This exception might contain other ReadXMLExceptions for contained rowsets or attributes.

Action: Fix the rowset-level or attribute-level exceptions in the details for this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25027: Attribute {1} at index {2} with XML tag {0} cannot be loaded.

Cause: An error occurred while reading the XML data for an attribute of a view row. This exception might contain other JboExceptions thrown from the set method for this attribute.

Action: Fix the JboException in the details for this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25028: Domain object type {0} cannot be created: {1}.

Cause: A domain object could not be created with the given value. Either a domain constructor that accepts the given value does not exist, or there is no conversion method in the domain object for the given value type, or the domain constructor threw an unexpected exception.

Action: Ensure that the value being passed is valid with respect to the domain type being created. For example, passing the string value 'one' to the 'oracle.jbo.domain.Number' constructor will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25029: Domain class {0} is not found.

Cause: The named data class (typically a domain) could not be found.

Action: Ensure that the data class is accessible from the CLASSPATH and is a valid data class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25030: Detail entity {0} with row key {1} cannot find or invalidate its owning entity.

Cause: No container entity was found for a detail entity in a composition association. This could occur if a nonexistent master key value was passed in during creation of a new detail entity instance, or if the foreign key value of this entity was modified so that it no longer matched any master entity.

Action: Pass a valid foreign key value to the 'create' method or 'setAttribute' method so that an appropriate master row is found for this entity.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25031: View row for view object {0} is missing entity row for {1}.

Cause: The client attempted to access an attribute of a view which is mapped to an entity row, but the corresponding entity row is null. If the view object consists of multiple entity object bases and if the secondary entity object bases are reference-only, the entity rows could be null if the foreign key linking the primary entity to the secondary entity object is null.

Action: Do not try to access attributes of missing entity rows in this situation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25032: Passivation to target store {1} is unsuccessful.

Cause: A failure occurred while trying to passivate the application module or transaction state.

Action: Resolve the detail exception raised by the passivation target store (Database, File or Memory).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25033: Activating state with id {0} from target store {1} is unsuccessful.

Cause: A failure occurred while trying to activate the application module or transaction state.

Action: Resolve the detail exception raised by the passivation target store (Database, File or Memory) and ensure that the state snapshot ID exists in the target store.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25034: Row with handle {1} is not found in rowset {0}.

Cause: The client attempted to locate a row with a stale row handle. This error might be raised if the client tries to take a row out of one query collection and use its handle to find a row in another query collection. Note that if the client calls executeQuery on a rowset, it might receive a new query collection. Thus, this error might occur if the client retrieves a row from a rowset, takes its row handle, calls executeQuery, and then tries to locate the row using the saved handle. This exception might also be raised if a row reference is used across transaction boundaries and the row handle has become stale and hence the corresponding row cannot be found.

Action: Make sure that the row handle is not stale. One approach is to find the row again using its primary key before attempting to act on the row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25035: The application module passivation store is invalid.

Cause: An application attempted to change an application module's passivation store after it had been initialized. The passivation store (Database, File or Memory) can only be initialized once. If the customer application logic has not specified a passivation store when the serialization framework is invoked, the passivation store is initialized by the framework.

Action: Check the client application logic for invocations of ApplicationModuleImpl.setStoreForPassiveState which are invoked after the application module passivation store has been initialized.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25036: An invalid object operation was invoked on type {0} with name {1}

Cause: An application invoked an object operation that is not supported in the object's current state.

Action: Remove the invalid operation invocation or provide exception handling logic.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25037: Detail row set {0} is missing a master row set iterator for view link {1}, master view object {2}.

Cause: This row set is a detail in a master-detail relationship, but it is missing a master row set iterator. Most likely, this occurred because a master row set iterator was removed through a call to removeMasterRowSetIterator() and has not been replaced with an appropriate one.

Action: Call setMasterRowSetIterator() to provide a valid master row set iterator.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25038: Value {2} passed as parameter {1} to method {0} is invalid.

Cause: An attempt was made to invoke a business components method with an invalid parameter value.

Action: Refer to the documentation of error message JBO-25006 (EXC_INVALID_PARAMETER) for more information. The difference between this error message and EXC_INVALID_PARAMETER is that this version does not include an explanation. In general, Oracle recommends using JBO-25006 instead of JBO-25038.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25039: No current row in row set iterator {0}

Cause: The client attempted to work with the current row of a row set iterator, but the iterator has no current row.

Action: Position the iterator to the correct row and perform the operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25040: Row should be locked before getting an output stream from an attribute.

Cause: The row containing a large object was not locked before attempting to call a method on the large object that could potentially change the data of the object.

Action: Lock the row before attempting to get an output stream or write into a large object domain instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25041: Type map cannot convert data from {1} to {0} with operation {2}.

Cause: The TypeFactory class asked the TypeMapEntries class to convert data, but the TypeMapEntries class did not know how to perform the conversion. This is typically an issue with the TypeMapEntries implementation.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25042: Row of trans post listener handle {0} not found in list.

Cause: Entity row of the given handle is not found in transaction post listener list. Most likely cause of this error is as follows: the user requests certain operation. The operation tries to get access to the row in database. This fails for whatever reason (this exception's detail might have further information). The system tries to fix the problem at the entity level. It looks for the entity row in the transaction post listener list. The specified row is not found.

Action: Look at the details and see if the cause can be determined from them. Check to see if concurrent updates to database could have caused the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25043: Extraneous key {0} of index {1} (in key-value array) passed to findByKey for view object {2}.

Cause: Extraneous key passed in to findByKey(). For example, suppose the View Object expects no more than a two-part key, but the key passed into findByKey is a three-part key. Then, this exception will be thrown.

Action: Provide a valid key.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25044: Application state snapshot is based on an older version of the application definition metadata.

Cause: An attempt was made to activate application module or transaction state based on an older metadata definition into an application module with a later metadata definition.

Action: Ensure that snapshots used for state activation were generated from the currently running version of the application definition metadata.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25045: Row set iterator {0} has detected an implicit synchronization attempt.

Cause: An attempt was made to implicitly synchronize an iterator in a 3-tier running environment. When the application module synchronization mode is set to SYNC_BATCH, iterator synchronization must be done explicitly.

Action: Remove code that attempts to synchronize the iterator implicitly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25046: Requested row not available in row set iterator {0}.

Cause: This exception is thrown when running in 3 tier SYNC_BATCH mode. The user requested a row, but that row is not available in the cache.

Action: Make appropriate API calls to bring the required row into cache. Then, try to get the row again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25047: Attempt to make call to server detected for application module {0}.

Cause: An attempt to make a call to server detected for an operation that is supposed to work only with client cache.

Action: Remove code/operation that attempts to call server.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25048: Operation {0} is invalid for a working set object.

Cause: This operation is invalid for this working set object. It might be because the operation doesn't make sense in batch mode, or because the batch communication mode (WSApplicationModuleImpl.getBatchCommMode()) does not allow this operation.

Action: Remove code/operation that calls the named method of set the batch communication mode to allow this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25049: Entity {0} cannot be set to batch mode because a key attribute is marked as refresh-on-insert or refresh-on-update.

Cause: An attempt was made to set batch mode on an entity that has a primary key marked as refresh-on-insert or refresh-on-update.

Action: Remove the refresh-on-insert or refresh-on-update setting of the primary key attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25050: Batch mode post operation failed. See Exception details for a list of failures.

Cause: Posting entities in batch mode failed with a set of exceptions

Action: Fix the cause for each of the exceptions in the details array.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25051: Row of range index {1} is not found in RowSetIterator {0}.

Cause: The client has attempted to locate a row with a range index, but the Row Set Iterator's range does not have a row at the index. It might be that the range index is too big (>= the range size), or that the range is at the bottom and the range index is beyond the last row of the Row Set. Or, the Row Set might have been reset because of operations like rollback and clear-cache. Hence, the range is empty and no row is found

Action: Make sure that the row set iterator is open and has rows in its range. Also, make sure that the range index falls between the first and the last row of the range.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25052: View object {0} with no key attributes cannot be activated.

Cause: A view object with no key attributes was configured to passivate one or more of its transient attributes. However, a view object without key attributes cannot participate in state passivation.

Action: Define one or more key attributes for this view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25053: Cannot navigate with unposted rows in a RangePaging RowSet.

Cause: An attempt has been made to navigate a rowset in Range Paging mode when the rowset has inserted/removed rows.

Action: Post this transaction before navigating.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25054: Cannot locate the specified stack snapshot id: {0}

Cause: An attempt has been made to activate a stack snapshot that does not exist. The specified snapshot might already have been activated or the stack might already have been cleared by a previous rollback/commit.

Action: Ensure that stack snapshot ids are maintained by the application across transaction boundaries.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25055: Snapshot {0} cannot be removed.

Cause: An attempt was made to remove a persistent snapshot that is referenced by the snapshot stack.

Action: Clear the snapshot stack before attempting to remove the referenced snapshot.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25056: Cannot call removeFromCollection() or removeAndRetain() on an Entity row: Entity name {0}

Cause: An attempt has been made to call removeFromCollection() on an Entity row. It is illegal to call removeFromCollection() on an Entity row.

Action: Remove code that calls removeFromCollection() on an Entity row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25057: Entity row update operation did not find matching row: Entity name {0}, key {1}

Cause: In LOCK_OPTUPDATE locking mode, an attempt was made to update an Entity row. The update operation failed to update any row.

Action: Another user might have modified the row and committed the changes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25058: Definition {1} of type {0} is not found in {2}.

Cause: No business component definition found with the given name in the project classpath.

Action: Provide a correct name for the business component definition and ensure the definition is available on the classpath. Names are of the format <code>myProjectPackage.BusinessPackage.BusinessComponent</code>. This error can also occur if there is a case conflict, as when the database expects 'DEPTNO' and receives 'Deptno' instead.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25059: View Object {0} has ManageRowsByKey turned on, but its key definition is empty

Cause: This View Object is not Entity based, and its ManageRowsByKey flag is true. Yet, its key definition is empty. Restated, the user has asked for the View rows to be managed by keys, but the key definition is empty (which would produce empty keys for all rows).

Action: In order to manage EO-less View Object by key, a meaningful (non-empty) key definition must be supplied.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25060: Unexpected error encountered while trying to retrieve the next row from JDBC ResultSet for collection {0}

Cause: An unexpected exception was thrown while retrieving the next row from JDBC ResultSet.

Action: Take a look at the detail exception for further information and fix underlying problems.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25061: Cannot enable passivation for internal ViewObjects and rowsets.

Cause: ViewRowSetImpl.setPassivationEnabled called for internal rowset

Action: Create a datamodel ViewObject instance and use rowsets from that ViewObject to make them passivation enabled.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25062: Cannot find a matching detail ViewObject. Link definition: {0}, master row set iterator {1}.

Cause: An attempt was made to create detail rowset. However, no matching detail view object could be found.

Action: Ensure that a matching view object is present before attempting to create a detail rowset.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25063: Operation {0} cannot be performed because the working set object is not bound.

Cause: This operation is invalid for this working set object because the working set object is not bound to actual implementation object.

Action: This action must be performed after the working set object is bound.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25064: Variable {1} in RowSet {0} is not a where-clause parameter. It is of kind {2}.

Cause: A call was made to define or set a named where-clause parameter value. However, the named variable's 'kind' is not 'where'. That is, the variable is not a where-clause parameter.

Action: Make sure that the variable name is correct and that the named variable is a where-clause parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25065: Named where-clause parameter {0} does not belong to ViewObject {1}. It belongs to an object of type {2}.

Cause: An attempt was made to remove a named where-clause parameter. However, this where-clause parameter is owned by neither the RowSet nor the ViewObject. Therefore, the parameter cannot be removed.

Action: It is illegal to try to remove a named where-clause parameter that does not belong to either the RowSet or the ViewObject.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25066: View Object {0} is based on an Entity built from Row Set. For such a View Object, cannot include QUERY_MODE_SCAN_DATABASE_TABLES in its query mode.

Cause: An attempt was made to include QUERY_MODE_SCAN_DATABASE_TABLES in the View Object's query mode (through a call to setQueryMode()). However, this View Object can perform query only through Entity Object. Hence, QUERY_MODE_SCAN_DATABASE_TABLES is inappropriate.

Action: The View Object is probably based on an Entity, which in turn is based on a RowSet (EntityDefOverRowSet). It is illegal to use QUERY_MODE_SCAN_DATABASE_TABLES for a View Object built on top of an Entity which is built over a Row Set. Do not include QUERY_MODE_SCAN_DATABASE_TABLES in the setQueryMode() invocation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25067: Entity {0} has a subclass EO {1} and no discriminator. Therefore this base Entity cannot be used to create an Entity Row.

Cause: An attempt was made to create a new instance of an Entity Row. However, this Entity Definition has a subclass Entity Definition with no discriminator. That is, this Entity Definition should really be abstract.

Action: Typically in this situation, the base class should not instantiate any row. Use the subclass Entity to create the row
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25068: Entity {0} has a base EO {1} with no discriminator, but base EO has rows in its cache. Cannot populate both caches.

Cause: An attempt was made to create a new instance of an Entity Row. However, this Entity Definition is a subclass Entity Definition with no discriminator, and a base EO has a row already instantiated. A conflict exists because nothing discriminates this Entity from the base Entity.

Action: Typically in this situation, the base class should not instantiate any row. Use the subclass Entity to create the row
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25069: Row definition {0} has two sibling subclasses defs, {1} and {2}, but no discriminator to distinguish them.

Cause: Two sibling subclasses of a Row Definition are found, but the Row Definition has no discriminator. This condition is disallowed because when a row is either retrieved or created, the framework cannot determine the correct row class. That is, the hierarchy forks withouth a discriminator. The only situation whether subclassing is allowed without discriminator is when the tree is straight lined and only one of the classes in the hierarchy line is used to instantiate rows.

Action: Either define discriminator attributes, or do not create siblings in the row class hierarchy.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25070: Where-clause param variable {0} needs ordinal index array.

Cause: This view object of entity is using Oracle number style binding (:1, :2, ... binding, not named binding) or JDBC style (? binding). A variable of where-clause-param kind is found, but the extended int array that designates where the value should be bound is missing.

Action: When defining a variable for where-clause param in conjunction with a binding style which is not Oracle named binding, specify an int array that designates where the value should be bound.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25071: Applying List binding {1} with given set of values leads to multiple matching rows for a row of type:{0}, key {2}

Cause: ListBinding results in more than one matching row for the given set of mapping values. Only one matching row is expected.

Action: Provide a new set of mapping values that will end up in a single matching row or adjust the StructureDef metadata to allow defaulting to the first matching row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25072: Applying List binding {1} with given set of values leads to no matching row for a row of type :{0}, key {2}

Cause: ListBinding failed to find any matching row for the given set of mapping values.

Action: Provide a new set of mapping values that will end up in a single matching row or adjust the StructureDef metadata to allow defaulting to the first matching row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25073: Definition {1} of type {0} is hidden

Cause: Def object is hidden. An attempt was made to access a hidden def object.

Action: This particular operation is disallowed on a hidden def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25074: Definition {1} of type {0} is hidden in {2}, operation: {3}

Cause: Def object is hidden. An attempt was made to access a hidden def object in the specified container object.

Action: This particular operation is disallowed on a hidden def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25075: Definition {0} of type {1} is read-only. Cannot modify it

Cause: Attempting to modify or save data for a def object which is read-only.

Action: If the def object is shared, do not attempt to modify anything. If the def object is session scoped, do not modify it if there are running instances of that definition. If the def object is session scoped and is not being used by any running instance, mark it editable before modifying it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25076: Expression validator does not allow setting a value to source attribute:{0}.

Cause: Expression validator does not allow direct assignment of a value to an attribute. This is to avoid possible cycle of assignments/validations.

Action: Remove direct assignments. If assignment is necessary, verify there is no cycle, and then use constructs like 'source.MyVar = ..'.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25077: Name {0} not found in the given object: {1}.

Cause: An invalid name was passed in an expression.

Action: Fix the expression by passing in a correct name for a property.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25078: Key attribute {1} for {0} not populated

Cause: While building the where-clause statement for an entity row operation (e.g., fault-in, delete, or update), the named key attribute value is not populated.

Action: This entity row operation requires the key attributes to be populated. Make sure that all key attributes have values in them.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25079: The list of discriminator attributes for subclass {0} is different from that of the base {1}

Cause: In a subclass hierarchy of RowDefs, found a subclass RowDef whose discr attr list has more attrs than the base class. It is disallowed for a subclass to change discr attr list in the subclass hierarchy.

Action: Make sure that subclass RowDefs have the same set of discr attributes as the base class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25080: Definition name: {0} does not match the file in which it is loaded from: {1}

Cause: An attempt has been made to load a definition metadata file named differently from the name or id of the top level xml element in the file.

Action: The name should be a valid Java identifier with no spaces or punctuation. The name or id of the top level xml element in the file should match the file name.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25081: The new fetch size {0} passed into setFetchSize() for a view object {2} is invalid. It is smaller than the old value {1}.

Cause: The fetch size passed into <code>ViewObjectImpl.setFetchSize()</code> is smaller than the previous value. Fetch size of a view object cannot decrease.

Action: Specify a value which is bigger than the current value.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25082: Cannot change the access mode for the row set {0} because either the VO has more than one RS or the RS has more than one iterator.

Cause: An attempt has been made to change the row set's access mode from scrollable/forward-only to range-paging or vice versa. This is allowed only if the VO has one or no row set. Or, an attempt has been made to set the row set's access mode to forward-only, but this is allowed only if the row set has one or no iterator.

Action: Close other row sets or iterators before changing the access mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25083: Cannot create a secondary iterator on row set {0} because the access mode is forward-only or range-paging

Cause: An attempt has been made to create a new row set iterator on a row set whose access mode is either forward-only or range-paging.

Action: Creation of secondary row set iterator is allowed if the row set's access mode is scrollable.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25084: Cannot call last() on row set {0} because the access mode uses range-paging

Cause: An attempt has been made to jump to the last row on a row set whose access mode uses range-paging.

Action: Replace 'last' with 'setRangeStart' for the range-paging based access mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25085: The value being set for attribute {0} does not match the value derived from list binding {1}

Cause: An attribute value being set does not match the attribute value derived from a list binding. This typically happens in the following situations. First, suppose the user sets values for Deptno from 10 to 20 and Dname from ABC to DEF. If a list binding is triggered by Deptno and if it sets Dname to XYZ, the result is an inconsistent state where DEF does not match XYZ. In this situation, this exception is thrown. Second, suppose there is an EmpDept view object with Emp and Dept entity bases. Suppose Dept is reference and read-only and there is a list binding on Dept.Dname whose derived attribute is Emp.Deptno. If the user selects a new Dept through the dept name, a new Dept entity row is brought in (because a new Emp.Deptno is chosen). After this, the framework checks to make sure that the Dname coming from the new entity row matches the original selection from the list bindng. If they do not match, this exception is thrown.

Action: Make sure the list binding definition and attribute set values end up in a consistent result (i.e., the derived values from the list binding match the row's attribute values).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25086: Operation {1} cannot be performed until definition {0} is resolved.

Cause: An attempt was made to use a def object before resolving it. The def object must be resolved first.

Action: Make sure resolveDefObject() is called before this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25087: Cannot call getRowCount() on row set {0} because the access mode uses range-paging

Cause: An attempt has been made to get the row count of a row set whose access mode uses range-paging.

Action: Replace getRowCount() with getEstimatedRowCount() for range-paging based access mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25088: Persdef {0} has no static definition set

Cause: An attempt was made to perform an operation on a persdef that requires the static definition object, but the persdef has no static definition.

Action: Set the static definition object before attempting the operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25089: View object {0} attempted to fetch rows beyond the row limit

Cause: The view object attempted to fetch rows beyond a global row limit.

Action: If in a search region narrow down the results by providing more search criteria otherwise contact your system administrator.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25090: Attribute value {3} leads to duplicate keys for this entity type {1}.

Cause: An attempt was made to set an attribute value that leads to addition of a newly fetched or created entity to the cache, but tut this value makes the entity key same as another existing entity. The primary key must be unique for this entity type.

Action: Add more attributes to the key definition for the entity type, so that each row for this entity is uniquely identifiable. Or fix the key value so that this entity has a unique key identifier.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25091: View object {0} has no primary entity

Cause: An attempt was made to get the primary post state of a view row that has no entity usages.

Action: Only call this method on a view row with one or more entity usages
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25092: Programmatically accessible view object definition {0} is not found.

Cause: An attempt has been made to find a view definition using a short name and no corresponding custom or standard object can be found.

Action: Use a shortname that corresponds to the name of a custom object in a registered custom object base package or elsethe name of a standard object that has been registered to be programmatically accessible.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25093: Attribute {0} is being modified, while it is being validated causing an infinite loop.

Cause: An attempt was made within an expression or validation rule to update an attribute while that attribute is being validated.

Action: Remove the call to set the erring attribute value
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25094: Row finder {0} found more than expected rows on rowset {1}.

Cause: The number of rows found by a row finder exceeded the expected maximum.

Action: Ensure no more than the specified number of rows exists.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25095: Invalid bind name value pairs passed into row finder {0} on rowset {1}.

Cause: An attempt was made to invoke RowFinder execute method with an invalid AttributeList.

Action: Pass the correct value for AttributeList.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25096: Accessor {0} was not correctly resolved in view def {1}. Locate the resolution error and address the issue.

Cause: An attempt was made to access a view link or view accessors which was not correctly resolved.

Action: At the time of view link or view accessor resolution, something failed. Most likely, that failure was reported, but the application decided to continue to work with the view def with the problem. Locate the error reported during the initial accessor resolution attempt and address the issue.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25097: Attempt to modify sealed comp oper {0}. This is not allowed.

Cause: An attempt was made to modify a comp oper object which has been sealed.

Action: It is illegal to attempt to modify sealed comp oper. Check the code that is attempting edit and avoid this.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25150: The method {1} on class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to call a method not on the list of allowed methods.

Action: Add the method to the list of allowed methods in adf-config.xml
Level: 1

Type: ERROR

Impact: Security

JBO-25151: Accessing the {1} property on class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to access a property not allowed by methods on the list.

Action: Add the get and set methods corresponding to the property to the list of allowed methods in adf-config.xml
Level: 1

Type: ERROR

Impact: Security

JBO-25152: Calling the constructor for class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to call a constructor not on the list of allowed constructors.

Action: Add the constructor to the list of allowed constructors in adf-config.xml.
Level: 1

Type: ERROR

Impact: Security

JBO-25153: Calling the {1} method on class {0} is not permitted.

Cause: An attempt was made within an untrusted expression to call a constructor not on the list of allowed constructors.

Action: Use an alternate method.
Level: 1

Type: ERROR

Impact: Security

JBO-25154: Calling the {1} function is not permitted.

Cause: An attempt was made within an untrusted expression to call a method which is on the list of blacklisted methods on scripts.

Action: Rename the method, or call it from a trusted context.
Level: 1

Type: ERROR

Impact: Security

JBO-25155: Defining an additional method is not permitted.

Cause: An attempt was made within an untrusted expression to define an additional method.

Action: Create the same logic without the use of an embedded method, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25156: Defining an additional class is not permitted.

Cause: An attempt was made within an untrusted expression to define an additional class.

Action: Create the same logic without the use of an embedded class, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25157: Calling the {1} method on class {0} is not permitted when used in a static context.

Cause: An attempt was made within an untrusted expression to call a method which is blacklisted when used in a static context.

Action: Instead use the method on an instance of the class.
Level: 1

Type: ERROR

Impact: Security

JBO-25158: Accessing the {1} property is not permitted.

Cause: An attempt was made within an untrusted expression to use a property on the list of blacklisted properties.

Action: Instead access the property with an allowed method.
Level: 1

Type: ERROR

Impact: Security

JBO-25159: Accessing the {1} property, when used in a static context on class {0}, is not permitted.

Cause: An attempt was made within an untrusted expression to use a property in a static context on the list of blacklisted properties.

Action: Instead access the property with an allowed method, or use in an instance context.
Level: 1

Type: ERROR

Impact: Security

JBO-25160: Defining a method pointer is not permitted.

Cause: An attempt was made within an untrusted expression to define a method pointer.

Action: Create the same logic without the use of a method pointer, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25161: Calling the {1} function is not permitted.

Cause: An attempt was made within an untrusted expression to call a method which is not allowed on scripts.

Action: Rename the method, or call it from a trusted context.
Level: 1

Type: ERROR

Impact: Security

JBO-25162: Using the Java field operator (.@) is not permitted.

Cause: An attempt was made within an untrusted expression to directly access a Java field via '.@'.

Action: Create the same logic without the use of the '.@' operator, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Security

JBO-25170: Expression timed out.

Cause: An untrusted expression exceeded the maximum time allotted for a run.

Action: Break the task up into multiple tasks, increase the timeout value, or mark the script as trusted.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25171: Expression exceeded the maximum number of new view instances ({0}).

Cause: An untrusted expression exceeded an allowed use of resources.

Action: Change your expression to use fewer resources.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25180: Exception in expression "{0}": {2}

Cause: An exception has occurred within a Transient Expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25181: Exception in expression "{0}" recalc expression {1} : {2}

Cause: An exception has occurred within a Recalc Expression.

Action: Examine the details to find the root cause, and modify the Expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25182: Exception in expression "{0}" validation rule {1} : {2}

Cause: An exception has occurred within a Validation Rule expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25183: Exception in expression "{0}" trigger {1} : {2}

Cause: An exception has occurred within a Trigger expression.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25184: Exception in expression "{0}" object function {1} : {2}

Cause: An exception has occurred within an Object Fucntion.

Action: Examine the details to find the root cause, and modify the function to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25185: Exception in expression "{0}" global function {1} : {2}

Cause: An exception has occurred within an Object Fucntion.

Action: Examine the details to find the root cause, and modify the function to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25186: Exception in expression "{0}" of unknown type {1} : {2}

Cause: An exception has occurred within an expression of unknown type.

Action: Examine the details to find the root cause, and modify the expression to avoid the root exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25187: Duplicate signature for method "{0}" when attempting to add to {1}

Cause: An attempt to add two methods of identical signature to an Object or Global Function.

Action: Change the method signatures to be different, and re-add the function.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25200: Application module is not connected to a database.

Cause: The application module is not connected to the database.

Action: Provide a valid set of connection credentials to connect to a database.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25201: A database connection already exists.

Cause: An attempt was made to reestablish a database connection.

Action: Disconnect the current database connection before trying to reestablish the JDBC connection.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25221: Method {0} not supported

Cause: Attempting to call a method that is either not implemented or not supported.

Action: This method is not available on the called object. E.g. <code>setAttribute()</code> in <code>oracle.jbo.Key</code> class is not implemented and will throw this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25222: Unable to create application module.

Cause: The application module was typically not created for one of the following reasons: 1. Business components deployed in local mode were not found on the classpath. 2. Unresolved classes existed on the server. 3. Java2 permissions were not granted. 4. Java pool size was too small.

Action: Depending on the cause, chose from the following actions: If business components are deployed in local mode, they might not be on the classpath. <br>If this is the cause of the error, the exception will usually be followed by a different exception, JBO-25002: NoDefException. If this occurs, try the following: Make a library for the business components. Add the library to the client's project properties. Include the library on the 'libraries' page when creating a deployment profile for the client (whether the client was a web application or a command-line application). Copy the library with the client to the target platform (whether the client was a web application or a command-line application). Include all the copied files (including the library) when setting the classpath on the target platform. There might be unresolved classes on the server. Try the following procedure to resolve any unresolved classes on the database. In the System Navigator, right-click the JDBC connection used to deploy the Business Components project. Choose Invoke SQLPlus from the context menu. Copy and paste the following SQLPlus script into the SQLPlus window. set termout off set echo off set heading off set pages 999 set linesize 2000 set feedback off select 'alter java class "'|| replace(dbms_java.longname(object_name),'/','.')||'" resolve;' from user_objects where object_type='JAVA CLASS' and status = 'INVALID' spool C:\temp\resolve.sql / spool off set echo on set termout on @C:\temp\resolve.sql There might be missing Java2 permissions. If this is the cause of the error, there will be permissions errors in the database trace file. To correct the problem, see the help topic 'Granting Permissions on a Business Components EJB' for information on granting Java2 permissions. Note: The location of the database trace file varies from installation to installation, but in a default Windows NT installation, the file will be in the directory ORACLE_HOME\admin\orcl\ udump and will have the form orclnnnn.trc. The Java pool size might be too small Business Components for Java deployed as EJBs work best with a Java pool size of at least 50MB. Edit the init.ora file and check the <code>java_pool_size</code> parameter. If it is under 50MB, change it, restart the database, and try the connection again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25223: Cannot create multiple root application modules.

Cause: When business components are running inside JServer, only one root application module can be created. This is because JServer (already) provides one transaction context.

Action: It is illegal to attempt to create multiple root transactions when running inside JServer.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25224: Could not disconnect and retain application module state because database state exists for current connection.

Cause: Trying to retain the application module state during a transaction disconnect failed.

Action: The disconnect and retain application module state target requires that no database state exist before the transaction connection is closed. Examples of database state include open database cursors in non-forward only view objects, database locks, and uncommitted database changes. The client should clean up this state by fetching or resetting any open view objects and committing any uncommitted changes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25226: Application module definition {0} contains recursive AM reference.

Cause: This application module definition contains recursive references to child application modules. For example, if application module definition appMod1 contains a child application module of appMod2, and appMod2 contains appMod1, this error will be raised.

Action: Remove recursive application module definition references.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25227: Recursive view links found. Master-detail chain: {0}.

Cause: The user has attempted to create a view link (in an application module) that will result in a recursive loop of view links. The error message should show a chain of recursive master-detail relationships.

Action: If a static view link is causing the recursion, remove the view link from the application module. If a dynamic view link is causing the recursion, remove the code that creates the recursive view link.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25228: Unable to register a database change notification request for {0} view object

Cause: The View Object that has auto refresh turned on failed to register an Oracle database change notification request.

Action: Ensure that the database user is granted CHANGE NOTIFICATION privilege. Look at the exception details for further troubleshooting.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25229: Unable to unregister a database change notification request for {0} view object

Cause: The View Object that has auto refresh turned on failed to unregister an Oracle database change notification request.

Action: Look at the exception details for further troubleshooting.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25230: XML document {0} has no stream to save

Cause: An attempt was made to save XML document, but the document has not been persisted (most likely saveXMLContents() is called without a call to writeXMLContents()).

Action: Call writeXMLContents() first.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25301: Application module {0} is not a root app module but has no parent

Cause: While traversing the parenthood chain for application modules, a child application module was found with no container (parent) application module.

Action: If this application has added custom business component classes, the application code might be attempting to access a child application module before it is fully initialized. If this is not the case, this error probably represents some internal error in the framework, in which case contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25302: Component object {0} has no parent

Cause: A business component is found without a container (parent) application module.

Action: If this application has added custom business component classes, the application code might be attempting to access a business component before it is fully initialized. If this is not the case, this error probably represents some internal error in the framework, in which case contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25303: Cannot clear entity cache {0} because it has modified rows

Cause: A dirty entity cache cannot be cleared. The client asked to clear an entity cache but some rows in the entity cache have been modified. An entity cache with modified rows cannot be cleared.

Action: Do not attempt to clear an entity cache with modified rows in it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25306: Design-time attribute {0} of type {1} could not be persisted

Cause: Could not persist a design-time attribute into the XML file.

Action: Identify the offending design-time attribute and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25307: XML file not open

Cause: XML file is not open.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25308: The primary key of an existing entity bean cannot be modified for entity facade {0}.

Cause: An attempt was made to modify the primary key of an existing entity bean. This is disallowed by EJB.

Action: Do not modify primary key of an old (not-new) entity bean.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-25309: The primary key of an entity bean cannot be null for entity facade {0}.

Cause: The primary key of an entity bean is null. This is disallowed by EJB.

Action: Set the primary key to be not null.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26000: A Generic exception occurred during loading Customizations.

Cause: Metadata objects failed to load due to unexpected or corrupt data in the XML file.

Action: Verify that the XML metadata for various components is valid.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26001: XML File not found for the Container {0}

Cause: Could not open the named XML file for reading.

Action: Try the following: Make sure that the file is present. In particular, if the file is to be found in a Zip/JAR file, make sure that the Zip/JAR file is included in the CLASSPATH. This error is also reported if the name of the XML file does not match the object Name specified in the XML file. If the file system supports case insensitive file names (e.g., Windows NT), make sure that the file name matches the object Name in the XML file in case-sensitive fashion. For a JPX file, this error is reported if the JPX file is missing the JboProject XML tag. Check the JPX file to make sure that the valid tag is in there. One XML file might be extending another XML file (specified by the Extends element in this XML file). This error is reported if the base XML file is not found. When loading the XML file for a package (JboPackage tag), this error is reported if some unexpected error occurs while loading a contained object. In all of the above cases, a more descriptive message might be printed on Diagnostic. To see these messages, run the application with Diagnostic turned on, as in 'java -Djbo.debugoutput=console ...', to see Diagnostic messages.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26002: Error Parsing the XML file "{0}".

Cause: Some XML parsing exception (<code>oracle.xml.parser.v2.XMLParseException</code>) was thrown.

Action: The XMLParseException information is output to Diagnostic. To see diagnostic messages, run the application with diagnostic turned on, for example 'java -Djbo.debugoutput=console ...'
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26003: Mismatch in the attribute indices declared in Java versus the indices in the definition for entity {0}.

Cause: An error occurred while loading entity object definitions. An attribute index in the Java class for this entity has a mismatch with the index in the definition, or an attribute index is missing in the Java class.

Action: Ensure that the indices of attributes in the definition for this entity match the indices defined in the Java class for this entity.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26004: A recursive base definition is found while attempting to set the base definition of {0} to {1}.

Cause: An attempt was made to set the base definition of another definition object, e.g., setting B's base definition to A (i.e., B Extends A). However, A already extends B. Setting a recursive (circular) subclassing relationship among definition objects is illegal.

Action: Review the subclassing hierarchy of the definition objects and correct errors.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26005: FetchMode must be either FETCH_AS_NEEDED, FETCH_ALL or FETCH_DEFAULT. View object {0}

Cause: The fetch mode specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'FetchMode'. Make sure that the value for that element is valid. Valid values are: 'FETCH_AS_NEEDED', 'FETCH_ALL', and 'FETCH_DEFAULT'
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26006: FetchSize must be a positive integer. View object {0}

Cause: The fetch size specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'FetchSize'. Make sure that the value for the element is a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26007: MaxFetchSize should be MAX_FETCH_UNLIMITED, MAX_FETCH_DEFAULT or integer. View object {0}

Cause: The maximum fetch size specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'MaxFetchSize'. Make sure that the value for the element is a non-negative integer, or 'MAX_FETCH_UNLIMITED', or 'MAX_FETCH_DEFAULT'. A MaxFetchSize of 0 is the same as MAX_FETCH_UNLIMITED.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26008: Could not resolve reference to "{0}".

Cause: A problem is found in resolving a view link definition or an association. In case of a view link, this error might be caused by the fact that the source or destination view object cannot found. Or, if the view link ends have attribute names, this error might indicate that the named attributes cannot be found. Similarly, for an association, this error indicates that either source or destination entity object or attributes involved in the association cannot be found.

Action: Make sure the XML definition for the view link/association has correct view object/entity object/attribute names.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26009: Serialized file "{0}" is invalid. The root object is not a Business Component object.

Cause: This error occurs if the application uses meta object serialization files (.ser files) instead of XML files. It indicates that after the .ser file was deserialized, the top level object returned from deserialization was not an instance of oracle.jbo.server.xml.JboElementImpl.

Action: Repair the corrupt .ser file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26010: Invalid Entity Attribute Name "{1}" specified for the View Attribute "{0}"

Cause: Entity attribute name in the view definition XML file is invalid or is not found.

Action: Make sure that the entity name is valid. Also, check to make sure that the named attribute does exist in the entity object. The entity object is identified by the EntityUsage element.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26011: SQLType not specified for the View Attribute "{0}"

Cause: Attribute definition found in XML file is invalid. It is missing SQLType value.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26012: Invalid View Link Definition "{0}". View Link must have two ViewLinkDefEnds.

Cause: The view link definition in the XML file is missing either the source or destination view link end. For a view link XML file, two elements named ViewLinkDefEnd should be found.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26013: Naming Exception occurred while looking up the object "{0}".

Cause: Meta object name passed for lookup is invalid.

Action: Normally, the meta object name is a dot-separated name of the meta object. For an entity object named Emp in package1.example, the correct name would be <code>package1.example.Emp</code>. To correct, locate where the invalid name is coming from (could be meta object names mentioned in an XML file, or the name of the project, etc.) and change the name to a valid one.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26015: View object {0} does not include a discriminator column {2} of entity base {1}.

Cause: A view definition does not include a discriminator column of an entity base. If an entity base has discriminator columns, it must include all of them in the view object's attribute mapping.

Action: Change the view definition to include discriminator column attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26016: Cannot set user query to view "{0}" because it is a destination in a view link

Cause: An attempt was made to call 'setQuery()' on a detail view object in a master detail view link.

Action: Do not call setQuery() if the view object is a detail.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26017: Association or view link definition {0} has an invalid attribute list.

Cause: The association or view link definition has a missing or invalid attribute list.

Action: Correct the error(s) in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26018: Entity {0} cannot be posted to the database because it has no attributes set.

Cause: An attempt was made to post a row with no attribute set. Some databases (Oracle Database in particular) do not allow an INSERT statement with no VALUE specified.

Action: Set some attributes on the row before attempting to insert it into the database.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26019: Attempting to remove a parent entity without removing all children entities

Cause: Attempting to remove a master which has detail entities. In the case of a composition, a master cannot be removed if it has details.

Action: Remove all the details of this master by accessing the details via an association and removing all of them.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26020: Attempting to insert row with no matching EO base

Cause: The application code tried to take a row from one row set (or view object) and insert it into another row set (view object). In response, the framework will make a copy of the row in the new row set. This new row will share references to the underlying entity objects. However, if the source and destination row sets do not share any entity object bases at all, this operation will fail as it does not find any entity rows to share.

Action: When attempting to take a row from one row set and insert into another, make sure that they share at least one entity object base.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26021: NullPointerException while parsing XML file "{0}". Perhaps missing DTD file?

Cause: A NullPointerException was thrown while parsing an XML file. A possible cause for this is that the DTD file is missing (oracle.jbo.dtd.jbo.dtd).

Action: Make sure the appropriate DTD file is present.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26022: Custom class {0} cannot be found.

Cause: A custom class could not be found and loaded. The custom class might be for a component (for example, view object), a definition (for example, view definition), or a row (for example, view row or entity row).

Action: Make sure that the named class is reachable from the CLASSPATH. The detail exception (if present) provides more specific reasons why the attempt to locate and load the custom class failed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26023: Custom class {0} is not assignable to {1}

Cause: Custom class was found and loaded, but it is invalid in that it is not assignable to a framework (super) class.

Action: Make sure that the custom class subclasses the appropriate framework (super) class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26024: An error occurred while creating InitialContext

Cause: An error occurred while creating initial context. This error usually carries a detail exception which will give further information on the cause of the error.

Action: When running inside JServer, make sure that the database user (schema) has the setContextClassLoader permission. To grant this, the database system administrator can invoke the following PL/SQL procedure: EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.lang.RuntimePermission', 'setContextClassLoader', null);
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26025: An error occurred while trying to get System properties

Cause: An error occurred while trying to get System properties. Specifically, System.getProperties() call failed.

Action: When running inside JServer, make sure that the database user (schema) has the proper property permission. To grant this, database system can invoke the following PL/SQL procedure: EXEC DBMS_JAVA.GRANT_PERMISSION('&&1', 'SYS:java.util.PropertyPermission', '', 'read');
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26026: An error occurred while loading properties from a properties file {0}

Cause: An error occurred while trying to get load properties.

Action: Check to see if the named properties file contains valid Java properties.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26027: Unable to find resource. {0}

Cause: Unable to find a resource

Action: Check to see if the resource exists and the framework code has adequate permissions to load the resource.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26028: View object {0} does not include a primary key attribute {2} of entity base {1}.

Cause: A view definition does not include a primary key attribute of an entity base. When a view object uses an entity as one of its entity bases, it must include all primary key attributes of the underlying entity object.

Action: Change the view definition to include all primary key attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26029: Could not find and load the type map class {0}

Cause: Custom type map class could not be found and loaded.

Action: Make sure that the named class is reachable from the CLASSPATH. If jbo.TypeMapEntries property is specified, make sure that the property value is correct. Also, though unlikely, this might be caused by an improper implementation of SQLBuilder where it is returning an incorrect value for type map class name. The detail exception (if present) will provide more specific reasons why the attempt to locate and load the custom class failed.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26030: Failed to lock the record, another user holds the lock.

Cause: This row has already been locked by another user or transaction.

Action: Try locking the row again and the operation should succeed after the other user or transaction has released the lock.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26031: Association end {0} of assoc {1} invalid for entity base {2} in view object {3}.

Cause: Problem in secondary entity base definition in view definition. The named entity base is supposed to use the named entity association end to join it with another entity base, but, when resolved with the association definition, the association end does not resolve to the same entity. For example, suppose one builds a view object with Dept and Emp. Emp is supposed to join with Dept using the EmpEnd of the DeptEmp association. For such a view definition, the framework verifies that EmpEnd indeed is from Emp entity. If EmpEnd was from another entity, say Person (or Dept), it would not be correct to use that association end to perform join.

Action: Most commonly, this is caused by incorrect information in the view object XML file. Make sure that the association end for the named entity usage is not pointing at the wrong end of association.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26032: Operation {0} is invalid for a ViewCriteria or ViewCriteriaRow.

Cause: The attempted operation is invalid for a ViewCriteria or ViewCriteriaRow.

Action: Remove code that attempts this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26033: Cannot find Application Data Model with name :{0}

Cause: Cannot find application definition of the given name

Action: Fix the application definition name or make the appropriate .cpx file available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26034: Cannot find Configuration with name :{0}

Cause: Cannot find configuration information in the application definition file

Action: Fix the Configuration name or make the appropriate .cpx file available in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26035: Secondary entity usage {0} is missing parts of association description.

Cause: A view definition is found with an entity usage definition where the secondary entity usage's association description is incomplete.

Action: Examine the view object's XML file. A secondary entity usage's association description should have the following elements: 'Association', 'AssociationEnd', and 'SourceUsage'. Check to see if any of these are missing.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26036: The configuration of meta object {0} causes recursive substitution.

Cause: An attempt was made to set up meta object substitution that leads to recursion. For example, consider a substitution where C substitutes B, and B substitutes A, and A substitutes C. This results in a recursive substitution and will cause this error.

Action: Review the meta object substitution and correct errors.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26037: Cannot find matching EO from discriminator columns for view object {0}, entity base {1}, discr value {2}.

Cause: While creating a new view row, the system found an entity object base with discriminator column attributes. However, the discriminator column values coming from the view row do not match any of the entity objects (the entity for the entity object base or any of its extended entities).

Action: Make sure that the view row discriminator column values match one and only one entity object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26038: Cannot find an entity usage for entity {1} in view link definition {0}, view link end {2}.

Cause: The view link definition is based on an entity association. One of its ends specifies the named entity definition, but the view definition for that view link end does not have an entity usage for that entity definition.

Action: Correct the error in the view link definition (XML file). In particular, check to see if the view link source and destination are not switched with those of the entity association.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26039: View object {0} does not include an alternate key attribute {2} of entity base {1}, entity key {3}.

Cause: A view definition does not include an alternate key attribute of an entity base. When a view object uses an entity as one of its entity bases, and when it defines a view object level alternate key using one of the entity alternate keys, it must map the entity attributes that make up the alternate key.

Action: Change the view definition to include all necessary alternate key attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26040: Failed to post entity {1} to database during "{0}" : SQL Statement "{2}".

Cause: Some database error occurred while posting (writing) an entity to the database in JDBC batch mode. This error normally carries a detail exception from the database which will give further information about the database failure.

Action: Look at the details of the exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26041: Failed to post data to database during "{0}": SQL Statement "{1}".

Cause: Some database error occurred while posting (writing) an entity to the database. This error normally carries a detail exception from the database which will give further information about the database failure.

Action: Look at the details of the exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26042: Failed to generate REF and OID on entity {0}.

Cause: A database failure occurred while trying to generate an object ID (OID) and object reference (REF). When a new row is created on an entity which maps to an Oracle object table, an OID and REF for the new row are generated. This executes a SQL statement like select a.oid, make_ref(table-name, a.oid) ... Somehow, this statement is failing.

Action: Ensure that : The Oracle database version is correct. The table in question is an object table. This error normally carries a detail exception from the database, which will give further information about the database failure. Take a look at the detail exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26043: REF and OID not supported by this SQLBuilder on entity {0}.

Cause: An attempt was made to generate an object ID (OID) and/or a reference (REF) on a database system that does not support Oracle objects.

Action: Do not try to create OID or REF on a database system that does not support Oracle objects.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26044: Error while getting estimated row count for view object {0}, statement {1}.

Cause: The application tried to get an estimated row count (getEstimatedRowCount()) on a row set. While building the appropriate query statement, executing it, and retrieving the estimated count, an error occurred. This error is accompanied by the SQL statement that caused the error. Also, it normally carries a detail exception from database, which will give further information about the database failure.

Action: Take a look at the SQL statement and the detail exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26045: Failed to generate PK-Based REF on entity {0}.

Cause: A database error occurred while trying to generate an object ID (OID) from the primary key. This operation is valid only if the table in question is an object table and if the table specifies that the reference (REF) is PK based.

Action: Ensure that: The Oracle database version is correct. The table in question is an object table. The object table uses a PK-based REF. This error normally carries a detail exception from database which will give further information about the database failure. Take a look at the detail exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26046: PK-Based REF not supported by this SQLBuilder on entity {0}.

Cause: An attempt was made to generate Oracle o8 object ref from a non-Oracle database SQLBuilder. This is not supported.

Action: Make sure that the correct SQLFlavor (i.e., SQLBuilder) is being used for the application and switch to the right one.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26047: LOCK_OPTUPDATE mode update operation missing change indicator value: Entity {0}, key {1}.

Cause: An attempt was made to update a row in LOCK_OPTUPDATE mode and the change indicator attribute value is not present.

Action: Look at the attribute mapping of the View Object that read in this Entity row and make sure that the View Object includes the change indicator attribute. The LOCK_OPTUPDATE mode requires the value to be present.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26048: Constraint "{2}" is violated during post operation "{0}" using SQL statement "{1}".

Cause: A constraint violation occurred in the database while posting (writing) an entity to the database. This error carries a detail exception from the database which will give further information about the database failure.

Action: Fix the cause for the constraint violation. Look at the details of the exception and address the database problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26049: An error occurred during loading definition {0}.

Cause: Metadata objects failed to load due to unexpected or corrupt data in the XML file.

Action: Verify that the XML metadata for various components is valid.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26050: An error occurred while writing personalization definition {0}.

Cause: An I/O error occurred while writing personalization definition.

Action: Check the detail I/O exception and make necessary correction.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26051: Unrecognized XML element tag {1} found in meta object {0}.

Cause: The element tag of the XML file is not recognized.

Action: Examine the XML file and make sure that the element tag is one of the recognized ones.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26053: Invalid association or view link definition "{0}". Invalid unbound attribute list.

Cause: An association or view link definition end has an invalid unbound attribute list. This error is raised if the unbound attribute is not one of the association/view link end attributes.

Action: Correct the error(s) in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26054: Invalid version number for {0}. Require {1} or greater, but found {2}.

Cause: The XML document is either missing the version number or has a version number which is lower than the required version number.

Action: Check to see if the XML document has gone through a proper migration process. If not, migrate the application.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26055: Failed to delete XML document {0}.

Cause: An attempt was made to delete an XML document from disk, but this operation failed.

Action: When running with MDS, make sure that the metadata store supports the delete operation. Check the detail exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26056: Multiple occurrences of XML element {1} found in {0}. Only one expected.

Cause: Multiple occurrences of an element were found in the XML document when only one was expected.

Action: Examine the XML document and see which element shows up mutiple times. If the issue looks like a problem in the framework's persistence code, report it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26057: Recursive entity references found in view def {0}. Entity refs: {1}

Cause: An attempt was made to create a view definition whose entity references have a cycle in it. For example, a view definition contains two entity references E and F, where E's source reference is F, and F's is E.

Action: Review your code that builds the view def. Make sure that entity references do not have a recursion in it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26058: Cannot define view link {0} in application module {1}. The view object {2} is in application module {3} and the view link''s application module is not a child of the view object''s application module.

Cause: An attempt was made to establish a data model view link in an application module, but either the master or the detail view object is in an AM which is not the same AM as the view link's, or is not a parent of the view link's AM.

Action: When creating a data model VL, the VL's AM must be the same as the VO's, or must be a child (nested) AM of the VO (for both master and detail).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26059: Invalid View Link Usage "{0}". Either the source "{1}" or the destination "{2}" is not defined.

Cause: The ViewLink Usage is not correctly defined.

Action: Specify both source and destination for the ViewLink Usage.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26060: Error while registering JDBC driver.

Cause: A SQLException occurred while trying to register a JDBC driver.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26061: Error while opening JDBC connection.

Cause: A SQLException occurred while trying to open a JDBC connection.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26062: Error while closing JDBC connection.

Cause: A SQLException occurred while trying to close a JDBC connection.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26064: Error while closing JDBC statement.

Cause: A SQLException occurred while trying to close a JDBC connection.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26065: Error during commit.

Cause: A SQLException occurred during the commit phase of this transaction.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26066: Error during rollback.

Cause: A SQLException occurred during the rollback phase of this transaction.

Action: Fix the underlying SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26067: Failed to add JDBC connection to the connection pool, connection pool is full.

Cause: An exception occurred while adding a JDBC connection to a pool that was already full.

Action: Modify the class that is using the pool to check the pool size before adding a new connection to the pool.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26068: Failed to return JDBC connection to the connection pool, connection does not belong to the pool.

Cause: The user attempted to return a connection to a pool that was not responsible for managing that connection.

Action: Modify the class that is using the pool to ensure that the connection belongs to the pool before returning the connection to the pool.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26069: Client request was timed out while waiting for a connection to be returned to the connection pool.

Cause: A client request was timed out while waiting for a connection to be returned to the pool.

Action: Increase the maximum pool size in order to accommodate 2x the maximum expected active request size.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26070: Column definition retrieval from JDBC failed on view object {0}.

Cause: A SQLException occurred while setting up metadata JDBC statement.

Action: Fix the underlying SQLException. There might be a datatype mismatch between the attributes of the view object and columns in the SQL for it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26071: Access mode {1} is invalid. View object {0}

Cause: The access mode specified in the view definition XML file is not valid.

Action: Check the content of the XML file for the view definition. Look for an XML element named 'AccessMode'. Make sure that the value for that element is valid.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26072: Another user changed the document {0}.

Cause: The client requested to write metaobject, but the metaobject document was updated by another user.

Action: This exception carries the most up to date def object. Resolve the differences and retry write.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26073: Document {0} has no MDS key.

Cause: The client requested to write metaobject, but the metaobject's MDS key is null and so we cannot perform the consistency check.

Action: An existing definition object's MDS key should not be null. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26074: MDS detected another user changed the document {0} since the mutable MO was obtained.

Cause: The client requested to write metaobject, but the metaobject document was updated by another user. The difference between this error and <code>EXC_PERS_DOC_INCONSISTENT</code> is that this error is detected by MDS between <code>getMutableMO()</code> and <code>flushChanges()</code>. <code>EXC_PERS_DOC_INCONSISTENT</code> is raised by an MOKey check.

Action: This exception carries the most up to date def object. Resolve the differences and retry write.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26075: Document {0} exists. Another user just created the same doc.

Cause: The client requested to create a new document. While creating and flushing the MDS MO, MDS threw a document-exists-exception, which means that another user just created the same document.

Action: Retry creating the document.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26076: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was deleted by another user.

Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was deleted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26077: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was deleted by another user.

Cause: During object merge, found a metadata element which was marked for update by the current user, but was deleted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26078: Merge for definition {0} failed for elem {1}. Inserted elem [{2} -> {3}] was inserted by another user.

Cause: During object merge, found a metadata element which was marked for insertion by the current user, but was inserted by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26079: Merge for definition {0} failed for elem {1}. Updated elem [{2} -> {3}] was updated by another user.

Cause: During object merge, found a metadata element which was marked for update by the current user, but was updated by another transaction committed or published by another user.

Action: Resolve this metadata merge conflict.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26080: Error while selecting entity for {0}

Cause: An unexpected exception occurred while executing the SQL to fetch data for an entity instance or lock it.

Action: Fix the cause for the SQLException in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26081: Error while getting datum for attribute {1} in {0}

Cause: A SQLException occurred when converting data from JDBC to <code>oracle.jbo.domain.Struct</code> attributes.

Action: Fix the conversion errors as suggested in SQLException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26083: Comparison operator {0} has a string code for its description, but the message bundle class cannot be found.

Cause: A comparison operator was specified with string code, but the message bundle class could not be loaded. When specifying a string code for translatable operator description, the framework first checks to see if the operator specification includes a message bundle class name. If so, it attempts to find the string in that message bundle. If not, then the framework tries to find the string in the owning object's (either view object or entity object) message bundle. If both fail, this error is raised.

Action: Make sure that the comparison operator specification is correct in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26084: Invalid association definition "{0}". Association must have two AssociationEnds.

Cause: The association definition in the XML file is missing either the source or destination association end. For an association XML file, two elements named AssociationEnd should be found.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26085: Missing association name in EO-exists validator {0} of {1}.

Cause: The EO-exists validator is missing the association name in its definition.

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26086: Association attributes do not match the destination EO''s primary keys in EO-exists validator {0} of {1}.

Cause: The EO-exists validator's source side attribute list does not match the desination EO's primary keys. For example, suppose there is a PurchaseOrder EO which includes an EO-exists validator to Customer EO. PurchaseOrder EO is using association CustToPurch to validate. In this case, the association attribute list on the PurchaseOrder side match with Customer's PK exactly (order does not matter--they must equal as sets).

Action: Correct the error in the XML file.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26087: The master end accessor {0} of composition assoc {1} has an invalid attribute kind: {2}.

Cause: The composition association's master end has attribute kind of RowSetIterator (cardinality -1 or > 1), i.e., it returns an iterator, rather than a row.

Action: Master end in an association must return a single row. Thus, the attribute kind must be Row (cardinality = 1).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26088: An attempt was made to edit property {1} of def object {0}, but this property may not be edited.

Cause: An attempt was made to edit a def object, but this property or object may not be edited.

Action: Do not try to edit this property. Instead, consider deleting and creating the def object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26100: An error occurred after commit was performed.

Cause: An exception occurred in the afterCommit notification phase of the transaction.

Action: Verify the exception in the details of this exception. Fix the failing afterCommit() overridden methods in the entities or transient TransactionListener objects registered with the transaction to listen into the commit/rollback cycle.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26101: An error occurred after posting was performed.

Cause: An exception occurred in the afterPost phase of the transaction.

Action: Verify the exception in the details of this exception. Fix the failing afterPost() overridden methods in the entities or transient TransactionPostListener objects registered with the transaction to listen into the post cycle.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-26102: An error occurred after rollback was performed.

Cause: An exception occurred in afterRollback notification phase of the transaction.

Action: Verify the exception in the details of this exception. Fix the failing afterRollback() overridden methods in the entities or transient TransactionListener objects registered with the transaction to listen into the commit/rollback cycle.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27001: Association attribute {2} included in {0} {1} is not updatable

Cause: This association attribute is marked readonly.

Action: Cannot modify the value of the association attribute as it is marked readonly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27002: Entity validation with key {1} failed in entity object {0}

Cause: A custom validation rule failed to validate an attribute value.

Action: Fix the attribute value so that it passes the custom validation rule.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27003: Validation of rows in view object {0} failed

Cause: Modified or new entities in this view object failed to validate.

Action: Fix the failing entity values and revalidate the view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27004: Attribute set for {2} in entity {1} failed

Cause: Attempting to modify a read-only entity-attribute.

Action: Do not modify a read-only attribute value.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27005: Validation of rows in application module {0} failed

Cause: Modified or new entities within this application module or nested application module failed to validate.

Action: Fix the failing entities and then revalidate this application module.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27006: Validation failed because attribute {2} is not found in {0} {1}

Cause: An attribute cannot be found by the given name during validation.

Action: Entity metadata could be corrupt as there is an attribute which is to be validated but no definition could be found for that attribute in the metadata.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27007: Validation of a view row in view object {0} failed

Cause: Attempting to validate a ViewRow failed.

Action: Fix the failing entities or attributes as found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27008: Attribute {2} in view object {1} cannot be set.

Cause: An attempt was made to modify a view row attribute that is read-only.

Action: Modify the updatable setting of the view attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27009: Batch set of attributes in view object {1} failed

Cause: Attempting to validate entities and attributes failed during validation of buffered attributes in Deferred Validation mode. (Not available in 3.x)

Action: Fix the failure cases.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27010: Attribute set with value {3} for {2} in {1} has invalid precision/scale

Cause: For strings, the length of the string value provided for an attribute is more than the max-length this attribute expects. For Numeric values, the length of the value (in string form) is more than what the attribute expects.

Action: Fix the attribute value with respect to the precision and scale information for the failing attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27011: Attribute set with value {3} for {2} in {1} failed

Cause: A validation rule for an attribute failed either due to an unexpected exception in validating the attribute with that rule, or due to failure in evaluating the NOT operation on the rule.

Action: Fix the attribute value so that it validates against the failing rule.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27012: Row validation method {2} failed for row with key {1} in {0}

Cause: The custom method validator attached to an entity returned false, indicating a failure in the validation for that entity.

Action: Fix the cause for failure in the custom validation method for this attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27013: Attribute set validation method {4} failed for attribute {2} in {1}

Cause: The custom method validator attached to an attribute returned false indicating a failure in validation for that attribute in the custom method.

Action: Fix the cause for failure in the custom validator method for this attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27014: Attribute {2} in {1} is required.

Cause: The attribute value cannot be null as it has been marked mandatory.

Action: Provide non-null values for mandatory attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27015: {0} contained entity/s still invalid

Cause: In validating a master, some child entities were found that could not be validated. This occurs only in the case when there is a composition association between the master and detail entities.

Action: Fix the attribute values in the child entities so that they are valid when the child entities are validated by the master
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27016: Invalid attribute kind for column {0}.

Cause: An unexpected attribute kind found in the definition for a view object.

Action: Fix the attribute kind information in the xml-metadata definition for attributes in this view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27017: The primary key for Entity {0} could not be determined.

Cause: While loading the metadata definition for this entity, there was no attribute marked as the primary key.

Action: Set at least one attribute as the primary key for this entity type, so that entities of this type can be uniquely identified.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27018: Attribute set with value {3} for {2} in {1} failed because of type mismatch

Cause: The type of attribute value provided as an argument to the set() method for this attribute is not an instance of the Java type that this attribute expects.

Action: Convert the argument to a proper Java type, such that it is an instance of the Java type that this attribute expects.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27019: The get method for attribute "{2}" in {1} cannot be resolved.

Cause: An unexpected exception occurred in the getAttribute method. Getter methods should throw a subclass of JboException so that custom exception messages are thrown/shown to the caller. This exception could also be thrown if the getter is not a public Java method.

Action: Do not throw any exception other than subclasses of JboException from any business logic code in the getter method for an attribute. Also verify that the getter method is a public Java method.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27020: The set method for attribute "{2}" in {1} cannot be resolved.

Cause: An unexpected exception occurred in the setAttribute method. Setter methods should throw a subclass of JboException so that custom exception messages are thrown/shown to the caller. This exception could also be thrown if the setter is not a public Java method.

Action: Do not throw any exception other than subclasses of JboException from any business logic code in the setter method for an attribute. Also verify that the setter method is a public Java method.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27021: Failed to load custom data type value at index {0} with java object of type {1} due to {2}.

Cause: An unexpected exception occurred during fetching values from a JDBC result set into an attribute for a row object. There could be conversion errors between the return type from JDBC for the attribute and its Java type.

Action: Verify that the JDBC-SQL type and Java type for the attribute are compatible. Fix any conversion errors or domain exceptions that are in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27022: Failed to load value at index {0} with java object of type {1} due to {2}.

Cause: An unexpected exception occurred during fetching values from a JDBC result set into an attribute for a row object. There could be conversion errors between the return type from JDBC for the attribute and its Java type.

Action: Verify that the JDBC-SQL type and Java type for the attribute are compatible. Fix any conversion errors or domain exceptions that are in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27023: Failed to validate all rows in a transaction.

Cause: An unexpected exception occurred during validating changes in a transaction.

Action: Verify the details for DeferredRowValidationException and fix those errors.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27024: Failed to validate a row with key {1} in {0}

Cause: An unexpected exception occurred during validating a row.

Action: Verify the details for DeferredRowValidationException and fix those errors at the row level. The details can also contain DeferredAttrValidationExceptions which needs to be fixed as well.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27025: Failed to validate attribute {2} with value {3}

Cause: An unexpected exception occurred during validating an attribute of a row.

Action: Verify the details for JboExceptions and fix those errors at the row level.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27026: Set method threw an exception found in the details of this exception.

Cause: An unexpected exception occurred during a setter method for an attribute. This exception should not be seen outside of the framework.

Action: Verify the details for JboExceptions and fix those errors
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27027: Missing mandatory attributes for a row with key {1} of type {0}

Cause: An unexpected exception occurred during validating attributes of a row for mandatory fields.

Action: Verify the details for JboExceptions and fix those attributes with null values.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27028: Variable {2} in manager {1} is not updatable.

Cause: An attempt was made to set the value of a variable that is not updatable.

Action: Change the updatable setting of the variable.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27029: Key definitions in definition {1} cannot be modified after it is resolved.

Cause: An attempt was made to modify the key definition after the definition is resolved (resolveDefObject()).

Action: It is illegal to modify key definitions after the definition is resolved. If key definitions are to be modified, it should be done before.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27030: An entity row without a primary key cannot be locked.

Cause: An attempt was made to lock an entity row with key which is not the primary key.

Action: For locking an entity row, only the primary key can be used (and not an alternate key). Do not use a non-primary key for locking.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27031: At least one of the following attributes {2} in {1} is required.

Cause: At least one of the list attributes must be not null.

Action: Provide a non-null value for one of these attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27032: Session definition full name must start with {0}

Cause: The specified session definition full name is invalid.

Action: Session definition full name must start with the package name, 'sessiondef'. Make sure that the full name starts with it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27033: Validator {0} cannot be designated transaction level because it does not implement JboTransValidatorInterface

Cause: An attempt was made to set a validator to transaction level validator, but the validator does not implement oracle.jbo.rules.JboTransValidatorInterface.

Action: Before setting the transaction level flag, make sure the validator class implements oracle.jbo.rules.JboTransValidatorInterface.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27034: Invalid kind for attribute {0} from the corresponding superclass attribute.

Cause: Attribute kind is different between an entity or view object and the corresponding superclass.

Action: Fix the attribute kind information in the xml-metadata definition for attributes in this entity or view object.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27035: Attribute {2} is required.

Cause: The attribute value cannot be null as it has been marked mandatory.

Action: Provide non-null values for mandatory attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27036: At least one of the following attributes {2} is required.

Cause: At least one of the list attributes must be not null.

Action: Provide a non-null value for one of these attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27037: Please provide a value that does not begin with a wildcard character for attribute {2}.

Cause: The attribute value may not begin with a wildcard character.

Action: Please provide a value that does not begin with a wildcard character.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27101: Attempt to access dead entity in {0}, key={1}

Cause: Trying to refer to an invalid/obsolete entity. This could occur if some business logic has held on to an entity reference which was removed and the transaction has been posted or committed. It could also occur if a reference entity has been removed from the cache and any ViewRow is attempting to access it.

Action: Use findByPrimaryKey to find a valid entity of the desired key instead of holding on to a reference to an entity instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27102: Attempt to access dead view row of persistent id {0}

Cause: Trying to access a ViewRow which is part of an obsolete/invalid collection. This could happen if a reference to the ViewRow is held by some business logic while the containing view object was removed.

Action: Find the referenced ViewRow either by re-querying or using findByKey methods to get a valid reference to the ViewRow.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27120: SQL error during query execution. Statement: {0}

Cause: Failed to execute a query. This could occur when trying to execute a query for a SQLValue domain class or a Sequence domain.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27121: SQL error during statement execution. Statement: {0}

Cause: Failed to execute a SQL statement.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27122: SQL error during statement preparation. Statement: {0}

Cause: Failed to prepare a JDBC PreparedStatement.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27123: SQL error during call statement preparation. Statement: {0}

Cause: Failed to prepare a JDBC CallableStatement.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27124: SQL error during empty statement creation

Cause: Failed to create a JDBC Statement object with the given set of parameters.

Action: Fix the cause for the SQLException thrown by JDBC found in the details of this exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27125: Cannot find matching type-map entries for all columns in a dynamic ViewObject-query

Cause: Failed to find a Java type for a column-type in the given dynamic ViewObject query.

Action: Either provide a typemap that maps the selected columns in the query or leave out the erring column-type from the query.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27126: Long running query "{0}" has been canceled.

Cause: The view object's query timeout was reached or the user requested cancellation of a long query.

Action: Review the query implementation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27127: The effective date operation for Entity {0} will introduce gaps or overlaps. key={1}

Cause: Effective date constraint violation while creating or updating a row. The operation will cause gaps or overlaps in the effective date timeline

Action: Change the start or end effective date if it is a new row. If it is an update choose a different mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27128: The effective date update operation for Entity {0} failed because an existing row has the effective start date that matches the effective date. key={1}

Cause: Effective date row update with UPDATE mode is disallowed because the start effective date of an existing row matches the effective date.

Action: Choose a different mode to update the row like correction mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27129: The effective date row for Entity {0} has end date less than start date, key={1}

Cause: Effective end date is greater than the start date.

Action: Change the start or end effective date.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27130: Current mode {0} is not supported in Multiple Changes Per Day.

Cause: Current mode is not supported in Multiple Changes Per Day.

Action: Switch to Update Change Insert mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27131: Current mode {0} is supported only in Multiple Changes Per Day.

Cause: Current mode is not supported in Multiple Changes Per Day.

Action: Switch to Update Change Insert mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27132: Current operation cannot be performed in {0} mode because no future rows exist. key={1}

Cause: Current operation cannot be performed when no future rows exist.

Action: Switch to Update mode.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27133: Current operation cannot be performed in {0} mode because no previous rows exist. key={1}

Cause: Current operation cannot be performed when no previous rows exist.

Action: Switch to a different mode or navigate to a row where previous rows exist.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27134: Current Multiple Changes Per Day operation can be performed only on first sequenced row. key={0}

Cause: Current Multiple Changes Per Day operation can be performed only on first sequenced row.

Action: Navigate to first sequenced row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27200: JNDI failure. Unable to lookup {0} at context {1}

Cause: JNDI lookup failed. It can be caused by an incorrect data source name, particularly for the internal connection, or an internal error.

Action: Check the internal data source name to see if it is valid. If the error is not caused by the internal connection problem, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27201: Error suspending current transaction

Cause: An error occurred while suspending a global transaction for JTA pcoll manager.

Action: Check the detail exception to determine the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27202: Error resuming current transaction

Cause: An error occurred while resuming a global transaction for JTA pcoll manager.

Action: Check the detail exception to determine the root cause of the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27203: Cannot use the default connection for persistence with global transactions.

Cause: While using global transactions, an attempt was made to use the transactional data source for acquiring the internal connection.

Action: Explicitly specify the jdbc url that should be used for creating the internal connection by setting the oracle.jbo.common.PropertyConstants.INTERNAL_CONNECTION_PARAMS property
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27500: The resource was not found.

Cause: The resource was not found

Action: Check the resource definition and the URL
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27501: The action was not found. Action name: "{0}"

Cause: The action was not found in the resource/resource collection

Action: Check the resource definition and the request content
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27502: Cannot generate content.

Cause: The content generation was not enabled in the request

Action: The request need to provide a Writer/OutputStream. For HTTP clients, the "Accept" header must be configured correctly
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27503: Invalid Resource Type.

Cause: The request is trying to execute an operation in resource collection that is only available for a specific resource. The cause also can be the opposite scenario.

Action: Check the resource path and the operation that was used in the request.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27504: The request content does not represent an action or it has an invalid structure.

Cause: The request content does not represent an action or it has an invalid structure.

Action: Check the request content.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27505: The request content doesn't match the specified resource

Cause: The request content doesn't match the specified resource.

Action: Check the request content and the resource path.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27506: The informed query string could not be processed.

Cause: The query string could not be proccessed. It may have wrong information or structure.

Action: Check the content/structure of the query string.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27507: The user is not authorized to execute this operation

Cause: The user doesn't have access to the requested operation.

Action: Check the if the requested operation was granted to the user.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-27508: Cannot parse content.

Cause: The content parsing was not enabled in the request

Action: The request need to provide a Reader/InputStream. For HTTP clients, the "Content-Type" and the "Content-Encoding" headers must be configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28000: PersistManager class {0} not found

Cause: The client specified a custom persistent collection through the jbo.pcoll.mgr property. However, the class specified could not be located or loaded.

Action: Make sure that the name specified for jbo.pcoll.mgr is for a valid class name. The class name should be fully qualified with the package name. A special keyword None represents no persistent collection manager, i.e., no spilling to disk will occur.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28001: Cannot connect to database

Cause: An error occurred while attempting to get a JDBC connection for persistent collection management.

Action: Make sure that the database connection URL is correct. The detail to this exception will give further information on the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28002: Could not create persistence control table {0}

Cause: An error occurred while creating the persistent collection control table. Normally, the control table's name is PCOLL_CONTROL.

Action: Check to make sure that the connection has appropriate authority to create a table. The detail to this exception will give further information on the problem.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28003: Could not delete row in control table for table {0}

Cause: An unexpected error occurred while attempting to delete the persistent collection control row.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28004: Could not lock row in control table for table {0}

Cause: An error occurred while trying to lock the persistent collection control row. This error is thrown in two situations: An unexpected database error occurred while attempting to lock the row. After the persistent collection manager committed changes to database, it tried to lock the control row. Between the time of commit and lock attempt, another user somehow managed to lock the row and not release it within a set time. In this case, the detail will be null.

Action: In the first case, see the details of this exception for further information on the database problem. In the second case, make sure that no other user locks the control rows outside the Business Components framework.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28005: Could not update row in control table for table {0}

Cause: An unexpected error occurred while attempting to update the persistent collection control row.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28006: Could not create persistence table {0}

Cause: An error occurred while attempting to create a database table to store persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28007: Could not commit while working on persistence table {0}

Cause: An unexpected error occurred while attempting to commit persistent collection changes

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28008: Could not create an index {0} on table {1} for persistent collection

Cause: An error occurred while attempting to create an index on a database table that stores persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28009: Error while getting current time from database

Cause: An unexpected error occurred while attempting to get the system date from the database. For the Oracle persistent manager, the SQL statement used for this would be 'select sysdate from dual'.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28010: Error while getting next sequence value for {0} from database

Cause: An error occurred while attempting to get the next value of a database sequence.

Action: Make sure that the sequence object exists in the database. Also look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28011: Error while querying for the next id from column {1} of table {0}, collection id {2}

Cause: An error occurred while attempting to query for the next id from a pers coll table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28012: Could not add key column {0} to table {1}

Cause: An error occurred while attempting to create add a key column on a database table that stores persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28013: Could not create key info table {0}

Cause: An error occurred while attempting to create a database table to store key info for persistent collection material.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28020: Passivation error on collection {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while passivating objects into the persistent store. An exception might have been thrown during serialization.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28021: Activation error on collection {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while activating objects from the persistent store. An exception might have been thrown during deserialization.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28030: Could not insert row into table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while inserting a passivation row into the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28031: Could not update row into table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while updating a passivation row in the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28032: Could not delete row from table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while deleting a passivation row from the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28033: Could not retrieve row from table {0}, collection id {1}, persistent id {2}

Cause: An unexpected error occurred while retrieving a passivation row from the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28034: Retrieval by id not supported for collection {0}, collection id {1}. Call enableAccessById()

Cause: The client attempted to retrieve a row in a persistent collection by an id, but the by-id access is not enabled on the persistent collection.

Action: Enable by-id access by calling PCollection.enableIdAccess.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28035: Persistent id {1} is invalid for a collection {0}, collection id {1}. It should be > 0

Cause: The client attempted to retrieve a row by an id, but the id value is invalid. The id must be greater than 0.

Action: Give a valid id.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28036: Object of id {2} is already active in its parent {3} in a persistent collection {0}, collection id {1}

Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a node which was thought to be passivated was found to be active.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28037: Object of id {2} not found in its parent {3} in a persistent collection {0}, collection id {1}

Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, a child node/element expected to be found in a node is missing.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28038: Could not delete all rows for collection of id {1} from table {0}

Cause: An unexpected error occurred while deleting all passivation rows from the persistent store table.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28039: Root node for collection {0} is invalid, collection id {1}, persistent id {2}

Cause: While attempting to activate an object of a given id, an internal integrity problem was found. In particular, the root node of the persistent collection is no good. It is either (1) <code>null</code>, (2) has younger or older sibling, or (3) has a parent node. None of these should apply to the root node.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28040: Could not retrieve ids of rows whose key id is {1} and hash is {2} from table {0}

Cause: An unexpected error occurred while retrieving an array of persistent ids of rows from the persistent store table of given key hash code at the given key index.

Action: Look at the details of this exception for further information on the problem and how to address it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28041: Update found multiple rows or no matching row. Persistence table {0}, collection id {1}, persistent id {2}

Cause: The system tried to update a row in the persistence store table, but it found either no row or more than one matching row.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28100: The resource pool, {0}, failed to create a pooled resource instance.

Cause: Either the JDBC connection pool or the application pool were unable to create a new pooled JDBC connection or application module.

Action: If the exception details indicate that an exception occurred while creating a JDBC connection then check the JDBC connection description to ensure that it references a valid, live database instance. If the exception details indicate that an exception occurred while creating an application module then check the application module configuration to ensure that it references a valid, live application server and application application module class.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28101: An application attempted to set a pooled resource that might be in use as available.

Cause: The application attempted to mark a pooled resource which has already been available in the resource pool as available.

Action: Remove the application logic that invokes {@link oracle.jbo.pool.ResourcePool#setAvailable(Object)}, or move the application logic such that it occurs only once before the resource is made available.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28102: A request was timed out while waiting for a resource to be returned to the resource pool, {0}.

Cause: A client request timed out while waiting for a resource to be returned to the resource pool.

Action: Increase the maximum resource pool size in order to accommodate the maximum expected active request size. If the exception details indicate that the exception was thrown while waiting for an application module in the application pool then the maximum pool size can be increased with the property, jbo.ampool.maxpoolsize. If the exception details indicate that the exception was thrown while waiting for a JDBC connection in the JDBC connection pool then the maximum pool size can be increased with the property, jbo.maxpoolsize.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28103: A pool operation was specified for a pooled resource that does not belong to the resource pool.

Cause: A pool request was made for a resource that does not belong to the pool.

Action: Ensure that the pool request is accessing the same pool instance that was used to acquire the resource instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28200: Validation threshold limit reached. Invalid Entities still in cache

Cause: Invalid entities still found in the validation list of the transaction after attempting to validate all invalid entities for the VALIDATION_THRESHOLD 10 times (by default).

Action: Fix any logic that invalidates entity instances in the validation cycle (perhaps in overridden validateEntity() methods) such that all entities are valid before the VALIDATION_THRESHOLD limit is reached.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28201: Post threshold limit reached. Some entities yet to be posted.

Cause: There are invalid entities or entities in the post list of the transaction after trying to post all changes for the POST_THRESHOLD 10 times (by default).

Action: Fix any logic that places entities in the transaction's list of entities to be validated or posted in the post cycle, such that all entities get posted before the POST_THRESHOLD is reached.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28202: Entities invalidated in beforeCommit(). Need to revalidate and post.

Cause: Invalid entity instances found in the transaction in the beforeCommit phase.

Action: Fix any business logic that invalidates entity instances in postChanges() such that there are no more invalid entities after all changes are posted during the commit cycle.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28203: The updated row cannot be refreshed because its key values are unset or modified by database triggers.

Cause: The row could not be refreshed after update because the value of its primary or unique key was not set or unknown.

Action: Ensure values are set for at least one primary or unique key that can be used to fetch the row that is being updated. If that is not possible, use a custom SQLBuilder with doRefreshSQL() defined to refresh the row.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28204: Too many objects match the alternate key {0} for entity {1}, key {2}.

Cause: Attempting to add a new entity to the cache with alternate key that is same as an existing entity. This exception is thrown when uniquing a newly fetched/created entity with the cached set of entities.

Action: Fix the named alternative value of the row. Or, the alternate key definition might have to be augmented with additional attributes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-28205: Validator {0} needs a row from iterator {1} to perform its validation, but did not find any row. Validation fails for row with key {2}.

Cause: A validator needs a row to perform validation, but the view object could not find any matching row.

Action: Since the necessary row is not found, the validation failed. Check to ensure that it is not an application error that cause no row to be found.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29000: Unexpected exception caught: {0}, msg={1}

Cause: If an unexpected exception occurs during a framework operation, this exception is thrown, with the unexpected exception included in the details of this exception.

Action: Fix the cause for the exception in the details for this JboException.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29001: Type mismatch. Expected {0}. Actual {0}

Cause: During creation of application module in the EJB deployment mode, the object returned by the EJB home is not an instance of oracle.jbo.common.remote.ejb.RemoteApplicationModule.

Action: This usually means that the wrong EJB home is being invoked to create a remote application module. Fix it to point to the correct home.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29004: Server-side configuration for creating the pool not specified.

Cause: A configuration was not specified for the remote ApplicationModule usage.

Action: Use the design time to specify a configuration for the remote ApplicationModule usage.
Level: 1

Type: ERROR

Impact: Configuration

JBO-29100: Attribute {0} is not selected

Cause: Def object is not selected. An attempt was made to access a nonselected def object.

Action: This particular operation is disallowed on a nonselected def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29101: Attribute {0} is not selected in {1}, operation: {2}

Cause: Def object is not selected. An attempt was made to access a nonselected def object in the specified container object.

Action: This particular operation is disallowed on a nonselected def object. Avoid this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29102: The S_ROW_ID table is unable to generate a new row ID.

Cause: No more row IDs were available in the database's configured row ID range.

Action: Contact the system administrator. The row ID table in the database needs to be refreshed with a new row ID range.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29103: Internal error: {0} cannot be null

Cause: This is an internal exception. The specified argument cannot be NULL.

Action: Contact the System Administrator. The specified argument cannot be NULL.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29104: Unable to create RowId generator application Module. Add the RowIdAM application module in the AM Usage for the current application.

Cause: The RowIdAM application module is not a shared application module of the current application module.

Action: Add the RowIdAM application module in the AM Usage for the current application or contact the System Administrator.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29105: Attributes referenced in view criteria {0}.{1} with property AppliedIfJoinSatisfied do not map to the same entity usage.

Cause: The attributes used in the View Criteria do not map to the same entity usage.

Action: Make sure the attributes used in the View Criteria all map to the same entity usage if AppliedIfJoinSatisfied is set to true.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29106: Attributes referenced in view criteria {0}.{1} with property AppliedIfJoinSatisfied map to the primary entity usage.

Cause: The attributes used in the View Criteria cannot map to the primary entity usage.

Action: Make sure the attributes used in the View Criteria all map to a non-primary entity usage if AppliedIfJoinSatisfied is set to true.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29107: View criteria {0}.{1} with property AppliedIfJoinSatisfied must be used with an entity-based view object.

Cause: The view criteria cannot be used with a non-entity based view object

Action: The view criteria can only be used with an entity-based view object if AppliedIfJoinSatisfied is set to true.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29108: The value specified for the property {0} in the rowidam.properties file is invalid.

Cause: Invalid value specified in the rowidam.properties file. The values cannot be <= 0.

Action: Update the properties to specify accepted values. The property values should be > 0.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29109: The value specified for column {0} in the S_ROW_ID table is invalid.

Cause: One or more column values in S_ROW_ID table are invalid.

Action: Update the S_ROW_ID table with accepted values. The column values should be greater than zero.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29110: Unable to cast the class type specified for RowId comparison to GeneratorSequenceImpl or BigDecimal.

Cause: Invalid value specified for comparison.

Action: The value to be compared with the RowId should be of type BigDecimal or any other type that can converted to BigDecimal.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29111: View criteria {0} is a union VC and contains an invalid element of type {1} at index {2}

Cause: This view crieria is marked for union query but contains a view criteria element which is neither a ViewCriteria nor ViewCriteriaUsage.

Action: A union view criteria can only contain ViewCriteria or ViewCriteriaUsage. Correct the view criteria definition.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29112: The time zone ''{0}'' defined in adf-config.xml or TimeZone.getDefault().getID() does not exist in your Oracle database table V$TIMEZONE_NAMES. Please set an available time zone in your TZ environment variable or user.timezone Java system property.

Cause: The time zone could not be set as the value defined in adf-config.xml or TimeZone.getDefault().getID() does not exist in Oracle database table V$TIMEZONE_NAMES.

Action: Set an existing time zone defined in your Oracle database table V$TIMEZONE_NAMES in TZ environment variable or user.timezone Java system property.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29113: Encountered database recoverable exception. Please retry your request.

Cause: Encountered database recoverable exception.

Action: Retry your request after performing some recovery steps such asacquiring a new connection.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29114: ADF context is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is {1}

Cause: An error message cannot be constructed because ADF context is not setup on the thread.

Action: Use the error code and the stack trace to diagnose the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29115: Unable to get the error message due to error {1}. Use the exception stack trace and error code to investigate the root cause of this exception. Root cause error code is {2}

Cause: An error occured while constructing a display message for an underlying exception.

Action: Use the error code and the stack trace to diagnose the root cause.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29116: Data modification not allowed for readonly transaction.

Cause: An attempt was made to modify object in readonly transaction.

Action: Use view object in non read-only transaction for modification.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-29117: Transaction security access type {0} does not allow application module {1} security access type {2}.

Cause: An attempt was made to activate application module with different transaction security access type.

Action: Use transaction with same or no security access type.
Level: 1

Type: ERROR

Impact: Security

JBO-29118: Viewobject {0} cannot be created in application with readonly access.

Cause: An attempt to create view object in an application module with unsecured view object.

Action: Create updateable view object in application module that do not contain unsecured view object.
Level: 1

Type: ERROR

Impact: Security

JBO-29119: Unsecured viewobject {0} cannot be created in non readonly access application module.

Cause: An attempt to create unsecured view object in an application module with updateable view object.

Action: Create unsecured view object in application module that do not contain unpdateable view object.
Level: 1

Type: ERROR

Impact: Security

JBO-30000: Application module pool {0} has already been created.

Cause: The application attempted to create an application pool with the same name as an existing application pool.

Action: Correct the application logic that is creating an application pool. Validate that a pool with the given name has not already been registered with the pool manager.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30001: Cookie {0} is invalid.

Cause: Deprecated.

Action: N/A
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30002: The pool signature for the cookie is invalid.

Cause: Deprecated.

Action: N/A
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30003: Application pool {0} fails to check out an application module due to the following exception:

Cause: The pool failed to create an application module instance during checkout. Typically this exception occurs when the pool has been configured with an invalid application module name, EJB server, etc. or when an invalid JDBC username, password, URL, or datasource name has been specified.

Action: See the exception details for more information regarding the failure. Correct the application's configuration properties appropriately.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30004: An application module that was not checked out was checked into the pool, {0}

Cause: The application attempted to check in an application module that was not checked out from the pool.

Action: Remove redundant releaseApplicationModule() invocations from the application logic.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30005: A pool operation was specified for an application module instance that was not created by that pool.

Cause: The application attempted to invoke an application pool method with an application module that was not created by that application pool instance.

Action: Correct the application logic. Use the session cookie that was used to acquire the application module instance to acquire a reference to the application pool that created that application module instance.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30006: The cookie for session {0} and application {1} is not a valid handle for application pool, {2}. The cookie cannot be used to access this pool instance.

Cause: The application attempted to access the application pool with a session cookie that is not registered with that application pool.

Action: Correct the application logic. The application should not reference the application pool directly. Use the session cookie interface for all application pool interaction.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30009: A thread attempted to set as 'available' an application module that could already be in use. An application module's availability cannot be changed from outside of the pool once it has been made available.

Cause: The application attempted to modify the availability status of an application module that is already in active pool use.

Action: Remove the application logic that is updating the application module availability status.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30010: The cookie for session {0} and application {1} cannot be replicated with an active cookie instance.

Cause: The web server attempted to replicate a session cookie with an existing, active cookie.

Action: Internal exception. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30011: A null session cookie application id, session id, or application pool reference ({0}, {1}, {2}) was specified during cookie construction. The cookie could not be constructed.

Cause: The application attempted to create a session cookie with an invalid set of cookie parameters.

Action: Correct the application logic that creates the session cookie. Verify that the cookie session id, application id, and application pool reference are all not null.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30012: A cookie for session {0} and application {1} has already been registered with application pool {2}. The cookie must be removed first.

Cause: The application attempted to create a session cookie in an application pool that already contains that session cookie.

Action: Correct the application logic that creates the session cookie. Remove the existing session cookie before creating a new one in that pool.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30013: The cookie environment for session {0} and application {1} cannot be reset after the cookie has become active.

Cause: The application attempted to change the session cookie environment after the session cookie became active.

Action: Correct the application logic that sets the session cookie environment. Move all logic that changes the session cookie such that it occurs before the session cookie becomes active. A session cookie is active after it is first used to acquire an application module.
Level: 1

Type: ERROR

Impact: Configuration

JBO-30014: The cookie for session {0} and application {1} cannot be removed from the application pool while it has an application module checked out.

Cause: Correct the application logic that sets the session cookie environment. Move all logic that changes the session cookie such that it occurs before the session cookie becomes active. A session cookie is active after it is first used to acquire an application module.

Action: Correct the application logic that removes the session cookie from the application pool. Be sure to invoke SessionCookie.releaseApplicationModule() before invoking ApplicationPool.removeCookie(SessionCookie).
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30015: The cookie for session {0} and application {1} cannot be serialized while in use.

Cause: The application attempted to serialize a session cookie while that cookie had an application module instance checked out or which the cookie was locked by a client request thread.

Action: Correct the serialization logic such that the session cookie is serialized after the session cookie application module has been released to the application pool and after all client requests have released their cookie locks.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30016: The request thread for session {0} and application {1} was timed out while waiting for an available application module in the pool, {2}.

Cause: The application request thread timed out while waiting for an available appliation module instance in the pool.

Action: Prevent wait timeouts by increasing the maximum pool size.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30017: The cookie for session {0} and application {1} cannot be reset while an ApplicationModule is reserved.

Cause: ApplicationModuleRef.resetState() was invoked while the ApplicationModuleRef was referencing a reserved ApplicationModule instance.

Action: Release the ApplicationModule with ApplicationModuleRef.releaseApplicationModule(true, boolean) before invoking resetState.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30018: The cookie configuration does not match the specified configuration. applicationId: {0}, sessionId: {1}, cookieConfig: {2}, specifiedConfig: {3}.

Cause: oracle.jbo.http.HttpContainer.findSessionCookie was invoked with a configName which was different than the configuration that was used to create the specified SessionCookie.

Action: Use a distinct applicationId to identify the cookie for each distinct Configuration.
Level: 1

Type: ERROR

Impact: Configuration

JBO-30019: An unavailable cookie state is detected while attempting to use a cookie from application {0}, session {1}.

Cause: An application pool method was invoked for a cookie that was not currently available. A cookie can be in an unavailable state if another thread is currently updating the cookie. For example, consider the following scenario: 1. cookie 1 releases an ApplicationModule with the managed state option 2. cookie 2 targets that ApplicationModule for recycling 3. Before cookie 2 has passivated the ApplicationModule state for cookie 1, cookie 1 requests another ApplicationModule In this instance the ApplicationPool could throw an unavailable exception. Note that most of the occurrences of this exception should be handled by the pooling framework.

Action: Report the exception to Oracle Support Services. Attempt the invalid operation again.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-30020: An invalid SessionCookie release mode was specified. applicationId: {0}, sessionId: {1}.

Cause: oracle.jbo.common.ampool.SessionCookie.releaseApplicationModule was invoked with an unsupported releaseMode.

Action: Invoke releaseApplicationModule(int) with a valid releaseMode attribute. Valid releaseModes include: SessionCookie.SHARED_MANAGED_RELEASE_MODE SessionCookie.SHARED_UNMANAGED_RELEASE_MODE SessionCookie.RESERVED_MANAGED_RELEASE_MODE SessionCookie.RESERVED_UNMANAGED_RELEASE_MODE
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33000: Configuration file {0} is not found.

Cause: The requested configuration file could not be found.

Action: Provide a correct name for the configuration file. Or, make sure that the named configuration file can be found in one of the accessible paths.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33001: Configuration file {0} is not found in the classpath.

Cause: The requested configuration file could not be found in the class paths.

Action: Make sure that the named configuration file can be located in one of the class paths.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33003: Connection name {0} is not defined.

Cause: The specified connection could not be found. Or an error occurred during processing of the specified connection.

Action: Make sure that the connection name is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33004: Configuration file cannot be parsed.

Cause: An error occurred while parsing configuration file.

Action: Check to make sure that the configuration file is a valid XML file. See the detail exception for further information.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33005: Configuration {0} is not found.

Cause: The named configuration parameter was not found in the configuration.

Action: The system expects to find the named configuration parameter, but could not. Check the configuration content to make sure that it contains the named configuration parameter.
Level: 1

Type: ERROR

Impact: Configuration

JBO-33006: Data source {0} is not supported.

Cause: This error message indicates that the underlying SQLBuilder does not support datasource.

Action: For this SQLBuilder, do not use datasource.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33007: Data source {0} is not found.

Cause: The specified datasource could not be found.

Action: Make sure that the datasource name is correct. See the detail exception for further info.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33020: Current time is not available from SQL statement "{0}".

Cause: An error occurred while getting the current time from the database.

Action: If there is a detail exception, it will give further information about what went wrong. If no detail exception was provided, that means the SQL statement to get the current time returned no result (no row). Check the SQL statement for correctness.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33021: User {0} cannot be authenticated.

Cause: An error occurred while authenticating the user.

Action: Make sure that the user authentication information is correct.
Level: 1

Type: ERROR

Impact: Security

JBO-33022: Thread {0} has timed out while waiting to acquire a lock.

Cause: A thread timed out while waiting for a resource that was protected with an 'oracle.jbo.common.Lock'.

Action: Verify that all threads that have acquired a lock have properly released that lock in a 'finally' code block.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33023: Thread {0} is attempting to release a session cookie lock that it did not acquire.

Cause: The application attempted to release a {@link oracle.jbo.common.Lock} that it did not hold.

Action: Internal exception. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33024: Graph nodes cannot be sorted due to a cycle in the graph.

Cause: A cycle was detected in the dependency graph.

Action: Check the edges in the graph and remove any cycles.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33025: Failed to release application module {0}. Cookie handle not found.

Cause: Failed to release application module due to missing cookie handle.

Action: Invoke the correct, counterpart releaseAM method.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33026: Value must be between {MinVal} and {MaxVal}

Cause: Input values failed the range validator test.

Action: Provide values that are within the range validator paramters.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33027: Value must be greater than {MinVal}

Cause: Input values failed the minimum validator test.

Action: Provide values that are greater than the minimum.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33028: Value must be less than {MaxVal}

Cause: Input values failed the maximum validator test.

Action: Provide values that are less than the maximum.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33029: Value must have exactly {MinLength} characters

Cause: Input values must be longer than minimum length.

Action: Provide values that are longer than the minimum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33030: Value can have at most {MaxLength} characters

Cause: Input values exceeded maximum length length.

Action: Provide values that are less than or equal to maximum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33031: Value must have at least {MinLength} and at most {MaxLength} characters

Cause: Value must have at least (minLen) and at most (maxLen) characters.

Action: Provide values that are between minimum and maximum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-33032: Value must have exactly {MaxLength} characters

Cause: alue must be exactly (maxLen) characters.

Action: Provide values that is exactly the maximum length.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34000: Definition class name missing in XML file of type {0}

Cause: Name of the definition Java class missing in the JClient XML file.

Action: Every metaobject in JClient must have name of the definition object's Java class in the XML file. Correct the error by regenerating XML file in the design time.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34001: Iterator binding {0} is not of the expected class {1}

Cause: The iterator binding is of the wrong Java class. Some controls expect to work with a JUIterRowBinding, while others with JUIterRangeBinding. This error indicates that the supplied iterator binding is not of the expected class.

Action: If the error is caused by some client code that supplies an iterator binding, correct the code to supply an iterator binding of the correct class. If the error is caused by framework code, contact Oracle Support Services with the stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34002: The application obj has already been set for form binding {0}. Cannot do it again

Cause: The form binding has already been registered with an application (JUApplication) object. It is illegal to try to set the form binding's application object again.

Action: This error typically means a program error. Contact Oracle Support Services with the stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34003: No iterators bound with the given name :{0}

Cause: No iterator binding found with the given name.

Action: Fix the iterator binding name before attempting to change the iterator associated with it.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34004: No matching row found for entered or selected item in the LOV iterator for a list-binding.

Cause: No matching row found for a selected value in a List binding.

Action: Enter/Select a valid item from the list so that the matching row in the LOV iterator can be found.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34005: Exceptions occurred in synchronizing updates from this application. Click Details to see the complete list.

Cause: Exceptions occurred in synchronizing data from the client Application into the Business Components tier.

Action: Fix the exceptions displayed in the details list and then reapply the changes.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34006: Method that creates the iterator for this object returns null.

Cause: Collection to which this iterator is bound returns null.

Action: Fix the return value so that a valid collection is available for this iterator to bind to.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34007: A value is not passed for mandatory parameter {0}.

Cause: Mandatory Parameter was not set by the calling code either programmatically or by overriding it in a nested container usecase.

Action: Set the mandatory parameter value
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34008: Final parameter {0} cannot be modified.

Cause: Mandatory Parameter was not set by the calling code either programmatically or by overriding it in a nested container usecase.

Action: Set the mandatory parameter value
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34009: ListBinding definition :{0} not found.

Cause: Server side ListBinding could not be found with the given usage name.

Action: Fix the server side ListBinding usage name in List binding metadata
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34010: The "{0}" descriptor appears in the application classpath more than once: - {1} - {2}

Cause: The cpx classpath name has already been found at a different source in the classpath. It is illegal to have the same relative cpx name in the classpath more than once.

Action: Refactor one of the indicated URLs in the message so it appears under a different relative package in the classpath.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34011: Validator expression {0} did not result in a valid object for bindingContainer:{1}

Cause: Expression for custom validator does not resolve into a valid object that as a public method of name validateBindingContainer and that takes the bindingContainer as the only parameter.

Action: Provide a different expression or fix the expression so that an object whose class has a method with following signature: public validateBindingContainer(DCBindingContainer ctr)
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34012: Attempting to register a Swing binding factory when Faces version is already installed.

Cause: Faces binding factory is already installed for ADF Model bindings. Attempt to install a Swing version will break the application due to binding class incompatibilities.

Action: Remove or replace references to juimodel in namespace attributes, in pagedef xml files in the application with: http://xmlns.oracle.com/adfm/uimodel.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34013: Enter a nonempty string and a string not equal to '%' in the list:{0} to filter the list of values.

Cause: Empty string or % was entered to filter list datsource for a list binding.

Action: Enter any other string to filter by in the list component bound to this list binding.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-34014: No matching child node found for row with key:{0} under parent node:{1}

Cause: No matching node in the current range of rows found for a row retrieved from the backend collection.

Action: Scroll the backend collection to the appropriate range where a node for this row will be found. If row keys are for rows outside of current range of rows in the RowIterator, use alternate client apis to access the row data avoiding calls into this node binding.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36000: An unexpected expression token is found.

Cause: Unexpected token found.

Action: Found an unexpected expression token. Make sure that the words are spelled correctly and that the expression makes sense.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36001: Mismatching parentheses are found.

Cause: Mismatching parentheses.

Action: Examine the expression and ensure that open parentheses match up with closing parentheses.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36002: The method call specification is invalid. "," or ")" is expected.

Cause: Invalid method call. After a method parameter, ',' or ')' is expected, but neither was found.

Action: Examine the expression and correct method invocation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36003: An expression token is not found.

Cause: Expecting a token. The expression string was terminated unexpectedly.

Action: Examine the expression and ensure that the expression does not end unexpectedly.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36004: Mismatching square brackets are found. An invalid array index is specified.

Cause: Mismatching square brackets.

Action: Examine the expression and ensure that open square brackets (for array index) match up with closing brackets.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36005: Variable {0} is not found.

Cause: Variable not found.

Action: Examine the expression and ensure that the variable name is correct.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36006: cannot convert {0} into {1}

Cause: Cannot convert data.

Action: Cannot convert data from one class to another. Examine the expression and ensure that the data assignment does not cause incompatible conversion of data.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36007: Binary operation {0} is invalid for strings.

Cause: An attempt was made to invoke an invalid binary operation on two strings.

Action: Examine the operation ID and correct the expression so that the invalid binary operation is not attempted on strings. The expression runtime only recognizes addition as a valid binary operation between two strings.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-36008: The AND separator for a BETWEEN operator cannot be found. Token {0} is found instead.

Cause: A BETWEEN operator was found but no AND for the two comparison expressions.

Action: Take a look at the expression string. The correct syntax for BETWEEN is 'testVal BETWEEN value1 AND value2'. The expression parser could not find the AND keyword. Correct the expression.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-55001: A value of type {1} cannot be set to a value of type {0}.

Cause: Unexpected type was provided to Variant utility.

Action: Provide an expected type as reported in the exception.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-55002: Variant type {0} is invalid.

Cause: The data-type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML-metadata definition in the component's XML file.

Action: Fix the component XML for the offending validation rule.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-55003: Variant name {0} is invalid.

Cause: The name of the variant type passed to the Variant utility from a Validation rule is invalid. This could be due to a corrupt XML meta data definition in the component's XML file.

Action: Fix the component XML for the offending validation rule.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56001: Row value is missing for data object {0}.

Cause: The Row Value for a SDOValueStore is null.

Action: Should not use SDOValueStore with a NULL row value.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56002: Operation {0} on object {1} is not supported.

Cause: An attempt was made to invoke an invalid service operation.

Action: Ensure that this service operation is defined at design time.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56003: Nonpersistent attribute {0} cannot be used in a database mode view criteria.

Cause: A nonpersistent attribute is used for DB ViewCriteriaItem.

Action: Make sure the attribute is persistent.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56004: Non-ViewLink accessor attribute {0} cannot be used for a view criteria item that has nested view criteria.

Cause: A non-ViewLink accessor is used for DB ViewCriteriaItem that has nested ViewCriteria.

Action: Make sure the attribute is a ViewLink accessor.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56005: SDO type is not found for ViewObject {0} with namespace {1} and name {2}.

Cause: SDO Type is not found for a ViewObject.

Action: Make sure the viewobject is SDO enabled.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56006: ComplexType or DataType SDO property {0} has conflict values {1} vs. {2} for attribute {3}.

Cause: Conflict input values for ComplexType non-value properties.

Action: Make sure the payload has the same values for the same ComplexType non-value properties.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56007: ViewObject not found for sdo dataobject {0} from base viewobject {1}.

Cause: Can't find corresponding ViewObject for one SDO Type.

Action: Make sure passing valid SDODataObject that maps to valid ViewObject.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56008: Mapped value for name {0} not found in viewobject {1} attribute {2}.

Cause: Can't find mapped value for one given name.

Action: Add neccessary name/value to PropertySet.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56009: Mapped name for value {0} not found in viewobject {1} attribute {2}.

Cause: Can't find mapped value for one given value.

Action: Add neccessary name/value to PropertySet.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56010: Comparision Operation {0} is invalid for ViewCriteriaItem of attribute {1}.

Cause: The attempted operation is invalid for a ViewCriteriaItem.

Action: Change the input value of this operation.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56101: Nonpersistent attribute {0} cannot be sorted upon.

Cause: A nonpersistent attribute is used for DB SortCriteria.

Action: Make sure the attribute is persistent.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56102: Dependencies specified for view attribute {0} conflict with dependencies specified on the underlying entity attribute.

Cause: View attribute dependencies conflict with the entity attribute dependencies.

Action: Ensure that the dependencies are not specified on both the view and entity attribute.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56103: View object {0} is not prepared.

Cause: This is the exception that gets thrown by ViewObjectImpl when attempting an operation on a declarative view object on which prepareVOForQuery has not been called, such as findByAltKey (bug 7455860) or createAndInitRow (bug 7504211).

Action: Call ViewObjectImpl.prepareVOForQuery before calling findByAltKey or createAndInitRow for the first time.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-56104: Entity {0} cannot be set to batch mode because it has streaming attribute types (e.g., Blob, Clob).

Cause: An attempt was made to set batch mode on an entity that has streaming attribute types (e.g., Blob, Clob).

Action: Remove BatchThreshold value from this entity's metadata.
Level: 1

Type: ERROR

Impact: Programmatic

JBO-80000: Connection is already open.

Cause: An open operation was attempted on a URL connection that is already open and in a active state.

Action: Ensure that a close operation has been called before invoking the open operation on the connection.
Level: 1

Type: ERROR

Impact: Other

JBO-80001: Connection is not open.

Cause: An interaction with the URL was attempted without opening the connection.

Action: Ensure that the connection has been opened and is active before starting an interaction with the URL.
Level: 1

Type: ERROR

Impact: Other

JBO-80002: Connection description cannot be created.

Cause: There was an internal error creating the metadata fragment for the URLConnection.

Action: Verify if the details necessary to create a new URL connection are provided.
Level: 1

Type: ERROR

Impact: Other

JBO-80003: Operation is invalid. Connection is already released to the pool.

Cause: An operation was attempted on a connection that had already been released to the pool.

Action: Obtain a new active reference to the connection from the connections context.
Level: 1

Type: ERROR

Impact: Other

JBO-80004: Authentication provider "{0}" cannot be initialized.

Cause: Either the metadata describing the authentication provider was corrupted or the class registered in the metadata for the authentication could not be loaded.

Action: Ensure that the class is available in the class path of the application. Contact Oracle Support Services if the corrupt metadata cannot be recovered.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

JBO-80005: The connection cannot be created. Connection metadata is invalid.

Cause: The connection metadata in the repository has been corrupted possibly due to an external edit.

Action: Contact Oracle Support Services to recover the corrupted metadata.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

JBO-80006: The connection instance cannot be created. Resource endpoint is not provided.

Cause: A URLConnection could not be created as the URI / URL to the resource endpoint was not supplied.

Action: Provide a valid URL / URI to create the connection.
Level: 1

Type: ERROR

Impact: Other

JBO-80007: The connection fails to open. Resource endpoint "{0}" does not exist.

Cause: The URL resource could not be accessed after the connection was created. If the connection describes an HTTP URL resource outside a firewall, the proxy settings might not have been correctly configured to access the URL.

Action: Ensure that the URL is active and can be accessed. If the connection describes an HTTP URL outside a firewall, verify that the correct proxy settings are configured.
Level: 1

Type: ERROR

Impact: Other

JBO-80008: Proxy is not supported for file connection protocol.

Cause: An attempt was made to configure proxy information for a file connection protocol.

Action: Proxy configuration is not supported for a file connection protocol. Remove any proxy configuration done for this connection.
Level: 1

Type: ERROR

Impact: Other

29 JPS-00001 to JPS-90642

JPS-00001: The method {0} is not supported.

Cause: An unsupported method was used.

Action: This operation is not supported. It cannot be used.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-00001: The method {0} is not supported.

Cause: An unsupported method was used.

Action: This operation is not supported. It cannot be used.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-00001: The method {0} is not supported.

Cause: An unsupported method was used.

Action: This operation is not supported. It cannot be used.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-00003: The HTTP response callback is null.

Cause: HTTP response callback was null.

Action: Check the log files and provide a valid HTTP response callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00003: The HTTP response callback is null.

Cause: HTTP response callback was null.

Action: Check the log files and provide a valid HTTP response callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00003: The HTTP response callback is null.

Cause: HTTP response callback was null.

Action: Check the log files and provide a valid HTTP response callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00004: The HTTP response is null.

Cause: HTTP response was null.

Action: Check the log files and provide a valid HTTP response.
Level: 1

Type: ERROR

Impact: Session

JPS-00004: The HTTP response is null.

Cause: HTTP response was null.

Action: Check the log files and provide a valid HTTP response.
Level: 1

Type: ERROR

Impact: Session

JPS-00004: The HTTP response is null.

Cause: HTTP response was null.

Action: Check the log files and provide a valid HTTP response.
Level: 1

Type: ERROR

Impact: Session

JPS-00005: HTTP request callback is null.

Cause: HTTP request callback was null.

Action: Check the log files and provide a valid HTTP request callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00005: HTTP request callback is null.

Cause: HTTP request callback was null.

Action: Check the log files and provide a valid HTTP request callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00005: HTTP request callback is null.

Cause: HTTP request callback was null.

Action: Check the log files and provide a valid HTTP request callback.
Level: 1

Type: ERROR

Impact: Session

JPS-00006: The HTTP request is null.

Cause: HTTP request was null.

Action: Check the log files and provide a valid HTTP request.
Level: 1

Type: ERROR

Impact: Session

JPS-00006: The HTTP request is null.

Cause: HTTP request was null.

Action: Check the log files and provide a valid HTTP request.
Level: 1

Type: ERROR

Impact: Session

JPS-00006: The HTTP request is null.

Cause: HTTP request was null.

Action: Check the log files and provide a valid HTTP request.
Level: 1

Type: ERROR

Impact: Session

JPS-00007: Cannot find an application ID.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Session

JPS-00007: Cannot find an application ID.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Session

JPS-00007: Cannot find an application ID.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Session

JPS-00008: The application ID {0} is invalid.

Cause: Application ID was NULL.

Action: Provide a valid application ID.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00008: The application ID {0} is invalid.

Cause: Application ID was NULL.

Action: Provide a valid application ID.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00008: The application ID {0} is invalid.

Cause: Application ID was NULL.

Action: Provide a valid application ID.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00009: The subject is read-only, and it cannot modified.

Cause: Attempted to modify a read-only subject.

Action: A read-only subject cannot be modified.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00009: The subject is read-only, and it cannot modified.

Cause: Attempted to modify a read-only subject.

Action: A read-only subject cannot be modified.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00009: The subject is read-only, and it cannot modified.

Cause: Attempted to modify a read-only subject.

Action: A read-only subject cannot be modified.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00010: A JPS context is not available in the callback handler.

Cause: A context was not available from callback handler.

Action: Check configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-00010: A JPS context is not available in the callback handler.

Cause: A context was not available from callback handler.

Action: Check configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-00010: A JPS context is not available in the callback handler.

Cause: A context was not available from callback handler.

Action: Check configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-00011: The service instance {0} already exists.

Cause: The named service instance was already in use.

Action: Use a different name for this service instance.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00011: The service instance {0} already exists.

Cause: The named service instance was already in use.

Action: Use a different name for this service instance.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00011: The service instance {0} already exists.

Cause: The named service instance was already in use.

Action: Use a different name for this service instance.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00012: The service instance {0} is missing.

Cause: The service instance with the name {0} was not found.

Action: Ensure the service instance name is present in the file jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00012: The service instance {0} is missing.

Cause: The service instance with the name {0} was not found.

Action: Ensure the service instance name is present in the file jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00012: The service instance {0} is missing.

Cause: The service instance with the name {0} was not found.

Action: Ensure the service instance name is present in the file jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00013: The login module {0} already exists.

Cause: The login module with the name {0} was already present.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00013: The login module {0} already exists.

Cause: The login module with the name {0} was already present.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00013: The login module {0} already exists.

Cause: The login module with the name {0} was already present.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00014: The login module with {0} is missing.

Cause: The login module with the name {0} did not exist.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00014: The login module with {0} is missing.

Cause: The login module with the name {0} did not exist.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00014: The login module with {0} is missing.

Cause: The login module with the name {0} did not exist.

Action: Ensure the login module name is correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00015: All available service instance names are already in use.

Cause: All service instance names were in use.

Action: Remove unwanted service instances from jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00015: All available service instance names are already in use.

Cause: All service instance names were in use.

Action: Remove unwanted service instances from jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00015: All available service instance names are already in use.

Cause: All service instance names were in use.

Action: Remove unwanted service instances from jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00016: All available service provider names are already in use.

Cause: All service provider names were in use.

Action: Remove unwanted service providers form jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00016: All available service provider names are already in use.

Cause: All service provider names were in use.

Action: Remove unwanted service providers form jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00016: All available service provider names are already in use.

Cause: All service provider names were in use.

Action: Remove unwanted service providers form jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00017: The LDAP type is invalid.

Cause: An invalid LDAP type was specified.

Action: Provide a valid LDAP type. Valid types are XML, OID, ACTIVE_DIRECTORY, IPLANET, OUD and OVD. See the documentation for details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00017: The LDAP type is invalid.

Cause: An invalid LDAP type was specified.

Action: Provide a valid LDAP type. Valid types are XML, OID, ACTIVE_DIRECTORY, IPLANET and OVD. See the documentation for details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00017: The LDAP type is invalid.

Cause: An invalid LDAP type was specified.

Action: Provide a valid LDAP type. Valid types are XML, OID, ACTIVE_DIRECTORY, IPLANET and OVD. See the documentation for details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00018: The keystore path {0} is null or invalid.

Cause: Keystore path was null.

Action: Provide a valid keystore path.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00018: The keystore path {0} is null or invalid.

Cause: Keystore path was null.

Action: Provide a valid keystore path.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00018: The keystore path {0} is null or invalid.

Cause: Keystore path was null.

Action: Provide a valid keystore path.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00019: The key type {0} is not supported.

Cause: Invalid key type was provided.

Action: Provide a valid key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00019: The key type {0} is not supported.

Cause: Invalid key type was provided.

Action: Provide a valid key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00019: The key type {0} is not supported.

Cause: Invalid key type was provided.

Action: Provide a valid key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00020: LDAP URL {0} is null or invalid.

Cause: Invalid or null LDAP URL was provided.

Action: Provide a valid LDAP URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00020: LDAP URL {0} is null or invalid.

Cause: Invalid or null LDAP URL was provided.

Action: Provide a valid LDAP URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00020: LDAP URL {0} is null or invalid.

Cause: Invalid or null LDAP URL was provided.

Action: Provide a valid LDAP URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00021: An Object named {0} does not exist.

Cause: Object with the name {0} did not exist.

Action: Verify that the object name is valid and exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00021: An Object named {0} does not exist.

Cause: Object with the name {0} did not exist.

Action: Verify that the object name is valid and exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00021: An Object named {0} does not exist.

Cause: Object with the name {0} did not exist.

Action: Verify that the object name is valid and exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00022: Callback handler missing for this login module request.

Cause: The callback handler was null.

Action: Provide an appropriate callback handler to invoke this login module.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00022: Callback handler missing for this login module request.

Cause: The callback handler was null.

Action: Provide an appropriate callback handler to invoke this login module.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00022: Callback handler missing for this login module request.

Cause: The callback handler was null.

Action: Provide an appropriate callback handler to invoke this login module.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00023: The callback used for this operation has no HTTP request value.

Cause: The callback did not have a request method.

Action: Verify that the callback is initialized with the correct HTTP request value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00023: The callback used for this operation has no HTTP request value.

Cause: The callback did not have a request method.

Action: Verify that the callback is initialized with the correct HTTP request value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00023: The callback used for this operation has no HTTP request value.

Cause: The callback did not have a request method.

Action: Verify that the callback is initialized with the correct HTTP request value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00024: The callback used for this operation has no digest response object value.

Cause: The callback did not have any digest response object.

Action: Verify that the callback is initialized with the correct digest response value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00024: The callback used for this operation has no digest response object value.

Cause: The callback did not have any digest response object.

Action: Verify that the callback is initialized with the correct digest response value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00024: The callback used for this operation has no digest response object value.

Cause: The callback did not have any digest response object.

Action: Verify that the callback is initialized with the correct digest response value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00025: The {0} subscriber {1} from the HTTP header is different from the subscriber configured by the identity store as {2}.

Cause: Found a subscriber mismatch.

Action: Check the identity store subscriber configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00025: The {0} subscriber {1} from the HTTP header is different from the subscriber configured by the identity store as {2}.

Cause: Found a subscriber mismatch.

Action: Check the identity store subscriber configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00025: The {0} subscriber {1} from the HTTP header is different from the subscriber configured by the identity store as {2}.

Cause: Found a subscriber mismatch.

Action: Check the identity store subscriber configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00026: The value "{0}" is invalid for {1}.

Cause: An invalid value was provided for this application.

Action: Provide the correct value for the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00026: The value {0} is invalid for the application {1}.

Cause: An invalid value was provided for this application.

Action: Provide the correct value for the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00026: The value {0} is invalid for the application {1}.

Cause: An invalid value was provided for this application.

Action: Provide the correct value for the application.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00027: There was an internal error: {0}

Cause: Internal system error was found.

Action: See the log files or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00027: internal error {0}

Cause: Internal system error was found.

Action: See the log files or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00027: internal error {0}

Cause: Internal system error was found.

Action: See the log files or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00028: The property runas.mode is deprecated and supported only for backward compatibility.

Cause: The property runas.mode has been deprecated.

Action: Use instead the oracle.security.jps.jaas.mode property in jps-config.xml.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00028: The property runas.mode is deprecated and supported only for backward compatibility.

Cause: The property runas.mode has been deprecated.

Action: Use instead the oracle.security.jps.jaas.mode property in jps-config.xml.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00028: The property runas.mode is deprecated and supported only for backward compatibility.

Cause: The property runas.mode has been deprecated.

Action: Use instead the oracle.security.jps.jaas.mode property in jps-config.xml.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00029: The audit service initialization failed for the application {0}. Reason {1}.

Cause: Audit service failed.

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00029: The audit service initialization failed for the application {0}. Reason {1}.

Cause: Audit service failed.

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00029: The audit service initialization failed for the application {0}. Reason {1}.

Cause: Audit service failed.

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00030: Cannot complete exist operation.

Cause: Could not find entity.

Action: Verify that the entity exist.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00030: Cannot complete exist operation.

Cause: Could not find entity.

Action: Verify that the entity exist.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00030: Cannot complete exist operation.

Cause: Could not find entity.

Action: Verify that the entity exist.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00031: Cannot load the required class {0}. Reason {1}.

Cause: Could not load a class.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00031: Cannot load the required class {0}. Reason {1}.

Cause: Could not load a class.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00031: Cannot load the required class {0}. Reason {1}.

Cause: Could not load a class.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00032: The migration cannot write directly to the specified LDAP identity store; specify an alternate LDIF file to create.

Cause: Could not perform a direct LDAP write operation.

Action: See the log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00032: The migration cannot write directly to the specified LDAP identity store; specify an alternate LDIF file to create.

Cause: Could not perform a direct LDAP write operation.

Action: See the log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00032: The migration cannot write directly to the specified LDAP identity store; specify an alternate LDIF file to create.

Cause: Could not perform a direct LDAP write operation.

Action: See the log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00033: The direct policy store should be XML-based, and it can be specified as an XML file or as an input stream.

Cause: The policy store specification was invalid.

Action: Check the policy store specification.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00033: The direct policy store should be XML-based, and it can be specified as an XML file or as an input stream.

Cause: The policy store specification was invalid.

Action: Check the policy store specification.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00033: The direct policy store should be XML-based, and it can be specified as an XML file or as an input stream.

Cause: The policy store specification was invalid.

Action: Check the policy store specification.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00034: Cannot find the application context.

Cause: A context was not available for the application.

Action: Check the jps-config.xml configuration.
Level: 1

Type: ERROR

Impact: Session

JPS-00034: Cannot find the application context.

Cause: A context was not available for the application.

Action: Check the jps-config.xml configuration.
Level: 1

Type: ERROR

Impact: Session

JPS-00034: Cannot find the application context.

Cause: A context was not available for the application.

Action: Check the jps-config.xml configuration.
Level: 1

Type: ERROR

Impact: Session

JPS-00035: The WSS digest value {0} is invalid.

Cause: Found missing WSS digest value in callback.

Action: Verify that the callback has a valid WSS digest value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00035: The WSS digest value {0} is invalid.

Cause: Found missing WSS digest value in callback.

Action: Verify that the callback has a valid WSS digest value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00035: The WSS digest value {0} is invalid.

Cause: Found missing WSS digest value in callback.

Action: Verify that the callback has a valid WSS digest value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00036: The WSS digest nonce {0} is invalid.

Cause: Found missing WSS digest nonce in callback.

Action: Verify that the callback has a valid WSS digest nonce.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00036: The WSS digest nonce {0} is invalid.

Cause: Found missing WSS digest nonce in callback.

Action: Verify that the callback has a valid WSS digest nonce.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00036: The WSS digest nonce {0} is invalid.

Cause: Found missing WSS digest nonce in callback.

Action: Verify that the callback has a valid WSS digest nonce.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00037: The WSS digest created {0} is invalid.

Cause: Found missing WSS digest created in callback.

Action: Verify that the callback has a valid WSS digest created.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00037: The WSS digest created {0} is invalid.

Cause: Found missing WSS digest created in callback.

Action: Verify that the callback has a valid WSS digest created.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00037: The WSS digest created {0} is invalid.

Cause: Found missing WSS digest created in callback.

Action: Verify that the callback has a valid WSS digest created.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00038: Cannot create or retrieve a ContextFactory.

Cause: Cannot retrieve or create a JPS ContextFactory.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Other

JPS-00038: Cannot create or retrieve a ContextFactory.

Cause: Cannot retrieve or create a JPS ContextFactory.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Other

JPS-00038: Cannot create or retrieve a ContextFactory.

Cause: Cannot retrieve or create a JPS ContextFactory.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Other

JPS-00039: The service instance with provider {0} and name {1} is missing.

Cause: A service instance configuration was missing.

Action: Check the service instance configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00039: The service instance with provider {0} and name {1} is missing.

Cause: A service instance configuration was missing.

Action: Check the service instance configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00039: The service instance with provider {0} and name {1} is missing.

Cause: A service instance configuration was missing.

Action: Check the service instance configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00040: The JPS audit component events file {0} is missing or invalid.

Cause: Cannot find the audit component events file.

Action: Make sure the audit component events file is available and valid.
Level: 1

Type: ERROR

Impact: Other

JPS-00040: The JPS audit component events file {0} is missing or invalid.

Cause: Cannot find the audit component events file.

Action: Make sure the audit component events file is available and valid.
Level: 1

Type: ERROR

Impact: Other

JPS-00040: The JPS audit component events file {0} is missing or invalid.

Cause: Cannot find the audit component events file.

Action: Make sure the audit component events file is available and valid.
Level: 1

Type: ERROR

Impact: Other

JPS-00041: Cannot load the JpsAdminService class.

Cause: The class JpsAdminService or a dependent class could not be loaded.

Action: Review the cause to resolve the error.
Level: 1

Type: ERROR

Impact: Other

JPS-00041: Cannot load the JpsAdminService class.

Cause: The class JpsAdminService or a dependent class could not be loaded.

Action: Review the cause to resolve the error.
Level: 1

Type: ERROR

Impact: Other

JPS-00041: Cannot load the JpsAdminService class.

Cause: The class JpsAdminService or a dependent class could not be loaded.

Action: Review the cause to resolve the error.
Level: 1

Type: ERROR

Impact: Other

JPS-00042: The LDAP connection pool provider {0} is not valid; the supported providers are JNDI or IDM. If unspecified, it defaults to UCP/JNDI provider.

Cause: The connection.pool.provider.type property value was invalid.

Action: Configure a supported connection.pool.provider.type value, or use the default provider by not setting the connection.pool.provider.type property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00042: The LDAP connection pool provider {0} is not valid; the supported providers are JNDI or IDM. If unspecified, it defaults to UCP/JNDI provider.

Cause: The connection.pool.provider.type property value was invalid.

Action: Configure a supported connection.pool.provider.type value, or use the default provider by not setting the connection.pool.provider.type property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00042: The LDAP connection pool provider {0} is not valid; the supported providers are JNDI or IDM. If unspecified, it defaults to UCP/JNDI provider.

Cause: The connection.pool.provider.type property value was invalid.

Action: Configure a supported connection.pool.provider.type value, or use the default provider by not setting the connection.pool.provider.type property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00043: Cannot establish an LDAP connection after {0} attempts.

Cause: The connection could not be established.

Action: Check the LDAP configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00043: Cannot establish an LDAP connection after {0} attempts.

Cause: The connection could not be established.

Action: Check the LDAP configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00043: Cannot establish an LDAP connection after {0} attempts.

Cause: The connection could not be established.

Action: Check the LDAP configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00044: The LDAP URL format must be ldap://<host>:<port> or ldaps://<host>:<port>; but found {0}.

Cause: Invalid LDAP URL format was found.

Action: The format of the LDAP URL must be ldap://<host>:<port> or ldaps://<host>:<port> format.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00044: The LDAP URL format must be ldap://<host>:<port> or ldaps://<host>:<port>; but found {0}.

Cause: Invalid LDAP URL format was found.

Action: The format of the LDAP URL must be ldap://<host>:<port> or ldaps://<host>:<port> format.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00044: The LDAP URL format must be ldap://<host>:<port> or ldaps://<host>:<port>; but found {0}.

Cause: Invalid LDAP URL format was found.

Action: The format of the LDAP URL must be ldap://<host>:<port> or ldaps://<host>:<port> format.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00045: The LDAP principal {0} is invalid.

Cause: The LDAP principal was invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00045: The LDAP principal {0} is invalid.

Cause: The LDAP principal was invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00045: The LDAP principal {0} is invalid.

Cause: The LDAP principal was invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00046: The LDAP credential is invalid.

Cause: The LDAP credential was invalid.

Action: Provide the correct credential value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00046: The LDAP credential is invalid.

Cause: The LDAP credential was invalid.

Action: Provide the correct credential value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00046: The LDAP credential is invalid.

Cause: The LDAP credential was invalid.

Action: Provide the correct credential value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00047: The Subject parameter cannot be null.

Cause: The supplied parameter was null.

Action: Check the Subject parameter supplied in the method call.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00047: The Subject parameter cannot be null.

Cause: The supplied parameter was null.

Action: Check the Subject parameter supplied in the method call.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00047: The Subject parameter cannot be null.

Cause: The supplied parameter was null.

Action: Check the Subject parameter supplied in the method call.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00048: Principals are missing in the Subject.

Cause: No principals were not found in the Subject.

Action: Verify that the supplied Subject contains principals.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00048: Principals are missing in the Subject.

Cause: No principals were not found in the Subject.

Action: Verify that the supplied Subject contains principals.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00048: Principals are missing in the Subject.

Cause: No principals were not found in the Subject.

Action: Verify that the supplied Subject contains principals.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00049: The authenticated user principal is missing in the Subject.

Cause: Authenticated user principal was not found in the Subject.

Action: Verify that the supplied Subject contains an authenticated user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00049: The authenticated user principal is missing in the Subject.

Cause: Authenticated user principal was not found in the Subject.

Action: Verify that the supplied Subject contains an authenticated user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00049: The authenticated user principal is missing in the Subject.

Cause: Authenticated user principal was not found in the Subject.

Action: Verify that the supplied Subject contains an authenticated user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00050: Invalid Subject parameter supplied.

Cause: The Subject contained an anonymous user principal and an authenticated user principal.

Action: Ensure that the Subject does not contain the anonymous user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00050: Invalid Subject parameter supplied.

Cause: The Subject contained an anonymous user principal and an authenticated user principal.

Action: Ensure that the Subject does not contain the anonymous user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00050: Invalid Subject parameter supplied.

Cause: The Subject contained an anonymous user principal and an authenticated user principal.

Action: Ensure that the Subject does not contain the anonymous user principal.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00051: The oracle.security.jps.config property not set.

Cause: The oracle.security.jps.config property was not set.

Action: Set the oracle.security.jps.config property to an appropriate value.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00051: The oracle.security.jps.config property not set.

Cause: The oracle.security.jps.config property was not set.

Action: Set the oracle.security.jps.config property to an appropriate value.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00051: The oracle.security.jps.config property not set.

Cause: The oracle.security.jps.config property was not set.

Action: Set the oracle.security.jps.config property to an appropriate value.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00052: Failed to Refresh Audit Service with new configuration.

Cause: Failed to reload the audit configuration.

Action: Check the audit configuration file to see if the lastest changes are valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00052: Failed to Refresh Audit Service with new configuration.

Cause: Failed to reload the audit configuration.

Action: Check the audit configuration file to see if the lastest changes are valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00052: Failed to Refresh Audit Service with new configuration.

Cause: Failed to reload the audit configuration.

Action: Check the audit configuration file to see if the lastest changes are valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00053: Component events file is missing for {0} at {1}.

Cause: The component events file for the given component type was missing.

Action: Verify that the properties set for the component files are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00053: Component events file is missing for {0} at {1}.

Cause: The component events file for the given component type was missing.

Action: Verify that the properties set for the component files are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00053: Component events file is missing for {0} at {1}.

Cause: The component events file for the given component type was missing.

Action: Verify that the properties set for the component files are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00054: Failed to create the auditor for {0}.

Cause: Failed to create the auditor object.

Action: Ensure that the component events file is not missing or corrupt and check the log files additional errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00054: Failed to create the auditor for {0}.

Cause: Failed to create the auditor object.

Action: Ensure that the component events file is not missing or corrupt and check the log files additional errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00054: Failed to create the auditor for {0}.

Cause: Failed to create the auditor object.

Action: Ensure that the component events file is not missing or corrupt and check the log files additional errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00055: Bootstrap credential store service is not initialized for the service configurator.

Cause: The bootstrap credetial store service was not initialised.

Action: Make sure the bootstrap credetial store service is initialized before any other services.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00055: Bootstrap credential store service is not initialized for the service configurator.

Cause: The bootstrap credetial store service was not initialised.

Action: Make sure the bootstrap credetial store service is initialized before any other services.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00055: Bootstrap credential store service is not initialized for the service configurator.

Cause: The bootstrap credetial store service was not initialised.

Action: Make sure the bootstrap credetial store service is initialized before any other services.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-00056: Failed to create identity store service instance {0}. Reason: {1}.

Cause: Failed to create identity store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00056: Failed to create identity store service instance {0}. Reason: {1}.

Cause: Failed to create identity store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00056: Failed to create identity store service instance {0}. Reason: {1}.

Cause: Failed to create identity store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00057: Failed to set OutputProperty for indent or XML encoding. Reason {0}.

Cause: Failed to setOutputProperty for indent or XML encoding. Cause: {0}

Action: Check the XML Transformer implementation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00057: Failed to set OutputProperty for indent or XML encoding. Reason {0}.

Cause: Failed to setOutputProperty for indent or XML encoding. Cause: {0}

Action: Check the XML Transformer implementation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00057: Failed to set OutputProperty for indent or XML encoding. Reason {0}.

Cause: Failed to setOutputProperty for indent or XML encoding. Cause: {0}

Action: Check the XML Transformer implementation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00058: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Reason {0}.

Cause: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Cause: {0}

Action: Check the JDK OutputStreamWriter supported encodings.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00058: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Reason {0}.

Cause: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Cause: {0}

Action: Check the JDK OutputStreamWriter supported encodings.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00058: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Reason {0}.

Cause: Failed to set XML output encoding to UTF-8 in OutputStreamWriter. Cause: {0}

Action: Check the JDK OutputStreamWriter supported encodings.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00059: The specified enterprise identity is null or invalid.

Cause: An enterprise identity provided was null or invalid

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00059: The specified enterprise identity is null or invalid.

Cause: An enterprise identity provided was null or invalid

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00059: The specified enterprise identity is null or invalid.

Cause: An enterprise identity provided was null or invalid

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00060: The specified enterprise identity {0} is not found in identity store.

Cause: The specified enterprise identity {0} was not found in the identity store.

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00060: The specified enterprise identity {0} is not found in identity store.

Cause: The specified enterprise identity {0} was not found in the identity store.

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00060: The specified enterprise identity {0} is not found in identity store.

Cause: The specified enterprise identity {0} was not found in the identity store.

Action: Provide a valid enterprise identity value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00061: No platform specific factory is found to create the platform principals. Check errors in the log files.

Cause: No platform specific factory was found to create platform principals.

Action: Check the log files for the errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00061: No platform specific factory is found to create the platform principals. Check errors in the log files.

Cause: No platform specific factory was found to create platform principals.

Action: Check the log files for the errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00061: No platform specific factory is found to create the platform principals. Check errors in the log files.

Cause: No platform specific factory was found to create platform principals.

Action: Check the log files for the errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00062: No identity store associated with policy store found.

Cause: No identity store associate with policy store found

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Configuration

JPS-00062: No identity store associate with policy store found.

Cause: No identity store associate with policy store found

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Configuration

JPS-00062: No identity store associate with policy store found.

Cause: No identity store associate with policy store found

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Configuration

JPS-00063: Jps servlet filter creation failed. Reason: {0}.

Cause: Jps Servlet Filter creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00063: Jps servlet filter creation failed. Reason: {0}.

Cause: Jps Servlet Filter creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00063: Jps servlet filter creation failed. Reason: {0}.

Cause: Jps Servlet Filter creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00064: Jps ejb interceptor creation failed. Reason: {0}.

Cause: Jps EJB Interceptor creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00064: Jps ejb interceptor creation failed. Reason: {0}.

Cause: Jps EJB Interceptor creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00064: Jps ejb interceptor creation failed. Reason: {0}.

Cause: Jps EJB Interceptor creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00065: Jps platform factory creation failed. Reason: {0}.

Cause: Jps Platform Factory creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00065: Jps platform factory creation failed. Reason: {0}.

Cause: Jps Platform Factory creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00065: Jps platform factory creation failed. Reason: {0}.

Cause: Jps Platform Factory creation failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Configuration

JPS-00066: Jps property value retrieval failed. Reason: {0}.

Cause: Jps property value retrieval failed

Action: Check the property values in jps configuration files
Level: 1

Type: ERROR

Impact: Configuration

JPS-00066: Jps property value retrieval failed. Reason: {0}.

Cause: Jps property value retrieval failed

Action: Check the property values in jps configuration files
Level: 1

Type: ERROR

Impact: Configuration

JPS-00066: Jps property value retrieval failed. Reason: {0}.

Cause: Jps property value retrieval failed

Action: Check the property values in jps configuration files
Level: 1

Type: ERROR

Impact: Configuration

JPS-00068: Ldap security checking failed. The LDAP url should start with ldaps and oracle.ldap.wltloc system property should be set. Reason : {0}.

Cause: Is LDAP secure failed

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Security

JPS-00068: Ldap security checking failed. The LDAP url should start with ldaps and oracle.ldap.wltloc system property should be set. Reason : {0}.

Cause: Is LDAP secure failed

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Security

JPS-00068: Ldap security checking failed. The LDAP url should start with ldaps and oracle.ldap.wltloc system property should be set. Reason : {0}.

Cause: Is LDAP secure failed

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Security

JPS-00069: Ldap credential store provider missing.

Cause: LDAP credential provider missed

Action: Ensure ldap credential store provider is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00069: Ldap credential store provider missing.

Cause: LDAP credential provider missed

Action: Ensure ldap credential store provider is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00069: Ldap credential store provider missing.

Cause: LDAP credential provider missed

Action: Ensure ldap credential store provider is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00070: Ldap policy store provider missing.

Cause: LDAP policy store provider missing

Action: Ensure ldap policy store is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00070: Ldap policy store provider missing.

Cause: LDAP policy store provider missing

Action: Ensure ldap policy store is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00070: Ldap policy store provider missing.

Cause: LDAP policy store provider missing

Action: Ensure ldap policy store is configured
Level: 1

Type: ERROR

Impact: Security

JPS-00071: Ldap bootstrap credential retrieval failed. Reason:{0}.

Cause: Retrieval of bootstrap credential failed

Action: Check the credential store configuration for credential types, maps and key
Level: 1

Type: ERROR

Impact: Security

JPS-00071: Ldap bootstrap credential retrieval failed. Reason:{0}.

Cause: Retrieval of bootstrap credential failed

Action: Check the credential store configuration for credential types, maps and key
Level: 1

Type: ERROR

Impact: Security

JPS-00071: Ldap bootstrap credential retrieval failed. Reason:{0}.

Cause: Retrieval of bootstrap credential failed

Action: Check the credential store configuration for credential types, maps and key
Level: 1

Type: ERROR

Impact: Security

JPS-00072: Policy schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of policy schema version in the store against to seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00072: Policy schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of policy schema version in the store against to seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00072: Policy schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of policy schema version in the store against to seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00073: Policy store schema version not found

Cause: Trying to determine version of the policy schema in the store

Action: Contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00073: Policy store schema version not found

Cause: Trying to determine version of the policy schema in the store

Action: Contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00073: Policy store schema version not found

Cause: Trying to determine version of the policy schema in the store

Action: Contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00074: Policy store schema version {0} is less than the latest schema version {1}, upgrade the Policy store schema to latest version.

Cause: Comparison of the Policy schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00074: Policy store schema version {0} is less than the latest schema version {1}, upgraded the Policy store schema to latest version.

Cause: Comparison of the Policy schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00074: Policy store schema version {0} is less than the latest schema version {1}, upgraded the Policy store schema to latest version.

Cause: Comparison of the Policy schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00075: Unable to query Policy store schema version under "{0}", Cause {1}

Cause: Query of Policy schema from the store failed

Action: Confirm the Policy store schema containers are present in the store
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00075: Unable to query Policy store schema version under "{0}", Cause {1}

Cause: Query of Policy schema from the store failed

Action: Confirm the Policy store schema containers are present in the store
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00075: Unable to query Policy store schema version under "{0}", Cause {1}

Cause: Query of Policy schema from the store failed

Action: Confirm the Policy store schema containers are present in the store
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00076: Policy schema version set to {0}

Cause: Version of the policy schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00076: Policy schema version set to {0}

Cause: Version of the policy schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00076: Policy schema version set to {0}

Cause: Version of the policy schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00077: Setting version of policy schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the Policy schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00077: Setting version of policy schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the Policy schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00077: Setting version of policy schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the Policy schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00078: Credential store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Credential schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00078: Credential store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Credential schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00078: Credential store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Credential schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00079: Credential store schema version not found

Cause: Check if the DN exists, or if the Credential Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00079: Credential store schema version not found

Cause: Check if the DN exists, or if the Credential Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00079: Credential store schema version not found

Cause: Check if the DN exists, or if the Credential Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00080: Credential store schema version {0} is less than the latest schema version {1}, upgrade the Credential store schema to latest version.

Cause: Comparison of the Credential schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00080: Credential store schema version {0} is less than the latest schema version {1}, upgraded the Credential store schema to latest version.

Cause: Comparison of the Credential schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00080: Credential store schema version {0} is less than the latest schema version {1}, upgraded the Credential store schema to latest version.

Cause: Comparison of the Credential schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00081: Unable to query Credential store schema version under "{0}", Cause {1}

Cause: Query of Credential schema from store store failed

Action: Confirm the Credential store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00081: Unable to query Credential store schema version under "{0}", Cause {1}

Cause: Query of Credential schema from store store failed

Action: Confirm the Credential store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00081: Unable to query Credential store schema version under "{0}", Cause {1}

Cause: Query of Credential schema from store store failed

Action: Confirm the Credential store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00082: Credential schema version set to {0}

Cause: Version of the credential schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00082: Credential schema version set to {0}

Cause: Version of the credential schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00082: Credential schema version set to {0}

Cause: Version of the credential schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00083: Setting version of credential schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the credential schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00083: Setting version of credential schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the credential schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00083: Setting version of credential schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the credential schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00084: IOException raised from FileLocker {0}.

Cause: Closing IO objects in FileLocker

Action: Check the file system for access privileges and disk space availability.
Level: 1

Type: WARNING

Impact: Other

JPS-00084: IOException raised from FileLocker {0}.

Cause: Closing IO objects in FileLocker

Action: Check the file system for access privileges and disk space availability.
Level: 1

Type: WARNING

Impact: Other

JPS-00084: IOException raised from FileLocker {0}.

Cause: Closing IO objects in FileLocker

Action: Check the file system for access privileges and disk space availability.
Level: 1

Type: WARNING

Impact: Other

JPS-00085: OID version is unavailable.

Cause: OID version is unavalable

Action: Check the ldap url against the server type passed.
Level: 1

Type: WARNING

Impact: Other

JPS-00085: OID version is unavailable.

Cause: OID version is unavalable

Action: Check the ldap url against the server type passed.
Level: 1

Type: WARNING

Impact: Other

JPS-00085: OID version is unavailable.

Cause: OID version is unavalable

Action: Check the ldap url against the server type passed.
Level: 1

Type: WARNING

Impact: Other

JPS-00086: Error while encoding search string: {0} to UTF-8 encoding

Cause: Unable to encode user string to UTF-8 encoding

Action: Check the search string.
Level: 1

Type: WARNING

Impact: Other

JPS-00086: Error while encoding search string: {0} to UTF-8 encoding

Cause: Unable to encode user string to UTF-8 encoding

Action: Check the search string.
Level: 1

Type: WARNING

Impact: Other

JPS-00086: Error while encoding search string: {0} to UTF-8 encoding

Cause: Unable to encode user string to UTF-8 encoding

Action: Check the search string.
Level: 1

Type: WARNING

Impact: Other

JPS-00087: The subject parameter is null.

Cause: The subject parameter is null

Action: Make sure the subject parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00087: The subject parameter is null.

Cause: The subject parameter is null

Action: Make sure the subject parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00087: The subject parameter is null.

Cause: The subject parameter is null

Action: Make sure the subject parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00088: The user name parameter is null.

Cause: The user name parameter is null

Action: Make sure the user name parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00088: The user name parameter is null.

Cause: The user name parameter is null

Action: Make sure the user name parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00088: The user name parameter is null.

Cause: The user name parameter is null

Action: Make sure the user name parameter is not null
Level: 1

Type: ERROR

Impact: Security

JPS-00089: The subject from the current AccessControlContext is null.

Cause: No subject is associated with the current AccessControlContext.

Action: Ensure that the subject is associated with the current AccessControlContext.
Level: 1

Type: ERROR

Impact: Security

JPS-00089: The subject from the current AccessControlContext is null.

Cause: No subject is associated with the current AccessControlContext.

Action: Ensure that the subject is associated with the current AccessControlContext.
Level: 1

Type: ERROR

Impact: Security

JPS-00089: The subject from the current AccessControlContext is null.

Cause: No subject is associated with the current AccessControlContext.

Action: Ensure that the subject is associated with the current AccessControlContext.
Level: 1

Type: ERROR

Impact: Security

JPS-00090: Failed to create policy store service instance {0}. Cause: {1}.

Cause: Failed to create policy store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00090: Failed to create policy store service instance {0}. Cause: {1}.

Cause: Failed to create policy store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00090: Failed to create policy store service instance {0}. Cause: {1}.

Cause: Failed to create policy store service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00091: No {0} available.

Cause: No {0} available.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00091: No {0} available.

Cause: No {0} available.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00091: No {0} available.

Cause: No {0} available.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00092: The ldap service was null.

Cause: The ldap service was null.

Action: Ensure the ldap service is not null.
Level: 1

Type: ERROR

Impact: Security

JPS-00092: The ldap service was null.

Cause: The ldap service was null.

Action: Ensure the ldap service is not null.
Level: 1

Type: ERROR

Impact: Security

JPS-00092: The ldap service was null.

Cause: The ldap service was null.

Action: Ensure the ldap service is not null.
Level: 1

Type: ERROR

Impact: Security

JPS-00093: Class {0} was not type of {1}.

Cause: Class {0} was not type of {1}.

Action: Ensure class name is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-00093: Class {0} was not type of {1}.

Cause: Class {0} was not type of {1}.

Action: Ensure class name is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-00093: Class {0} was not type of {1}.

Cause: Class {0} was not type of {1}.

Action: Ensure class name is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-00094: Failed to parse digest response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JPS-00094: Failed to parse digest response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JPS-00094: Failed to parse digest response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JPS-00095: {0} system properties not set.

Cause: System properties {0} not set.

Action: Set the system properties.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00095: {0} system properties not set.

Cause: System properties {0} not set.

Action: Set the system properties.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00095: {0} system properties not set.

Cause: System properties {0} not set.

Action: Set the system properties.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00096: No {0} defined for {1}.

Cause: No {0} defined for {1}.

Action: Defined the specified object.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00096: No {0} defined for {1}.

Cause: No {0} defined for {1}.

Action: Defined the specified object.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00096: No {0} defined for {1}.

Cause: No {0} defined for {1}.

Action: Defined the specified object.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00097: {0} missing in message : {1}.

Cause: {0} missing in message : {1}.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00097: {0} missing in message : {1}.

Cause: {0} missing in message : {1}.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00097: {0} missing in message : {1}.

Cause: {0} missing in message : {1}.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00098: Duplicate error message.

Cause: Duplicate error message.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00098: Duplicate error message.

Cause: Duplicate error message.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00098: Duplicate error message.

Cause: Duplicate error message.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00099: {0} already exists.

Cause: {0} already exists.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00099: {0} already exists.

Cause: {0} already exists.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00099: {0} already exists.

Cause: {0} already exists.

Action: Check the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00100: Failed to instantiate {0}.

Cause: Failed to instantiate {0}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00100: Failed to instantiate {0}.

Cause: Failed to instantiate {0}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00100: Failed to instantiate {0}.

Cause: Failed to instantiate {0}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00101: {0} not match {1}.

Cause: {0} not match with {1}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00101: {0} not match {1}.

Cause: {0} not match with {1}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00101: {0} not match {1}.

Cause: {0} not match with {1}.

Action: Check the object type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00102: Unhandled entry {0}

Cause: Unhandled entry {0}.

Action: Check the entry.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00102: Unhandled entry {0}

Cause: Unhandled entry {0}.

Action: Check the entry.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00102: Unhandled entry {0}

Cause: Unhandled entry {0}.

Action: Check the entry.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00103: Invalid login module type {0}.

Cause: Invalid login module type {0}.

Action: Use valid login module type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00103: Invalid login module type {0}.

Cause: Invalid login module type {0}.

Action: Use valid login module type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00103: Invalid login module type {0}.

Cause: Invalid login module type {0}.

Action: Use valid login module type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00104: System policy does not exist.

Cause: System policy does not exist.

Action: Ensure system policy exist.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00104: System policy does not exist.

Cause: System policy does not exist.

Action: Ensure system policy exist.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00104: System policy does not exist.

Cause: System policy does not exist.

Action: Ensure system policy exist.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00105: Failed to create temp dir {0}.

Cause: Failed to create temp dir {0}.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00105: Failed to create temp dir {0}.

Cause: Failed to create temp dir {0}.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00105: Failed to create temp dir {0}.

Cause: Failed to create temp dir {0}.

Action: Check the log for more details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00106: InputStream has no more data to read.

Cause: InputStream had no more data to read.

Action: Check the log for more details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00106: InputStream has no more data to read.

Cause: InputStream had no more data to read.

Action: Check the log for more details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00106: InputStream has no more data to read.

Cause: InputStream had no more data to read.

Action: Check the log for more details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00107: {0} invoked.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00107: {0} invoked.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00107: {0} invoked.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00108: Event {0} was ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00108: Event {0} was ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00108: Event {0} was ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00109: Overwriting credentials is allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00109: Overwriting credentials is allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00109: Overwriting credentials is allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00110: Failed to decode {0}. Reason {1}.

Cause: Failed to decode {0}. Reason: {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00110: Failed to decode {0}. Reason {1}.

Cause: Failed to decode {0}. Reason: {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00110: Failed to decode {0}. Reason {1}.

Cause: Failed to decode {0}. Reason: {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00111: Current timer interval ({0} seconds) is too short.

Cause: Current timer interval ({0} seconds) is too short.

Action: Please set a longer interval in the configuration file.
Level: 1

Type: WARNING

Impact: Security

JPS-00111: Current timer interval ({0} seconds) is too short.

Cause: Current timer interval ({0} seconds) is too short.

Action: Please set a longer interval in the configuration file.
Level: 1

Type: WARNING

Impact: Security

JPS-00111: Current timer interval ({0} seconds) is too short.

Cause: Current timer interval ({0} seconds) is too short.

Action: Please set a longer interval in the configuration file.
Level: 1

Type: WARNING

Impact: Security

JPS-00112: Set property {0} to value {1}.

Cause: Set property {0} to value {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00112: Set property {0} to value {1}.

Cause: Set property {0} to value {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00112: Set property {0} to value {1}.

Cause: Set property {0} to value {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00113: Failed to parse condition {0}. Reason {1}.

Cause: Failed to parse condition {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00113: Failed to parse condition {0}. Reason {1}.

Cause: Failed to arse condition {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00113: Failed to parse condition {0}. Reason {1}.

Cause: Failed to arse condition {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00114: Failed to load data file {0}.

Cause: Failed to load data file {0}.

Action: Please check file location.
Level: 1

Type: WARNING

Impact: Security

JPS-00114: Failed to load data file {0}.

Cause: Failed to load data file {0}.

Action: Please check file location.
Level: 1

Type: WARNING

Impact: Security

JPS-00114: Failed to load data file {0}.

Cause: Failed to load data file {0}.

Action: Please check file location.
Level: 1

Type: WARNING

Impact: Security

JPS-00115: Failed to modify JPS Schema.

Cause: Failed to modify JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00115: Failed to modify JPS Schema.

Cause: Failed to modify JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00115: Failed to modify JPS Schema.

Cause: Failed to modify JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00116: Failed to read JPS Schema.

Cause: Failed to read JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00116: Failed to read JPS Schema.

Cause: Failed to read JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00116: Failed to read JPS Schema.

Cause: Failed to read JPS Schema.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00117: Failed to delete System Policy name {0}. Reason {1}.

Cause: Failed to delete System Policy name {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00117: Failed to delete System Policy name {0}. Reason {1}.

Cause: Failed to delete System Policy name {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00117: Failed to delete System Policy name {0}. Reason {1}.

Cause: Failed to delete System Policy name {0}. Reason {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00118: {0} not found.

Cause: {0} not found.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00118: {0} not found.

Cause: {0} not found.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00118: {0} not found.

Cause: {0} not found.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00119: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Cause: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00119: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Cause: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00119: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Cause: Failed to create ResourceEntry name: {0}, action: {1}, cause: {2}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00120: Failed to seed attribute {0}, ldap object class {1}.

Cause: Failed to seed attribute {0}, ldap object class {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00120: Failed to seed attribute {0}, ldap object class {1}.

Cause: Failed to seed attribute {0}, ldap object class {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00120: Failed to seed attribute {0}, ldap object class {1}.

Cause: Failed to seed attribute {0}, ldap object class {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00121: Failed to parse LDIF record {0}. Reason: {1}.

Cause: Failed to parse LDIF record {0}. Reason: {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00121: Failed to parse LDIF record {0}. Reason: {1}.

Cause: Failed to parse LDIF record {0}. Reason: {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00121: Failed to parse LDIF record {0}. Reason: {1}.

Cause: Failed to parse LDIF record {0}. Reason: {1}.

Action: Check the LDAP configuration to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00122: Farm DN {0} does not exist.

Cause: Farm DN {0} does not exist.

Action: Ensure farm DN is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00122: Farm DN {0} does not exist.

Cause: Farm DN {0} does not exist.

Action: Ensure farm DN is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00122: Farm DN {0} does not exist.

Cause: Farm DN {0} does not exist.

Action: Ensure farm DN is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00123: RDN {0} not found under farm {1}.

Cause: RDN {0} not found under farm {1}.

Action: Check LDAP server type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00123: RDN {0} not found under farm {1}.

Cause: RDN {0} not found under farm {1}.

Action: Check LDAP server type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00123: RDN {0} not found under farm {1}.

Cause: RDN {0} not found under farm {1}.

Action: Check LDAP server type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00124: {0} is not supported.

Cause: {0} is not supported.

Action: Use a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00124: {0} was not supported.

Cause: {0} was not supported.

Action: Use a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00124: {0} was not supported.

Cause: {0} was not supported.

Action: Use a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00125: Property {0} was null.

Cause: Property {0} was null.

Action: Ensure property is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00125: Property {0} was null.

Cause: Property {0} was null.

Action: Ensure property is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00125: Property {0} was null.

Cause: Property {0} was null.

Action: Ensure property is not null.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-00126: Overwriting credentials is not allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00126: Overwriting credentials is not allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00126: Overwriting credentials is not allowed at application credential store migration with Weblogic server running in {0} and system property {1} set to {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00127: Failed to create igf service instance {0}. Reason: {1}.

Cause: Failed to create igf service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00127: Failed to create igf service instance {0}. Reason: {1}.

Cause: Failed to create igf service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00127: Failed to create igf service instance {0}. Reason: {1}.

Cause: Failed to create igf service instance {0}. Cause: {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00128: Keystore schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Keystore schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00128: Keystore schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Keystore schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00128: Keystore schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Keystore schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00129: Keystore schema version not found

Cause: Check if the DN exists, or if the Keystore schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00129: Keystore schema version not found

Cause: Check if the DN exists, or if the Keystore schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00129: Keystore schema version not found

Cause: Check if the DN exists, or if the Keystore schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00130: Keystore schema version {0} is less than the latest schema version {1}, upgrade the Keystore schema to latest version.

Cause: Comparison of the Keystore schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00130: Keystore schema version {0} is less than the latest schema version {1}, upgraded the Keystore schema to latest version.

Cause: Comparison of the Keystore schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00130: Keystore schema version {0} is less than the latest schema version {1}, upgraded the Keystore schema to latest version.

Cause: Comparison of the Keystore schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00131: Unable to query Keystore schema version under "{0}", Cause {1}

Cause: Query of Keystore schema from store store failed

Action: Confirm the Keystore schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00131: Unable to query Keystore schema version under "{0}", Cause {1}

Cause: Query of Keystore schema from store store failed

Action: Confirm the Keystore schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00131: Unable to query Keystore schema version under "{0}", Cause {1}

Cause: Query of Keystore schema from store store failed

Action: Confirm the Keystore schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00132: Keystore schema version set to {0}

Cause: Version of the keystore schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00132: Keystore schema version set to {0}

Cause: Version of the keystore schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00132: Keystore schema version set to {0}

Cause: Version of the keystore schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00133: Setting version of keystore schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the keystore schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00133: Setting version of keystore schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the keystore schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00133: Setting version of keystore schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the keystore schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00134: The offline deployment staging directory {0} does not exist.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00134: The offline deployment staging directory {0} does not exist.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00134: The offline deployment staging directory {0} does not exist.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00135: Exception occurs on saving ear file {0}.

Cause: The cause may be due to bad ear file or insufficient permission.

Action: Check the ear file and the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00135: Exception occurs on saving ear file {0}.

Cause: The cause may be due to bad ear file or insufficient permission.

Action: Check the ear file and the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00135: Exception occurs on saving ear file {0}.

Cause: The cause may be due to bad ear file or insufficient permission.

Action: Check the ear file and the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00136: Exception occurs on saving offline deployment property file in application directory {0}.

Cause: The cause may be due to insufficient permission.

Action: Check the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00136: Exception occurs on saving offline deployment property file in application directory {0}.

Cause: The cause may be due to insufficient permission.

Action: Check the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00136: Exception occurs on saving offline deployment property file in application directory {0}.

Cause: The cause may be due to insufficient permission.

Action: Check the file system permissiion.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00137: Found offline deployed app {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00137: Found offline deployed app {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00137: Found offline deployed app {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00138: Exception occurs on opening the staging application in {0}.

Cause: This may be caused by bad .ear file on the disk.

Action: Check the .ear file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00138: Exception occurs on opening the staging application in {0}.

Cause: This may be caused by bad .ear file on the disk.

Action: Check the .ear file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00138: Exception occurs on opening the staging application in {0}.

Cause: This may be caused by bad .ear file on the disk.

Action: Check the .ear file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00139: Exception occurs on loading the property file of the staging application in {0}.

Cause: Failed to open the property file.

Action: Check the property file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00139: Exception occurs on loading the property file of the staging application in {0}.

Cause: Failed to open the property file.

Action: Check the property file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00139: Exception occurs on loading the property file of the staging application in {0}.

Cause: Failed to open the property file.

Action: Check the property file on the disk.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00140: Failed to delete the staging app {0}. Migration flag file created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

JPS-00140: Failed to delete the staging app {0}. Migration flag file created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

JPS-00140: Failed to delete the staging app {0}. Migration flag file created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

JPS-00141: Cannot handle offline deployed application due to the required system property {0} is not set.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00141: Cannot handle offline deployed application due to the required system property {0} is not set.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00141: Cannot handle offline deployed application due to the required system property {0} is not set.

Cause: The cause may be that the product was installed inproperly.

Action: Install the product properly.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00142: No opss-application.xml found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00142: No opss-application.xml found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00142: No opss-application.xml found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

JPS-00143: Error on migrating security artifacts.

Cause: Error on migrating security artifacts.

Action: Check security related files in your application, such as opss-application.xml, jazn-data.xml, cwallet.sso, etc.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00143: Error on migrating security artifacts.

Cause: Error on migrating security artifacts.

Action: Check security related files in your application, such as opss-application.xml, jazn-data.xml, cwallet.sso, etc.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00143: Error on migrating security artifacts.

Cause: Error on migrating security artifacts.

Action: Check security related files in your application, such as opss-application.xml, jazn-data.xml, cwallet.sso, etc.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00144: Error on opening ear file {0}.

Cause: Error on opening ear file.

Action: Check the ear file.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00144: Error on opening ear file {0}.

Cause: Error on opening ear file.

Action: Check the ear file.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00144: Error on opening ear file {0}.

Cause: Error on opening ear file.

Action: Check the ear file.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00145: Found no installed application at {0}.

Cause: Found no installed application at {0}.

Action: Check the installed application at {0}.
Level: 1

Type: WARNING

Impact: Deployment

JPS-00145: Found no installed application at {0}.

Cause: Found no installed application at {0}.

Action: Check the installed application at {0}.
Level: 1

Type: WARNING

Impact: Deployment

JPS-00145: Found no installed application at {0}.

Cause: Found no installed application at {0}.

Action: Check the installed application at {0}.
Level: 1

Type: WARNING

Impact: Deployment

JPS-00146: Failed to create identity store service instance {0}. Reason: the service does not enable the virtualizes flag, but references other service instance.

Cause: Failed to create identity store service instance {0}. Cause: the service does not enable the virtualize flag, but references other service instance.

Action: Either make the virtualize flag true, or directly define the ldap configuration instead of using service reference
Level: 1

Type: WARNING

Impact: Configuration

JPS-00146: Failed to create identity store service instance {0}. Reason: the service does not enable the virtualize flag, but references other service instance.

Cause: Failed to create identity store service instance {0}. Cause: the service does not enable the virtualize flag, but references other service instance.

Action: Either make the virtualize flag true, or directly define the ldap configuration instead of using service reference
Level: 1

Type: WARNING

Impact: Configuration

JPS-00146: Failed to create identity store service instance {0}. Reason: the service does not enable the virtualize flag, but references other service instance.

Cause: Failed to create identity store service instance {0}. Cause: the service does not enable the virtualize flag, but references other service instance.

Action: Either make the virtualize flag true, or directly define the ldap configuration instead of using service reference
Level: 1

Type: WARNING

Impact: Configuration

JPS-00147: Keystore re-association not supported.

Cause: Configuration of key store was not suitable for re-association.

Action: Confirm the key store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00147: Keystore re-association not supported.

Cause: Configuration of key store was not suitable for re-association.

Action: Confirm the key store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00147: Keystore re-association not supported.

Cause: Configuration of key store was not suitable for re-association.

Action: Confirm the key store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00148: Jps JBoss signing key seeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00148: Jps JBoss signing key seeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00148: Jps JBoss signing key seeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00149: Jps JBoss signing key already exists. Seeding ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00149: Jps JBoss signing key already exists. Seeding ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00149: Jps JBoss signing key already exists. Seeding ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00150: Key 1 and Key 2 are no longer supported for system parameter -Djps.subject.cache.key, please use key 4 (default), 3, or 5 (fastest).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00150: Key 1 and Key 2 are no longer supported for system parameter -Djps.subject.cache.key, please use key 4 (default), 3, or 5 (fastest).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00150: Key 1 and Key 2 are no longer supported for system parameter -Djps.subject.cache.key, please use key 4 (default), 3, or 5 (fastest).

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00151: Audit store instantiation failure, type: {0} reason: {1}

Cause: Audit metadata store failed to be instantiated, type: {0}, reason: {1}

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00151: Audit store instantiation failure, type: {0} reason: {1}

Cause: Audit metadata store failed to be instantiated, type: {0}, reason: {1}

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00151: Audit store instantiation failure, type: {0} reason: {1}

Cause: Audit metadata store failed to be instantiated, type: {0}, reason: {1}

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00152: Component not registered, name: {0}

Cause: Component {0} not registered and no audit configuration found.

Action: Register component with audit service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00152: Component not registered, name: {0}

Cause: Component {0} not registered and no audit configuration found.

Action: Register component with audit service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00152: Component not registered, name: {0}

Cause: Component {0} not registered and no audit configuration found.

Action: Register component with audit service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00153: The principal {0} is invalid.

Cause: The principal is invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00153: The principal {0} is invalid.

Cause: The principal is invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00153: The principal {0} is invalid.

Cause: The principal is invalid.

Action: Provide a correct value for principal.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00154: The rule condition {0} is invalid.

Cause: The rule condition function is invalid.

Action: Provide a correct value for rule condition function.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00154: The rule condition {0} is invalid.

Cause: The rule condition function is invalid.

Action: Provide a correct value for rule condition function.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00154: The rule condition {0} is invalid.

Cause: The rule condition function is invalid.

Action: Provide a correct value for rule condition function.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00155: Audit metadata store is not instantiated in audit service.

Cause: Audit metadata store is not instantiated.

Action: Verify that the audit store properties for audit service are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00155: Audit metadata store is not instantiated in audit service.

Cause: Audit metadata store is not instantiated.

Action: Verify that the audit store properties for audit service are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00155: Audit metadata store is not instantiated in audit service.

Cause: Audit metadata store is not instantiated.

Action: Verify that the audit store properties for audit service are correct in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00156: Audit metadata store type {0} is invalid

Cause: Audit metadata store type {0} is invalid

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00156: Audit metadata store type {0} is invalid

Cause: Audit metadata store type {0} is invalid

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00156: Audit metadata store type {0} is invalid

Cause: Audit metadata store type {0} is invalid

Action: Check the audit service configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00157: The DN {0} was invalid LdapName format, see javax.naming.ldap.LdapName

Cause: The DN {0} was invalid LdapName format, see javax.naming.ldap.LdapName

Action: Ensure property in format of javax.naming.ldap.LdapName.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00157: The DN {0} is invalid

Cause: The DN {0} is invalid

Action: Check the given DN value.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00157: The DN {0} is invalid

Cause: The DN {0} is invalid

Action: Check the given DN value.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00158: Audit store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Audit schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00158: Audit store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Audit schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00158: Audit store schema upgrade not required. Store Schema version {0} is compatible to the seed schema version {1}

Cause: Comparison of Audit schema version in the store against the seed schema version.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00159: Audit store schema version not found

Cause: Check if the DN exists, or if the Audit Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00159: Audit store schema version not found

Cause: Check if the DN exists, or if the Audit Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00159: Audit store schema version not found

Cause: Check if the DN exists, or if the Audit Store schema version attribute is present at the specificied location

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00160: Audit store schema version {0} is less than the latest schema version {1}, upgrade the Audit store schema to latest version.

Cause: Comparison of the Audit schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00160: Audit store schema version {0} is less than the latest schema version {1}, upgraded the Credential store schema to latest version.

Cause: Comparison of the Audit schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00160: Audit store schema version {0} is less than the latest schema version {1}, upgraded the Credential store schema to latest version.

Cause: Comparison of the Audit schema version in the store against the schema to seed

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00161: Unable to query Audit store schema version under "{0}", Cause {1}

Cause: Query of Audit schema from store store failed

Action: Confirm the Audit store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00161: Unable to query Audit store schema version under "{0}", Cause {1}

Cause: Query of Audit schema from store store failed

Action: Confirm the Audit store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00161: Unable to query Audit store schema version under "{0}", Cause {1}

Cause: Query of Audit schema from store store failed

Action: Confirm the Audit store schema container in the store is present
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00162: Audit schema version set to {0}

Cause: Version of the audit schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00162: Audit schema version set to {0}

Cause: Version of the audit schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00162: Audit schema version set to {0}

Cause: Version of the audit schema has been set in the store

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00163: Setting version of audit schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the audit schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00163: Setting version of audit schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the audit schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00163: Setting version of audit schema in the store failed. Cause {0}

Cause: Unexpected error occurred while setting the version of the audit schema in the store

Action: Confirm the container is present in the store and caller has sufficient privileges to perform this operation
Level: 1

Type: ERROR

Impact: Configuration

JPS-00164: Audit store re-association not supported.

Cause: Configuration of audit store was not suitable for re-association.

Action: Confirm the audit store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00164: Audit store re-association not supported.

Cause: Configuration of audit store was not suitable for re-association.

Action: Confirm the audit store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00164: Audit store re-association not supported.

Cause: Configuration of audit store was not suitable for re-association.

Action: Confirm the audit store configuration is updated.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00165: Failed to reload component {0} runtime policy with error message {1}.

Cause: Failed to reload component runtime policy.

Action: Check component run policy and custom fitler preset definition.
Level: 1

Type: ERROR

Impact: Other

JPS-00165: Failed to reload component {0} runtime policy with error message {1}.

Cause: Failed to reload component runtime policy.

Action: Check component run policy and custom fitler preset definition.
Level: 1

Type: ERROR

Impact: Other

JPS-00165: Failed to reload component {0} runtime policy with error message {1}.

Cause: Failed to reload component runtime policy.

Action: Check component run policy and custom fitler preset definition.
Level: 1

Type: ERROR

Impact: Other

JPS-00166: Failed to retrieve Embedded LDAP store information.

Cause: Failed to retrieve embedded ldap store information.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00167: Invalid xml content was found. {0} Location: {1}.

Cause: Invalid xml content was found. {0} Location: {1}.

Action: Fix the invalid xml elements according to the xsd schema definition.
Level: 1

Type: WARNING

Impact: Security

JPS-00167: Failed to validate the xml content. {0} Location: {1}.

Cause: Failed to validate the xml content. {0} Location: {1}.

Action: Fix the invalid xml elements according to the xsd schema definition.
Level: 1

Type: WARNING

Impact: Security

JPS-00167: Failed to validate the xml content. {0} Location: {1}.

Cause: Failed to validate the xml content. {0} Location: {1}.

Action: Fix the invalid xml elements according to the xsd schema definition.
Level: 1

Type: WARNING

Impact: Security

JPS-00168: OID server version {0} is not supported

Cause: OID server version {0} is not supported

Action: Check the support matrix.
Level: 1

Type: ERROR

Impact: Other

JPS-00168: OID server version {0} is not supported

Cause: OID server version {0} is not supported

Action: Check the support matrix.
Level: 1

Type: ERROR

Impact: Other

JPS-00168: OID server version {0} is not supported

Cause: OID server version {0} is not supported

Action: Check the support matrix.
Level: 1

Type: ERROR

Impact: Other

JPS-00169: Cannot get server log directory. Reason: {0}.

Cause: Cannot get server log directory. Reason: {0}.

Action: Check server configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00169: Failed to get server log directory. Reason: {0}.

Cause: Failed to get server log directory. Reason: {0}.

Action: Check server configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00169: Failed to get server log directory. Reason: {0}.

Cause: Failed to get server log directory. Reason: {0}.

Action: Check server configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00170: Initializing OPSS Java Policy Provider.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00171: OPSS Java Policy Provider initialized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00172: OPSS Java Policy Provider is set as the system-wide Policy object.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00173: OPSS Java Policy Provider is already set as the system-wide Policy object. Skipped setting the system-wide Policy object.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00174: Failed to create the enterprise user principal for "{0}". Reason: {1}.

Cause: Error on creating the enterprise user principal.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00175: Failed to create the enterprise group principal for "{0}". Reason: {1}.

Cause: Error on creating the enterprise group principal.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00176: Service instance of {0} is in state {1} that does not allow invocation of {2}.

Cause: Service instance is in a state that does not allow current invocation.

Action: Only invoke service instance's method when it is in right state.
Level: 1

Type: WARNING

Impact: Security

JPS-00177: Failed to clean up application security artifacts.

Cause: Error on cleaning up application security artifacts.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Deployment

JPS-00178: Service provider " {0} " not available from configuration service.

Cause: Service provider not available.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00179: Service context configuration for " {0} " not available from configuration service.

Cause: Service context configuration not available.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00180: Failed to create service context for tenant ID " {0} ".

Cause: Failed to create service context.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00181: Your search criteria (current search iterator) has expired(stale). Start a new search.

Cause: Your search criteria (current search iterator) has expired(stale).

Action: Start a new search.
Level: 1

Type: ERROR

Impact: Other

JPS-00182: Method getView for JpsConfigurationP was not run for RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter

Cause: Method getView for JpsConfigurationP was not run for RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter

Action: Call method getView for JpsConfigurationP on RuntimeViewAdapter object before calling getServiceProperties() of ServiceInstanceDescriptorAdapter
Level: 1

Type: ERROR

Impact: Configuration

JPS-00183: Jps diagnostics started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00184: Jps diagnostics startup failed.

Cause: Failed to start JPS diagnostics.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Other

JPS-00185: Tenant Context is not set

Cause: Tenant Context is not set

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-00186: Failed to validate the Tenant Context for the tenant with ID " {0} ".

Cause: Tenant Context is Invalid

Action: Only invoke services that you signed up for
Level: 1

Type: ERROR

Impact: Security

JPS-00187: A dump to execute JPS diagnostic tests.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00188: Dumps security information in current execution thread, such as application name, subject, etc.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00189: OPSS diagnostic test to execute.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00190: Tenant ID cannot be found from user "{0}" profile.

Cause: Tenant ID cannot be found from authenticated user profile.

Action: Check user profile.
Level: 1

Type: WARNING

Impact: Other

JPS-00191: Identity context not found.

Cause: IdentityContext not found from request attributes.

Action: OAM IAP.
Level: 1

Type: WARNING

Impact: Other

JPS-00192: Service instance not found for the service type.

Cause: Service instance not available for the service type.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00193: Service instance "{0}" cannot be instantiated. Reason: {1}.

Cause: Service instance cannot be instantiated.

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00194: OPSS diagnostic test parameters to execute. Example: username=user1;groupname=group1

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00195: Dumps properties used to initialize User/Role Api when User/Role Api initialization fails.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00196: Jps started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00197: Failed to migrate application credential during deployment.

Cause: Migration of Application credential failed during deployment.

Action: Check the server logs for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00198: Custom product logger set (class: {0}, name: {1}). All JPS messages would be redirected to this logger.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00199: JpsLogger has initialized Loggers. Cannot set custom product Logger after initializing loggers.

Cause: Loggers have already been initialized.

Action: Set product logger before creating JpsLogger instance.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00200: Invalid path. Please make sure the provided config path is a directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00201: Invalid path. Please make sure the provided config directory has jps-config.xml and jps-config-jse.xml inside it.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00202: Jps post service activation operations started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00203: Upgrade of file based domain not supported.

Cause: Upgrading of file based domain not supported

Action: Please move the file based domain to database based domain, then run reconfiguration
Level: 1

Type: ERROR

Impact: Configuration

JPS-00204: Migrate source or destination store context lookup failure

Cause: Migrate source or destination context in migration could not be looked up.

Action: Check the configuration file to verify service context settings
Level: 1

Type: ERROR

Impact: Configuration

JPS-00205: Security store version configured is incompatible

Cause: Security store version configured is incompatible with this release.

Action: Please use security store version 12.1.3 or lower
Level: 1

Type: ERROR

Impact: Configuration

JPS-00206: Jps is already started.

Cause: Can not start Jps again since it is already started.

Action: Please do not start JPS if it is already started
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00207: Service context {0} is not in active state

Cause: Service context is not in active state.

Action: Please check logs to see service context failure.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00208: Jps initializing.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00209: Jps startup failed.

Cause: Jps startup is failed due to some error.

Action: Please check logs to see Jps startup failure.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00210: Jps inactive.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00211: Not supported platform type {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00212: Error occurred while stopping jps due to: {0}.

Cause: Error occured while stopping the OPSS

Action: Check the server logs for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00214: Operation "{0}" is not supported in OPSS Mode "{1}".

Cause: the invoked operation is not supported in JPS_API mode

Action: set the OPSS Mode to one of COMPATIBLE or MULTIPLE
Level: 1

Type: ERROR

Impact: Configuration

JPS-00216: Failed to get a handle to the global audit service for tenant {0}.

Cause: Failed to get a handle to the global audit service

Action: Check configuration
Level: 1

Type: ERROR

Impact: Security

JPS-00217: The schema specified in {0} is already in use for security store. Please create a new schema.

Cause: The schema specified in {0} is already in use for security store.

Action: Please create a new schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00218: Comparison of credential failed for map : {0}, key : {1}.

Cause: Encryption key comparison failed.

Action: Retry importEncryptionKey command or api.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00219: Expected keys not found in the credential map : {0}.

Cause: Expected keys not found in the credential map

Action: Verify the credential store content.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-00220: Cannot find datasource definition {0}. Reason: {1}.

Cause: Cannot find datasource definition {0}. Reason: {1}.

Action: Check weblogic configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00221: Error occurred while resetting jps due to: {0}.

Cause: Error occured while resetting OPSS

Action: Check the server logs for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00222: Jps is reset.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-00223: Specified JPS context "{0}" not found

Cause: Specified JPS context not found

Action: Check the configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-00224: Invalid inputted migration parameters "{0}"

Cause: Invalid inputted migration parameters

Action: Check inputted migration parameters.
Level: 1

Type: ERROR

Impact: Security

JPS-00225: Commmand: {0} is not supported.

Cause: Commmand: {0} is not supported.

Action: Use a valid command. Try <command> --help for more information.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00226: Service setup check completed for configurator.

Cause: Service setup check completed for configurator.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00227: Completed the Migration of Policy Artifacts.

Cause: Completed the Migration of Policy Artifacts.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-00228: Security store is not seeded with the schema.

Cause: Security store is not seeded with the schema.

Action: Check the log files to resolve the warning.
Level: 1

Type: WARNING

Impact: Other

JPS-00229: Trying to load the schema into the security store ...

Cause: Trying to load the schema into the security store ...

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00230: BootStrap Wallet file is created.

Cause: BootStrap Wallet file is created.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Programmatic

JPS-00231: Completed the seeding of schema into the security store.

Cause: Completed the seeding of schema into the security store.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

JPS-00232: Successfully loaded the security store schema.

Cause: Successfully loaded the security store schema.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00233: Migration of Policy Artifacts failed.

Cause: Migration of Policy Artifacts failed.

Action: Check the log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-00234: Persist jps-config.xml to directory: {0} - done.

Cause: Persist jps-config.xml to directory: {0} - done.

Action: No action Required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00235: Persist jps-config-jse.xml to directory: {0} - done.

Cause: Persist jps-config-jse.xml to directory: {0} - done.

Action: No action Required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-00236: Bootstrap key store service instance already present in bootstrap credential store context.

Cause: Bootstrap key store service instance already present in bootstrap credential store context.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00237: Adding keystore service instance to bootstrap context for the {0} file.

Cause: Adding keystore service instance to bootstrap context for the {0} file.

Action: No Action Required
Level: 1

Type: NOTIFICATION

Impact: Process

JPS-00238: Error in loading the property file.

Cause: Error in loading the property file.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00239: Exception while updating the keystore service instance to bootstrap context for {0} file.

Cause: Exception while updating the keystore service instance to bootstrap context for {0} file.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Process

JPS-00240: JpsConfiguration object is not passed, not able to add Keystore service instance to Bootstrap context.

Cause: JpsConfiguration object is not passed, not able to add Keystore service instance to Bootstrap context.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00241: No file based keystore service instance is found, not able to add Keystore service instance to Bootstrap context.

Cause: This operation is not supported in restricted-JRF domain

Action: Please check document for supported operations in restricted-JRf domain
Level: 1

Type: ERROR

Impact: Configuration

JPS-00242: This operation is not supported in restricted-JRF domain

Cause: No file based keystore service instance is found, not able to add Keystore service instance to Bootstrap context.

Action: Check the log files to resolve the error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-00243: {0} cannot be started as JRF Executor serivce retrieval got failed.

Cause: {0} cannot be started as JRF Executor serivce retrieval got failed.

Action: Check stack trace for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-00244: No audit log directory is set. Cannot perform audit operations for component {0}.

Cause: Failed to get audit log directory. Audit calls may fail.

Action: Check if the audit log directory is set either in audit service properties or as a system property.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00245: No audit log directory is set. Disabling audit for component {0}.

Cause: Failed to get audit log directory.

Action: Check if the audit log directory is set either in audit service properties or as a system property.
Level: 1

Type: WARNING

Impact: Configuration

JPS-00246: new Startup().start() is required to be called before using OPSS API.

Cause: OPSS API is used without calling new Startup().start() first.

Action: Call new Startup().start() before using OPSS API.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01000: The credential map {0} is invalid.

Cause: The specified credential map name was invalid.

Action: Ensure the credential map name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01000: The credential map {0} is invalid.

Cause: The specified credential map name was invalid.

Action: Ensure the credential map name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01000: The credential map {0} is invalid.

Cause: The specified credential map name was invalid.

Action: Ensure the credential map name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01001: The credential key {0} is invalid.

Cause: The specified credential key name was invalid.

Action: Ensure the credential key name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01001: The credential key {0} is invalid.

Cause: The specified credential key name was invalid.

Action: Ensure the credential key name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01001: The credential key {0} is invalid.

Cause: The specified credential key name was invalid.

Action: Ensure the credential key name is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01002: The value {0} is invalid in this password credential.

Cause: The specified password credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01002: The value {0} is invalid in this password credential.

Cause: The specified password credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01002: The value {0} is invalid in this password credential.

Cause: The specified password credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01003: The value of name {0}, url {1}, of port {2} is invalid in this datasource credential.

Cause: The specified datasource credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01003: The value of name {0}, url {1}, of port {2} is invalid in this datasource credential.

Cause: The specified datasource credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01003: The value of name {0}, url {1}, of port {2} is invalid in this datasource credential.

Cause: The specified datasource credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01004: The value {0} is invalid in this generic credential.

Cause: The specified generic credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01004: The value {0} is invalid in this generic credential.

Cause: The specified generic credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01004: The value {0} is invalid in this generic credential.

Cause: The specified generic credential was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01005: The credential type {0} is not supported.

Cause: The specified credential type was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01005: The credential type {0} is not supported.

Cause: The specified credential type was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01005: The credential type {0} is not supported.

Cause: The specified credential type was invalid.

Action: Use only a supported credential type. The supported types are {0}.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01006: The credential expired on {0}.

Cause: This credential expired on {0}.

Action: Create a new credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01006: The credential expired on {0}.

Cause: This credential expired on {0}.

Action: Create a new credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01006: The credential expired on {0}.

Cause: This credential expired on {0}.

Action: Create a new credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01007: The credential with map {0} and key {1} already exists.

Cause: This credential already existed.

Action: Use a credential with different map name or key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01007: The credential with map {0} and key {1} already exists.

Cause: This credential already existed.

Action: Use a credential with different map name or key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01007: The credential with map {0} and key {1} already exists.

Cause: This credential already existed.

Action: Use a credential with different map name or key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01008: The credential map name {0} already exists.

Cause: This credential map name already existed.

Action: Use a different map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01008: The credential map name {0} already exists.

Cause: This credential map name already existed.

Action: Use a different map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01008: The credential map name {0} already exists.

Cause: This credential map name already existed.

Action: Use a different map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01009: The credential with map {0} and key {1} does not exist.

Cause: This credential did not exist.

Action: Check the credential map name and key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01009: The credential with map {0} and key {1} does not exist.

Cause: This credential did not exist.

Action: Check the credential map name and key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01009: The credential with map {0} and key {1} does not exist.

Cause: This credential did not exist.

Action: Check the credential map name and key.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01010: The credential map {0} does not exist.

Cause: This credential map name did not exist.

Action: Check the credential map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01010: The credential map {0} does not exist.

Cause: This credential map name did not exist.

Action: Check the credential map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01010: The credential map {0} does not exist.

Cause: This credential map name did not exist.

Action: Check the credential map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01011: The credential store location property {0} is not configured, or the configured value {1} is invalid.

Cause: The credential store location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01011: The credential store location property {0} is not configured, or the configured value {1} is invalid.

Cause: The credential store location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01011: The credential store location property {0} is not configured, or the configured value {1} is invalid.

Cause: The credential store location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01012: The credential property {0} is invalid or not defined.

Cause: The credential property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01012: The credential property {0} is invalid or not defined.

Cause: The credential property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01012: The credential property {0} is invalid or not defined.

Cause: The credential property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01013: The credential store DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected credential store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01013: The credential store DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected credential store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01013: The credential store DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected credential store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01014: The credential {0} is invalid.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01014: The credential {0} is invalid.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01014: The credential {0} is invalid.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01015: Cannot retrieve credential {0}.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01015: Cannot retrieve credential {0}.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01015: Cannot retrieve credential {0}.

Cause: This credential was invalid.

Action: Use only a supported credential type. The supported types are password or generic.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01016: A password credential is expected; instead found {0} for alias {1} and key {2} at location {3}.

Cause: Wrong credential type was found.

Action: Use the password credential type. Expecting password credential but found {0} for alias {1} and key {2} at location {3}.
Level: 1

Type: WARNING

Impact: Other

JPS-01016: A password credential is expected; instead found {0} for alias {1} and key {2} at location {3}.

Cause: Wrong credential type was found.

Action: Use the password credential type. Expecting password credential but found {0} for alias {1} and key {2} at location {3}.
Level: 1

Type: WARNING

Impact: Other

JPS-01016: A password credential is expected; instead found {0} for alias {1} and key {2} at location {3}.

Cause: Wrong credential type was found.

Action: Use the password credential type. Expecting password credential but found {0} for alias {1} and key {2} at location {3}.
Level: 1

Type: WARNING

Impact: Other

JPS-01017: A generic credential is expected; instead found {0}.

Cause: Wrong credential type was found.

Action: Use the generic credential type. Expecting generic credential but found {0}.
Level: 1

Type: WARNING

Impact: Other

JPS-01017: A generic credential is expected; instead found {0}.

Cause: Wrong credential type was found.

Action: Use the generic credential type. Expecting generic credential but found {0}.
Level: 1

Type: WARNING

Impact: Other

JPS-01017: A generic credential is expected; instead found {0}.

Cause: Wrong credential type was found.

Action: Use the generic credential type. Expecting generic credential but found {0}.
Level: 1

Type: WARNING

Impact: Other

JPS-01018: A password credential is missing in the credential store.

Cause: The password credential was not found in the credential store.

Action: Ensure that the credential is present in the credential store.
Level: 1

Type: ERROR

Impact: Session

JPS-01018: A password credential is missing in the credential store.

Cause: The password credential was not found in the credential store.

Action: Ensure that the credential is present in the credential store.
Level: 1

Type: ERROR

Impact: Session

JPS-01018: A password credential is missing in the credential store.

Cause: The password credential was not found in the credential store.

Action: Ensure that the credential is present in the credential store.
Level: 1

Type: ERROR

Impact: Session

JPS-01019: The credential store {0} has been moved or deleted.

Cause: The specified credential store did not exist.

Action: Ensure that the credential store location is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01019: The credential store {0} has been moved or deleted.

Cause: The specified credential store did not exist.

Action: Ensure that the credential store location is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01019: The credential store {0} has been moved or deleted.

Cause: The specified credential store did not exist.

Action: Ensure that the credential store location is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01020: Cannot create store {0}.

Cause: Could not create the credential store.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01020: Cannot create store {0}.

Cause: Could not create the credential store.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01020: Cannot create store {0}.

Cause: Could not create the credential store.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01021: The generic credential {0} is not serializable.

Cause: This generic credential was not serializable.

Action: Make this credential serializable.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01021: The generic credential {0} is not serializable.

Cause: This generic credential was not serializable.

Action: Make this credential serializable.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01021: The generic credential {0} is not serializable.

Cause: This generic credential was not serializable.

Action: Make this credential serializable.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01022: The expiration time {0} is invalid: the expiration time must be later than the creation time.

Cause: Invalid credential expiration time.

Action: Set the expiration time to a time later than the credential creation time.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01022: The expiration time {0} is invalid: the expiration time must be later than the creation time.

Cause: Invalid credential expiration time.

Action: Set the expiration time to a time later than the credential creation time.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01022: The expiration time {0} is invalid: the expiration time must be later than the creation time.

Cause: Invalid credential expiration time.

Action: Set the expiration time to a time later than the credential creation time.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01023: Store does not contain all expected maps. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01023: Store does not contain all expected maps. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01023: Store does not contain all expected maps. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01024: Store contains all expected maps. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01024: Store contains all expected maps. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01024: Store contains all expected maps. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01025: Store does not contain all expected credentials. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01025: Store does not contain all expected credentials. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01025: Store does not contain all expected credentials. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01026: Store contains all expected credentials. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01026: Store contains all expected credentials. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01026: Store contains all expected credentials. Result {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01027: Cannot get credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01027: Cannot get credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01027: Cannot get credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01028: successful getting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01028: successful getting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01028: successful getting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01029: successful getting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01029: successful getting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01029: successful getting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01030: Cannot get credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01030: Cannot get credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01030: Cannot get credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01031: Cannot retrieve map names. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01031: Cannot retrieve map names. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01031: Cannot retrieve map names. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01032: successful setting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01032: successful setting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01032: successful setting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01033: Cannot set credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01033: Cannot set credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01033: Cannot set credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01034: successful resetting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01034: successful resetting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01034: successful resetting of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01035: Cannot reset credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01035: Cannot reset credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01035: Cannot reset credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01036: successful setting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01036: successful setting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01036: successful setting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01037: Cannot set credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01037: Cannot set credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01037: Cannot set credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01038: successful resetting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01038: successful resetting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01038: successful resetting of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01039: Cannot reset credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01039: Cannot reset credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01039: Cannot reset credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01040: successful deletion of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01040: successful deletion of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01040: successful deletion of credential

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01041: Cannot delete credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01041: Cannot delete credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01041: Cannot delete credential. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01042: successful deletion of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01042: successful deletion of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01042: successful deletion of credential map

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01043: Cannot delete credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01043: Cannot delete credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01043: Cannot delete credential map. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01044: successful deletion of all credentials from the store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01044: successful deletion of all credentials from the store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01044: successful deletion of all credentials from the store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01045: Cannot delete all credentials from the store. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01045: Cannot delete all credentials from the store. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01045: Cannot delete all credentials from the store. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01046: successful retrieving of map names; mapNameSet {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01046: successful retrieving of map names; mapNameSet {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01046: successful retrieving of map names; mapNameSet {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01047: Cannot persist the wallet. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01047: Cannot persist the wallet. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01047: Cannot persist the wallet. Reason {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-01048: Modifying of credential failed. Reason {0}

Cause: Modification of credential failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01048: Modifying of credential failed. Reason {0}

Cause: Modification of credential failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01048: Modifying of credential failed. Reason {0}

Cause: Modification of credential failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01049: Reading all credentials from the store failed. Reason {0}

Cause: Read of all credentials failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01049: Reading all credentials from the store failed. Reason {0}

Cause: Read of all credentials failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01049: Reading all credentials from the store failed. Reason {0}

Cause: Read of all credentials failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01050: Opening of wallet based credential store failed. Reason {0}

Cause: Credential wallet could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01050: Opening of wallet based credential store failed. Reason {0}

Cause: Credential wallet could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01050: Opening of wallet based credential store failed. Reason {0}

Cause: Credential wallet could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01051: Credential audit events cannot be logged. Reason {0}

Cause: Credential store audit events logging not enabled

Action: Check the audit configuration to ensure auditing enabled
Level: 1

Type: WARNING

Impact: Compliance

JPS-01051: Credential audit events cannot be logged. Reason {0}

Cause: Credential store audit events logging not enabled

Action: Check the audit configuration to ensure auditing enabled
Level: 1

Type: WARNING

Impact: Compliance

JPS-01051: Credential audit events cannot be logged. Reason {0}

Cause: Credential store audit events logging not enabled

Action: Check the audit configuration to ensure auditing enabled
Level: 1

Type: WARNING

Impact: Compliance

JPS-01052: Credential audit event logging failed. Reason {0}

Cause: Credential audit event logging failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01052: Credential audit event logging failed. Reason {0}

Cause: Credential audit event logging failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01052: Credential audit event logging failed. Reason {0}

Cause: Credential audit event logging failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01053: Creation of new credential map failed. Reason {0}

Cause: Creation of new credential map failed

Action: Ensure all jps libraries are in setup properly in the runtime
Level: 1

Type: WARNING

Impact: Compliance

JPS-01053: Creation of new credential map failed. Reason {0}

Cause: Creation of new credential map failed

Action: Ensure all jps libraries are in setup properly in the runtime
Level: 1

Type: WARNING

Impact: Compliance

JPS-01053: Creation of new credential map failed. Reason {0}

Cause: Creation of new credential map failed

Action: Ensure all jps libraries are in setup properly in the runtime
Level: 1

Type: WARNING

Impact: Compliance

JPS-01054: Refresh of credential wallet failed. Reason {0}

Cause: Refresh of credstore wallet failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01054: Refresh of credential wallet failed. Reason {0}

Cause: Refresh of credstore wallet failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01054: Refresh of credential wallet failed. Reason {0}

Cause: Refresh of credstore wallet failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01055: Could not create credential store instance. Reason {0}

Cause: Could not create credential store instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01055: Could not create credential store instance. Reason {0}

Cause: Could not create credential store instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01055: Could not create credential store instance. Reason {0}

Cause: Could not create credential store instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-01056: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Cause: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Action: Check the value of the location property
Level: 1

Type: ERROR

Impact: Configuration

JPS-01056: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Cause: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Action: Check the value of the location property
Level: 1

Type: ERROR

Impact: Configuration

JPS-01056: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Cause: The credential store location {0} was invalid. It should be a directory or full path to cwallet.sso file.

Action: Check the value of the location property
Level: 1

Type: ERROR

Impact: Configuration

JPS-01057: The credential map was invalid. Reason {0}

Cause: The credential map was null.

Action: Check the value of the credential map
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01057: The credential map was invalid. Reason {0}

Cause: The credential map was null.

Action: Check the value of the credential map
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01057: The credential map was invalid. Reason {0}

Cause: The credential map was null.

Action: Check the value of the credential map
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01058: The credential dn {0} was invalid.

Cause: The credential dn was invalid.

Action: Ensure the credential dn is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01058: The credential dn {0} was invalid.

Cause: The credential dn was invalid.

Action: Ensure the credential dn is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01058: The credential dn {0} was invalid.

Cause: The credential dn was invalid.

Action: Ensure the credential dn is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01059: The credential store instance {0} was not fully initialized.

Cause: The credential store was not fully initialized until data source is available.

Action: Wait and retry later
Level: 1

Type: ERROR

Impact: Configuration

JPS-01059: The credential store instance {0} was not fully initialized.

Cause: The credential store was not fully initialized until data source is available.

Action: Wait and retry later
Level: 1

Type: ERROR

Impact: Configuration

JPS-01059: The credential store instance {0} was not fully initialized.

Cause: The credential store was not fully initialized until data source is available.

Action: Wait and retry later
Level: 1

Type: ERROR

Impact: Configuration

JPS-01060: The credential store instance does not have the property ldap url/JDBC url/datasource JNDI name defined.

Cause: The credential store property ldap.url or jdbc.url or datasource.jndi.name was not defined.

Action: Check the configuration for this property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01060: The credential store instance does not have the property ldap url/JDBC url/datasource JNDI name defined.

Cause: The credential store property ldap.url or jdbc.url or datasource.jndi.name was not defined.

Action: Check the configuration for this property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01060: The credential store instance does not have the property ldap url/JDBC url/datasource JNDI name defined.

Cause: The credential store property ldap.url or jdbc.url or datasource.jndi.name was not defined.

Action: Check the configuration for this property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01061: Access to boostrap credential store denied to application code.

Cause: Application code was trying to access a bootstrap credential store. Bootstrap credential store is intended only for the OPSS usage.

Action: bootstrap_credstore_context need not be used for credential store operations.
Level: 1

Type: ERROR

Impact: Security

JPS-01062: A backup of the bootstrap credential store could not be created.

Cause: A backup of the bootstrap cwallet.sso could not be created.

Action: Investigate the logs to find out the root cause of the exception in file operations
Level: 1

Type: ERROR

Impact: Security

JPS-01063: Credential compatibility check failed. Cannot migrate credential: {0}

Cause: There exists one or more generic credential in the store that cannot be migrated.

Action: Ensure that the store does not contain any generic credential with binary attribute before migration.
Level: 1

Type: WARNING

Impact: Security

JPS-01064: Invalid password: Passwords must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-01065: Could not decrypt credential due to encryption key mismatch.

Cause: Decryption of credential failed

Action: Ensure that the bootstrap wallet contains the correct encryption key that was used to encrypt the credentials in the store.
Level: 1

Type: ERROR

Impact: Security

JPS-01500: The anonymous service configuration is missing.

Cause: The anonymous service configuration was missing in jps-config.xml.

Action: Configure the anonymous service in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01500: The anonymous service configuration is missing.

Cause: The anonymous service configuration was missing in jps-config.xml.

Action: Configure the anonymous service in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01500: The anonymous service configuration is missing.

Cause: The anonymous service configuration was missing in jps-config.xml.

Action: Configure the anonymous service in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01501: The anonymous identity store provider instance {0} is not found.

Cause: The anonymous identity store provider configuration was invalid.

Action: Check the anonymous identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01501: The anonymous identity store provider instance {0} is not found.

Cause: The anonymous identity store provider configuration was invalid.

Action: Check the anonymous identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01501: The anonymous identity store provider instance {0} is not found.

Cause: The anonymous identity store provider configuration was invalid.

Action: Check the anonymous identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01502: The LDAP identity store provider instance {0} is not found.

Cause: Invalid or missing LDAP identity store provider configuration.

Action: Check LDAP identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01502: The LDAP identity store provider instance {0} is not found.

Cause: Invalid or missing LDAP identity store provider configuration.

Action: Check LDAP identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01502: The LDAP identity store provider instance {0} is not found.

Cause: Invalid or missing LDAP identity store provider configuration.

Action: Check LDAP identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01503: The XML identity store provider instance {0} is not found.

Cause: Invalid or missing XML identity store provider configuration.

Action: Check the XML identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01503: The XML identity store provider instance {0} is not found.

Cause: Invalid or missing XML identity store provider configuration.

Action: Check the XML identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01503: The XML identity store provider instance {0} is not found.

Cause: Invalid or missing XML identity store provider configuration.

Action: Check the XML identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01504: The secret store provider for provider {0} and instance {1} does not exist.

Cause: The credential provider was missing.

Action: Check the configuration of the credential store provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01504: The secret store provider for provider {0} and instance {1} does not exist.

Cause: The credential provider was missing.

Action: Check the configuration of the credential store provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01504: The secret store provider for provider {0} and instance {1} does not exist.

Cause: The credential provider was missing.

Action: Check the configuration of the credential store provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-01505: The key store provider {0} is missing or not configured.

Cause: The keystore provider configuration was missing in jps-config.xml.

Action: Configure a keystore provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01505: The key store provider {0} is missing or not configured.

Cause: The keystore provider configuration was missing in jps-config.xml.

Action: Configure a keystore provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01505: The key store provider {0} is missing or not configured.

Cause: The keystore provider configuration was missing in jps-config.xml.

Action: Configure a keystore provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01506: Invalid context name.

Cause: Invalid context name found.

Action: Check the configurations of contexts in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01506: Invalid context name.

Cause: Invalid context name found.

Action: Check the configurations of contexts in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01506: Invalid context name.

Cause: Invalid context name found.

Action: Check the configurations of contexts in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01507: Invalid login module name.

Cause: Invalid login module name found.

Action: Check the login module configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01507: Invalid login module name.

Cause: Invalid login module name found.

Action: Check the login module configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01507: Invalid login module name.

Cause: Invalid login module name found.

Action: Check the login module configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01508: Invalid login module descriptor.

Cause: Invalid login module descriptor found.

Action: Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01508: Invalid login module descriptor.

Cause: Invalid login module descriptor found.

Action: Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01508: Invalid login module descriptor.

Cause: Invalid login module descriptor found.

Action: Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01509: Invalid login module class name.

Cause: Invalid login module class name found.

Action: Check the loginModuleClassName property in the login module instance configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01509: Invalid login module class name.

Cause: Invalid login module class name found.

Action: Check the loginModuleClassName property in the login module instance configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01509: Invalid login module class name.

Cause: Invalid login module class name found.

Action: Check the loginModuleClassName property in the login module instance configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01510: Invalid login module entries.

Cause: Invalid login module entries found.

Action: The expected login module to be invoked is not present or misconfigured. Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01510: Invalid login module entries.

Cause: Invalid login module entries found.

Action: The expected login module to be invoked is not present or misconfigured. Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01510: Invalid login module entries.

Cause: Invalid login module entries found.

Action: The expected login module to be invoked is not present or misconfigured. Check the login module instance configurations in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01511: Invalid login module entry.

Cause: The login module entries were not valid in the jps-config.xml file.

Action: Correct the login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01511: Invalid login module entry.

Cause: The login module entries were not valid in the jps-config.xml file.

Action: Correct the login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01511: Invalid login module entry.

Cause: The login module entries were not valid in the jps-config.xml file.

Action: Correct the login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01512: Missing login module entry.

Cause: The login module entries were missing in the jps-config.xml file.

Action: Add the appropriate login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01512: Missing login module entry.

Cause: The login module entries were missing in the jps-config.xml file.

Action: Add the appropriate login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01512: Missing login module entry.

Cause: The login module entries were missing in the jps-config.xml file.

Action: Add the appropriate login module entries in service instances and service providers.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01513: The configuration of the JAAS login provider {0} and the service instance {1} are missing.

Cause: The login module provider was missing.

Action: Ensure that a login module provider is configured in the jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01513: The configuration of the JAAS login provider {0} and the service instance {1} are missing.

Cause: The login module provider was missing.

Action: Ensure that a login module provider is configured in the jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01513: The configuration of the JAAS login provider {0} and the service instance {1} are missing.

Cause: The login module provider was missing.

Action: Ensure that a login module provider is configured in the jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01514: The default context is missing in jps-config.xml.

Cause: Default context was missing in jps-config.xml.

Action: Add a default context to jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01514: The default context is missing in jps-config.xml.

Cause: Default context was missing in jps-config.xml.

Action: Add a default context to jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01514: The default context is missing in jps-config.xml.

Cause: Default context was missing in jps-config.xml.

Action: Add a default context to jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01515: A context named anonymous is missing in jps-config.xml.

Cause: Context named anonymous was missing in jps-config.xml.

Action: Add a context named anonymous in jps-config.xml file with an anonymous service instance reference.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01515: A context named anonymous is missing in jps-config.xml.

Cause: Context named anonymous was missing in jps-config.xml.

Action: Add a context named anonymous in jps-config.xml file with an anonymous service instance reference.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01515: A context named anonymous is missing in jps-config.xml.

Cause: Context named anonymous was missing in jps-config.xml.

Action: Add a context named anonymous in jps-config.xml file with an anonymous service instance reference.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01516: The default credential store service is missing in default jps-config.xml.

Cause: The default credential store service was missing in the default context in jps-config.xml.

Action: There must be at least one credential store service configured in the default context.
Level: 1

Type: ERROR

Impact: Other

JPS-01516: The default credential store service is missing in default jps-config.xml.

Cause: The default credential store service was missing in the default context in jps-config.xml.

Action: There must be at least one credential store service configured in the default context.
Level: 1

Type: ERROR

Impact: Other

JPS-01516: The default credential store service is missing in default jps-config.xml.

Cause: The default credential store service was missing in the default context in jps-config.xml.

Action: There must be at least one credential store service configured in the default context.
Level: 1

Type: ERROR

Impact: Other

JPS-01517: The generic identity store provider is missing.

Cause: Invalid or missing generic identity store provider configuration.

Action: Check the generic identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01517: The generic identity store provider is missing.

Cause: Invalid or missing generic identity store provider configuration.

Action: Check the generic identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01517: The generic identity store provider is missing.

Cause: Invalid or missing generic identity store provider configuration.

Action: Check the generic identity store provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01518: The anonymous service is not available in the application context.

Cause: The anonymous service was not available in context.

Action: Check the context in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-01518: The anonymous service is not available in the application context.

Cause: The anonymous service was not available in context.

Action: Check the context in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-01518: The anonymous service is not available in the application context.

Cause: The anonymous service was not available in context.

Action: Check the context in jps-config.xml.
Level: 1

Type: ERROR

Impact: Session

JPS-01519: The default context configuration is missing in jps-config.xml.

Cause: The default context configuration was not available in jps-config.xml.

Action: Ensure that the default context is present in jps-config.xml.
Level: 1

Type: WARNING

Impact: Session

JPS-01519: The default context configuration is missing in jps-config.xml.

Cause: The default context configuration was not available in jps-config.xml.

Action: Ensure that the default context is present in jps-config.xml.
Level: 1

Type: WARNING

Impact: Session

JPS-01519: The default context configuration is missing in jps-config.xml.

Cause: The default context configuration was not available in jps-config.xml.

Action: Ensure that the default context is present in jps-config.xml.
Level: 1

Type: WARNING

Impact: Session

JPS-01520: Cannot initialize identity store, cause: {0}.

Cause: Could not initialize identity store.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01520: Cannot initialize identity store, cause: {0}.

Cause: Could not initialize identity store.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01520: Cannot initialize identity store, cause: {0}.

Cause: Could not initialize identity store.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01521: Identity store file path is invalid.

Cause: Identity store file path was invalid or null.

Action: Ensure that the path configured with the property ADF_IM_FILE_PATH is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01521: Identity store file path is invalid.

Cause: Identity store file path was invalid or null.

Action: Ensure that the path configured with the property ADF_IM_FILE_PATH is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01521: Identity store file path is invalid.

Cause: Identity store file path was invalid or null.

Action: Ensure that the path configured with the property ADF_IM_FILE_PATH is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01522: The Jps configuration is invalid.

Cause: JPS configuration was null or invalid.

Action: Verify configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01522: The Jps configuration is invalid.

Cause: JPS configuration was null or invalid.

Action: Verify configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01522: The Jps configuration is invalid.

Cause: JPS configuration was null or invalid.

Action: Verify configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01523: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was not valid.

Action: Verify that the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01523: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was not valid.

Action: Verify that the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01523: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was not valid.

Action: Verify that the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01524: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service provider configuration was invalid.

Action: Veirfy that the provider is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01524: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service provider configuration was invalid.

Action: Veirfy that the provider is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01524: The service instance {0} is invalid or not configured in jps-config.xml.

Cause: A service provider configuration was invalid.

Action: Veirfy that the provider is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01525: The identity store service is not properly configured.

Cause: Found invalid identity store service configuration in jps-config.xml.

Action: Ensure a valid identity store configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01525: The identity store service is not properly configured.

Cause: Found invalid identity store service configuration in jps-config.xml.

Action: Ensure a valid identity store configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01525: The identity store service is not properly configured.

Cause: Found invalid identity store service configuration in jps-config.xml.

Action: Ensure a valid identity store configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01526: Configured identity store, user manager, or role manager is invalid. The error is {0}.

Cause: Found null value for configured identity store, user manager, or role manager.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01526: Configured identity store, user manager, or role manager is invalid. The error is {0}.

Cause: Found null value for configured identity store, user manager, or role manager.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01526: Configured identity store, user manager, or role manager is invalid. The error is {0}.

Cause: Found null value for configured identity store, user manager, or role manager.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01527: The identity store factory name is not configured.

Cause: Could not find identity store factory name.

Action: Use the property ADF_IM_FACTORY_CLASS to specify the factory class.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01527: The identity store factory name is not configured.

Cause: Could not find identity store factory name.

Action: Use the property ADF_IM_FACTORY_CLASS to specify the factory class.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01527: The identity store factory name is not configured.

Cause: Could not find identity store factory name.

Action: Use the property ADF_IM_FACTORY_CLASS to specify the factory class.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01528: Idm identity store is invalid.

Cause: The identity store was not configured correctly.

Action: Correct the configuration of the identity store in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01528: Idm identity store is invalid.

Cause: The identity store was not configured correctly.

Action: Correct the configuration of the identity store in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01528: Idm identity store is invalid.

Cause: The identity store was not configured correctly.

Action: Correct the configuration of the identity store in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01529: The context {0} contains multiple services of type {1}.

Cause: The context {0} contains multiple services of type {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01529: The context {0} contains multiple services of type {1}.

Cause: The context {0} contains multiple services of type {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01529: The context {0} contains multiple services of type {1}.

Cause: The context {0} contains multiple services of type {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01530: The anonymous service is already configured in the context {0}.

Cause: The anonymous service is already configured in the context {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01530: The anonymous service is already configured in the context {0}.

Cause: The anonymous service is already configured in the context {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01530: The anonymous service is already configured in the context {0}.

Cause: The anonymous service is already configured in the context {0}.

Action: Check jps-config.xml for correctness.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01531: Configuration location {0} is a directory. File name expected.

Cause: Configuration location {0} is a directory. File name expected.

Action: Provide a valid configuration file location, including a file name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01531: Configuration location {0} is a directory. File name expected.

Cause: Configuration location {0} is a directory. File name expected.

Action: Provide a valid configuration file location, including a file name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01531: Configuration location {0} is a directory. File name expected.

Cause: Configuration location {0} is a directory. File name expected.

Action: Provide a valid configuration file location, including a file name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01532: The service instance location {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was invalid.

Action: Verify that the location of the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01532: The service instance location {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was invalid.

Action: Verify that the location of the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01532: The service instance location {0} is invalid or not configured in jps-config.xml.

Cause: A service instance configuration was invalid.

Action: Verify that the location of the instance is correctly configured in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01533: Failed to create service instance {0} for application {1}.

Cause: Failed to create service instance {0} for application {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01533: Failed to create service instance {0} for application {1}.

Cause: Failed to create service instance {0} for application {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01533: Failed to create service instance {0} for application {1}.

Cause: Failed to create service instance {0} for application {1}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01534: Failed to get identity store configuration.

Cause: Failed to get identity store configuration.

Action: Ensure the configuration is available.
Level: 1

Type: ERROR

Impact: Security

JPS-01534: Failed to get identity store configuration.

Cause: Failed to get identity store configuration.

Action: Ensure the configuration is available.
Level: 1

Type: ERROR

Impact: Security

JPS-01534: Failed to get identity store configuration.

Cause: Failed to get identity store configuration.

Action: Ensure the configuration is available.
Level: 1

Type: ERROR

Impact: Security

JPS-01535: Failed to get configuration name {0}.

Cause: Failed to get configuration name {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01535: Failed to get configuration name {0}.

Cause: Failed to get configuration name {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01535: Failed to get configuration name {0}.

Cause: Failed to get configuration name {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01536: Failed to evaluate XML expression on Object {0}.

Cause: Failed to evaluate XML expression on Object {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01536: Failed to evaluate XML expression on Object {0}.

Cause: Failed to evaluate XML expression on Object {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01536: Failed to evaluate XML expression on Object {0}.

Cause: Failed to evaluate XML expression on Object {0}.

Action: Check the log files to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-01537: Failed to handle config location {0}. Reason {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

JPS-01537: Failed to handle config location {0}. Reason {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

JPS-01537: Failed to handle config location {0}. Reason {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Security

JPS-01538: The default policy provider was not found.

Cause: The default policy provider was not found.

Action: Ensure policy provider configuration is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-01538: The default policy provider was not found.

Cause: The default policy provider was not found.

Action: Ensure policy provider configuration is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-01538: The default policy provider was not found.

Cause: The default policy provider was not found.

Action: Ensure policy provider configuration is correct.
Level: 1

Type: ERROR

Impact: Security

JPS-01539: The Ovd IGF service provider instance {0} is not found.

Cause: Invalid or missing Ovd IGF service provider configuration.

Action: Check Ovd IGF service provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01539: The Ovd IGF service provider instance {0} is not found.

Cause: Invalid or missing Ovd IGF service provider configuration.

Action: Check Ovd IGF service provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01539: The Ovd IGF service provider instance {0} is not found.

Cause: Invalid or missing Ovd IGF service provider configuration.

Action: Check Ovd IGF service provider configuration in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01543: The value of {0} is invalid. It must be an integer.

Cause: attribute.expire.time.seconds is not an integer.

Action: Ensure attribute.expire.time.seconds is a valid integer.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01543: The value of {0} is invalid. It must be an integer.

Cause: attribute.expire.time.seconds is not an integer.

Action: Ensure attribute.expire.time.seconds is a valid integer.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01543: The value of {0} is invalid. It must be an integer.

Cause: attribute.expire.time.seconds is not an integer.

Action: Ensure attribute.expire.time.seconds is a valid integer.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01544: The provided configuration file path {0} is invalid or null.

Cause: The provided configuration file path {0} is invalid or null.

Action: Provide a valid configuration file path.
Level: 1

Type: ERROR

Impact: Configuration

JPS-01545: Back up of JPS Config file {0} done.

Cause: Back up of JPS Config file {0} done.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-02000: The authentication of user {0} succeeded.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02000: The authentication of user {0} succeeded.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02000: The authentication of user {0} succeeded.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02001: The authentication of user {0} failed. Reason: {1}

Cause: User authentication failed.

Action: Ensure the user exists in the identity store. Check the user credentials that are being sent for authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02001: The authentication of user {0} failed.

Cause: User authentication failed.

Action: Ensure the user exists in the identity store. Check the user credentials that are being sent for authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02001: The authentication of user {0} failed.

Cause: User authentication failed.

Action: Ensure the user exists in the identity store. Check the user credentials that are being sent for authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02003: Authentication failed.

Cause: Could not authenticate user.

Action: Ensure that authentication uses valid user name and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02003: Authentication failed.

Cause: Could not authenticate user.

Action: Ensure that authentication uses valid user name and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02003: Authentication failed.

Cause: Could not authenticate user.

Action: Ensure that authentication uses valid user name and password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02004: Cannot authenticate user {0}.

Cause: Could not authenticate user.

Action: Ensure that the credentials provided for authentication are correct.
Level: 1

Type: ERROR

Impact: Security

JPS-02004: Cannot authenticate user {0}.

Cause: Could not authenticate user.

Action: Ensure that the credentials provided for authentication are correct.
Level: 1

Type: ERROR

Impact: Security

JPS-02004: Cannot authenticate user {0}.

Cause: Could not authenticate user.

Action: Ensure that the credentials provided for authentication are correct.
Level: 1

Type: ERROR

Impact: Security

JPS-02005: Cannot login user {0} because {1}. Check the log files for more details.

Cause: Encountered an error while authenticating user.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02005: Cannot login user {0} because {1}. Check the log files for more details.

Cause: Encountered an error while authenticating user.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02005: Cannot login user {0} because {1}. Check the log files for more details.

Cause: Encountered an error while authenticating user.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02008: Authenticated role name is invalid: property {0} is invalid or not configured.

Cause: Found invalid or undefined authentication role name property.

Action: Ensure that authentication role name properties are valid in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02008: Authenticated role name is invalid: property {0} is invalid or not configured.

Cause: Found invalid or undefined authentication role name property.

Action: Ensure that authentication role name properties are valid in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02008: Authenticated role name is invalid: property {0} is invalid or not configured.

Cause: Found invalid or undefined authentication role name property.

Action: Ensure that authentication role name properties are valid in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02009: SAML trusted assertion issuer is not configured: property set {0} is not configured.

Cause: Could not find configuration for SAML trusted assertion issuer.

Action: Set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02009: SAML trusted assertion issuer is not configured: property set {0} is not configured.

Cause: Could not find configuration for SAML trusted assertion issuer.

Action: Set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02009: SAML trusted assertion issuer is not configured: property set {0} is not configured.

Cause: Could not find configuration for SAML trusted assertion issuer.

Action: Set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02010: Cannot verify SAML assertion.

Cause: Found invalid assertion; SAML trusted assertion issuer was not configured.

Action: Check assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02010: Cannot verify SAML assertion.

Cause: Found invalid assertion; SAML trusted assertion issuer was not configured.

Action: Check assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02010: Cannot verify SAML assertion.

Cause: Found invalid assertion; SAML trusted assertion issuer was not configured.

Action: Check assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02011: SAML assertion is missing name identifier.

Cause: Found invalid assertion: name identifier was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02011: SAML assertion is missing name identifier.

Cause: Found invalid assertion: name identifier was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02011: SAML assertion is missing name identifier.

Cause: Found invalid assertion: name identifier was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02012: SAML assertion subject name is invalid.

Cause: Found invalid assertion: subject name was null.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02012: SAML assertion subject name is invalid.

Cause: Found invalid assertion: subject name was null.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02012: SAML assertion subject name is invalid.

Cause: Found invalid assertion: subject name was null.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02013: SAML assertion issuer name is invalid.

Cause: Found invalid assertion: issuer name was invalid.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02013: SAML assertion issuer name is invalid.

Cause: Found invalid assertion: issuer name was invalid.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02013: SAML assertion issuer name is invalid.

Cause: Found invalid assertion: issuer name was invalid.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02014: SAML assertion is invalid.

Cause: Found invalid assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02014: SAML assertion is invalid.

Cause: Found invalid assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02014: SAML assertion is invalid.

Cause: Found invalid assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02015: SAML assertion has missing subject.

Cause: Found invalid assertion: subject statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02015: SAML assertion has missing subject.

Cause: Found invalid assertion: subject statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02015: SAML assertion has missing subject.

Cause: Found invalid assertion: subject statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02016: SAML assertion is missing conditions.

Cause: Found invalid assertion: condition statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02016: SAML assertion is missing conditions.

Cause: Found invalid assertion: condition statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02016: SAML assertion is missing conditions.

Cause: Found invalid assertion: condition statement was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02017: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "not before" in the SAML assertion is set to a date earlier than or equal to today's date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02017: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "not before" in the SAML assertion is set to a date earlier than or equal to today's date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02017: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "not before" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "not before" in the SAML assertion is set to a date earlier than or equal to today's date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02018: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "on or after" in the SAML assertion is set to a valid date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02018: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "on or after" in the SAML assertion is set to a valid date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02018: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Cause: Found invalid condition "on or after" in SAML assertion. Current Time:{0}, {1} milli seconds, {2} Time:{3}.

Action: Verify that the condition "on or after" in the SAML assertion is set to a valid date.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02019: SAML assertion is missing assertion issuers signature.

Cause: Found invalid assertion: assertion issuers signature was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02019: SAML assertion is missing assertion issuers signature.

Cause: Found invalid assertion: assertion issuers signature was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02019: SAML assertion is missing assertion issuers signature.

Cause: Found invalid assertion: assertion issuers signature was missing.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02020: Signature for SAML assertion issuer is invalid.

Cause: Found invalid signature in SAML assertion issuer.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02020: Signature for SAML assertion issuer is invalid.

Cause: Found invalid signature in SAML assertion issuer.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02020: Signature for SAML assertion issuer is invalid.

Cause: Found invalid signature in SAML assertion issuer.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02021: Signature certificate (X509 Data) for SAML assertion issuer is invalid.

Cause: Found invalid signature certificate (X509 Data) in SAML assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02021: Signature certificate (X509 Data) for SAML assertion issuer is invalid.

Cause: Found invalid signature certificate (X509 Data) in SAML assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02021: Signature certificate (X509 Data) for SAML assertion issuer is invalid.

Cause: Found invalid signature certificate (X509 Data) in SAML assertion.

Action: Ensure the use of a valid assertion.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02022: Cannot verify signature for SAML assertion.

Cause: Failed to verify issuers signature in assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02022: Cannot verify signature for SAML assertion.

Cause: Failed to verify issuers signature in assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02022: Cannot verify signature for SAML assertion.

Cause: Failed to verify issuers signature in assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02023: Cannot verify SAML assertion signature certificate path.

Cause: Found invalid assertion signature.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02023: Cannot verify SAML assertion signature certificate path.

Cause: Found invalid assertion signature.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02023: Cannot verify SAML assertion signature certificate path.

Cause: Found invalid assertion signature.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02024: Cannot retrieve trusted CA policy for issuer {0}.

Cause: Found invalid assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02024: Cannot retrieve trusted CA policy for issuer {0}.

Cause: Found invalid assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02024: Cannot retrieve trusted CA policy for issuer {0}.

Cause: Found invalid assertion.

Action: Check the assertion and set the property saml.trusted.issuers in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02025: Cannot modify read-only Subject.

Cause: Could not modify a read-only subject.

Action: Ensure the program logic is correct and that the program does not attempt to modify a read-only subject.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02025: Cannot modify read-only Subject.

Cause: Could not modify a read-only subject.

Action: Ensure the program logic is correct and that the program does not attempt to modify a read-only subject.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02025: Cannot modify read-only Subject.

Cause: Could not modify a read-only subject.

Action: Ensure the program logic is correct and that the program does not attempt to modify a read-only subject.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02026: X509 certificate is invalid.

Cause: The X509 certificate passed to the callback handler was null or invalid.

Action: Ensure that the callback handler uses a valid X509 certificate.
Level: 1

Type: ERROR

Impact: Other

JPS-02026: X509 certificate is invalid.

Cause: The X509 certificate passed to the callback handler was null or invalid.

Action: Ensure that the callback handler uses a valid X509 certificate.
Level: 1

Type: ERROR

Impact: Other

JPS-02026: X509 certificate is invalid.

Cause: The X509 certificate passed to the callback handler was null or invalid.

Action: Ensure that the callback handler uses a valid X509 certificate.
Level: 1

Type: ERROR

Impact: Other

JPS-02027: The property set {0} is missing in jps-config.xml.

Cause: Could not find property set in jps-config.xml.

Action: Configure the property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02027: The property set {0} is missing in jps-config.xml.

Cause: Could not find property set in jps-config.xml.

Action: Configure the property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02027: The property set {0} is missing in jps-config.xml.

Cause: Could not find property set in jps-config.xml.

Action: Configure the property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02028: The extended property set {0} is missing in jps-config.xml.

Cause: Could not find extended property set in jps-config.xml.

Action: Configure the extended property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02028: The extended property set {0} is missing in jps-config.xml.

Cause: Could not find extended property set in jps-config.xml.

Action: Configure the extended property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02028: The extended property set {0} is missing in jps-config.xml.

Cause: Could not find extended property set in jps-config.xml.

Action: Configure the extended property set in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02029: The default realm is not configured in identity store service {0}.

Cause: Could not find the default realm in the identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02029: The default realm is not configured in identity store service {0}.

Cause: Could not find the default realm in the identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02029: The default realm is not configured in identity store service {0}.

Cause: Could not find the default realm in the identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02030: The default realm configured in identity store service {0} is empty or null.

Cause: Found null default realm configured in identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02030: The default realm configured in identity store service {0} is empty or null.

Cause: Found null default realm configured in identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02030: The default realm configured in identity store service {0} is empty or null.

Cause: Found null default realm configured in identity store service.

Action: Configure the default realm property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02031: The invalid realm name property {0} is configured in identity store service {1}.

Cause: Found invalid realm name property in identity store service.

Action: Configure the correct realm name property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02031: The invalid realm name property {0} is configured in identity store service {1}.

Cause: Found invalid realm name property in identity store service.

Action: Configure the correct realm name property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02031: The invalid realm name property {0} is configured in identity store service {1}.

Cause: Found invalid realm name property in identity store service.

Action: Configure the correct realm name property in the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02032: The duplicate realm name {0} is configured in identity store service {1}.

Cause: Found duplicate realm in identity store service.

Action: Remove duplicate realm configuration from the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02032: The duplicate realm name {0} is configured in identity store service {1}.

Cause: Found duplicate realm in identity store service.

Action: Remove duplicate realm configuration from the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02032: The duplicate realm name {0} is configured in identity store service {1}.

Cause: Found duplicate realm in identity store service.

Action: Remove duplicate realm configuration from the identity store service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02033: The realm name {0} passed for authentication is invalid. Was expecting {1}, but found {0}.

Cause: Found invalid realm name {0}. Was expecting {1}, but found {0}.

Action: Check the realm name passed to the authentication of user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02033: The realm name {0} passed for authentication is invalid. Was expecting {1}, but found {0}.

Cause: Found invalid realm name {0}. Was expecting {1}, but found {0}.

Action: Check the realm name passed to the authentication of user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02033: The realm name {0} passed for authentication is invalid. Was expecting {1}, but found {0}.

Cause: Found invalid realm name {0}. Was expecting {1}, but found {0}.

Action: Check the realm name passed to the authentication of user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02034: Realm name is missing in user name for authentication in multi-realm configuration.

Cause: The realm name was not supplied for authentication of multi-realm configuration.

Action: Ensure that the realm name value is passed in the user name when authenticating a multi-realm configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02034: Realm name is missing in user name for authentication in multi-realm configuration.

Cause: The realm name was not supplied for authentication of multi-realm configuration.

Action: Ensure that the realm name value is passed in the user name when authenticating a multi-realm configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02034: Realm name is missing in user name for authentication in multi-realm configuration.

Cause: The realm name was not supplied for authentication of multi-realm configuration.

Action: Ensure that the realm name value is passed in the user name when authenticating a multi-realm configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02035: Cannot properly initialize the Kerberos authenticator.

Cause: Could not initialize the Kerberos authenticator.

Action: Check the log files for errors and contact the domain administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02035: Cannot properly initialize the Kerberos authenticator.

Cause: Could not initialize the Kerberos authenticator.

Action: Check the log files for errors and contact the domain administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02035: Cannot properly initialize the Kerberos authenticator.

Cause: Could not initialize the Kerberos authenticator.

Action: Check the log files for errors and contact the domain administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02036: Browser does not support Kerberos authentication.

Cause: Could not find support for Kerberos authentication, or it was not configured correctly.

Action: Verify that the browser is set to allow Kerberos authentication.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02036: Browser does not support Kerberos authentication.

Cause: Could not find support for Kerberos authentication, or it was not configured correctly.

Action: Verify that the browser is set to allow Kerberos authentication.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02036: Browser does not support Kerberos authentication.

Cause: Could not find support for Kerberos authentication, or it was not configured correctly.

Action: Verify that the browser is set to allow Kerberos authentication.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02037: The SAML assertion issuer {0} certificate is missing from the keystore.

Cause: Could not find SAML assertion certificate in keystore.

Action: Store the SAML assertion issuer's certificate in the keystore, and configure the trustpoint alias in JpsSAMLLoginModuule.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02037: The SAML assertion issuer {0} certificate is missing from the keystore.

Cause: Could not find SAML assertion certificate in keystore.

Action: Store the SAML assertion issuer's certificate in the keystore, and configure the trustpoint alias in JpsSAMLLoginModuule.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02037: The SAML assertion issuer {0} certificate is missing from the keystore.

Cause: Could not find SAML assertion certificate in keystore.

Action: Store the SAML assertion issuer's certificate in the keystore, and configure the trustpoint alias in JpsSAMLLoginModuule.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02038: The SAML assertion {0} is missing a signature.

Cause: Could not find expected signature in assertion.

Action: Check that the assertion sent has a valid signature.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02038: The SAML assertion {0} is missing a signature.

Cause: Could not find expected signature in assertion.

Action: Check that the assertion sent has a valid signature.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02038: The SAML assertion {0} is missing a signature.

Cause: Could not find expected signature in assertion.

Action: Check that the assertion sent has a valid signature.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02039: Cannot assert certificate. Reason {0}.

Cause: Found invalid certificate, or could not find corresponding user in identity store.

Action: Make sure that the assertion is valid.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02039: Cannot assert certificate. Reason {0}.

Cause: Found invalid certificate, or could not find corresponding user in identity store.

Action: Make sure that the assertion is valid.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02039: Cannot assert certificate. Reason {0}.

Cause: Found invalid certificate, or could not find corresponding user in identity store.

Action: Make sure that the assertion is valid.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02040: Both user identity and token were provided for assertion. Either user identity or token should be provided, not both.

Cause: Both user identity and token were provided for assertion.

Action: Provide either user identity or a token for assertion, not both.
Level: 1

Type: ERROR

Impact: Other

JPS-02040: Both user identity and token were provided for assertion. Either user identity or token should be provided, not both.

Cause: Both user identity and token were provided for assertion.

Action: Provide either user identity or a token for assertion, not both.
Level: 1

Type: ERROR

Impact: Other

JPS-02040: Both user identity and token were provided for assertion. Either user identity or token should be provided, not both.

Cause: Both user identity and token were provided for assertion.

Action: Provide either user identity or a token for assertion, not both.
Level: 1

Type: ERROR

Impact: Other

JPS-02041: Asserter class was configured as {0}, but does not implement {1}.

Cause: Assertor class was configured as {0}, but does not implement {1}.

Action: Provide an Assertor that implements {1}.
Level: 1

Type: ERROR

Impact: Other

JPS-02041: Assertor class was configured as {0}, but does not implement {1}.

Cause: Assertor class was configured as {0}, but does not implement {1}.

Action: Provide an Assertor that implements {1}.
Level: 1

Type: ERROR

Impact: Other

JPS-02041: Assertor class was configured as {0}, but does not implement {1}.

Cause: Assertor class was configured as {0}, but does not implement {1}.

Action: Provide an Assertor that implements {1}.
Level: 1

Type: ERROR

Impact: Other

JPS-02042: Token assertion failed.

Cause: Token assertion failed.

Action: Check detailed logs for more information.
Level: 1

Type: ERROR

Impact: Other

JPS-02042: Token assertion failed.

Cause: Token assertion failed.

Action: Check detailed logs for more information.
Level: 1

Type: ERROR

Impact: Other

JPS-02042: Token assertion failed.

Cause: Token assertion failed.

Action: Check detailed logs for more information.
Level: 1

Type: ERROR

Impact: Other

JPS-02043: User name cannot be null or empty.

Cause: User name cannot be null or empty.

Action: Check that the user name is not null or empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02043: User name cannot be null or empty.

Cause: User name cannot be null or empty.

Action: Check that the user name is not null or empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02043: User name cannot be null or empty.

Cause: User name cannot be null or empty.

Action: Check that the user name is not null or empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02044: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Cause: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Action: Check that the attesting entity for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02044: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Cause: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Action: Check that the attesting entity for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02044: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Cause: Found invalid attesting entity in SAML assertion. Attesting entity: {0}.

Action: Check that the attesting entity for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02045: Audience URI for SAML assertion is invalid.

Cause: SAML assertion audience URI is invalid.

Action: Check that the audience URI for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02045: Audience URI for SAML assertion is invalid.

Cause: SAML assertion audience URI is invalid.

Action: Check that the audience URI for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02045: Audience URI for SAML assertion is invalid.

Cause: SAML assertion audience URI is invalid.

Action: Check that the audience URI for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02046: Cannot get the user name from SAML assertion name identifier: {0}.

Cause: Cannot get the user name from SAML assertion name identifier: {0}.

Action: Check that the name identifier for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02046: Cannot get the user name from SAML assertion name identifier: {0}.

Cause: Cannot get the user name from SAML assertion name identifier: {0}.

Action: Check that the name identifier for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02046: Cannot get the user name from SAML assertion name identifier: {0}.

Cause: Cannot get the user name from SAML assertion name identifier: {0}.

Action: Check that the name identifier for the SAML assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02047: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Cause: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Action: Provide an SAMLNameIdentifierMapper that implements oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.
Level: 1

Type: ERROR

Impact: Other

JPS-02047: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Cause: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Action: Provide an SAMLNameIdentifierMapper that implements oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.
Level: 1

Type: ERROR

Impact: Other

JPS-02047: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Cause: SAMLNameIdentifierMapper class was configured as {0}, but does not implement oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.

Action: Provide an SAMLNameIdentifierMapper that implements oracle.security.jps.internal.jaas.module.saml.SAMLNameIdentifierMapper.
Level: 1

Type: ERROR

Impact: Other

JPS-02048: Incorrect password was provided.

Cause: Incorrect password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02048: Incorrect password was provided.

Cause: Incorrect password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02048: Incorrect password was provided.

Cause: Incorrect password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02049: Null or empty password was provided.

Cause: Null or empty password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02049: Null or empty password was provided.

Cause: Null or empty password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02049: Null or empty password was provided.

Cause: Null or empty password was provided.

Action: Ensure that authentication uses correct password.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02050: Signature verification failed. Principal: {0}

Cause: Signature verification failed.

Action: This error is unlikely to occur. Contact technical support when necessary.
Level: 1

Type: ERROR

Impact: Security

JPS-02050: Signature verification failed. Principal: {0}

Cause: Signature verification failed.

Action: This error is unlikely to occur. Contact technical support when necessary.
Level: 1

Type: ERROR

Impact: Security

JPS-02050: Signature verification failed. Principal: {0}

Cause: Signature verification failed.

Action: This error is unlikely to occur. Contact technical support when necessary.
Level: 1

Type: ERROR

Impact: Security

JPS-02051: No auth module to validate request: auth context ID "{0}" of application context "{1}".

Cause: Server auth context did not have auth module to validate request.

Action: Ensure that the server auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02052: No auth module to secure response: auth context ID "{0}" of application context "{1}".

Cause: Server auth context did not have auth module to secure response.

Action: Ensure that the server auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02053: No auth module to validate response: auth context ID "{0}" of application context "{1}".

Cause: Client auth context did not have auth module to validate response.

Action: Ensure that the client auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02054: No auth module to secure request: auth context ID "{0}" of application context "{1}".

Cause: Client auth context did not have auth module to secure request.

Action: Ensure that the client auth module is properly configured and bound for use by applications.
Level: 1

Type: ERROR

Impact: Security

JPS-02055: Cannot instantiate auth module class "{0}" for application context "{1}", cause: {2}.

Cause: Could not load the auth module.

Action: Ensure that the module class name is correctly supplied and the class is in the class path.
Level: 1

Type: ERROR

Impact: Security

JPS-02056: The auth module must support message type: {0}.

Cause: Auth module did not support the required message type.

Action: Ensure that the class correctly implements the required auth module interfaces.
Level: 1

Type: ERROR

Impact: Security

JPS-02057: The message layer "{0}" is not supported.

Cause: The specified message layer was not supported.

Action: Provide a valid message layer.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02058: Null callback handler is not supported.

Cause: The specified callback handler was null.

Action: Supply a non-null callback handler.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02059: The default auth provider "{0}" for layer "{1}" is not configured.

Cause: The default auth provider was not configured.

Action: Ensure that the provider is configured in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-02060: The auth module "{0}" is missing.

Cause: The specified auth module did not exist.

Action: Configure the auth module in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02061: No auth module configured for provider "{0}".

Cause: No auth module configured for the specified provider.

Action: Configure an auth module for the provider in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02062: Cannot determine the JDK vendor. Defaults to Oracle JDK Kerberos Login Module.

Cause: Cannot determine the JDK vendor. Defaults to Oracle JDK Kerberos Login Module.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-02063: Failed to create Kerberos Login Module instance "{0}". Reason: {1}.

Cause: Failed to create Kerberos Login Module instance "{0}". Reason: {1}.

Action: Ensure that the Login Module class name is correctly supplied and the class is in the class path.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02500: The principal name is invalid.

Cause: Found null principal name.

Action: Check the principal name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02500: The principal name is invalid.

Cause: Found null principal name.

Action: Check the principal name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02500: The principal name is invalid.

Cause: Found null principal name.

Action: Check the principal name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02501: The principal type {0} is invalid.

Cause: Found invalid principal type.

Action: Check the principal type.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02501: The principal type {0} is invalid.

Cause: Found invalid principal type.

Action: Check the principal type.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02501: The principal type {0} is invalid.

Cause: Found invalid principal type.

Action: Check the principal type.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02502: The password {0} is invalid.

Cause: Found invalid password.

Action: Check the password passed to create user account.
Level: 1

Type: ERROR

Impact: Data

JPS-02502: The password {0} is invalid.

Cause: Found invalid password.

Action: Check the password passed to create user account.
Level: 1

Type: ERROR

Impact: Data

JPS-02502: The password {0} is invalid.

Cause: Found invalid password.

Action: Check the password passed to create user account.
Level: 1

Type: ERROR

Impact: Data

JPS-02503: The user name {0} is invalid.

Cause: Found invalid user name.

Action: Ensure that the user name used to create, fetch, or remove the account is valid.
Level: 1

Type: ERROR

Impact: Data

JPS-02503: The user name {0} is invalid.

Cause: Found invalid user name.

Action: Ensure that the user name used to create, fetch, or remove the account is valid.
Level: 1

Type: ERROR

Impact: Data

JPS-02503: The user name {0} is invalid.

Cause: Found invalid user name.

Action: Ensure that the user name used to create, fetch, or remove the account is valid.
Level: 1

Type: ERROR

Impact: Data

JPS-02504: The user range starting at {0} and ending at {1} is not a valid range.

Cause: The user range was invalid.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02504: The user range starting at {0} and ending at {1} is not a valid range.

Cause: The user range was invalid.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02504: The user range starting at {0} and ending at {1} is not a valid range.

Cause: The user range was invalid.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02505: The group {0} is invalid.

Cause: Group name was invalid.

Action: Check the group name that is being sent for creating/fetching/removing group.
Level: 1

Type: ERROR

Impact: Data

JPS-02505: The group {0} is invalid.

Cause: Group name was invalid.

Action: Check the group name that is being sent for creating/fetching/removing group.
Level: 1

Type: ERROR

Impact: Data

JPS-02505: The group {0} is invalid.

Cause: Group name was invalid.

Action: Check the group name that is being sent for creating/fetching/removing group.
Level: 1

Type: ERROR

Impact: Data

JPS-02506: The group range starting at {0} and ending at {1} is not valid range.

Cause: The JPSUserManager.getGroups() method was invoked with invalid start or end range.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02506: The group range starting at {0} and ending at {1} is not valid range.

Cause: The JPSUserManager.getGroups() method was invoked with invalid start or end range.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02506: The group range starting at {0} and ending at {1} is not valid range.

Cause: The JPSUserManager.getGroups() method was invoked with invalid start or end range.

Action: Check the start and end range. The start range cannot be less than 0, and the end range cannot be less than start range.
Level: 1

Type: ERROR

Impact: Data

JPS-02507: The anonymous user is not found.

Cause: The anonymous user was not found.

Action: Ensure that a valid anonymous user is configured.
Level: 1

Type: ERROR

Impact: Session

JPS-02507: The anonymous user is not found.

Cause: The anonymous user was not found.

Action: Ensure that a valid anonymous user is configured.
Level: 1

Type: ERROR

Impact: Session

JPS-02507: The anonymous user is not found.

Cause: The anonymous user was not found.

Action: Ensure that a valid anonymous user is configured.
Level: 1

Type: ERROR

Impact: Session

JPS-02508: The anonymous user name is invalid; property {0} is invalid or not defined.

Cause: The anonymous.user.name property was not configured in the anonymous service configuration.

Action: Configure the anonymous.user.name property to a valid user name in the identity store while configuring the Anonymous Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02508: The anonymous user name is invalid; property {0} is invalid or not defined.

Cause: The anonymous.user.name property was not configured in the anonymous service configuration.

Action: Configure the anonymous.user.name property to a valid user name in the identity store while configuring the Anonymous Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02508: The anonymous user name is invalid; property {0} is invalid or not defined.

Cause: The anonymous.user.name property was not configured in the anonymous service configuration.

Action: Configure the anonymous.user.name property to a valid user name in the identity store while configuring the Anonymous Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02509: The user {0} already exists in the store; choose a different user name.

Cause: The specified user name already existed in the store.

Action: Provide a different user name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02509: The user {0} already exists in the store; choose a different user name.

Cause: The specified user name already existed in the store.

Action: Provide a different user name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02509: The user {0} already exists in the store; choose a different user name.

Cause: The specified user name already existed in the store.

Action: Provide a different user name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02510: The group {0} already exists in the store; choose a different group name.

Cause: The specified group name already existed in the store.

Action: Provide a different group name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02510: The group {0} already exists in the store; choose a different group name.

Cause: The specified group name already existed in the store.

Action: Provide a different group name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02510: The group {0} already exists in the store; choose a different group name.

Cause: The specified group name already existed in the store.

Action: Provide a different group name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02511: The role for group {0} is invalid.

Cause: Found null role in group.

Action: Check the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02511: The role for group {0} is invalid.

Cause: Found null role in group.

Action: Check the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02511: The role for group {0} is invalid.

Cause: Found null role in group.

Action: Check the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02512: Cannot create a new user {0}.

Cause: Could not create user.

Action: Ensure that the user name is valid and distinct from any other existing user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02512: Cannot create a new user {0}.

Cause: Could not create user.

Action: Ensure that the user name is valid and distinct from any other existing user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02512: Cannot create a new user {0}.

Cause: Could not create user.

Action: Ensure that the user name is valid and distinct from any other existing user name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02513: Cannot drop user {0}.

Cause: Could not drop the user.

Action: Ensure this user already exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02513: Cannot drop user {0}.

Cause: Could not drop the user.

Action: Ensure this user already exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02513: Cannot drop user {0}.

Cause: Could not drop the user.

Action: Ensure this user already exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02514: Cannot retrieve user profile.

Cause: Could not get profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02514: Cannot retrieve user profile.

Cause: Could not get profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02514: Cannot retrieve user profile.

Cause: Could not get profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02515: Cannot update user profile.

Cause: Could not set profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02515: Cannot update user profile.

Cause: Could not set profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02515: Cannot update user profile.

Cause: Could not set profile for user.

Action: Ensure that the user exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02516: Cannot retrieve role profile.

Cause: Could not get role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02516: Cannot retrieve role profile.

Cause: Could not get role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02516: Cannot retrieve role profile.

Cause: Could not get role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02517: Cannot update role profile.

Cause: Could not set role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02517: Cannot update role profile.

Cause: Could not set role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02517: Cannot update role profile.

Cause: Could not set role profile.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02518: Cannot create role {0}.

Cause: Could not create role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Security

JPS-02518: Cannot create role {0}.

Cause: Could not create role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Security

JPS-02518: Cannot create role {0}.

Cause: Could not create role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Security

JPS-02519: Cannot drop role {0}.

Cause: Could not drop role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02519: Cannot drop role {0}.

Cause: Could not drop role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02519: Cannot drop role {0}.

Cause: Could not drop role.

Action: Ensure that the role exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02520: Cannot grant role to the principal.

Cause: Could not grant permission to role.

Action: Ensure that the permission is set for the role.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02520: Cannot grant role to the principal.

Cause: Could not grant permission to role.

Action: Ensure that the permission is set for the role.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02520: Cannot grant role to the principal.

Cause: Could not grant permission to role.

Action: Ensure that the permission is set for the role.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02521: Cannot revoke role from principal.

Cause: Could not revoke role.

Action: Check that the correct permission to revoke the role is set.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02521: Cannot revoke role from principal.

Cause: Could not revoke role.

Action: Check that the correct permission to revoke the role is set.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02521: Cannot revoke role from principal.

Cause: Could not revoke role.

Action: Check that the correct permission to revoke the role is set.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02522: Cannot add user to role owners.

Cause: Could not add owner to role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02522: Cannot add user to role owners.

Cause: Could not add owner to role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02522: Cannot add user to role owners.

Cause: Could not add owner to role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02523: Cannot remove user from role owners.

Cause: Could not remove owner from role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02523: Cannot remove user from role owners.

Cause: Could not remove owner from role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02523: Cannot remove user from role owners.

Cause: Could not remove owner from role.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02524: Cannot retrieve role owners.

Cause: Could not get role owners.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02524: Cannot retrieve role owners.

Cause: Could not get role owners.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02524: Cannot retrieve role owners.

Cause: Could not get role owners.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02525: Cannot retrieve role grantees.

Cause: Could not get role grantees.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02525: Cannot retrieve role grantees.

Cause: Could not get role grantees.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02525: Cannot retrieve role grantees.

Cause: Could not get role grantees.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02526: Cannot retrieve the roles granted to principal.

Cause: Could not get granted roles.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02526: Cannot retrieve the roles granted to principal.

Cause: Could not get granted roles.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02526: Cannot retrieve the roles granted to principal.

Cause: Could not get granted roles.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02527: Cannot close identity store.

Cause: Could not close identity store.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02527: Cannot close identity store.

Cause: Could not close identity store.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02527: Cannot close identity store.

Cause: Could not close identity store.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02528: Cannot obtain a handle for role manager MBean.

Cause: Could not get role manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02528: Cannot obtain a handle for role manager MBean.

Cause: Could not get role manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02528: Cannot obtain a handle for role manager MBean.

Cause: Could not get role manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02529: Cannot obtain a handle for user manager MBean.

Cause: Could not get user manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02529: Cannot obtain a handle for user manager MBean.

Cause: Could not get user manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02529: Cannot obtain a handle for user manager MBean.

Cause: Could not get user manager object name.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02530: Cannot get a list of searchable attributes.

Cause: Could not get searchable attributes.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02530: Cannot get a list of searchable attributes.

Cause: Could not get searchable attributes.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02530: Cannot get a list of searchable attributes.

Cause: Could not get searchable attributes.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02531: Cannot get list of user property names.

Cause: Could not get user property names.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02531: Cannot get list of user property names.

Cause: Could not get user property names.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02531: Cannot get list of user property names.

Cause: Could not get user property names.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02532: Cannot parse principals of role.

Cause: Could not parse role principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02532: Cannot parse principals of role.

Cause: Could not parse role principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02532: Cannot parse principals of role.

Cause: Could not parse role principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02533: Cannot parse principals of user.

Cause: Could not parse user principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02533: Cannot parse principals of user.

Cause: Could not parse user principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02533: Cannot parse principals of user.

Cause: Could not parse user principals.

Action: Check log files and correct the appropriate configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02534: Cannot find role {0}.

Cause: Could not completer search role operation.

Action: Correct the role name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02534: Cannot find role {0}.

Cause: Could not completer search role operation.

Action: Correct the role name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02534: Cannot find role {0}.

Cause: Could not completer search role operation.

Action: Correct the role name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02535: Cannot complete search for roles.

Cause: Could not complete search for multiple roles.

Action: Correct role names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02535: Cannot complete search for roles.

Cause: Could not complete search for multiple roles.

Action: Correct role names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02535: Cannot complete search for roles.

Cause: Could not complete search for multiple roles.

Action: Correct role names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02536: Cannot complete search for user {0}.

Cause: Could not completer user search.

Action: Correct user name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02536: Cannot complete search for user {0}.

Cause: Could not completer user search.

Action: Correct user name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02536: Cannot complete search for user {0}.

Cause: Could not completer user search.

Action: Correct user name and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02537: Cannot complete search for users.

Cause: Could not complete search for multiple users.

Action: Correct user names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02537: Cannot complete search for users.

Cause: Could not complete search for multiple users.

Action: Correct user names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02537: Cannot complete search for users.

Cause: Could not complete search for multiple users.

Action: Correct user names and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02538: Cannot complete search operation.

Cause: Failed to complete search.

Action: Correct the search query.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02538: Cannot complete search operation.

Cause: Failed to complete search.

Action: Correct the search query.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02538: Cannot complete search operation.

Cause: Failed to complete search.

Action: Correct the search query.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02539: Cannot change password of user {0}.

Cause: Could not change password.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02539: Cannot change password of user {0}.

Cause: Could not change password.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02539: Cannot change password of user {0}.

Cause: Could not change password.

Action: Contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02540: User {0} not found in the identity store.

Cause: User {0} not found in the identity store.

Action: Ensure user is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02540: User {0} not found in the identity store.

Cause: User {0} not found in the identity store.

Action: Ensure user is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02540: User {0} not found in the identity store.

Cause: User {0} not found in the identity store.

Action: Ensure user is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02541: Identity store has an invalid configured subscriber name.

Cause: Found invalid subscriber name.

Action: Correct the configuration of property subscriber.name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02541: Identity store has an invalid configured subscriber name.

Cause: Found invalid subscriber name.

Action: Correct the configuration of property subscriber.name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02541: Identity store has an invalid configured subscriber name.

Cause: Found invalid subscriber name.

Action: Correct the configuration of property subscriber.name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02542: unknown identity store service type {0}.

Cause: Found unknown identity store service type {0}.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02542: unknown identity store service type {0}.

Cause: Found unknown identity store service type {0}.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02542: unknown identity store service type {0}.

Cause: Found unknown identity store service type {0}.

Action: Correct the identity store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02543: Search type {0} is invalid.

Cause: Found invalid search type {0}.

Action: Correct the type passed for the search.
Level: 1

Type: ERROR

Impact: Other

JPS-02543: Search type {0} is invalid.

Cause: Found invalid search type {0}.

Action: Correct the type passed for the search.
Level: 1

Type: ERROR

Impact: Other

JPS-02543: Search type {0} is invalid.

Cause: Found invalid search type {0}.

Action: Correct the type passed for the search.
Level: 1

Type: ERROR

Impact: Other

JPS-02544: Operation type {0} is invalid.

Cause: Found invalid operation type {0}.

Action: Correct the type passed for the operation.
Level: 1

Type: ERROR

Impact: Other

JPS-02544: Operation type {0} is invalid.

Cause: Found invalid operation type {0}.

Action: Correct the type passed for the operation.
Level: 1

Type: ERROR

Impact: Other

JPS-02544: Operation type {0} is invalid.

Cause: Found invalid operation type {0}.

Action: Correct the type passed for the operation.
Level: 1

Type: ERROR

Impact: Other

JPS-02545: Search filter type {0} is invalid.

Cause: Found invalid search filter type {0}.

Action: Correct the type passed for the search filter.
Level: 1

Type: ERROR

Impact: Other

JPS-02545: Search filter type {0} is invalid.

Cause: Found invalid search filter type {0}.

Action: Correct the type passed for the search filter.
Level: 1

Type: ERROR

Impact: Other

JPS-02545: Search filter type {0} is invalid.

Cause: Found invalid search filter type {0}.

Action: Correct the type passed for the search filter.
Level: 1

Type: ERROR

Impact: Other

JPS-02546: Scope type is invalid {0}.

Cause: Found invalid scope type {0}.

Action: Correct the type passed for the scope.
Level: 1

Type: ERROR

Impact: Other

JPS-02546: Scope type is invalid {0}.

Cause: Found invalid scope type {0}.

Action: Correct the type passed for the scope.
Level: 1

Type: ERROR

Impact: Other

JPS-02546: Scope type is invalid {0}.

Cause: Found invalid scope type {0}.

Action: Correct the type passed for the scope.
Level: 1

Type: ERROR

Impact: Other

JPS-02547: Cannot create realm {0}.

Cause: Could not created realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02547: Cannot create realm {0}.

Cause: Could not created realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02547: Cannot create realm {0}.

Cause: Could not created realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02548: Cannot delete realm {0}.

Cause: Could not delete realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02548: Cannot delete realm {0}.

Cause: Could not delete realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02548: Cannot delete realm {0}.

Cause: Could not delete realm.

Action: Check log files for error details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02549: A realm with the specified name already exists.

Cause: A realm with the specified name already exists.

Action: Choose a different realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02549: A realm with the specified name already exists.

Cause: A realm with the specified name already exists.

Action: Choose a different realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02549: A realm with the specified name already exists.

Cause: A realm with the specified name already exists.

Action: Choose a different realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02550: The realm {0} does not exist.

Cause: Could not find realm with the name {0}.

Action: Correct the supplied realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02550: The realm {0} does not exist.

Cause: Could not find realm with the name {0}.

Action: Correct the supplied realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02550: The realm {0} does not exist.

Cause: Could not find realm with the name {0}.

Action: Correct the supplied realm name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02551: Cannot perform an unsupported operation on a serialized object.

Cause: Could not perform operation on serialized object.

Action: Check log files for error details.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02551: Cannot perform an unsupported operation on a serialized object.

Cause: Could not perform operation on serialized object.

Action: Check log files for error details.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02551: Cannot perform an unsupported operation on a serialized object.

Cause: Could not perform operation on serialized object.

Action: Check log files for error details.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02552: Cannot add a duplicate owner.

Cause: Attempted to add already present owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02552: Cannot add a duplicate owner.

Cause: Attempted to add already present owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02552: Cannot add a duplicate owner.

Cause: Attempted to add already present owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02553: Cannot remove an owner that is not present.

Cause: Attempted to remove a non existing owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02553: Cannot remove an owner that is not present.

Cause: Attempted to remove a non existing owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02553: Cannot remove an owner that is not present.

Cause: Attempted to remove a non existing owner.

Action: Correct the owner's name.
Level: 1

Type: TRACE

Impact: Data

JPS-02554: Cannot add a duplicate member.

Cause: Attempted to add already present member.

Action: Correct the member's name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02554: Cannot add a duplicate member.

Cause: Attempted to add already present member.

Action: Correct the member's name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02554: Cannot add a duplicate member.

Cause: Attempted to add already present member.

Action: Correct the member's name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02555: Cannot complete identity store operation. The error is {0}.

Cause: Could not perform identity store operation.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02555: Cannot complete identity store operation. The error is {0}.

Cause: Could not perform identity store operation.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02555: Cannot complete identity store operation. The error is {0}.

Cause: Could not perform identity store operation.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02556: Run into error {0} while using identity store.

Cause: Run into an internal identity store error.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02556: Run into error {0} while using identity store.

Cause: Run into an internal identity store error.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02556: Run into error {0} while using identity store.

Cause: Run into an internal identity store error.

Action: Check error log files for details.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02557: The group {0} is invalid.

Cause: Found null or invalid group.

Action: Correct the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02557: The group {0} is invalid.

Cause: Found null or invalid group.

Action: Correct the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02557: The group {0} is invalid.

Cause: Found null or invalid group.

Action: Correct the group's name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02558: Operation isOwnedBy failed.

Cause: Could not perform operation isOwnedBy.

Action: Correct the owner's name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02558: Operation isOwnedBy failed.

Cause: Could not perform operation isOwnedBy.

Action: Correct the owner's name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02558: Operation isOwnedBy failed.

Cause: Could not perform operation isOwnedBy.

Action: Correct the owner's name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02559: Operation isManagedBy failed.

Cause: Could not perform operation isManagedBy.

Action: Correct the name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02559: Operation isManagedBy failed.

Cause: Could not perform operation isManagedBy.

Action: Correct the name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02559: Operation isManagedBy failed.

Cause: Could not perform operation isManagedBy.

Action: Correct the name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02560: Cannot update role.

Cause: Could not update role.

Action: Verify that the role name is correct and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02560: Cannot update role.

Cause: Could not update role.

Action: Verify that the role name is correct and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02560: Cannot update role.

Cause: Could not update role.

Action: Verify that the role name is correct and, if necessary, contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02561: The realm entry {0} is missing in the identity store XML file.

Cause: Could not find realm entry {0} in XML-based identity store.

Action: Ensure that the realm name is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02561: The realm entry {0} is missing in the identity store XML file.

Cause: Could not find realm entry {0} in XML-based identity store.

Action: Ensure that the realm name is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02561: The realm entry {0} is missing in the identity store XML file.

Cause: Could not find realm entry {0} in XML-based identity store.

Action: Ensure that the realm name is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02562: Identity store entry is missing in the identity store XML file.

Cause: Could not find identity store entry in XML-based identity store.

Action: Ensure that entry is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02562: Identity store entry is missing in the identity store XML file.

Cause: Could not find identity store entry in XML-based identity store.

Action: Ensure that entry is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02562: Identity store entry is missing in the identity store XML file.

Cause: Could not find identity store entry in XML-based identity store.

Action: Ensure that entry is present in the XML-based identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02563: Length of the name attribute should be more than {0}.

Cause: Found attribute name with less than {0} characters.

Action: Ensure that the length of the attribute name is at least the minimum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02563: Length of the name attribute should be more than {0}.

Cause: Found attribute name with less than {0} characters.

Action: Ensure that the length of the attribute name is at least the minimum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02563: Length of the name attribute should be more than {0}.

Cause: Found attribute name with less than {0} characters.

Action: Ensure that the length of the attribute name is at least the minimum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02564: Length of the name attribute should be less than {0}.

Cause: Found attribute name with more than {0} characters.

Action: Ensure that the length of the attribute name is at most the maximum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02564: Length of the name attribute should be less than {0}.

Cause: Found attribute name with more than {0} characters.

Action: Ensure that the length of the attribute name is at most the maximum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02564: Length of the name attribute should be less than {0}.

Cause: Found attribute name with more than {0} characters.

Action: Ensure that the length of the attribute name is at most the maximum length.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02565: Name attribute contains invalid characters.

Cause: Found invalid characters in attribute name.

Action: Ensure that attribute names have characters in the following sets only: [a-z], [A-Z], [0-9], ['.', '-', '_'].
Level: 1

Type: ERROR

Impact: Configuration

JPS-02565: Name attribute contains invalid characters.

Cause: Found invalid characters in attribute name.

Action: Ensure that attribute names have characters in the following sets only: [a-z], [A-Z], [0-9], ['.', '-', '_'].
Level: 1

Type: ERROR

Impact: Configuration

JPS-02565: Name attribute contains invalid characters.

Cause: Found invalid characters in attribute name.

Action: Ensure that attribute names have characters in the following sets only: [a-z], [A-Z], [0-9], ['.', '-', '_'].
Level: 1

Type: ERROR

Impact: Configuration

JPS-02566: The identity store config property {0} with value {1} is invalid.

Cause: Found invalid identity store configuration property.

Action: Correct the configuration of the identity store property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02566: The identity store config property {0} with value {1} is invalid.

Cause: Found invalid identity store configuration property.

Action: Correct the configuration of the identity store property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02566: The identity store config property {0} with value {1} is invalid.

Cause: Found invalid identity store configuration property.

Action: Correct the configuration of the identity store property.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02567: The credential with map {0} and key {1} does not exist.

Cause: Could not find credential with map and key names provided.

Action: Ensure that a credential with given map and key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02567: The credential with map {0} and key {1} does not exist.

Cause: Could not find credential with map and key names provided.

Action: Ensure that a credential with given map and key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02567: The credential with map {0} and key {1} does not exist.

Cause: Could not find credential with map and key names provided.

Action: Ensure that a credential with given map and key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02568: The password credential with map {0} and key {1} is invalid.

Cause: Found invalid user name or password.

Action: Ensure that the user name and password in the credential store are correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02568: The password credential with map {0} and key {1} is invalid.

Cause: Found invalid user name or password.

Action: Ensure that the user name and password in the credential store are correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02568: The password credential with map {0} and key {1} is invalid.

Cause: Found invalid user name or password.

Action: Ensure that the user name and password in the credential store are correct.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02569: Cannot find the XML file {0}.

Cause: Could not find XML file for XML-based identity store {0}.

Action: Check the path of the XML file specified for the identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02569: Cannot find the XML file {0}.

Cause: Could not find XML file for XML-based identity store {0}.

Action: Check the path of the XML file specified for the identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02569: Cannot find the XML file {0}.

Cause: Could not find XML file for XML-based identity store {0}.

Action: Check the path of the XML file specified for the identity store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02570: XML file is unspecified.

Cause: Could not determine XML file.

Action: Specify the XML file for the XML-based repository.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02570: XML file is unspecified.

Cause: Could not determine XML file.

Action: Specify the XML file for the XML-based repository.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02570: XML file is unspecified.

Cause: Could not determine XML file.

Action: Specify the XML file for the XML-based repository.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02571: The algorithm {0} to encode passwords is not supported.

Cause: Found invalid password encoding algorithm.

Action: Specify a valid algorithm for password encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02571: The algorithm {0} to encode passwords is not supported.

Cause: Found invalid password encoding algorithm.

Action: Specify a valid algorithm for password encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02571: The algorithm {0} to encode passwords is not supported.

Cause: Found invalid password encoding algorithm.

Action: Specify a valid algorithm for password encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02572: Caller does not have IdentityAssertion permission to execute this operation. Reason {0}.

Cause: Caller did not have IdentityAssertion permission.

Action: Make sure the caller has IdentityAssertion permission to execute this operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02572: Caller does not have IdentityAssertion permission to execute this operation. Reason {0}.

Cause: Caller did not have IdentityAssertion permission.

Action: Make sure the caller has IdentityAssertion permission to execute this operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02572: Caller does not have IdentityAssertion permission to execute this operation. Reason {0}.

Cause: Caller did not have IdentityAssertion permission.

Action: Make sure the caller has IdentityAssertion permission to execute this operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02573: Cannot grant a role to itself.

Cause: Attempted to grant a role to itself.

Action: Verify that no role is being granted to itself.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02573: Cannot grant a role to itself.

Cause: Attempted to grant a role to itself.

Action: Verify that no role is being granted to itself.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02573: Cannot grant a role to itself.

Cause: Attempted to grant a role to itself.

Action: Verify that no role is being granted to itself.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02574: Cannot delete default realm.

Cause: Could not delete default realm.

Action: The default realm cannot be deleted: assign another realm as the default realm before deleting this one.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02574: Cannot delete default realm.

Cause: Could not delete default realm.

Action: The default realm cannot be deleted: assign another realm as the default realm before deleting this one.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02574: Cannot delete default realm.

Cause: Could not delete default realm.

Action: The default realm cannot be deleted: assign another realm as the default realm before deleting this one.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-02575: A user with the specified name does not exist.

Cause: Could not find user with the specified name.

Action: Check the user name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02575: A user with the specified name does not exist.

Cause: Could not find user with the specified name.

Action: Check the user name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02575: A user with the specified name does not exist.

Cause: Could not find user with the specified name.

Action: Check the user name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02576: A role with the specified name already exists.

Cause: Role with the specified name already existed.

Action: Use a different role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02576: A role with the specified name already exists.

Cause: Role with the specified name already existed.

Action: Use a different role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02576: A role with the specified name already exists.

Cause: Role with the specified name already existed.

Action: Use a different role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02577: A role with the specified name does not exist.

Cause: Could not find role with the specified name.

Action: Check the role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02577: A role with the specified name does not exist.

Cause: Could not find role with the specified name.

Action: Check the role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02577: A role with the specified name does not exist.

Cause: Could not find role with the specified name.

Action: Check the role name.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02578: The principal type {0} is invalid for the identity store type {1}.

Cause: Found unsupported principal type {0} for identity store type {1}.

Action: Verify that principals have supported types.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02578: The principal type {0} is invalid for the identity store type {1}.

Cause: Found unsupported principal type {0} for identity store type {1}.

Action: Verify that principals have supported types.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02578: The principal type {0} is invalid for the identity store type {1}.

Cause: Found unsupported principal type {0} for identity store type {1}.

Action: Verify that principals have supported types.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02579: Identity store type for application {0} is null or empty.

Cause: Found null identity store type configured in identity store.

Action: Pass one of the following identity store types: XML, OID, ACTIVE_DIRECTORY, IPLANET, EDIRECTORY, OPEN_LDAP, COREID, OVD, OUD, or CUSTOM.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02579: Identity store type for application {0} is null or empty.

Cause: Found null identity store type configured in identity store.

Action: Pass one of the following identity store types: XML, OID, ACTIVE_DIRECTORY, IPLANET, EDIRECTORY, OPEN_LDAP, COREID, OVD, or CUSTOM.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02579: Identity store type for application {0} is null or empty.

Cause: Found null identity store type configured in identity store.

Action: Pass one of the following identity store types: XML, OID, ACTIVE_DIRECTORY, IPLANET, EDIRECTORY, OPEN_LDAP, COREID, OVD, or CUSTOM.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02580: Cannot grant role {0} to {1} because it would lead to a cyclic dependency.

Cause: Could not grant role {0} to {1}, because it would lead to a cyclic dependency.

Action: Revoke the grant which would create the cyclic dependency, and try again.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02580: Cannot grant role {0} to {1} because it would lead to a cyclic dependency.

Cause: Could not grant role {0} to {1}, because it would lead to a cyclic dependency.

Action: Revoke the grant which would create the cyclic dependency, and try again.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02580: Cannot grant role {0} to {1} because it would lead to a cyclic dependency.

Cause: Could not grant role {0} to {1}, because it would lead to a cyclic dependency.

Action: Revoke the grant which would create the cyclic dependency, and try again.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-02582: LDAP user or group search base is invalid.

Cause: Found invalid LDAP user or group search base.

Action: Check that the user and group search base properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-02582: LDAP user or group search base is invalid.

Cause: Found invalid LDAP user or group search base.

Action: Check that the user and group search base properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-02582: LDAP user or group search base is invalid.

Cause: Found invalid LDAP user or group search base.

Action: Check that the user and group search base properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

JPS-02583: JPS principal "{0}" with identity store type "{1}" cannot be created.

Cause: JPS principal "{0}" with identity store type "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02583: JPS principal "{0}" with identity store type "{1}" cannot be created.

Cause: JPS principal "{0}" with identity store type "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02583: JPS principal "{0}" with identity store type "{1}" cannot be created.

Cause: JPS principal "{0}" with identity store type "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02584: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the user value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02584: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the user value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02584: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS user name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the user value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02585: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the enterprise role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02585: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the enterprise role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02585: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Cause: JPS enterprise role name "{0}", principal type "{1}" with identity store type "{2}" cannot be created.

Action: Ensure the enterprise role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02586: JPS application role name "{0}", principal type "{1}" cannot be created.

Cause: JPS application role name "{0}", principal type "{1}" cannot be created.

Action: Ensure the application role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02586: JPS application role name "{0}", principal type "{1}" cannot be created.

Cause: JPS application role name "{0}", principal type "{1}" cannot be created.

Action: Ensure the application role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02586: JPS application role name "{0}", principal type "{1}" cannot be created.

Cause: JPS application role name "{0}", principal type "{1}" cannot be created.

Action: Ensure the application role value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02587: Principal class "{0}", name "{1}" cannot be created.

Cause: Principal class "{0}", name "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02587: Principal class "{0}", name "{1}" cannot be created.

Cause: Principal class "{0}", name "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02587: Principal class "{0}", name "{1}" cannot be created.

Cause: Principal class "{0}", name "{1}" cannot be created.

Action: Ensure the principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02588: Enterprise user principal "{0}" cannot be created. Reason: {1}.

Cause: Enterprise user principal "{0}" cannot be created.

Action: Ensure the user principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02588: Enterprise user principal "{0}" cannot be created.

Cause: Enterprise user principal "{0}" cannot be created.

Action: Ensure the user principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02588: Enterprise user principal "{0}" cannot be created.

Cause: Enterprise user principal "{0}" cannot be created.

Action: Ensure the user principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02589: Enterprise role principal "{0}" cannot be created. Reason: {1}.

Cause: Enterprise role principal "{0}" cannot be created.

Action: Ensure the role principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02589: Enterprise role principal "{0}" cannot be created.

Cause: Enterprise role principal "{0}" cannot be created.

Action: Ensure the role principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02589: Enterprise role principal "{0}" cannot be created.

Cause: Enterprise role principal "{0}" cannot be created.

Action: Ensure the role principal value is valid.
Level: 1

Type: ERROR

Impact: Security

JPS-02590: Token type {0} cannot be supported. Supported types are: {1}.

Cause: Token type {0} cannot be supported. Supported types are: {1}.

Action: Use the Supported types.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02590: Token type {0} cannot be supported. Supported types are: {1}.

Cause: Token type {0} cannot be supported. Supported types are: {1}.

Action: Use the Supported types.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02590: Token type {0} cannot be supported. Supported types are: {1}.

Cause: Token type {0} cannot be supported. Supported types are: {1}.

Action: Use the Supported types.
Level: 1

Type: ERROR

Impact: Configuration

JPS-02591: Guid {0} is assigned to principal {1}.

Cause: Guid {0} is assigned to principal {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-02591: Guid {0} is assigned to principal {1}.

Cause: Guid {0} is assigned to principal {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-02591: Guid {0} is assigned to principal {1}.

Cause: Guid {0} is assigned to principal {1}.

Action: Check log for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-02592: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Cause: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Action: Check libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02592: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Cause: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Action: Check libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02592: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Cause: Failed to push ldap config data to libOvd for service instance "{0}" in JPS context "{1}", cause: {2}

Action: Check libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02593: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Cause: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Action: Check IGF API or libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02593: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Cause: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Action: Check IGF API or libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02593: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Cause: Failed to get IGF UserManager or RoleManager instance from IGF API, cause: {0}

Action: Check IGF API or libOvd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-02594: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Cause: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Action: Check jps-config.xml to make sure the IGF service has either the IDStore instance defined, or use the WlsLdapIdStoreConfigProvider to get LDAP config from WLS Authentication providers.
Level: 1

Type: ERROR

Impact: Security

JPS-02594: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Cause: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Action: Check jps-config.xml to make sure the IGF service has either the IDStore instance defined, or use the WlsLdapIdStoreConfigProvider to get LDAP config from WLS Authentication providers.
Level: 1

Type: ERROR

Impact: Security

JPS-02594: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Cause: The service instance "{0}" in JPS context "{1}" has no LDAP instance configured

Action: Check jps-config.xml to make sure the IGF service has either the IDStore instance defined, or use the WlsLdapIdStoreConfigProvider to get LDAP config from WLS Authentication providers.
Level: 1

Type: ERROR

Impact: Security

JPS-02595: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Cause: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Action: Check jps-config.xml to make sure the specified ldap is defined as a JPS service instance.
Level: 1

Type: ERROR

Impact: Security

JPS-02595: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Cause: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Action: Check jps-config.xml to make sure the specified ldap is defined as a JPS service instance.
Level: 1

Type: ERROR

Impact: Security

JPS-02595: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Cause: The IGFService specified ldap "{0}" is not defined in the JPS service instances

Action: Check jps-config.xml to make sure the specified ldap is defined as a JPS service instance.
Level: 1

Type: ERROR

Impact: Security

JPS-02596: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Cause: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Action: Check jps-config.xml to make sure the provider type class for ldap instance is "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider".
Level: 1

Type: ERROR

Impact: Security

JPS-02596: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Cause: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Action: Check jps-config.xml to make sure the provider type class for ldap instance is "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider".
Level: 1

Type: ERROR

Impact: Security

JPS-02596: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Cause: The provider class type for the specified ldap instance "{0}" is configured as "{1}", which not the expected type of "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider"

Action: Check jps-config.xml to make sure the provider type class for ldap instance is "oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider".
Level: 1

Type: ERROR

Impact: Security

JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.

Cause: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which is a custom type and not supported by libOvd

Action: The "idstore.type" property must be specified in jps-config.xml file as specific type such as OID, OVD etc. Alternatively, select a specific WLS LDAP Authentication provider that matches your LDAP server.
Level: 1

Type: ERROR

Impact: Security

JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.

Cause: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which is a custom type and not supported by libOvd

Action: The "idstore.type" property must be specified in jps-config.xml file as specific type such as OID, OVD etc. Alternatively, select a specific WLS LDAP Authentication provider that matches your LDAP server.
Level: 1

Type: ERROR

Impact: Security

JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.

Cause: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which is a custom type and not supported by libOvd

Action: The "idstore.type" property must be specified in jps-config.xml file as specific type such as OID, OVD etc. Alternatively, select a specific WLS LDAP Authentication provider that matches your LDAP server.
Level: 1

Type: ERROR

Impact: Security

JPS-02598: Pushed ldap name and types info to libOvd. Ldaps : {0}.

Cause: libOvd is enabled so Ldap configuration info is passed to libOvd

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-02598: Pushed ldap name and types info to libOvd. Ldaps : {0}.

Cause: libOvd is enabled so Ldap configuration info is passed to libOvd

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-02598: Pushed ldap name and types info to libOvd. Ldaps : {0}.

Cause: libOvd is enabled so Ldap configuration info is passed to libOvd

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-02599: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Cause: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Action: Use supported Identity Store provider for the IdentiyStoreService
Level: 1

Type: ERROR

Impact: Security

JPS-02599: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Cause: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Action: Use supported Identity Store provider for the IdentiyStoreService
Level: 1

Type: ERROR

Impact: Security

JPS-02599: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Cause: The configured Identity Store provider "{0}" is not supported by IDM IdentityDirectory

Action: Use supported Identity Store provider for the IdentiyStoreService
Level: 1

Type: ERROR

Impact: Security

JPS-02600: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Cause: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Action: Supply the system flag of "-Dcommon.components.home" and point it to the oracle_common folder
Level: 1

Type: ERROR

Impact: Security

JPS-02600: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Cause: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Action: Supply the system flag of "-Dcommon.components.home" and point it to the oracle_common folder
Level: 1

Type: ERROR

Impact: Security

JPS-02600: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Cause: libOvd required system parameter of "common.components.home" is not supplied in the JVM command line

Action: Supply the system flag of "-Dcommon.components.home" and point it to the oracle_common folder
Level: 1

Type: ERROR

Impact: Security

JPS-02601: Failed to get Ovd virtualization service for service instance "{0}" in JPS context "{1}", cause: {2}

Cause: Failed to get Ovd virtualization service for service instance "{0}" in JPS context "{1}", cause: {2}

Action: Check Ovd log for more details.
Level: 1

Type: ERROR

Impact: Security

JPS-03000: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the application policy context "{3}". Cause {4}

Cause: Could not load a permission class.

Action: Ensure that the class name is correct and available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03000: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the application policy context "{3}". Cause {4}

Cause: Could not load a permission class.

Action: Ensure that the class name is correct and available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03000: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the application policy context "{3}". Cause {4}

Cause: Could not load a permission class.

Action: Ensure that the class name is correct and available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03001: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the system policy context. Cause {3}

Cause: Could not load a class.

Action: Ensure that the class name is correct and is available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03001: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the system policy context. Cause {3}

Cause: Could not load a class.

Action: Ensure that the class name is correct and is available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03001: Cannot instantiate permission class "{0}", target "{1}", or actions "{2}" as defined in the system policy context. Cause {3}

Cause: Could not load a class.

Action: Ensure that the class name is correct and is available in the current class loader.
Level: 1

Type: WARNING

Impact: Security

JPS-03004: Cannot log check authorization event to the audit service.

Cause: Could not log check authorization events to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-03004: Cannot log check authorization event to the audit service.

Cause: Could not log check authorization events to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-03004: Cannot log check authorization event to the audit service.

Cause: Could not log check authorization events to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-03005: LDAP policy store contains invalid configuration parameters.

Cause: Found invalid parameters in LDAP policy store configuration.

Action: Check the configuration of the LDAP policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-03005: LDAP policy store contains invalid configuration parameters.

Cause: Found invalid parameters in LDAP policy store configuration.

Action: Check the configuration of the LDAP policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-03005: LDAP policy store contains invalid configuration parameters.

Cause: Found invalid parameters in LDAP policy store configuration.

Action: Check the configuration of the LDAP policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-03006: The name "{0}" of application role "{1}" is missing or invalid.

Cause: Found missing or invalid name in application role.

Action: The internal identifier generated by the policy store seems malformed, due to an internal policy store error; contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

JPS-03006: The name "{0}" of application role "{1}" is missing or invalid.

Cause: Found missing or invalid name in application role.

Action: The internal identifier generated by the policy store seems malformed, due to an internal policy store error; contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

JPS-03006: The name "{0}" of application role "{1}" is missing or invalid.

Cause: Found missing or invalid name in application role.

Action: The internal identifier generated by the policy store seems malformed, due to an internal policy store error; contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

JPS-03007: Authorization check permission succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03007: Authorization check permission succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03007: Authorization check permission succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03008: Authorization check permission failed.

Cause: Current Subject or source code did not have required permissions

Action: Provide the required permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-03008: Authorization check permission failed.

Cause: Current Subject or source code did not have required permissions

Action: Provide the required permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-03008: Authorization check permission failed.

Cause: Current Subject or source code did not have required permissions

Action: Provide the required permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-03009: Executing privileged action in {0} mode as subject {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03009: Executing privileged action in {0} mode as subject {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03009: Executing privileged action in {0} mode as subject {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03010: Policy store cleanup thread started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03010: Policy store cleanup thread started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03010: Policy store cleanup thread started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03011: Policy store cleanup thread stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03011: Policy store cleanup thread stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03011: Policy store cleanup thread stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03012: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Cause: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-03012: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Cause: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-03012: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Cause: Error occurred when computing application roles in application context {0} for subject {1}. Exception: {2}

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-03013: Unsupported API method call.

Cause: Unsupported API method call.

Action: Check the policy provider.
Level: 1

Type: WARNING

Impact: Security

JPS-03013: Unsupported API method call.

Cause: Unsupported API method call.

Action: Check the policy provider.
Level: 1

Type: WARNING

Impact: Security

JPS-03013: Unsupported API method call.

Cause: Unsupported API method call.

Action: Check the policy provider.
Level: 1

Type: WARNING

Impact: Security

JPS-03014: Failed to distribute policy by timer.

Cause: Failed to distribute policy by timer.

Action: Check the log for more details or contact the administator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03014: Failed to distribute policy by timer.

Cause: Failed to distribute policy by timer.

Action: Check the log for more details or contact the administator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03014: Failed to distribute policy by timer.

Cause: Failed to distribute policy by timer.

Action: Check the log for more details or contact the administator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03015: Resource-Actions "{0}" will be skipped in bulk authorization evaluation for Application: "{1}".

Cause: Application name not set in the resource-actions.

Action: Set the Application name in the resource-actions
Level: 1

Type: WARNING

Impact: Configuration

JPS-03015: Resource-Actions '{0}' will be skipped in bulk authorization evaluation for Application: '{1}'.

Cause: Application name not set in the resource-actions.

Action: Set the Application name in the resource-actions
Level: 1

Type: WARNING

Impact: Configuration

JPS-03015: Resource-Actions '{0}' will be skipped in bulk authorization evaluation for Application: '{1}'.

Cause: Application name not set in the resource-actions.

Action: Set the Application name in the resource-actions
Level: 1

Type: WARNING

Impact: Configuration

JPS-03016: Resource-Actions "{0}" will be skipped in bulk authorization. Reason: "{1}"

Cause: Failed to convert the Resource-Actions into a Permission instance.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03016: Resource-Actions '{0}' will be skipped in bulk authorization. Reason: '{1}'

Cause: Failed to convert the Resource-Actions into a Permission instance.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03016: Resource-Actions '{0}' will be skipped in bulk authorization. Reason: '{1}'

Cause: Failed to convert the Resource-Actions into a Permission instance.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03017: Failed to compute Application roles for Subject "{0}". Reason "{1}"

Cause: Unable to get the ApplicationRoles granted to a principal.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03017: Failed to compute Application roles for Subject '{0}'. Reason '{1}'

Cause: Unable to get the ApplicationRoles granted to a principal.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03017: Failed to compute Application roles for Subject '{0}'. Reason '{1}'

Cause: Unable to get the ApplicationRoles granted to a principal.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03018: The authorization result is ignoring policies from application {0} as the application is not available

Cause: The application is not available at runtime, or the application is not defined in the policystore.

Action: Check if the application is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03018: The authorization result is ignoring policies from application {0} as the application is not available

Cause: The application is not available at runtime, or the application is not defined in the policystore.

Action: Check if the application is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03018: The authorization result is ignoring policies from application {0} as the application is not available

Cause: The application is not available at runtime, or the application is not defined in the policystore.

Action: Check if the application is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03019: Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03019: Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03019: Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03020: Policy evaluation in the system policy failed. Reason: {0}

Cause: Error occurred while evaluating system policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03020: Policy evaluation in the system policy failed. Reason: {0}

Cause: Error occurred while evaluating system policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03020: Policy evaluation in the system policy failed. Reason: {0}

Cause: Error occurred while evaluating system policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03021: Admin Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating administrative policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03021: Admin Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating administrative policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03021: Admin Policy evaluation in the application {0} failed. Reason: {1}

Cause: Error occurred while evaluating administrative policies.

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03022: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Cause: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03022: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Cause: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03022: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Cause: Failed to initialize PolicyStore for Discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03023: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Cause: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Action: Make sure directory for writing discovered policy exist, is directory and can write.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03023: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Cause: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Action: Make sure directory for writing discovered policy exist, is directory and can write.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03023: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Cause: Discovered policy directory either not exist or can not write, isExist={0},isDirectory={1},canWrite={2}

Action: Make sure directory for writing discovered policy exist, is directory and can write.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03024: Failed to write policy information during discovery. Reason: {0}

Cause: Failed to dump policy objects in discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03024: Failed to write policy information during discovery. Reason: {0}

Cause: Failed to dump policy objects in discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03024: Failed to write policy information during discovery. Reason: {0}

Cause: Failed to dump policy objects in discovery mode. Reason: {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03025: Input permission is null when getPermissions is called for application name= {0}

Cause: Input permission is null when getPermissions is called. application name= {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03025: Input permission is null when getPermissions is called for application name= {0}

Cause: Input permission is null when getPermissions is called. application name= {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03025: Input permission is null when getPermissions is called for application name= {0}

Cause: Input permission is null when getPermissions is called. application name= {0}

Action: Refer to the logs to rectify the problem.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: {0}

Cause: PolicyStore service instance and PDPService service instance not found in the default JpsContext in an uncontrolled mode.

Action: Configure a PDPService service instance in the default JpsContext, or if running in an uncontroled mode, a PolicyStore Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: {0}

Cause: PolicyStore service instance and PDPService service instance not found in the default JpsContext in an uncontrolled mode.

Action: Configure a PDPService service instance in the default JpsContext, or if running in an uncontroled mode, a PolicyStore Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03026: PDPService and PolicyStore Service instance not found in default context. Reason: {0}

Cause: PolicyStore service instance and PDPService service instance not found in the default JpsContext in an uncontrolled mode.

Action: Configure a PDPService service instance in the default JpsContext, or if running in an uncontroled mode, a PolicyStore Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03027: PDPService service instance failed during initialization due to lack of grant. If you are seeing this error after a new installation, make sure you have updated weblogic.policy as installation step suggested

Cause: PDPService service instance failed during initialization because of lack of grant.

Action: check codebase grant like weblogic.policy to see if proper grant set for all codebase of PDP service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03027: PDPService service instance failed during initialization due to lack of grant. If you are seeing this error after a new installation, make sure you have updated weblogic.policy as installation step suggested

Cause: PDPService service instance failed during initialization because of lack of grant.

Action: check codebase grant like weblogic.policy to see if proper grant set for all codebase of PDP service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03027: PDPService service instance failed during initialization due to lack of grant. If you are seeing this error after a new installation, make sure you have updated weblogic.policy as installation step suggested

Cause: PDPService service instance failed during initialization because of lack of grant.

Action: check codebase grant like weblogic.policy to see if proper grant set for all codebase of PDP service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-03028: Unable to convert to a permission entry to resource-actions entry. Reason: {0}

Cause: Unable to convert to a permission entry to resource-actions entry.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03028: Unable to convert to a permission entry to resource-actions entry. Reason: {0}

Cause: Unable to convert to a permission entry to resource-actions entry.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03028: Unable to convert to a permission entry to resource-actions entry. Reason: {0}

Cause: Unable to convert to a permission entry to resource-actions entry.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03029: Unable to Notify to external Application:{0} Refresh Event. Reason {1}

Cause: Unable to Notify to external Appliacation Refresh Event.

Action: Check the logs for more information to resolve the error.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03030: Catch exception in PDP registration, will retry later.

Cause: Catch exception in PDP registration, retry later.

Action: check the exception details and retry
Level: 1

Type: WARNING

Impact: Configuration

JPS-03031: Catch InterruptedException in PDP registration. Registration failed.

Cause: Catch InterruptedException in PDP registration. Registration failed

Action: check the exception details and retry
Level: 1

Type: ERROR

Impact: Configuration

JPS-03032: Can not access PD server web service during PDP registration, will retry later.

Cause: PD Server web service not available, retry later.

Action: wait retry to access to PD Server web service
Level: 1

Type: WARNING

Impact: Configuration

JPS-03033: Can not access PD client web service during PDP registration, will retry later.

Cause: PD client web service not available, retry later.

Action: wait retry to access to PD client web service
Level: 1

Type: WARNING

Impact: Configuration

JPS-03034: Policystore is not ready on admin server during PDP registration, will retry later.

Cause: Policystore isn't available from admin server, retry later.

Action: wait retry accessing policystore
Level: 1

Type: WARNING

Impact: Configuration

JPS-03035: PDP registration succeeded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-03036: No PDP Service is found in JPS Context {1}

Cause: PDPService service instance is not found in JPS Context.

Action: Configure a PDPService service instance in JPS Context
Level: 1

Type: ERROR

Impact: Configuration

JPS-03037: Exception happened during PDP initialization.

Cause: Exception happened during PDP Initialization

Action: check the exception details and retry
Level: 1

Type: ERROR

Impact: Configuration

JPS-03038: Unable to find PolicyStore or Schema Version. Check farm name and root name of policystore service instance in OPSS configuration file.

Cause: Unable to find PolicyStore or Schema Version.

Action: Check farm name and root name of policystore service instance in OPSS configuration file
Level: 1

Type: ERROR

Impact: Configuration

JPS-03039: Exception {0} happened during Policystore agent processing message {1}, the message will be ignored.

Cause: Exception happened during PolicyStore agent processing

Action: check the exception details and retry
Level: 1

Type: ERROR

Impact: Configuration

JPS-03040: Subject resolver cache initiation failed.

Cause: Subject resolver cache initiation failed.

Action: Make sure all jars are included in the classpath.
Level: 1

Type: ERROR

Impact: Security

JPS-03041: Subject resolver cache property, key: {0}, value: {1} is not valid.

Cause: Subject resolver cache property, key: {0}, value: {1} is not valid.

Action: Check pdp service configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03042: PDP Service property, key: {0}, value: {1} is not valid, use default value: {2}.

Cause: PDP Service property, key: {0}, value: {1} is not valid, use default value: {2}.

Action: Check pdp service configuration.
Level: 1

Type: WARNING

Impact: Security

JPS-03044: Mandatory property {0} of PDP service is missing.

Cause: Mandatory property of PDP service is missing.

Action: provide the required property
Level: 1

Type: ERROR

Impact: Configuration

JPS-03150: Error during setting the field of a provider MBean. {0}

Cause: Error during setting the field of a provider MBean. {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03150: Error during setting the field of a provider MBean. {0}

Cause: Error during setting the field of a provider MBean. {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03150: Error during setting the field of a provider MBean. {0}

Cause: Error during setting the field of a provider MBean. {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03151: getSecurityService returning null for requested service type of {0} for realm {1}

Cause: getSecurityService returning null for requested service type of {0} for realm {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03151: getSecurityService returning null for requested service type of {0} for realm {1}

Cause: getSecurityService returning null for requested service type of {0} for realm {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03151: getSecurityService returning null for requested service type of {0} for realm {1}

Cause: getSecurityService returning null for requested service type of {0} for realm {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03152: Query Atz Cache specified but no response collector supplied

Cause: Query Atz Cache specified but no response collector supplied.

Action: Supply the response collector in the request.
Level: 1

Type: ERROR

Impact: Security

JPS-03152: Query Atz Cache specified but no response collector supplied

Cause: Query Atz Cache specified but no response collector supplied.

Action: Supply the response collector in the request.
Level: 1

Type: ERROR

Impact: Security

JPS-03152: Query Atz Cache specified but no response collector supplied

Cause: Query Atz Cache specified but no response collector supplied.

Action: Supply the response collector in the request.
Level: 1

Type: ERROR

Impact: Security

JPS-03153: Error parsing atz. cache flush time.

Cause: Error parsing atz. cache flush time.

Action: Verify that the value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03153: Error parsing atz. cache flush time.

Cause: Error parsing atz. cache flush time.

Action: Verify that the value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03153: Error parsing atz. cache flush time.

Cause: Error parsing atz. cache flush time.

Action: Verify that the value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03154: Authorization cache has been flushed. Time={0}

Cause: Authorization cache has been flushed. Time={0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03154: Authorization cache has been flushed. Time={0}

Cause: Authorization cache has been flushed. Time={0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03154: Authorization cache has been flushed. Time={0}

Cause: Authorization cache has been flushed. Time={0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03155: Cannot locate class: {0}

Cause: Cannot locate class: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03155: Cannot locate class: {0}

Cause: Cannot locate class: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03155: Cannot locate class: {0}

Cause: Cannot locate class: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03156: The exception has been thrown by ARME. The authorization result is set to deny.

Cause: The exception has been thrown by ARME. The authorization result is set to deny.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03156: The exception has been thrown by ARME. The authorization result is set to deny.

Cause: The exception has been thrown by ARME. The authorization result is set to deny.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03156: The exception has been thrown by ARME. The authorization result is set to deny.

Cause: The exception has been thrown by ARME. The authorization result is set to deny.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03157: Error during initialization of the security framework.

Cause: Error during initialization of the security framework.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03157: Error during initialization of the security framework.

Cause: Error during initialization of the security framework.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03157: Error during initialization of the security framework.

Cause: Error during initialization of the security framework.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03158: Failed to parse resource cache size: {0}

Cause: Failed to parse resource cache size: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03158: Failed to parse resource cache size: {0}

Cause: Failed to parse resource cache size: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03158: Failed to parse resource cache size: {0}

Cause: Failed to parse resource cache size: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03159: Invalid built in type in Value object: {0}

Cause: Invalid built in type in Value object: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03159: Invalid built in type in Value object: {0}

Cause: Invalid built in type in Value object: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03159: Invalid built in type in Value object: {0}

Cause: Invalid built in type in Value object: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03160: Attempt to {0} a {1} value for type: {2}

Cause: Attempt to {0} a {1} value for type: {2}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03160: Attempt to {0} a {1} value for type: {2}

Cause: Attempt to {0} a {1} value for type: {2}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03160: Attempt to {0} a {1} value for type: {2}

Cause: Attempt to {0} a {1} value for type: {2}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03161: identifier not found in symbol table: {0}

Cause: Identifier not found in symbol table: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03161: identifier not found in symbol table: {0}

Cause: Identifier not found in symbol table: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03161: identifier not found in symbol table: {0}

Cause: Identifier not found in symbol table: {0}

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03162: ERROR: PARSE: reason:==> {0}

Cause: ERROR: PARSE: reason:==>

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03162: ERROR: PARSE: reason:==>

Cause: ERROR: PARSE: reason:==>

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03162: ERROR: PARSE: reason:==>

Cause: ERROR: PARSE: reason:==>

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03163: Invalid Declaration type received by setDeclType

Cause: Invalid Declaration type received by setDeclType.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03163: Invalid Declaration type received by setDeclType

Cause: Invalid Declaration type received by setDeclType.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03163: Invalid Declaration type received by setDeclType

Cause: Invalid Declaration type received by setDeclType.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03164: Got exception

Cause: Got exception.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03164: Got exception

Cause: Got exception.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03164: Got exception

Cause: Got exception.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03165: Invalid declaration type found: {0}

Cause: Invalid declaration type found: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03165: Invalid declaration type found: {0}

Cause: Invalid declaration type found: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03165: Invalid declaration type found: {0}

Cause: Invalid declaration type found: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03166: Unexpected PolicyParserTokenType: {0}

Cause: Unexpected PolicyParserTokenType: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03166: Unexpected PolicyParserTokenType: {0}

Cause: Unexpected PolicyParserTokenType: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03166: Unexpected PolicyParserTokenType: {0}

Cause: Unexpected PolicyParserTokenType: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03167: Invalid attribute type: {0}

Cause: Invalid attribute type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03167: Invalid attribute type: {0}

Cause: Invalid attribute type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03167: Invalid attribute type: {0}

Cause: Invalid attribute type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03168: Invalid attribute value type: {0}

Cause: Invalid attribute value type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03168: Invalid attribute value type: {0}

Cause: Invalid attribute value type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03168: Invalid attribute value type: {0}

Cause: Invalid attribute value type: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03169: Invalid configuration

Cause: Invalid configuration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03169: Invalid configuration

Cause: Invalid configuration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03169: Invalid configuration

Cause: Invalid configuration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03170: Try to get {0}, but JPS Policy tree is not available.

Cause: Try to get {0}, but JPS Policy tree is not available.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03170: Try to get {0}, but JPS Policy tree is not available.

Cause: Try to get {0}, but JPS Policy tree is not available.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03170: Try to get {0}, but JPS Policy tree is not available.

Cause: Try to get {0}, but JPS Policy tree is not available.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03171: Unable to update policy: unable to get {0} instance

Cause: Unable to update policy: unable to get {0} instance.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03171: Unable to update policy: unable to get {0} instance

Cause: Unable to update policy: unable to get {0} instance.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03171: Unable to update policy: unable to get {0} instance

Cause: Unable to update policy: unable to get {0} instance.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03172: Unspecified error in {0}

Cause: Unspecified error in {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03172: Unspecified error in {0}

Cause: Unspecified error in {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03172: Unspecified error in {0}

Cause: Unspecified error in {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03173: Commit error: {0}

Cause: Commit error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03173: Commit error: {0}

Cause: Commit error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03173: Commit error: {0}

Cause: Commit error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03174: ARME can not find state.chk file.

Cause: ARME can not find state.chk file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03174: ARME can not find state.chk file.

Cause: ARME can not find state.chk file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03174: ARME can not find state.chk file.

Cause: ARME can not find state.chk file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03175: Invalid mac found in write check, rewrite policies and mac

Cause: !!!>>>Invalid mac found in write check, rewrite policies and mac

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03175: !!!>>>Invalid mac found in write check, rewrite policies and mac

Cause: !!!>>>Invalid mac found in write check, rewrite policies and mac

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03175: !!!>>>Invalid mac found in write check, rewrite policies and mac

Cause: !!!>>>Invalid mac found in write check, rewrite policies and mac

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03176: Failed to write check file.

Cause: Failed to write check file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03176: Failed to write check file.

Cause: Failed to write check file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03176: Failed to write check file.

Cause: Failed to write check file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03177: Failed to close check file writer

Cause: Failed to close check file writer.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03177: Failed to close check file writer

Cause: Failed to close check file writer.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03177: Failed to close check file writer

Cause: Failed to close check file writer.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03178: Failed to write mac, which will cause Mac verification error in the future.

Cause: Failed to write mac, which will cause Mac verification error in the future.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03178: Failed to write mac, which will cause Mac verification error in the future.

Cause: Failed to write mac, which will cause Mac verification error in the future.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03178: Failed to write mac, which will cause Mac verification error in the future.

Cause: Failed to write mac, which will cause Mac verification error in the future.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03179: Prepare request in invalid state for update

Cause: Prepare request in invalid state for update.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03179: Prepare request in invalid state for update

Cause: Prepare request in invalid state for update.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03179: Prepare request in invalid state for update

Cause: Prepare request in invalid state for update.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03180: Error happens: {0}

Cause: Error happened: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03180: Error happens: {0}

Cause: Error happened: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03180: Error happens: {0}

Cause: Error happened: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03181: ArmeRuntimeException happens

Cause: ArmeRuntimeException happened.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03181: ArmeRuntimeException happens

Cause: ArmeRuntimeException happened.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03181: ArmeRuntimeException happens

Cause: ArmeRuntimeException happened.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03182: Cannot get AppGuardInstance, so cannot get information to request policy update from PD.

Cause: Cannot get AppGuardInstanceii, so cannot get information to request policy update from PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03182: Cannot get AppGuardInstance, so cannot get information to request policy update from PD.

Cause: Cannot get AppGuardInstanceii, so cannot get information to request policy update from PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03182: Cannot get AppGuardInstance, so cannot get information to request policy update from PD.

Cause: Cannot get AppGuardInstanceii, so cannot get information to request policy update from PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03183: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Cause: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03183: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Cause: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03183: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Cause: Internal error. The local PD registration is required but LocalPdPort object has not been set. The registration process cannot be completed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03184: No host specified in the ARME configuration, attempting to determine host address...

Cause: No host specified in the ARME configuration, attempting to determine host address...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03184: No host specified in the ARME configuration, attempting to determine host address...

Cause: No host specified in the ARME configuration, attempting to determine host address...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03184: No host specified in the ARME configuration, attempting to determine host address...

Cause: No host specified in the ARME configuration, attempting to determine host address...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03185: No {0} found in the ARME configuration. Cannot contact PD

Cause: No {0} found in the ARME configuration. Cannot contact PD.

Action: Verify configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03185: No {0} found in the ARME configuration. Cannot contact PD

Cause: No {0} found in the ARME configuration. Cannot contact PD.

Action: Verify configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03185: No {0} found in the ARME configuration. Cannot contact PD

Cause: No {0} found in the ARME configuration. Cannot contact PD.

Action: Verify configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03186: InstanceName not found in ARME configuration, using LocalName and host

Cause: InstanceName not found in arme configuration, using LocalName and host.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03186: InstanceName not found in ARME configuration, using LocalName and host

Cause: InstanceName not found in arme configuration, using LocalName and host.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03186: InstanceName not found in ARME configuration, using LocalName and host

Cause: InstanceName not found in arme configuration, using LocalName and host.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03187: No {0} from ARME, unable to contact PD

Cause: No {0} from ARME, unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03187: No {0} from ARME, unable to contact PD

Cause: No {0} from ARME, unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03187: No {0} from ARME, unable to contact PD

Cause: No {0} from ARME, unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03188: Exception initializing SSL. Unable to contact PD

Cause: Exception initializing SSL. Unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03188: Exception initializing SSL. Unable to contact PD

Cause: Exception initializing SSL. Unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03188: Exception initializing SSL. Unable to contact PD

Cause: Exception initializing SSL. Unable to contact PD.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03189: Error getting attribute: {0}

Cause: Error getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03189: Error getting attribute: {0}

Cause: Error getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03189: Error getting attribute: {0}

Cause: Error getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03190: Failed to close File reader while reading salt.

Cause: Failed to close File reader while reading salt.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03190: Failed to close File reader while reading salt.

Cause: Failed to close File reader while reading salt.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03190: Failed to close File reader while reading salt.

Cause: Failed to close File reader while reading salt.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03191: Could not obtain digest algorithm {0}

Cause: Could not obtain digest algorithm '{0}'.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03191: Could not obtain digest algorithm {0}

Cause: Could not obtain digest algorithm '{0}'.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03191: Could not obtain digest algorithm {0}

Cause: Could not obtain digest algorithm '{0}'.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03192: Index of ListValue is wrong

Cause: Index of ListValue is wrong.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03192: Index of ListValue is wrong

Cause: Index of ListValue is wrong.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03192: Index of ListValue is wrong

Cause: Index of ListValue is wrong.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03193: PBEService is not initialized

Cause: PBEService is not initialized.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03193: PBEService is not initialized

Cause: PBEService is not initialized.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03193: PBEService is not initialized

Cause: PBEService is not initialized.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03194: Port is not number type

Cause: Port is not number type.

Action: Verify that the port value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03194: Port is not number type

Cause: Port is not number type.

Action: Verify that the port value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03194: Port is not number type

Cause: Port is not number type.

Action: Verify that the port value is an integer.
Level: 1

Type: ERROR

Impact: Security

JPS-03195: Can not get host IP information, using default IP address: {0}

Cause: Cannot get host IP information, use default IP address: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03195: Can not get host IP information, using default IP address: {0}

Cause: Cannot get host IP information, use default IP address: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03195: Can not get host IP information, using default IP address: {0}

Cause: Cannot get host IP information, use default IP address: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03196: Can not get host IP information.

Cause: Cannot get host IP information.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03196: Can not get host IP information.

Cause: Cannot get host IP information.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03196: Can not get host IP information.

Cause: Cannot get host IP information.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03197: ARME shutdown failed: {0}

Cause: ARME shutdown failed: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03197: ARME shutdown failed: {0}

Cause: ARME shutdown failed: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03197: ARME shutdown failed: {0}

Cause: ARME shutdown failed: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03198: Can not get enablePerfStats from ARME config file

Cause: Cannot get enablePerfStats from arme config file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03198: Can not get enablePerfStats from ARME config file

Cause: Cannot get enablePerfStats from arme config file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03198: Can not get enablePerfStats from ARME config file

Cause: Cannot get enablePerfStats from arme config file.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03199: Configuration file is [{0}]

Cause: Configuration file is [{0}].

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03199: Configuration file is [{0}]

Cause: Configuration file is [{0}].

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03199: Configuration file is [{0}]

Cause: Configuration file is [{0}].

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03200: getDebugStore: IOException caught.

Cause: getDebugStore: IOException happens.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03200: getDebugStore: IOException caught.

Cause: getDebugStore: IOException happens.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03200: getDebugStore: IOException caught.

Cause: getDebugStore: IOException happens.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03201: Privilege name error: {0}

Cause: privilege name error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03201: Privilege name error: {0}

Cause: privilege name error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03201: Privilege name error: {0}

Cause: privilege name error: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03202: Resource name or application name invalid.

Cause: Resource name or application name invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03202: Resource name or application name invalid.

Cause: Resource name or application name invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03202: Resource name or application name invalid.

Cause: Resource name or application name invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03203: Resource name is wrong according to ALES naming logic

Cause: Pesource name is wrong according to ALES naming logic.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03203: Resource name is wrong according to ALES naming logic

Cause: Pesource name is wrong according to ALES naming logic.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03203: Resource name is wrong according to ALES naming logic

Cause: Pesource name is wrong according to ALES naming logic.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03204: Invalid object name

Cause: Invalid object name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03204: Invalid object name

Cause: Invalid object name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03204: Invalid object name

Cause: Invalid object name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03205: Logical name {0} is invalid

Cause: Logical name {0} is invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03205: Logical name {0} is invalid

Cause: Logical name {0} is invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03205: Logical name {0} is invalid

Cause: Logical name {0} is invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03206: Logical name {0} is undefined

Cause: Logical name {0} is undefined.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03206: Logical name {0} is undefined

Cause: Logical name {0} is undefined.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03206: Logical name {0} is undefined

Cause: Logical name {0} is undefined.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03207: IOException occurred when storing logical names {0}

Cause: ioexception occured when storing logical names {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03207: IOException occurred when storing logical names {0}

Cause: ioexception occured when storing logical names {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03207: IOException occurred when storing logical names {0}

Cause: ioexception occured when storing logical names {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03208: Logical names record is not correct

Cause: Logical names record is not correct.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03208: Logical names record is not correct

Cause: Logical names record is not correct.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03208: Logical names record is not correct

Cause: Logical names record is not correct.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03209: objectTree is initialized properly

Cause: ObjectTree is initialized properly.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03209: objectTree is initialized properly

Cause: ObjectTree is initialized properly.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03209: objectTree is initialized properly

Cause: ObjectTree is initialized properly.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03210: Can not close data files: {0}

Cause: Cannot close data files: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03210: Can not close data files: {0}

Cause: Cannot close data files: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03210: Can not close data files: {0}

Cause: Cannot close data files: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03211: Blocking queue is broken

Cause: Blocking queue is broken.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03211: Blocking queue is broken

Cause: Blocking queue is broken.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03211: Blocking queue is broken

Cause: Blocking queue is broken.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03212: Session data could not be loaded. Session abandoned

Cause: Session data could not be loaded. Session abandoned.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03212: Session data could not be loaded. Session abandoned

Cause: Session data could not be loaded. Session abandoned.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03212: Session data could not be loaded. Session abandoned

Cause: Session data could not be loaded. Session abandoned.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03213: args value is null or wrong type

Cause: Args value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03213: args value is null or wrong type

Cause: Args value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03213: args value is null or wrong type

Cause: Args value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03214: Could not add attribute(s) to cache

Cause: Could not add attribute(s) to cache.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03214: Could not add attribute(s) to cache

Cause: Could not add attribute(s) to cache.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03214: Could not add attribute(s) to cache

Cause: Could not add attribute(s) to cache.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03215: Caught BadParameterException during get attribute: {0}

Cause: Caught BadParameterException while getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03215: Caught BadParameterException during get attribute: {0}

Cause: Caught BadParameterException while getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03215: Caught BadParameterException during get attribute: {0}

Cause: Caught BadParameterException while getting attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03216: Installing custom retriever: {0}

Cause: Installing custom retriever: {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03216: Installing custom retriever: {0}

Cause: Installing custom retriever: {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03216: Installing custom retriever: {0}

Cause: Installing custom retriever: {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03217: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Cause: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03217: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Cause: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03217: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Cause: Caught exception while retrieving attribute from context: {0} Continue retrieving static attribute value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03218: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}

Cause: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03218: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}

Cause: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03218: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}

Cause: Failed to transport AttributeValue to AttributeElement, caught {0}: {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03219: AttributeValue type error, not single and list, return null

Cause: AttributeValue type error, not single and list, return null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03219: AttributeValue type error, not single and list, return null

Cause: AttributeValue type error, not single and list, return null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03219: AttributeValue type error, not single and list, return null

Cause: AttributeValue type error, not single and list, return null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03220: Exception from the LDAP/DB server, code: {0}, trying alternate connection

Cause: Exception from the LDAP/DB server, code: {0}, trying alternate connection.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03220: Exception from the LDAP/DB server, code: {0}, trying alternate connection

Cause: Exception from the LDAP/DB server, code: {0}, trying alternate connection.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03220: Exception from the LDAP/DB server, code: {0}, trying alternate connection

Cause: Exception from the LDAP/DB server, code: {0}, trying alternate connection.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03221: Alternate LDAP/DB connection failed, code: {0}

Cause: Alternate LDAP/DB connection failed, code: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03221: Alternate LDAP/DB connection failed, code: {0}

Cause: Alternate LDAP/DB connection failed, code: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03221: Alternate LDAP/DB connection failed, code: {0}

Cause: Alternate LDAP/DB connection failed, code: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03222: Null extendedContext is passed to attribute retriever, cannot look for value.

Cause: Null extendedContext is passed to attribute retriever, cannot look for value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03222: Null extendedContext is passed to attribute retriever, cannot look for value.

Cause: Null extendedContext is passed to attribute retriever, cannot look for value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03222: Null extendedContext is passed to attribute retriever, cannot look for value.

Cause: Null extendedContext is passed to attribute retriever, cannot look for value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-03223: Caught exception while retrieving attribute: {0}

Cause: Caught exception while retrieving attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03223: Caught exception while retrieving attribute: {0}

Cause: Caught exception while retrieving attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03223: Caught exception while retrieving attribute: {0}

Cause: Caught exception while retrieving attribute: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03224: Parameter value is null or wrong type.

Cause: Parameter value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03224: Parameter value is null or wrong type.

Cause: Parameter value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03224: Parameter value is null or wrong type.

Cause: Parameter value is null or wrong type.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03225: Calling RBACEvals:{0}

Cause: Calling RBACEvals:{0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03225: Calling RBACEvals:{0}

Cause: Calling RBACEvals:{0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03225: Calling RBACEvals:{0}

Cause: Calling RBACEvals:{0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03226: Empty Application name or Obligation name is passed to report_obligation function.

Cause: Empty Application name or Obligation name is passed to report_obligation function.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03226: Empty Application name or Obligation name is passed to report_obligation function.

Cause: Empty Application name or Obligation name is passed to report_obligation function.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03226: Empty Application name or Obligation name is passed to report_obligation function.

Cause: Empty Application name or Obligation name is passed to report_obligation function.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03227: Unexpected error: invalid parameter instances.

Cause: Unexpected error: invalid parameter instances.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03227: Unexpected error: invalid parameter instances.

Cause: Unexpected error: invalid parameter instances.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03227: Unexpected error: invalid parameter instances.

Cause: Unexpected error: invalid parameter instances.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03228: The value of args is null

Cause: args is null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03228: The value of args is null

Cause: args is null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03228: The value of args is null

Cause: args is null.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03229: Error during initialization of RetrieverConfiguration.

Cause: Error during initialization of RetrieverConfiguration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03229: Error during initialization of RetrieverConfiguration.

Cause: Error during initialization of RetrieverConfiguration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03229: Error during initialization of RetrieverConfiguration.

Cause: Error during initialization of RetrieverConfiguration.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03230: args value type is null or wrong type value

Cause: args value type is null or wrong type value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03230: args value type is null or wrong type value

Cause: args value type is null or wrong type value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03230: args value type is null or wrong type value

Cause: args value type is null or wrong type value.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03231: {0} supplied to subject_in_group is not a qualified group, will qualify

Cause: {0} supplied to subject_in_group is not a qualified group, will qualify.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03231: {0} supplied to subject_in_group is not a qualified group, will qualify

Cause: {0} supplied to subject_in_group is not a qualified group, will qualify.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03231: {0} supplied to subject_in_group is not a qualified group, will qualify

Cause: {0} supplied to subject_in_group is not a qualified group, will qualify.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03232: Qualified group is {0}

Cause: qualified group is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03232: Qualified group is {0}

Cause: qualified group is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03232: Qualified group is {0}

Cause: qualified group is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03233: Type of args should be String[]

Cause: args should be String[].

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03233: Type of args should be String[]

Cause: args should be String[].

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03233: Type of args should be String[]

Cause: args should be String[].

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03234: No value is passed to {0}

Cause: No value is passed to {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03234: No value is passed to {0}

Cause: No value is passed to {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03234: No value is passed to {0}

Cause: No value is passed to {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03235: No attribute name is passed to sys_obj_exists

Cause: No attribute name is passed to sys_obj_exists.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03235: No attribute name is passed to sys_obj_exists

Cause: No attribute name is passed to sys_obj_exists.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03235: No attribute name is passed to sys_obj_exists

Cause: No attribute name is passed to sys_obj_exists.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03236: Failed to get attribute {0} for eval function {0}

Cause: Failed to get attribute {0} for eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03236: Failed to get attribute {0} for eval function {0}

Cause: Failed to get attribute {0} for eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03236: Failed to get attribute {0} for eval function {0}

Cause: Failed to get attribute {0} for eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03237: Value passed to {0} is not valid, {1}

Cause: Value passed to {0} is not valid, {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03237: Value passed to {0} is not valid, {1}

Cause: Value passed to {0} is not valid, {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03237: Value passed to {0} is not valid, {1}

Cause: Value passed to {0} is not valid, {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03238: {0} is not a valid value for {1}

Cause: {0} is not a valid value for {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03238: {0} is not a valid value for {1}

Cause: {0} is not a valid value for {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03238: {0} is not a valid value for {1}

Cause: {0} is not a valid value for {1}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03239: valid_timeval called for unexpected eval function {0}

Cause: valid_timeval called for unexpected eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03239: valid_timeval called for unexpected eval function {0}

Cause: valid_timeval called for unexpected eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03239: valid_timeval called for unexpected eval function {0}

Cause: valid_timeval called for unexpected eval function {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03240: Unknown eval function {0} used in valid_until_timeofday

Cause: Unknown eval function {0} used in valid_until_timeofday.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03240: Unknown eval function {0} used in valid_until_timeofday

Cause: Unknown eval function {0} used in valid_until_timeofday.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03240: Unknown eval function {0} used in valid_until_timeofday

Cause: Unknown eval function {0} used in valid_until_timeofday.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03241: Disabling extended performance data...

Cause: Disabling extended performance data...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03241: Disabling extended performance data...

Cause: Disabling extended performance data...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03241: Disabling extended performance data...

Cause: Disabling extended performance data...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03242: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Cause: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03242: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Cause: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03242: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Cause: The extended performance data have been retrieved. The total number of attributes is {0}, the total number of functions is {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03243: Unexpected MBean attribute get method: {0}

Cause: Unexpected mbean attribute get method: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03243: Unexpected MBean attribute get method: {0}

Cause: Unexpected mbean attribute get method: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03243: Unexpected MBean attribute get method: {0}

Cause: Unexpected mbean attribute get method: {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03244: {0} specified but no response collector supplied

Cause: {0} specified but no response collector supplied.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03244: {0} specified but no response collector supplied

Cause: {0} specified but no response collector supplied.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03244: {0} specified but no response collector supplied

Cause: {0} specified but no response collector supplied.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03245: Received {0} in isProtectedResource

Cause: Received {0} in isProtectedResource.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03245: Received {0} in isProtectedResource

Cause: Received {0} in isProtectedResource.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03245: Received {0} in isProtectedResource

Cause: Received {0} in isProtectedResource.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03246: Role object passed into wles atz provider is null, ignoring

Cause: Null role object passed into wles atz provider, ignoring.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03246: Role object passed into wles atz provider is null, ignoring

Cause: Null role object passed into wles atz provider, ignoring.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03246: Role object passed into wles atz provider is null, ignoring

Cause: Null role object passed into wles atz provider, ignoring.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03247: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Cause: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03247: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Cause: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03247: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Cause: A SecurityRole object passed to the authorization engine has role name equal to null. The object will be ignored. The string representation of the object is {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03248: Error {0}

Cause: Error {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03248: Error {0}

Cause: Error {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03248: Error {0}

Cause: Error {0}.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03249: ASI shutdown failed

Cause: ASI shutdown failed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03249: ASI shutdown failed

Cause: ASI shutdown failed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03249: ASI shutdown failed

Cause: ASI shutdown failed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03250: getInstance: Warning: The parent classloaders are different.

Cause: getInstance: Warning: The parent classloaders are different.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03250: getInstance: Warning: The parent classloaders are different.

Cause: getInstance: Warning: The parent classloaders are different.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03250: getInstance: Warning: The parent classloaders are different.

Cause: getInstance: Warning: The parent classloaders are different.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-03251: addClassJars: {0}

Cause: addClassJars: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03251: addClassJars: {0}

Cause: addClassJars: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03251: addClassJars: {0}

Cause: addClassJars: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03252: Missing JAR file: {0}

Cause: Missing JAR file: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03252: Missing JAR file: {0}

Cause: Missing JAR file: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03252: Missing JAR file: {0}

Cause: Missing JAR file: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03253: Error initializing URLs in classloader. Vector: {0}

Cause: Error initializing URLs in classloader. Vector: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03253: Error initializing URLs in classloader. Vector: {0}

Cause: Error initializing URLs in classloader. Vector: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03253: Error initializing URLs in classloader. Vector: {0}

Cause: Error initializing URLs in classloader. Vector: {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03254: lazy getRoles failed with error {0}

Cause: lazy getRoles failed with error {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03254: lazy getRoles failed with error {0}

Cause: lazy getRoles failed with error {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03254: lazy getRoles failed with error {0}

Cause: lazy getRoles failed with error {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03255: null value returned in roles list, ignoring

Cause: null value returned in roles list, ignoring.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03255: null value returned in roles list, ignoring

Cause: null value returned in roles list, ignoring.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03255: null value returned in roles list, ignoring

Cause: null value returned in roles list, ignoring.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03256: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Cause: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03256: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Cause: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03256: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Cause: Internal error. Method queryRoles has returned role {0} that starts with an incorrect prefix for a role. The role will be ignored.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03257: Passed an non URLResource, in getAttributeValue

Cause: Passed a non URLResource, in getAttributeValue.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03257: Passed an non URLResource, in getAttributeValue

Cause: Passed a non URLResource, in getAttributeValue.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03257: Passed an non URLResource, in getAttributeValue

Cause: Passed a non URLResource, in getAttributeValue.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03258: Initializing UserUtils; {0}

Cause: Initializing UserUtils; {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03258: Initializing UserUtils; {0}

Cause: Initializing UserUtils; {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03258: Initializing UserUtils; {0}

Cause: Initializing UserUtils; {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03259: Invalid built in type received

Cause: Invalid built in type received.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03259: Invalid built in type received

Cause: Invalid built in type received.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03259: Invalid built in type received

Cause: Invalid built in type received.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03260: Attempt to {0} when CRED is wrong type

Cause: Attempt to {0} when CRED is wrong type.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03260: Attempt to {0} when CRED is wrong type

Cause: Attempt to {0} when CRED is wrong type.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03260: Attempt to {0} when CRED is wrong type

Cause: Attempt to {0} when CRED is wrong type.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03261: No locally defined evaluator found for function {0}.

Cause: No locally defined evaluator found for function {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03261: No locally defined evaluator found for function {0}.

Cause: No locally defined evaluator found for function {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03261: No locally defined evaluator found for function {0}.

Cause: No locally defined evaluator found for function {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03262: DiscoveryModeRoleMap does not support this operation

Cause: DiscoveryModeRoleMap does not support this operation

Action: Do not call method not supported
Level: 1

Type: WARNING

Impact: Configuration

JPS-03262: DiscoveryModeRoleMap does not support this operation

Cause: DiscoveryModeRoleMap does not support this operation

Action: Do not call method not supported
Level: 1

Type: WARNING

Impact: Configuration

JPS-03262: DiscoveryModeRoleMap does not support this operation

Cause: DiscoveryModeRoleMap does not support this operation

Action: Do not call method not supported
Level: 1

Type: WARNING

Impact: Configuration

JPS-03263: DiscoveryModeRoleMap never contains data

Cause: DiscoveryModeRoleMap never contains data

Action: Do not try to get data from DiscoveryModeRoleMap.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03263: DiscoveryModeRoleMap never contains data

Cause: DiscoveryModeRoleMap never contains data

Action: Do not try to get data from DiscoveryModeRoleMap.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03263: DiscoveryModeRoleMap never contains data

Cause: DiscoveryModeRoleMap never contains data

Action: Do not try to get data from DiscoveryModeRoleMap.
Level: 1

Type: WARNING

Impact: Configuration

JPS-03264: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Cause: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Action: Please check the configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03264: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Cause: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Action: Please check the configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03264: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Cause: The attribute dependency leads to a dead loop, {1} depends on {0} already.

Action: Please check the configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-03265: Data source based DB query failed, try again.

Cause: Data source based DB query failed, try again.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03265: Data source based DB query failed, try again.

Cause: Data source based DB query failed, try again.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03265: Data source based DB query failed, try again.

Cause: Data source based DB query failed, try again.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03266: Failed to retrieve connection for url {0} due to following exception {1}.

Cause: Failed to retrieve connection for {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03266: Failed to retrieve connection for url {0} due to following exception {1}.

Cause: Failed to retrieve connection for {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03266: Failed to retrieve connection for url {0} due to following exception {1}.

Cause: Failed to retrieve connection for {0}.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-03267: Ignoring credential variable exception in computeObligation for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03267: Ignoring credential variable exception in computeObligation for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03267: Ignoring credential variable exception in computeObligation for {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-03268: In Policy {0}, an invalid Resource Name Expression {1} was encountered. The Policy will not participate in the runtime authorization evaluation. Reason: {2}

Cause: Resource name expression in policy is invalid

Action: Correct the reource name expression.
Level: 1

Type: ERROR

Impact: Security

JPS-03268: In Policy {0}, an invalid Resource Name Expression {1} was encountered. The Policy will not participate in the runtime authorization evaluation. Reason: {2}

Cause: Resource name expression in policy is invalid

Action: Correct the reource name expression.
Level: 1

Type: ERROR

Impact: Security

JPS-03268: In Policy {0}, an invalid Resource Name Expression {1} was encountered. The Policy will not participate in the runtime authorization evaluation. Reason: {2}

Cause: Resource name expression in policy is invalid

Action: Correct the reource name expression.
Level: 1

Type: ERROR

Impact: Security

JPS-03269: Size of bag provided for type-one-and-only function is not one.

Cause: Size of bag provided to type one and only function is not one.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03269: Size of bag provided for type-one-and-only function is not one.

Cause: Size of bag provided to type one and only function is not one.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03269: Size of bag provided for type-one-and-only function is not one.

Cause: Size of bag provided to type one and only function is not one.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03270: Invalid value of year {0} or month {1} in yearMonthDuration .Must be between max and min values for integer.

Cause: Value provided for year or month is outside the supported integer range on this JVM.

Action: Provide a valid integer value.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03270: Invalid value of year {0} or month {1} in yearMonthDuration .Must be between max and min values for integer.

Cause: Value provided for year or month is outside the supported integer range on this JVM.

Action: Provide a valid integer value.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03270: Invalid value of year {0} or month {1} in yearMonthDuration .Must be between max and min values for integer.

Cause: Value provided for year or month is outside the supported integer range on this JVM.

Action: Provide a valid integer value.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03271: Function name passed to evaluator is null.

Cause: Function name is null.

Action: Provide a valid function name.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03271: Function name passed to evaluator is null.

Cause: Function name is null.

Action: Provide a valid function name.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03271: Function name passed to evaluator is null.

Cause: Function name is null.

Action: Provide a valid function name.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03272: No arguments passed to function {0}.

Cause: No arguments passed to function.

Action: Provide a valid function arguments.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03272: No arguments passed to function {0}.

Cause: No arguments passed to function.

Action: Provide a valid function arguments.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03272: No arguments passed to function {0}.

Cause: No arguments passed to function.

Action: Provide a valid function arguments.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-03273: Application {0} attribute {1} is not available.

Cause: Application {0} attribute {1} is not available.

Action: None.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-04000: Cannot get the default policy store.

Cause: Could not find to the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04000: Cannot get the default policy store.

Cause: Could not find to the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04000: Cannot get the default policy store.

Cause: Could not find to the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04001: Cannot read the default policy store.

Cause: Could not read the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04001: Cannot read the default policy store.

Cause: Could not read the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04001: Cannot read the default policy store.

Cause: Could not read the default policy store.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04002: Cannot get application policy for application "{0}".

Cause: Encountered a policy store internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04002: Cannot get application policy for application "{0}".

Cause: Encountered a policy store internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04002: Cannot get application policy for application "{0}".

Cause: Encountered a policy store internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04003: Duplicate principal present "{0}"in a grant request.

Cause: Found that list of principals in the grantee for the grant contains duplicate

Action: Correct the list of principals in the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04003: Duplicate principal present "{0}"in a grant request.

Cause: Found that list of principals in the grantee for the grant contains duplicate

Action: Correct the list of principals in the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04003: Duplicate principal present "{0}"in a grant request.

Cause: Found that list of principals in the grantee for the grant contains duplicate

Action: Correct the list of principals in the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04004: Duplicate permission present "{0}" in a grant request.

Cause: Found that list of permissions in the grant contains duplicate.

Action: Correct the list of permissions in the grant.
Level: 1

Type: WARNING

Impact: Security

JPS-04004: Duplicate permission present "{0}" in a grant request.

Cause: Found that list of permissions in the grant contains duplicate.

Action: Correct the list of permissions in the grant.
Level: 1

Type: WARNING

Impact: Security

JPS-04004: Duplicate permission present "{0}" in a grant request.

Cause: Found that list of permissions in the grant contains duplicate.

Action: Correct the list of permissions in the grant.
Level: 1

Type: WARNING

Impact: Security

JPS-04005: More than one result found for given Application Name:{0}, Query:{1}, Actual results:{2}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04005: More than one result found for given Application Name:{0}, Query:{1}, Actual results:{2}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04005: More than one result found for given Application Name:{0}, Query:{1}, Actual results:{2}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04006: No results found for given Application Name:{0}, DN: {1}, Query: {2}.

Cause: No results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04021: Application Policy "{0}" already exists.

Cause: Encountered two application policy contexts with identical names.

Action: Modify an application policy context to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04021: Cannot create application policy context "{0}".

Cause: Encountered two application policy contexts with identical names.

Action: Modify an application policy context to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04021: Cannot create application policy context "{0}".

Cause: Encountered two application policy contexts with identical names.

Action: Modify an application policy context to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04022: Cannot create application policy context "{0}".

Cause: Failed to complete persist operation while creating an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04022: Cannot create application policy context "{0}".

Cause: Failed to complete persist operation while creating an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04022: Cannot create application policy context "{0}".

Cause: Failed to complete persist operation while creating an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04026: Cannot delete application policy context "{0}".

Cause: Could not find a policy context with the provided name.

Action: Verify that a context with the provided name exists.
Level: 1

Type: WARNING

Impact: Security

JPS-04026: Cannot delete application policy context "{0}".

Cause: Could not find a policy context with the provided name.

Action: Verify that a context with the provided name exists.
Level: 1

Type: WARNING

Impact: Security

JPS-04026: Cannot delete application policy context "{0}".

Cause: Could not find a policy context with the provided name.

Action: Verify that a context with the provided name exists.
Level: 1

Type: WARNING

Impact: Security

JPS-04027: Role with name "{0}" does not exist.

Cause: Could not find a role with name {0}.

Action: Verify that a role with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04027: Role with name "{0}" does not exist.

Cause: Could not find a role with name {0}.

Action: Verify that a role with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04027: Role with name "{0}" does not exist.

Cause: Could not find a role with name {0}.

Action: Verify that a role with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04028: Application with name "{0}" does not exist.

Cause: Could not find application with name {0}.

Action: Verify that an application with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04028: Application with name "{0}" does not exist.

Cause: Could not find application with name {0}.

Action: Verify that an application with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04028: Application with name "{0}" does not exist.

Cause: Could not find application with name {0}.

Action: Verify that an application with the provided name exists.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04029: Cannot create principal with class name "{0}".

Cause: Could not create principal with class name {0}.

Action: Verify that the provided class name is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04029: Cannot create principal with class name "{0}".

Cause: Could not create principal with class name {0}.

Action: Verify that the provided class name is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04029: Cannot create principal with class name "{0}".

Cause: Could not create principal with class name {0}.

Action: Verify that the provided class name is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04030: Cannot delete application policy context "{0}".

Cause: Failed to complete persist operation while deleting an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04030: Cannot delete application policy context "{0}".

Cause: Failed to complete persist operation while deleting an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04030: Cannot delete application policy context "{0}".

Cause: Failed to complete persist operation while deleting an application policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04031: Parameter "{0}" is null or empty.

Cause: Supplied parameter {0} was null or empty.

Action: Verify that the supplied parameter is non-null. If it is of type String, ensure that its length is positive.
Level: 1

Type: WARNING

Impact: Security

JPS-04031: Parameter "{0}" is null.

Cause: Supplied parameter {0} was null.

Action: Verify that the supplied parameter is non-null. If it is of type String, ensure that its length is positive.
Level: 1

Type: WARNING

Impact: Security

JPS-04031: Parameter "{0}" is null.

Cause: Supplied parameter {0} was null.

Action: Verify that the supplied parameter is non-null. If it is of type String, ensure that its length is positive.
Level: 1

Type: WARNING

Impact: Security

JPS-04032: Parameter "{0}" supplied is not the instance of "{1}".

Cause: Parameter {0} supplied is not the instance of {1}.

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04032: Parameter "{0}" supplied is not the instance of "{1}".

Cause: Parameter {0} supplied is not the instance of {1}.

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04032: Parameter "{0}" supplied is not the instance of "{1}".

Cause: Parameter {0} supplied is not the instance of {1}.

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04033: Parameter "{0}" supplied is not of the type "{1}" (as expected).

Cause: Parameter {0} supplied is not of the type {1} (as expected).

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04033: Parameter "{0}" supplied is not of the type "{1}" (as expected).

Cause: Parameter {0} supplied is not of the type {1} (as expected).

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04033: Parameter "{0}" supplied is not of the type "{1}" (as expected).

Cause: Parameter {0} supplied is not of the type {1} (as expected).

Action: Ensure parameter is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04034: Failed to modify properties for Application "{0}".

Cause: Cannot modify application policy.

Action: Check the logs for errors.
Level: 1

Type: WARNING

Impact: Security

JPS-04034: Failed to modify properties for Application "{0}".

Cause: Cannot modify application policy.

Action: Check the logs for errors.
Level: 1

Type: WARNING

Impact: Security

JPS-04034: Failed to modify properties for Application "{0}".

Cause: Cannot modify application policy.

Action: Check the logs for errors.
Level: 1

Type: WARNING

Impact: Security

JPS-04035: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure attribute name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04035: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure attribute name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04035: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: AttributeName {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure attribute name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04036: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure function name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04036: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure function name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04036: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters other than alphanumeric and/or underscores.

Cause: Function Name {0} supplied should start with alphabet or an underscore. Name cannot contain characters contain other than alphanumeric and/or underscores.

Action: Ensure function name is of correct datatype.
Level: 1

Type: WARNING

Impact: Security

JPS-04037: Name "{0}" starts or ends with whitespace.

Cause: Object name should not start with or end with whitespace.

Action: Ensure object name has no whitespace in the beginning and end.
Level: 1

Type: WARNING

Impact: Security

JPS-04037: Name '{0}' starts or ends with whitespace.

Cause: Object name should not start with or end with whitespace.

Action: Ensure object name has no whitespace in the beginning and end.
Level: 1

Type: WARNING

Impact: Security

JPS-04037: Name '{0}' starts or ends with whitespace.

Cause: Object name should not start with or end with whitespace.

Action: Ensure object name has no whitespace in the beginning and end.
Level: 1

Type: WARNING

Impact: Security

JPS-04038: Object name only contains whitespace.

Cause: Object name should not only contain whitespace.

Action: Ensure object name doesn't only contain whitespace.
Level: 1

Type: WARNING

Impact: Security

JPS-04038: Object name only contains whitespace.

Cause: Object name should not only contain whitespace.

Action: Ensure object name doesn't only contain whitespace.
Level: 1

Type: WARNING

Impact: Security

JPS-04038: Object name only contains whitespace.

Cause: Object name should not only contain whitespace.

Action: Ensure object name doesn't only contain whitespace.
Level: 1

Type: WARNING

Impact: Security

JPS-04039: Application "{0}", Deleting {1} entries under "{2}", Maximum remaining re-tries {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04039: Application "{0}", Deleting {1} entries under "{2}", Maximum remaining re-tries {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04039: Application "{0}", Deleting {1} entries under "{2}", Maximum remaining re-tries {3}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04080: Scanning of system policy failed. Reason {0}

Cause: Scan of system policy failed.

Action: Check the system policy setup and the provider setup.
Level: 1

Type: WARNING

Impact: Security

JPS-04080: Scanning of system policy failed. Reason {0}

Cause: Scan of system policy failed.

Action: Check the system policy setup and the provider setup.
Level: 1

Type: WARNING

Impact: Security

JPS-04080: Scanning of system policy failed. Reason {0}

Cause: Scan of system policy failed.

Action: Check the system policy setup and the provider setup.
Level: 1

Type: WARNING

Impact: Security

JPS-04081: Policy store purge thread interrupted. Reason {0}.

Cause: Purge thread interrupted in policy caching.

Action: Check the policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04081: Policy store purge thread interrupted. Reason {0}.

Cause: Purge thread interrupted in policy caching.

Action: Check the policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04081: Policy store purge thread interrupted. Reason {0}.

Cause: Purge thread interrupted in policy caching.

Action: Check the policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04082: Deletion of system policy failed. Reason {0}

Cause: Deletion of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04082: Deletion of system policy failed. Reason {0}

Cause: Deletion of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04082: Deletion of system policy failed. Reason {0}

Cause: Deletion of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04083: Creation of system policy failed. Reason {0}

Cause: Creation of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04083: Creation of system policy failed. Reason {0}

Cause: Creation of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04083: Creation of system policy failed. Reason {0}

Cause: Creation of system policy failed.

Action: Provide legal non empty values for policy name
Level: 1

Type: WARNING

Impact: Security

JPS-04084: Migration of application policy failed. Further migration of application policies halted. Reason: {0}.

Cause: Exception in migration of application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04084: Migration of application policy failed. Reason: {0}.

Cause: Exception in migration of application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04084: Migration of application policy failed. Reason: {0}.

Cause: Exception in migration of application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04085: Migration of codebase policy failed. Reason: {0}.

Cause: Exception in migration of codebase policy

Action: Check codebase policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04085: Migration of codebase policy failed. Reason: {0}.

Cause: Exception in migration of codebase policy

Action: Check codebase policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04085: Migration of codebase policy failed. Reason: {0}.

Cause: Exception in migration of codebase policy

Action: Check codebase policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04086: Could not perform isPolicyModified. Reason {0}

Cause: Is policy modification check failed.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04086: Could not perform isPolicyModified. Reason {0}

Cause: Is policy modification check failed.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04086: Could not perform isPolicyModified. Reason {0}

Cause: Is policy modification check failed.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04089: Could not get policy cache count. Reason {0}

Cause: Could not retrieve policy cache count.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04089: Could not get policy cache count. Reason {0}

Cause: Could not retrieve policy cache count.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04089: Could not get policy cache count. Reason {0}

Cause: Could not retrieve policy cache count.

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-04090: The policy store property {0} is invalid or not defined.

Cause: The policy store property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04090: The policy store property {0} is invalid or not defined.

Cause: The policy store property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04090: The policy store property {0} is invalid or not defined.

Cause: The policy store property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04091: Application {0} is being deployed with policy migration option set to {1}, start policy migration.

Cause: Start application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04091: Application {0} is being deployed with policy migration option set to {1}, start policy migration.

Cause: Start application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04091: Application {0} is being deployed with policy migration option set to {1}, start policy migration.

Cause: Start application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04092: Application {0} is being deployed with policy migration option set to neither OVERWRITE nor MERGE, skip policy migration.

Cause: Skip application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04092: Application {0} is being deployed with policy migration option set to neither OVERWRITE nor MERGE, skip policy migration.

Cause: Skip application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04092: Application {0} is being deployed with policy migration option set to neither OVERWRITE nor MERGE, skip policy migration.

Cause: Skip application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04093: Application policy migration for application {0} is completed successfully.

Cause: Complete application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04093: Application policy migration for application {0} is completed successfully.

Cause: Complete application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04093: Application policy migration for application {0} is completed successfully.

Cause: Complete application policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04094: Start removing application policies for Application {0}.

Cause: Start application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04094: Start removing application policies for Application {0}.

Cause: Start application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04094: Start removing application policies for Application {0}.

Cause: Start application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04095: Application policy removal for application {0} is completed successfully.

Cause: Complete application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04095: Application policy removal for application {0} is completed successfully.

Cause: Complete application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04095: Application policy removal for application {0} is completed successfully.

Cause: Complete application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04096: Application policies for application {0} was NOT removed in application undeployment with jps.policystore.removal set to OFF.

Cause: Skip application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04096: Application policies for application {0} was NOT removed in application undeployment with jps.policystore.removal set to OFF.

Cause: Skip application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04096: Application policies for application {0} was NOT removed in application undeployment with jps.policystore.removal set to OFF.

Cause: Skip application policy removal

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04097: Application {0} is being deployed without existing application policies found in static deployment, start policy migration.

Cause: Start application policy migration in static deployment

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04097: Application {0} is being deployed without existing application policies found in static deployment, start policy migration.

Cause: Start application policy migration in static deployment

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04097: Application {0} is being deployed without existing application policies found in static deployment, start policy migration.

Cause: Start application policy migration in static deployment

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04098: Start codebase policy migration for application {0}.

Cause: Start codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04098: Start codebase policy migration for application {0}.

Cause: Start codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04098: Start codebase policy migration for application {0}.

Cause: Start codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04099: Codebase policy migration for {0} is completed successfully.

Cause: Complete codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04099: Codebase policy migration for {0} is completed successfully.

Cause: Complete codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04099: Codebase policy migration for {0} is completed successfully.

Cause: Complete codebase policy migration

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-04100: Application Role "{0}" already exists.

Cause: Encountered two roles with identical names.

Action: Modify a role to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04100: Cannot create application role "{0}".

Cause: Encountered two roles with identical names.

Action: Modify a role to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04100: Cannot create application role "{0}".

Cause: Encountered two roles with identical names.

Action: Modify a role to have a distinct name.
Level: 1

Type: WARNING

Impact: Security

JPS-04101: Cannot create application role "{0}".

Cause: Failed to complete persist operation while creating an application role.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04101: Cannot create application role "{0}".

Cause: Failed to complete persist operation while creating an application role.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04101: Cannot create application role "{0}".

Cause: Failed to complete persist operation while creating an application role.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04102: Cannot create application role. Cause: Invalid Argument -- Multiple role categories supplied for single application role

Cause: Persist operation failed because more than one role category supplied for create role

Action: Ensure supplied parameters are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-04102: Cannot create application role. Cause: Invalid Argument -- Multiple role categories supplied for single application role

Cause: Persist operation failed because more than one role category supplied for create role

Action: Ensure supplied parameters are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-04102: Cannot create application role. Cause: Invalid Argument -- Multiple role categories supplied for single application role

Cause: Persist operation failed because more than one role category supplied for create role

Action: Ensure supplied parameters are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-04110: Cannot delete application role "{0}". Cause: Application role not found.

Cause: Could not find an application role in the application policy.

Action: Check the name of the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-04110: Cannot delete application role "{0}". Cause: Application role not found.

Cause: Could not find an application role in the application policy.

Action: Check the name of the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-04110: Cannot delete application role "{0}". Cause: Application role not found.

Cause: Could not find an application role in the application policy.

Action: Check the name of the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-04111: Cannot delete application role "{0}".

Cause: Could not remove application role from policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04111: Cannot delete application role "{0}".

Cause: Could not remove application role from policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04111: Cannot delete application role "{0}".

Cause: Could not remove application role from policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04112: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role is a member of one or more other application roles (nested role hierarchy).

Action: Flatten the nested role hierarchy, and then remove the desired role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04112: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role is a member of one or more other application roles (nested role hierarchy).

Action: Flatten the nested role hierarchy, and then remove the desired role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04112: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role is a member of one or more other application roles (nested role hierarchy).

Action: Flatten the nested role hierarchy, and then remove the desired role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04113: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use, or contains enterprise groups or enterprise users.

Action: Remove the enterprise groups and enterprise users from the application role, or remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04113: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use, or contains enterprise groups or enterprise users.

Action: Remove the enterprise groups and enterprise users from the application role, or remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04113: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use, or contains enterprise groups or enterprise users.

Action: Remove the enterprise groups and enterprise users from the application role, or remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04114: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role has one or more permissions granted to it.

Action: Revoke the permission(s) from the application role, and then remove the role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04114: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role has one or more permissions granted to it.

Action: Revoke the permission(s) from the application role, and then remove the role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04114: Cannot delete application role "{0}".

Cause: Could not remove application role "{0}" because it may be in use; this role has one or more permissions granted to it.

Action: Revoke the permission(s) from the application role, and then remove the role. Alternatively, remove the application role using the option force set to true.
Level: 1

Type: WARNING

Impact: Security

JPS-04120: Cannot add principal to application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04120: Cannot add principal to application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04120: Cannot add principal to application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04121: Cannot add principal to application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Ensure the application role is present in the application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-04121: Cannot add principal to application role.

Cause: Could not find application role in the application policy context.

Action: Ensure the application role is present in the application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-04121: Cannot add principal to application role.

Cause: Could not find application role in the application policy context.

Action: Ensure the application role is present in the application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-04122: Cannot add principal to application role; principal(s) "{0}" is already a member of application role "{1}".

Cause: Found that principal {0} is already a member of the application role {1}.

Action: Correct the principal name.
Level: 1

Type: WARNING

Impact: Security

JPS-04122: Cannot add principal to application role.

Cause: Found that principal {0} is already a member of the application role {1}.

Action: Correct the principal name.
Level: 1

Type: WARNING

Impact: Security

JPS-04122: Cannot add principal to application role.

Cause: Found that principal {0} is already a member of the application role {1}.

Action: Correct the principal name.
Level: 1

Type: WARNING

Impact: Security

JPS-04123: Cannot add principal to the application role.

Cause: Attempted to insert an application role as a member of itself.

Action: Correct the application role principal name. The containment in the role hierarchy must be cycle-free.
Level: 1

Type: WARNING

Impact: Security

JPS-04123: Cannot add principal to the application role.

Cause: Attempted to insert an application role as a member of itself.

Action: Correct the application role principal name. The containment in the role hierarchy must be cycle-free.
Level: 1

Type: WARNING

Impact: Security

JPS-04123: Cannot add principal to the application role.

Cause: Attempted to insert an application role as a member of itself.

Action: Correct the application role principal name. The containment in the role hierarchy must be cycle-free.
Level: 1

Type: WARNING

Impact: Security

JPS-04124: The application role {0} added to {1} has no GUID defined.

Cause: The application role {0} added to {1} has no GUID defined.

Action: Ensure the application role has GUID before adding it as a member of an application role.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04124: The application role {0} added to {1} has no GUID defined.

Cause: The application role {0} added to {1} has no GUID defined.

Action: Ensure the application role has GUID before adding it as a member of an application role.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04124: The application role {0} added to {1} has no GUID defined.

Cause: The application role {0} added to {1} has no GUID defined.

Action: Ensure the application role has GUID before adding it as a member of an application role.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04125: Application Role {0} granted to role category {1} cannot be found in application {2}

Cause: Application Role {0} granted to role category {1} cannot be found in application {2}

Action: Ensure application role exists before assigning it to a role category
Level: 1

Type: WARNING

Impact: Security

JPS-04125: Application Role {0} granted to role category {1} cannot be found in application {2}

Cause: Application Role {0} granted to role category {1} cannot be found in application {2}

Action: Ensure application role exists before assigning it to a role category
Level: 1

Type: WARNING

Impact: Security

JPS-04125: Application Role {0} granted to role category {1} cannot be found in application {2}

Cause: Application Role {0} granted to role category {1} cannot be found in application {2}

Action: Ensure application role exists before assigning it to a role category
Level: 1

Type: WARNING

Impact: Security

JPS-04130: Cannot remove principal from application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04130: Cannot remove principal from application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04130: Cannot remove principal from application role.

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04131: Cannot remove principal from application role; cannot find application role "{0}" in application policy context.

Cause: Could not find the specified application role in the application policy context.

Action: Correct the application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04131: Cannot remove principal from application role; cannot find application role "{0}" in application policy context.

Cause: Could not find the specified application role in the application policy context.

Action: Correct the application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04131: Cannot remove principal from application role; cannot find application role "{0}" in application policy context.

Cause: Could not find the specified application role in the application policy context.

Action: Correct the application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04132: Cannot remove principal from application role; principal "{0}" is not member of application role "{1}".

Cause: See error message.

Action: Correct the principal role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04132: Cannot remove principal from application role; principal "{0}" is not member of application role "{1}".

Cause: See error message.

Action: Correct the principal role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04132: Cannot remove principal from application role; principal "{0}" is not member of application role "{1}".

Cause: See error message.

Action: Correct the principal role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04135: Resource name not specified in application {0}.

Cause: Resource name not specified in application {0}.

Action: Ensure the resource name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04136: Resource type name not specified in application {0}.

Cause: Resource type name not specified in application {0}.

Action: Ensure the resource type name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04137: Permission set name not specified in application {0}.

Cause: Permission set name not specified in application {0}.

Action: Ensure the permission set name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04138: Application role name not specified in application {0}.

Cause: Application role name not specified in application {0}.

Action: Ensure the application role name is not null.
Level: 1

Type: WARNING

Impact: Security

JPS-04140: Cannot complete application role search because search expression "{0}" is incorrect.

Cause: Found an invalid search pattern.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04140: Cannot complete application role search because search expression "{0}" is incorrect.

Cause: Found an invalid search pattern.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04140: Cannot complete application role search because search expression "{0}" is incorrect.

Cause: Found an invalid search pattern.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04141: Cannot complete application role search because of internal error {0}.

Cause: Encountered an internal policy store error while searching the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04141: Cannot complete application role search because of internal error {0}.

Cause: Encountered an internal policy store error while searching the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04141: Cannot complete application role search because of internal error {0}.

Cause: Encountered an internal policy store error while searching the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04142: Cannot complete application role search because search role attribute "{0}" is incorrect.

Cause: Could not complete the search because the application role attribute {0} was invalid.

Action: Supply a valid role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04142: Cannot complete application role search because search role attribute "{0}" is incorrect.

Cause: Could not complete the search because the application role attribute {0} was invalid.

Action: Supply a valid role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04142: Cannot complete application role search because search role attribute "{0}" is incorrect.

Cause: Could not complete the search because the application role attribute {0} was invalid.

Action: Supply a valid role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04143: Cannot find application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04143: Cannot find application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04143: Cannot find application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04144: Cannot get granted application role for principal "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04144: Cannot get granted application role for principal "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04144: Cannot get granted application role for principal "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04145: Cannot get all application roles for application "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04145: Cannot get all application roles for application "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04145: Cannot get all application roles for application "{0}".

Cause: Encountered an internal policy store error.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04146: Cannot complete application role search because search role attribute name is null.

Cause: Could not complete the search because the role attribute name was NULL.

Action: Provide a non-null role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04146: Cannot complete application role search because search role attribute name is null.

Cause: Could not complete the search because the role attribute name was NULL.

Action: Provide a non-null role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04146: Cannot complete application role search because search role attribute name is null.

Cause: Could not complete the search because the role attribute name was NULL.

Action: Provide a non-null role attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-04147: Cannot get members of application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04147: Cannot get members of application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04147: Cannot get members of application role "{0}".

Cause: Could not find application role in the application policy context.

Action: Supply the name of an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04148: Exception when converting "{0}" to number, msg is "{1}".

Cause: Exception when converting {0} to number, msg is {1}

Action: Only number is allowed
Level: 1

Type: WARNING

Impact: Security

JPS-04148: Exception when converting "{0}" to number, msg is "{1}".

Cause: Exception when converting {0} to number, msg is {1}

Action: Only number is allowed
Level: 1

Type: WARNING

Impact: Security

JPS-04148: Exception when converting "{0}" to number, msg is "{1}".

Cause: Exception when converting {0} to number, msg is {1}

Action: Only number is allowed
Level: 1

Type: WARNING

Impact: Security

JPS-04150: Cannot alter application role {0} since multiple entries found for the application name:{1} query: {2} and actual result is {3}.

Cause: Encountered the policy store error {0}.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04150: Cannot alter application role {0} since multiple entries found for the application name:{1} query: {2} and actual result is {3}.

Cause: Encountered the policy store error {0}.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04150: Cannot alter application role {0} since multiple entries found for the application name:{1} query: {2} and actual result is {3}.

Cause: Encountered the policy store error {0}.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04151: Cannot alter application role.

Cause: Could not find application role {0} in the application policy context.

Action: Provide an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04151: Cannot alter application role.

Cause: Could not find application role {0} in the application policy context.

Action: Provide an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04151: Cannot alter application role.

Cause: Could not find application role {0} in the application policy context.

Action: Provide an existing application role name.
Level: 1

Type: WARNING

Impact: Security

JPS-04153: In Domain {0}, Application {1} is not present.

Cause: Application not found in the policystore

Action: Check the name of the application in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04153: In Domain {0}, Application {1} is not present.

Cause: Application not found in the policystore

Action: Check the name of the application in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04153: In Domain {0}, Application {1} is not present.

Cause: Application not found in the policystore

Action: Check the name of the application in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04154: Refresh of application policy failed. Reason {0}

Cause: Refresh of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04154: Refresh of application policy failed. Reason {0}

Cause: Refresh of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04154: Refresh of application policy failed. Reason {0}

Cause: Refresh of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04155: Scanning of application policy failed. Reason {0}

Cause: Scan of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04155: Scanning of application policy failed. Reason {0}

Cause: Scan of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04155: Scanning of application policy failed. Reason {0}

Cause: Scan of application policy failed.

Action: Check the application policy setup and the provider setup
Level: 1

Type: WARNING

Impact: Security

JPS-04156: RoleCategory modification attribute "{0}" is invalid.

Cause: Invalid RoleCategory modify attribute

Action: Check whether the attribute you are trying to modify is valid or not.
Level: 1

Type: WARNING

Impact: Security

JPS-04156: RoleCategory modification attribute "{0}" is invalid.

Cause: Invalid RoleCategory modify attribute

Action: Check whether the attribute you are trying to modify is valid or not.
Level: 1

Type: WARNING

Impact: Security

JPS-04156: RoleCategory modification attribute "{0}" is invalid.

Cause: Invalid RoleCategory modify attribute

Action: Check whether the attribute you are trying to modify is valid or not.
Level: 1

Type: WARNING

Impact: Security

JPS-04157: RoleCategory "{0}" already exists.

Cause: The role category already exists.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04157: RoleCategory {0} already exists.

Cause: The role category already exists.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04157: RoleCategory {0} already exists.

Cause: The role category already exists.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04158: RoleCategory {0} does not exists

Cause: The role category does not exist.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04158: RoleCategory {0} does not exists

Cause: The role category does not exist.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04158: RoleCategory {0} does not exists

Cause: The role category does not exist.

Action: Supply a different role category name.
Level: 1

Type: WARNING

Impact: Security

JPS-04159: Role category search value: {0}, is invalid for matcher type: {1}

Cause: The role category search query has invalid parameter value

Action: Modify the search query and supply correct parameter value.
Level: 1

Type: WARNING

Impact: Security

JPS-04159: Role category search value: {0}, is invalid for matcher type: {1}

Cause: The role category search query has invalid parameter value

Action: Modify the search query and supply correct parameter value.
Level: 1

Type: WARNING

Impact: Security

JPS-04159: Role category search value: {0}, is invalid for matcher type: {1}

Cause: The role category search query has invalid parameter value

Action: Modify the search query and supply correct parameter value.
Level: 1

Type: WARNING

Impact: Security

JPS-04160: Cannot find PermissionSet {0} in policy store.

Cause: Could not find PermissionSet in policy store.

Action: Provide the name of a valid PermissionSet.
Level: 1

Type: WARNING

Impact: Security

JPS-04160: Cannot find PermissionSet {0}.

Cause: Could not find PermissionSet in policy store.

Action: Provide the name of a valid PermissionSet.
Level: 1

Type: WARNING

Impact: Security

JPS-04160: Cannot find PermissionSet {0}.

Cause: Could not find PermissionSet in policy store.

Action: Provide the name of a valid PermissionSet.
Level: 1

Type: WARNING

Impact: Security

JPS-04161: Search for PermissionSet {0} by name yielded more than one result.

Cause: Found a duplicate PermissionSet name in search context.

Action: Ensure that all PermissionSet names in the current search context are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04161: Search for PermissionSet {0} by name yielded more than one result.

Cause: Found a duplicate PermissionSet name in search context.

Action: Ensure that all PermissionSet names in the current search context are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04161: Search for PermissionSet {0} by name yielded more than one result.

Cause: Found a duplicate PermissionSet name in search context.

Action: Ensure that all PermissionSet names in the current search context are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04162: PermissionSet "{0}" already exists in policy store.

Cause: Permission Set already exists.

Action: Create a PermissionSet with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04162: PermissionSet {0} already exists in policy store.

Cause: Permission Set already exists.

Action: Create a PermissionSet with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04162: PermissionSet {0} already exists in policy store.

Cause: Permission Set already exists.

Action: Create a PermissionSet with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04163: PermissionSet {0} cannot have empty ResourceActions.

Cause: PermissionSet {0} has empty ResourceActions.

Action: Ensure PermissionSet has ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04163: PermissionSet {0} cannot have empty ResourceActions.

Cause: PermissionSet {0} has empty ResourceActions.

Action: Ensure PermissionSet has ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04163: PermissionSet {0} cannot have empty ResourceActions.

Cause: PermissionSet {0} has empty ResourceActions.

Action: Ensure PermissionSet has ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04164: MemberResource {0} of type {1} not found in application {1}.

Cause: MemberResource {0} of type {1} not found in application {1}.

Action: Ensure the Resource exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04164: Resource {0} referenced by MemberResources not found in application {1}.

Cause: Resource {0} referenced by MemberResources not found in application {1}.

Action: Ensure the Resource exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04164: Resource {0} referenced by MemberResources not found in application {1}.

Cause: Resource {0} referenced by MemberResources not found in application {1}.

Action: Ensure the Resource exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04165: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Cause: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Action: Ensure the ResourceType exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04165: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Cause: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Action: Ensure the ResourceType exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04165: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Cause: ResourceType {0} referenced by MemberResource {1} not found in application {2}.

Action: Ensure the ResourceType exists in the PolicyStore.
Level: 1

Type: WARNING

Impact: Security

JPS-04166: MemberResource {0} of type {1} does not have actions defined.

Cause: MemberResource {0} of type {1} does not have actions defined.

Action: Ensure the MemberResource has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04166: MemberResource {0} of type {1} does not have actions defined.

Cause: MemberResource {0} of type {1} does not have actions defined.

Action: Ensure the MemberResource has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04166: MemberResource {0} of type {1} does not have actions defined.

Cause: MemberResource {0} of type {1} does not have actions defined.

Action: Ensure the MemberResource has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04167: MemberResource {0} of type {1} has actions defined.

Cause: MemberResource {0} of type {1} has actions defined.

Action: Ensure the MemberResource does not have actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04167: MemberResource {0} of type {1} has actions defined.

Cause: MemberResource {0} of type {1} has actions defined.

Action: Ensure the MemberResource does not have actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04167: MemberResource {0} of type {1} has actions defined.

Cause: MemberResource {0} of type {1} has actions defined.

Action: Ensure the MemberResource does not have actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04168: PermissionSet {0} cannot be created without ResourceActions.

Cause: PermissionSet {0} cannot be created without ResourceActions.

Action: Create a PermissionSet with ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04168: PermissionSet {0} cannot be created without ResourceActions.

Cause: PermissionSet {0} cannot be created without ResourceActions.

Action: Create a PermissionSet with ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04168: PermissionSet {0} cannot be created without ResourceActions.

Cause: PermissionSet {0} cannot be created without ResourceActions.

Action: Create a PermissionSet with ResourceActions.
Level: 1

Type: WARNING

Impact: Security

JPS-04169: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Cause: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Action: Modify PermissionSet using a ResourceAction that has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04169: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Cause: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Action: Modify PermissionSet using a ResourceAction that has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04169: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Cause: ResourceAction {0} used to modify PermissionSet {1} has invalid actions for ResourceType {2}.

Action: Modify PermissionSet using a ResourceAction that has valid actions.
Level: 1

Type: WARNING

Impact: Security

JPS-04173: The resource type {0} is not found in store

Cause: Unsupported Resource Type {0}.

Action: Check Resource Type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04173: The resource type {0} is not found in store

Cause: Unsupported Resource Type {0}.

Action: Check Resource Type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04173: The resource type {0} is not found in store

Cause: Unsupported Resource Type {0}.

Action: Check Resource Type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04179: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence

Cause: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence.

Action: Ensure the ResourceType reference exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04179: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence

Cause: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence.

Action: Ensure the ResourceType reference exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04179: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence

Cause: The resource type reference for resource {0} is not found in the application {1}. Hence using the first occurrence.

Action: Ensure the ResourceType reference exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04190: Cannot find resource.

Cause: Could not find resource in the resource store.

Action: Modify your search query.
Level: 1

Type: WARNING

Impact: Security

JPS-04190: Cannot find resource.

Cause: Could not find resource in the resource store.

Action: Modify your search query.
Level: 1

Type: WARNING

Impact: Security

JPS-04190: Cannot find resource.

Cause: Could not find resource in the resource store.

Action: Modify your search query.
Level: 1

Type: WARNING

Impact: Security

JPS-04191: Cannot find unregistered resource finder for resource type "{0}".

Cause: Could not find a registered resource finder for the resource type.

Action: Provide a resource finder implementation for the resource type, and register it with JPS.
Level: 1

Type: WARNING

Impact: Security

JPS-04191: Cannot find unregistered resource finder for resource type "{0}".

Cause: Could not find a registered resource finder for the resource type.

Action: Provide a resource finder implementation for the resource type, and register it with JPS.
Level: 1

Type: WARNING

Impact: Security

JPS-04191: Cannot find unregistered resource finder for resource type "{0}".

Cause: Could not find a registered resource finder for the resource type.

Action: Provide a resource finder implementation for the resource type, and register it with JPS.
Level: 1

Type: WARNING

Impact: Security

JPS-04192: Cannot load resource finder with provider name "{0}".

Cause: Found an incorrect implementation: argumentless public constructor is missing.

Action: Revisit the implementation to provide an argumentless public constructor.
Level: 1

Type: WARNING

Impact: Security

JPS-04192: Cannot load resource finder with provider name "{0}".

Cause: Found an incorrect implementation: argumentless public constructor is missing.

Action: Revisit the implementation to provide an argumentless public constructor.
Level: 1

Type: WARNING

Impact: Security

JPS-04192: Cannot load resource finder with provider name "{0}".

Cause: Found an incorrect implementation: argumentless public constructor is missing.

Action: Revisit the implementation to provide an argumentless public constructor.
Level: 1

Type: WARNING

Impact: Security

JPS-04193: Cannot load resource finder with provider name "{0}" and class "{1}".

Cause: Could not load resource finder class: error encountered while reading a registered class file for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04193: Cannot load resource finder with provider name "{0}" and class "{1}".

Cause: Could not load resource finder class: error encountered while reading a registered class file for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04193: Cannot load resource finder with provider name "{0}" and class "{1}".

Cause: Could not load resource finder class: error encountered while reading a registered class file for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04194: Cannot initialize resource finder with provider name "{0}" and class name "{1}".

Cause: Found an error while initializing a registered class for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04194: Cannot initialize resource finder with provider name "{0}" and class name "{1}".

Cause: Found an error while initializing a registered class for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04194: Cannot initialize resource finder with provider name "{0}" and class name "{1}".

Cause: Found an error while initializing a registered class for resource finder.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04195: Cannot load the resource finder with provider "{0}".

Cause: Found an error in external resource finder configuration: a required property was missing.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04195: Cannot load the resource finder with provider "{0}".

Cause: Found an error in external resource finder configuration: a required property was missing.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04195: Cannot load the resource finder with provider "{0}".

Cause: Found an error in external resource finder configuration: a required property was missing.

Action: Check the configuration of the class property in jps-config.xml.
Level: 1

Type: WARNING

Impact: Security

JPS-04198: Resource {0} in application {1} has a non existent resource type {2}. Ignoring this resource.

Cause: Resource {0} in application {1} has a non existent resource type {2}. Ignoring this resource.

Action: Ensure the ResourceType exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04198: Resource name = {0} in application = {1} has a non existing resource type = {2} ignoring this resource.

Cause: Resource name = {0} in application = {1} has a non existing resource type = {2} ignoring this resource.

Action: Ensure the ResourceType exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04198: Resource name = {0} in application = {1} has a non existing resource type = {2} ignoring this resource.

Cause: Resource name = {0} in application = {1} has a non existing resource type = {2} ignoring this resource.

Action: Ensure the ResourceType exists for every resource.
Level: 1

Type: WARNING

Impact: Security

JPS-04200: Cannot grant policy due to a policy store internal error.

Cause: Encountered a policy store error.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04200: Cannot grant policy due to a policy store internal error.

Cause: Encountered a policy store error.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04200: Cannot grant policy due to a policy store internal error.

Cause: Encountered a policy store error.

Action: Check the error details to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-04201: Cannot grant permission(s). Grant already exists for grantee {0}.

Cause: Permissions already granted to grantee.

Action: Grant a different set of permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-04201: Cannot grant permission(s). Grant already exists for grantee {0}.

Cause: Permissions already granted to grantee.

Action: Grant a different set of permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-04201: Cannot grant permission(s). Grant already exists for grantee {0}.

Cause: Permissions already granted to grantee.

Action: Grant a different set of permissions.
Level: 1

Type: WARNING

Impact: Security

JPS-04202: Cannot revoke policy.

Cause: Encountered an internal policy store error while revoking a policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04202: Cannot revoke policy.

Cause: Encountered an internal policy store error while revoking a policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04202: Cannot revoke policy.

Cause: Encountered an internal policy store error while revoking a policy.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04203: Cannot revoke permission.

Cause: Found that a permission has not been granted.

Action: Provide the appropriate permission to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04203: Cannot revoke permission.

Cause: Found that a permission has not been granted.

Action: Provide the appropriate permission to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04203: Cannot revoke permission.

Cause: Found that a permission has not been granted.

Action: Provide the appropriate permission to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04204: Cannot revoke permissions.

Cause: Found that permissions have not been granted.

Action: Provide the appropriate permissions to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04204: Cannot revoke permissions.

Cause: Found that permissions have not been granted.

Action: Provide the appropriate permissions to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04204: Cannot revoke permissions.

Cause: Found that permissions have not been granted.

Action: Provide the appropriate permissions to the grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04205: Cannot revoke permissions.

Cause: Found that permissions have not been granted to principals.

Action: Provide the appropriate permissions to principals.
Level: 1

Type: WARNING

Impact: Security

JPS-04205: Cannot revoke permissions.

Cause: Found that permissions have not been granted to principals.

Action: Provide the appropriate permissions to principals.
Level: 1

Type: WARNING

Impact: Security

JPS-04205: Cannot revoke permissions.

Cause: Found that permissions have not been granted to principals.

Action: Provide the appropriate permissions to principals.
Level: 1

Type: WARNING

Impact: Security

JPS-04206: Cannot revoke permissions.

Cause: Found that permissions have not been granted to code source.

Action: Correct the code source grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04206: Cannot revoke permissions.

Cause: Found that permissions have not been granted to code source.

Action: Correct the code source grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04206: Cannot revoke permissions.

Cause: Found that permissions have not been granted to code source.

Action: Correct the code source grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04207: Matching Grantee not found: {0}.

Cause: Found that permissions have not been granted to principals or code source.

Action: Correct the list of principals and code source in the grantee, or revoke permissions granted to this grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04207: Matching Grantee not found: {0}.

Cause: Found that permissions have not been granted to principals or code source.

Action: Correct the list of principals and code source in the grantee, or revoke permissions granted to this grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04207: Matching Grantee not found: {0}.

Cause: Found that permissions have not been granted to principals or code source.

Action: Correct the list of principals and code source in the grantee, or revoke permissions granted to this grantee.
Level: 1

Type: WARNING

Impact: Security

JPS-04208: Cannot modify policy due to a policy store internal error.

Cause: Encountered an internal policy store error while modifying the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04208: Cannot modify policy due to a policy store internal error.

Cause: Encountered an internal policy store error while modifying the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04208: Cannot modify policy due to a policy store internal error.

Cause: Encountered an internal policy store error while modifying the policy store.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04209: Cannot modify property {0}.

Cause: Could not modify a property.

Action: Supply the name of a property that can be modified.
Level: 1

Type: WARNING

Impact: Security

JPS-04209: Cannot modify property {0}.

Cause: Could not modify a property.

Action: Supply the name of a property that can be modified.
Level: 1

Type: WARNING

Impact: Security

JPS-04209: Cannot modify property {0}.

Cause: Could not modify a property.

Action: Supply the name of a property that can be modified.
Level: 1

Type: WARNING

Impact: Security

JPS-04210: Modification code {0} is invalid.

Cause: Found an unsupported modification code.

Action: Ensure that the modification code is ADD, REMOVE, or REPLACE.
Level: 1

Type: WARNING

Impact: Security

JPS-04210: Modification code {0} is invalid.

Cause: Found an unsupported modification code.

Action: Ensure that the modification code is ADD, REMOVE, or REPLACE.
Level: 1

Type: WARNING

Impact: Security

JPS-04210: Modification code {0} is invalid.

Cause: Found an unsupported modification code.

Action: Ensure that the modification code is ADD, REMOVE, or REPLACE.
Level: 1

Type: WARNING

Impact: Security

JPS-04211: Cannot query, update, or delete Object with type "{0}" and name "{1}".

Cause: Attempted to query, update, or delete an invalid policy store object.

Action: Ensure that the object to be queried, updated, or deleted belongs to the appropriate policy domain
Level: 1

Type: WARNING

Impact: Security

JPS-04211: Cannot query, update, or delete Object with type "{0}" and name "{1}".

Cause: Attempted to query, update, or delete an invalid policy store object.

Action: Ensure that the object to be queried, updated, or deleted belongs to the appropriate policy domain
Level: 1

Type: WARNING

Impact: Security

JPS-04211: Cannot query, update, or delete Object with type "{0}" and name "{1}".

Cause: Attempted to query, update, or delete an invalid policy store object.

Action: Ensure that the object to be queried, updated, or deleted belongs to the appropriate policy domain
Level: 1

Type: WARNING

Impact: Security

JPS-04212: PermissionSet "{0}" is in use, cannot delete.

Cause: Permission set already existed.

Action: Permission set with the same name cannot be created. Use different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04212: PermissionSet "{0}" is in use, cannot delete.

Cause: Permission set already existed.

Action: Permission set with the same name cannot be created. Use different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04212: PermissionSet "{0}" is in use, cannot delete.

Cause: Permission set already existed.

Action: Permission set with the same name cannot be created. Use different name.
Level: 1

Type: WARNING

Impact: Security

JPS-04213: Cannot modify a grant with an empty permission entry.

Cause: Encountered empty permission entry list while modifying a grant

Action: Pass a non empty permission entry list while modifying a grant
Level: 1

Type: WARNING

Impact: Security

JPS-04213: Cannot modify a grant with an empty permission entry.

Cause: Encountered empty permission entry list while modifying a grant

Action: Pass a non empty permission entry list while modifying a grant
Level: 1

Type: WARNING

Impact: Security

JPS-04213: Cannot modify a grant with an empty permission entry.

Cause: Encountered empty permission entry list while modifying a grant

Action: Pass a non empty permission entry list while modifying a grant
Level: 1

Type: WARNING

Impact: Security

JPS-04216: Cannot grant/revoke permissions because type "{0} " is not known.

Cause: Resource type validation for Permission set failed

Action: Check whether the grant's permission's resourcetype is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04216: Cannot grant/revoke permissions because type "{0} " is not known.

Cause: Resource type validation for Permission set failed

Action: Check whether the grant's permission's resourcetype is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04216: Cannot grant/revoke permissions because type "{0} " is not known.

Cause: Resource type validation for Permission set failed

Action: Check whether the grant's permission's resourcetype is provisioned in the policystore.
Level: 1

Type: WARNING

Impact: Security

JPS-04217: Grant/revoke failed for grantee "{0}", permission class "{1}", resource name "{2}", permission actions "{3}", resource type "{4}". Reason: permission actions is not a subset of resource type actions " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the actions in the Permission are valid actions for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04217: Grant/revoke failed for grantee "{0}", permission class "{1}", resource name "{2}", permission actions "{3}", resource type "{4}". Reason: permission actions is not a subset of resource type actions " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the actions in the Permission are valid actions for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04217: Grant/revoke failed for grantee "{0}", permission class "{1}", resource name "{2}", permission actions "{3}", resource type "{4}". Reason: permission actions is not a subset of resource type actions " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the actions in the Permission are valid actions for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04218: Grant/revoke failed for grantee "{0}", permission class "{1}", resource Name "{2}", permission actions "{3}", resource type "{4}". Reason: permission class is not equal to resource type matcher class " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the matcher class in the Permission is valid for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04218: Grant/revoke failed for grantee "{0}", permission class "{1}", resource Name "{2}", permission actions "{3}", resource type "{4}". Reason: permission class is not equal to resource type matcher class " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the matcher class in the Permission is valid for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04218: Grant/revoke failed for grantee "{0}", permission class "{1}", resource Name "{2}", permission actions "{3}", resource type "{4}". Reason: permission class is not equal to resource type matcher class " {5}".

Cause: Resource type validation for Permission set failed

Action: Check whether the matcher class in the Permission is valid for the resource type provisioned in the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-04219: The action {0} is invalid for resource type {1}.

Cause: The action {0} is invalid for resource type {1}.

Action: Check the ResourceActionsEntry parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04219: The action {0} is invalid for resource type {1}.

Cause: The action {0} is invalid for resource type {1}.

Action: Check the ResourceActionsEntry parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04219: The action {0} is invalid for resource type {1}.

Cause: The action {0} is invalid for resource type {1}.

Action: Check the ResourceActionsEntry parameter.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04220: Cannot search because the search query "{0}" was empty (has no child query).

Cause: The search query {0} was empty (has no child query).

Action: Provide a non-empty search query in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04220: Cannot search because the search query "{0}" was empty (has no child query).

Cause: The search query {0} was empty (has no child query).

Action: Provide a non-empty search query in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04220: Cannot search because the search query "{0}" was empty (has no child query).

Cause: The search query {0} was empty (has no child query).

Action: Provide a non-empty search query in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04221: Cannot search because the grant search query "{0}" has illegal object type for search property "{1}".

Cause: The grant search query {0} has wrong object type in search value for search property {1}.

Action: Provide an object type corresponding to the search property.
Level: 1

Type: WARNING

Impact: Security

JPS-04221: Cannot search because the grant search query "{0}" has illegal object type for search property "{1}".

Cause: The grant search query {0} has wrong object type in search value for search property {1}.

Action: Provide an object type corresponding to the search property.
Level: 1

Type: WARNING

Impact: Security

JPS-04221: Cannot search because the grant search query "{0}" has illegal object type for search property "{1}".

Cause: The grant search query {0} has wrong object type in search value for search property {1}.

Action: Provide an object type corresponding to the search property.
Level: 1

Type: WARNING

Impact: Security

JPS-04222: Cannot search because the search query was null for "{0}" .

Cause: The search query was null for {0} .

Action: Provide a non-null search query .
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04222: Cannot search because the search query was null for "{0}" .

Cause: The search query was null for {0} .

Action: Provide a non-null search query .
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04222: Cannot search because the search query was null for "{0}" .

Cause: The search query was null for {0} .

Action: Provide a non-null search query .
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04223: Access to tenant system policy is not allowed.

Cause: Access to tenant system policy is not allowed.

Action: Access global system policy instead.
Level: 1

Type: WARNING

Impact: Security

JPS-04227: The object name "{0}" is invalid.

Cause: The object name {0} is invalid.

Action: Pass a correct object name in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04227: The object name {0} is invalid.

Cause: The object name {0} is invalid.

Action: Pass a correct object name in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04227: The object name {0} is invalid.

Cause: The object name {0} is invalid.

Action: Pass a correct object name in.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04300: Cannot save policy.

Cause: Could not save policy. Cause {0}.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04300: Cannot save policy.

Cause: Could not save policy. Cause {0}.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04300: Cannot save policy.

Cause: Could not save policy. Cause {0}.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04301: Cannot read from policy store. Reason is {0}, {1}

Cause: Could not read from the policy store.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04301: Cannot read from policy store. Reason is {0}, {1}

Cause: Could not read from the policy store.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04301: Cannot read from policy store. Reason is {0}, {1}

Cause: Could not read from the policy store.

Action: Check the log files and resolve the error.
Level: 1

Type: ERROR

Impact: Security

JPS-04302: Cannot read from policy store.

Cause: Could not find the location property {1} in instance {0}.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04302: Cannot read from policy store.

Cause: Could not find the location property {1} in instance {0}.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04302: Cannot read from policy store.

Cause: Could not find the location property {1} in instance {0}.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04303: Cannot read from policy store.

Cause: Could not find value for system property '{0}' or for location property '{2}' in instance '{1}'.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04303: Cannot read from policy store.

Cause: Could not find value for system property '{0}' or for location property '{2}' in instance '{1}'.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04303: Cannot read from policy store.

Cause: Could not find value for system property '{0}' or for location property '{2}' in instance '{1}'.

Action: Ensure the location is set to a valid policy store file.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04304: Policy store instance descriptor {0}, location value {1} is ignored.

Cause: Could not find value for the system property '{0}', which overrides the descriptor property {1} in the policy store service instance.

Action: Unset the system property so that the location is picked up from configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-04304: Policy store instance descriptor {0}, location value {1} is ignored.

Cause: Could not find value for the system property '{0}', which overrides the descriptor property {1} in the policy store service instance.

Action: Unset the system property so that the location is picked up from configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-04304: Policy store instance descriptor {0}, location value {1} is ignored.

Cause: Could not find value for the system property '{0}', which overrides the descriptor property {1} in the policy store service instance.

Action: Unset the system property so that the location is picked up from configuration in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-04305: Could not determine the work folder for controlled and mixed mode PD.

Cause: Could not determine the work folder for controlled and mixed mode PD.

Action: Ensure system property "oracle.security.jps.config" or "domain.home" is set and jps-config.xml is present under ${domain.home}/config/fmwconfig.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04410: Cannot create JACC module policy context "{0}" for application {1}.

Cause: Could not create application policy because found two application module contexts with identical names.

Action: Ensure that all application module context names are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04410: Cannot create JACC module policy context "{0}" for application {1}.

Cause: Could not create application policy because found two application module contexts with identical names.

Action: Ensure that all application module context names are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04410: Cannot create JACC module policy context "{0}" for application {1}.

Cause: Could not create application policy because found two application module contexts with identical names.

Action: Ensure that all application module context names are distinct.
Level: 1

Type: WARNING

Impact: Security

JPS-04411: Cannot create application "{0}" JACC module policy context "{1}".

Cause: Could not create application module policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04411: Cannot create application "{0}" JACC module policy context "{1}".

Cause: Could not create application module policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04411: Cannot create application "{0}" JACC module policy context "{1}".

Cause: Could not create application module policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04412: Cannot delete JACC module "{0}".

Cause: Could not find JACC policy context to delete.

Action: Check the JACC policy context name.
Level: 1

Type: WARNING

Impact: Security

JPS-04412: Cannot delete JACC module "{0}".

Cause: Could not find JACC policy context to delete.

Action: Check the JACC policy context name.
Level: 1

Type: WARNING

Impact: Security

JPS-04412: Cannot delete JACC module "{0}".

Cause: Could not find JACC policy context to delete.

Action: Check the JACC policy context name.
Level: 1

Type: WARNING

Impact: Security

JPS-04413: Cannot delete JACC module policy context "{0}".

Cause: Could not delete JACC policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04413: Cannot delete JACC module policy context "{0}".

Cause: Could not delete JACC policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04413: Cannot delete JACC module policy context "{0}".

Cause: Could not delete JACC policy; persist operation failed.

Action: Refer to the base exception in log files and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-04420: Application policy context name is missing from application role {0}.

Cause: Could not find application policy context in the application role principal.

Action: Ensure that the application role principal has an application context.
Level: 1

Type: WARNING

Impact: Security

JPS-04420: Application policy context name is missing from application role {0}.

Cause: Could not find application policy context in the application role principal.

Action: Ensure that the application role principal has an application context.
Level: 1

Type: WARNING

Impact: Security

JPS-04420: Application policy context name is missing from application role {0}.

Cause: Could not find application policy context in the application role principal.

Action: Ensure that the application role principal has an application context.
Level: 1

Type: WARNING

Impact: Security

JPS-04421: Administrator role name is invalid.

Cause: Found an invalid administrator role name.

Action: Correct the name of the administrator role.
Level: 1

Type: WARNING

Impact: Security

JPS-04421: Administrator role name is invalid.

Cause: Found an invalid administrator role name.

Action: Correct the name of the administrator role.
Level: 1

Type: WARNING

Impact: Security

JPS-04421: Administrator role name is invalid.

Cause: Found an invalid administrator role name.

Action: Correct the name of the administrator role.
Level: 1

Type: WARNING

Impact: Security

JPS-04422: Policy is malformed.

Cause: Found system policy that granted permissions to application role(s).

Action: Grants to application roles are not allowed in a system policy. Remove such grants.
Level: 1

Type: WARNING

Impact: Security

JPS-04422: Policy is malformed.

Cause: Found system policy that granted permissions to application role(s).

Action: Grants to application roles are not allowed in a system policy. Remove such grants.
Level: 1

Type: WARNING

Impact: Security

JPS-04422: Policy is malformed.

Cause: Found system policy that granted permissions to application role(s).

Action: Grants to application roles are not allowed in a system policy. Remove such grants.
Level: 1

Type: WARNING

Impact: Security

JPS-04423: Application role name "{0}" is invalid.

Cause: Found invalid application role name {0}.

Action: Verify that the application role name conforms with the role name syntax.
Level: 1

Type: WARNING

Impact: Security

JPS-04423: Application role name "{0}" is invalid.

Cause: Found invalid application role name {0}.

Action: Verify that the application role name conforms with the role name syntax.
Level: 1

Type: WARNING

Impact: Security

JPS-04423: Application role name "{0}" is invalid.

Cause: Found invalid application role name {0}.

Action: Verify that the application role name conforms with the role name syntax.
Level: 1

Type: WARNING

Impact: Security

JPS-04502: Java SSO Login

Cause: This was JSSO page title.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04502: Java SSO Login

Cause: This was JSSO page title.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04502: Java SSO Login

Cause: This was JSSO page title.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04503: Enter your single sign-on username and password.

Cause: User name and password were required for logging into JSSO.

Action: Enter a valid user name and password.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04503: Enter your single sign-on username and password.

Cause: User name and password were required for logging into JSSO.

Action: Enter a valid user name and password.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04503: Enter your single sign-on username and password.

Cause: User name and password were required for logging into JSSO.

Action: Enter a valid user name and password.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04504: Username

Cause: This was JSSO login user name.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04504: Username

Cause: This was JSSO login user name.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04504: Username

Cause: This was JSSO login user name.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04505: Password

Cause: This was JSSO login user password.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04505: Password

Cause: This was JSSO login user password.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04505: Password

Cause: This was JSSO login user password.

Action: No action needed.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04506: Login

Cause: Submit button.

Action: Press submit.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04506: Login

Cause: Submit button.

Action: Press submit.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04506: Login

Cause: Submit button.

Action: Press submit.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04507: Cancel

Cause: Cancel button.

Action: Press cancel to abort login.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04507: Cancel

Cause: Cancel button.

Action: Press cancel to abort login.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04507: Cancel

Cause: Cancel button.

Action: Press cancel to abort login.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04508: Failed.

Cause: JSSO login failed.

Action: Check user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04508: Failed.

Cause: JSSO login failed.

Action: Check user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04508: Failed.

Cause: JSSO login failed.

Action: Check user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04509: The maximum number of login attempts is exceeded. Contact the application administrator, or retry after {0} minutes.

Cause: Maximum login attempts was exceeded.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04509: The maximum number of login attempts is exceeded. Contact the application administrator, or retry after {0} minutes.

Cause: Maximum login attempts was exceeded.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04509: The maximum number of login attempts is exceeded. Contact the application administrator, or retry after {0} minutes.

Cause: Maximum login attempts was exceeded.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04510: Incorrect username or password.

Cause: User name or password was invalid.

Action: Check the user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04510: Incorrect username or password.

Cause: User name or password was invalid.

Action: Check the user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04510: Incorrect username or password.

Cause: User name or password was invalid.

Action: Check the user name and password used for login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04511: Java SSO Application Error.

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04511: Java SSO Application Error.

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04511: Java SSO Application Error.

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04512: application error

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04512: application error

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04512: application error

Cause: Encountered and internal error.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04513: The Java SSO application is not properly configured.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04513: The Java SSO application is not properly configured.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04513: The Java SSO application is not properly configured.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04514: Configuration error: {0}.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04514: Configuration error: {0}.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04514: Configuration error: {0}.

Cause: The Java SSO application was not correctly configured.

Action: Reconfigure the application.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04515: Usage arguments:

Cause: Defines the keytool usage.

Action: See error message.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04515: Usage arguments:

Cause: Defines the keytool usage.

Action: See error message.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04515: Usage arguments:

Cause: Defines the keytool usage.

Action: See error message.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04516: No key type for algorithm.

Cause: The algorithm key type was not specified.

Action: Configure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04516: No key type for algorithm.

Cause: The algorithm key type was not specified.

Action: Configure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04516: No key type for algorithm.

Cause: The algorithm key type was not specified.

Action: Configure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04517: Key does not match any known algorithm.

Cause: The given key did not match the corresponding algorithm.

Action: Reconfigure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04517: Key does not match any known algorithm.

Cause: The given key did not match the corresponding algorithm.

Action: Reconfigure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04517: Key does not match any known algorithm.

Cause: The given key did not match the corresponding algorithm.

Action: Reconfigure the algorithm key type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04518: The number of JSSO cookies is zero or invalid.

Cause: Could not find JSSO cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04518: The number of JSSO cookies is zero or invalid.

Cause: Could not find JSSO cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04518: The number of JSSO cookies is zero or invalid.

Cause: Could not find JSSO cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04519: The number of Oracle Access Manager cookies is zero or invalid.

Cause: Could not find Oracle Access Manager cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04519: The number of Oracle Access Manager cookies is zero or invalid.

Cause: Could not find Oracle Access Manager cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04519: The number of Oracle Access Manager cookies is zero or invalid.

Cause: Could not find Oracle Access Manager cookie in header.

Action: Login again or contact the system administrator.
Level: 1

Type: TRACE

Impact: Requests/Responses

JPS-04520: Token type is invalid: expected type is COOKIE_TOKEN, but found {0}.

Cause: The token type configured was invalid: it should be COOKIE_TOKEN.

Action: Reconfigure the token type to a valid value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04520: Token type is invalid: expected type is COOKIE_TOKEN, but found {0}.

Cause: The token type configured was invalid: it should be COOKIE_TOKEN.

Action: Reconfigure the token type to a valid value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04520: Token type is invalid: expected type is COOKIE_TOKEN, but found {0}.

Cause: The token type configured was invalid: it should be COOKIE_TOKEN.

Action: Reconfigure the token type to a valid value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04521: The JSSO property {0} is not set.

Cause: JSSO property was not correctly configured.

Action: Reconfigure the property to a correct value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04521: The JSSO property {0} is not set.

Cause: JSSO property was not correctly configured.

Action: Reconfigure the property to a correct value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04521: The JSSO property {0} is not set.

Cause: JSSO property was not correctly configured.

Action: Reconfigure the property to a correct value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04522: The authentication type {0} is invalid.

Cause: JSSO did not support this authentication type.

Action: Reconfigure the type to a supported type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04522: The authentication type {0} is invalid.

Cause: JSSO did not support this authentication type.

Action: Reconfigure the type to a supported type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04522: The authentication type {0} is invalid.

Cause: JSSO did not support this authentication type.

Action: Reconfigure the type to a supported type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04523: Token is no longer valid.

Cause: The incoming token was no longer valid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04523: Token is no longer valid.

Cause: The incoming token was no longer valid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04523: Token is no longer valid.

Cause: The incoming token was no longer valid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04524: Cannot create token from JSSO cookie.

Cause: Could not create token from the JSSO cookie; cookie may have expired.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04524: Cannot create token from JSSO cookie.

Cause: Could not create token from the JSSO cookie; cookie may have expired.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04524: Cannot create token from JSSO cookie.

Cause: Could not create token from the JSSO cookie; cookie may have expired.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04525: The number of cookies is zero or the invalid number {0}.

Cause: Could not find at least one cookie in the request.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04525: The number of cookies is zero or the invalid number {0}.

Cause: Could not find at least one cookie in the request.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04525: The number of cookies is zero or the invalid number {0}.

Cause: Could not find at least one cookie in the request.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04526: Token has invalid version number.

Cause: Token had invalid version number.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04526: Token has invalid version number.

Cause: Token had invalid version number.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04526: Token has invalid version number.

Cause: Token had invalid version number.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04527: Token has an invalid format.

Cause: Token was corrupted or had invalid format.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04527: Token has an invalid format.

Cause: Token was corrupted or had invalid format.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04527: Token has an invalid format.

Cause: Token was corrupted or had invalid format.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04528: An error occurred while encoding JSSO token.

Cause: Could not encode JSSO token.

Action: Specify a valid, supported encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04528: An error occurred while encoding JSSO token.

Cause: Could not encode JSSO token.

Action: Specify a valid, supported encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04528: An error occurred while encoding JSSO token.

Cause: Could not encode JSSO token.

Action: Specify a valid, supported encoding.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04529: Cannot verify signature in the JSSO token.

Cause: Could not verify signature: the token was tampered with, or the signature algorithm was invalid.

Action: Specify a supported signature algorithm.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04529: Cannot verify signature in the JSSO token.

Cause: Could not verify signature: the token was tampered with, or the signature algorithm was invalid.

Action: Specify a supported signature algorithm.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04529: Cannot verify signature in the JSSO token.

Cause: Could not verify signature: the token was tampered with, or the signature algorithm was invalid.

Action: Specify a supported signature algorithm.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04530: Algorithm is unsupported.

Cause: Specified algorithm was unsupported.

Action: Check documentation for the list of supported algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04530: Algorithm is unsupported.

Cause: Specified algorithm was unsupported.

Action: Check documentation for the list of supported algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04530: Algorithm is unsupported.

Cause: Specified algorithm was unsupported.

Action: Check documentation for the list of supported algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04531: Error creating cipher.

Cause: Could not create cipher.

Action: Check documentation for the list of supported cipher algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04531: Error creating cipher.

Cause: Could not create cipher.

Action: Check documentation for the list of supported cipher algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04531: Error creating cipher.

Cause: Could not create cipher.

Action: Check documentation for the list of supported cipher algorithms.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04532: JSSO logout URL is not configured.

Cause: The logout URL was not configured or invalid.

Action: Check the logout URL configuration properties, and reconfigure it to a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04532: JSSO logout URL is not configured.

Cause: The logout URL was not configured or invalid.

Action: Check the logout URL configuration properties, and reconfigure it to a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04532: JSSO logout URL is not configured.

Cause: The logout URL was not configured or invalid.

Action: Check the logout URL configuration properties, and reconfigure it to a valid URL.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04533: JSSO has encountered an unexpected error.

Cause: An internal error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04533: JSSO has encountered an unexpected error.

Cause: An internal error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04533: JSSO has encountered an unexpected error.

Cause: An internal error occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04534: JSSO symmetric key is missing.

Cause: The symmetric key configuration was missing.

Action: Ensure that the properties "custom.sso.cred.key" and "custom.sso.cred.alias" are configured in the service instance, and that the symmetric key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04534: JSSO symmetric key is missing.

Cause: The symmetric key configuration was missing.

Action: Ensure that the properties "custom.sso.cred.key" and "custom.sso.cred.alias" are configured in the service instance, and that the symmetric key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04534: JSSO symmetric key is missing.

Cause: The symmetric key configuration was missing.

Action: Ensure that the properties "custom.sso.cred.key" and "custom.sso.cred.alias" are configured in the service instance, and that the symmetric key is present in the credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04535: Identity name is invalid.

Cause: User identity was invalid or missing.

Action: Provide a valid user identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04535: Identity name is invalid.

Cause: User identity was invalid or missing.

Action: Provide a valid user identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04535: Identity name is invalid.

Cause: User identity was invalid or missing.

Action: Provide a valid user identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04536: The token name {0} is missing in request object.

Cause: Token name was missing in the request object.

Action: Ensure that the token name is present in the request object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04536: The token name {0} is missing in request object.

Cause: Token name was missing in the request object.

Action: Ensure that the token name is present in the request object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04536: The token name {0} is missing in request object.

Cause: Token name was missing in the request object.

Action: Ensure that the token name is present in the request object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04537: No token name is specified for token collector {0}.

Cause: Token collector was invalid or missing.

Action: Configure a valid token collector with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04537: No token name is specified for token collector {0}.

Cause: Token collector was invalid or missing.

Action: Configure a valid token collector with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04537: No token name is specified for token collector {0}.

Cause: Token collector was invalid or missing.

Action: Configure a valid token collector with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04538: The request object class is invalid.

Cause: The request object class was invalid.

Action: Ensure that the request object is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04538: The request object class is invalid.

Cause: The request object class was invalid.

Action: Ensure that the request object is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04538: The request object class is invalid.

Cause: The request object class was invalid.

Action: Ensure that the request object is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04539: Token collector is not properly initialized.

Cause: Could not initialize the token collector.

Action: Ensure that the token collector is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04539: Token collector is not properly initialized.

Cause: Could not initialize the token collector.

Action: Ensure that the token collector is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04539: Token collector is not properly initialized.

Cause: Could not initialize the token collector.

Action: Ensure that the token collector is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04540: The token asserter is not properly initialized.

Cause: Could not initialize the token asserter.

Action: Ensure that the token asserter is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04540: The token asserter is not properly initialized.

Cause: Could not initialize the token asserter.

Action: Ensure that the token asserter is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04540: The token asserter is not properly initialized.

Cause: Could not initialize the token asserter.

Action: Ensure that the token asserter is correctly configured and initialized.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04541: Cannot find authenticated identity.

Cause: Authentication failed.

Action: Provide a valid identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04541: Cannot find authenticated identity.

Cause: Authentication failed.

Action: Provide a valid identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04541: Cannot find authenticated identity.

Cause: Authentication failed.

Action: Provide a valid identity.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04542: The token collector class {0} is not properly configured in the configuration file.

Cause: Token collector class was missing.

Action: Configure a valid token collector class with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04542: The token collector class {0} is not properly configured in the configuration file.

Cause: Token collector class was missing.

Action: Configure a valid token collector class with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04542: The token collector class {0} is not properly configured in the configuration file.

Cause: Token collector class was missing.

Action: Configure a valid token collector class with the property "idm.token.collector.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04543: No login module is configured for application.

Cause: Could not find configured login module.

Action: Configure a login module in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04543: No login module is configured for application.

Cause: Could not find configured login module.

Action: Configure a login module in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04543: No login module is configured for application.

Cause: Could not find configured login module.

Action: Configure a login module in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04544: The subject of the identity is invalid.

Cause: Subject was missing.

Action: Ensure that the valid Subject is present.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04544: The subject of the identity is invalid.

Cause: Subject was missing.

Action: Ensure that the valid Subject is present.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04544: The subject of the identity is invalid.

Cause: Subject was missing.

Action: Ensure that the valid Subject is present.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04545: Cannot verify the Subject {0}.

Cause: Could not verify Subject.

Action: Check the user credentials.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04545: Cannot verify the Subject {0}.

Cause: Could not verify Subject.

Action: Check the user credentials.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04545: Cannot verify the Subject {0}.

Cause: Could not verify Subject.

Action: Check the user credentials.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04546: The configuration (idm.subject.loginmodule.disabled=true) specifies that the Subject is populated by the token asserter.

Cause: Could not find Subject asserter.

Action: Configure an asserter to use a login module that returns a valid Subject.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04546: The configuration (idm.subject.loginmodule.disabled=true) specifies that the Subject is populated by the token asserter.

Cause: Could not find Subject asserter.

Action: Configure an asserter to use a login module that returns a valid Subject.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04546: The configuration (idm.subject.loginmodule.disabled=true) specifies that the Subject is populated by the token asserter.

Cause: Could not find Subject asserter.

Action: Configure an asserter to use a login module that returns a valid Subject.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04547: The token type {0} is not properly configured in the configuration file.

Cause: Could not find token type configuration.

Action: Configure a token type in the service instance with the property "idm.token.type property".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04547: The token type {0} is not properly configured in the configuration file.

Cause: Could not find token type configuration.

Action: Configure a token type in the service instance with the property "idm.token.type property".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04547: The token type {0} is not properly configured in the configuration file.

Cause: Could not find token type configuration.

Action: Configure a token type in the service instance with the property "idm.token.type property".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04548: The token asserter class {0} is not properly configured in the configuration file.

Cause: Could not find token asserter class configuration.

Action: Configure a token asseter class in the service instance with the property "idm.token.asserter.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04548: The token asserter class {0} is not properly configured in the configuration file.

Cause: Could not find token asserter class configuration.

Action: Configure a token asseter class in the service instance with the property "idm.token.asserter.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04548: The token asserter class {0} is not properly configured in the configuration file.

Cause: Could not find token asserter class configuration.

Action: Configure a token asseter class in the service instance with the property "idm.token.asserter.class".
Level: 1

Type: ERROR

Impact: Configuration

JPS-04549: Token is no longer valid.

Cause: Found invalid or expired token.

Action: Check that the token is valid and has not expired.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04549: Token is no longer valid.

Cause: Found invalid or expired token.

Action: Check that the token is valid and has not expired.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04549: Token is no longer valid.

Cause: Found invalid or expired token.

Action: Check that the token is valid and has not expired.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04550: Token type is invalid: expected type is HEADER_TOKEN, but found {0}.

Cause: Token type was invalid: it should be HEADER_TOKEN.

Action: Reconfigure the token type to a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04550: Token type is invalid: expected type is HEADER_TOKEN, but found {0}.

Cause: Token type was invalid: it should be HEADER_TOKEN.

Action: Reconfigure the token type to a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04550: Token type is invalid: expected type is HEADER_TOKEN, but found {0}.

Cause: Token type was invalid: it should be HEADER_TOKEN.

Action: Reconfigure the token type to a valid type.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04551: The number of OSSO headers is zero or an invalid number.

Cause: Could not find OSSO header in HTTP request.

Action: Login again, or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04551: The number of OSSO headers is zero or an invalid number.

Cause: Could not find OSSO header in HTTP request.

Action: Login again, or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04551: The number of OSSO headers is zero or an invalid number.

Cause: Could not find OSSO header in HTTP request.

Action: Login again, or contact the system administrator.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04552: The required Oracle Access Manager property {0} is missing or invalid.

Cause: A required Oracle Access Manager property was missing or invalid.

Action: Configure the property "access.sdk.install.path" in the service instance in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04552: The required Oracle Access Manager property {0} is missing or invalid.

Cause: A required Oracle Access Manager property was missing or invalid.

Action: Configure the property "access.sdk.install.path" in the service instance in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04552: The required Oracle Access Manager property {0} is missing or invalid.

Cause: A required Oracle Access Manager property was missing or invalid.

Action: Configure the property "access.sdk.install.path" in the service instance in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04553: The user identity {0} for Oracle Access Manager is invalid.

Cause: The user identity for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04553: The user identity {0} for Oracle Access Manager is invalid.

Cause: The user identity for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04553: The user identity {0} for Oracle Access Manager is invalid.

Cause: The user identity for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04554: The user password for Oracle Access Manager is invalid.

Cause: The user password for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04554: The user password for Oracle Access Manager is invalid.

Cause: The user password for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04554: The user password for Oracle Access Manager is invalid.

Cause: The user password for Oracle Access Manager was invalid.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04555: The user {0} is not logged in to Oracle Access Manager. The error is {1}.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04555: The user {0} is not logged in to Oracle Access Manager. The error is {1}.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04555: The user {0} is not logged in to Oracle Access Manager. The error is {1}.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04556: The user {0} is not authorized to access a resource type authentication in Oracle Access Manager.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04556: The user {0} is not authorized to access a resource type authentication in Oracle Access Manager.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04556: The user {0} is not authorized to access a resource type authentication in Oracle Access Manager.

Cause: The user was not logged in Oracle Access Manager.

Action: Login again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04557: Invalid parameter {0} supplied. Cannot be null or empty.

Cause: Invalid parameter {0} supplied. Cannot be null or empty.

Action: Ensure the parameter is not null or empty.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04557: Invalid parameter {0} supplied. Cannot be null or empty.

Cause: Invalid parameter {0} supplied. Cannot be null or empty.

Action: Ensure the parameter is not null or empty.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04557: Invalid parameter {0} supplied. Cannot be null or empty.

Cause: Invalid parameter {0} supplied. Cannot be null or empty.

Action: Ensure the parameter is not null or empty.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04558: The SSO service is not properly configured: {0}.

Cause: The SSO service is not properly configured: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04558: The SSO service is not properly configured: {0}.

Cause: The SSO service is not properly configured: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04558: The SSO service is not properly configured: {0}.

Cause: The SSO service is not properly configured: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-04559: Failed to create the {0} token. Cause: {1}.

Cause: Failed to create the {0} token. Cause: {1}.

Action: Re-login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04559: Failed to create the {0} token. Cause: {1}.

Cause: Failed to create the {0} token. Cause: {1}.

Action: Re-login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04559: Failed to create the {0} token. Cause: {1}.

Cause: Failed to create the {0} token. Cause: {1}.

Action: Re-login.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04560: SSO provider cannot initiate SSO process: {0}.

Cause: SSO provider cannot initiate SSO process: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04560: SSO provider cannot initiate SSO process: {0}.

Cause: SSO provider cannot initiate SSO process: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04560: SSO provider cannot initiate SSO process: {0}.

Cause: SSO provider cannot initiate SSO process: {0}.

Action: Check the SSO Service configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-04561: Invalid parameter {0} supplied. Cannot be null.

Cause: Invalid parameter {0} supplied. Cannot be null.

Action: Ensure the parameter is not null.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04561: Invalid parameter {0} supplied. Cannot be null.

Cause: Invalid parameter {0} supplied. Cannot be null.

Action: Ensure the parameter is not null.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04561: Invalid parameter {0} supplied. Cannot be null.

Cause: Invalid parameter {0} supplied. Cannot be null.

Action: Ensure the parameter is not null.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-04601: Cannot obtain audit service for policy store.

Cause: Could not query audit service about audit logging level for policy store messages.

Action: Ensure that auditing is configured correctly.
Level: 1

Type: WARNING

Impact: Security

JPS-04601: Cannot obtain audit service for policy store.

Cause: Could not query audit service about audit logging level for policy store messages.

Action: Ensure that auditing is configured correctly.
Level: 1

Type: WARNING

Impact: Security

JPS-04601: Cannot obtain audit service for policy store.

Cause: Could not query audit service about audit logging level for policy store messages.

Action: Ensure that auditing is configured correctly.
Level: 1

Type: WARNING

Impact: Security

JPS-04602: Cannot log policy management event to the audit service.

Cause: Could not log policy management audit messages to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-04602: Cannot log policy management event to the audit service.

Cause: Could not log policy management audit messages to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-04602: Cannot log policy management event to the audit service.

Cause: Could not log policy management audit messages to the audit service.

Action: Ensure that auditing is configured correctly in your environment and application.
Level: 1

Type: WARNING

Impact: Security

JPS-05500: Cannot create the user manager MBean.

Cause: Could not create the user manager MBean.

Action: Check errors in log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05500: Cannot create the user manager MBean.

Cause: Could not create the user manager MBean.

Action: Check errors in log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05500: Cannot create the user manager MBean.

Cause: Could not create the user manager MBean.

Action: Check errors in log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05501: Cannot create the role manager MBean.

Cause: Could not create the role manager MBean.

Action: Check the log files for errors and contact domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05501: Cannot create the role manager MBean.

Cause: Could not create the role manager MBean.

Action: Check the log files for errors and contact domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05501: Cannot create the role manager MBean.

Cause: Could not create the role manager MBean.

Action: Check the log files for errors and contact domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05502: Cannot create the identity store MBean.

Cause: Could not create the identity store MBean.

Action: Check log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05502: Cannot create the identity store MBean.

Cause: Could not create the identity store MBean.

Action: Check log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05502: Cannot create the identity store MBean.

Cause: Could not create the identity store MBean.

Action: Check log files and contact the domain administrator.
Level: 1

Type: ERROR

Impact: Configuration

JPS-05513: Failed to determine realms to migrate file {0}. Reason {1}.

Cause: Failed determine realms to migrate file {0}. Reason {1}.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-05513: Failed to determine realms to migrate file {0}. Reason {1}.

Cause: Failed determine realms to migrate file {0}. Reason {1}.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-05513: Failed to determine realms to migrate file {0}. Reason {1}.

Cause: Failed determine realms to migrate file {0}. Reason {1}.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-05521: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Cause: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Action: Use a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-05521: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Cause: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Action: Use a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-05521: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Cause: Invalid jaas.login.controlFlag {0} found for {1} service instance. Valid values should be {2}.

Action: Use a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-05542: Bootstrap credential store context missing

Cause: Could not find bootstrap credstore context

Action: Contact aystem administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05542: Bootstrap credential store context missing

Cause: Could not find bootstrap credstore context

Action: Contact aystem administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05542: Bootstrap credential store context missing

Cause: Could not find bootstrap credstore context

Action: Contact aystem administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05546: Bootstrap credential store service missing

Cause: Could not find bootstrap credstore service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05546: Bootstrap credential store service missing

Cause: Could not find bootstrap credstore service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05546: Bootstrap credential store service missing

Cause: Could not find bootstrap credstore service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05626: Bootstrap credential already present in store

Cause: Credential already present in the store

Action: use different map name or key name for the credential
Level: 1

Type: WARNING

Impact: Compliance

JPS-05626: Bootstrap credential already present in store

Cause: Credential already present in the store

Action: use different map name or key name for the credential
Level: 1

Type: WARNING

Impact: Compliance

JPS-05626: Bootstrap credential already present in store

Cause: Credential already present in the store

Action: use different map name or key name for the credential
Level: 1

Type: WARNING

Impact: Compliance

JPS-05657: Bootstrap credential store context {0} missing

Cause: Could not find bootstrap credential store context

Action: Contact aystem administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05658: Bootstrap credential store service {0} missing from bootstrap credential store context {1}

Cause: Could not find bootstrap credential store service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-05659: location attribute missing from bootstrap credential store service {0}

Cause: Could not find location attribute of bootstrap credential store service

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06000: The source context {0} is missing in jps configuration file.

Cause: While migrating a security store, found that the context, specified as source {0}, did not exist in jps-config.xml.

Action: Provide a context for source that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06000: The source context {0} is missing in jps-config.xml.

Cause: While migrating a security store, found that the context, specified as source {0}, did not exist in jps-config.xml.

Action: Provide a context for source that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06000: The source context {0} is missing in jps-config.xml.

Cause: While migrating a security store, found that the context, specified as source {0}, did not exist in jps-config.xml.

Action: Provide a context for source that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06001: The destination context {0} is missing in jps configuration file.

Cause: While migration of a security store, found that the context, specified as destination {0}, did not exist in jps-config.xml.

Action: Provide a context for destination that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06001: The destination context {0} is missing in jps-config.xml.

Cause: While migration of a security store, found that the context, specified as destination {0}, did not exist in jps-config.xml.

Action: Provide a context for destination that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06001: The destination context {0} is missing in jps-config.xml.

Cause: While migration of a security store, found that the context, specified as destination {0}, did not exist in jps-config.xml.

Action: Provide a context for destination that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06002: Cannot clean the destination credential store. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06002: Cannot clean the destination credential store. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06002: Cannot clean the destination credential store. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06003: Cannot migrate credential folder/key {0}/{1}.Reason {2}.

Cause: Cannot migrate this credential.

Action: Verify that the credential is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06003: Cannot migrate credential folder/key {0}/{1}.Reason {2}.

Cause: Cannot migrate this credential.

Action: Verify that the credential is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06003: Cannot migrate credential folder/key {0}/{1}.Reason {2}.

Cause: Cannot migrate this credential.

Action: Verify that the credential is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06004: Cannot migrate an unknown user. Reason {0}.

Cause: Cannot migrate this user.

Action: Verify that the user is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06004: Cannot migrate an unknown user. Reason {0}.

Cause: Cannot migrate this user.

Action: Verify that the user is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06004: Cannot migrate an unknown user. Reason {0}.

Cause: Cannot migrate this user.

Action: Verify that the user is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06005: Cannot get password of user {0}. Reason {1}.

Cause: Cannot get this user password.

Action: Verify that the password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06005: Cannot get password of user {0}. Reason {1}.

Cause: Cannot get this user password.

Action: Verify that the password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06005: Cannot get password of user {0}. Reason {1}.

Cause: Cannot get this user password.

Action: Verify that the password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06006: Cannot migrate user {0}. Reason {1}.

Cause: Cannot migrate this user name.

Action: Verify that the user name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06006: Cannot migrate user {0}. Reason {1}.

Cause: Cannot migrate this user name.

Action: Verify that the user name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06006: Cannot migrate user {0}. Reason {1}.

Cause: Cannot migrate this user name.

Action: Verify that the user name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06007: Cannot migrate an unknown role. Reason {0}.

Cause: Cannot migrate this role.

Action: Verify that the role is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06007: Cannot migrate an unknown role. Reason {0}.

Cause: Cannot migrate this role.

Action: Verify that the role is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06007: Cannot migrate an unknown role. Reason {0}.

Cause: Cannot migrate this role.

Action: Verify that the role is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06008: Cannot migrate role {0}. Reason {1}.

Cause: Cannot migrate this role name.

Action: Verify that the role name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06008: Cannot migrate role {0}. Reason {1}.

Cause: Cannot migrate this role name.

Action: Verify that the role name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06008: Cannot migrate role {0}. Reason {1}.

Cause: Cannot migrate this role name.

Action: Verify that the role name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06009: Cannot migrate any member of role {0}. Reason {1}.

Cause: Cannot migrate members.

Action: Verify that the members are correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06009: Cannot migrate any member of role {0}. Reason {1}.

Cause: Cannot migrate members.

Action: Verify that the members are correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06009: Cannot migrate any member of role {0}. Reason {1}.

Cause: Cannot migrate members.

Action: Verify that the members are correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06010: Cannot migrate an unknown member of role {0}. Reason {1}.

Cause: Cannot migrate this member.

Action: Verify that the member is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06010: Cannot migrate an unknown member of role {0}. Reason {1}.

Cause: Cannot migrate this member.

Action: Verify that the member is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06010: Cannot migrate an unknown member of role {0}. Reason {1}.

Cause: Cannot migrate this member.

Action: Verify that the member is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06011: Cannot migrate member {0} of role: {1}. Reason {2}.

Cause: Cannot migrate this member name.

Action: Verify that the member name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06011: Cannot migrate member {0} of role: {1}. Reason {2}.

Cause: Cannot migrate this member name.

Action: Verify that the member name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06011: Cannot migrate member {0} of role: {1}. Reason {2}.

Cause: Cannot migrate this member name.

Action: Verify that the member name is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06012: Cannot migrate a global grant. Reason {0}.

Cause: Could not migrate a global grant. Reason {0}.

Action: Verify that the grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06012: cannot migrate a global grant. Reason {0}.

Cause: Could not migrate a global grant. Reason {0}.

Action: Verify that the grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06012: cannot migrate a global grant. Reason {0}.

Cause: Could not migrate a global grant. Reason {0}.

Action: Verify that the grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06013: Cannot migrate an application grant. Reason {0}.

Cause: Could not migrate an application grant. Reason {0}.

Action: Verify that the application grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06013: cannot migrate an application grant. Reason {0}.

Cause: Could not migrate an application grant. Reason {0}.

Action: Verify that the application grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06013: cannot migrate an application grant. Reason {0}.

Cause: Could not migrate an application grant. Reason {0}.

Action: Verify that the application grant is correctly specified.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06014: Cannot migrate an indirect password for {0}. Reason {1}.

Cause: Could not migrate an indirect password due to an exception.

Action: Verify that the indirect password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06014: Cannot migrate an indirect password for {0}. Reason {1}.

Cause: Could not migrate an indirect password due to an exception.

Action: Verify that the indirect password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06014: Cannot migrate an indirect password for {0}. Reason {1}.

Cause: Could not migrate an indirect password due to an exception.

Action: Verify that the indirect password is correctly specified.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06015: Cannot migrate an indirect password for {0} because the specified realm is null.

Cause: Could not migrate an indirect password because the given realm was null.

Action: Provide a non-null realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06015: Cannot migrate an indirect password for {0} because the specified realm is null.

Cause: Could not migrate an indirect password because the given realm was null.

Action: Provide a non-null realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06015: Cannot migrate an indirect password for {0} because the specified realm is null.

Cause: Could not migrate an indirect password because the given realm was null.

Action: Provide a non-null realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06016: Cannot migrate an indirect password for {0} because the specified user name is null.

Cause: Could not migrate an indirect password because the given user name was null.

Action: Provide a non-null user name.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06016: Cannot migrate an indirect password for {0} because the specified user name is null.

Cause: Could not migrate an indirect password because the given user name was null.

Action: Provide a non-null user name.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06016: Cannot migrate an indirect password for {0} because the specified user name is null.

Cause: Could not migrate an indirect password because the given user name was null.

Action: Provide a non-null user name.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06017: Cannot migrate an indirect password for {0} because the specified realm does not exist.

Cause: Could not migrate an indirect password because the input realm does not exist.

Action: Provide an existing realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06017: Cannot migrate an indirect password for {0} because the specified realm does not exist.

Cause: Could not migrate an indirect password because the input realm does not exist.

Action: Provide an existing realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06017: Cannot migrate an indirect password for {0} because the specified realm does not exist.

Cause: Could not migrate an indirect password because the input realm does not exist.

Action: Provide an existing realm.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06018: Cannot migrate an indirect password for {0} because the specified user does not exist.

Cause: Could not migrate an indirect password because the input user does not exist.

Action: Provide an existing user.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06018: Cannot migrate an indirect password for {0} because the specified user does not exist.

Cause: Could not migrate an indirect password because the input user does not exist.

Action: Provide an existing user.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06018: Cannot migrate an indirect password for {0} because the specified user does not exist.

Cause: Could not migrate an indirect password because the input user does not exist.

Action: Provide an existing user.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06019: The identity store associated with context {0} is missing in jps-config.xml.

Cause: While migration of a policy store, found that the context, specified as containing the associated identity store {0}, did not exist in jps-config.xml.

Action: Provide a context to associate identity store that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06019: The identity store associated with context {0} is missing in jps-config.xml.

Cause: While migration of a policy store, found that the context, specified as containing the associated identity store {0}, did not exist in jps-config.xml.

Action: Provide a context to associate identity store that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06019: The identity store associated with context {0} is missing in jps-config.xml.

Cause: While migration of a policy store, found that the context, specified as containing the associated identity store {0}, did not exist in jps-config.xml.

Action: Provide a context to associate identity store that is present in jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06020: The principal class {0} specified in the source policy store cannot be loaded. Reason {1}.

Cause: Could not load a class. Reason {0}.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06020: The principal class {0} specified in the source policy store cannot be loaded. Reason {1}.

Cause: Could not load a class. Reason {0}.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06020: The principal class {0} specified in the source policy store cannot be loaded. Reason {1}.

Cause: Could not load a class. Reason {0}.

Action: Ensure the class is in the class path.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06021: Cannot migrate the credentials in the folder {0}. Reason: {1}.

Cause: Cannot migrate the credentials in this folder.

Action: Check the folder in the source credential store.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06021: Cannot migrate the credentials in the folder {0}. Reason: {1}.

Cause: Cannot migrate the credentials in this folder.

Action: Check the folder in the source credential store.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06021: Cannot migrate the credentials in the folder {0}. Reason: {1}.

Cause: Cannot migrate the credentials in this folder.

Action: Check the folder in the source credential store.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06022: Cannot determine the folder to be migrated.

Cause: The credential store has more than one folder and the folder to be migrated was not defined.

Action: Specify the folder to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06022: Cannot determine the folder to be migrated.

Cause: The credential store has more than one folder and the folder to be migrated was not defined.

Action: Specify the folder to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06022: Cannot determine the folder to be migrated.

Cause: The credential store has more than one folder and the folder to be migrated was not defined.

Action: Specify the folder to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06023: The input file {0} specified for migration or upgrade is not valid.

Cause: The file {0} was non-readable, empty, or did not exist.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06023: The input file {0} specified for migration or upgrade is not valid.

Cause: The file {0} was non-readable, empty, or did not exist.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06023: The input file {0} specified for migration or upgrade is not valid.

Cause: The file {0} was non-readable, empty, or did not exist.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06024: Cannot initialize the destination identity store.

Cause: One or more required configuration properties were not be properly defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06024: Cannot initialize the destination identity store.

Cause: One or more required configuration properties were not be properly defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06024: Cannot initialize the destination identity store.

Cause: One or more required configuration properties were not be properly defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06025: There are undefined credential properties for the destination identity store.

Cause: One or more required configuration properties for credentials were not defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06025: There are undefined credential properties for the destination identity store.

Cause: One or more required configuration properties for credentials were not defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06025: There are undefined credential properties for the destination identity store.

Cause: One or more required configuration properties for credentials were not defined.

Action: Check the configuration of the destination identity store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06026: Cannot get credentials for the destination identity store from the domain credential store.

Cause: Credentials were not found in the domain credential store.

Action: Ensure that the domain credential store has the appropriate credentials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06026: Cannot get credentials for the destination identity store from the domain credential store.

Cause: Credentials were not found in the domain credential store.

Action: Ensure that the domain credential store has the appropriate credentials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06026: Cannot get credentials for the destination identity store from the domain credential store.

Cause: Credentials were not found in the domain credential store.

Action: Ensure that the domain credential store has the appropriate credentials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06027: Cannot migrate the specified realm.

Cause: The specified realm was not found in the source store.

Action: Specify a valid realm name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06027: Cannot migrate the specified realm.

Cause: The specified realm was not found in the source store.

Action: Specify a valid realm name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06027: Cannot migrate the specified realm.

Cause: The specified realm was not found in the source store.

Action: Specify a valid realm name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06028: The required identity store property {0} required for migration is undefined.

Cause: A property required for migration was not configured in the identity store.

Action: Specify the missing configuration property.
Level: 1

Type: ERROR

Impact: Other

JPS-06028: The required identity store property {0} required for migration is undefined.

Cause: A property required for migration was not configured in the identity store.

Action: Specify the missing configuration property.
Level: 1

Type: ERROR

Impact: Other

JPS-06028: The required identity store property {0} required for migration is undefined.

Cause: A property required for migration was not configured in the identity store.

Action: Specify the missing configuration property.
Level: 1

Type: ERROR

Impact: Other

JPS-06029: JAZN properties cannot be read from config file {0}.

Cause: JAZN properties could not be read from config file {0}.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06029: JAZN properties cannot be read from config file {0}.

Cause: JAZN properties could not be read from config file {0}.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06029: JAZN properties cannot be read from config file {0}.

Cause: JAZN properties could not be read from config file {0}.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06030: The required JAZN property {0} could not be read.

Cause: A required JAZN property {0} could not be read.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06030: The required JAZN property {0} could not be read.

Cause: A required JAZN property {0} could not be read.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06030: The required JAZN property {0} could not be read.

Cause: A required JAZN property {0} could not be read.

Action: Check the configuration file and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06031: No application is configured in the source policy store.

Cause: No application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06031: No application is configured in the source policy store.

Cause: No application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06031: No application is configured in the source policy store.

Cause: No application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06032: Unable to determine the application policy to migrate.

Cause: More than one application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06032: Unable to determine the application policy to migrate.

Cause: More than one application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06032: Unable to determine the application policy to migrate.

Cause: More than one application was configured in the source policy store.

Action: Check the source policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06033: The source credential store contains no credentials.

Cause: The requested credential was not found in the credential store.

Action: Ensure that the credential store has the requested credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06033: The source credential store contains no credentials.

Cause: The requested credential was not found in the credential store.

Action: Ensure that the credential store has the requested credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06033: The source credential store contains no credentials.

Cause: The requested credential was not found in the credential store.

Action: Ensure that the credential store has the requested credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06034: The folder {0} is missing in the credential store.

Cause: The requested map name was not found in the credential store.

Action: Ensure that the credential store contains the requested map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06034: The folder {0} is missing in the credential store.

Cause: The requested map name was not found in the credential store.

Action: Ensure that the credential store contains the requested map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06034: The folder {0} is missing in the credential store.

Cause: The requested map name was not found in the credential store.

Action: Ensure that the credential store contains the requested map name.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06035: The destination file {0} already exists; the existing LDIF file will not be appended or overwritten.

Cause: The destination file is already present.

Action: Delete the destination file, or provide the name of a non-existing file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06035: The destination file {0} already exists; the existing LDIF file will not be appended or overwritten.

Cause: The destination file is already present.

Action: Delete the destination file, or provide the name of a non-existing file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06035: The destination file {0} already exists; the existing LDIF file will not be appended or overwritten.

Cause: The destination file is already present.

Action: Delete the destination file, or provide the name of a non-existing file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06036: Cannot determine the default realm to migrate file {0}. Reason {1}.

Cause: An internal error occurred while determining the default realm.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06036: Cannot determine the default realm to migrate file {0}. Reason {1}.

Cause: An internal error occurred while determining the default realm.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06036: Cannot determine the default realm to migrate file {0}. Reason {1}.

Cause: An internal error occurred while determining the default realm.

Action: Check log files and try again.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06037: Cannot initialize the source credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06037: Cannot initialize the source credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06037: Cannot initialize the source credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06038: Cannot initialize the destination credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06038: Cannot initialize the destination credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06038: Cannot initialize the destination credential store.

Cause: The configuration for the credential store was invalid.

Action: Verify that the credential store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06039: Cannot migrate property {0} of user {1}. Reason {2}.

Cause: Cannot migrate property {0} for user {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06039: Cannot migrate property {0} of user {1}. Reason {2}.

Cause: Cannot migrate property {0} for user {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06039: Cannot migrate property {0} of user {1}. Reason {2}.

Cause: Cannot migrate property {0} for user {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06040: Cannot migrate property {0} of role {1}. Reason {2}.

Cause: Cannot migrate property {0} for role {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06040: Cannot migrate property {0} of role {1}. Reason {2}.

Cause: Cannot migrate property {0} for role {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06040: Cannot migrate property {0} of role {1}. Reason {2}.

Cause: Cannot migrate property {0} for role {1}. Reason {2}.

Action: Check the log files and retry migrating.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06041: The switch or keyword " {0} " is not applicable to " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06041: The switch or keyword " {0} " is not applicable to " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06041: The switch or keyword " {0} " is not applicable to " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06042: Invalid scope for migration.

Cause: Value of scope keyword was invalid.

Action: Enter only one of the defined values/alias of scope as a value for the keyword scope.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06042: Invalid scope for migration.

Cause: Value of scope keyword was invalid.

Action: Enter only one of the defined values/alias of scope as a value for the keyword scope.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06042: Invalid scope for migration.

Cause: Value of scope keyword was invalid.

Action: Enter only one of the defined values/alias of scope as a value for the keyword scope.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06043: The source application is undefined but required to migrate application-specific policies.

Cause: Optional keyword srcApp was not defined.

Action: Specify, in the parameter srcApp, the value of the application whose policies are to be migrated.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06043: The source application is undefined but required to migrate application-specific policies.

Cause: Optional keyword srcApp was not defined.

Action: Specify, in the parameter srcApp, the value of the application whose policies are to be migrated.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06043: The source application is undefined but required to migrate application-specific policies.

Cause: Optional keyword srcApp was not defined.

Action: Specify, in the parameter srcApp, the value of the application whose policies are to be migrated.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06044: Cannot create the temporary file {0}.

Cause: Could not write the XML file.

Action: Check permissions or disk space in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06044: Cannot create the temporary file {0}.

Cause: Could not write the XML file.

Action: Check permissions or disk space in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06044: Cannot create the temporary file {0}.

Cause: Could not write the XML file.

Action: Check permissions or disk space in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06045: Cannot parse the file {0}.

Cause: Could not parse the XML file.

Action: Check that the file is present in the java.io.tmpdir directory, and that it contains well-formed XML.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06045: Cannot parse the file {0}.

Cause: Could not parse the XML file.

Action: Check that the file is present in the java.io.tmpdir directory, and that it contains well-formed XML.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06045: Cannot parse the file {0}.

Cause: Could not parse the XML file.

Action: Check that the file is present in the java.io.tmpdir directory, and that it contains well-formed XML.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06046: Cannot delete the file {0}.

Cause: The temp file could not be deleted.

Action: Check that the file is not being accessed by other applications.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06046: Cannot delete the file {0}.

Cause: The temp file could not be deleted.

Action: Check that the file is not being accessed by other applications.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06046: Cannot delete the file {0}.

Cause: The temp file could not be deleted.

Action: Check that the file is not being accessed by other applications.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06047: Cannot migrate user credentials of user {0}.

Cause: The source identity store was configured not to give cleartext password.

Action: Configure the source identity store to obfuscate password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06047: Cannot migrate user credentials of user {0}.

Cause: The source identity store was configured not to give cleartext password.

Action: Configure the source identity store to obfuscate password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06047: Cannot migrate user credentials of user {0}.

Cause: The source identity store was configured not to give cleartext password.

Action: Configure the source identity store to obfuscate password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06048: Null values passed in for username or application stripes.

Cause: The user name or the application stripe was null.

Action: The user name must not be null. The list of application names must be null if only global policies are to be extracted.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06048: Null values passed in for username or application stripes.

Cause: The user name or the application stripe was null.

Action: The user name must not be null. The list of application names must be null if only global policies are to be extracted.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06048: Null values passed in for username or application stripes.

Cause: The user name or the application stripe was null.

Action: The user name must not be null. The list of application names must be null if only global policies are to be extracted.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06049: Application list is empty. Only global policies will be extracted.

Cause: The list of applications was empty.

Action: Only global policies are collected.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

JPS-06049: Application list is empty. Only global policies will be extracted.

Cause: The list of applications was empty.

Action: Only global policies are collected.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

JPS-06049: Application list is empty. Only global policies will be extracted.

Cause: The list of applications was empty.

Action: Only global policies are collected.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

JPS-06050: file {0} was not found

Cause: The xml file was not found.

Action: Check if the file is present in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06050: file {0} was not found

Cause: The xml file was not found.

Action: Check if the file is present in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06050: file {0} was not found

Cause: The xml file was not found.

Action: Check if the file is present in the java.io.tmpdir directory.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06051: Processing of privilege roles is supported only when migrating an XML Policy store to an LDAP Policy Store.

Cause: Processing of privilege roles was supported only when migrating an XML policy store to an LDAP policy store.

Action: Make sure that the source store is XML-based and the destination store is LDAP-based.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06051: Processing of privilege roles is supported only when migrating an XML Policy store to an LDAP Policy Store.

Cause: Processing of privilege roles was supported only when migrating an XML policy store to an LDAP policy store.

Action: Make sure that the source store is XML-based and the destination store is LDAP-based.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06051: Processing of privilege roles is supported only when migrating an XML Policy store to an LDAP Policy Store.

Cause: Processing of privilege roles was supported only when migrating an XML policy store to an LDAP policy store.

Action: Make sure that the source store is XML-based and the destination store is LDAP-based.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06052: Error while processing a PermissionSet grant.

Cause: Error encountered while processing permissionSet grant.

Action: Check log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06052: Error while processing a PermissionSet grant.

Cause: Error encountered while processing permissionSet grant.

Action: Check log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06052: Error while processing a PermissionSet grant.

Cause: Error encountered while processing permissionSet grant.

Action: Check log files for details.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06053: Processing privilege roles failed. Cause {0}

Cause: The processing of privilege roles failed.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06053: Processing privilege roles failed. Cause {0}

Cause: The processing of privilege roles failed.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06053: Processing privilege roles failed. Cause {0}

Cause: The processing of privilege roles failed.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06054: Error in creating resourceTypes in destination store. Cause {0}

Cause: Error encountered while creating resourceTypes in destination store.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06054: Error in creating resourceTypes in destination store. Cause {0}

Cause: Error encountered while creating resourceTypes in destination store.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06054: Error in creating resourceTypes in destination store. Cause {0}

Cause: Error encountered while creating resourceTypes in destination store.

Action: Check log files for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06055: Location of the ldif file containing resourceType definitions cannot be null.

Cause: Location of the LDIF file containing resourceType definitions was null or not found.

Action: Provide the absolute path for the resource file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06055: Location of the ldif file containing resourceType definitions cannot be null.

Cause: Location of the LDIF file containing resourceType definitions was null or not found.

Action: Provide the absolute path for the resource file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06055: Location of the ldif file containing resourceType definitions cannot be null.

Cause: Location of the LDIF file containing resourceType definitions was null or not found.

Action: Provide the absolute path for the resource file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06056: Error while reading resource type file {0}.

Cause: Error encountered while reading the resource type file {0}.

Action: Ensure that the file exists and that it has the expected format.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06056: Error while reading resource type file {0}.

Cause: Error encountered while reading the resource type file {0}.

Action: Ensure that the file exists and that it has the expected format.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06056: Error while reading resource type file {0}.

Cause: Error encountered while reading the resource type file {0}.

Action: Ensure that the file exists and that it has the expected format.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06057: Resource type name or matcher class cannot be null.

Cause: Resource type name or matcher class was null.

Action: Provide a valid name and matcher class for the resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06057: Resource type name or matcher class cannot be null.

Cause: Resource type name or matcher class was null.

Action: Provide a valid name and matcher class for the resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06057: Resource type name or matcher class cannot be null.

Cause: Resource type name or matcher class was null.

Action: Provide a valid name and matcher class for the resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06058: Permission class {0} with more than one matching resource type found.

Cause: Permission class had more than one matching resource type.

Action: Ensure that the a permission class has just one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06058: Permission class {0} with more than one matching resource type found.

Cause: Permission class had more than one matching resource type.

Action: Ensure that the a permission class has just one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06058: Permission class {0} with more than one matching resource type found.

Cause: Permission class had more than one matching resource type.

Action: Ensure that the a permission class has just one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06059: A grant entry containing {0} as one of principals has multiple principal entries. This entry cannot be processed.

Cause: A grant for a privilege role had multiple principals.

Action: Ensure that the privilege role grant has a single principal.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06059: A grant entry containing {0} as one of principals has multiple principal entries. This entry cannot be processed.

Cause: A grant for a privilege role had multiple principals.

Action: Ensure that the privilege role grant has a single principal.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06059: A grant entry containing {0} as one of principals has multiple principal entries. This entry cannot be processed.

Cause: A grant for a privilege role had multiple principals.

Action: Ensure that the privilege role grant has a single principal.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06060: The resource type definition file is missing.

Cause: The resource type definition file was not found.

Action: Provide the absolute path location for the resource definition file in LDIF format when using the option procPrivOption.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06060: The resource type definition file is missing.

Cause: The resource type definition file was not found.

Action: Provide the absolute path location for the resource definition file in LDIF format when using the option procPrivOption.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06060: The resource type definition file is missing.

Cause: The resource type definition file was not found.

Action: Provide the absolute path location for the resource definition file in LDIF format when using the option procPrivOption.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06061: The switch or keyword " {0} " is not defined for " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06061: The switch or keyword " {0} " is not defined for " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06061: The switch or keyword " {0} " is not defined for " {1} = {2} ".

Cause: One or more optional switches or keywords were invalid.

Action: Refer to the command documentation for the correct usage.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06062: Application role {0} corresponding to a member application role not defined.

Cause: Application role not defined.

Action: Check logs for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06062: Application role {0} corresponding to a member application role not defined.

Cause: Application role not defined.

Action: Check logs for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06062: Application role {0} corresponding to a member application role not defined.

Cause: Application role not defined.

Action: Check logs for detials.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06063: No Matching resource type definition found for permission class {0}.

Cause: Permission class representing resource granted to a privilleged role does not have corresponding resource type definition.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06063: No Matching resource type definition found for permission class {0}.

Cause: Permission class representing resource granted to a privilleged role does not have corresponding resource type definition.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06063: No Matching resource type definition found for permission class {0}.

Cause: Permission class representing resource granted to a privilleged role does not have corresponding resource type definition.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06064: Error getting the application role {0} from the source policy store

Cause: The application role was either not present or defined multiple times.

Action: Check the source policy store and make sure that the application role is uniquely defined.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06064: Error getting the application role {0} from the source policy store

Cause: The application role was either not present or defined multiple times.

Action: Check the source policy store and make sure that the application role is uniquely defined.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06064: Error getting the application role {0} from the source policy store

Cause: The application role was either not present or defined multiple times.

Action: Check the source policy store and make sure that the application role is uniquely defined.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06065: Report generation failed

Cause: .

Action: .
Level: 1

Type: ERROR

Impact: Configuration

JPS-06065: Report generation failed

Cause: .

Action: .
Level: 1

Type: ERROR

Impact: Configuration

JPS-06065: Report generation failed

Cause: .

Action: .
Level: 1

Type: ERROR

Impact: Configuration

JPS-06066: Invalid value for mode: {0}.

Cause: Invalid value for mode: {0}.

Action: Make sure the value for mode is valid
Level: 1

Type: ERROR

Impact: Security

JPS-06066: Invalid value for mode.

Cause: Invalid value for mode

Action: Make sure the value for mode is valid
Level: 1

Type: ERROR

Impact: Security

JPS-06066: Invalid value for mode.

Cause: Invalid value for mode

Action: Make sure the value for mode is valid
Level: 1

Type: ERROR

Impact: Security

JPS-06067: {0} config file either not found or not a valid file.

Cause: {0} config file either not found or not a valid file

Action: Make sure to provide a valid config file
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06067: {0} config file either not found or not a valid file.

Cause: {0} config file either not found or not a valid file

Action: Make sure to provide a valid config file
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06067: {0} config file either not found or not a valid file.

Cause: {0} config file either not found or not a valid file

Action: Make sure to provide a valid config file
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06068: Unable to read configurations from jazn config file : {0}.

Cause: Unable to read configurations from jazn data file : {0}.

Action: Check the jazn data file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06068: Unable to read configurations from jazn config file : {0}.

Cause: Unable to read configurations from jazn data file : {0}.

Action: Check the jazn data file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06068: Unable to read configurations from jazn config file : {0}.

Cause: Unable to read configurations from jazn data file : {0}.

Action: Check the jazn data file.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06069: Provider referred from jazn config file {0} is of type XML and not LDAP.

Cause: Provider referred from jps-config file {0} is of type XML and not LDAP.

Action: Refer to a provider of type LDAP.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06069: Provider referred from jazn config file {0} is of type XML and not LDAP.

Cause: Provider referred from jps-config file {0} is of type XML and not LDAP.

Action: Refer to a provider of type LDAP.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06069: Provider referred from jazn config file {0} is of type XML and not LDAP.

Cause: Provider referred from jps-config file {0} is of type XML and not LDAP.

Action: Refer to a provider of type LDAP.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06070: Unable to read policies from policy store.

Cause: Unable to read policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06070: Unable to read policies from policy store.

Cause: Unable to read policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06070: Unable to read policies from policy store.

Cause: Unable to read policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06071: Unable to read global policies from policy store.

Cause: Unable to read global policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06071: Unable to read global policies from policy store.

Cause: Unable to read global policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06071: Unable to read global policies from policy store.

Cause: Unable to read global policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06072: Unable to read permissions for grantee {0} from policy store.

Cause: Unable to read permissions for grantee {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06072: Unable to read permissions for grantee {0} from policy store.

Cause: Unable to read permissions for grantee {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06072: Unable to read permissions for grantee {0} from policy store.

Cause: Unable to read permissions for grantee {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06073: Unable to read realm policies from policy store.

Cause: Unable to read realm policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06073: Unable to read realm policies from policy store.

Cause: Unable to read realm policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06073: Unable to read realm policies from policy store.

Cause: Unable to read realm policies from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06074: Unable to read realm policies from realm {0} from policy store.

Cause: Unable to read realm policies from realm {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06074: Unable to read realm policies from realm {0} from policy store.

Cause: Unable to read realm policies from realm {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06074: Unable to read realm policies from realm {0} from policy store.

Cause: Unable to read realm policies from realm {0} from policy store.

Action: Check the policy store.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06075: Unsupported resource type file format. Use either an ldif file or a jazn-data with only resource type definitions.

Cause: Unsupported resource type file format.

Action: Use either an ldif file or a jazn-data with only resource type definitions.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06075: Unsupported resource type file format. Use either an ldif file or a jazn-data with only resource type definitions.

Cause: Unsupported resource type file format.

Action: Use either an ldif file or a jazn-data with only resource type definitions.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06075: Unsupported resource type file format. Use either an ldif file or a jazn-data with only resource type definitions.

Cause: Unsupported resource type file format.

Action: Use either an ldif file or a jazn-data with only resource type definitions.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06076: A Resource Type referred by {0} is expected to have a matching class {1} but has {2}.

Cause: A Resource Type referred by a Permission is expected to have the same matching class as defined in the Permission

Action: Make sure a permission class has one matching resource type with the same class name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06076: A Resource Type referred by {0} is expected to have a matching class {1} but has {2}.

Cause: A Resource Type referred by a Permission is expected to have the same matching class as defined in the Permission

Action: Make sure a permission class has one matching resource type with the same class name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06076: A Resource Type referred by {0} is expected to have a matching class {1} but has {2}.

Cause: A Resource Type referred by a Permission is expected to have the same matching class as defined in the Permission

Action: Make sure a permission class has one matching resource type with the same class name.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06077: A Resource Type referred by {0} is not defined.

Cause: A Resource Type referred by a Permission is not defined.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06077: A Resource Type referred by {0} is not defined.

Cause: A Resource Type referred by a Permission is not defined.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06077: A Resource Type referred by {0} is not defined.

Cause: A Resource Type referred by a Permission is not defined.

Action: Make sure a permission class has one matching resource type.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06078: Cannot migrate keystore/stripe {0}/{1}.Reason {2}.

Cause: Cannot migrate the keystore in this stripe.

Action: Check the keystore and stripe in the source keystore service.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06078: Cannot migrate keystore/stripe {0}/{1}.Reason {2}.

Cause: Cannot migrate the keystore in this stripe.

Action: Check the keystore and stripe in the source keystore service.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06078: Cannot migrate keystore/stripe {0}/{1}.Reason {2}.

Cause: Cannot migrate the keystore in this stripe.

Action: Check the keystore and stripe in the source keystore service.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06079: Cannot determine the stripe to be migrated.

Cause: The keystore service has more than one stripes and the stripe to be migrated was not defined.

Action: Specify the stripe to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06079: Cannot determine the stripe to be migrated.

Cause: The keystore service has more than one stripes and the stripe to be migrated was not defined.

Action: Specify the stripe to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06079: Cannot determine the stripe to be migrated.

Cause: The keystore service has more than one stripes and the stripe to be migrated was not defined.

Action: Specify the stripe to be migrated.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06080: The source keystore service contains no keystore within the given application stripe.

Cause: The requested keystore was not found in the keystore service.

Action: Ensure that the keystore service has the requested keystore.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06080: The source keystore service contains no keystore within the given application stripe.

Cause: The requested keystore was not found in the keystore service.

Action: Ensure that the keystore service has the requested keystore.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06080: The source keystore service contains no keystore within the given application stripe.

Cause: The requested keystore was not found in the keystore service.

Action: Ensure that the keystore service has the requested keystore.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06082: Cannot initialize the source keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06082: Cannot initialize the source keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06082: Cannot initialize the source keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06083: Cannot initialize the destination keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06083: Cannot initialize the destination keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06083: Cannot initialize the destination keystore service.

Cause: The configuration for the keystore service was invalid.

Action: Verify that the keystore service configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06084: Cannot clean the destination keystore service. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06084: Cannot clean the destination keystore service. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06084: Cannot clean the destination keystore service. Reason {0}.

Cause: A codebase grant was found without the required permissions.

Action: Set the right permissions to the codebase grant.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06085: Resource types not defined for the application {0}.

Cause: Resource Types not found for the application {0}.

Action: Define the resource types for the application {0}.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06085: Resource types not defined for the application {0}.

Cause: Resource Types not found for the application {0}.

Action: Define the resource types for the application {0}.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06085: Resource types not defined for the application {0}.

Cause: Resource Types not found for the application {0}.

Action: Define the resource types for the application {0}.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06086: Cannot upgrade policies for application {0}.

Cause: Exception during policy upgradation.

Action: Check the Causing exception and fix the error.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06086: Cannot upgrade policies for application {0}.

Cause: Exception during policy upgradation.

Action: Check the Causing exception and fix the error.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06086: Cannot upgrade policies for application {0}.

Cause: Exception during policy upgradation.

Action: Check the Causing exception and fix the error.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06087: Duplicate permissions: {0} present in grant in source.

Cause: Duplicate permissions are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06087: Duplicate permissions: {0} present in grant in source.

Cause: Duplicate permissions are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06087: Duplicate permissions: {0} present in grant in source.

Cause: Duplicate permissions are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06088: Duplicates principals:{0} present in grant in source.

Cause: Duplicates principals are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06088: Duplicates principals:{0} present in grant in source.

Cause: Duplicates principals are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06088: Duplicates principals:{0} present in grant in source.

Cause: Duplicates principals are present in a grant in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06089: Duplicate grant {0} present in source.

Cause: Duplicate grants are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06089: Duplicate grant {0} present in source.

Cause: Duplicate grants are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06089: Duplicate grant {0} present in source.

Cause: Duplicate grants are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06090: Duplicate app-role {0} present in source.

Cause: Duplicate app-roles are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06090: Duplicate app-role {0} present in source.

Cause: Duplicate app-roles are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06090: Duplicate app-role {0} present in source.

Cause: Duplicate app-roles are present in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06091: Duplicate member {0} present in an app-role in source.

Cause: Duplicate members are present in an app-role in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06091: Duplicate member {0} present in an app-role in source.

Cause: Duplicate members are present in an app-role in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06091: Duplicate member {0} present in an app-role in source.

Cause: Duplicate members are present in an app-role in source.

Action: See error message.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06092: Can not overwrite global policy.

Cause: Can not overwrite global policy.

Action: Do not set overwrite to true
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06100: Policy Store version {0} and Oracle Platform Security Services Version {1} are not compatible.

Cause: The policy store version and the version of Oracle Platform Security Services does not match

Action: Upgrade your binaries or your policy store.
Level: 1

Type: ERROR

Impact: Security

JPS-06100: Policy Store version {0} and Oracle Platform Security Services Version {1} are not compatible.

Cause: The policy store version and the version of Oracle Platform Security Services does not match

Action: Upgrade your binaries or your policy store.
Level: 1

Type: ERROR

Impact: Security

JPS-06100: Policy Store version {0} and Oracle Platform Security Services Version {1} are not compatible.

Cause: The policy store version and the version of Oracle Platform Security Services does not match

Action: Upgrade your binaries or your policy store.
Level: 1

Type: ERROR

Impact: Security

JPS-06101: Cannot initialize the source auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06101: Cannot initialize the source auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06101: Cannot initialize the source auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06102: Cannot initialize the destination auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06102: Cannot initialize the destination auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06102: Cannot initialize the destination auditstore service.

Cause: The configuration for the audit store was invalid.

Action: Verify that the audit store configuration is correct and try again.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06103: Default Admin Role {0} not found in the policy domain {1} in the destination policy store

Cause: The destination policy store may not conform to leates version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06103: Default Admin Role {0} not found in the policy domain {1} in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06103: Default Admin Role {0} not found in the policy domain {1} in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06104: Default Admin Role {0} not found in the application {1} in the destination policy store

Cause: The destination policy store may not conform to leates version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06104: Default Admin Role {0} not found in the application {1} in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06104: Default Admin Role {0} not found in the application {1} in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06105: Default system Admin Role {0} not found in the destination policy store

Cause: The destination policy store may not conform to leates version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06105: Default system Admin Role {0} not found in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06105: Default system Admin Role {0} not found in the destination policy store

Cause: The destination policy store may not conform to latest version and need to be upgraded

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-06106: Instantiation of bootstrap credential store specified in file {0} failed. Reason {1}

Cause: The configuration provided is not valid.

Action: Provide a valid configuration file which has configuration for bootstrap credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06106: Instantiation of bootstrap credential store specified in file {0} failed. Reason {1}

Cause: The configuration provided is not valid.

Action: Provide a valid configuration file which has configuration for bootstrap credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06106: Instantiation of bootstrap credential store specified in file {0} failed. Reason {1}

Cause: The configuration provided is not valid.

Action: Provide a valid configuration file which has configuration for bootstrap credential.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06107: Instantiation of credential store at path {0} failed. Reason: {1}

Cause: An underlying exception prevented initialization of credentials file.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06107: Instantiation of credential store at path {0} failed. Reason: {1}

Cause: An underlying exception prevented initialization of credentials file.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06107: Instantiation of credential store at path {0} failed. Reason: {1}

Cause: An underlying exception prevented initialization of credentials file.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06108: Import/Export of keys failed. Reason: {0}

Cause: An underlying exception prevented exporting/importing of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06108: Import/Export of keys failed. Reason: {0}

Cause: An underlying exception prevented exporting/importing of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06108: Import/Export of keys failed. Reason: {0}

Cause: An underlying exception prevented exporting/importing of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06109: Cannot read key from key file in Directory {0}. Reason {1}.

Cause: An underlying exception prevented reading of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06109: Cannot read key from key file in Directory {0}. Reason {1}.

Cause: An underlying exception prevented reading of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06109: Cannot read key from key file in Directory {0}. Reason {1}.

Cause: An underlying exception prevented reading of key.

Action: Check the cause of the exception and fix it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06110: Key file Directory {0} does not have write permissions.

Cause: Key file directory not writable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06110: Key file Directory {0} does not have write permissions.

Cause: Key file directory not writable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06110: Key file Directory {0} does not have write permissions.

Cause: Key file directory not writable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06111: Key file Directory {0} does not have read permissions.

Cause: Key file directory is not readable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06111: Key file Directory {0} does not have read permissions.

Cause: Key file directory is not readable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06111: Key file Directory {0} does not have read permissions.

Cause: Key file directory is not readable.

Action: Change the permissions of the directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06112: Key file Directory {0} does not exist.

Cause: The path specified either donnot exist or is not a directory.

Action: Provide a valid directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06112: Key file Directory {0} does not exist.

Cause: The path specified either donnot exist or is not a directory.

Action: Provide a valid directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06112: Key file Directory {0} does not exist.

Cause: The path specified either donnot exist or is not a directory.

Action: Provide a valid directory.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06113: Configuration file {0} is not valid. It is either not present or does not have read permissions.}

Cause: The file is either not present or is not readable.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06113: Configuration file {0} is not valid. It is either not present or does not have read permissions.}

Cause: The file is either not present or is not readable.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06113: Configuration file {0} is not valid. It is either not present or does not have read permissions.}

Cause: The file is either not present or is not readable.

Action: Provide a valid file.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06114: Key is not present in the key file in Directory {0}.

Cause: Export might have not completed successfully.

Action: Provide key file that has key in it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06114: Key is not present in the key file in Directory {0}.

Cause: Export might have not completed successfully.

Action: Provide key file that has key in it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06114: Key is not present in the key file in Directory {0}.

Cause: Export might have not completed successfully.

Action: Provide key file that has key in it.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06115: Empty DB username information. Please make sure to provide the correct jdbcUser info.

Cause: Empty DB username information.

Action: Please make sure to provide the correct jdbcUser info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06115: Empty DB username information. Please make sure to provide the correct jdbcUser info.

Cause: Empty DB username information.

Action: Please make sure to provide the correct jdbcUser info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06115: Empty DB username information. Please make sure to provide the correct jdbcUser info.

Cause: Empty DB username information.

Action: Please make sure to provide the correct jdbcUser info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06116: Empty DB password information. Please make sure to provide the correct jdbcPassword info.

Cause: Empty DB password information.

Action: Please make sure to provide the correct jdbcPassword info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06116: Empty DB password information. Please make sure to provide the correct jdbcPassword info.

Cause: Empty DB password information.

Action: Please make sure to provide the correct jdbcPassword info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06116: Empty DB password information. Please make sure to provide the correct jdbcPassword info.

Cause: Empty DB password information.

Action: Please make sure to provide the correct jdbcPassword info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06117: Empty JDBC host and port information. Please make sure to provide the correct jdbcUrl info.

Cause: Empty DB host and port information.

Action: Please make sure to provide the correct jdbcUrl info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06117: Empty JDBC host and port information. Please make sure to provide the correct jdbcUrl info.

Cause: Empty DB host and port information.

Action: Please make sure to provide the correct jdbcUrl info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06117: Empty JDBC host and port information. Please make sure to provide the correct jdbcUrl info.

Cause: Empty DB host and port information.

Action: Please make sure to provide the correct jdbcUrl info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06118: Empty JDBC Driver information. Please make sure to provide the correct jdbcDriver info.

Cause: Empty JDBC Driver information.

Action: Please make sure to provide the correct jdbcDriver info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06118: Empty JDBC Driver information. Please make sure to provide the correct jdbcDriver info.

Cause: Empty JDBC Driver information.

Action: Please make sure to provide the correct jdbcDriver info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06118: Empty JDBC Driver information. Please make sure to provide the correct jdbcDriver info.

Cause: Empty JDBC Driver information.

Action: Please make sure to provide the correct jdbcDriver info.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06119: Recovery failed. Key backup not Found.

Cause: No import was performed or import was not sucessfull.

Action: import the key(s) again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06119: Recovery failed. Key backup not Found.

Cause: No import was performed or import was not sucessfull.

Action: import the key(s) again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06119: Recovery failed. Key backup not Found.

Cause: No import was performed or import was not sucessfull.

Action: import the key(s) again.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06120: Policystore is already upgraded, so it will not be upgraded again.

Cause: Policystore is already upgraded.

Action: Policystore will not be upgraded again.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06121: Keystore is already upgraded, so it will not be upgraded again.

Cause: Keystore is already upgraded.

Action: Keystore will not be upgraded again.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06122: Auditstore is already upgraded, so it will not be upgraded again.

Cause: Auditstore is already upgraded.

Action: Auditstore will not be upgraded again.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06123: XACML Policy/PolicySet Defaults not supported in OES.

Cause: XACML Policy/PolicySet Defaults not supported in OES.

Action: XACML Policy/PolicySet Defaults not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06124: XACML Policy/PolicySet Max Delegation Depth not supported in OES.

Cause: XACML Policy/PolicySet Max Delegation Depth not supported in OES.

Action: XACML Policy/PolicySet Max Delegation Depth not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06125: XACML attribute Issuer not supported in OES for the element {0}.

Cause: XACML attribute Issuer not supported in OES.

Action: XACML attribute Issuer not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06126: XACML PolicySet/Policy/Rule Combiner Parameters not supported in OES.

Cause: XACML Policy/Rule Combiner Parameters not supported in OES.

Action: XACML Policy/Rule Combiner Parameters not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06127: XACML Attribute Selector not supported in OES.

Cause: XACML Attribute Selector not supported in OES.

Action: XACML Attribute Selector not supported in OES.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06128: Unknown Policy/PolicySet Id reference {0}.

Cause: Unknown Variable reference.

Action: Provide an Id Reference of a Policy/PolicySet that exists in the application
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06129: Unknown Variable reference {0}.

Cause: Unknown Policy/PolicySet Id reference.

Action: Provide a variable Reference for which a vadiable definition exists in the policy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-06131: Migration of Audit Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06132: Migration of Audit Store data completed, Time taken for migration is {0}

Cause: Migration of Audit Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06133: Migration of Credential Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06134: Migration of Credential Store data completed, Time taken for migration is {0}

Cause: Migration of Credential Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06135: Migration of Credential folder data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06136: Migration of Credential folder data completed, Time taken for migration is {0}

Cause: Migration of Credential folder data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06137: Migration of Application Policies {0} in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06138: Migration of Application Policies {0} completed, Time taken for migration is {1}

Cause: Migration of Application Policies {0} completed, Time taken for migration is {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06139: Migration of Global Policies in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06140: Migration of Global Policies completed, Time taken for migration is {0}

Cause: Migration of System Policies completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06141: Migration of All[Application + Global] policies in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06142: Migration of All[Application + Global] policies completed, Time taken for migration is {0}

Cause: Migration of All[Application + Global] policies completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06143: Migration of Java Policies in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06144: Migration of Java Policies completed, Time taken for migration is {0}

Cause: Migration of Java Policies completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06145: Migration of Identity Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06146: Migration of Identity Store data completed, Time taken for migration is {0}

Cause: Migration of Identity Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06147: Migration of Admin Role Members started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06148: Migration of {0} Admin Role Members completed in {1}

Cause: Migration of {0} Admin Role Members completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06149: Migration of Grants started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06150: Migration of {0} Grants completed in {1}

Cause: Migration of {0} Grants completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06151: Migration of Policy Domains started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06152: Migration of {0} Policy Domains completed in {1}

Cause: Migration of {0} Policy Domains completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06153: Migration of Application Roles started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06154: Migration of {0} Application Roles completed in {1}

Cause: Migration of {0} Application Roles completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06155: Migration of Resources started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06156: Migration of {0} Resources completed in {1}

Cause: Migration of {0} Resources completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06157: Migration of Admin Roles started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06158: Migration of {0} Admin Roles completed in {1}

Cause: Migration of {0} Admin Roles completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06159: Migration of Policies started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06160: Migration of {0} Policies completed in {1}

Cause: Migration of {0} Policies completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06161: Migration of Resource Types started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06162: Migration of {0} Resource Types completed in {1}

Cause: Migration of {0} Resource Types completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06163: Migration of Permission Sets started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06164: Migration of {0} Permission Sets completed in {1}

Cause: Migration of {0} Permission Sets completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06165: Migration of Functions started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06166: Migration of {0} Functions completed in {1}

Cause: Migration of {0} Functions completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06167: Migration of Attributes started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06168: Migration of {0} Attributes completed in {1}

Cause: Migration of {0} Attributes completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06169: Migration of Role Policies started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06170: Migration of {0} Role Policies completed in {1}

Cause: Migration of {0} Role Policies completed in {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06171: Failed to create policy store object, please check the logs.

Cause: Failed to create policy store object, please check the logs.

Action: Please check the logs.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06172: {0} service not found in default context, skipping upgrade for this service.

Cause: {0} service not found in default context of OPSS configuration

Action: Configure {0} service in default context of OPSS configuration files and run the upgrade again
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06173: Policystore upgrade from {0} to {1} not supported

Cause: Policystore upgrade from {0} to {1} not supported

Action: Policystore must be upgraded to a higher patchset first.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06174: OPSS data is not backed up as part of upgrade process in LDAP/DB based OPSS Store

Cause: OPSS data is not backed up as part of upgrade process in LDAP/DB based OPSS Store

Action: Back up data manually before running upgrade in LDAP/DB based OPSS Store.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06175: Migration of CombiningAlgorithms started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06176: Migration of {0} CombiningAlgorithms completed in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06177: Migration of Policy Rule started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06178: Migration of {0} Policy Rule completed in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06179: Migration of Policy Set started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06180: Migration of {0} Policy Set completed in {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06181: Migration of Key Store data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06182: Migration of Key Store data completed, Time taken for migration is {0}

Cause: Migration of Key Store data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06183: Migration of Key Store stripe data in progress.....

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06184: Migration of Key Store stripe data completed, Time taken for migration is {0}

Cause: Migration of KeyStore stripe data completed, Time taken for migration is {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06185: More than one properties set references present for policy store service instance in jps-config file {0}

Cause: More than one property set references present in policy store service instance in jps-config.xml file

Action: Make sure only one property set references under policy store service instance in jps-config.xml file
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06186: Either bootstrap credstore or key store service instance is not found in bootstrap context

Cause: Either bootstrap credstore or key store service instance is not found in bootstrap context

Action: Ensure both bootstrap credstore and keystore service instance reference in bootstrap context is present
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06187: Not able to find file based keystore service instance, while adding keystore service instance to bootstrap context

Cause: Not able to find file based keystore service instance, while adding keystore service instance to bootstrap context

Action: Ensure file based keystore service instance reference in jps-config.xml is present
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06188: New Application Policy {0} created during migration

Cause: Migration of Application Roles completed in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06189: Migrate Permission Name = {0}, Exception during modification of permission. Message = {1}.

Cause: Migrate Permission Name = {0}, Exception during modification of permission. Message = {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06190: Miagrtion failed in Perm Member : {0}.

Cause: Miagrtion failed in Perm Member : {0}

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06191: PermissionMigrator Thread {0} failed due to {1}.

Cause: PermissionMigrator Thread {0} failed due to {1}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06192: Cannot get source policy store.

Cause: While migrating a security store, cannot get source policy store.

Action: Check and make sure source policy store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06193: Cannot get destination policy store.

Cause: While migrating a security store, cannot get destionation policy store.

Action: Check and make sure destination policy store is configured correctly.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06194: There are multiple logic security stores in the db schema : {0}. Please split them before doing upgrade.

Cause: Found multiple security stores in the db schema.

Action: Reassociate each security store to separated db schema.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06195: Security store is already transformed, so it will not be transformed again.

Cause: Security store is already transformed.

Action: Security store will not be transfromed again.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06196: Transformation of security store started.

Cause: Begin security store transformation.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06197: Transformation of security store completed in {0}.

Cause: Finish security store transformation.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Upgrade

JPS-06198: OPSS Schema is not upgraded. Current schema version is {0}. Schema version for upgrade is {1}

Cause: OPSS Schema is not upgraded.

Action: Upgrade OPSS Schema first before upgrading Opss Data and Config.
Level: 1

Type: ERROR

Impact: Upgrade

JPS-06199: Source application type dose not match the type of destination application.

Cause: Source application type dose not match the destination application type.

Action: No actions are required.
Level: 1

Type: WARNING

Impact: Upgrade

JPS-06200: Property {0} with value "{1}" is invalid in the meta data property file.

Cause: Property {0} with value "{1}" is invalid in the meta data property file.

Action: Check the meta data property file.
Level: 1

Type: ERROR

Impact: Security

JPS-06201: Property {0} is missing in the meta data property file.

Cause: Property {0} is missing in the meta data property file.

Action: Check the meta data property file.
Level: 1

Type: ERROR

Impact: Security

JPS-06202: Cannot migrate {0} named "{1}", policy object already exists in application policy with different metadata.

Cause: {0} named "{1}" already exists in application policy with differnt metadata.

Action: Check policy store data in source application policy, remove conflict data.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-06500: Alias already exists in the keystore

Cause: The specified alias name already existed in the keystore.

Action: Specify a unique alias name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06500: Alias already exists in the keystore

Cause: The specified alias name already existed in the keystore.

Action: Specify a unique alias name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06500: Alias already exists in the keystore

Cause: The specified alias name already existed in the keystore.

Action: Specify a unique alias name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06501: Keystore {0} in stripe {1} already exists

Cause: Keystore with the given name already existed.

Action: Specify a unique keystore name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06501: Keystore {0} in stripe {1} already exists

Cause: Keystore with the given name already existed.

Action: Specify a unique keystore name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06501: Keystore {0} in stripe {1} already exists

Cause: Keystore with the given name already existed.

Action: Specify a unique keystore name.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06502: Failed to read keystore. Reason {0}

Cause: Could not read the keystore.

Action: Verify the keystore location and that sufficient permissions are in place.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06502: Failed to read keystore

Cause: Could not read the keystore.

Action: Verify the keystore location and that sufficient permissions are in place.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06502: Failed to read keystore

Cause: Could not read the keystore.

Action: Verify the keystore location and that sufficient permissions are in place.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06503: Failed to write keystore. Reason {0}

Cause: Could not read the keystore.

Action: Verify the keystore location, that sufficient permissions are in place and that sufficient disk space is available.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06503: Failed to write keystore

Cause: Could not read the keystore.

Action: Verify the keystore location, that sufficient permissions are in place and that sufficient disk space is available.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06503: Failed to write keystore

Cause: Could not read the keystore.

Action: Verify the keystore location, that sufficient permissions are in place and that sufficient disk space is available.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06504: Failed to perform cryptographic operation

Cause: The java provider did not support this cryptographic operation.

Action: Verify that a provider that supports this algorithm/padding/key is configured.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06504: Failed to perform cryptographic operation

Cause: The java provider did not support this cryptographic operation.

Action: Verify that a provider that supports this algorithm/padding/key is configured.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06504: Failed to perform cryptographic operation

Cause: The java provider did not support this cryptographic operation.

Action: Verify that a provider that supports this algorithm/padding/key is configured.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06505: Failed to generate certificate request

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06505: Failed to generate certificate request

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06505: Failed to generate certificate request

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06506: Key generation algorithm not supported

Cause: An unsupported key-pair generation algorithm was used.

Action: Specify a supported key-pair generation algorithm.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06506: Key generation algorithm not supported

Cause: An unsupported key-pair generation algorithm was used.

Action: Specify a supported key-pair generation algorithm.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06506: Key generation algorithm not supported

Cause: An unsupported key-pair generation algorithm was used.

Action: Specify a supported key-pair generation algorithm.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06507: Root CA import failed.

Cause: The root CA certificate and/or key file was malformed.

Action: Verify that the root CA certificate and/or key files is valid.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06507: Root CA import failed.

Cause: The root CA certificate and/or key file was malformed.

Action: Verify that the root CA certificate and/or key files is valid.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06507: Root CA import failed.

Cause: The root CA certificate and/or key file was malformed.

Action: Verify that the root CA certificate and/or key files is valid.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06508: Failed to generate CA signed certificate.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06508: Failed to generate CA signed certificate.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06508: Failed to generate CA signed certificate.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06509: The keystore has been moved or deleted.

Cause: The keystore did not exist at this location.

Action: Verify that the location of keystore is correct.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06509: The keystore has been moved or deleted.

Cause: The keystore did not exist at this location.

Action: Verify that the location of keystore is correct.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06509: The keystore has been moved or deleted.

Cause: The keystore did not exist at this location.

Action: Verify that the location of keystore is correct.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06510: The keystore location property is not configured, or the configured value {0} is invalid.

Cause: The keystore location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06510: The keystore location property is not configured, or the configured value {0} is invalid.

Cause: The keystore location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06510: The keystore location property is not configured, or the configured value {0} is invalid.

Cause: The keystore location was not specified.

Action: Check the value of the location attribute.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06511: Cannot create keystore at {0}.

Cause: Could not create the keystore.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06511: Cannot create keystore at {0}.

Cause: Could not create the keystore.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06511: Cannot create keystore at {0}.

Cause: Could not create the keystore.

Action: Verify the store location, that sufficient permissions are in place, and that sufficient disk space is available.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06513: Failed to save keystore. Reason :

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06513: Failed to save keystore. Reason {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06513: Failed to save keystore. Reason {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06514: Opening of file based keystore failed. Reason :

Cause: Keystore could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06514: Opening of file based keystore failed.

Cause: Keystore could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06514: Opening of file based keystore failed.

Cause: Keystore could not be opened

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06515: Refreshing of file based keystore failed. Reason {0}

Cause: Refresh of keystore failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06515: Refreshing of file based keystore failed. Reason {0}

Cause: Refresh of keystore failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06515: Refreshing of file based keystore failed. Reason {0}

Cause: Refresh of keystore failed

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06516: Failed to get credential store. Reason {0}

Cause: Could not get credential store.

Action: Verify credential store is correctly configured and initialized.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06516: Failed to get credential store. Reason {0}

Cause: Could not get credential store.

Action: Verify credential store is correctly configured and initialized.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06516: Failed to get credential store. Reason {0}

Cause: Could not get credential store.

Action: Verify credential store is correctly configured and initialized.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06517: Failed to create the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06517: Failed to create the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06517: Failed to create the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06518: Keystore {0} in stripe {1} does not exist.

Cause: Could not perform this operation since the keystore did not exist.

Action: Specify an existing keystore name for this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06518: Keystore {0} in stripe {1} does not exist.

Cause: Could not perform this operation since the keystore did not exist.

Action: Specify an existing keystore name for this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06518: Keystore {0} in stripe {1} does not exist.

Cause: Could not perform this operation since the keystore did not exist.

Action: Specify an existing keystore name for this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06519: Failed to get/set credential with map {0} and key {1} in bootstrap credstore. Reason {2}

Cause: Credential store was not available or permissions were not in place.

Action: Verify credential store is correctly configured and permissions are granted.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06519: Failed to get/set credential in credstore. Reason {0}

Cause: Credential store was not available or permissions were not in place.

Action: Verify credential store is correctly configured and permissions are granted.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06519: Failed to get/set credential in credstore. Reason {0}

Cause: Credential store was not available or permissions were not in place.

Action: Verify credential store is correctly configured and permissions are granted.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06520: Failed to encode/decode certificate or public key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06520: Failed to encode/decode certificate or public key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06520: Failed to encode/decode certificate or public key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06521: Invalid admin password, operation not permitted

Cause: Invalid admin password was specified.

Action: Specify the correct admin password to perform this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06521: Invalid admin password, operation not permitted

Cause: Invalid admin password was specified.

Action: Specify the correct admin password to perform this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06521: Invalid admin password, operation not permitted

Cause: Invalid admin password was specified.

Action: Specify the correct admin password to perform this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06522: Failed to roll over keystore master key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06522: Failed to roll over keystore master key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06522: Failed to roll over keystore master key.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06523: Failed to reset keystore administrator password.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06523: Failed to reset keystore administrator password.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06523: Failed to reset keystore administrator password.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06524: Failed to read certificates from keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06524: Failed to read certificates from keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06524: Failed to read certificates from keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06525: Failed to list/renew expiring certificates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06525: Failed to list/renew expiring certificates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06525: Failed to list/renew expiring certificates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06526: Failed to list policy violations in keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06526: Failed to list policy violations in keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06526: Failed to list policy violations in keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06527: Invalid keystore name {0}

Cause: Invalid keystore name was specified.

Action: Specify a keystore name that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06527: Invalid keystore name {0}

Cause: Invalid keystore name was specified.

Action: Specify a keystore name that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06527: Invalid keystore name {0}

Cause: Invalid keystore name was specified.

Action: Specify a keystore name that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06528: Invalid alias value {0}

Cause: Invalid alias value was specified.

Action: Specify an alias value that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06528: Invalid alias value {0}

Cause: Invalid alias value was specified.

Action: Specify an alias value that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06528: Invalid alias value {0}

Cause: Invalid alias value was specified.

Action: Specify an alias value that is not null or empty and contains only alphanumeric characters.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06529: Passwords must not be null or empty.

Cause: Password was specified as null or empty.

Action: Specify a non null or non empty password for a keystore protected by password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06529: Passwords must not be null or empty.

Cause: Password was specified as null or empty.

Action: Specify a non null or non empty password for a keystore protected by password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06529: Passwords must not be null or empty.

Cause: Password was specified as null or empty.

Action: Specify a non null or non empty password for a keystore protected by password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06530: Invalid stripe value {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06530: Invalid stripe value {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06530: Invalid stripe value {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06531: Operation failed, keystore password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06531: Operation failed, keystore password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06531: Operation failed, keystore password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06532: Failed to delete the keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06532: Failed to delete the keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06532: Failed to delete the keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06533: Algorithm {0} not supported

Cause: The algorithm was not supported by keystore.

Action: Check the list of supported algorithms and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06533: Algorithm {0} not supported

Cause: The algorithm was not supported by keystore.

Action: Check the list of supported algorithms and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06533: Algorithm {0} not supported

Cause: The algorithm was not supported by keystore.

Action: Check the list of supported algorithms and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06534: Keystore master key roll-over failed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06534: Keystore master key roll-over failed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06534: Keystore master key roll-over failed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06535: Failed to generate secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06535: Failed to generate secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06535: Failed to generate secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06536: Failed to import secret key for keystore {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06536: Failed to import secret key for keystore {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06536: Failed to import secret key for keystore {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06537: Failed to change password for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06537: Failed to change password for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06537: Failed to change password for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06538: Cannot set password for trusted certificate entry.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06538: Cannot set password for trusted certificate entry.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06538: Cannot set password for trusted certificate entry.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06539: Operation failed, key password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06539: Operation failed, key password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06539: Operation failed, key password does not match

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06540: Failed to change password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06540: Failed to change password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06540: Failed to change password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06541: Invalid keystore entry type {0}

Cause: The keystore entry type was invalid for this operation.

Action: Check the list of supported keystore entry types from documentation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06541: Invalid keystore entry type {0}

Cause: The keystore entry type was invalid for this operation.

Action: Check the list of supported keystore entry types from documentation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06541: Invalid keystore entry type {0}

Cause: The keystore entry type was invalid for this operation.

Action: Check the list of supported keystore entry types from documentation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06542: Failed to list aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06542: Failed to list aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06542: Failed to list aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06543: Invalid Distinguished Name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06543: Invalid Distinguished Name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06543: Invalid Distinguished Name {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06544: Failed to generate key pair for alias {0} keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06544: Failed to generate key pair for alias {0} keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06544: Failed to generate key pair for alias {0} keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06545: The expected keystore entry with alias "{0}" either does not exist or is not of the specified keystore entry type for keystore "{1}" in stripe "{2}".

Cause: The alias value either did not exist or did not point to the specified keystore entry type.

Action: Specify a valid alias value that points to the specified keystore entry type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06545: The expected keystore entry with alias "{0}" does not exist for keystore "{1}" in stripe "{2}".

Cause: The alias value either did not exist or did not point to the specified keystore entry type.

Action: Specify a valid alias value that points to the specified keystore entry type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06545: The expected keystore entry with alias "{0}" does not exist for keystore "{1}" in stripe "{2}".

Cause: The alias value either did not exist or did not point to the specified keystore entry type.

Action: Specify a valid alias value that points to the specified keystore entry type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06546: Failed to get secret key with alias {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06546: Failed to get secret key with alias {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06546: Failed to get secret key with alias {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06547: Failed to get certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06547: Failed to get certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06547: Failed to get certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06548: Failed to export certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06548: Failed to export certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06548: Failed to export certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06549: No corresponding key pair found for this certificate

Cause: The alias value did not point to the matching key pair for this certificate

Action: Specify a valid alias value that points to a key pair whose public key matches that of the certificate.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06549: No corresponding key pair found for this certificate

Cause: The alias value did not point to the matching key pair for this certificate

Action: Specify a valid alias value that points to a key pair whose public key matches that of the certificate.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06549: No corresponding key pair found for this certificate

Cause: The alias value did not point to the matching key pair for this certificate

Action: Specify a valid alias value that points to a key pair whose public key matches that of the certificate.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06550: Failed to parse the certificate chain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06550: Failed to parse the certificate chain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06550: Failed to parse the certificate chain

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06551: Failed to import the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06551: Failed to import the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06551: Failed to import the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06552: Failed to delete the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06552: Failed to delete the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06552: Failed to delete the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06553: Cannot perform this operation on domain trust store

Cause: The operation was not supported for domain trust store.

Action: Check product documentation to see the operations permitted on domain trust store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06553: Cannot perform this operation on domain trust store

Cause: The operation was not supported for domain trust store.

Action: Check product documentation to see the operations permitted on domain trust store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06553: Cannot perform this operation on domain trust store

Cause: The operation was not supported for domain trust store.

Action: Check product documentation to see the operations permitted on domain trust store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06554: Cannot perform this operation on demo CA keystore

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06554: Cannot perform this operation on demo CA keystore

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06554: Cannot perform this operation on demo CA keystore

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06555: Mismatch between the values of key aliases and key passwords

Cause: There should be equal number of entries for key aliases and key passwords

Action: Ensure that key aliases and key passwords are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06555: Mismatch between the values of key aliases and key passwords

Cause: There should be equal number of entries for key aliases and key passwords

Action: Ensure that key aliases and key passwords are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06555: Mismatch between the values of key aliases and key passwords

Cause: There should be equal number of entries for key aliases and key passwords

Action: Ensure that key aliases and key passwords are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06556: Keystore to be imported is not valid

Cause: The keystore file being imported was either empty or of invalid format.

Action: Ensure that the keystore being imported is of valid format.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06556: Keystore to be imported is not valid

Cause: The keystore file being imported was either empty or of invalid format.

Action: Ensure that the keystore being imported is of valid format.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06556: Keystore to be imported is not valid

Cause: The keystore file being imported was either empty or of invalid format.

Action: Ensure that the keystore being imported is of valid format.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06557: Mismatch between the values of CSF maps and keys

Cause: There should be equal number of entries for CSF maps and CSF keys

Action: Ensure that CSF maps and keys are either both null, or are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06557: Mismatch between the values of CSF maps and keys

Cause: There should be equal number of entries for CSF maps and CSF keys

Action: Ensure that CSF maps and keys are either both null, or are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06557: Mismatch between the values of CSF maps and keys

Cause: There should be equal number of entries for CSF maps and CSF keys

Action: Ensure that CSF maps and keys are either both null, or are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06558: Mismatch between the values of key alias/password and CSF map/key

Cause: There should be equal number of entries for key alias/password and CSF map/key

Action: Ensure that key alias/password and CSF map/key are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06558: Mismatch between the values of key alias/password and CSF map/key

Cause: There should be equal number of entries for key alias/password and CSF map/key

Action: Ensure that key alias/password and CSF map/key are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06558: Mismatch between the values of key alias/password and CSF map/key

Cause: There should be equal number of entries for key alias/password and CSF map/key

Action: Ensure that key alias/password and CSF map/key are equal in number.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06559: Keystore type {0} not supported

Cause: The keystore type was not supported.

Action: Check the list of supported keystore types and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06559: Keystore type {0} not supported

Cause: The keystore type was not supported.

Action: Check the list of supported keystore types and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06559: Keystore type {0} not supported

Cause: The keystore type was not supported.

Action: Check the list of supported keystore types and specify one of them.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06560: Failed to import the keystore {0} in stripe {1}. Reason {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06560: Failed to import the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06560: Failed to import the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06561: Failed to export the keystore {0} in stripe {1}. Reason {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06561: Failed to export the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06561: Failed to export the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06562: Failed to load the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06562: Failed to load the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06562: Failed to load the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06563: Failed to save the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06563: Failed to save the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06563: Failed to save the keystore.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06564: Method not implemented

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06564: Method not implemented

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06564: Method not implemented

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06565: Invalid keystore protection parameter

Cause: The specified keystore protection type was not supported.

Action: Ensure that the keystore protection type is a password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06565: Invalid keystore protection parameter

Cause: The specified keystore protection type was not supported.

Action: Ensure that the keystore protection type is a password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06565: Invalid keystore protection parameter

Cause: The specified keystore protection type was not supported.

Action: Ensure that the keystore protection type is a password.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06566: No trusted certificate found with this alias

Cause: The specified alias did not refer to a trusted certificate.

Action: Ensure that the alias refers to a trusted certificate in the keystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06566: No trusted certificate found with this alias

Cause: The specified alias did not refer to a trusted certificate.

Action: Ensure that the alias refers to a trusted certificate in the keystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06566: No trusted certificate found with this alias

Cause: The specified alias did not refer to a trusted certificate.

Action: Ensure that the alias refers to a trusted certificate in the keystore.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06567: Unsupported key type

Cause: The key type was not supported.

Action: Ensure that key is either private key or secret key.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06567: Unsupported key type

Cause: The key type was not supported.

Action: Ensure that key is either private key or secret key.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06567: Unsupported key type

Cause: The key type was not supported.

Action: Ensure that key is either private key or secret key.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06568: Insufficient permissions for this operation. Reason {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06568: Insufficient permissions for this operation

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06568: Insufficient permissions for this operation

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06569: Keystore {0} in app stripe {1} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06569: Keystore {0} in app stripe {1} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06569: Keystore {0} in app stripe {1} does not exist

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06570: Failed to set keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06570: Failed to set keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06570: Failed to set keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06571: Failed to delete keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06571: Failed to delete keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06571: Failed to delete keystore policy

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06572: Null policy name/value not allowed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06572: Null policy name/value not allowed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06572: Null policy name/value not allowed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06573: Failed to list keystore policies

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06573: Failed to list keystore policies

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06573: Failed to list keystore policies

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06574: Invalid key parameters

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06574: Invalid key parameters

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06574: Invalid key parameters

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06575: Certificate import failed as the public key in the certificate did not match the one in the keystore.

Cause: The public key in the certificate does not match the one in the keystore.

Action: Ensure that the certificate is imported into the alias used for generating certificate request.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06575: Certificate import failed.

Cause: The public key in the certificate does not match the one in the keystore.

Action: Ensure that the certificate is imported into the alias used for generating certificate request.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06575: Certificate import failed.

Cause: The public key in the certificate does not match the one in the keystore.

Action: Ensure that the certificate is imported into the alias used for generating certificate request.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06576: Failed to read {0} with alias {1}.

Cause: Failed to read {0} with alias {1}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06576: Failed to read {0} with alias {1}.

Cause: Failed to read {0} with alias {1}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06576: Failed to read {0} with alias {1}.

Cause: Failed to read {0} with alias {1}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06577: Failed to create private key {0}.

Cause: Failed to create private key {0}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06577: Failed to create private key {0}.

Cause: Failed to create private key {0}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06577: Failed to create private key {0}.

Cause: Failed to create private key {0}.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06578: Cert with alias {0} was invalid.

Cause: Cert with alias {0} was invalid.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06578: Cert with alias {0} was invalid.

Cause: Cert with alias {0} was invalid.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06578: Cert with alias {0} was invalid.

Cause: Cert with alias {0} was invalid.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06579: Failed to read keystore data.

Cause: Failed to read keystore data.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06579: Failed to read keystore data.

Cause: Failed to read keystore data.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06579: Failed to read keystore data.

Cause: Failed to read keystore data.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06580: Failed to check keystore integrity.

Cause: Failed to check keystore integrity.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06580: Failed to check keystore integrity.

Cause: Failed to check keystore integrity.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06580: Failed to check keystore integrity.

Cause: Failed to check keystore integrity.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06581: Failed to load certificates from the keystore.

Cause: Failed to load certificates from the keystore.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06581: Failed to load certificates from the keystore.

Cause: Failed to load certificates from the keystore.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06581: Failed to load certificates from the keystore.

Cause: Failed to load certificates from the keystore.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06582: Failed to get trusted certs.

Cause: Failed to get trusted certs

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06582: Failed to get trusted certs.

Cause: Failed to get trusted certs

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06582: Failed to get trusted certs.

Cause: Failed to get trusted certs

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06583: Failed to check if audit is enabled.

Cause: Keystore audit events logging was not enabled.

Action: Check the audit configuration to ensure auditing enabled.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06583: Failed to check if audit is enabled.

Cause: Keystore audit events logging was not enabled.

Action: Check the audit configuration to ensure auditing enabled.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06583: Failed to check if audit is enabled.

Cause: Keystore audit events logging was not enabled.

Action: Check the audit configuration to ensure auditing enabled.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06584: Failed to log audit record.

Cause: Keystore audit event logging failed.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06584: Failed to log audit record.

Cause: Keystore audit event logging failed.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06584: Failed to log audit record.

Cause: Keystore audit event logging failed.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06585: Created keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06585: Created keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06585: Created keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06586: Deleted keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06586: Deleted keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06586: Deleted keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06587: Successfully listed keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06587: Successfully listed keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06587: Successfully listed keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06588: Failed to list keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06588: Failed to list keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06588: Failed to list keystores in stripe {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06589: Successfully got the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06589: Successfully got the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06589: Successfully got the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06590: Failed to get the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06590: Failed to get the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06590: Failed to get the handle to keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06591: Successfully changed the password of keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06591: Successfully changed the password of keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06591: Successfully changed the password of keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06592: Successfully generated key pair with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06592: Successfully generated key pair with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06592: Successfully generated key pair with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06593: Successfully generated secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06593: Successfully generated secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06593: Successfully generated secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06594: Successfully changed password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06594: Successfully changed password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06594: Successfully changed password for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06595: Successfully listed aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06595: Successfully listed aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06595: Successfully listed aliases for keystore {0} in stripe {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06596: Successfully listed properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06596: Successfully listed properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06596: Successfully listed properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06597: Failed to list properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06597: Failed to list properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06597: Failed to list properties for secret key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06598: Successfully got certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06598: Successfully got certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06598: Successfully got certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06599: Successfully exported certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06599: Successfully exported certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06599: Successfully exported certificate request for key with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06600: Failed to export certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06600: Failed to export certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06600: Failed to export certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06601: Successfully exported certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06601: Successfully exported certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06601: Successfully exported certificate(s) with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06602: Successfully imported the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06602: Successfully imported the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06602: Successfully imported the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06603: Successfully deleted the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06603: Successfully deleted the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06603: Successfully deleted the key store entry with alias {0} for keystore {1} in stripe {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06604: Successfully imported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06604: Successfully imported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06604: Successfully imported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06605: Successfully exported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06605: Successfully exported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06605: Successfully exported the keystore {0} in stripe {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06606: Could not create keystore service instance. Reason {0}

Cause: Could not create keystore service instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06606: Could not create keystore service instance. Reason {0}

Cause: Could not create keystore service instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06606: Could not create keystore service instance. Reason {0}

Cause: Could not create keystore service instance

Action: Contact system administrator
Level: 1

Type: WARNING

Impact: Compliance

JPS-06607: The keystore service DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected keystore DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06607: The keystore service DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected keystore DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06607: The keystore service DN {0} is missing in the store; the target DN must be pre-configured.

Cause: The expected keystore DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06608: The farm DN property {0} is invalid or not defined.

Cause: The farm name property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06608: The farm DN property {0} is invalid or not defined.

Cause: The farm name property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06608: The farm DN property {0} is invalid or not defined.

Cause: The farm name property {0} was invalid or not defined.

Action: Check the configuration of this property.
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-06609: The keystore is not initialized.

Cause: The keystore was not loaded.

Action: Load the keystore before trying this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06609: The keystore is not initialized.

Cause: The keystore was not loaded.

Action: Load the keystore before trying this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06609: The keystore is not initialized.

Cause: The keystore was not loaded.

Action: Load the keystore before trying this operation.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06610: Keystore {0} did not exist.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06610: Keystore {0} did not exist.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06610: Keystore {0} did not exist.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06611: The keystore service instance {0} was not initialized.

Cause: Keystore service was not completely initialized.

Action: Wait until data source is available and try again later.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06611: The keystore service instance {0} was not initialized.

Cause: Keystore service was not completely initialized.

Action: Wait until data source is available and try again later.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06611: The keystore service instance {0} was not initialized.

Cause: Keystore service was not completely initialized.

Action: Wait until data source is available and try again later.
Level: 1

Type: ERROR

Impact: Configuration

JPS-06612: The properties for keystore {0} in stripe {1} were read successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06612: The properties for keystore {0} in stripe {1} were read successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06612: The properties for keystore {0} in stripe {1} were read successfully

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06613: Supported key sizes could not be determined for this algorithm.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06613: Supported key sizes could not be determined for this algorithm.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06613: Supported key sizes could not be determined for this algorithm.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06614: Operation not supported - unable to delete key store {0} in stripe {1}.

Cause: Deletion of domain trust store or the demo CA key store was not permitted.

Action: Choose a different key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06614: Failed to delete key store {0} in stripe {1}.

Cause: Deletion of domain trust store or the demo CA key store was not permitted.

Action: Choose a different key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06614: Failed to delete key store {0} in stripe {1}.

Cause: Deletion of domain trust store or the demo CA key store was not permitted.

Action: Choose a different key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06615: Operation not supported - unable to delete alias {0} in key store {1} in stripe {2}.

Cause: Deletion of demo CA key was not permitted.

Action: Choose a different key alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06615: Failed to delete alias {0} in key store {1} in stripe {2}.

Cause: Deletion of demo CA key was not permitted.

Action: Choose a different key alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06615: Failed to delete alias {0} in key store {1} in stripe {2}.

Cause: Deletion of demo CA key was not permitted.

Action: Choose a different key alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06616: Missing certificate chain.

Cause: Certificate chain was null.

Action: Specify a valid certificate chain.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06616: Missing certificate chain.

Cause: Certificate chain was null.

Action: Specify a valid certificate chain.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06616: Missing certificate chain.

Cause: Certificate chain was null.

Action: Specify a valid certificate chain.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06617: Successfully retrieved the attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06617: Successfully retrieved the attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06617: Successfully retrieved the attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06618: Failed to retrieve attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06618: Failed to retrieve attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06618: Failed to retrieve attribute {0} from the keystore {1} in stripe {2}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06619: Key store file keystores.xml integrity check failed. Location: {0}

Cause: File keystore.xml has been manually edited.

Action: Restore the keystore file to the last working backup and try again.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06619: Key store file keystores.xml integrity check failed.

Cause: File keystore.xml has been manually edited.

Action: Restore the keystore file to the last working backup and try again.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06619: Key store file keystores.xml integrity check failed.

Cause: File keystore.xml has been manually edited.

Action: Restore the keystore file to the last working backup and try again.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06620: Key store file integrity checker initialization failed. Reason {0}

Cause: Problem using the bootstrap credential store service.

Action: Check the bootstrap credential store configuration.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06620: Key store file integrity checker initialization failed. Reason {0}

Cause: Problem using the bootstrap credential store service.

Action: Check the bootstrap credential store configuration.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06620: Key store file integrity checker initialization failed. Reason {0}

Cause: Problem using the bootstrap credential store service.

Action: Check the bootstrap credential store configuration.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06621: Cannot change password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06621: Cannot change password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06621: Cannot change password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06622: Cannot change key password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06622: Cannot change key password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06622: Cannot change key password of a permission protected key store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06623: Invalid KSS URI: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06624: Cannot synchronize centralized key store(s) from stripe {0} to bootstrap key store(s). Reason {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-06625: Invalid component type {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-06626: Could not get bootstrap key store service. Reason {0}

Cause: Could not get bootstrap key store service.

Action: Verify key store service is correctly configured and initialized.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06627: Invalid keystore provider type. Value {0}

Cause: Value of keystore.provider.type is invalid.

Action: Assign a valid value to keystore.provider.type.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06628: Key alias {0} corresponds to neither a key nor a trusted certificate in the imported keystore.

Cause: Given key alias corresponds to neither a key nor a trusted certificate.

Action: Given key alias should correspond to either a key or a trusted certificate.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06629: No alias specified so skipping import/export

Cause: Key aliases should not be null or empty string.

Action: Ensure that key aliases are neither null nor empty string.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06630: Import of entry with alias: {0} into appStripe:{1} keystore:{2} skipped as it already exists in the keystore.

Cause: Alias already exists in the keystore. Alias overwriting while importing not supported.

Action: Alias to be imported shouldn't pre-exist in the key store.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06631: Certificate import failed as the minimum number of certificates expected is {0}

Cause: K required were not given.

Action: Ensure that minimum number of certificates are imported.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06632: Invalid key store attribute {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06633: Cannot synchronize component key store(s) under stripe {0} into corresponding wallets. Reason {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-06634: One or more of keystores inside application stripe {0} are not permission protected.

Cause: One or more of keystores inside the application stripe are not permission protected.

Action: Ensure that all keystores in the application stripe are permission protected.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06635: Either or both of stripe name {0} and keystore format {1} is null or empty string.

Cause: Either or both of stripe name and keystore format is null or empty string.

Action: Ensure that stripe name and keystore format are both non-empty string.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06636: Application stripe {0} does not exist in keystore.

Cause: Given application stripe doesn't exist in keystore.

Action: Provide name of an application stripe that is already existing in keystore.
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06637: Trusted certificate with Subject DN {0} is missing from trust store of keystore.

Cause: A trusted certificate is missing from trust store of keystore.

Action: Ensure that the trusted certificate is present in trust store of keystore.
Level: 1

Type: WARNING

Impact: Compliance

JPS-06638: KeyStore Entry required were not given.

Cause: KeyStore Entry required were not given.

Action: Provide KeyStore Entry as input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06639: The following aliases were encountered in the keystore: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-06640: Empty alias specified for importing wallet keystore, so skipping import

Cause: Key aliases of wallet keystore to import should not be empty string.

Action: Ensure that key aliases of wallet keystore to import are not empty string.
Level: 1

Type: WARNING

Impact: Configuration

JPS-06641: Invalid keySize format : {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Compliance

JPS-07000: Provide a valid jps configuration file.

Cause: The jps configuration file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07000: Provide a valid jps configuration file.

Cause: The jps configuration file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07000: Provide a valid jps configuration file.

Cause: The jps configuration file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07001: Provide a valid application name.

Cause: Application ID was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07001: Provide a valid application name.

Cause: Application ID was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07001: Provide a valid application name.

Cause: Application ID was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07002: Provide a valid jazn-data file. .

Cause: The jazn-data file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07002: Provide a valid jazn-data file. .

Cause: The jazn-data file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07002: Provide a valid jazn-data file. .

Cause: The jazn-data file was invalid.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07003: Provide a valid folder name.

Cause: The patch delta folder was invalid.

Action: Provide a valid folder for generating patch delta files.
Level: 1

Type: ERROR

Impact: Security

JPS-07003: Provide a valid folder name.

Cause: The patch delta folder was invalid.

Action: Provide a valid folder for generating patch delta files.
Level: 1

Type: ERROR

Impact: Security

JPS-07003: Provide a valid folder name.

Cause: The patch delta folder was invalid.

Action: Provide a valid folder for generating patch delta files.
Level: 1

Type: ERROR

Impact: Security

JPS-07004: ApplicationPolicy object is null/empty.

Cause: ApplicationPolicy object was null

Action: Make sure to create a not null ApplicationPolicy object
Level: 1

Type: ERROR

Impact: Security

JPS-07004: ApplicationPolicy object is null/empty.

Cause: ApplicationPolicy object was null

Action: Make sure to create a not null ApplicationPolicy object
Level: 1

Type: ERROR

Impact: Security

JPS-07004: ApplicationPolicy object is null/empty.

Cause: ApplicationPolicy object was null

Action: Make sure to create a not null ApplicationPolicy object
Level: 1

Type: ERROR

Impact: Security

JPS-07005: The "{0} " jazn data file does not exists.

Cause: Jazn data file does not exists.

Action: Make sure to provide an existing jazn-data file.
Level: 1

Type: ERROR

Impact: Security

JPS-07005: The "{0} " jazn data file does not exists.

Cause: Jazn data file does not exists.

Action: Make sure to provide an existing jazn-data file.
Level: 1

Type: ERROR

Impact: Security

JPS-07005: The "{0} " jazn data file does not exists.

Cause: Jazn data file does not exists.

Action: Make sure to provide an existing jazn-data file.
Level: 1

Type: ERROR

Impact: Security

JPS-07006: "{0}" Not a folder. Please provide a valid folder.

Cause: Not a folder.

Action: Make sure to provide a valid folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07006: "{0}" Not a folder. Please provide a valid folder.

Cause: Not a folder.

Action: Make sure to provide a valid folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07006: "{0}" Not a folder. Please provide a valid folder.

Cause: Not a folder.

Action: Make sure to provide a valid folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07007: "{0}" folder does not exists

Cause: The folder does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07007: "{0}" folder does not exists

Cause: The folder does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07007: "{0}" folder does not exists

Cause: The folder does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07008: The {0} jps configuration file does not exist.

Cause: The jps configuration file does not exists.

Action: Make sure to provide an existing jps configuration file.
Level: 1

Type: ERROR

Impact: Security

JPS-07008: The {0} jps configuration file does not exist.

Cause: The jps configuration file does not exists.

Action: Make sure to provide an existing jps configuration file.
Level: 1

Type: ERROR

Impact: Security

JPS-07008: The {0} jps configuration file does not exist.

Cause: The jps configuration file does not exists.

Action: Make sure to provide an existing jps configuration file.
Level: 1

Type: ERROR

Impact: Security

JPS-07009: The "{0}" folder for generating patch delta files does not exist.

Cause: The folder to generate the patch delta files does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07009: The "{0}" folder for generating patch delta files does not exist.

Cause: The folder to generate the patch delta files does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07009: The "{0}" folder for generating patch delta files does not exist.

Cause: The folder to generate the patch delta files does not exists.

Action: Make sure to provide an existing folder.
Level: 1

Type: ERROR

Impact: Security

JPS-07010: The AppRole "{0}" cannot be created. Cause {1} .

Cause: The approle could not be created.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-07010: The AppRole "{0}" cannot be created. Cause {1} .

Cause: The approle could not be created.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-07010: The AppRole "{0}" cannot be created. Cause {1} .

Cause: The approle could not be created.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-07011: The AppRole object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07011: The AppRole object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07011: The AppRole object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07012: The ResourceType object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Enusre to provide a valid ResourceType Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07012: The ResourceType object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Enusre to provide a valid ResourceType Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07012: The ResourceType object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Enusre to provide a valid ResourceType Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07013: The AppRole list is null/empty while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole List.
Level: 1

Type: ERROR

Impact: Security

JPS-07013: The AppRole list is null/empty while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole List.
Level: 1

Type: ERROR

Impact: Security

JPS-07013: The AppRole list is null/empty while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid AppRole List.
Level: 1

Type: ERROR

Impact: Security

JPS-07014: The Resource object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to pass a valid Resource object.
Level: 1

Type: ERROR

Impact: Security

JPS-07014: The Resource object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to pass a valid Resource object.
Level: 1

Type: ERROR

Impact: Security

JPS-07014: The Resource object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to pass a valid Resource object.
Level: 1

Type: ERROR

Impact: Security

JPS-07015: The PermissionSet object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid PermissionSet object.
Level: 1

Type: ERROR

Impact: Security

JPS-07015: The PermissionSet object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid PermissionSet object.
Level: 1

Type: ERROR

Impact: Security

JPS-07015: The PermissionSet object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid PermissionSet object.
Level: 1

Type: ERROR

Impact: Security

JPS-07016: The Association object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid Association object.
Level: 1

Type: ERROR

Impact: Security

JPS-07016: The Association object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid Association object.
Level: 1

Type: ERROR

Impact: Security

JPS-07016: The Association object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Ensure to provide a valid Association object.
Level: 1

Type: ERROR

Impact: Security

JPS-07017: Internal Error.

Cause: That was an internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07017: Internal Error.

Cause: That was an internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07017: Internal Error.

Cause: That was an internal error.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: ERROR

Impact: Security

JPS-07018: Application Role: "{0}" cannot be added. Reason {1} .

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07018: Application Role: "{0}" cannot be added. Reason {1} .

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07018: Application Role: "{0}" cannot be added. Reason {1} .

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07019: Permission Set: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07019: Permission Set: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07019: Permission Set: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07020: Resource: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07020: Resource: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07020: Resource: "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07021: Resource Type "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07021: Resource Type "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07021: Resource Type "{0}" cannot be added. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07022: Member: name "{0}" ,class "{1}" cannot be granted an application role: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07022: Member: name "{0}" ,class "{1}" cannot be granted an application role: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07022: Member: name "{0}" ,class "{1}" cannot be granted an application role: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07023: Resource Actions: name "{0}", actions "{1}" cannot be added in permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07023: Resource Actions: name "{0}", actions "{1}" cannot be added in permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07023: Resource Actions: name "{0}", actions "{1}" cannot be added in permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07024: Permission: "{0}" cannot be granted to grantee "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07024: Permission: "{0}" cannot be granted to grantee "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07024: Permission: "{0}" cannot be granted to grantee "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07025: Permission set: "{0}" cannot be granted to grantee "{1}". Reason {2}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07025: Permission set: "{0}" cannot be granted to grantee "{1}". Reason {2}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07025: Permission set: "{0}" cannot be granted to grantee "{1}". Reason {2}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07026: Application Role: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07026: Application Role: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07026: Application Role: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07027: Permission Set: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07027: Permission Set: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07027: Permission Set: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07028: Resource: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07028: Resource: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07028: Resource: "{0}" cannot be modified. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07029: Resource Type: "{0}" cannot be modified. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07029: Resource Type: "{0}" cannot be modified. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07029: Resource Type: "{0}" cannot be modified. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07030: Application Role: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07030: Application Role: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07030: Application Role: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07031: Permission Set: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07031: Permission Set: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07031: Permission Set: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07032: Resource: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07032: Resource: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07032: Resource: "{0}" cannot be deleted. Reason {1}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07033: Resource Type: "{0}" cannot be deleted. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07033: Resource Type: "{0}" cannot be deleted. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07033: Resource Type: "{0}" cannot be deleted. Reason {1}

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07034: Member: name "{0}", class "{1}" cannot be revoked from application role: "{2}". reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07034: Member: name "{0}", class "{1}" cannot be revoked from application role: "{2}". reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07034: Member: name "{0}", class "{1}" cannot be revoked from application role: "{2}". reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07035: Resource Actions: name "{0}", actions "{1}" cannot be deleted from permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07035: Resource Actions: name "{0}", actions "{1}" cannot be deleted from permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07035: Resource Actions: name "{0}", actions "{1}" cannot be deleted from permission set: "{2}". Reason {3}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07036: Permission: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07036: Permission: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07036: Permission: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07037: Permission set: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07037: Permission set: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07037: Permission set: "{0}" cannot be revoked from grantee: "{1}". Reason {2}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07038: Additions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07038: Additions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07038: Additions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07039: Deletions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07039: Deletions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07039: Deletions cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07040: Modifications cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07040: Modifications cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07040: Modifications cannot be read. Reason {0}.

Cause: Policy store reported an error.

Action: Check the Reason and fix the problem.
Level: 1

Type: WARNING

Impact: Security

JPS-07041: The argument "{0}" is not applicable for phase "{1}".

Cause: Extra argument provided

Action: Please provide only relavent parameters
Level: 1

Type: ERROR

Impact: Security

JPS-07041: The argument "{0}" is not applicable for phase "{1}".

Cause: Extra argument provided

Action: Please provide only relavent parameters
Level: 1

Type: ERROR

Impact: Security

JPS-07041: The argument "{0}" is not applicable for phase "{1}".

Cause: Extra argument provided

Action: Please provide only relavent parameters
Level: 1

Type: ERROR

Impact: Security

JPS-07042: Illegal value provided for argument "{0}".

Cause: Illegal value provided for an argument

Action: Please provide a legal value for the argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07042: Illegal value provided for argument "{0}".

Cause: Illegal value provided for an argument

Action: Please provide a legal value for the argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07042: Illegal value provided for argument "{0}".

Cause: Illegal value provided for an argument

Action: Please provide a legal value for the argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07043: Cannot find application policy {0}.

Cause: Could not find application policy {0}.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07043: Cannot find application policy {0}.

Cause: Could not find application policy {0}.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07043: Cannot find application policy {0}.

Cause: Could not find application policy {0}.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07044: Cannot retrieve newline application policy.

Cause: Could not retrieve newline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07044: Cannot retrieve newline application policy.

Cause: Could not retrieve newline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07044: Cannot retrieve newline application policy.

Cause: Could not retrieve newline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07045: Cannot retrieve baseline application policy.

Cause: Could not retrieve baseline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07045: Cannot retrieve baseline application policy.

Cause: Could not retrieve baseline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07045: Cannot retrieve baseline application policy.

Cause: Could not retrieve baseline application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07046: Cannot retrieve customer application policy.

Cause: Could not retrieve customer application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07046: Cannot retrieve customer application policy.

Cause: Could not retrieve customer application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07046: Cannot retrieve customer application policy.

Cause: Could not retrieve customer application policy.

Action: Check the application name passed.
Level: 1

Type: ERROR

Impact: Security

JPS-07047: This artifact is newly added in patch version.

Cause: Policy store doesn't suport metadata

Action: Update policy store
Level: 1

Type: ERROR

Impact: Security

JPS-07047: This artifact is newly added in patch version.

Cause: The required parameter was null.

Action: Enusre to provide a valid RoleCategory Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07047: This artifact is newly added in patch version.

Cause: The required parameter was null.

Action: Enusre to provide a valid RoleCategory Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07056: Addition conflicts initialization failed.

Cause: Internal Error occured when attempting to load Addition Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07056: Addition conflicts initialization failed.

Cause: Internal Error occured when attempting to load Addition Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07056: Addition conflicts initialization failed.

Cause: Internal Error occured when attempting to load Addition Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07057: Modification conflicts initialization failed.

Cause: Internal Error occured when attempting to load Modification Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07057: Modification conflicts initialization failed.

Cause: Internal Error occured when attempting to load Modification Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07057: Modification conflicts initialization failed.

Cause: Internal Error occured when attempting to load Modification Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07058: Deletion conflicts initialization failed.

Cause: Internal Error occured when attempting to load Deletion Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07058: Deletion conflicts initialization failed.

Cause: Internal Error occured when attempting to load Deletion Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07058: Deletion conflicts initialization failed.

Cause: Internal Error occured when attempting to load Deletion Conflicts from Patch Delta.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07059: Conflicting addition changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Addition conflicts are not resolved.

Action: Resolve addition conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07059: Conflicting addition changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Addition conflicts are not resolved.

Action: Resolve addition conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07059: Conflicting addition changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Addition conflicts are not resolved.

Action: Resolve addition conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07060: Conflicting modification changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Modification conflicts are not resolved.

Action: Resolve modification conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07060: Conflicting modification changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Modification conflicts are not resolved.

Action: Resolve modification conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07060: Conflicting modification changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Modification conflicts are not resolved.

Action: Resolve modification conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07061: Conflicting deletion changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07061: Conflicting deletion changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07061: Conflicting deletion changes in the patch have been identified. Silent Apply process halted. Resolve the conflicts and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07062: Additions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07062: Additions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07062: Additions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07063: Deletions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07063: Deletions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07063: Deletions Writer initialization failed for resolve.

Cause: Additions Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07064: Modifications Writer initialization failed for resolve.

Cause: Modification Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07064: Modifications Writer initialization failed for resolve.

Cause: Modification Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07064: Modifications Writer initialization failed for resolve.

Cause: Modification Writer initialization failed for resolve.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07065: Dependency artifact {0} is not resolved for artifact {1}.

Cause: Dependency artifact {0} is not resolved for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07065: Dependency artifact {0} is not resolved for artifact {1}.

Cause: Dependency artifact {0} is not resolved for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07065: Dependency artifact {0} is not resolved for artifact {1}.

Cause: Dependency artifact {0} is not resolved for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07066: Dependency artifact {0} resolution is not valid for artifact {1}.

Cause: Dependency artifact {0} resolution is not valid for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07066: Dependency artifact {0} resolution is not valid for artifact {1}.

Cause: Dependency artifact {0} resolution is not valid for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07066: Dependency artifact {0} resolution is not valid for artifact {1}.

Cause: Dependency artifact {0} resolution is not valid for artifact {1}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07067: Artifact not resolved {0}.

Cause: Artifact not resolved {0}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07067: Artifact not resolved {0}.

Cause: Artifact not resolved {0}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07067: Artifact not resolved {0}.

Cause: Artifact not resolved {0}.

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07069: Deletion of member {0} of permission set {1} renders the permission set empty.

Cause: Deletion of member will render Permission set empty

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07069: Deletion of member {0} of permission set {1} renders the permission set empty.

Cause: Deletion of member will render Permission set empty

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07069: Deletion of member {0} of permission set {1} renders the permission set empty.

Cause: Deletion of member will render Permission set empty

Action: Check the resolutions.
Level: 1

Type: ERROR

Impact: Security

JPS-07070: The argument {0} is not passed

Cause: The required argument is not passed.

Action: Provide the required argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07070: The argument {0} is not passed

Cause: The required argument is not passed.

Action: Provide the required argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07070: The argument {0} is not passed

Cause: The required argument is not passed.

Action: Provide the required argument.
Level: 1

Type: ERROR

Impact: Security

JPS-07071: Deletion Changes in the patch have been identified. Applying the changes will permanently delete policy store artifacts. Silent Apply process halted. Review the changes and Apply the patch.

Cause: Addition Safe changes and Modification Safe changes have been applied.However, Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07071: Deletion Changes in the patch have been identified. Applying the changes will permanently delete policy store artifacts. Silent Apply process halted. Review the changes and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07071: Deletion Changes in the patch have been identified. Applying the changes will permanently delete policy store artifacts. Silent Apply process halted. Review the changes and Apply the patch.

Cause: Deletion conflicts are not resolved.

Action: Resolve deletion conflicts.
Level: 1

Type: ERROR

Impact: Security

JPS-07077: Cannot generate report. Reason {0}

Cause: Report generation failed.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07077: Cannot generate report. Reason {0}

Cause: Report generation failed.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07077: Cannot generate report. Reason {0}

Cause: Report generation failed.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Security

JPS-07078: Report file {0} path is invalid.

Cause: Report file specified is not a valid file path.

Action: Specify a valid file path.
Level: 1

Type: ERROR

Impact: Security

JPS-07078: Report file {0} path is invalid.

Cause: Report file specified is not a valid file path.

Action: Specify a valid file path.
Level: 1

Type: ERROR

Impact: Security

JPS-07078: Report file {0} path is invalid.

Cause: Report file specified is not a valid file path.

Action: Specify a valid file path.
Level: 1

Type: ERROR

Impact: Security

JPS-07079: Report file {0} cannot be created in the given directory.

Cause: The directory doesn't have write permission.

Action: Specify a directory which has write permission.
Level: 1

Type: ERROR

Impact: Security

JPS-07079: Report file {0} cannot be created in the given directory.

Cause: The directory doesn't have write permission.

Action: Specify a directory which has write permission.
Level: 1

Type: ERROR

Impact: Security

JPS-07079: Report file {0} cannot be created in the given directory.

Cause: The directory doesn't have write permission.

Action: Specify a directory which has write permission.
Level: 1

Type: ERROR

Impact: Security

JPS-07080: Report file {0} already exists.

Cause: Report file exists.

Action: Specify a non existing file.
Level: 1

Type: ERROR

Impact: Security

JPS-07080: Report file {0} already exists.

Cause: Report file exists.

Action: Specify a non existing file.
Level: 1

Type: ERROR

Impact: Security

JPS-07080: Report file {0} already exists.

Cause: Report file exists.

Action: Specify a non existing file.
Level: 1

Type: ERROR

Impact: Security

JPS-07081: Could not find policystore in "{0}" jps context in production config.

Cause: Could not find policystore in {0} jps context in production config.

Action: Provide a service instance for policystore in the {0} jps context in production config.
Level: 1

Type: ERROR

Impact: Security

JPS-07082: Loading base policy store complete in {0}.

Cause: Loading base policy store complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07083: Initializing Application Policy Comparator complete in {0}.

Cause: Initializing Application Policy Comparator complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07084: Loading new policy store complete in {0}.

Cause: Loading new policy store complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07085: Oracle Delta calculation complete in {0}.

Cause: Oracle Delta calculation complete in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07086: Production application policy store object created in {0}.

Cause: Production application policy store object created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07087: Customer delta created in {0}.

Cause: Customer delta created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07088: Patch delta created in {0}.

Cause: Patch delta created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07089: Report File created in {0}.

Cause: Report file created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07090: Customer delta files created in {0}.

Cause: Customer delta files created in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07093: The Role category object is null while persisting to Addition Safe Changes.

Cause: The required parameter was null.

Action: Enusre to provide a valid RoleCategory Object.
Level: 1

Type: ERROR

Impact: Security

JPS-07101: Beginning to apply additions...

Cause: Beginning to apply additions...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07102: Additions applied in {0}

Cause: Additions applied in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07103: Beginning to apply modifications...

Cause: Beginning to apply modifications...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07104: Modifications applied in {0}

Cause: Modifications applied in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07105: Beginning to apply deletions...

Cause: Beginning to apply deletions...

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07106: Deletions applied in {0}

Cause: Deletions applied in {0}.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07107: {0} Application roles added.

Cause: {0} Application roles added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07108: {0} Role categories added.

Cause: {0} Role categories added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07109: {0} Resource type entries added.

Cause: {0} Resource type entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07110: {0} Resource entries added.

Cause: {0} Resource entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07111: {0} Permission set entries added.

Cause: {0} Permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07112: {0} Application role membership entries added.

Cause: {0} Application role membership entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07113: {0} Application role categories entries added.

Cause: {0} Application role categories entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07114: {0} Resources to permission sets added.

Cause: {0} Resources to permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07115: {0} Permission set membership entries added.

Cause: {0} Permission set membership entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07116: {0} Grantee to permission set entries added.

Cause: {0} Grantee to permission set entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07117: {0} Grantee to permission membership entries added.

Cause: {0} Grantee to permission membership entries added.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07118: {0} Application roles modified.

Cause: {0} Application roles modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07119: {0} Role categories modified.

Cause: {0} Role categories modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07120: {0} Resource type entries modified.

Cause: {0} Resource type entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07121: {0} Resource entries modified.

Cause: {0} Resource entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07122: {0} Permission set entries modified.

Cause: {0} Permission set entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07123: {0} Resources to permission sets added.

Cause: {0} Resources to permission set entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07124: {0} Grantee to permission membership entries modified.

Cause: {0} Grantee to permission membership entries modified.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07125: Dissociated {0} members from application roles.

Cause: Deassociated {0} members and application roles.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07126: Dissociated {0} categories from application roles.

Cause: Deassociated {0} categories and application roles.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07127: Dissociated {0} resources from permission sets.

Cause: Deassociated {0} resources and permission sets.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07128: Revoked {0} permission sets from grantees.

Cause: Revoked {0} permission sets from grantees.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07129: Revoked {0} permissions from grantees.

Cause: Revoked {0} permissions from grantees.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07130: {0} Application roles deleted.

Cause: {0} Application roles deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07131: {0} Role categories deleted.

Cause: {0} Role categories deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07132: {0} Permission set entries deleted.

Cause: {0} Permission set entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07133: {0} Resource entries deleted.

Cause: {0} Resource entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07134: {0} Resource type entries deleted.

Cause: {0} Resource type entries deleted.

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07135: Progress - Apply Additions ----------------------- {0}% Done

Cause: Progress...Apply additions

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07136: Progress - Apply Modifications -------------------- {0}% Done

Cause: Progress...Apply modifications

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07137: Progress - Apply Deletions ----------------------- {0}% Done

Cause: Progress...Apply deletions

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07138: Dissociated of members from application roles (skipped, not applicable).

Cause: Dissociation of members from application roles (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07139: Dissociation of categories from application roles (skipped, not applicable)

Cause: Disassociation of categories from application roles (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07140: Dissociation of resources from permission sets (skipped, not applicable).

Cause: Disassociation of resources from permission sets (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07141: Revoke of permission sets from grantees (skipped, not applicable).

Cause: Revoke of permission sets from grantees (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07142: Revoke of permissions from grantees (skipped, not applicable).

Cause: Revoke of permissions from grantees (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07143: Application roles deletion (skipped, not applicable).

Cause: Deletion of application roles (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07144: Role categories deletion (skipped, not applicable).

Cause: Deletion of role categories (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07145: Permission set entries deletion (skipped, not applicable).

Cause: Deletion of permission sets (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07146: Resource entries deletion (skipped, not applicable)

Cause: Deletion of resources (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07147: Resource type entries deletion (skipped, not applicable).

Cause: Deletion of resource types (skipped, not applicable)

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07148: Deletions not applicable when the silent flag is on.

Cause: Deletions not applicable when the silent flag is enabled

Action: No actions are required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07150: You can set only one of the two flags - {0} or {1} but not both.

Cause: Dual flags have been set. This is not permitted

Action: Set only one of the two flags - {0} or {1}
Level: 1

Type: ERROR

Impact: Security

JPS-07151: role member {0} of application role: {1} not found.

Cause: role member {0} of application role: {1} not found

Action: Add back role member: {0} or run patching analysis again
Level: 1

Type: ERROR

Impact: Security

JPS-07152: Name collisions have been identified. The patch process halted. Eliminate the collisions by renaming or removing artifacts in production store. Please find artifacts which have name collision between production store and patch version in file {0}.

Cause: Name collisions exist.

Action: Eliminate the name collisions by renaming or removing the policy artifacts in production store.
Level: 1

Type: ERROR

Impact: Security

JPS-07500: Trust protocol {0} is not supported.

Cause: Requested trust protocol is not supported

Action: Provide correct trust protocol
Level: 1

Type: ERROR

Impact: Security

JPS-07500: Trust protocol {0} is not supported.

Cause: Requested trust protocol is not supported

Action: Provide correct trust protocol
Level: 1

Type: ERROR

Impact: Security

JPS-07500: Trust protocol {0} is not supported.

Cause: Requested trust protocol is not supported

Action: Provide correct trust protocol
Level: 1

Type: ERROR

Impact: Security

JPS-07501: Token context is invalid.

Cause: Token context object is empty or does not contain required parameters

Action: Check token context object contains required parameter
Level: 1

Type: ERROR

Impact: Security

JPS-07501: Token context is invalid.

Cause: Token context object is empty or does not contain required parameters

Action: Check token context object contains required parameter
Level: 1

Type: ERROR

Impact: Security

JPS-07501: Token context is invalid.

Cause: Token context object is empty or does not contain required parameters

Action: Check token context object contains required parameter
Level: 1

Type: ERROR

Impact: Security

JPS-07502: Trust Service token provider {0} is not found.

Cause: Token provider not configured in the jps-config.xml file

Action: Check jps-config.xml file and verify that requested token provider is correctly configured
Level: 1

Type: ERROR

Impact: Security

JPS-07502: Trust Service token provider {0} is not found.

Cause: Token provider not configured in the jps-config.xml file

Action: Check jps-config.xml file and verify that requested token provider is correctly configured
Level: 1

Type: ERROR

Impact: Security

JPS-07502: Trust Service token provider {0} is not found.

Cause: Token provider not configured in the jps-config.xml file

Action: Check jps-config.xml file and verify that requested token provider is correctly configured
Level: 1

Type: ERROR

Impact: Security

JPS-07503: Trust Service token provider class name {0}.

Cause: Token provider class loading

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07503: Trust Service token provider class name {0}.

Cause: Token provider class loading

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07503: Trust Service token provider class name {0}.

Cause: Token provider class loading

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07504: Trust Service Keystore initialization failed.

Cause: Keystore is is missing or not configured correctly

Action: Check the keystore and ensure that necessary certificates and keys are present
Level: 1

Type: ERROR

Impact: Security

JPS-07504: Trust Service Keystore initialization failed.

Cause: Keystore is is missing or not configured correctly

Action: Check the keystore and ensure that necessary certificates and keys are present
Level: 1

Type: ERROR

Impact: Security

JPS-07504: Trust Service Keystore initialization failed.

Cause: Keystore is is missing or not configured correctly

Action: Check the keystore and ensure that necessary certificates and keys are present
Level: 1

Type: ERROR

Impact: Security

JPS-07505: Trust service provider protocol {0}

Cause: Trust Service provider protocol information

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07505: Trust service provider protocol {0}

Cause: Trust Service provider protocol information

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07505: Trust service provider protocol {0}

Cause: Trust Service provider protocol information

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07506: Token context creation failed.

Cause: Incorrct protocol or associated provider configuration.

Action: Check protocol and associated provider configuration
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07506: Token context creation failed.

Cause: Incorrct protocol or associated provider configuration.

Action: Check protocol and associated provider configuration
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07506: Token context creation failed.

Cause: Incorrct protocol or associated provider configuration.

Action: Check protocol and associated provider configuration
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07507: Token issue operation

Cause: Trust service token issue opertion.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07507: Token issue operation

Cause: Trust service token issue opertion.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07507: Token issue operation

Cause: Trust service token issue opertion.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07508: Token issue operation failed.

Cause: Trust service token issue opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07508: Token issue operation failed.

Cause: Trust service token issue opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07508: Token issue operation failed.

Cause: Trust service token issue opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07509: Invalid token operation

Cause: Invalid Trust Service token opertion.

Action: Check invoked operation name
Level: 1

Type: ERROR

Impact: Security

JPS-07509: Invalid token operation

Cause: Invalid Trust Service token opertion.

Action: Check invoked operation name
Level: 1

Type: ERROR

Impact: Security

JPS-07509: Invalid token operation

Cause: Invalid Trust Service token opertion.

Action: Check invoked operation name
Level: 1

Type: ERROR

Impact: Security

JPS-07510: Token validate operation.

Cause: Trust Service validate token opertion.

Action: No action required
Level: 1

Type: ERROR

Impact: Security

JPS-07510: Token validate operation.

Cause: Trust Service validate token opertion.

Action: No action required
Level: 1

Type: ERROR

Impact: Security

JPS-07510: Token validate operation.

Cause: Trust Service validate token opertion.

Action: No action required
Level: 1

Type: ERROR

Impact: Security

JPS-07511: Validate operation failed.

Cause: Trust service token validate opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07511: Validate operation failed.

Cause: Trust service token validate opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07511: Validate operation failed.

Cause: Trust service token validate opertion failed.

Action: Check provider configuration
Level: 1

Type: ERROR

Impact: Security

JPS-07512: Missing token issuer identity.

Cause: Token issuer identity missing.

Action: Provide token issuer identity
Level: 1

Type: ERROR

Impact: Security

JPS-07512: Missing token issuer identity.

Cause: Token issuer identity missing.

Action: Provide token issuer identity
Level: 1

Type: ERROR

Impact: Security

JPS-07512: Missing token issuer identity.

Cause: Token issuer identity missing.

Action: Provide token issuer identity
Level: 1

Type: ERROR

Impact: Security

JPS-07513: Invalid subject confirmation method.

Cause: Invalid subject confirmation method.

Action: Provide correct subject confirmation method
Level: 1

Type: ERROR

Impact: Security

JPS-07513: Invalid subject confirmation method.

Cause: Invalid subject confirmation method.

Action: Provide correct subject confirmation method
Level: 1

Type: ERROR

Impact: Security

JPS-07513: Invalid subject confirmation method.

Cause: Invalid subject confirmation method.

Action: Provide correct subject confirmation method
Level: 1

Type: ERROR

Impact: Security

JPS-07514: Token audience restriction condition check failed.

Cause: Invalid token audience condition.

Action: Check the audience condition
Level: 1

Type: ERROR

Impact: Security

JPS-07514: Token audience restriction condition check failed.

Cause: Invalid token audience condition.

Action: Check the audience condition
Level: 1

Type: ERROR

Impact: Security

JPS-07514: Token audience restriction condition check failed.

Cause: Invalid token audience condition.

Action: Check the audience condition
Level: 1

Type: ERROR

Impact: Security

JPS-07515: Token signature validation failed.

Cause: Invalid token signature.

Action: Check token integrity and verify signature using correct certificate
Level: 1

Type: ERROR

Impact: Security

JPS-07515: Token signature validation failed.

Cause: Invalid token signature.

Action: Check token integrity and verify signature using correct certificate
Level: 1

Type: ERROR

Impact: Security

JPS-07515: Token signature validation failed.

Cause: Invalid token signature.

Action: Check token integrity and verify signature using correct certificate
Level: 1

Type: ERROR

Impact: Security

JPS-07516: Invalid token.

Cause: Invalid token.

Action: Check token integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07516: Invalid token.

Cause: Invalid token.

Action: Check token integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07516: Invalid token.

Cause: Invalid token.

Action: Check token integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07517: Input token is not an instance of GenericToken class.

Cause: Input token is not an instance of GenericToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07517: Input token is not an instance of GenericToken class.

Cause: Input token is not an instance of GenericToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07517: Input token is not an instance of GenericToken class.

Cause: Input token is not an instance of GenericToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07518: Input token is not an instance of UsernameToken class

Cause: Input token is not an instance of UsernameToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07518: Input token is not an instance of UsernameToken class

Cause: Input token is not an instance of UsernameToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07518: Input token is not an instance of UsernameToken class

Cause: Input token is not an instance of UsernameToken class.

Action: Check the token object class
Level: 1

Type: ERROR

Impact: Security

JPS-07519: Setting subject conformation method failed.

Cause: Invalid token object.

Action: Check the token object
Level: 1

Type: ERROR

Impact: Security

JPS-07519: Setting subject conformation method failed.

Cause: Invalid token object.

Action: Check the token object
Level: 1

Type: ERROR

Impact: Security

JPS-07519: Setting subject conformation method failed.

Cause: Invalid token object.

Action: Check the token object
Level: 1

Type: ERROR

Impact: Security

JPS-07520: Token signing failed.

Cause: Token signing key is unavailable.

Action: Check the keystore and verify that signing key is present
Level: 1

Type: ERROR

Impact: Security

JPS-07520: Token signing failed.

Cause: Token signing key is unavailable.

Action: Check the keystore and verify that signing key is present
Level: 1

Type: ERROR

Impact: Security

JPS-07520: Token signing failed.

Cause: Token signing key is unavailable.

Action: Check the keystore and verify that signing key is present
Level: 1

Type: ERROR

Impact: Security

JPS-07521: Token signature is not available.

Cause: Unsigned token.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07521: Token signature is not available.

Cause: Unsigned token.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07521: Token signature is not available.

Cause: Unsigned token.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07522: Token is not valid yet {0}

Cause: Token is not valid yet.

Action: Check the token validity start date.
Level: 1

Type: ERROR

Impact: Security

JPS-07522: Token is not valid yet {0}

Cause: Token is not valid yet.

Action: Check the token validity start date.
Level: 1

Type: ERROR

Impact: Security

JPS-07522: Token is not valid yet {0}

Cause: Token is not valid yet.

Action: Check the token validity start date.
Level: 1

Type: ERROR

Impact: Security

JPS-07523: Token has expired {0}

Cause: Token has expired.

Action: Check the token validity end date.
Level: 1

Type: ERROR

Impact: Security

JPS-07523: Token has expired {0}

Cause: Token has expired.

Action: Check the token validity end date.
Level: 1

Type: ERROR

Impact: Security

JPS-07523: Token has expired {0}

Cause: Token has expired.

Action: Check the token validity end date.
Level: 1

Type: ERROR

Impact: Security

JPS-07524: Certificate is unavailable {0}

Cause: Certificate is not available.

Action: Check the keystore and ensure that the certificate is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07524: Certificate is unavailable {0}

Cause: Certificate is not available.

Action: Check the keystore and ensure that the certificate is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07524: Certificate is unavailable {0}

Cause: Certificate is not available.

Action: Check the keystore and ensure that the certificate is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07525: Private key is unavailable

Cause: Private key is not available.

Action: Check the keystore and ensure that the private key is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07525: Private key is unavailable

Cause: Private key is not available.

Action: Check the keystore and ensure that the private key is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07525: Private key is unavailable

Cause: Private key is not available.

Action: Check the keystore and ensure that the private key is present.
Level: 1

Type: ERROR

Impact: Security

JPS-07526: Initializing provider

Cause: Provider is initiliazing.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07526: Initializing provider

Cause: Provider is initiliazing.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07526: Initializing provider

Cause: Provider is initiliazing.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07527: Shutting down provider

Cause: Provider is shutting down.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07527: Shutting down provider

Cause: Provider is shutting down.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07527: Shutting down provider

Cause: Provider is shutting down.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07528: Received unknown token type {0}

Cause: Received token type is unknown.

Action: Check the provided token.
Level: 1

Type: WARNING

Impact: Security

JPS-07528: Received unknown token type {0}

Cause: Received token type is unknown.

Action: Check the provided token.
Level: 1

Type: WARNING

Impact: Security

JPS-07528: Received unknown token type {0}

Cause: Received token type is unknown.

Action: Check the provided token.
Level: 1

Type: WARNING

Impact: Security

JPS-07529: Received unknown token class {0}

Cause: Token class is unknown.

Action: Check the token class.
Level: 1

Type: WARNING

Impact: Security

JPS-07529: Received unknown token class {0}

Cause: Token class is unknown.

Action: Check the token class.
Level: 1

Type: WARNING

Impact: Security

JPS-07529: Received unknown token class {0}

Cause: Token class is unknown.

Action: Check the token class.
Level: 1

Type: WARNING

Impact: Security

JPS-07530: Invalid token type or token not found

Cause: Invalid token authentication type specified.

Action: Check the token authentication type.
Level: 1

Type: WARNING

Impact: Security

JPS-07530: Invalid token type or token not found

Cause: Invalid token authentication type specified.

Action: Check the token authentication type.
Level: 1

Type: WARNING

Impact: Security

JPS-07530: Invalid token type or token not found

Cause: Invalid token authentication type specified.

Action: Check the token authentication type.
Level: 1

Type: WARNING

Impact: Security

JPS-07531: Input token is not an instance of {0}

Cause: Specified insance is not correct.

Action: Check the instance type validity.
Level: 1

Type: WARNING

Impact: Security

JPS-07531: Input token is not an instance of {0}

Cause: Specified insance is not correct.

Action: Check the instance type validity.
Level: 1

Type: WARNING

Impact: Security

JPS-07531: Input token is not an instance of {0}

Cause: Specified insance is not correct.

Action: Check the instance type validity.
Level: 1

Type: WARNING

Impact: Security

JPS-07532: Instance of {0} is invalid

Cause: Specified instance is invalid.

Action: Check the specified instance and ensure that it is correct
Level: 1

Type: WARNING

Impact: Security

JPS-07532: Instance of {0} is invalid

Cause: Specified instance is invalid.

Action: Check the specified instance and ensure that it is correct
Level: 1

Type: WARNING

Impact: Security

JPS-07532: Instance of {0} is invalid

Cause: Specified instance is invalid.

Action: Check the specified instance and ensure that it is correct
Level: 1

Type: WARNING

Impact: Security

JPS-07533: Received empty token byte array

Cause: Given token is empty.

Action: Check the token content and ensure that it is not empty.
Level: 1

Type: ERROR

Impact: Security

JPS-07533: Received empty token byte array

Cause: Given token is empty.

Action: Check the token content and ensure that it is not empty.
Level: 1

Type: ERROR

Impact: Security

JPS-07533: Received empty token byte array

Cause: Given token is empty.

Action: Check the token content and ensure that it is not empty.
Level: 1

Type: ERROR

Impact: Security

JPS-07534: Trust service configuration is not valid

Cause: Invalid configuration parameters.

Action: Check the configuration parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-07534: Trust service configuration is not valid

Cause: Invalid configuration parameters.

Action: Check the configuration parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-07534: Trust service configuration is not valid

Cause: Invalid configuration parameters.

Action: Check the configuration parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-07535: Using {0} Trust service configuration

Cause: Configuration type used by Trust Service

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07535: Using {0} Trust service configuration

Cause: Configuration type used by Trust Service

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07535: Using {0} Trust service configuration

Cause: Configuration type used by Trust Service

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07536: Token credential missing

Cause: Token signing or validation credential missing.

Action: Provide correct credential.
Level: 1

Type: ERROR

Impact: Security

JPS-07536: Token credential missing

Cause: Token signing or validation credential missing.

Action: Provide correct credential.
Level: 1

Type: ERROR

Impact: Security

JPS-07536: Token credential missing

Cause: Token signing or validation credential missing.

Action: Provide correct credential.
Level: 1

Type: ERROR

Impact: Security

JPS-07537: Token signature missing

Cause: Token signature missing.

Action: Check the token for integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07537: Token signature missing

Cause: Token signature missing.

Action: Check the token for integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07537: Token signature missing

Cause: Token signature missing.

Action: Check the token for integrity.
Level: 1

Type: ERROR

Impact: Security

JPS-07538: The input token is not specified

Cause: Input token not provided.

Action: Check if the token has been provided.
Level: 1

Type: ERROR

Impact: Security

JPS-07538: The input token is not specified

Cause: Input token not provided.

Action: Check if the token has been provided.
Level: 1

Type: ERROR

Impact: Security

JPS-07538: The input token is not specified

Cause: Input token not provided.

Action: Check if the token has been provided.
Level: 1

Type: ERROR

Impact: Security

JPS-07539: Token signing method is not specified

Cause: Token signing algorithm parameter missing.

Action: Check the token signing algorithm parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07539: Token signing method is not specified

Cause: Token signing algorithm parameter missing.

Action: Check the token signing algorithm parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07539: Token signing method is not specified

Cause: Token signing algorithm parameter missing.

Action: Check the token signing algorithm parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07540: Token signing method is invalid

Cause: Token signing algorithm parameter invalid

Action: Check the specified token signing algorithm.
Level: 1

Type: ERROR

Impact: Security

JPS-07540: Token signing method is invalid

Cause: Token signing algorithm parameter invalid

Action: Check the specified token signing algorithm.
Level: 1

Type: ERROR

Impact: Security

JPS-07540: Token signing method is invalid

Cause: Token signing algorithm parameter invalid

Action: Check the specified token signing algorithm.
Level: 1

Type: ERROR

Impact: Security

JPS-07541: Token signing private key is not specified

Cause: Token signing private key missing.

Action: Check the token signing private key parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07541: Token signing private key is not specified

Cause: Token signing private key missing.

Action: Check the token signing private key parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07541: Token signing private key is not specified

Cause: Token signing private key missing.

Action: Check the token signing private key parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07542: Token signing certificate is not specified

Cause: Token signing certificate missing.

Action: Check the token signing certificate parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07542: Token signing certificate is not specified

Cause: Token signing certificate missing.

Action: Check the token signing certificate parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07542: Token signing certificate is not specified

Cause: Token signing certificate missing.

Action: Check the token signing certificate parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07543: Token signing credential is not specified

Cause: Token signing credential missing.

Action: Check the token signing credential parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07543: Token signing credential is not specified

Cause: Token signing credential missing.

Action: Check the token signing credential parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07543: Token signing credential is not specified

Cause: Token signing credential missing.

Action: Check the token signing credential parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07544: The specified token type is invalid

Cause: The token type is not supported.

Action: Check the token type parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07544: The specified token type is invalid

Cause: The token type is not supported.

Action: Check the token type parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07544: The specified token type is invalid

Cause: The token type is not supported.

Action: Check the token type parameter.
Level: 1

Type: ERROR

Impact: Security

JPS-07545: Invalid TokenContext class

Cause: Internal Error. The correct TokenContext class is not created.

Action: Provide the correct TokenProvider class in trust configurations.
Level: 1

Type: ERROR

Impact: Security

JPS-07546: Token cannot be issued for virtual or anonymous user

Cause: Trust token cannot be issued for anonymous or virtual users

Action: Ensure usage of Trust service is limited to users present in configured identity store.
Level: 1

Type: ERROR

Impact: Security

JPS-07600: Application policy for stripe name {0} not found. Nothing to undeploy

Cause: No associated application policies

Action: Check application policy setup or contact system administrator
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07601: Complete staging offline deployment for application {0} in {1}

Cause: Complete staging offline deployment for application {0} in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07601: Complete staging offline deployment for application {0} in {1}

Cause: Complete staging offline deployment for application {0} in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07601: Complete staging offline deployment for application {0} in {1}

Cause: Complete staging offline deployment for application {0} in {1}

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-07602: Removal of application policy failed. Reason: {0}.

Cause: Exception in removing application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-07602: Removal of application policy failed. Reason: {0}.

Cause: Exception in removing application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-07602: Removal of application policy failed. Reason: {0}.

Cause: Exception in removing application policy

Action: Check application policy setup or contact system administrator
Level: 1

Type: WARNING

Impact: Security

JPS-07603: Cannot purge changelog. Reason {0}.

Cause: Purge changelog failed.

Action: Check policystore configuration.
Level: 1

Type: ERROR

Impact: Security

JPS-07604: Wrong policy combining algorithm name {0} is used.

Cause: wrong policy combining algorithm name was used

Action: Check combining algorithm name being used
Level: 1

Type: WARNING

Impact: Security

JPS-07605: Unsupported policy combining algorithm name {0} is used.

Cause: Unsupported policy combining algorithm name was used

Action: Check combining algorithm name being used
Level: 1

Type: WARNING

Impact: Security

JPS-07606: Cannot clean applications. Reason {0}.

Cause: Clean applications failed.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-07607: {0} is used in source, but it is not supported by destination policy store.

Cause: Source contains policy artifacts that is not supported by destination policy store

Action: Make sure source only contain policy artifacts which are compatible with destination policy store
Level: 1

Type: WARNING

Impact: Security

JPS-08000: Subject object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Subject.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08000: Subject object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Subject.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08000: Subject object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Subject.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08001: Action object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Action.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08001: Action object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Action.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08001: Action object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Action.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08002: Resource object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Resource.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08002: Resource object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Resource.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08002: Resource object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Resource.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08003: Environment object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Environment.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08003: Environment object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Environment.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08003: Environment object {0} is not supported.

Cause: Specified Object type is not supported by the provider for Environment.

Action: Check the document for supported object types.
Level: 1

Type: ERROR

Impact: Security

JPS-08004: Invalid resource string: {0}.

Cause: The resource string is invalid.

Action: Check the document for the resource string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08004: Invalid resource string: {0}.

Cause: The resource string is invalid.

Action: Check the document for the resource string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08004: Invalid resource string: {0}.

Cause: The resource string is invalid.

Action: Check the document for the resource string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08005: Subject cannot be null.

Cause: The subject is null.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08005: Subject cannot be null.

Cause: The subject is null.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08005: Subject cannot be null.

Cause: The subject is null.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08006: Action cannot be null.

Cause: The action is null.

Action: Use a valid action.
Level: 1

Type: ERROR

Impact: Security

JPS-08006: Action cannot be null.

Cause: The action is null.

Action: Use a valid action.
Level: 1

Type: ERROR

Impact: Security

JPS-08006: Action cannot be null.

Cause: The action is null.

Action: Use a valid action.
Level: 1

Type: ERROR

Impact: Security

JPS-08007: Resource cannot be null.

Cause: The resource is null.

Action: Use a valid resource.
Level: 1

Type: ERROR

Impact: Security

JPS-08007: Resource cannot be null.

Cause: The resource is null.

Action: Use a valid resource.
Level: 1

Type: ERROR

Impact: Security

JPS-08007: Resource cannot be null.

Cause: The resource is null.

Action: Use a valid resource.
Level: 1

Type: ERROR

Impact: Security

JPS-08008: Action list cannot be null or empty.

Cause: The action list is null or empty.

Action: Use a valid action list.
Level: 1

Type: ERROR

Impact: Security

JPS-08008: Action list cannot be null or empty.

Cause: The action list is null or empty.

Action: Use a valid action list.
Level: 1

Type: ERROR

Impact: Security

JPS-08008: Action list cannot be null or empty.

Cause: The action list is null or empty.

Action: Use a valid action list.
Level: 1

Type: ERROR

Impact: Security

JPS-08009: Resource list cannot be null or empty.

Cause: The resource list is null or empty.

Action: Use a valid resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08009: Resource list cannot be null or empty.

Cause: The resource list is null or empty.

Action: Use a valid resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08009: Resource list cannot be null or empty.

Cause: The resource list is null or empty.

Action: Use a valid resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08010: The size of action list and resource list is different.

Cause: The size of action list and resource list is different.

Action: The size of action list should be identical to the size of resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08010: The size of action list and resource list is different.

Cause: The size of action list and resource list is different.

Action: The size of action list should be identical to the size of resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08010: The size of action list and resource list is different.

Cause: The size of action list and resource list is different.

Action: The size of action list should be identical to the size of resource list.
Level: 1

Type: ERROR

Impact: Security

JPS-08011: Subject object {0} is not a valid subject on platform {1}.

Cause: The subject object is not a valid subject on current platform.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08011: Subject object {0} is not a valid subject on platform {1}.

Cause: The subject object is not a valid subject on current platform.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08011: Subject object {0} is not a valid subject on platform {1}.

Cause: The subject object is not a valid subject on current platform.

Action: Use a valid subject.
Level: 1

Type: ERROR

Impact: Security

JPS-08012: Scope cannot be null or empty.

Cause: Scope is null or empty.

Action: Use a valid scope.
Level: 1

Type: ERROR

Impact: Security

JPS-08012: Scope cannot be null or empty.

Cause: Scope is null or empty.

Action: Use a valid scope.
Level: 1

Type: ERROR

Impact: Security

JPS-08012: Scope cannot be null or empty.

Cause: Scope is null or empty.

Action: Use a valid scope.
Level: 1

Type: ERROR

Impact: Security

JPS-08013: Query Type cannot be null.

Cause: Query Type is null.

Action: Use a valid Query Type.
Level: 1

Type: ERROR

Impact: Security

JPS-08013: Query Type cannot be null.

Cause: Query Type is null.

Action: Use a valid Query Type.
Level: 1

Type: ERROR

Impact: Security

JPS-08013: Query Type cannot be null.

Cause: Query Type is null.

Action: Use a valid Query Type.
Level: 1

Type: ERROR

Impact: Security

JPS-08014: Invalid scope string: {0}.

Cause: The scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08014: Invalid scope string: {0}.

Cause: The scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08014: Invalid scope string: {0}.

Cause: The scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08015: Invalid search scope string: {0}.

Cause: The search scope in scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08015: Invalid search scope string: {0}.

Cause: The search scope in scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08015: Invalid search scope string: {0}.

Cause: The search scope in scope string is invalid.

Action: Check the document for the scope string format.
Level: 1

Type: ERROR

Impact: Security

JPS-08016: An error has occurred while processing the PepResponse result.

Cause: An error has occurred while processing the PepResponse results.

Action: Check the policy setup and client code.
Level: 1

Type: ERROR

Impact: Security

JPS-08016: An error has occurred while processing the PepResponse result.

Cause: An error has occurred while processing the PepResponse results.

Action: Check the policy setup and client code.
Level: 1

Type: ERROR

Impact: Security

JPS-08016: An error has occurred while processing the PepResponse result.

Cause: An error has occurred while processing the PepResponse results.

Action: Check the policy setup and client code.
Level: 1

Type: ERROR

Impact: Security

JPS-08017: Invalid resource string: {0}. Please provide a fully qualified resource string.

Cause: Fully qualified resource string is required.

Action: Please specify application ID, resource type and resource name.
Level: 1

Type: ERROR

Impact: Security

JPS-08017: Invalid resource string: {0}. Please provide a fully qualified resource string.

Cause: Fully qualified resource string is required.

Action: Please specify application ID, resource type and resource name.
Level: 1

Type: ERROR

Impact: Security

JPS-08017: Invalid resource string: {0}. Please provide a fully qualified resource string.

Cause: Fully qualified resource string is required.

Action: Please specify application ID, resource type and resource name.
Level: 1

Type: ERROR

Impact: Security

JPS-08018: The configured policy provider {0} does not implement AzPolicy interface.

Cause: The configured policy provider does not implement AzPolicy interface.

Action: You must configure policy provider that implements AzPolicy interface, e.g. by calling Policy.setPolicy().
Level: 1

Type: ERROR

Impact: Security

JPS-08018: The configured policy provider {0} does not implement AzPolicy interface.

Cause: The configured policy provider does not implement AzPolicy interface.

Action: You must configure policy provider that implements AzPolicy interface, e.g. by calling Policy.setPolicy().
Level: 1

Type: ERROR

Impact: Security

JPS-08018: The configured policy provider {0} does not implement AzPolicy interface.

Cause: The configured policy provider does not implement AzPolicy interface.

Action: You must configure policy provider that implements AzPolicy interface, e.g. by calling Policy.setPolicy().
Level: 1

Type: ERROR

Impact: Security

JPS-08019: Requested operation is not supported.

Cause: Requested operation is not supported.

Action: Do not invoke unsupported operation.
Level: 1

Type: ERROR

Impact: Security

JPS-08020: The authorization service instance is invalid.

Cause: The authorization service instance is invalid.

Action: Check the service instance and ensure that is a supported authorization service instance.
Level: 1

Type: ERROR

Impact: Security

JPS-08021: The input configuration parameter is invalid.

Cause: The input configuration parameter is invalid.

Action: Check the configuration parameter validity.
Level: 1

Type: ERROR

Impact: Security

JPS-08022: Incorrect authorization service instance type.

Cause: Incorrect authorization service instance type.

Action: Check the authorization service instance type.
Level: 1

Type: ERROR

Impact: Security

JPS-08023: The environment parameter is missing.

Cause: The environment paramater is missing.

Action: Check the environment paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08024: Policy context parameter is missing.

Cause: Policy context parameter is missing.

Action: Check the policy context paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08025: Session context parameter is missing.

Cause: Session context parameter is missing.

Action: Check the session paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08026: Database connection parameter is missing.

Cause: Database connection parameter is missing or not a right type.

Action: Check the database connection paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08027: Security predicate parameter is missing.

Cause: Security predicate parameter is missing.

Action: Check the security predicate paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08028: Cannot find appName attribute in resource collection.

Cause: Can't find appName attribute in resource collection.

Action: Add appName attribute to resource collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08029: Privilege parameter is missing or not a right type

Cause: Privilege parameter is missing or not a right type.

Action: Check the privilege paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08030: DB object parameter is missing or not a right type.

Cause: DB object parameter is missing or not a right type.

Action: Check the DB object paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08031: Client env parameter is not a right type.

Cause: Client env parameter is not a right type.

Action: Check the client env paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08032: Client env parameter has unsupported value.

Cause: Client env parameter has unsupported value.

Action: Check the client env paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08033: Check privilege mode parameter has unsupported value.

Cause: Check privilege mode parameter has unsupported value.

Action: Check the Check privilege paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08034: Value of parameter {0} should be type {1}, but has a wrong type {2}.

Cause: Invalid parameter type

Action: Check the paramater.
Level: 1

Type: ERROR

Impact: Security

JPS-08035: Type of RAS parameter value is not supported.

Cause: Type of RAS parameter value is not supported.

Action: Do not use unsupported type for RAS parameter value.
Level: 1

Type: ERROR

Impact: Security

JPS-08036: Invalid data type in Subject collection, it only accepts RuntimeAttribute.

Cause: Invalid data type in Subject collection, it only accepts RuntimeAttribute.

Action: Use RuntimeAttribute in Subject collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08037: Invalid data type in Action collection, it only accepts RuntimeAttribute.

Cause: Invalid data type in Action collection, it only accepts RuntimeAttribute.

Action: Use RuntimeAttribute in Action collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08038: Invalid data type in Resource collection, it only accepts RuntimeAttribute.

Cause: Invalid data type in Resource collection, it only accepts RuntimeAttribute.

Action: Use RuntimeAttribute in Resource collection.
Level: 1

Type: ERROR

Impact: Security

JPS-08500: Component audit definition {0} already exists.

Cause: Component audit definition {0} already exists.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08500: Component audit definition {0} already exists.

Cause: Component audit definition {0} already exists.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08500: Component audit definition {0} already exists.

Cause: Component audit definition {0} already exists.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08501: Failed to create component audit definition {0}. Reason: {1}.

Cause: Failed to create component audit definition {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08501: Failed to create component audit definition {0}. Reason: {1}.

Cause: Failed to create component audit definition {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08501: Failed to create component audit definition {0}. Reason: {1}.

Cause: Failed to create component audit definition {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08502: Failed to search database mapping table for component {0}. Reason: {1}.

Cause: Failed to search database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08502: Failed to search database mapping table for component {0}. Reason: {1}.

Cause: Failed to search database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08502: Failed to search database mapping table for component {0}. Reason: {1}.

Cause: Failed to search database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08503: Cannot search audit definition for component {0}. Reason: {1}.

Cause: Cannot search audit definition for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08503: Failed to search audit definition for component {0}. Reason: {1}.

Cause: Failed to search audit definition for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08503: Failed to search audit definition for component {0}. Reason: {1}.

Cause: Failed to search audit definition for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08504: Failed to search generic attribute groups. Reason: {0}.

Cause: Failed to search generic attribute groups. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08504: Failed to search generic attribute groups. Reason: {0}.

Cause: Failed to search generic attribute groups. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08504: Failed to search generic attribute groups. Reason: {0}.

Cause: Failed to search generic attribute groups. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08505: Failed to create database mapping table for component {0}. Reason: {1}.

Cause: Failed to create database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08505: Failed to create database mapping table for component {0}. Reason: {1}.

Cause: Failed to create database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08505: Failed to create database mapping table for component {0}. Reason: {1}.

Cause: Failed to create database mapping table for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08506: Failed to create filter config for component {0}. Reason: {1}.

Cause: Failed to create filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08506: Failed to create filter config for component {0}. Reason: {1}.

Cause: Failed to create filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08506: Failed to create filter config for component {0}. Reason: {1}.

Cause: Failed to create filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08507: Component audit definition {0} does not exist.

Cause: Component audit definition {0} does not exist.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08507: Component audit definition {0} does not exist.

Cause: Component audit definition {0} does not exist.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08507: Component audit definition {0} does not exist.

Cause: Component audit definition {0} does not exist.

Action: Check given component type.
Level: 1

Type: WARNING

Impact: Security

JPS-08508: Failed to search filter config for component {0}. Reason: {1}.

Cause: Failed to search filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08508: Failed to search filter config for component {0}. Reason: {1}.

Cause: Failed to search filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08508: Failed to search filter config for component {0}. Reason: {1}.

Cause: Failed to search filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08509: Failed to update filter config for component {0}. Reason: {1}.

Cause: Failed to update filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08509: Failed to update filter config for component {0}. Reason: {1}.

Cause: Failed to update filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08509: Failed to update filter config for component {0}. Reason: {1}.

Cause: Failed to update filter config for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08510: The expected audit store DN {0} was missing.

Cause: The expected audit store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: WARNING

Impact: Security

JPS-08510: The expected audit store DN {0} was missing.

Cause: The expected audit store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: WARNING

Impact: Security

JPS-08510: The expected audit store DN {0} was missing.

Cause: The expected audit store DN {0} was missing.

Action: Configure this DN during the bootstrap process.
Level: 1

Type: WARNING

Impact: Security

JPS-08511: Audit store was not fully initialized until data source is available.

Cause: Audit store was not fully initialized until data source is available.

Action: Wait and retry later.
Level: 1

Type: WARNING

Impact: Security

JPS-08511: Audit store was not fully initialized until data source is available.

Cause: Audit store was not fully initialized until data source is available.

Action: Wait and retry later.
Level: 1

Type: WARNING

Impact: Security

JPS-08511: Audit store was not fully initialized until data source is available.

Cause: Audit store was not fully initialized until data source is available.

Action: Wait and retry later.
Level: 1

Type: WARNING

Impact: Security

JPS-08512: Failed to retrieve value. Reason: {0}.

Cause: Failed to retrieve value. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08512: Failed to retrieve value. Reason: {0}.

Cause: Failed to retrieve value. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08512: Failed to retrieve value. Reason: {0}.

Cause: Failed to retrieve value. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08513: Failed to search component types. Reason: {0}.

Cause: Failed to search component types. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08513: Failed to search component types. Reason: {0}.

Cause: Failed to search component types. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08513: Failed to search component types. Reason: {0}.

Cause: Failed to search component types. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08514: Failed to search system XLF. Reason: {0}.

Cause: Failed to search system XLF. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08514: Failed to search system XLF. Reason: {0}.

Cause: Failed to search system XLF. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08514: Failed to search system XLF. Reason: {0}.

Cause: Failed to search system XLF. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08515: Failed to search XLF for component {0}. Reason: {1}.

Cause: Failed to search XLF for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08515: Failed to search XLF for component {0}. Reason: {1}.

Cause: Failed to search XLF for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08515: Failed to search XLF for component {0}. Reason: {1}.

Cause: Failed to search XLF for component {0}. Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08516: Failed to search system definition. Reason: {0}.

Cause: Failed to search system definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08516: Failed to search system definition. Reason: {0}.

Cause: Failed to search system definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08516: Failed to search system definition. Reason: {0}.

Cause: Failed to search system definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08517: System audit definition already exists.

Cause: System audit definition already exists.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08517: System audit definition already exists.

Cause: System audit definition already exists.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08517: System audit definition already exists.

Cause: System audit definition already exists.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08518: Failed to create system audit definition. Reason: {0}.

Cause: Failed to create system audit definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08518: Failed to create system audit definition. Reason: {0}.

Cause: Failed to create system audit definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08518: Failed to create system audit definition. Reason: {0}.

Cause: Failed to create system audit definition. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08519: Error in creating filter tree. Reason: {0}.

Cause: Error in creating filter tree. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08519: Error in creating filter tree. Reason: {0}.

Cause: Error in creating filter tree. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08519: Error in creating filter tree. Reason: {0}.

Cause: Error in creating filter tree. Reason: {0}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08520: Audit definition {0} is invalid.

Cause: Audit definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08520: Audit definition {0} is invalid.

Cause: Audit definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08520: Audit definition {0} is invalid.

Cause: Audit definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08521: Attribute mapping table {0} for component type {1} is invalid.

Cause: Attribute mapping table {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08521: Attribute mapping table {0} for component type {1} is invalid.

Cause: Attribute mapping table {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08521: Attribute mapping table {0} for component type {1} is invalid.

Cause: Attribute mapping table {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08522: Filter config {0} for component type {1} is invalid.

Cause: Filter config {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08522: Filter config {0} for component type {1} is invalid.

Cause: Filter config {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08522: Filter config {0} for component type {1} is invalid.

Cause: Filter config {0} for component type {1} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08523: Component type value {0} is invalid.

Cause: Component type value {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08523: Component type value {0} is invalid.

Cause: Component type value {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08523: Component type value {0} is invalid.

Cause: Component type value {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08524: System definition {0} is invalid.

Cause: System definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08524: System definition {0} is invalid.

Cause: System definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08524: System definition {0} is invalid.

Cause: System definition {0} is invalid.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08525: Audit definition for component type {0} not found.

Cause: Audit definition for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08525: Audit definition for component type {0} not found.

Cause: Audit definition for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08525: Audit definition for component type {0} not found.

Cause: Audit definition for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08526: XLF for component type {0} not found.

Cause: XLF for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08526: XLF for component type {0} not found.

Cause: XLF for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08526: XLF for component type {0} not found.

Cause: XLF for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08527: Attribute mapping table for component type {0} not found.

Cause: Attribute mapping table for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08527: Attribute mapping table for component type {0} not found.

Cause: Attribute mapping table for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08527: Attribute mapping table for component type {0} not found.

Cause: Attribute mapping table for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08528: Filter config for component type {0} not found.

Cause: Filter config for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08528: Filter config for component type {0} not found.

Cause: Filter config for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08528: Filter config for component type {0} not found.

Cause: Filter config for component type {0} not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08529: Generic attribute groups not found.

Cause: Generic attribute groups not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08529: Generic attribute groups not found.

Cause: Generic attribute groups not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08529: Generic attribute groups not found.

Cause: Generic attribute groups not found.

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08530: Failed to search audit definition in audit store. Reason: {0}.

Cause: Failed to search audit definition in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08530: Failed to search audit definition in audit store. Reason: {0}.

Cause: Failed to search audit definition in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08530: Failed to search audit definition in audit store. Reason: {0}.

Cause: Failed to search audit definition in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08531: Failed to create audit metadata in audit store. Reason: {0}.

Cause: Failed to create audit metadata in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08531: Failed to create audit metadata in audit store. Reason: {0}.

Cause: Failed to create audit metadata in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08531: Failed to create audit metadata in audit store. Reason: {0}.

Cause: Failed to create audit metadata in audit store. Reason: {0}.

Action: Ensure that the audit store configuration for audit service are correct in jps-config.xml.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08532: Audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08532: Audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08532: Audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08533: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Cause: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08533: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Cause: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08533: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Cause: Component XLF for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08534: Generic attribute groups in destination store do not match those in source store.

Cause: Generic attribute groups in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08534: Generic attribute groups in destination store do not match those in source store.

Cause: Generic attribute groups in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08534: Generic attribute groups in destination store do not match those in source store.

Cause: Generic attribute groups in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08535: Attribute group "{0}" in destination store does not match the one in source store.

Cause: Attribute group "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08535: Attribute group "{0}" in destination store does not match the one in source store.

Cause: Attribute group "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08535: Attribute group "{0}" in destination store does not match the one in source store.

Cause: Attribute group "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08536: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08536: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08536: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Cause: Audit filter config for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08537: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Cause: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08537: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Cause: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08537: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Cause: Attribute mapping table for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08538: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Cause: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08538: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Cause: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08538: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Cause: Event definitions for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08539: Event category "{0}" in destination store does not match the one in source store.

Cause: Event category "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08539: Event category "{0}" in destination store does not match the one in source store.

Cause: Event category "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08539: Event category "{0}" in destination store does not match the one in source store.

Cause: Event category "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08540: Level list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Level list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08540: Level list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Level list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08540: Level list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Level list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08541: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08541: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08541: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Cause: Filter preset definition list for audit definition "{0}" in destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08542: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Cause: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08542: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Cause: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08542: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Cause: Attribute "{0}" in attribute group "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08543: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Cause: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08543: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Cause: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08543: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Cause: Custom filter preset definition in filter config of audit definition "{0}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08544: Failed to remove component definition "{0}". Reason: {1}.

Cause: Failed to remove component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08544: Failed to remove component definition "{0}". Reason: {1}.

Cause: Failed to remove component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08544: Failed to remove component definition "{0}". Reason: {1}.

Cause: Failed to remove component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08545: Failed to update component definition "{0}". Reason: {1}.

Cause: Failed to update component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08545: Failed to update component definition "{0}". Reason: {1}.

Cause: Failed to update component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08545: Failed to update component definition "{0}". Reason: {1}.

Cause: Failed to update component definition "{0}". Reason: {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08546: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Cause: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08546: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Cause: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08546: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Cause: Filter preset definition "{0}" in filter config of audit definition "{1}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08547: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Cause: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08547: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Cause: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08547: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Cause: Filter category "{0}" of filter preset definition "{1}" in filter config of audit definition "{2}" in the destination store does not match the one in source store.

Action: See error message.
Level: 1

Type: WARNING

Impact: Configuration

JPS-08548: Cannot register to audit service for component "{0}".

Cause: Cannot register component definition "{0}" to audit service. Reason {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08548: Failed to register to audit service for component "{0}".

Cause: Failed to register component definition "{0}" to audit service. Reason {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08548: Failed to register to audit service for component "{0}".

Cause: Failed to register component definition "{0}" to audit service. Reason {1}.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08549: Audit registration service not available.

Cause: Audit registration service not available.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08549: Audit registration service not available.

Cause: Audit registration service not available.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08549: Audit registration service not available.

Cause: Audit registration service not available.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08550: Audit loader startup failed. Cause: "{0}".

Cause: Audit loader startup failed.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08550: Audit loader startup failed. Cause: "{0}".

Cause: Audit loader startup failed.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08550: Audit loader startup failed. Cause: "{0}".

Cause: Audit loader startup failed.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08551: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Cause: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08551: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Cause: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08551: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Cause: Failed to upgrade audit event definition due to incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08552: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Cause: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08552: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Cause: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08552: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Cause: Upgrade audit event definition with incompatible data mapping. Component type: "{0}".

Action: See error message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08553: Failed to load opss_audit_registration.xml. Reason "{0}".

Cause: Failed to load opss_audit_registration.xml, Reason "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08553: Failed to load opss_audit_registration.xml. Reason "{0}".

Cause: Failed to load opss_audit_registration.xml, Reason "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08553: Failed to load opss_audit_registration.xml. Reason "{0}".

Cause: Failed to load opss_audit_registration.xml, Reason "{0}".

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08554: Failed to register Component type "{0}" due to malformed version number in event definition.

Cause: Failed to register Component type "{0}" due to malformed version number in event definition.

Action: See error message.
Level: 1

Type: WARNING

Impact: Security

JPS-08555: During provisioning operations, subscriptions will not be accepted

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-08556: Component type value null is invalid.

Cause: Component type value null is invalid.

Action: Use the appropriate componentType while doing registration of component to AuditStore
Level: 1

Type: ERROR

Impact: Security

JPS-08557: Component events definition file is invalid. Reason - "{0}".

Cause: Component events definition file is invalid. Reason - "{0}".

Action: Correct the events definition file based on reason
Level: 1

Type: ERROR

Impact: Security

JPS-09000: Resource type {0} already in use for {1}.

Cause: Resource type was already in use.

Action: Use a different resource type name.
Level: 1

Type: WARNING

Impact: Security

JPS-09000: Resource type {0} already in use for {1}.

Cause: Resource type was already in use.

Action: Use a different resource type name.
Level: 1

Type: WARNING

Impact: Security

JPS-09000: Resource type {0} already in use for {1}.

Cause: Resource type was already in use.

Action: Use a different resource type name.
Level: 1

Type: WARNING

Impact: Security

JPS-09001: Resource matching class name is missing. A subtype must not have its own matching algorithm.

Cause: Resource matching class name was missing.

Action: A subtype must not have its own matching algorithm.
Level: 1

Type: WARNING

Impact: Security

JPS-09001: Resource matching class name is missing. A subtype must not have its own matching algorithm.

Cause: Resource matching class name was missing.

Action: A subtype must not have its own matching algorithm.
Level: 1

Type: WARNING

Impact: Security

JPS-09001: Resource matching class name is missing. A subtype must not have its own matching algorithm.

Cause: Resource matching class name was missing.

Action: A subtype must not have its own matching algorithm.
Level: 1

Type: WARNING

Impact: Security

JPS-09002: The parameter {0} of type {1} does not exist.

Cause: This parameter did not exist.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09002: The parameter {0} of type {1} does not exist.

Cause: This parameter did not exist.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09002: The parameter {0} of type {1} does not exist.

Cause: This parameter did not exist.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09003: For the parameter {0} more than expected values found for the Application name:{1}, Policy Domain:{2}, Query Parameter:{3}, Actual results: {4}

Cause: More then expected values for given parameter found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09003: For the parameter {0} more than expected values found for the Application name:{1}, Policy Domain:{2}, Query Parameter:{3}, Actual results: {4}

Cause: More then expected values for given parameter found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09003: For the parameter {0} more than expected values found for the Application name:{1}, Policy Domain:{2}, Query Parameter:{3}, Actual results: {4}

Cause: More then expected values for given parameter found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09004: For type {0} the modification is not allowed for {1}.

Cause: Modify operation was not allowed.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09004: For type {0} the modification is not allowed for {1}.

Cause: Modify operation was not allowed.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09004: For type {0} the modification is not allowed for {1}.

Cause: Modify operation was not allowed.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09005: For the parameter {0} the given value {1} is invalid.

Cause: The value for the given parameter was invalid.

Action: Provide the valid value for the given paramter.
Level: 1

Type: WARNING

Impact: Security

JPS-09005: For the parameter {0} the given value {1} is invalid.

Cause: The value for the given parameter was invalid.

Action: Provide the valid value for the given paramter.
Level: 1

Type: WARNING

Impact: Security

JPS-09005: For the parameter {0} the given value {1} is invalid.

Cause: The value for the given parameter was invalid.

Action: Provide the valid value for the given paramter.
Level: 1

Type: WARNING

Impact: Security

JPS-09006: Resource {0} already in use for {1}.

Cause: Resource was already in use.

Action: Use a different resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-09006: Resource {0} already in use for {1}.

Cause: Resource was already in use.

Action: Use a different resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-09006: Resource {0} already in use for {1}.

Cause: Resource was already in use.

Action: Use a different resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-09007: RoleCategory {0} cannot be deleted

Cause: The role category is referenced by one or more application roles.

Action: Modify the application role(s) definition that reference this role category by removing the role category for the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-09007: RoleCategory {0} cannot be deleted

Cause: The role category is referenced by one or more application roles.

Action: Modify the application role(s) definition that reference this role category by removing the role category for the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-09007: RoleCategory {0} cannot be deleted

Cause: The role category is referenced by one or more application roles.

Action: Modify the application role(s) definition that reference this role category by removing the role category for the application role.
Level: 1

Type: WARNING

Impact: Security

JPS-09008: Application policy for application {0} does not exist.

Cause: Application policy did not exist.

Action: The application policy must exist. Check the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-09008: Application policy for application {0} does not exist.

Cause: Application policy did not exist.

Action: The application policy must exist. Check the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-09008: Application policy for application {0} does not exist.

Cause: Application policy did not exist.

Action: The application policy must exist. Check the policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-09009: Only limited set of properties are supported for resource action search. See the documentation for more details.

Cause: The property user to search resource action was invalid.

Action: Only limited set of properties are supported for resource action search. See the documentation for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09009: Only limited set of properties are supported for resource action search. See the documentation for more details.

Cause: The property user to search resource action was invalid.

Action: Only limited set of properties are supported for resource action search. See the documentation for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09009: Only limited set of properties are supported for resource action search. See the documentation for more details.

Cause: The property user to search resource action was invalid.

Action: Only limited set of properties are supported for resource action search. See the documentation for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-09010: Cannot create permission set {0} with a non existent resource type {1}.

Cause: Permission set could not be created without resource type.

Action: Resource type must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09010: Cannot create permission set {0} with a non existent resource type {1}.

Cause: Permission set could not be created without resource type.

Action: Resource type must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09010: Cannot create permission set {0} with a non existent resource type {1}.

Cause: Permission set could not be created without resource type.

Action: Resource type must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09011: Cannot create permission set {0} with a non existent resource {1}.

Cause: Permission set could not be created without resource.

Action: Resource must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09011: Cannot create permission set {0} with a non existent resource {1}.

Cause: Permission set could not be created without resource.

Action: Resource must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09011: Cannot create permission set {0} with a non existent resource {1}.

Cause: Permission set could not be created without resource.

Action: Resource must be pre-defined to create the permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-09012: Search value cannot be null. It can be null only if MATCHER is ANY.

Cause: Search value was null. It could be null only if MATCHER is ANY.

Action: Verify the search value for the given query.
Level: 1

Type: WARNING

Impact: Security

JPS-09012: Search value cannot be null. It can be null only if MATCHER is ANY.

Cause: Search value was null. It could be null only if MATCHER is ANY.

Action: Verify the search value for the given query.
Level: 1

Type: WARNING

Impact: Security

JPS-09012: Search value cannot be null. It can be null only if MATCHER is ANY.

Cause: Search value was null. It could be null only if MATCHER is ANY.

Action: Verify the search value for the given query.
Level: 1

Type: WARNING

Impact: Security

JPS-09013: This application roles {0} does not belong to this application {1}.

Cause: This application role did not belong to this application.

Action: Ensure this application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09013: This application roles {0} does not belong to this application {1}.

Cause: This application role did not belong to this application.

Action: Ensure this application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09013: This application roles {0} does not belong to this application {1}.

Cause: This application role did not belong to this application.

Action: Ensure this application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09014: The application role {0} cannot have null name or unique name for the application {1}.

Cause: The name or unique name of this application role was null or invalid.

Action: Ensure the name or unique name of this application role is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-09014: The application role {0} cannot have null name or unique name for the application {1}.

Cause: The name or unique name of this application role was null or invalid.

Action: Ensure the name or unique name of this application role is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-09014: The application role {0} cannot have null name or unique name for the application {1}.

Cause: The name or unique name of this application role was null or invalid.

Action: Ensure the name or unique name of this application role is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-09015: Application role does not exist in current application.

Cause: Application role was not found in current application.

Action: Ensure the application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09015: Application role does not exist in current application.

Cause: Application role was not found in current application.

Action: Ensure the application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09015: Application role does not exist in current application.

Cause: Application role was not found in current application.

Action: Ensure the application role belongs to this application.
Level: 1

Type: WARNING

Impact: Security

JPS-09016: Unknown policy store service type {0}.

Cause: Unknown policy store service type {0}.

Action: Correct the policy store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09016: Unknown policy store service type {0}.

Cause: Unknown policy store service type {0}.

Action: Correct the policy store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09016: Unknown policy store service type {0}.

Cause: Unknown policy store service type {0}.

Action: Correct the policy store configuration.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09017: Policy entry {0} cannot be found.

Cause: Policy entry {0} cannot be found.

Action: Correct the policy entry.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09017: Policy entry {0} cannot be found.

Cause: Policy entry {0} cannot be found.

Action: Correct the policy entry.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09017: Policy entry {0} cannot be found.

Cause: Policy entry {0} cannot be found.

Action: Correct the policy entry.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09018: Policy object {0} cannot be found.

Cause: Policy object {0} cannot be found.

Action: Correct the policy object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09018: Policy object {0} cannot be found.

Cause: Policy object {0} cannot be found.

Action: Correct the policy object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09018: Policy object {0} cannot be found.

Cause: Policy object {0} cannot be found.

Action: Correct the policy object.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09019: {0} could not be cached.

Cause: {0} did not be cached.

Action: Ensure the Resource has valid actions.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09019: {0} could not be cached.

Cause: {0} did not be cached.

Action: Ensure the Resource has valid actions.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09019: {0} could not be cached.

Cause: {0} did not be cached.

Action: Ensure the Resource has valid actions.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09020: Principal entry class "{0}", name "{1}" cannot be created.

Cause: Principal entry class "{0}", name "{1}" cannot be created.

Action: Ensure that the principal entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09020: Principal entry class "{0}", name "{1}" cannot be created.

Cause: Principal entry class "{0}", name "{1}" cannot be created.

Action: Ensure that the principal entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09020: Principal entry class "{0}", name "{1}" cannot be created.

Cause: Principal entry class "{0}", name "{1}" cannot be created.

Action: Ensure that the principal entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09021: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Cause: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Action: Ensure that the permission entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09021: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Cause: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Action: Ensure that the permission entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09021: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Cause: Permission entry class "{0}", target "{1}", action "{2}" cannot be created.

Action: Ensure that the permission entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09022: Resource entry type "{0}", resource "{1}" cannot be created.

Cause: Resource entry type "{0}", resource "{1}" cannot be created.

Action: Ensure that the resource entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09022: Resource entry type "{0}", resource "{1}" cannot be created.

Cause: Resource entry type "{0}", resource "{1}" cannot be created.

Action: Ensure that the resource entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09022: Resource entry type "{0}", resource "{1}" cannot be created.

Cause: Resource entry type "{0}", resource "{1}" cannot be created.

Action: Ensure that the resource entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09023: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Cause: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Action: Ensure that the resource type entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09023: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Cause: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Action: Ensure that the resource type entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09023: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Cause: Resource type entry name "{0}", matcher class "{1}", provider "{2}" cannot be created.

Action: Ensure that the resource type entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09024: Resource action entry type "{0}", name "{1}" cannot be created.

Cause: Resource action entry type "{0}", name "{1}" cannot be created.

Action: Ensure that the resource action entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09024: Resource action entry type "{0}", name "{1}" cannot be created.

Cause: Resource action entry type "{0}", name "{1}" cannot be created.

Action: Ensure that the resource action entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09024: Resource action entry type "{0}", name "{1}" cannot be created.

Cause: Resource action entry type "{0}", name "{1}" cannot be created.

Action: Ensure that the resource action entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09025: Permission set entry (name: "{0}", actions: "{1}") cannot be created.

Cause: Permissionset entry name "{0}", actions "{1}" cannot be created.

Action: Ensure that the permissionset entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09025: Permission set entry (name: "{0}", actions: "{1}") cannot be created.

Cause: Permissionset entry name "{0}", actions "{1}" cannot be created.

Action: Ensure that the permissionset entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09025: Permission set entry (name: "{0}", actions: "{1}") cannot be created.

Cause: Permissionset entry name "{0}", actions "{1}" cannot be created.

Action: Ensure that the permissionset entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09026: Role category entry name "{0}" cannot be created.

Cause: Role category entry name "{0}" cannot be created.

Action: Ensure that the role category entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09026: Role category entry name "{0}" cannot be created.

Cause: Role category entry name "{0}" cannot be created.

Action: Ensure that the role category entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09026: Role category entry name "{0}" cannot be created.

Cause: Role category entry name "{0}" cannot be created.

Action: Ensure that the role category entry class is correct and entry value is valid.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09027: Grantee DN was missing for principal {0}.

Cause: Grantee DN was missing for principal {0}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09027: Grantee DN was missing for principal {0}.

Cause: Grantee DN was missing for principal {0}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09027: Grantee DN was missing for principal {0}.

Cause: Grantee DN was missing for principal {0}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09028: Failed to get permission for principal {0}. Reason: {1}.

Cause: Failed to get permission for principal {0}. Reason: {1}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09028: Failed to get permission for principal {0}. Reason: {1}.

Cause: Failed to get permission for principal {0}. Reason: {1}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09028: Failed to get permission for principal {0}. Reason: {1}.

Cause: Failed to get permission for principal {0}. Reason: {1}.

Action: Check principal value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09029: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Cause: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Action: Check log for details.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09029: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Cause: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Action: Check log for details.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09029: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Cause: Total Time to getPermissions in the Application {0} with {1} number of Grantees is: {2} ms.

Action: Check log for details.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09030: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Cause: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09030: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Cause: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09030: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Cause: Code signer data {0} cannot be migrated due to limitation in the destination policy store.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09031: Failed to read java policies for Application: {0}. Reason: {1}.

Cause: Failed to read java policies for Application: {0}. Reason: {1}.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09031: Failed to read java policies for Application: {0}. Reason: {1}.

Cause: Failed to read java policies for Application: {0}. Reason: {1}.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09031: Failed to read java policies for Application: {0}. Reason: {1}.

Cause: Failed to read java policies for Application: {0}. Reason: {1}.

Action: Check log for details.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09032: Only one of permission array {0} and permission entry list {1} can be null or non-null.

Cause: Only one of permission array {0} and permission entry list {1} can be null/non-null.

Action: Ensure one of permission array or permission entry list values is null or non-null.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09032: Only one of permission array {0} and permission entry list {1} can be null or non-null.

Cause: Only one of permission array {0} and permission entry list {1} can be null/non-null.

Action: Ensure one of permission array or permission entry list values is null or non-null.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09032: Only one of permission array {0} and permission entry list {1} can be null or non-null.

Cause: Only one of permission array {0} and permission entry list {1} can be null/non-null.

Action: Ensure one of permission array or permission entry list values is null or non-null.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09033: No grantee found for grantee entry {0}.

Cause: No grantee found for grantee entry {0}.

Action: Ensure the grantee exist in the policy store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09033: No grantee found for grantee entry {0}.

Cause: No grantee found for grantee entry {0}.

Action: Ensure the grantee exist in the policy store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09033: No grantee found for grantee entry {0}.

Cause: No grantee found for grantee entry {0}.

Action: Ensure the grantee exist in the policy store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09034: Modification on single-value attribute {0} but contains multiple attribute values.

Cause: Modification on single-value attribute {0} but contains multiple attribute values.

Action: Check modification details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09034: Modification on single-value attribute {0} but contains multiple attribute values.

Cause: Modification on single-value attribute {0} but contains multiple attribute values.

Action: Check modification details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09034: Modification on single-value attribute {0} but contains multiple attribute values.

Cause: Modification on single-value attribute {0} but contains multiple attribute values.

Action: Check modification details.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09035: Failed to create DN for {0}. Reason: {1}.

Cause: Failed to create DN for {0}. Reason: {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09035: Failed to create DN for {0}. Reason: {1}.

Cause: Failed to create DN for {0}. Reason: {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09035: Failed to create DN for {0}. Reason: {1}.

Cause: Failed to create DN for {0}. Reason: {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09036: Failed to read JACC policy {0}. Reason: {0}.

Cause: Failed to read JACC policy {0}. Reason: {0}.

Action: Check LDAP configuration to resolve this error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09036: Failed to read JACC policy {0}. Reason: {0}.

Cause: Failed to read JACC policy {0}. Reason: {0}.

Action: Check LDAP configuration to resolve this error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09036: Failed to read JACC policy {0}. Reason: {0}.

Cause: Failed to read JACC policy {0}. Reason: {0}.

Action: Check LDAP configuration to resolve this error.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09037: No application DN found for name {0} under farm {1}.

Cause: No application DN found for name {0} under farm {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09037: No application DN found for name {0} under farm {1}.

Cause: No application DN found for name {0} under farm {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09037: No application DN found for name {0} under farm {1}.

Cause: No application DN found for name {0} under farm {1}.

Action: Check DN name.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09038: Resource type {0} does not exist for resource {1}

Cause: This resource type does not exist.

Action: Provide a valid resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-09038: Resource type {0} does not exist for resource {1}

Cause: This resource type does not exist.

Action: Provide a valid resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-09038: Resource type {0} does not exist for resource {1}

Cause: This resource type does not exist.

Action: Provide a valid resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-09041: Expression component provided for RuleExpressionEntry must not be null.

Cause: Expression component provided for RuleExpressionEntry must not be null.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09041: Expression component provided for RuleExpressionEntry must not be null.

Cause: Expression component provided for RuleExpressionEntry must not be null.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09041: Expression component provided for RuleExpressionEntry must not be null.

Cause: Expression component provided for RuleExpressionEntry must not be null.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09042: Invalid expression component provided to RuleExpressionEntry.

Cause: Invalid expression component provided to RuleExpressionEntry.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09042: Invalid expression component provided to RuleExpressionEntry.

Cause: Invalid expression component provided to RuleExpressionEntry.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09042: Invalid expression component provided to RuleExpressionEntry.

Cause: Invalid expression component provided to RuleExpressionEntry.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09043: Function entry for an expression must not be null.

Cause: Function entry for an expression must not be null.

Action: Check value of FunctionEntry.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09043: Function entry for an expression must not be null.

Cause: Function entry for an expression must not be null.

Action: Check value of FunctionEntry.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09043: Function entry for an expression must not be null.

Cause: Function entry for an expression must not be null.

Action: Check value of FunctionEntry.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09044: Expression component of type {0} not supported.

Cause: Expression component of type {0} not supported.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09044: Expression component of type {0} not supported.

Cause: Expression component of type {0} not supported.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09044: Expression component of type {0} not supported.

Cause: Expression component of type {0} not supported.

Action: Check value of ExpressionComponent.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09045: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Cause: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Action: Check parameters to constructor of VarArgsInfo.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09045: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Cause: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Action: Check parameters to constructor of VarArgsInfo.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09045: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Cause: Minimum number of input parameters must be less than or equal to maximum number of input parameters

Action: Check parameters to constructor of VarArgsInfo.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09046: The Matcher {0} in the search query is invalid

Cause: The matcher in the search query is invalid

Action: Provide a valid Search Matcher in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09046: The Matcher {0} in the search query is invalid

Cause: The matcher in the search query is invalid

Action: Provide a valid Search Matcher in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09046: The Matcher {0} in the search query is invalid

Cause: The matcher in the search query is invalid

Action: Provide a valid Search Matcher in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09047: The Property {0} in the search query is invalid

Cause: The search property in the query is invalid

Action: Provide a valid Search property in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09047: The Property {0} in the search query is invalid

Cause: The search property in the query is invalid

Action: Provide a valid Search property in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09047: The Property {0} in the search query is invalid

Cause: The search property in the query is invalid

Action: Provide a valid Search property in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09048: The search value is invalid

Cause: The search value in the query is invalid

Action: Provide a valid Search value in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09048: The search value is invalid

Cause: The search value in the query is invalid

Action: Provide a valid Search value in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09048: The search value is invalid

Cause: The search value in the query is invalid

Action: Provide a valid Search value in the query.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09049: Null value provided for {0}

Cause: Invalid value provided to DataType object.

Action: Provide a non-null value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09049: Null value provided for {0}

Cause: Invalid value provided to DataType object.

Action: Provide a non-null value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09049: Null value provided for {0}

Cause: Invalid value provided to DataType object.

Action: Provide a non-null value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09050: Host name {0} is invalid for DNS name

Cause: Invalid value provided as DNS host.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09050: Host name {0} is invalid for DNS name

Cause: Invalid value provided as DNS host.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09050: Host name {0} is invalid for DNS name

Cause: Invalid value provided as DNS host.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09051: Invalid data. Lower DNS port {0} is greater than higher port {1}.

Cause: Lower port is greater than upper range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09051: Invalid data. Lower DNS port {0} is greater than higher port {1}.

Cause: Lower port is greater than upper range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09051: Invalid data. Lower DNS port {0} is greater than higher port {1}.

Cause: Lower port is greater than upper range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09052: Unknown format, can not parse valid date from string {0}.

Cause: Unknown format for date string.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09052: Unknown format, can not parse valid date from string {0}.

Cause: Unknown format for date string.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09052: Unknown format, can not parse valid date from string {0}.

Cause: Unknown format for date string.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09053: Invalid string {0} for fractional seconds.

Cause: Invalid string for fractional seconds.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09053: Invalid string {0} for fractional seconds.

Cause: Invalid string for fractional seconds.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09053: Invalid string {0} for fractional seconds.

Cause: Invalid string for fractional seconds.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09054: Invalid string {0} for hour offset.

Cause: Invalid string for hour offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09054: Invalid string {0} for hour offset.

Cause: Invalid string for hour offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09054: Invalid string {0} for hour offset.

Cause: Invalid string for hour offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09055: Invalid string {0} for minute offset.

Cause: Invalid string for minute offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09055: Invalid string {0} for minute offset.

Cause: Invalid string for minute offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09055: Invalid string {0} for minute offset.

Cause: Invalid string for minute offset.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09056: Negative value {0} not allowed.

Cause: Negative value not aloowed.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09056: Negative value {0} not allowed.

Cause: Negative value not aloowed.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09056: Negative value {0} not allowed.

Cause: Negative value not aloowed.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09057: Invalid string {0} for dayTimeDuration. Cannot parse.

Cause: Invalid string format for dayTimeDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09057: Invalid string {0} for dayTimeDuration. Cannot parse.

Cause: Invalid string format for dayTimeDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09057: Invalid string {0} for dayTimeDuration. Cannot parse.

Cause: Invalid string format for dayTimeDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09058: Invalid string {0} for RFC822 name.

Cause: RFC822Name cannot end with @.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09058: Invalid string {0} for RFC822 name.

Cause: RFC822Name cannot end with @.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09058: Invalid string {0} for RFC822 name.

Cause: RFC822Name cannot end with @.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09059: Invalid string {0} for RFC822 domain.

Cause: Invvalid RFC822 domain name.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09059: Invalid string {0} for RFC822 domain.

Cause: Invvalid RFC822 domain name.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09059: Invalid string {0} for RFC822 domain.

Cause: Invvalid RFC822 domain name.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09060: Invalid string {0} for yearMonthDuration.

Cause: Invalid string format for yearMonthDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09060: Invalid string {0} for yearMonthDuration.

Cause: Invalid string format for yearMonthDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09060: Invalid string {0} for yearMonthDuration.

Cause: Invalid string format for yearMonthDuration

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09061: Invalid string {0} for OpssTime, must be a number.

Cause: Invalid string for time field, must be a number.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09061: Invalid string {0} for OpssTime, must be a number.

Cause: Invalid string for time field, must be a number.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09061: Invalid string {0} for OpssTime, must be a number.

Cause: Invalid string for time field, must be a number.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09062: Invalid value {0}, must be between lower range {1} and upper range {2}.

Cause: Value provided for data type not in required range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09062: Invalid value {0}, must be between lower range {1} and upper range {2}.

Cause: Value provided for data type not in required range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09062: Invalid value {0}, must be between lower range {1} and upper range {2}.

Cause: Value provided for data type not in required range.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09063: Invalid inputted Hex Binary value {0}.

Cause: Invalid value provided for OpssHexBinary data type.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09063: Invalid inputed Hex Binary value {0}.

Cause: Invalid value provided for OpssHexBinary data type.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09063: Invalid inputed Hex Binary value {0}.

Cause: Invalid value provided for OpssHexBinary data type.

Action: Provide a valid value
Level: 1

Type: WARNING

Impact: Programmatic

JPS-09064: Invalid extension manager, cannot be used to find constraint attributes and functions.

Cause: Internal error: invalid extension manager cannot be used to find constraint attributes or functions.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-09400: Attribute key cannot be null.

Cause: Attribute key was null.

Action: Provide a valid attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09400: Attribute key cannot be null.

Cause: Attribute key was null.

Action: Provide a valid attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09400: Attribute key cannot be null.

Cause: Attribute key was null.

Action: Provide a valid attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09401: Name of attribute key cannot be null.

Cause: Name of attribute key was null.

Action: Provide a valid name of attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09401: Name of attribute key cannot be null.

Cause: Name of attribute key was null.

Action: Provide a valid name of attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09401: Name of attribute key cannot be null.

Cause: Name of attribute key was null.

Action: Provide a valid name of attribute key.
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09402: Attribute service instance not found in the default context.

Cause: Attribute service instance not found in the default JpsContext.

Action: Configure an attribute service instance in the default JpsContext.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09402: Attribute service instance not found in the default context.

Cause: Attribute service instance not found in the default JpsContext.

Action: Configure an attribute service instance in the default JpsContext.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09402: Attribute service instance not found in the default context.

Cause: Attribute service instance not found in the default JpsContext.

Action: Configure an attribute service instance in the default JpsContext.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09500: Template name is not initialized, please follow the document for method execution order

Cause: Template name is not initialized.

Action: Ensure that execution order is followed as per document
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09501: Either template name or target store or target key or credential object is passed as NULL, {0} is not inserted

Cause: Either template name or target store or target key or credential objcet is passed as NULL, corresponding credential/key object is not inserted

Action: Ensure that all the parameters are passed to insert credential/key object
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09502: Error occurred when initializing security artifacts. Reason {0}

Cause: Security Artifact initialization failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09503: Error occurred when cleaning the environment, please clean it manually

Cause: Error occurred while cleaning the environment

Action: Please clean it manually
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09504: Error occurred when processing credentials for template {0}. Reason {1}

Cause: Failed while processing credentials

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09505: Error occurred when processing keys for template {0}. Reason {1}.

Cause: Failed while processing keys

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09506: Error occurred when commiting changes, calling abort method to clean up the environment

Cause: Failed while commiting changes

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09507: No templates are processed, please call processXXX() methods

Cause: No templates are processed, please call processXXX() methods

Action: Please call processXXX() methods before calling end() method
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09508: No artifacts found for template {0}

Cause: No templates specified in component-security-info.xml file

Action: Please add new template in component-security-info.xml file
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09509: No processing mode specified for template {0}

Cause: No processing mode specified for a template

Action: Please add processing mode for a template in component-security-info.xml file
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09510: No credentials found for template {0}

Cause: No credentials are available to seed into OPSS security store for template {0}

Action: Please check the logs or corresponding credential data file in template
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09511: Not able to instantiate credential store object for credential store {0}

Cause: Scratch directory credential store initialization failed

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09512: Not able to instantiate key store service object for key stores {0}

Cause: Scratch directory key store initialization failed

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09513: Not able to get the handle for bootstrap cwallet.sso {0}

Cause: Not able to get the handle for bootstrap wallet

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09514: Credential already exist for map {0} and key {1}

Cause: Credentials already exist in the Opss CredentialStore Implementation

Action: Pass credentials with unique map and key name
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09515: CIE CredentialsInfo object should not be null

Cause: Passed CIE CredentialStoreInfo object is NULL

Action: Please pass valid CIE credential object
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09516: CIE KeystoreInfo object should not be null

Cause: Passed CIE KeystoresInfo object is NULL

Action: Please pass valid CIE key store object
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09517: CIE PrivateKeyInfo object should not be null

Cause: Passed CIE PrivateKeyInfo object is NULL

Action: Please pass valid CIE private key object
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09518: Alias '''{0}''' already exist in key store {1}

Cause: Alias already exist in the Opss key store Implementation

Action: Please key object with unique alias
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09519: Error occurred when processing audit data for template {0}. Reason {1}

Cause: Failed while processing audit data

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09520: Error occurred when processing authorization data for template {0}. Reason {1}.

Cause: Failed while processing authorization data

Action: Check the logs
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09521: More than one application stripe {0} found in authorization data file {1}.

Cause: More than one application stripe in authorization data file

Action: Ensure that the authorization file does not have more than one application stripe
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09522: Authorization data file {0} is not present.

Cause: No authorization data file found.

Action: Verify if the file is present
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09523: No keys found for template {0}

Cause: No keys are available to seed into OPSS security store for template {0}

Action: Please check the logs or corresponding keystore data file in template
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09524: More than one component types found in audit store data file {0} for template {1}.

Cause: More than one component types in audit store data file

Action: Ensure that the audit store file does not have more than one component type
Level: 1

Type: ERROR

Impact: Requests/Responses

JPS-09600: File {0} is cannot be found. Check if the specified file is expected in the specified location.

Cause: File {0} cannot be found.

Action: Check if the specified file exists and accessible in the specified location.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09601: The value "{0}" is invalid for {1}.

Cause: An invalid value was provided for this configuration.

Action: Provide the correct value.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09602: Fail to find default JPS Context in {0}.

Cause: Fail to find default JPS Context in the jps-config.xml.

Action: Check content of jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09603: SecurityContext.getSharedSecretStore and getSharedSecretStorePassword return inconsistent values.

Cause: SecurityContext.getSharedSecretStore and getSharedSecretStorePassword return inconsistent values.

Action: Both shared secret store name and password are required for configuring a domain with shared database security store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09604: JDBC Information {0} is missing for configuring security store to database.

Cause: JDBC Information is missing for configuring security store to database.

Action: Check if all required jdbc information is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09605: Fail to find JPS Context with id {0} in {1}.

Cause: Fail to find the specific JPS Context in the jps-config.xml.

Action: Check content of jps-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09606: Error encountered while importing encryption key in shared database security store.

Cause: Error encoutered while seeding encryption key in shared database security store.

Action: Check if encryption key is exported and imported properly.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09607: OpssSecurityConfiguration is in invalid state.

Cause: OpssSecurityConfiguration is in invalid state, it has not been initialized properly

Action: If creating expanded domain, check if database is up and all the required datasource information are provided.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09608: OpssSecurityConfiguration is in invalid state, start method is not invoked prior to other methods.

Cause: OpssSecurityConfiguration is in invalid state - start() method is not invoked by CIE prior to other methods

Action: Check if CIE is invoking OpssSecurityConfiguration in proper order.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09609: Failed to initialize OPSS security context based on SecurityContext object from CIE.

Cause: Failed to initialize OPSS security context based on SecurityConext object passed from CIE.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09610: Error during updating audit loader repositoryType. Exception {0}

Cause: Failed to update audit loader repository type to DB.

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09611: Error updating audit loader credential in bootstrap wallet. Exception {0}

Cause: Failed to add audit loader credentials to bootstrap wallet

Action: Check the logs.
Level: 1

Type: WARNING

Impact: Configuration

JPS-09612: JDBC password for {0} is missing for configuring security store to database.

Cause: JDBC password is missing for configuring security store to database.

Action: Check if jdbc password is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09613: JDBC username for {0} is missing for configuring security store to database.

Cause: JDBC username is missing for configuring security store to database.

Action: Check if jdbc username is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09614: The supplied password for property {0} is invalid.

Cause: The supplied password for property {0} is invalid.

Action: Please provide valid password.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09615: Update jps configuration file(s) failed for service {0}. Exception {1}

Cause: Update jps configuration file(s) failed for service {0}.

Action: Check log file for errors.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09616: The schema {0} is already in use for security store(s). Please create a new schema.

Cause: The schema {0} is already in use for security store(s).

Action: Please create a new schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09617: Failed to create a domain with shared security store because no security store was found in the database schema {0}.

Cause: Failed to create a domain with shared security store because no security store was found in the database schema {0}.

Action: Please check if a security store is configured properly for the database schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09618: Data migration failed for configurator {0}

Cause: Failed to migrate data for configurator {0}.

Action: Please check the logs and check if a security store is configured properly for the database schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09619: Jps test service failed for configurator

Cause: Jps test service failed for configurator.

Action: Please check the logs and check if a security store is configured properly for the database schema.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09620: Failed to rollback data.

Cause: Failed to rollback data.

Action: Please check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09621: No entry found for artifact type {0} in component-security-info.xml file of template {1}.

Cause: Artifact is not registered in component-security-info.xml file of template, but artifact data is present as part of template.

Action: Please register missing artifact in component-security-info.xml file
Level: 1

Type: WARNING

Impact: Requests/Responses

JPS-09622: Error during configuring DB security store. Exception {0}.

Cause: Error occured during configuring DB security store.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09623: Error during updating JPS configuration in shared DB security store. Exception {0}.

Cause: Error updating JPS configuration in shared DB security store.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Configuration

JPS-09624: JDBC database name for {0} is missing for configuring security store to database.

Cause: JDBC database name is missing for configuring security store to database.

Action: Check if jdbc database is supplied.
Level: 1

Type: ERROR

Impact: Configuration

JPS-09625: Jps test service completed for configurator.

Cause: Jps test service completed for configurator.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09626: Rolling back of data for configurator is completed.

Cause: Rolling back of data for configurator is completed.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-09627: Trying to rollback data for configurator.

Cause: Trying to rollback data for configurator.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Configuration

JPS-10000: There was an internal error in the policy store.

Cause: The opearion is not allowed for multivalued attribute.

Action: The opearion is not allowed for multivalued attribute.Supply a valid opearion
Level: 1

Type: WARNING

Impact: Security

JPS-10000: There was an internal error in the policy store.

Cause: The opearion is not allowed for multivalued attribute.

Action: The opearion is not allowed for multivalued attribute.Supply a valid opearion
Level: 1

Type: WARNING

Impact: Security

JPS-10000: There was an internal error in the policy store.

Cause: The opearion is not allowed for multivalued attribute.

Action: The opearion is not allowed for multivalued attribute.Supply a valid opearion
Level: 1

Type: WARNING

Impact: Security

JPS-10001: Exception happened while decoding value: {0}.

Cause: The encoding format is not correct.

Action: Check encoding format of String value.
Level: 1

Type: WARNING

Impact: Security

JPS-10001: Exception happened while decoding value: {0}.

Cause: The encoding format is not correct.

Action: Check encoding format of String value.
Level: 1

Type: WARNING

Impact: Security

JPS-10001: Exception happened while decoding value: {0}.

Cause: The encoding format is not correct.

Action: Check encoding format of String value.
Level: 1

Type: WARNING

Impact: Security

JPS-10002: Container is not ready. Reason: {0}.

Cause: Container is not ready.

Action: Wait for container to start up successfully.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10003: Null search value is not allowed, unless the matcher is ANY.

Cause: Query value is null but the matcher is not ANY.

Action: Do not use null query value if the matcher is not ANY.
Level: 1

Type: WARNING

Impact: Security

JPS-10004: The search value {0} is invalid.

Cause: Query value is invalid.

Action: Use an valid query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10005: Access denied. {0}

Cause: Access to policy store is denied.

Action: Do not perform such operation on policy store.
Level: 1

Type: WARNING

Impact: Security

JPS-10050: The application {0} cannot be found at runtime due to {1}.

Cause: Corresponding runtime application does not exist.

Action: Check if policy is properly distributed.
Level: 1

Type: ERROR

Impact: Security

JPS-10050: The application {0} cannot be found at runtime due to {1}.

Cause: Corresponding runtime application does not exist.

Action: Check if policy is properly distributed.
Level: 1

Type: ERROR

Impact: Security

JPS-10050: The application {0} cannot be found at runtime due to {1}.

Cause: Corresponding runtime application does not exist.

Action: Check if policy is properly distributed.
Level: 1

Type: ERROR

Impact: Security

JPS-10051: Policy object "{0}" already exists in application policy "{1}".

Cause: Policy object with same name exists in this application policy.

Action: Try a different name.
Level: 1

Type: ERROR

Impact: Security

JPS-10051: Policy object {0} already exists in application policy {1}.

Cause: Policy object with same name exists in this application policy.

Action: Try a different name.
Level: 1

Type: ERROR

Impact: Security

JPS-10051: Policy object {0} already exists in application policy {1}.

Cause: Policy object with same name exists in this application policy.

Action: Try a different name.
Level: 1

Type: ERROR

Impact: Security

JPS-10052: The list of runtime events is NULL.

Cause: The list of runtime events is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10052: The list of runtime events is NULL.

Cause: The list of runtime events is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10052: The list of runtime events is NULL.

Cause: The list of runtime events is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10053: The runtime events is NULL.

Cause: The runtime event is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10053: The runtime events is NULL.

Cause: The runtime event is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10053: The runtime events is NULL.

Cause: The runtime event is NULL

Action: Please contact the security administrator.
Level: 1

Type: ERROR

Impact: Security

JPS-10100: The policy domain "{0}" does not exist.

Cause: The policy domain does not exist

Action: Check the policy domain name.
Level: 1

Type: WARNING

Impact: Security

JPS-10100: The policy domain, {0}, does not exist.

Cause: The policy domain does not exist

Action: Check the policy domain name.
Level: 1

Type: WARNING

Impact: Security

JPS-10100: The policy domain, {0}, does not exist.

Cause: The policy domain does not exist

Action: Check the policy domain name.
Level: 1

Type: WARNING

Impact: Security

JPS-10102: The policy domain "{0}" already exists.

Cause: The policy domain exists

Action: Create a policy domain with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10102: The policy domain, {0}, already exists.

Cause: The policy domain exists

Action: Create a policy domain with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10102: The policy domain, {0}, already exists.

Cause: The policy domain exists

Action: Create a policy domain with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10151: Application role {0} does not exist

Cause: The application role does not exist.

Action: Provide correct application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10151: Application role {0} does not exist

Cause: The application role does not exist.

Action: Provide correct application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10151: Application role {0} does not exist

Cause: The application role does not exist.

Action: Provide correct application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10152: Application Role {0} is used.

Cause: Application Role is used.

Action: Remove the objects which use this application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10152: Application Role {0} is used.

Cause: Application Role is used.

Action: Remove the objects which use this application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10152: Application Role {0} is used.

Cause: Application Role is used.

Action: Remove the objects which use this application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10153: Application role {0} does not belong to current application.

Cause: Application role does not belong to current application policy.

Action: Modify the application role with application role manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10153: Application role {0} does not belong to current application.

Cause: Application role does not belong to current application policy.

Action: Modify the application role with application role manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10153: Application role {0} does not belong to current application.

Cause: Application role does not belong to current application policy.

Action: Modify the application role with application role manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10154: Class {0} is not supported.

Cause: The principal class specified is not supported.

Action: Provide correct principal class.
Level: 1

Type: WARNING

Impact: Security

JPS-10154: Class {0} is not supported.

Cause: The principal class specified is not supported.

Action: Provide correct principal class.
Level: 1

Type: WARNING

Impact: Security

JPS-10154: Class {0} is not supported.

Cause: The principal class specified is not supported.

Action: Provide correct principal class.
Level: 1

Type: WARNING

Impact: Security

JPS-10155: The application role attribute {0} is not supported for app role search.

Cause: The application role attribute specified is not supported.

Action: Provide supported attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10155: The application role attribute {0} is not supported for app role search.

Cause: The application role attribute specified is not supported.

Action: Provide supported attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10155: The application role attribute {0} is not supported for app role search.

Cause: The application role attribute specified is not supported.

Action: Provide supported attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10156: Error occurred while fetching the application role {0}.

Cause: The internal error occured while fetching the application role.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10156: Error occurred while fetching the application role {0}.

Cause: The internal error occured while fetching the application role.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10156: Error occurred while fetching the application role {0}.

Cause: The internal error occured while fetching the application role.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10157: More than one results found for given Application role:{0}, Application name {1}, query:{2} and Actual result: {3}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10157: More than one results found for given Application role:{0}, Application name {1}, query:{2} and Actual result: {3}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10157: More than one results found for given Application role:{0}, Application name {1}, query:{2} and Actual result: {3}.

Cause: More than one results found for application name.

Action: Refer to the log files for details and correct the error.
Level: 1

Type: WARNING

Impact: Security

JPS-10158: Invalid parameter.

Cause: Invalid parameter value.

Action: Please check the values are of required type.
Level: 1

Type: WARNING

Impact: Security

JPS-10158: Invalid parameter.

Cause: Invalid parameter value.

Action: Please check the values are of required type.
Level: 1

Type: WARNING

Impact: Security

JPS-10158: Invalid parameter.

Cause: Invalid parameter value.

Action: Please check the values are of required type.
Level: 1

Type: WARNING

Impact: Security

JPS-10159: Application Role {0} has an invalid unique name

Cause: Application role has an invalid unique name

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10159: Application Role {0} has an invalid unique name

Cause: Application role has an invalid unique name

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10159: Application Role {0} has an invalid unique name

Cause: Application role has an invalid unique name

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10160: The Application role {0} does not belong to application. The application role dn {1} and unique name {2} are not matching.

Cause: The Application role does not belong to application contex.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10160: The Application role {0} does not belong to application. The application role dn {1} and unique name {2} are not matching.

Cause: The Application role does not belong to application contex.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10160: The Application role {0} does not belong to application. The application role dn {1} and unique name {2} are not matching.

Cause: The Application role does not belong to application contex.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10161: Internal error- More than one grantee entries found.

Cause: Internal error- More than one grantee entries found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10161: Internal error- More than one grantee entries found.

Cause: Internal error- More than one grantee entries found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10161: Internal error- More than one grantee entries found.

Cause: Internal error- More than one grantee entries found.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10162: Grantee DN was missing

Cause: Grantee DN was missing

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10162: Grantee DN was missing

Cause: Grantee DN was missing

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10162: Grantee DN was missing

Cause: Grantee DN was missing

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10163: Internal error while revoking the permissions. Number of permissions to revoke (or delete) {0} : though only {1} permission(s) would be revoked (or deleted) if this operation were to proceed

Cause: Internal error while revoking the permissions.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10163: Internal error while revoking the permissions. Number of permissions to revoke (or delete) {0} : though only {1} permission(s) would be revoked (or deleted) if this operation were to proceed

Cause: Internal error while revoking the permissions.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10163: Internal error while revoking the permissions. Number of permissions to revoke (or delete) {0} : though only {1} permission(s) would be revoked (or deleted) if this operation were to proceed

Cause: Internal error while revoking the permissions.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10164: Only one of permission list and permission entry list can be null/non-null.

Cause: Only one of permission list and permission entry list can be null/non-null

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10164: Only one of permission list and permission entry list can be null/non-null.

Cause: Only one of permission list and permission entry list can be null/non-null

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10164: Only one of permission list and permission entry list can be null/non-null.

Cause: Only one of permission list and permission entry list can be null/non-null

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10165: MATCHER.ANY not allowed for this kind of search operation

Cause: MATCHER.ANY not allowed for this kind of search operation

Action: Search is not allowed for the MATCHER.ANY
Level: 1

Type: WARNING

Impact: Security

JPS-10165: MATCHER.ANY not allowed for this kind of search operation

Cause: MATCHER.ANY not allowed for this kind of search operation

Action: Search is not allowed for the MATCHER.ANY
Level: 1

Type: WARNING

Impact: Security

JPS-10165: MATCHER.ANY not allowed for this kind of search operation

Cause: MATCHER.ANY not allowed for this kind of search operation

Action: Search is not allowed for the MATCHER.ANY
Level: 1

Type: WARNING

Impact: Security

JPS-10166: Error occurred during performing the operation {0}.

Cause: Error occured during performing the operation.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10166: Error occurred during performing the operation {0}.

Cause: Error occured during performing the operation.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10166: Error occurred during performing the operation {0}.

Cause: Error occured during performing the operation.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10167: Obligation does not exist for the policy domain {0}.

Cause: Obligation does not exist for the policy domain {0}.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10167: Obligation does not exist for the policy domain {0}.

Cause: Obligation does not exist for the policy domain {0}.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10167: Obligation does not exist for the policy domain {0}.

Cause: Obligation does not exist for the policy domain {0}.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10168: Error occurred while preparing the principal in {0} method of {1} class : {2}. In standalone mode, weblogic specific jars should not be in classpath. Please check the classpath and try again.

Cause: Fail to resolve principal.

Action: Check classpath which may contain weblogic specific jars.
Level: 1

Type: ERROR

Impact: Security

JPS-10200: Administration role {0} already exists

Cause: Cannot have two administration roles with the same name.

Action: Provide a new name to the administration role.
Level: 1

Type: WARNING

Impact: Security

JPS-10200: Administration role {0} already exists

Cause: Cannot have two administration roles with the same name.

Action: Provide a new name to the administration role.
Level: 1

Type: WARNING

Impact: Security

JPS-10200: Administration role {0} already exists

Cause: Cannot have two administration roles with the same name.

Action: Provide a new name to the administration role.
Level: 1

Type: WARNING

Impact: Security

JPS-10201: Administration role {0} does not exist

Cause: Administration role is not found.

Action: Check the administration role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10201: Administration role {0} does not exist

Cause: Administration role is not found.

Action: Check the administration role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10201: Administration role {0} does not exist

Cause: Administration role is not found.

Action: Check the administration role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10202: Administration role {0} is used

Cause: Administration role is used.

Action: Remove administration role members first.
Level: 1

Type: WARNING

Impact: Security

JPS-10202: Administration role {0} is used

Cause: Administration role is used.

Action: Remove administration role members first.
Level: 1

Type: WARNING

Impact: Security

JPS-10202: Administration role {0} is used

Cause: Administration role is used.

Action: Remove administration role members first.
Level: 1

Type: WARNING

Impact: Security

JPS-10203: Administration role {0} does not belong to current context

Cause: Administration role does not belong to current context.

Action: Use it in correct context.
Level: 1

Type: WARNING

Impact: Security

JPS-10203: Administration role {0} does not belong to current context

Cause: Administration role does not belong to current context.

Action: Use it in correct context.
Level: 1

Type: WARNING

Impact: Security

JPS-10203: Administration role {0} does not belong to current context

Cause: Administration role does not belong to current context.

Action: Use it in correct context.
Level: 1

Type: WARNING

Impact: Security

JPS-10204: Cannot create admin role with default name {0}

Cause: Cannot create admin role with reserved name.

Action: Use another name for admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10204: Cannot create admin role with default name {0}

Cause: Cannot create admin role with reserved name.

Action: Use another name for admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10204: Cannot create admin role with default name {0}

Cause: Cannot create admin role with reserved name.

Action: Use another name for admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10205: Cannot delete default admin role {0}

Cause: Cannot delete default admin role.

Action: Check the admin role name for deletion.
Level: 1

Type: WARNING

Impact: Security

JPS-10205: Cannot delete default admin role {0}

Cause: Cannot delete default admin role.

Action: Check the admin role name for deletion.
Level: 1

Type: WARNING

Impact: Security

JPS-10205: Cannot delete default admin role {0}

Cause: Cannot delete default admin role.

Action: Check the admin role name for deletion.
Level: 1

Type: WARNING

Impact: Security

JPS-10206: Cannot grant {0}, {1} to admin role because its super admin role has no such privilege

Cause: Cannot grant privileges to admin role whose super role has not.

Action: Check the admin resource action to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10206: Cannot grant {0}, {1} to admin role because its super admin role has no such privilege

Cause: Cannot grant privileges to admin role whose super role has not.

Action: Check the admin resource action to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10206: Cannot grant {0}, {1} to admin role because its super admin role has no such privilege

Cause: Cannot grant privileges to admin role whose super role has not.

Action: Check the admin resource action to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10207: Admin resource {0} is not for this scope {1}

Cause: This admin resource is not for this scope

Action: Check the admin resource to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10207: Admin resource {0} is not for this scope {1}

Cause: This admin resource is not for this scope

Action: Check the admin resource to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10207: Admin resource {0} is not for this scope {1}

Cause: This admin resource is not for this scope

Action: Check the admin resource to grant.
Level: 1

Type: WARNING

Impact: Security

JPS-10208: Cannot change rights of default admin role {0}

Cause: Cannot change righs of default admin role for a scope

Action: Check the admin role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10208: Cannot change rights of default admin role {0}

Cause: Cannot change righs of default admin role for a scope

Action: Check the admin role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10208: Cannot change rights of default admin role {0}

Cause: Cannot change righs of default admin role for a scope

Action: Check the admin role name.
Level: 1

Type: WARNING

Impact: Security

JPS-10209: The value for the SEARCH_PROPERTY.PRINCIPAL does implement the java.security.Principal interface. It is of type "{0}".

Cause: The search by value is not an instance of java.security.Principal

Action: Supply an object of type java.security.Principal
Level: 1

Type: WARNING

Impact: Security

JPS-10209: The value for the SEARCH_PROPERTY.PRINCIPAL does implement the java.security.Principal interface. It is of type '{0}'.

Cause: The search by value is not an instance of java.security.Principal

Action: Supply an object of type java.security.Principal
Level: 1

Type: WARNING

Impact: Security

JPS-10209: The value for the SEARCH_PROPERTY.PRINCIPAL does implement the java.security.Principal interface. It is of type '{0}'.

Cause: The search by value is not an instance of java.security.Principal

Action: Supply an object of type java.security.Principal
Level: 1

Type: WARNING

Impact: Security

JPS-10210: The value for the SEARCH_PROPERTY.PRINCIPAL_NAME is not of type java.lang.String. It is of type "{0}".

Cause: The search by value is not an instance of java.lang.String

Action: Supply an object of type java.lang.String
Level: 1

Type: WARNING

Impact: Security

JPS-10210: The value for the SEARCH_PROPERTY.PRINCIPAL_NAME is not of type java.lang.String. It is of type '{0}'.

Cause: The search by value is not an instance of java.lang.String

Action: Supply an object of type java.lang.String
Level: 1

Type: WARNING

Impact: Security

JPS-10210: The value for the SEARCH_PROPERTY.PRINCIPAL_NAME is not of type java.lang.String. It is of type '{0}'.

Cause: The search by value is not an instance of java.lang.String

Action: Supply an object of type java.lang.String
Level: 1

Type: WARNING

Impact: Security

JPS-10211: Administration role cannot have more than one grantee for parameter Application:{0}, policy Domain:{1}, Query Parameter:{2}, Actual results:{3}.

Cause: The admin role cannot have more than one grantee entry.

Action: Check only one grantee entry available to admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10211: Administration role cannot have more than one grantee for parameter Application:{0}, policy Domain:{1}, Query Parameter:{2}, Actual results:{3}.

Cause: The admin role cannot have more than one grantee entry.

Action: Check only one grantee entry available to admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10211: Administration role cannot have more than one grantee for parameter Application:{0}, policy Domain:{1}, Query Parameter:{2}, Actual results:{3}.

Cause: The admin role cannot have more than one grantee entry.

Action: Check only one grantee entry available to admin role.
Level: 1

Type: WARNING

Impact: Security

JPS-10250: Resource type reference should not be null.

Cause: The parameter resource type reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10250: Resource type reference should not be null.

Cause: The parameter resource type reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10250: Resource type reference should not be null.

Cause: The parameter resource type reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10251: The resource type reference is invalid.

Cause: The current resource type reference is invalid.

Action: Use a valid resource type reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10251: The resource type reference is invalid.

Cause: The current resource type reference is invalid.

Action: Use a valid resource type reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10251: The resource type reference is invalid.

Cause: The current resource type reference is invalid.

Action: Use a valid resource type reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10252: The resource type "{0}" already exists.

Cause: The resource type has existed.

Action: Make sure the resource type does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10252: The resource type {0} already exists.

Cause: The resource type has existed.

Action: Make sure the resource type does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10252: The resource type {0} already exists.

Cause: The resource type has existed.

Action: Make sure the resource type does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10253: The super resource type {0} does not exist.

Cause: The resource type is referring an invalid super resource type.

Action: Make sure the super resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10253: The super resource type {0} does not exist.

Cause: The resource type is referring an invalid super resource type.

Action: Make sure the super resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10253: The super resource type {0} does not exist.

Cause: The resource type is referring an invalid super resource type.

Action: Make sure the super resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10254: The resource type {0} should not have its own matcher since it has super type.

Cause: The resource type has both its own matching algorithm and super type.

Action: Remove matching algorithm if the resource type should have super type. Otherwise, remove super type.
Level: 1

Type: WARNING

Impact: Security

JPS-10254: The resource type {0} should not have its own matcher since it has super type.

Cause: The resource type has both its own matching algorithm and super type.

Action: Remove matching algorithm if the resource type should have super type. Otherwise, remove super type.
Level: 1

Type: WARNING

Impact: Security

JPS-10254: The resource type {0} should not have its own matcher since it has super type.

Cause: The resource type has both its own matching algorithm and super type.

Action: Remove matching algorithm if the resource type should have super type. Otherwise, remove super type.
Level: 1

Type: WARNING

Impact: Security

JPS-10255: Resource type search context should not be null.

Cause: The resource type context could not be gotten.

Action: Make sure the application policy is available.
Level: 1

Type: WARNING

Impact: Security

JPS-10255: Resource type search context should not be null.

Cause: The resource type context could not be gotten.

Action: Make sure the application policy is available.
Level: 1

Type: WARNING

Impact: Security

JPS-10255: Resource type search context should not be null.

Cause: The resource type context could not be gotten.

Action: Make sure the application policy is available.
Level: 1

Type: WARNING

Impact: Security

JPS-10256: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10256: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10256: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10257: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10257: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10257: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10258: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10258: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10258: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10259: The name of resource type could not be modified.

Cause: Resource type name could not be modified.

Action: Do not put resource type name in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10259: The name of resource type could not be modified.

Cause: Resource type name could not be modified.

Action: Do not put resource type name in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10259: The name of resource type could not be modified.

Cause: Resource type name could not be modified.

Action: Do not put resource type name in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10260: The super type of resource type could not be modified.

Cause: The super type of resource type could not be modified.

Action: Do not put super type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10260: The super type of resource type could not be modified.

Cause: The super type of resource type could not be modified.

Action: Do not put super type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10260: The super type of resource type could not be modified.

Cause: The super type of resource type could not be modified.

Action: Do not put super type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10261: The matching algorithm of resource type could not be modified.

Cause: The matching algorithm of resource type could not be modified.

Action: Do not put matching algorithm in ModificationItem
Level: 1

Type: WARNING

Impact: Security

JPS-10261: The matching algorithm of resource type could not be modified.

Cause: The matching algorithm of resource type could not be modified.

Action: Do not put matching algorithm in ModificationItem
Level: 1

Type: WARNING

Impact: Security

JPS-10261: The matching algorithm of resource type could not be modified.

Cause: The matching algorithm of resource type could not be modified.

Action: Do not put matching algorithm in ModificationItem
Level: 1

Type: WARNING

Impact: Security

JPS-10262: The action delimiter of resource type could not be modified.

Cause: The action delimiter of resource type could not be modified.

Action: Do not put action delimiter in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10262: The action delimiter of resource type could not be modified.

Cause: The action delimiter of resource type could not be modified.

Action: Do not put action delimiter in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10262: The action delimiter of resource type could not be modified.

Cause: The action delimiter of resource type could not be modified.

Action: Do not put action delimiter in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10263: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Cause: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10263: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Cause: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10263: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Cause: The operation REPLACE_ATTRIBUTE could not be used to the allowed actions of resource type.

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10264: The property {0} of resource type is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10264: The property {0} of resource type is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10264: The property {0} of resource type is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10265: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10265: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10265: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10266: The value data type of property {0} should be String.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10266: The value data type of property {0} should be String.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10266: The value data type of property {0} should be String.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10267: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10267: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10267: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10268: The resource type {0} is in use, could not be deleted.

Cause: The resource type could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10268: The resource type {0} is in use, could not be deleted.

Cause: The resource type could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10268: The resource type {0} is in use, could not be deleted.

Cause: The resource type could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10269: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Cause: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10269: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Cause: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10269: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Cause: The operation REPLACE_ATTRIBUTE could not be used to the resource type attribute

Action: Use REMOVE_ATTRIBUTE and ADD_ATTRIBUTE in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10270: The resource type attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource type attribute being deleted was used in one or morepolicies and could not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10270: The resource type attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource type attribute being deleted was used in one or morepolicies and could not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10270: The resource type attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource type attribute being deleted was used in one or morepolicies and could not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10271: The resource matcher class of resource type {0} could not be modified to {1}.

Cause: The resource type matcher class was changed while modifying.

Action: Keep matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10271: The resource matcher class of resource type {0} could not be modified to {1}.

Cause: The resource type matcher class was changed while modifying.

Action: Keep matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10271: The resource matcher class of resource type {0} could not be modified to {1}.

Cause: The resource type matcher class was changed while modifying.

Action: Keep matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10272: Permission Class not found in the classpath: {0}

Cause: The permission class was not found in the class path.

Action: Make sure that the permission class is part of the class path for the program.
Level: 1

Type: WARNING

Impact: Security

JPS-10272: Permission Class not found in the classpath: {0}

Cause: The permission class was not found in the class path.

Action: Make sure that the permission class is part of the class path for the program.
Level: 1

Type: WARNING

Impact: Security

JPS-10272: Permission Class not found in the classpath: {0}

Cause: The permission class was not found in the class path.

Action: Make sure that the permission class is part of the class path for the program.
Level: 1

Type: WARNING

Impact: Security

JPS-10273: Permission class expected to be either oracle.security.jps.ResourcePermission or extending oracle.security.jps.AbstractTypedPermission but found {0} Resource Type: {1} is sharing permission class with Resource Type: {2}

Cause: The Permission class is not either ResourcePermission or Abstracted Permission

Action: The Permission class for the resource type must be a Resource permission
Level: 1

Type: WARNING

Impact: Security

JPS-10273: Permission class expected to be either oracle.security.jps.ResourcePermission or extending oracle.security.jps.AbstractTypedPermission but found {0} Resource Type: {1} is sharing permission class with Resource Type: {2}

Cause: The Permission class is not either ResourcePermission or Abstracted Permission

Action: The Permission class for the resource type must be a Resource permission
Level: 1

Type: WARNING

Impact: Security

JPS-10273: Permission class expected to be either oracle.security.jps.ResourcePermission or extending oracle.security.jps.AbstractTypedPermission but found {0} Resource Type: {1} is sharing permission class with Resource Type: {2}

Cause: The Permission class is not either ResourcePermission or Abstracted Permission

Action: The Permission class for the resource type must be a Resource permission
Level: 1

Type: WARNING

Impact: Security

JPS-10274: Permission should be associated with a Resource Type. Permission Name: {0}

Cause: The permission should have a resource type associated with it

Action: Make sure that the permission has a resource type associated with it
Level: 1

Type: WARNING

Impact: Security

JPS-10274: Permission should be associated with a Resource Type. Permission Name: {0}

Cause: The permission should have a resource type associated with it

Action: Make sure that the permission has a resource type associated with it
Level: 1

Type: WARNING

Impact: Security

JPS-10274: Permission should be associated with a Resource Type. Permission Name: {0}

Cause: The permission should have a resource type associated with it

Action: Make sure that the permission has a resource type associated with it
Level: 1

Type: WARNING

Impact: Security

JPS-10275: Resource Type Matcher Class and Permissions do not match. {0} and {1} do not match

Cause: Resource Type Matcher Class and Permissions do not match.

Action: Make sure that the Matcher Class and Permissions match.
Level: 1

Type: WARNING

Impact: Security

JPS-10275: Resource Type Matcher Class and Permissions do not match. {0} and {1} do not match

Cause: Resource Type Matcher Class and Permissions do not match.

Action: Make sure that the Matcher Class and Permissions match.
Level: 1

Type: WARNING

Impact: Security

JPS-10275: Resource Type Matcher Class and Permissions do not match. {0} and {1} do not match

Cause: Resource Type Matcher Class and Permissions do not match.

Action: Make sure that the Matcher Class and Permissions match.
Level: 1

Type: WARNING

Impact: Security

JPS-10276: Cannot determine the Resource Type from the permission {0}

Cause: Cannot determine the Resource Type from the permission.

Action: Make sure that there is a resource type associated with the permission class
Level: 1

Type: WARNING

Impact: Security

JPS-10276: Cannot determine the Resource Type from the permission {0}

Cause: Cannot determine the Resource Type from the permission.

Action: Make sure that there is a resource type associated with the permission class
Level: 1

Type: WARNING

Impact: Security

JPS-10276: Cannot determine the Resource Type from the permission {0}

Cause: Cannot determine the Resource Type from the permission.

Action: Make sure that there is a resource type associated with the permission class
Level: 1

Type: WARNING

Impact: Security

JPS-10277: Allowed attributes can not be modified.

Cause: Allowed attributes can not be modified.

Action: Make sure not modifying allowed attributes
Level: 1

Type: WARNING

Impact: Security

JPS-10277: Allowed attributes can not be modified.

Cause: Allowed attributes can not be modified.

Action: Make sure not modifying allowed attributes
Level: 1

Type: WARNING

Impact: Security

JPS-10277: Allowed attributes can not be modified.

Cause: Allowed attributes can not be modified.

Action: Make sure not modifying allowed attributes
Level: 1

Type: WARNING

Impact: Security

JPS-10278: Requested modification to the resource type {0} is not allowed.

Cause: Requested modification to the resource type is not allowed.

Action: Make sure not to make certain type of changes to the resource type when it is used by resources
Level: 1

Type: WARNING

Impact: Security

JPS-10278: Requested modification to the resource type {0} is not allowed.

Cause: Requested modification to the resource type is not allowed.

Action: Make sure not to make certain type of changes to the resource type when it is used by resources
Level: 1

Type: WARNING

Impact: Security

JPS-10278: Requested modification to the resource type {0} is not allowed.

Cause: Requested modification to the resource type is not allowed.

Action: Make sure not to make certain type of changes to the resource type when it is used by resources
Level: 1

Type: WARNING

Impact: Security

JPS-10279: The custom resource matcher class of resource type {0} could not be modified to {1}.

Cause: The custom resource matcher class was changed while modifying the resource type.

Action: Keep custom resource matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10279: The custom resource matcher class of resource type {0} could not be modified to {1}.

Cause: The custom resource matcher class was changed while modifying the resource type.

Action: Keep custom resource matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10279: The custom resource matcher class of resource type {0} could not be modified to {1}.

Cause: The custom resource matcher class was changed while modifying the resource type.

Action: Keep custom resource matcher class unchanged.
Level: 1

Type: WARNING

Impact: Security

JPS-10280: The resource attribute {0} does not exist in the resource type {1}.

Cause: The resource attribute does not exist in the resource type.

Action: Check all the valid resource attributes in the resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10400: Resource reference should not be null.

Cause: The parameter resource reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10400: Resource reference should not be null.

Cause: The parameter resource reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10400: Resource reference should not be null.

Cause: The parameter resource reference is null.

Action: Use a valid object.
Level: 1

Type: WARNING

Impact: Security

JPS-10401: The resource reference is invalid.

Cause: The current resource reference is invalid.

Action: Use a valid resource reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10401: The resource reference is invalid.

Cause: The current resource reference is invalid.

Action: Use a valid resource reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10401: The resource reference is invalid.

Cause: The current resource reference is invalid.

Action: Use a valid resource reference.
Level: 1

Type: WARNING

Impact: Security

JPS-10402: The resource {0} does not exist.

Cause: The resource does not exist.

Action: Make sure the resource exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10402: The resource {0} does not exist.

Cause: The resource does not exist.

Action: Make sure the resource exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10402: The resource {0} does not exist.

Cause: The resource does not exist.

Action: Make sure the resource exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10403: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10403: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10403: Could not get an available data manager.

Cause: The data manager is invalid.

Action: Make sure policy store and related configuration are correct.
Level: 1

Type: WARNING

Impact: Security

JPS-10404: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10404: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10404: The resource type {0} does not exist.

Cause: The resource type does not exist.

Action: Make sure the resource type exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10405: The resource "{0}" with type "{1}" already exists in current application policy.

Cause: The resource to be created has existed.

Action: Make sure the resource does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10405: The resource {0} with type {1} already exists in current application policy.

Cause: The resource to be created has existed.

Action: Make sure the resource does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10405: The resource {0} with type {1} already exists in current application policy.

Cause: The resource to be created has existed.

Action: Make sure the resource does not exist.
Level: 1

Type: WARNING

Impact: Security

JPS-10406: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10406: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10406: The modification operator {0} is invalid.

Cause: The operator in ModificationItem is invalid.

Action: Make sure the operation is one of DirContext.ADD_ATTRIBUTE, DirContext.REPLACE_ATTRIBUTE and DirContext.REMOVE_ATTRIBUTE.
Level: 1

Type: WARNING

Impact: Security

JPS-10407: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10407: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10407: The property name {0} is unknown.

Cause: The attribute ID in ModificationItem is undefined.

Action: Make sure the attribute ID is a valid one.
Level: 1

Type: WARNING

Impact: Security

JPS-10408: The name and type of resource could not be modified.

Cause: The name and type of resource could not be modified.

Action: Do not put resource name and type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10408: The name and type of resource could not be modified.

Cause: The name and type of resource could not be modified.

Action: Do not put resource name and type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10408: The name and type of resource could not be modified.

Cause: The name and type of resource could not be modified.

Action: Do not put resource name and type in ModificationItem.
Level: 1

Type: WARNING

Impact: Security

JPS-10409: The property {0} of resource is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10409: The property {0} of resource is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10409: The property {0} of resource is single, could not have more than one value.

Cause: The property could not have more than one value.

Action: First remove the existing value before adding new one.
Level: 1

Type: WARNING

Impact: Security

JPS-10410: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10410: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10410: Could not add or replace the property {0} since there is no value provided.

Cause: There is no value provided when trying to add or replace an property.

Action: Provide the new value.
Level: 1

Type: WARNING

Impact: Security

JPS-10411: The resource {0} is in use, could not be deleted.

Cause: The resource could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10411: The resource {0} is in use, could not be deleted.

Cause: The resource could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10411: The resource {0} is in use, could not be deleted.

Cause: The resource could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10412: The resource attribute {0} already exists in the current entry.

Cause: The resource attribute could not be added since it already exists.

Action: Remove duplicate resource attributes.
Level: 1

Type: WARNING

Impact: Security

JPS-10412: The resource attribute {0} already exists in the current entry.

Cause: The resource attribute could not be added since it already exists.

Action: Remove duplicate resource attributes.
Level: 1

Type: WARNING

Impact: Security

JPS-10412: The resource attribute {0} already exists in the current entry.

Cause: The resource attribute could not be added since it already exists.

Action: Remove duplicate resource attributes.
Level: 1

Type: WARNING

Impact: Security

JPS-10413: The resource action {0} already exists in the current entry.

Cause: The resource action could not be added since it already exists.

Action: Remove duplicate resource actions
Level: 1

Type: WARNING

Impact: Security

JPS-10413: The resource action {0} already exists in the current entry.

Cause: The resource action could not be added since it already exists.

Action: Remove duplicate resource actions
Level: 1

Type: WARNING

Impact: Security

JPS-10413: The resource action {0} already exists in the current entry.

Cause: The resource action could not be added since it already exists.

Action: Remove duplicate resource actions
Level: 1

Type: WARNING

Impact: Security

JPS-10414: The resource attribute {0} could not be deleted since it does not exist.

Cause: The resource attribute could not be deleted since it does not exist.

Action: Check if the resource attribute exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10414: The resource attribute {0} could not be deleted since it does not exist.

Cause: The resource attribute could not be deleted since it does not exist.

Action: Check if the resource attribute exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10414: The resource attribute {0} could not be deleted since it does not exist.

Cause: The resource attribute could not be deleted since it does not exist.

Action: Check if the resource attribute exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10415: The resource action {0} could not be deleted since it does not exist.

Cause: The resource action could not be deleted since it does not exist.

Action: Check if the resource action exists
Level: 1

Type: WARNING

Impact: Security

JPS-10415: The resource action {0} could not be deleted since it does not exist.

Cause: The resource action could not be deleted since it does not exist.

Action: Check if the resource action exists
Level: 1

Type: WARNING

Impact: Security

JPS-10415: The resource action {0} could not be deleted since it does not exist.

Cause: The resource action could not be deleted since it does not exist.

Action: Check if the resource action exists
Level: 1

Type: WARNING

Impact: Security

JPS-10416: Resource {0} does not belong to the context.

Cause: The resource does not belong to current context

Action: Pass in correct resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10416: Resource {0} does not belong to the context.

Cause: The resource does not belong to current context

Action: Pass in correct resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10416: Resource {0} does not belong to the context.

Cause: The resource does not belong to current context

Action: Pass in correct resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10417: Resource query across different resource type is not allowed.

Cause: Resource query across different resource type is not allowed

Action: Pass in correct query parameter.
Level: 1

Type: WARNING

Impact: Security

JPS-10417: Resource query across different resource type is not allowed.

Cause: Resource query across different resource type is not allowed

Action: Pass in correct query parameter.
Level: 1

Type: WARNING

Impact: Security

JPS-10417: Resource query across different resource type is not allowed.

Cause: Resource query across different resource type is not allowed

Action: Pass in correct query parameter.
Level: 1

Type: WARNING

Impact: Security

JPS-10418: Cannot delete a resource that has one more child resources.

Cause: Can not detele a resource that has one or more child resources

Action: Delete all child resources and then try again.
Level: 1

Type: WARNING

Impact: Security

JPS-10418: Cannot delete a resource that has one more child resources.

Cause: Can not detele a resource that has one or more child resources

Action: Delete all child resources and then try again.
Level: 1

Type: WARNING

Impact: Security

JPS-10418: Cannot delete a resource that has one more child resources.

Cause: Can not detele a resource that has one or more child resources

Action: Delete all child resources and then try again.
Level: 1

Type: WARNING

Impact: Security

JPS-10419: Resource hierarchy type change is not allowed.

Cause: Resource hierarchy type change is not allowed.

Action: Check the resource hierarchy type
Level: 1

Type: WARNING

Impact: Security

JPS-10419: Resource hierarchy type change is not allowed.

Cause: Resource hierarchy type change is not allowed.

Action: Check the resource hierarchy type
Level: 1

Type: WARNING

Impact: Security

JPS-10419: Resource hierarchy type change is not allowed.

Cause: Resource hierarchy type change is not allowed.

Action: Check the resource hierarchy type
Level: 1

Type: WARNING

Impact: Security

JPS-10420: Resource name must begin with the resource name delimiter.

Cause: Resource name must begin with the resource name delimiter

Action: Add resource name delimiter in the begining of the resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-10420: Resource name must begin with the resource name delimiter.

Cause: Resource name must begin with the resource name delimiter

Action: Add resource name delimiter in the begining of the resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-10420: Resource name must begin with the resource name delimiter.

Cause: Resource name must begin with the resource name delimiter

Action: Add resource name delimiter in the begining of the resource name.
Level: 1

Type: WARNING

Impact: Security

JPS-10421: The given all action value already exists.

Cause: The given all action value already exists

Action: Check the input all action value and check for duplicate values.
Level: 1

Type: WARNING

Impact: Security

JPS-10421: The given all action value already exists.

Cause: The given all action value already exists

Action: Check the input all action value and check for duplicate values.
Level: 1

Type: WARNING

Impact: Security

JPS-10421: The given all action value already exists.

Cause: The given all action value already exists

Action: Check the input all action value and check for duplicate values.
Level: 1

Type: WARNING

Impact: Security

JPS-10422: The resource attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource attribute is used in policy(-ies) and can not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10422: The resource attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource attribute is used in policy(-ies) and can not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10422: The resource attribute {0} is used in policy(-ies) and can not be deleted.

Cause: The resource attribute is used in policy(-ies) and can not be deleted.

Action: Before deleting the resource attribute, make sure it is not used.
Level: 1

Type: WARNING

Impact: Security

JPS-10423: The action {0} is used by the {1} and can not be deleted.

Cause: The action is used by the permissionSet/permission and can not be deleted.

Action: Check if the action is used in any PermissionSet/Permission before deleting.
Level: 1

Type: WARNING

Impact: Security

JPS-10423: The action {0} is used by the permissionSet/permission and can not be deleted.

Cause: The action is used by the permissionSet/permission and can not be deleted.

Action: Check if the action is used in any PermissionSet/Permission before deleting.
Level: 1

Type: WARNING

Impact: Security

JPS-10423: The action {0} is used by the permissionSet/permission and can not be deleted.

Cause: The action is used by the permissionSet/permission and can not be deleted.

Action: Check if the action is used in any PermissionSet/Permission before deleting.
Level: 1

Type: WARNING

Impact: Security

JPS-10424: The resourceType {0} of hierarchy type is invalid as its parent is null.

Cause: The heirarical resourcetype's parent is null.

Action: Make sure to provide a valid name for the heirarical resourcetype
Level: 1

Type: ERROR

Impact: Security

JPS-10424: The resourceType {0} of hierarchy type is invalid as its parent is null.

Cause: The heirarical resourcetype's parent is null.

Action: Make sure to provide a valid name for the heirarical resourcetype
Level: 1

Type: ERROR

Impact: Security

JPS-10424: The resourceType {0} of hierarchy type is invalid as its parent is null.

Cause: The heirarical resourcetype's parent is null.

Action: Make sure to provide a valid name for the heirarical resourcetype
Level: 1

Type: ERROR

Impact: Security

JPS-10425: The resource attribute {0} already contains the value {1}.

Cause: The resource attribute already contains this value.

Action: Remove duplicate resource attributes values.
Level: 1

Type: WARNING

Impact: Security

JPS-10425: The resource attribute {0} already contains the value {1}.

Cause: The resource attribute already contains this value.

Action: Remove duplicate resource attributes values.
Level: 1

Type: WARNING

Impact: Security

JPS-10425: The resource attribute {0} already contains the value {1}.

Cause: The resource attribute already contains this value.

Action: Remove duplicate resource attributes values.
Level: 1

Type: WARNING

Impact: Security

JPS-10426: Cannot set all actions keyword for resource type with non-null matcher class.

Cause: All actions keyword cannot be set to resource type with matcher class

Action: Do not set all actions keyword for a resource type with a matcher class.
Level: 1

Type: WARNING

Impact: Security

JPS-10426: Cannot set all actions keyword for resource type with non-null matcher class.

Cause: All actions keyword cannot be set to resource type with matcher class

Action: Do not set all actions keyword for a resource type with a matcher class.
Level: 1

Type: WARNING

Impact: Security

JPS-10426: Cannot set all actions keyword for resource type with non-null matcher class.

Cause: All actions keyword cannot be set to resource type with matcher class

Action: Do not set all actions keyword for a resource type with a matcher class.
Level: 1

Type: WARNING

Impact: Security

JPS-10427: The resource name expression "{0}" is not a valid Java regular expression.

Cause: Regular expression provided for resource name expression is invalid.

Action: Check that the resource name expression is a valid Java regular expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10427: The resource name expression "{0}" is not a valid Java regular expression.

Cause: Regular expression provided for resource name expression is invalid.

Action: Check that the resource name expression is a valid Java regular expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10427: The resource name expression "{0}" is not a valid Java regular expression.

Cause: Regular expression provided for resource name expression is invalid.

Action: Check that the resource name expression is a valid Java regular expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10428: The resource {0} of type {1} does not exist.

Cause: The resource of the resource type does not exist.

Action: Make sure the resource of the resource type exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10428: The resource {0} of type {1} does not exist.

Cause: The resource of the resource type does not exist.

Action: Make sure the resource of the resource type exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10428: The resource {0} of type {1} does not exist.

Cause: The resource of the resource type does not exist.

Action: Make sure the resource of the resource type exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10429: The value data type of property {0} should be String and not {1}.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10429: The value data type of property {0} should be String and not {1}.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10429: The value data type of property {0} should be String and not {1}.

Cause: The value data type of property is not String.

Action: Use a String object as value.
Level: 1

Type: WARNING

Impact: Security

JPS-10430: The Resource name {0} has an invalid format

Cause: Too many delimiters in the resurce name

Action: Limit the number of delimiters in the beginning and middle of resource name to one.
Level: 1

Type: WARNING

Impact: Security

JPS-10431: Wrong isSingle property for the attribute {0}; expected {1}, but {2}.

Cause: Wrong isSingle property of resource attribute

Action: Ensure isSingle property of the attribute in resource is the same as the definiton in resource type
Level: 1

Type: WARNING

Impact: Security

JPS-10432: Wrong DataType property for the attribute {0}; expected {1}, but {2}.

Cause: Wrong DataType property of resource attribute

Action: Ensure DataType property of the attribute on resource is the same as the definition in resource type
Level: 1

Type: WARNING

Impact: Security

JPS-10451: Permission set {0} does not belong to the context.

Cause: The permission set does not belong to current context

Action: Pass in correct permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-10451: Permission set {0} does not belong to the context.

Cause: The permission set does not belong to current context

Action: Pass in correct permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-10451: Permission set {0} does not belong to the context.

Cause: The permission set does not belong to current context

Action: Pass in correct permission set.
Level: 1

Type: WARNING

Impact: Security

JPS-10452: Permission set {0} has ResourceActionsEntry with null ResourceEntry and null ResourceNameExpression.

Cause: Both ResourceEntry and Resource name expression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10452: Permission set {0} has ResourceActionsEntry with null ResourceEntry and null ResourceNameExpression.

Cause: Both ResourceEntry and Resource name expression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10452: Permission set {0} has ResourceActionsEntry with null ResourceEntry and null ResourceNameExpression.

Cause: Both ResourceEntry and Resource name expression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10454: No resources or actions have been identified by the permission set.

Cause: No resources or actions have been identified by the permissionset.

Action: Ensure that the permission set is created with valid resource actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10454: No resources or actions have been identified by the permission set.

Cause: No resources or actions have been identified by the permissionset.

Action: Ensure that the permission set is created with valid resource actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10454: No resources or actions have been identified by the permission set.

Cause: No resources or actions have been identified by the permissionset.

Action: Ensure that the permission set is created with valid resource actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10455: Resource is not protected by a Java Permission.

Cause: Resource is not protected by a Java Permission.

Action: Ensure that the permission set is created with valid resource object.
Level: 1

Type: WARNING

Impact: Security

JPS-10455: Resource is not protected by a Java Permission.

Cause: Resource is not protected by a Java Permission.

Action: Ensure that the permission set is created with valid resource object.
Level: 1

Type: WARNING

Impact: Security

JPS-10455: Resource is not protected by a Java Permission.

Cause: Resource is not protected by a Java Permission.

Action: Ensure that the permission set is created with valid resource object.
Level: 1

Type: WARNING

Impact: Security

JPS-10456: ResourceExpression and ResourceAction cannot be specified at the same time.

Cause: ResourceExpression and ResourceAction cannot be specified at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10456: ResourceExpression and ResourceAction cannot be specified at the same time.

Cause: ResourceExpression and ResourceAction cannot be specified at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10456: ResourceExpression and ResourceAction cannot be specified at the same time.

Cause: ResourceExpression and ResourceAction cannot be specified at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10457: Not able to perform operation due to invalid parameter. Cause: "{0}".

Cause: Not able to perform operation due to invalid parameter. Cause: {0}.

Action: Ensure that the operation is called with valid parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10457: Not able to perform operation due to invalid parameter. Cause: "{0}".

Cause: Not able to perform operation due to invalid parameter. Cause: {0}.

Action: Ensure that the operation is called with valid parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10457: Not able to perform operation due to invalid parameter. Cause: "{0}".

Cause: Not able to perform operation due to invalid parameter. Cause: {0}.

Action: Ensure that the operation is called with valid parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10458: ResourceExpression and ResourceAction cannot be null at the same time.

Cause: ResourceExpression and ResourceAction cannot be null at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10458: ResourceExpression and ResourceAction cannot be null at the same time.

Cause: ResourceExpression and ResourceAction cannot be null at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10458: ResourceExpression and ResourceAction cannot be null at the same time.

Cause: ResourceExpression and ResourceAction cannot be null at the same time.

Action: PermissionSet ResourceAction should contain either Resource expression or ResoruceEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10459: The modified permission set {0} contains resources of multiple resource types. It is not permitted as there is policy(-ies) that references that permission set and uses resource attributes.

Cause: The modified permission set contained resources of multiple resource types. It was not permitted if there was a policy that referenced that permission set and used resource attributes.

Action: Fix the permission set or modify the policy(-ies).
Level: 1

Type: WARNING

Impact: Security

JPS-10459: The modified permission set {0} contains resources of multiple resource types. It is not permitted as there is policy(-ies) that references that permission set and uses resource attributes.

Cause: The modified permission set contained resources of multiple resource types. It was not permitted if there was a policy that referenced that permission set and used resource attributes.

Action: Fix the permission set or modify the policy(-ies).
Level: 1

Type: WARNING

Impact: Security

JPS-10459: The modified permission set {0} contains resources of multiple resource types. It is not permitted as there is policy(-ies) that references that permission set and uses resource attributes.

Cause: The modified permission set contained resources of multiple resource types. It was not permitted if there was a policy that referenced that permission set and used resource attributes.

Action: Fix the permission set or modify the policy(-ies).
Level: 1

Type: WARNING

Impact: Security

JPS-10460: The permission set search query {0} is not supported

Cause: The permission set search query is not supported.

Action: Use supported query scenario.
Level: 1

Type: WARNING

Impact: Security

JPS-10460: The permission set search query {0} is not supported

Cause: The permission set search query is not supported.

Action: Use supported query scenario.
Level: 1

Type: WARNING

Impact: Security

JPS-10460: The permission set search query {0} is not supported

Cause: The permission set search query is not supported.

Action: Use supported query scenario.
Level: 1

Type: WARNING

Impact: Security

JPS-10463: Requested actions: " {0} " are not a subset of valid actions: " {1}" for the given resource: " {2} " and type: " {3} ".

Cause: Invalid resource actions for the given resource.

Action: Ensure that the actions in the resource-actions are a valid subset of the actions defined by the resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10463: Requested actions: " {0} " are not a subset of valid actions: " {1}" for the given resource: " {2} " and type: " {3} ".

Cause: Invalid resource actions for the given resource.

Action: Ensure that the actions in the resource-actions are a valid subset of the actions defined by the resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10463: Requested actions: " {0} " are not a subset of valid actions: " {1}" for the given resource: " {2} " and type: " {3} ".

Cause: Invalid resource actions for the given resource.

Action: Ensure that the actions in the resource-actions are a valid subset of the actions defined by the resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10464: Error occurred while getting the permission set entry for permission set search query {0}.

Cause: Error occured while getting the permission set entry for permission set search query.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10464: Error occurred while getting the permission set entry for permission set search query {0}.

Cause: Error occured while getting the permission set entry for permission set search query.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10464: Error occurred while getting the permission set entry for permission set search query {0}.

Cause: Error occured while getting the permission set entry for permission set search query.

Action: See the log files for more details.
Level: 1

Type: WARNING

Impact: Security

JPS-10465: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10465: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10465: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10466: Resource {0} has no Resource Actions, but Resource Type {1} has resource actions.

Cause: Empty resource actions for the given Resource, but Resource type has actions.

Action: Ensure that the actions in the resource-actions are not null or empty since the resource type has actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10466: Resource {0} has no Resource Actions, but Resource Type {1} has resource actions.

Cause: Empty resource actions for the given Resource, but Resource type has actions.

Action: Ensure that the actions in the resource-actions are not null or empty since the resource type has actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10466: Resource {0} has no Resource Actions, but Resource Type {1} has resource actions.

Cause: Empty resource actions for the given Resource, but Resource type has actions.

Action: Ensure that the actions in the resource-actions are not null or empty since the resource type has actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10467: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10467: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10467: Permission set {0} has ResourceActionsEntry with null expression in ResourceNameExpression.

Cause: Expression in ResourceNameExpression of ResourceActionsEntry is null

Action: Pass in correct ResourceActionsEntry with non-null Resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10468: Duplicate permission " {0} " in policy store.

Cause: Duplicate permission in policy store.

Action: Check the policy store and ensure that there is no duplicate permission.
Level: 1

Type: WARNING

Impact: Security

JPS-10468: Duplicate permission " {0} " in policy store.

Cause: Duplicate permission in policy store.

Action: Check the policy store and ensure that there is no duplicate permission.
Level: 1

Type: WARNING

Impact: Security

JPS-10468: Duplicate permission " {0} " in policy store.

Cause: Duplicate permission in policy store.

Action: Check the policy store and ensure that there is no duplicate permission.
Level: 1

Type: WARNING

Impact: Security

JPS-10469: Cannot remove all the ResourceActionsEntrys in PermissionSet.

Cause: Try to remove all the ResourceActionsEntrys in existing PermissionSet.

Action: Check the updated resource actions, make sure PermissionSet does not have up empty resource actions.
Level: 1

Type: WARNING

Impact: Security

JPS-10470: The resource type name "{0}", does not match the resourceType in the encoded target name: "{1}". Permission class is "{2}"

Cause: Invalid resource type in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10470: The resource type name "{0}", does not match the resourceType in the encoded target name: "{1}". Permission class is "{2}"

Cause: Invalid resource type in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10470: The resource type name "{0}", does not match the resourceType in the encoded target name: "{1}". Permission class is "{2}"

Cause: Invalid resource type in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10471: Resource type is missing in the target name: "{0}", for permission: "{1}"

Cause: Resource type missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10471: Resource type is missing in the target name: "{0}", for permission: "{1}"

Cause: Resource type missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10471: Resource type is missing in the target name: "{0}", for permission: "{1}"

Cause: Resource type missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10472: Target "{0}" is missing the prefix "=resourceName=". Unable to determine the resource name for permission: "{1}"

Cause: Target name missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10472: Target "{0}" is missing the prefix '=resourceName='. Unable to determine the resource name for permission: "{1}"

Cause: Target name missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10472: Target "{0}" is missing the prefix '=resourceName='. Unable to determine the resource name for permission: "{1}"

Cause: Target name missing in permission target.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10473: The target name "{0}" is invalid. Should start with "{1}"

Cause: Target name encoding is not correct.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10473: The target name "{0}" is invalid. Should start with "{1}"

Cause: Target name encoding is not correct.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10473: The target name "{0}" is invalid. Should start with "{1}"

Cause: Target name encoding is not correct.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10474: The parameter: "{0}", value: "{1}" cannot be null

Cause: Permission target is null.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10474: The parameter: "{0}", value: "{1}" cannot be null

Cause: Permission target is null.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10474: The parameter: "{0}", value: "{1}" cannot be null

Cause: Permission target is null.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10475: The permission actions: "{0}" are not a subset of valid actions defined in resource type: "{1}"

Cause: Permission actions do not match with valid resource type actions.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10475: The permission actions: "{0}" are not a subset of valid actions defined in resource type: "{1}"

Cause: Permission actions do not match with valid resource type actions.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10475: The permission actions: "{0}" are not a subset of valid actions defined in resource type: "{1}"

Cause: Permission actions do not match with valid resource type actions.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10500: The target policy, {0}, does not exist.

Cause: The policy object does not exist.

Action: Check if the target policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10500: The target policy, {0}, does not exist.

Cause: The policy object does not exist.

Action: Check if the target policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10500: The target policy, {0}, does not exist.

Cause: The policy object does not exist.

Action: Check if the target policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10501: Policy query contains unrecognizable information.

Cause: Policy query contains unrecognizable information.

Action: Check the policy query object.
Level: 1

Type: WARNING

Impact: Security

JPS-10501: Policy query contains unrecognizable information.

Cause: Policy query contains unrecognizable information.

Action: Check the policy query object.
Level: 1

Type: WARNING

Impact: Security

JPS-10501: Policy query contains unrecognizable information.

Cause: Policy query contains unrecognizable information.

Action: Check the policy query object.
Level: 1

Type: WARNING

Impact: Security

JPS-10502: Policy rule information is missing.

Cause: Policy rule information is missing.

Action: Check if policy rule information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10502: Policy rule information is missing.

Cause: Policy rule information is missing.

Action: Check if policy rule information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10502: Policy rule information is missing.

Cause: Policy rule information is missing.

Action: Check if policy rule information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10503: Obligation information is missing.

Cause: Obligation information is missing.

Action: Check if obligation information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10503: Obligation information is missing.

Cause: Obligation information is missing.

Action: Check if obligation information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10503: Obligation information is missing.

Cause: Obligation information is missing.

Action: Check if obligation information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10504: Permission set information is missing.

Cause: Permission set information is missing.

Action: Check if permission set information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10504: Permission set information is missing.

Cause: Permission set information is missing.

Action: Check if permission set information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10504: Permission set information is missing.

Cause: Permission set information is missing.

Action: Check if permission set information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10505: Grantee information is missing.

Cause: Grantee information is missing.

Action: Check if grantee information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10505: Grantee information is missing.

Cause: Grantee information is missing.

Action: Check if grantee information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10505: Grantee information is missing.

Cause: Grantee information is missing.

Action: Check if grantee information exists in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10506: The policy rule, {0}, does not exist.

Cause: The policy rule does not exist.

Action: Check the policy rule name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10506: The policy rule, {0}, does not exist.

Cause: The policy rule does not exist.

Action: Check the policy rule name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10506: The policy rule, {0}, does not exist.

Cause: The policy rule does not exist.

Action: Check the policy rule name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10507: The condition string is in wrong format, {0}.

Cause: Condition string is in wrong format.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10507: The condition string is in wrong format, {0}.

Cause: Condition string is in wrong format.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10507: The condition string is in wrong format, {0}.

Cause: Condition string is in wrong format.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10508: Policy condition contains an unknown function, {0}.

Cause: Policy condition contains an unknown function.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10508: Policy condition contains an unknown function, {0}.

Cause: Policy condition contains an unknown function.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10508: Policy condition contains an unknown function, {0}.

Cause: Policy condition contains an unknown function.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10509: Policy condition parsing error.

Cause: Policy condition parsing error.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10509: Policy condition parsing error.

Cause: Policy condition parsing error.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10509: Policy condition parsing error.

Cause: Policy condition parsing error.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10510: The expression, {0}, is unknown.

Cause: The policy expression is unknown.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10510: The expression, {0}, is unknown.

Cause: The policy expression is unknown.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10510: The expression, {0}, is unknown.

Cause: The policy expression is unknown.

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10511: The data type, {0}, is unknown.

Cause: The data type is unknown

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10511: The data type, {0}, is unknown.

Cause: The data type is unknown

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10511: The data type, {0}, is unknown.

Cause: The data type is unknown

Action: Check condition string in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10512: A ResourceActionsEntry should contain either resource entry or resource name expression.

Cause: The ResourceActionsEntry object does not contain resource infomation.

Action: Check ResourceActionsEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10512: A ResourceActionsEntry should contain either resource entry or resource name expression.

Cause: The ResourceActionsEntry object does not contain resource infomation.

Action: Check ResourceActionsEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10512: A ResourceActionsEntry should contain either resource entry or resource name expression.

Cause: The ResourceActionsEntry object does not contain resource infomation.

Action: Check ResourceActionsEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10513: The search value type {0} is not supported for {1}.

Cause: Query criteria type does not support.

Action: Pass in a correct query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10513: The search value type {0} is not supported for {1}.

Cause: Query criteria type does not support.

Action: Pass in a correct query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10513: The search value type {0} is not supported for {1}.

Cause: Query criteria type does not support.

Action: Pass in a correct query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10514: Cannot add PermissionSet to PolicyEntry if it has ResourceType.

Cause: Resource type is already defined in PolicyEntry.

Action: clear resource type of PolicyEntry before adding PermissionSetEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10514: Cannot add PermissionSet to PolicyEntry if it has ResourceType.

Cause: Resource type is already defined in PolicyEntry.

Action: clear resource type of PolicyEntry before adding PermissionSetEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10514: Cannot add PermissionSet to PolicyEntry if it has ResourceType.

Cause: Resource type is already defined in PolicyEntry.

Action: clear resource type of PolicyEntry before adding PermissionSetEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10515: Cannot set ResourceType to PolicyEntry if it has PermissionSet.

Cause: Permission Set is already defined in PolicyEntry.

Action: clear Permission Set of PolicyEntry before setting Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-10515: Cannot set ResourceType to PolicyEntry if it has PermissionSet.

Cause: Permission Set is already defined in PolicyEntry.

Action: clear Permission Set of PolicyEntry before setting Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-10515: Cannot set ResourceType to PolicyEntry if it has PermissionSet.

Cause: Permission Set is already defined in PolicyEntry.

Action: clear Permission Set of PolicyEntry before setting Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-10516: Cannot add Rule if there is rule already in PolicyEntry

Cause: Add rule to policy when the policy already has rule.

Action: Delete existing rule before adding new rule to policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10516: Cannot add Rule if there is rule already in PolicyEntry

Cause: Add rule to policy when the policy already has rule.

Action: Delete existing rule before adding new rule to policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10516: Cannot add Rule if there is rule already in PolicyEntry

Cause: Add rule to policy when the policy already has rule.

Action: Delete existing rule before adding new rule to policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10517: Delete rule not existing in PolicyEntry

Cause: rule does not belong to the PolicyEntry.

Action: Check the rule before deleting rule from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10517: Delete rule not existing in PolicyEntry

Cause: rule does not belong to the PolicyEntry.

Action: Check the rule before deleting rule from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10517: Delete rule not existing in PolicyEntry

Cause: rule does not belong to the PolicyEntry.

Action: Check the rule before deleting rule from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10518: Delete permission set not existing in PolicyEntry

Cause: permission set does not belong to the PolicyEntry.

Action: Check the permission set before deleting permission set from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10518: Delete permission set not existing in PolicyEntry

Cause: permission set does not belong to the PolicyEntry.

Action: Check the permission set before deleting permission set from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10518: Delete permission set not existing in PolicyEntry

Cause: permission set does not belong to the PolicyEntry.

Action: Check the permission set before deleting permission set from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10519: Delete obligation not existing in PolicyEntry

Cause: obligation does not belong to the PolicyEntry.

Action: Check the obligation before deleting obligation from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10519: Delete obligation not existing in PolicyEntry

Cause: obligation does not belong to the PolicyEntry.

Action: Check the obligation before deleting obligation from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10519: Delete obligation not existing in PolicyEntry

Cause: obligation does not belong to the PolicyEntry.

Action: Check the obligation before deleting obligation from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10520: Delete Principal not existing in PolicyEntry

Cause: principal does not belong to the PolicyEntry.

Action: Check the principal before deleting principal from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10520: Delete Principal not existing in PolicyEntry

Cause: principal does not belong to the PolicyEntry.

Action: Check the principal before deleting principal from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10520: Delete Principal not existing in PolicyEntry

Cause: principal does not belong to the PolicyEntry.

Action: Check the principal before deleting principal from PolicyEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-10521: The obligation {0} already exists.

Cause: The obligation already exists in the policy entry.

Action: Check ObligationEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10521: The obligation {0} already exists.

Cause: The obligation already exists in the policy entry.

Action: Check ObligationEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10521: The obligation {0} already exists.

Cause: The obligation already exists in the policy entry.

Action: Check ObligationEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10522: The parameters passed in is invalid, we expect {0}, but {1} is passed in.

Cause: The parameter passed in the function is not valid.

Action: Pass in correct parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10522: The parameters passed in is invalid, we expect {0}, but {1} is passed in.

Cause: The parameter passed in the function is not valid.

Action: Pass in correct parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10522: The parameters passed in is invalid, we expect {0}, but {1} is passed in.

Cause: The parameter passed in the function is not valid.

Action: Pass in correct parameters.
Level: 1

Type: WARNING

Impact: Security

JPS-10523: The function return type is invalid, we expect OpssBoolean, but {0} is passed in.

Cause: The return type of the function is not valid.

Action: Pass in a function with OpssBoolean return type.
Level: 1

Type: WARNING

Impact: Security

JPS-10523: The function return type is invalid, we expect OpssBoolean, but {0} is passed in.

Cause: The return type of the function is not valid.

Action: Pass in a function with OpssBoolean return type.
Level: 1

Type: WARNING

Impact: Security

JPS-10523: The function return type is invalid, we expect OpssBoolean, but {0} is passed in.

Cause: The return type of the function is not valid.

Action: Pass in a function with OpssBoolean return type.
Level: 1

Type: WARNING

Impact: Security

JPS-10524: The query with search property {0}, comparator type {1} and matcher {2} is not supported.

Cause: Such query is not supported.

Action: Pass in a supported query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10524: The query with search property {0}, comparator type {1} and matcher {2} is not supported.

Cause: Such query is not supported.

Action: Pass in a supported query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10524: The query with search property {0}, comparator type {1} and matcher {2} is not supported.

Cause: Such query is not supported.

Action: Pass in a supported query value.
Level: 1

Type: WARNING

Impact: Security

JPS-10525: The attribute assignment {0} could not be added since it already exists.

Cause: The attribute assignment could not be added since it already exists.

Action: Remove duplicate attribute assignments.
Level: 1

Type: WARNING

Impact: Security

JPS-10525: The attribute assignment {0} could not be added since it already exists.

Cause: The attribute assignment could not be added since it already exists.

Action: Remove duplicate attribute assignments.
Level: 1

Type: WARNING

Impact: Security

JPS-10525: The attribute assignment {0} could not be added since it already exists.

Cause: The attribute assignment could not be added since it already exists.

Action: Remove duplicate attribute assignments.
Level: 1

Type: WARNING

Impact: Security

JPS-10526: The permission set {0} could not be added since it already exists.

Cause: The permission set could not be added since it already exists.

Action: Remove duplicate permission sets.
Level: 1

Type: WARNING

Impact: Security

JPS-10526: The permission set {0} could not be added since it already exists.

Cause: The permission set could not be added since it already exists.

Action: Remove duplicate permission sets.
Level: 1

Type: WARNING

Impact: Security

JPS-10526: The permission set {0} could not be added since it already exists.

Cause: The permission set could not be added since it already exists.

Action: Remove duplicate permission sets.
Level: 1

Type: WARNING

Impact: Security

JPS-10527: The principal {0} could not be added since it already exists.

Cause: The principal could not be added since it already exists.

Action: Remove duplicate principals.
Level: 1

Type: WARNING

Impact: Security

JPS-10527: The principal {0} could not be added since it already exists.

Cause: The principal could not be added since it already exists.

Action: Remove duplicate principals.
Level: 1

Type: WARNING

Impact: Security

JPS-10527: The principal {0} could not be added since it already exists.

Cause: The principal could not be added since it already exists.

Action: Remove duplicate principals.
Level: 1

Type: WARNING

Impact: Security

JPS-10528: The Policy {0} referenced multiple resource types and resource attribute is used in policy condition or obligation.

Cause: Policies that used resource attributes in their conditions or obligations could not refrence one or more permission sets that contain resources of multiple types.

Action: Split the policy to reference only one resource type in each policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10528: The Policy {0} referenced multiple resource types and resource attribute is used in policy condition or obligation.

Cause: Policies that used resource attributes in their conditions or obligations could not refrence one or more permission sets that contain resources of multiple types.

Action: Split the policy to reference only one resource type in each policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10528: The Policy {0} referenced multiple resource types and resource attribute is used in policy condition or obligation.

Cause: Policies that used resource attributes in their conditions or obligations could not refrence one or more permission sets that contain resources of multiple types.

Action: Split the policy to reference only one resource type in each policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10529: The resource attribute {0} used in policy condition or obligation is invalid resource attribute of type {1}.

Cause: The resource attribute used in policy condition was invalid for the referenced resource type

Action: Fix the policy condition to use only valid attributes for the given resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10529: The resource attribute {0} used in policy condition or obligation is invalid resource attribute of type {1}.

Cause: The resource attribute used in policy condition was invalid for the referenced resource type

Action: Fix the policy condition to use only valid attributes for the given resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10529: The resource attribute {0} used in policy condition or obligation is invalid resource attribute of type {1}.

Cause: The resource attribute used in policy condition was invalid for the referenced resource type

Action: Fix the policy condition to use only valid attributes for the given resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-10530: Cannot create a policy {0} with AdminRole(s) {1}.

Cause: Cannot create a policy with AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10530: Cannot create a policy {0} with AdminRole(s) {1}.

Cause: Cannot create a policy with AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10530: Cannot create a policy {0} with AdminRole(s) {1}.

Cause: Cannot create a policy with AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10531: Cannot grant permission to AdminRole(s) {0}.

Cause: Cannot grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10531: Cannot grant permission to AdminRole(s) {0}.

Cause: Cannot grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10531: Cannot grant permission to AdminRole(s) {0}.

Cause: Cannot grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10532: Cannot grant AdminRole {0} to another AdminRole {1}.

Cause: Cannot grant AdminRole to another AdminRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10532: Cannot grant AdminRole {0} to another AdminRole {1}.

Cause: Cannot grant AdminRole to another AdminRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10532: Cannot grant AdminRole {0} to another AdminRole {1}.

Cause: Cannot grant AdminRole to another AdminRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10533: Cannot revoke AdminRole {0} from another AdminRole {1}.

Cause: Cannot revoke AdminRole from another AdminRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10533: Cannot revoke AdminRole {0} from another AdminRole {1}.

Cause: Cannot revoke AdminRole from another AdminRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10533: Cannot revoke AdminRole {0} from another AdminRole {1}.

Cause: Cannot revoke AdminRole from another AdminRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10534: Cannot grant AdminRole {0} to an AppRole {1}.

Cause: Cannot grant AdminRole to an AppRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10534: Cannot grant AdminRole {0} to an AppRole {1}.

Cause: Cannot grant AdminRole to an AppRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10534: Cannot grant AdminRole {0} to an AppRole {1}.

Cause: Cannot grant AdminRole to an AppRole.

Action: Change to grant AdminRole to either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10535: Cannot revoke AdminRole {0} from an AppRole {1}.

Cause: Cannot revoke AdminRole from an AppRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10535: Cannot revoke AdminRole {0} from an AppRole {1}.

Cause: Cannot revoke AdminRole from an AppRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10535: Cannot revoke AdminRole {0} from an AppRole {1}.

Cause: Cannot revoke AdminRole from an AppRole.

Action: Change to revoke AdminRole from either enterprise role or user.
Level: 1

Type: WARNING

Impact: Security

JPS-10536: AdminRole {0} cannot be managed outside of the AdminManager.

Cause: AdminRole cannot be managed outside of AdminManager.

Action: Use AdminManager for all AdminRole related administrative tasks.
Level: 1

Type: WARNING

Impact: Security

JPS-10536: AdminRole {0} cannot be managed outside of the AdminManager.

Cause: AdminRole cannot be managed outside of AdminManager.

Action: Use AdminManager for all AdminRole related administrative tasks.
Level: 1

Type: WARNING

Impact: Security

JPS-10536: AdminRole {0} cannot be managed outside of the AdminManager.

Cause: AdminRole cannot be managed outside of AdminManager.

Action: Use AdminManager for all AdminRole related administrative tasks.
Level: 1

Type: WARNING

Impact: Security

JPS-10537: Cannot modify grant permission to AdminRole(s) {0}.

Cause: Cannot modify grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10537: Cannot modify grant permission to AdminRole(s) {0}.

Cause: Cannot modify grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10537: Cannot modify grant permission to AdminRole(s) {0}.

Cause: Cannot modify grant permission to AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10538: Cannot revoke permission from AdminRole(s) {0}.

Cause: Cannot revoke permission from AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10538: Cannot revoke permission from AdminRole(s) {0}.

Cause: Cannot revoke permission from AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10538: Cannot revoke permission from AdminRole(s) {0}.

Cause: Cannot revoke permission from AdminRoleEntry(s).

Action: Remove the AdminRole principals from the principal list.
Level: 1

Type: WARNING

Impact: Security

JPS-10539: Basic policy cannot have {0} information.

Cause: Basic policy cannot have {0} information.

Action: Remove the information from basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10539: Basic policy cannot have {0} information.

Cause: Basic policy cannot have {0} information.

Action: Remove the information from basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10539: Basic policy cannot have {0} information.

Cause: Basic policy cannot have {0} information.

Action: Remove the information from basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10540: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Cause: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Action: Use ResourceActionsEntry with ResourceEntry for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10540: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Cause: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Action: Use ResourceActionsEntry with ResourceEntry for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10540: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Cause: Basic policy cannot have ResourceActionsEntry without ResourceEntry.

Action: Use ResourceActionsEntry with ResourceEntry for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10541: Basic policy cannot use Resource {0} without Resource Matcher Class.

Cause: Basic policy cannot use Resource {0} without Resource Matcher Class.

Action: Use Resource with Resource Matcher Class for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10541: Basic policy cannot use Resource {0} without Resource Matcher Class.

Cause: Basic policy cannot use Resource {0} without Resource Matcher Class.

Action: Use Resource with Resource Matcher Class for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10541: Basic policy cannot use Resource {0} without Resource Matcher Class.

Cause: Basic policy cannot use Resource {0} without Resource Matcher Class.

Action: Use Resource with Resource Matcher Class for basic policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10542: Default TransformerFactory cannot be located.

Cause: The TransformerFactory cannot be loaded

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10542: Default TransformerFactory cannot be located.

Cause: The TransformerFactory cannot be loaded

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10542: Default TransformerFactory cannot be located.

Cause: The TransformerFactory cannot be loaded

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10543: Failed to retrieve Transformer.

Cause: The TransformerFactory cannot generate a Transformer.

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10543: Failed to retrieve Transformer.

Cause: The TransformerFactory cannot generate a Transformer.

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10543: Failed to retrieve Transformer.

Cause: The TransformerFactory cannot generate a Transformer.

Action: Check the environment
Level: 1

Type: WARNING

Impact: Security

JPS-10544: The policy "{0}" already exists.

Cause: The role policy object exists.

Action: Create a role policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10544: The policy, {0}, exists.

Cause: The role policy object exists.

Action: Create a role policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10544: The policy, {0}, exists.

Cause: The role policy object exists.

Action: Create a role policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10545: The application role {0} could not be added since it already exists.

Cause: The application role could not be added since it already exists.

Action: Remove duplicate application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10545: The application role {0} could not be added since it already exists.

Cause: The application role could not be added since it already exists.

Action: Remove duplicate application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10545: The application role {0} could not be added since it already exists.

Cause: The application role could not be added since it already exists.

Action: Remove duplicate application role.
Level: 1

Type: WARNING

Impact: Security

JPS-10546: The resource {0}, {1} could not be added since it already exists.

Cause: The resource could not be added since it already exists.

Action: Remove duplicate resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10546: The resource {0}, {1} could not be added since it already exists.

Cause: The resource could not be added since it already exists.

Action: Remove duplicate resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10546: The resource {0}, {1} could not be added since it already exists.

Cause: The resource could not be added since it already exists.

Action: Remove duplicate resource.
Level: 1

Type: WARNING

Impact: Security

JPS-10547: The resource name expression {0}, {1} could not be added since it already exists.

Cause: The resource name expression could not be added since it already exists.

Action: Remove duplicate resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10547: The resource name expression {0}, {1} could not be added since it already exists.

Cause: The resource name expression could not be added since it already exists.

Action: Remove duplicate resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10547: The resource name expression {0}, {1} could not be added since it already exists.

Cause: The resource name expression could not be added since it already exists.

Action: Remove duplicate resource name expression.
Level: 1

Type: WARNING

Impact: Security

JPS-10548: The policy rule {0} already exists.

Cause: The policy rule already exists.

Action: Create policy rule with different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10548: The policy rule {0} already exists.

Cause: The policy rule already exists.

Action: Create policy rule with different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10548: The policy rule {0} already exists.

Cause: The policy rule already exists.

Action: Create policy rule with different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10549: The policy rule {0} is in use, could not be deleted.

Cause: The policy rule could not be deleted without cascade since it is in use.

Action: Cascade delete it or first remove all referring objects.
Level: 1

Type: WARNING

Impact: Security

JPS-10550: Attribute "{0}" already exists

Cause: Cannot have two attributes with the same name.

Action: Provide a new name to the attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10550: Attribute {0} already exists

Cause: Cannot have two attributes with the same name.

Action: Provide a new name to the attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10550: Attribute {0} already exists

Cause: Cannot have two attributes with the same name.

Action: Provide a new name to the attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10551: Attribute {0} does not exist

Cause: Attribute not found.

Action: Check the attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-10551: Attribute {0} does not exist

Cause: Attribute not found.

Action: Check the attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-10551: Attribute {0} does not exist

Cause: Attribute not found.

Action: Check the attribute name.
Level: 1

Type: WARNING

Impact: Security

JPS-10552: Attribute {0} is used.

Cause: Attribute is already used.

Action: Remove the objects which use this attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10552: Attribute {0} is used.

Cause: Attribute is already used.

Action: Remove the objects which use this attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10552: Attribute {0} is used.

Cause: Attribute is already used.

Action: Remove the objects which use this attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10553: Attribute {0} does not belong to current application.

Cause: Attribute does not belong to current application policy.

Action: Modify the attribute with extension manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10553: Attribute {0} does not belong to current application.

Cause: Attribute does not belong to current application policy.

Action: Modify the attribute with extension manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10553: Attribute {0} does not belong to current application.

Cause: Attribute does not belong to current application policy.

Action: Modify the attribute with extension manager from correct application policy.
Level: 1

Type: WARNING

Impact: Security

JPS-10554: The name of Attribute in policy repository is missing

Cause: Attribute in policy store has no name.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10554: The name of Attribute in policy repository is missing

Cause: Attribute in policy store has no name.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10554: The name of Attribute in policy repository is missing

Cause: Attribute in policy store has no name.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10555: The type of Attribute in policy repository is missing

Cause: Attribute in policy store has no type.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10555: The type of Attribute in policy repository is missing

Cause: Attribute in policy store has no type.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10555: The type of Attribute in policy repository is missing

Cause: Attribute in policy store has no type.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10556: The category of Attribute in policy repository is missing

Cause: Attribute in policy store has no category.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10556: The category of Attribute in policy repository is missing

Cause: Attribute in policy store has no category.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10556: The category of Attribute in policy repository is missing

Cause: Attribute in policy store has no category.

Action: Check the underline policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10557: Cannot overwrite a built-in attribute, {0}.

Cause: Try to overwrite a built-in attribute.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10557: Cannot overwrite a built-in attribute, {0}.

Cause: Try to overwrite a built-in attribute.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10557: Cannot overwrite a built-in attribute, {0}.

Cause: Try to overwrite a built-in attribute.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10558: Cannot modify a built-in attribute, {0}.

Cause: Try to modify a built-in attribute.

Action: Do not modify a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10558: Cannot modify a built-in attribute, {0}.

Cause: Try to modify a built-in attribute.

Action: Do not modify a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10558: Cannot modify a built-in attribute, {0}.

Cause: Try to modify a built-in attribute.

Action: Do not modify a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10559: Cannot delete a built-in attribute, {0}.

Cause: Try to delete a built-in attribute.

Action: Do not delete a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10559: Cannot delete a built-in attribute, {0}.

Cause: Try to delete a built-in attribute.

Action: Do not delete a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10559: Cannot delete a built-in attribute, {0}.

Cause: Try to delete a built-in attribute.

Action: Do not delete a built-in attribute.
Level: 1

Type: WARNING

Impact: Security

JPS-10581: Cannot overwrite a built-in function, {0}.

Cause: Try to overwrite a built-in function.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10581: Cannot overwrite a built-in function, {0}.

Cause: Try to overwrite a built-in function.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10581: Cannot overwrite a built-in function, {0}.

Cause: Try to overwrite a built-in function.

Action: Do not overwrite a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10582: The function does not exist, {0}.

Cause: The function does not exist.

Action: Check the function name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10582: The function does not exist, {0}.

Cause: The function does not exist.

Action: Check the function name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10582: The function does not exist, {0}.

Cause: The function does not exist.

Action: Check the function name passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10583: The function is in use, {0}.

Cause: The function is in use.

Action: Cannot delete a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10583: The function is in use, {0}.

Cause: The function is in use.

Action: Cannot delete a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10583: The function is in use, {0}.

Cause: The function is in use.

Action: Cannot delete a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10584: The function is used in some policies, your changes on return type may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change return type of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10584: The function is used in some policies, your changes on return type may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change return type of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10584: The function is used in some policies, your changes on return type may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change return type of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10585: The function is used in some policies, your changes on parameter types may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change parameter types of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10585: The function is used in some policies, your changes on parameter types may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change parameter types of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10585: The function is used in some policies, your changes on parameter types may lead to unpredictable issues.

Cause: The function is in use.

Action: Cannot change parameter types of a function in use.
Level: 1

Type: WARNING

Impact: Security

JPS-10586: Cannot modify a built-in function, {0}.

Cause: Try to modify a built-in function.

Action: Do not modify a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10586: Cannot modify a built-in function, {0}.

Cause: Try to modify a built-in function.

Action: Do not modify a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10586: Cannot modify a built-in function, {0}.

Cause: Try to modify a built-in function.

Action: Do not modify a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10587: Cannot delete a built-in function, {0}.

Cause: Try to delete a built-in function.

Action: Do not delete a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10587: Cannot delete a built-in function, {0}.

Cause: Try to delete a built-in function.

Action: Do not delete a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10587: Cannot delete a built-in function, {0}.

Cause: Try to delete a built-in function.

Action: Do not delete a built-in function.
Level: 1

Type: WARNING

Impact: Security

JPS-10588: The function "{0}" already exists.

Cause: The function exists.

Action: Create a function with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10588: The function already exists, {0}.

Cause: The function exists.

Action: Create a function with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10588: The function already exists, {0}.

Cause: The function exists.

Action: Create a function with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10589: Cascade delete is not supported.

Cause: Cascade delete not supported.

Action: Set the cascade delete parameter to false.
Level: 1

Type: WARNING

Impact: Security

JPS-10589: Cascade delete is not supported.

Cause: Cascade delete not supported.

Action: Set the cascade delete parameter to false.
Level: 1

Type: WARNING

Impact: Security

JPS-10589: Cascade delete is not supported.

Cause: Cascade delete not supported.

Action: Set the cascade delete parameter to false.
Level: 1

Type: WARNING

Impact: Security

JPS-10590: Cannot find the function entry for function name {0}.

Cause: Cannot find the function entry for function name.

Action: Check function entry in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10590: Cannot find the function entry for function name {0}.

Cause: Cannot find the function entry for function name.

Action: Check function entry in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10590: Cannot find the function entry for function name {0}.

Cause: Cannot find the function entry for function name.

Action: Check function entry in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10591: Cannot find the expression type for expression {0}.

Cause: Cannot find the expression type for the expression.

Action: Check expression in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10591: Cannot find the expression type for expression {0}.

Cause: Cannot find the expression type for the expression.

Action: Check expression in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10591: Cannot find the expression type for expression {0}.

Cause: Cannot find the expression type for the expression.

Action: Check expression in policy repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10592: Operation {1} is not allowed for multi valued attribute {0}

Cause: The category of Attribute is Invalid.

Action: The category of Attribute is Invalid. Supply a valid Attribute category
Level: 1

Type: WARNING

Impact: Security

JPS-10592: Operation {1} is not allowed for multi valued attribute {0}

Cause: The category of Attribute is Invalid.

Action: The category of Attribute is Invalid. Supply a valid Attribute category
Level: 1

Type: WARNING

Impact: Security

JPS-10592: Operation {1} is not allowed for multi valued attribute {0}

Cause: The category of Attribute is Invalid.

Action: The category of Attribute is Invalid. Supply a valid Attribute category
Level: 1

Type: WARNING

Impact: Security

JPS-10600: Failed to initialize PD instance.

Cause: Failed to initialize PD instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10600: Failed to initialize PD instance.

Cause: Failed to initialize PD instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10600: Failed to initialize PD instance.

Cause: Failed to initialize PD instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10601: Failed to initialize PolicyDistributionManager instance.

Cause: Failed to initialize PolicyDistributionManager instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10601: Failed to initialize PolicyDistributionManager instance.

Cause: Failed to initialize PolicyDistributionManager instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10601: Failed to initialize PolicyDistributionManager instance.

Cause: Failed to initialize PolicyDistributionManager instance.

Action: Refer to the base exception in logs to resolve the issue.
Level: 1

Type: WARNING

Impact: Security

JPS-10602: PD has not been initialized.

Cause: PD has not been initialized.

Action: Check if OPSS policy store provider has been initialized successfully.
Level: 1

Type: WARNING

Impact: Security

JPS-10602: PD has not been initialized.

Cause: PD has not been initialized.

Action: Check if OPSS policy store provider has been initialized successfully.
Level: 1

Type: WARNING

Impact: Security

JPS-10602: PD has not been initialized.

Cause: PD has not been initialized.

Action: Check if OPSS policy store provider has been initialized successfully.
Level: 1

Type: WARNING

Impact: Security

JPS-10603: FAILURE: Retry {0} failed after {1} times retries due to following exception {2}.

Cause: PD operation failed to retry.

Action: Check connectivity to backend repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10603: FAILURE: Retry {0} failed after {1} times retries.

Cause: PD operation failed to retry.

Action: Check connectivity to backend repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10603: FAILURE: Retry {0} failed after {1} times retries.

Cause: PD operation failed to retry.

Action: Check connectivity to backend repository.
Level: 1

Type: WARNING

Impact: Security

JPS-10604: The operation is not allowed for non-controlled mode application {0}.

Cause: Can not distribute policy for non-controlled policy distribution mode application

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10604: The operation is not allowed for non-controlled mode application {0}.

Cause: Can not distribute policy for non-controlled policy distribution mode application

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10604: The operation is not allowed for non-controlled mode application {0}.

Cause: Can not distribute policy for non-controlled policy distribution mode application

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10605: Failed to distribute policy for catch exception.

Cause: Distribute policy failed for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10605: Failed to distribute policy for catch exception.

Cause: Distribute policy failed for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10605: Failed to distribute policy for catch exception.

Cause: Distribute policy failed for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10606: Failed to distribute policy to PDP {0} for catch exception {1}.

Cause: Failed to distribute policy to pdp for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10606: Failed to distribute policy to PDP {0} for catch exception {1}.

Cause: Failed to distribute policy to pdp for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10606: Failed to distribute policy to PDP {0} for catch exception {1}.

Cause: Failed to distribute policy to pdp for catch exception

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10607: Invalid cache key {0} in {1} cache.

Cause: Invalid cache key

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10607: Invalid cache key {0} in {1} cache.

Cause: Invalid cache key

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10607: Invalid cache key {0} in {1} cache.

Cause: Invalid cache key

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10608: Failed to copy files from active directory {0} to update directory {1}.

Cause: Failed to copy cache file from active directory to update directory

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10608: Failed to copy files from active directory {0} to update directory {1}.

Cause: Failed to copy cache file from active directory to update directory

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10608: Failed to copy files from active directory {0} to update directory {1}.

Cause: Failed to copy cache file from active directory to update directory

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10609: Failed to write state.chk file.

Cause: Failed to write state.chk file

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10609: Failed to write state.chk file.

Cause: Failed to write state.chk file

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10609: Failed to write state.chk file.

Cause: Failed to write state.chk file

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10610: Failed to update local cache since distributed payload for application {0} is empty.

Cause: Failed to update local cache since distributed payload is empty

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10610: Failed to update local cache since distributed payload for application {0} is empty.

Cause: Failed to update local cache since distributed payload is empty

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10610: Failed to update local cache since distributed payload for application {0} is empty.

Cause: Failed to update local cache since distributed payload is empty

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10611: Invalid distribution state {0} in step {1}.

Cause: Invalid distribution state

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10611: Invalid distribution state {0} in step {1}.

Cause: Invalid distribution state

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10611: Invalid distribution state {0} in step {1}.

Cause: Invalid distribution state

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10612: Local cache file verification failed, so redistribute all binding applications

Cause: Failed to verify local cache file, so need to redistribution all binding applications

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10612: Local cache file verification failed, so redistribute all binding applications

Cause: Failed to verify local cache file, so need to redistribution all binding applications

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10612: Local cache file verification failed, so redistribute all binding applications

Cause: Failed to verify local cache file, so need to redistribution all binding applications

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10613: Failed to parse PD port number, do not start PD registration web service.

Cause: Failed to parse PD port number, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10613: Failed to parse PD port number, do not start PD registration web service.

Cause: Failed to parse PD port number, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10613: Failed to parse PD port number, do not start PD registration web service.

Cause: Failed to parse PD port number, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10614: Failed to start PD registration web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10614: Failed to start PD registration web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10614: Failed to start PD registration web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10615: Catch exception.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10615: Catch exception.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10615: Catch exception.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10616: Failed to find local host name, do not start PD registration web service.

Cause: Failed to find local host name, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10616: Failed to find local host name, do not start PD registration web service.

Cause: Failed to find local host name, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10616: Failed to find local host name, do not start PD registration web service.

Cause: Failed to find local host name, do not start PD registration web service.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10617: Failed to start PD push policy web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10617: Failed to start PD push policy web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10617: Failed to start PD push policy web service for catch exception.

Cause: Failed to start PD registration web service for catch exception.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10618: Invalid SSL configuration.

Cause: Invalid SSL configuration, please check log for details

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10618: Invalid SSL configuration.

Cause: Invalid SSL configuration, please check log for details

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10618: Invalid SSL configuration.

Cause: Invalid SSL configuration, please check log for details

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10619: Failed to initialize cipher {0} for local cache encryption/decryption.

Cause: Failed to initialize cipher for local cache encryption/decryption.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10619: Failed to initialize cipher {0} for local cache encryption/decryption.

Cause: Failed to initialize cipher for local cache encryption/decryption.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10619: Failed to initialize cipher {0} for local cache encryption/decryption.

Cause: Failed to initialize cipher for local cache encryption/decryption.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10620: Exception reported in registration thread.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10620: Exception reported in registration thread.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10620: Exception reported in registration thread.

Cause: Catch interrupt exception in start registration service thread.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10621: PD Lock not found

Cause: PD Lock node not found.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10621: PD Lock not found

Cause: PD Lock node not found.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10621: PD Lock not found

Cause: PD Lock node not found.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10622: Invalid PD Lock update time {0}.

Cause: Invalid PD Lock update time stamp.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10622: Invalid PD Lock update time {0}.

Cause: Invalid PD Lock update time stamp.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10622: Invalid PD Lock update time {0}.

Cause: Invalid PD Lock update time stamp.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10623: PD is running in another Admin, please distribute policy after the process finished.

Cause: PD is running in another Admin, please distribute policy after the process finished.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10623: PD is running in another Admin, please distribute policy after the process finished.

Cause: PD is running in another Admin, please distribute policy after the process finished.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10623: PD is running in another Admin, please distribute policy after the process finished.

Cause: PD is running in another Admin, please distribute policy after the process finished.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10624: Failed to connect primary server, try secondary server.

Cause: Failed to connect primary server, try secondary server.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10624: Failed to connect primary server, try secondary server.

Cause: Failed to connect primary server, try secondary server.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10624: Failed to connect primary server, try secondary server.

Cause: Failed to connect primary server, try secondary server.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10625: Failed to read from the local cache. The cache will be removed. Reason: {0}

Cause: Failed to read from the local cache. The cache will be removed.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10625: Failed to read from the local cache. The cache will be removed. Reason: {0}

Cause: Failed to read from the local cache. The cache will be removed.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10625: Failed to read from the local cache. The cache will be removed. Reason: {0}

Cause: Failed to read from the local cache. The cache will be removed.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10626: Encryption/Decryption of the local cache file using the algorithm {0} is not supported.

Cause: The specified algorithm for local cache encryption/decryption is not supported.

Action: Please check PDP service configuration in jps-config.xml file.
Level: 1

Type: ERROR

Impact: Security

JPS-10626: Encryption/Decryption of the local cache file using the algorithm {0} is not supported.

Cause: The specified algorithm for local cache encryption/decryption is not supported.

Action: Please check PDP service configuration in jps-config.xml file.
Level: 1

Type: ERROR

Impact: Security

JPS-10626: Encryption/Decryption of the local cache file using the algorithm {0} is not supported.

Cause: The specified algorithm for local cache encryption/decryption is not supported.

Action: Please check PDP service configuration in jps-config.xml file.
Level: 1

Type: ERROR

Impact: Security

JPS-10627: The key length used to initialize cipher {0} is not valid. Expected key length is {1} bits, but raw key length is {2} bits.

Cause: The key length used to initialize cipher is not valid.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10627: The key length used to initialize cipher {0} is not valid. Expected key length is {1} bits, but raw key length is {2} bits.

Cause: The key length used to initialize cipher is not valid.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10627: The key length used to initialize cipher {0} is not valid. Expected key length is {1} bits, but raw key length is {2} bits.

Cause: The key length used to initialize cipher is not valid.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10628: Retry {0} for the {1} times.

Cause: Retry {0} for the {1} times.

Action: No actions are required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10629: SUCCESS: Retry {0} successfully after {1} times retries.

Cause: SUCCESS: Retry {0} successfully after {1} times retries.

Action: No actions are required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10630: The default DB policy store is missing for mixed mode.

Cause: The default DB policy store is missing for mixed mode.

Action: Configure one DB policy store instance.
Level: 1

Type: ERROR

Impact: Security

JPS-10631: Failed to distribute policy to Real Application Security Database, target RAS database {0}, exception {1}.

Cause: Failed to distribute policy to Real Application Security Database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10632: Failed to obtain the datasource for Real Application Security Database, target RAS database {0}, exception {1}

Cause: Failed to obtain the datasource for Real Application Security Database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10633: Failed to fetch the information from the intermediate table, target RAS database {0}, exception {1}"

Cause: Failed to fetch the information from the intermediate table

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10634: Failed to prepare data for distributing policy to Real Application Security Database, application name {0}, exception {1}.

Cause: Failed to prepare data for distributing policy to Real Application Security Database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10635: Failed to update the intermediate table in the policy store database, target RAS database {0}, exception {1}.

Cause: Failed to update the intermediate table in the policy store database

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10636: Incorrect Real Application Security PDP address format.

Cause: Incorrect Real Application Security PDP address format

Action: Refer to the log files for details. The correct format should start with "ras:"
Level: 1

Type: ERROR

Impact: Security

JPS-10700: The value of attribute {0} should be unique

Cause: The unique attribute has duplicated values.

Action: Keep attribute value unique.
Level: 1

Type: WARNING

Impact: Security

JPS-10700: The value of attribute {0} should be unique

Cause: The unique attribute has duplicated values.

Action: Keep attribute value unique.
Level: 1

Type: WARNING

Impact: Security

JPS-10700: The value of attribute {0} should be unique

Cause: The unique attribute has duplicated values.

Action: Keep attribute value unique.
Level: 1

Type: WARNING

Impact: Security

JPS-10701: Data Source lookup failure. It is safe to ignore the warning during Websphere server starts up. If you still get the warning after WebSphere server starts up, check your configuration.

Cause: Websphere data source lookup failure.

Action: Safe to ignore during WebSphere starts up.
Level: 1

Type: ERROR

Impact: Security

JPS-10701: Data Source lookup failure. It is safe to ignore the warning during Websphere server starts up. If you still get the warning after WebSphere server starts up, check your configuration.

Cause: Websphere data source lookup failure.

Action: Safe to ignore during WebSphere starts up.
Level: 1

Type: ERROR

Impact: Security

JPS-10701: Data Source lookup failure. It is safe to ignore the warning during Websphere server starts up. If you still get the warning after WebSphere server starts up, check your configuration.

Cause: Websphere data source lookup failure.

Action: Safe to ignore during WebSphere starts up.
Level: 1

Type: ERROR

Impact: Security

JPS-10702: The datasource {0} is not found.

Cause: Given datasource jndi name is not found.

Action: Check datasource jndi name.
Level: 1

Type: ERROR

Impact: Security

JPS-10702: The datasource {0} is not found.

Cause: Given datasource jndi name is not found.

Action: Check datasource jndi name.
Level: 1

Type: ERROR

Impact: Security

JPS-10702: The datasource {0} is not found.

Cause: Given datasource jndi name is not found.

Action: Check datasource jndi name.
Level: 1

Type: ERROR

Impact: Security

JPS-10750: Application Policy unique name: "{0}" is invalid

Cause: The application policy unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10750: Application Policy unique name: "{0}" is invalid

Cause: The application policy unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10750: Application Policy unique name: "{0}" is invalid

Cause: The application policy unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10751: The version number of Application policy : "{0}" is invalid

Cause: The application policy version number is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10751: The version number of Application policy : "{0}" is invalid

Cause: The application policy version number is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10751: The version number of Application policy : "{0}" is invalid

Cause: The application policy version number is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10752: The policy entry unique name: "{0}" is invalid

Cause: The policy entry unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10752: The policy entry unique name: "{0}" is invalid

Cause: The policy entry unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10752: The policy entry unique name: "{0}" is invalid

Cause: The policy entry unique name is invalid

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10800: The role policy object "{0}" does not exist.

Cause: The role policy object does not exist.

Action: Check if the target role policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10800: The role policy object does not exist for {0}.

Cause: The role policy object does not exist.

Action: Check if the target role policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10800: The role policy object does not exist for {0}.

Cause: The role policy object does not exist.

Action: Check if the target role policy exists.
Level: 1

Type: WARNING

Impact: Security

JPS-10801: The role policy object "{0}" already exists.

Cause: The policy object exists.

Action: Create a policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10801: The role policy object already exists for {0}.

Cause: The policy object exists.

Action: Create a policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10801: The role policy object already exists for {0}.

Cause: The policy object exists.

Action: Create a policy with a different name.
Level: 1

Type: WARNING

Impact: Security

JPS-10802: Application role hierarchy cannot participate in a role mapping policy.

Cause: One or more principals in the role mapping policy are of type: ApplicationRole or AnonymousRole or AuthenticatedRole or and AdminRole.

Action: Identify the principal type in the incomming principals, and ensure only a user or group principal type is supplied.
Level: 1

Type: WARNING

Impact: Security

JPS-10802: Application role hierarchy cannot participate in a role mapping policy.

Cause: One or more principals in the role mapping policy are of type: ApplicationRole or AnonymousRole or AuthenticatedRole or and AdminRole.

Action: Identify the principal type in the incomming principals, and ensure only a user or group principal type is supplied.
Level: 1

Type: WARNING

Impact: Security

JPS-10802: Application role hierarchy cannot participate in a role mapping policy.

Cause: One or more principals in the role mapping policy are of type: ApplicationRole or AnonymousRole or AuthenticatedRole or and AdminRole.

Action: Identify the principal type in the incomming principals, and ensure only a user or group principal type is supplied.
Level: 1

Type: WARNING

Impact: Security

JPS-10803: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Cause: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Action: Ensure that resource(s)/resource name expression(s) are not permission based.
Level: 1

Type: WARNING

Impact: Security

JPS-10803: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Cause: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Action: Ensure that resource(s)/resource name expression(s) are not permission based.
Level: 1

Type: WARNING

Impact: Security

JPS-10803: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Cause: At least one of the Resource(s)/Resource Name Expression(s) used in Role Policy are permission based. This is not allowed.

Action: Ensure that resource(s)/resource name expression(s) are not permission based.
Level: 1

Type: WARNING

Impact: Security

JPS-10804: The advice {0} already exists.

Cause: The advice already exists in the policy entry.

Action: Check AdviceEntry passed in.
Level: 1

Type: WARNING

Impact: Security

JPS-10850: The SM Config Tool is used to configure the Security Modules for Oracle Entitlements Server Here are the various options that it will accept -smType <java, wls, ws, rmi, was, jboss> -smConfigId <config id of sm is always required> -serverLocation <in case of was, wls, jboss, this is the location of the server> -pdServer OES Admin Server hostName -pdPort SSL Port for OES Admin Server -pdClientPort SSL Port for WLS SM client -serverNodeName - server node name of websphere -serverName - server instance name of websphere -serverUserName - user name of application server -serverPassword - password of application server -prpFileName - path for the prp file used.

Cause: When help is asked for

Action: Help message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10850: The SM Config Tool is used to configure the Security Modules for Oracle Entitlements Server Here are the various options that it will accept -smType <java, wls, ws, rmi, was, jboss> -smConfigId <config id of sm is always required> -serverLocation <in case of was, wls, jboss, this is the location of the server> -pdServer OES Admin Server hostName -pdPort SSL Port for OES Admin Server -pdClientPort SSL Port for WLS SM client -serverNodeName - server node name of websphere -serverName - server instance name of websphere -serverUserName - user name of application server -serverPassword - password of application server -prpFileName - path for the prp file used.

Cause: When help is asked for

Action: Help message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10850: The SM Config Tool is used to configure the Security Modules for Oracle Entitlements Server Here are the various options that it will accept -smType <java, wls, ws, rmi, was, jboss> -smConfigId <config id of sm is always required> -serverLocation <in case of was, wls, jboss, this is the location of the server> -pdServer OES Admin Server hostName -pdPort SSL Port for OES Admin Server -pdClientPort SSL Port for WLS SM client -serverNodeName - server node name of websphere -serverName - server instance name of websphere -serverUserName - user name of application server -serverPassword - password of application server -prpFileName - path for the prp file used.

Cause: When help is asked for

Action: Help message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10851: Please enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10851: Please enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10851: Please enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10852: Configuring for PDP proxy mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10852: Configuring for PDP proxy mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10852: Configuring for PDP proxy mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10853: Configuring for Controlled Policy Distribution Mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10853: Configuring for Controlled Policy Distribution Mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10853: Configuring for Controlled Policy Distribution Mode

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10854: Configuring for Direct Connection to the Database Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10854: Configuring for Direct Connection to the Database Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10854: Configuring for Direct Connection to the Database Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10855: Configuring for Direct Connection to the Ldap Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10855: Configuring for Direct Connection to the Ldap Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10855: Configuring for Direct Connection to the Ldap Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10856: Configuring for Direct Connection to the Derby Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10856: Configuring for Direct Connection to the Derby Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10856: Configuring for Direct Connection to the Derby Policy Store

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10857: Value is missing or corrupt {0}. Please supply an appropriate value.

Cause: Error Message

Action: Please supply the required parameters as specified in the message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10857: Value is missing or corrupt {0}. Please supply an appropriate value.

Cause: Error Message

Action: Please supply the required parameters as specified in the message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10857: Value is missing or corrupt {0}. Please supply an appropriate value.

Cause: Error Message

Action: Please supply the required parameters as specified in the message.
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10858: Security Module configuration is created at: {0}

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10858: Security Module configuration is created at: {0}

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10858: Security Module configuration is created at: {0}

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10859: Please re-enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10859: Please re-enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10859: Please re-enter a value for {0}:

Cause: Prompt Message

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10890: sys_obj_q

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10890: sys_obj_q

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10890: sys_obj_q

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10891: Full qualified resource name on which the query is performed: /foo/bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10891: Full qualified resource name on which the query is performed: /foo/bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10891: Full qualified resource name on which the query is performed: /foo/bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10892: sys_subjectroles

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10893: List of unqualified role names granted to user for current request

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10900: The enrollment response is truncated.

Cause: Enrollment response is truncated.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10900: TBD

Cause: Enrollment response is truncated.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10900: TBD

Cause: Enrollment response is truncated.

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-10901: Keystore {0} does not exist.

Cause: Keystore {0} does not exist.

Action: Check the file system.
Level: 1

Type: ERROR

Impact: Security

JPS-10901: TBD

Cause: Keystore {0} does not exist.

Action: Check the file system.
Level: 1

Type: ERROR

Impact: Security

JPS-10901: TBD

Cause: Keystore {0} does not exist.

Action: Check the file system.
Level: 1

Type: ERROR

Impact: Security

JPS-10902: Enrollment server error.

Cause: Enrollment server error.

Action: Check enrollment server status.
Level: 1

Type: ERROR

Impact: Security

JPS-10902: TBD

Cause: Enrollment server error.

Action: Check enrollment server status.
Level: 1

Type: ERROR

Impact: Security

JPS-10902: TBD

Cause: Enrollment server error.

Action: Check enrollment server status.
Level: 1

Type: ERROR

Impact: Security

JPS-10903: Enrollment is proceeded successfully.

Cause: Enrollment is proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10903: TBD

Cause: Enrollment is proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10903: TBD

Cause: Enrollment is proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10904: Enrollment is not proceeded successfully.

Cause: Enrollment is not proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10904: TBD

Cause: Enrollment is not proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10904: TBD

Cause: Enrollment is not proceeded successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10905: The program works in console mode only.

Cause: The program works in console mode only.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10905: TBD

Cause: The program works in console mode only.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10905: TBD

Cause: The program works in console mode only.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10906: Enter password for {0}:

Cause: Enter password for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10906: Enter password for {0}:

Cause: Enter password for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10906: Enter password for {0}:

Cause: Enter password for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10907: Enter password for {0} again:

Cause: Enter password for {0} again:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10907: Enter password for {0} again:

Cause: Enter password for {0} again:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10907: Enter password for {0} again:

Cause: Enter password for {0} again:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10908: The passwords you inputted do not match.

Cause: The passwords you inputted do not match.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10908: The passwords you inputted do not match.

Cause: The passwords you inputted do not match.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10908: The passwords you inputted do not match.

Cause: The passwords you inputted do not match.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10909: Passwords are saved in credential store.

Cause: Passwords are saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10909: Passwords are saved in credential store.

Cause: Passwords are saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10909: Passwords are saved in credential store.

Cause: Passwords are saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10910: Passwords are not saved in credential store.

Cause: Passwords are not saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10910: TBD

Cause: Passwords are not saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10910: TBD

Cause: Passwords are not saved in credential store.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10911: {0} is not set.

Cause: {0} is not set.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10911: TBD

Cause: {0} is not set.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10911: TBD

Cause: {0} is not set.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10912: Keystores are initialized successfully.

Cause: Keystores are initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10912: TBD

Cause: Keystores are initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10912: TBD

Cause: Keystores are initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10913: Keystores are not initialized successfully.

Cause: Keystores are not initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10913: TBD

Cause: Keystores are not initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10913: TBD

Cause: Keystores are not initialized successfully.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10914: Enter username for {0}:

Cause: Enter username for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10914: TBD

Cause: Enter username for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10914: TBD

Cause: Enter username for {0}:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10915: Enter credential map name:

Cause: Enter credential map name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10915: Enter credential map name:

Cause: Enter credential map name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10915: Enter credential map name:

Cause: Enter credential map name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10916: Enter credential key name:

Cause: Enter credential key name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10916: Enter credential key name:

Cause: Enter credential key name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10916: Enter credential key name:

Cause: Enter credential key name:

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10917: Input password can not be null.

Cause: The passwords you inputted can not be null.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10917: Input password can not be null.

Cause: The passwords you inputted can not be null.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10917: Input password can not be null.

Cause: The passwords you inputted can not be null.

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10920: function: urn:oasis:names:tc:xacml:1.0:function:integer-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10920: function: urn:oasis:names:tc:xacml:1.0:function:integer-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10920: function: urn:oasis:names:tc:xacml:1.0:function:integer-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10921: function: urn:oasis:names:tc:xacml:1.0:function:date-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10921: function: urn:oasis:names:tc:xacml:1.0:function:date-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10921: function: urn:oasis:names:tc:xacml:1.0:function:date-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10922: function: urn:oasis:names:tc:xacml:1.0:function:time-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10922: function: urn:oasis:names:tc:xacml:1.0:function:time-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10922: function: urn:oasis:names:tc:xacml:1.0:function:time-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10923: function: urn:oasis:names:tc:xacml:1.0:function:string-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10923: function: urn:oasis:names:tc:xacml:1.0:function:string-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10923: function: urn:oasis:names:tc:xacml:1.0:function:string-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10924: function: urn:oasis:names:tc:xacml:1.0:function:integer-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10924: function: urn:oasis:names:tc:xacml:1.0:function:integer-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10924: function: urn:oasis:names:tc:xacml:1.0:function:integer-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10925: function: urn:oasis:names:tc:xacml:1.0:function:date-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10925: function: urn:oasis:names:tc:xacml:1.0:function:date-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10925: function: urn:oasis:names:tc:xacml:1.0:function:date-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10926: function: urn:oasis:names:tc:xacml:1.0:function:time-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10926: function: urn:oasis:names:tc:xacml:1.0:function:time-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10926: function: urn:oasis:names:tc:xacml:1.0:function:time-is-in The function returns true if the LHS (left-hand side) matches one of the values in RHS (right-hand side); LHS should be single-valued. RHS can be single or multi-valued.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10927: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10927: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10927: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10928: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10928: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10928: function: urn:oasis:names:tc:xacml:1.0:function:integer-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10929: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10929: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10929: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10930: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10930: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10930: function: urn:oasis:names:tc:xacml:1.0:function:integer-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10931: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10931: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10931: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10932: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10932: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10932: function: urn:oasis:names:tc:xacml:1.0:function:time-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10933: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10933: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10933: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10934: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10934: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10934: function: urn:oasis:names:tc:xacml:1.0:function:time-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10935: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10935: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10935: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than The function returns true if the value of LHS is greater than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10936: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10936: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10936: function: urn:oasis:names:tc:xacml:1.0:function:date-greater-than-or-equal The function returns true if the value of LHS is greater than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10937: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10937: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10937: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than The function returns true if the value of LHS is less than RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10938: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10938: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10938: function: urn:oasis:names:tc:xacml:1.0:function:date-less-than-or-equal The function returns true if the value of LHS is less than or equals to RHS. Both LHS and RHS should be single value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10939: function: urn:oasis:names:tc:xacml:1.0:function:string-regexp-match The LHS should be a single-value string type attribute/value. The RHS should be a single value string which complies with Java Regular Expression.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10939: function: urn:oasis:names:tc:xacml:1.0:function:string-regexp-match The LHS should be a single-value string type attribute/value. The RHS should be a single value string which complies with Java Regular Expression.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10939: function: urn:oasis:names:tc:xacml:1.0:function:string-regexp-match The LHS should be a single-value string type attribute/value. The RHS should be a single value string which complies with Java Regular Expression.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10940: function: urn:oasis:names:tc:xacml:1.0:function:or The function stands for an OR operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10940: function: urn:oasis:names:tc:xacml:1.0:function:or The function stands for an OR operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10940: function: urn:oasis:names:tc:xacml:1.0:function:or The function stands for an OR operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10941: function: urn:oasis:names:tc:xacml:1.0:function:and The function stands for an AND operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10941: function: urn:oasis:names:tc:xacml:1.0:function:and The function stands for an AND operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10941: function: urn:oasis:names:tc:xacml:1.0:function:and The function stands for an AND operation between two single-value boolean expressions/values.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10942: function: urn:oasis:names:tc:xacml:1.0:function:not The function stands for a NOT operation on a single-value boolean expression/value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10942: function: urn:oasis:names:tc:xacml:1.0:function:not The function stands for a NOT operation on a single-value boolean expression/value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10942: function: urn:oasis:names:tc:xacml:1.0:function:not The function stands for a NOT operation on a single-value boolean expression/value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10943: function: valid_for_mseconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10943: function: valid_for_mseconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10943: function: valid_for_mseconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10944: function: valid_for_seconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10944: function: valid_for_seconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10944: function: valid_for_seconds The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10945: function: valid_for_minutes The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10945: function: valid_for_minutes The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10945: function: valid_for_minutes The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10946: function: valid_for_hours The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10946: function: valid_for_hours The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10946: function: valid_for_hours The function accepts a single integer value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10947: function: valid_until_time The function accepts a single time value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10947: function: valid_until_time The function accepts a single time value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10947: function: valid_until_time The function accepts a single time value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10948: function: valid_until_date The function accepts a single date value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10948: function: valid_until_date The function accepts a single date value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10948: function: valid_until_date The function accepts a single date value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10949: function: sys_defined The function accepts a single string value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10949: function: sys_defined The function accepts a single string value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10949: function: sys_defined The function accepts a single string value.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10950: current_gmt_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10950: current_gmt_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10950: current_gmt_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10951: current_gmt_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10951: current_gmt_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10951: current_gmt_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10952: sys_subjectgroups

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10952: sys_subjectgroups

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10952: sys_subjectgroups

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10953: sys_user

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10953: sys_user

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10953: sys_user

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10954: sys_app

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10954: sys_app

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10954: sys_app

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10955: sys_obj_type

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10955: sys_obj_type

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10955: sys_obj_type

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10956: sys_obj

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10956: sys_obj

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10956: sys_obj

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10957: sys_privilege

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10957: sys_privilege

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10957: sys_privilege

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10958: boolean_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10958: boolean_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10958: boolean_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10959: string_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10959: string_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10959: string_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10960: integer_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10960: integer_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10960: integer_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10961: date_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10961: date_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10961: date_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10962: time_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10962: time_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10962: time_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10963: string_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10963: string_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10963: string_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10964: integer_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10964: integer_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10964: integer_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10965: date_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10965: date_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10965: date_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10966: time_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10966: time_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10966: time_is_in

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10967: integer_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10967: integer_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10967: integer_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10968: integer_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10968: integer_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10968: integer_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10969: integer_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10969: integer_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10969: integer_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10970: integer_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10970: integer_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10970: integer_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10971: time_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10971: time_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10971: time_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10972: time_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10972: time_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10972: time_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10973: time_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10973: time_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10973: time_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10974: time_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10974: time_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10974: time_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10975: date_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10975: date_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10975: date_greater_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10976: date_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10976: date_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10976: date_greater_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10977: date_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10977: date_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10977: date_less_than

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10978: date_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10978: date_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10978: date_less_than_or_equal

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10979: string_regexp_match

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10979: string_regexp_match

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10979: string_regexp_match

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10980: or

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10980: or

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10980: or

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10981: and

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10981: and

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10981: and

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10982: not

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10982: not

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10982: not

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10983: valid_for_mseconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10983: valid_for_mseconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10983: valid_for_mseconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10984: valid_for_seconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10984: valid_for_seconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10984: valid_for_seconds

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10985: valid_for_minutes

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10985: valid_for_minutes

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10985: valid_for_minutes

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10986: valid_for_hours

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10986: valid_for_hours

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10986: valid_for_hours

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10987: valid_until_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10987: valid_until_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10987: valid_until_time

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10988: valid_until_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10988: valid_until_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10988: valid_until_date

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10989: attribute_has_value

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10989: attribute_has_value

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10989: attribute_has_value

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10990: The attribute will be assigned current time value n GMT time zone during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10990: The attribute will be assigned current time value during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10990: The attribute will be assigned current time value during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10991: The attribute will be assigned current date value n GMT time zone during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10991: The attribute will be assigned current date value during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10991: The attribute will be assigned current date value during evaluation

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10992: List of unqualified group names to which user belongs: ["admin", "managers"]

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10992: List of unqualified group names to which user belongs: ["admin", "managers"]

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10992: List of unqualified group names to which user belongs: ["admin", "managers"]

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10993: Current user: unqualified form: system

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10993: Current user: unqualified form: system

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10993: Current user: unqualified form: system

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10994: Unqualified name of the binding resource for the resource on which the query is performed: admin

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10994: Unqualified name of the binding resource for the resource on which the query is performed: admin

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10994: Unqualified name of the binding resource for the resource on which the query is performed: admin

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10995: ResourceType on which the query is performed: LibraryResourceType

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10995: ResourceType on which the query is performed: LibraryResourceType

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10995: ResourceType on which the query is performed: LibraryResourceType

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10996: Resource on which the query is performed: bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10996: Resource on which the query is performed: bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10996: Resource on which the query is performed: bar

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10997: Unqualified name of the action on which the resource is being queried.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10997: Unqualified name of the action on which the resource is being queried.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10997: Unqualified name of the action on which the resource is being queried.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10998: function: urn:oasis:names:tc:xacml:1.0:function:boolean-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side);If LHS or RHS is a multiple value attribute and the other side is single value attribute,the function returns false;If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10998: function: urn:oasis:names:tc:xacml:1.0:function:boolean-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side);If LHS or RHS is a multiple value attribute and the other side is single value attribute,the function returns false;If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10998: function: urn:oasis:names:tc:xacml:1.0:function:boolean-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side);If LHS or RHS is a multiple value attribute and the other side is single value attribute,the function returns false;If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10999: function: urn:oasis:names:tc:xacml:1.0:function:string-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10999: function: urn:oasis:names:tc:xacml:1.0:function:string-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-10999: function: urn:oasis:names:tc:xacml:1.0:function:string-equal The function returns true if the LHS (left-hand side) matches RHS (right-hand side); If LHS or RHS is a multiple value attribute and the other side is single value attribute, the function returns false; If both LHS and RHS are multiple value attribute, they have the same number of elements and for each element from the list on the left, there exists an element from the list on the right, the function returns true.

Cause: built-in attribute/function display name and desription

Action: Prompt message, no action required
Level: 1

Type: NOTIFICATION

Impact: Security

JPS-11000: Policy Set member with type: "{0}" and name "{1}" does not exist

Cause: The policy set member does not exist in policy store

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11001: Can not delete policy set "{0}" which is referred by other policy set

Cause: The policy set to be deleted is referred by other policy set

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11002: Policy set dependency loop could be introduced by modifyPolicySet operation

Cause: The policy set depdency could be introduced by modifyPolicySet operation

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11003: Policy set "{0}" does not exist

Cause: The policy set entry with specified name does not exist in policy store

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11004: Multiple principal entries provided have principal constraint

Cause: Multiple principal entries have principal constraint

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11005: Can not add AllResource to permission set: "{0}"

Cause: Adding AllResource to Permission set is not supported

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11006: Adding {0} combiner parameters for {0} "{1}" not referred in this policy set

Cause: Adding policy or policy set combiner paramers for policy or policy set not referred in this policy set

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11007: Can not add codesource, principals, resource actions or permission sets to {0}: "{1}" which has XACML3 target

Cause: Adding codesource, principals, resource actions or permissin sets to policy, policy set or rule which has XACML3 target

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11008: Can not add XACML3 target to {0}: "{1}" which has codesource, principals, resource actions or permission sets

Cause: Adding XACML3 target to policy, policy set or rule which has codesource, principals, resource actions or permissin sets

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-11009: Policy set "{0}" already exists

Cause: The policy set entry with specified name already exists in the policy store

Action: Refer to the log files for details.
Level: 1

Type: ERROR

Impact: Security

JPS-12000: No such Configuration Profile "{0}" exists in the system.

Cause: The specified configuration profile is not registered with configuration service.

Action: Check the name, or try listing the registered profiles.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12001: Cannot create ContextConfiguration, A JPS Context with name "{0}" already exists in the system.

Cause: A jpsContext with the specified contextId exists in the system.

Action: Use another unique contextId.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12002: Could not Construct the ConfigurationManagementService: Configuration Context Descriptor NOT FOUND in jps-config.xml or specifies an invalid Configuration serviceInstance descriptor.

Cause: A jpsContext by the name "ConfigContext" that references a Configuration Service Instance Descriptor is missing from jps-config.xml.

Action: Check the MultiTenancy Enablement steps and/or scripts.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12003: Could not Construct ConfigurationManagementService from its Descriptor in jps-config.xml, due to empty/missing configuration data in the Descriptor.

Cause: The configuration jpsContext does seem to contain a <serviceInstanceRef> pointing to the ConfigurationManagementService instance descriptor.

Action: Check the MultiTenancy Enablement steps and/or scripts.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12004: No such JpsContext "{0}" exists in jps-config.xml.

Cause: A jpsContext with the specified contextId does not exists in the system.

Action: Check jps-config.xml of the domain.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12005: A ContextConfiguration with "{0}" "{1}" already exists in the system.

Cause: A ContextConfiguration with the specified name already exists.

Action: Use another unique name.
Level: 1

Type: ERROR

Impact: Data

JPS-12006: No Registered ContextConfiguration with "{0}" "{1}" exists in the system.

Cause: The specified configuration profile is not registered with configuration service.

Action: Check the name, or try listing the registered profiles.
Level: 1

Type: ERROR

Impact: Data

JPS-12007: Cannot delete ContextConfiguration "{0}" in "{1}" state.

Cause: A ContextConfiguration in ACTIVE state cannot be deleted.

Action: DeActivate the context and then try deleting it.
Level: 1

Type: ERROR

Impact: Data

JPS-12008: Cannot DeActivate ContextConfiguration "{0}" as it is in state "{1}".

Cause: A ContextConfiguration ACTIVE state (only) can be DeActivated. DeActivation from other states is illegal.

Action: Make sure the context configuration is ACTIVE and then try deactivating it.
Level: 1

Type: ERROR

Impact: Data

JPS-12009: Cannot Activate ContextConfiguration "{0}" as it is in state "{1}".

Cause: A ContextConfiguration must be in COMPLETE or INACTIVE state for Activation to succeed.

Action: Check to make sure the state of the Context is COMPLETE or INACTIVE.
Level: 1

Type: ERROR

Impact: Data

JPS-12010: Cannot Update ContextConfiguration "{0}" as it is in state "{1}".

Cause: A ContextConfiguration must be in CREATED or INACTIVE state before it can be UPDATED.

Action: Check to make sure the state of the Context is CREATED or INACTIVE. A configuration in COMPLETE or ACTIVE states cannot be updated
Level: 1

Type: ERROR

Impact: Data

JPS-12011: OPSS Runtime Cannot fetch Configuration for context "{0}", The context does not exist or is not in ACTIVE state.

Cause: OPSS Runtime failed to fetch the Configuration for the context. Either the context does not exist or is not in ACTIVE state. The Runtime can only view ContextConfigurations in ACTIVE state

Action: Check to make sure the Context exists and is in ACTIVE state.
Level: 1

Type: ERROR

Impact: Data

JPS-12012: Cannot initialize Configuration Store : One of DataSource/JDBC-URL/FilePath for MetaDataStore should be Configured in the Configuration Service Descriptor.

Cause: The configuration serviceInstance descriptor does not seem to contain a property for DataSource/JDBC-URL/FilePath for connecting to the Configuration Store.

Action: Check MultiTenancy enablement steps/scripts.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12013: File based Configuration Store should be used only for Development and not in Production.

Cause: File based Configuration Store should be used only for Testing and not in Production.

Action: Nothing to do if this is a Test Environment, else check Multi-Tenancy enablement steps.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12014: Map/Key name(s) for Credential required to bind to MetaDataStore with JDBC-URL not configured in the Configuration Service.

Cause: A Password Credential is required when JDBC-URL is used to connect to the Configuration Store.

Action: Check to see that the Configuration serviceInstance descriptor contains properties for the Map and Key name of the credential.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12015: Property JPS_CONFIG_PATH not set for use by PersistenceManager.

Cause: Internal Error/Bug: The Configuration Management Service is expected to set a property JPS.CONFIGSERVICE.PATH for use by the PersistenceManager.

Action: Report Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Process

JPS-12016: Internal Error: Unable to locate ContextConfiguration named "{0}" in the Configuration Profile "{1}".

Cause: Internal Error/Bug: The Configuration Service is in a state where it thinks the specified contextId should exist under the specified profileId, but the persisted information in the store does not match the expectation.

Action: Report Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Process

JPS-12017: Invalid Customization expression , specified XPath "{0}" does not evaluate to a "{1}".

Cause: The XPath expression specified in Customization spec does not point to the intended element in the Configuration Profile document.

Action: Check the XPath expression against the structure of the configuration Profile being referenced..
Level: 1

Type: ERROR

Impact: Data

JPS-12018: Invalid Location Override Customization in Global Scope. Location Customization can be specified for ServiceInstances only.

Cause: The Location Override in Customization spec is only applicable to a serviceInstance attribute and cannot be applied to an element in Global Scope.

Action: Check the XPath expression.
Level: 1

Type: ERROR

Impact: Data

JPS-12019: Cannot apply "{0}" overrides on element of type "{1}", expected an element of type "{2}", check the Element XPath specified in the customization.

Cause: The XPath expression specified in Customization spec does not point to the intended element in the Configuration Profile document.

Action: Check the XPath expression against the structure of the configuration Profile being referenced..
Level: 1

Type: ERROR

Impact: Data

JPS-12020: Cannot modify values of existing ExtendedProperty elements during customization.

Cause: Cannot modify values of existing ExtendedProperty elements during customization.

Action: This is an Unsupported Customization spec, change the customization instructions supplied to the Configuration Management Service.
Level: 1

Type: WARNING

Impact: Data

JPS-12021: Cannot create ContextConfiguration "{0}", No such profile "{1}" exists in the system.

Cause: Cannot create ContextConfiguration as the referenced Configuration Profile does not seem to exist.

Action: Check the name of the specified profile.
Level: 1

Type: ERROR

Impact: Data

JPS-12022: MetaDataObject "{0}" not found. Ensure ContextConfiguration "{1}" exists or first create it.

Cause: The PersistenceManager is unable to find the MetaDataObject corresponding to the specified contextId.

Action: Check the name of the context or make sure it is registered with the Configuration Service.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12023: Mutable MetadataObject "{0}" cannot be obtained from MetadataStore specified since there are pending writes to other MetadataStores. Do flushChanges/cancelChanges on MDSSession to proceed.

Cause: Internal Error/Bug : The persistence manager is in a state where it is trying to perform multiple updates to the profile document concurrently.

Action: Report a Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Process

JPS-12024: A profile with name "{0}" already exists.

Cause: A configuration profile with the given name already exists.

Action: Try using a unique profileId.
Level: 1

Type: ERROR

Impact: Data

JPS-12025: Cannot Delete Profile "{0}" ,Named ContextConfigurations exist under the profile.

Cause: A configuration profile which has named ContextConfiguration's referencing it cannot be deleted.

Action: Try deleting the ContextConfiguration's before attempting to delete the profile.
Level: 1

Type: ERROR

Impact: Data

JPS-12026: No such ContextConfiguration "{0}" exists in the system.

Cause: The specified ContextConfiguration is not registered with the Configuration Service.

Action: Check the name or try listing the registered ContextConfigurations.
Level: 1

Type: ERROR

Impact: Data

JPS-12027: Required PasswordCredential at Map = "{0}",Key = "{1}" was not found in Specified Bootstrap CredentialStore.

Cause: A required PasswordCredential does not exist at the specified map, and key in the supplied bootstrap credential store.

Action: Check the bootstrap credential store.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12028: Malformed jps-config.xml : stale service instance reference "{0}" from JpsContext.

Cause: The PersistenceManager found a STALE <serviceInstanceRef> that does not exist in the jps-config.xml.

Action: Check the jps-config.xml of the Profile or the Out-of-the-Box jps-config.xml as appropriate.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12029: Cannot set Name for ContextConfiguration "{0}" in state "{1}", deactivate it first.

Cause: Cannot set contextName for a ContextConfiguration in ACTIVE.

Action: DeActivate it first and then set a Name for it.
Level: 1

Type: ERROR

Impact: Data

JPS-12030: Cannot setContextName, ConfigurationContext "{0}" is already Named "{1}", unset the Name first.

Cause: A ContextConfiguration that is already has a Name cannot be Named again.

Action: Unset the current Name first and then set a new Name for it.
Level: 1

Type: ERROR

Impact: Data

JPS-12031: Cannot unset Name for ContextConfiguration "{0}" in state "{1}", deactivate it first.

Cause: Cannot unset the contextName for a ContextConfiguration in ACTIVE state.

Action: DeActivate the Context first and then unset the contextName.
Level: 1

Type: ERROR

Impact: Data

JPS-12032: Error in initializing JAXBContext.

Cause: Internal Error: JAXB context initialization in PersistenceManager Failed.

Action: Report a Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12033: Invalid profile jps-config.xml document, does not contain a required element "{0}".

Cause: Internal Error: the profile document does not contain a mandatory element.

Action: Check the jps-config.xml that was used as a Configuration Profile.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12034: MDSPersistenceManager Cannot handle Persistence of Element "{0}".

Cause: Unsupported operation : The persistence manager configured with the Configuration Service does not handle persistence of the specified element.

Action: Report a Bug on Oracle OPSS with relevant logs.
Level: 1

Type: ERROR

Impact: Configuration

JPS-12035: Cannot setContextName for ConfigurationContext "{0}" to Name "{1}", as the Name is already assigned to "{2}".

Cause: Names used for ContextConfiguration must be unique, an attempt is being made to set the same Name for more than one ContextConfiguration.

Action: Use a different unique Name.
Level: 1

Type: ERROR

Impact: Data

JPS-12036: ContextConfiguration "{0}" does not have any name set for it, Naming a ContextConfiguration is mandatory before its configuration STATE can be set to COMPLETE.

Cause: An attempt is being made to set the STATE of an Un-Named ContextConfiguraton to COMPLETE.

Action: Use the setContextName(contextId) method to set a Name.
Level: 1

Type: ERROR

Impact: Data

JPS-12037: Service configuration update done for Configurator.

Cause: Service configuration update done for Configurator.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

JPS-12038: Failed to check if audit is enabled.

Cause: Configuration management events logging was not enabled.

Action: Check the audit configuration to ensure auditing enabled.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12039: Failed to log audit record.

Cause: Configuration management audit event logging failed.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12100: The expiry time should be in format {0}

Cause: Invalid input

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12101: The filter value is {0} invalid

Cause: Invalid input

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12102: One of the attributes {0} is undefined

Cause: Invalid input

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12103: Parameter {0} is missing

Cause: Missing Parameter

Action: Correct the input.
Level: 1

Type: WARNING

Impact: Configuration

JPS-12104: Alias {0} did not exist or point to a key

Cause: Alias did not exist or point to a key

Action: Correct the input Alias.
Level: 1

Type: WARNING

Impact: Configuration

JPS-20000: GlobalPolicy can not be created by MAPI methods

Cause: GlobalPolicy can not be created by MAPI methods.

Action: Set up policy store using reassociation or upgrading
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20000: GlobalPolicy can not be created by MAPI methods

Cause: GlobalPolicy can not be created by MAPI methods.

Action: Set up policy store using reassociation or upgrading
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20000: GlobalPolicy can not be created by MAPI methods

Cause: GlobalPolicy can not be created by MAPI methods.

Action: Set up policy store using reassociation or upgrading
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20001: GlobalPolicy can not be deleted by MAPI methods.

Cause: GlobalPolicy can not be deleted by MAPI methods.

Action: GlobalPolicy is a built-in stripe, can not be deleted
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20001: GlobalPolicy can not be deleted by MAPI methods.

Cause: GlobalPolicy can not be deleted by MAPI methods.

Action: GlobalPolicy is a built-in stripe, can not be deleted
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20001: GlobalPolicy can not be deleted by MAPI methods.

Cause: GlobalPolicy can not be deleted by MAPI methods.

Action: GlobalPolicy is a built-in stripe, can not be deleted
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20002: GlobalPolicy can not be returned from the method.

Cause: GlobalPolicy can not be returned from the method.

Action: Gets GlobalPolicy from the method getGlobalPolicy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20002: GlobalPolicy can not be returned from the method.

Cause: GlobalPolicy can not be returned from the method.

Action: Gets GlobalPolicy from the method getGlobalPolicy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20002: GlobalPolicy can not be returned from the method.

Cause: GlobalPolicy can not be returned from the method.

Action: Gets GlobalPolicy from the method getGlobalPolicy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20003: Cannot add global role to application role

Cause: Attempted to add a global role {0} to members of an application role or grant a global role {0} to an applicaton role

Action: Do not add a global role to members of an application role and do not grant a global role to an application role.
Level: 1

Type: WARNING

Impact: Security

JPS-20004: Principals can not contain global role.

Cause: Principals contain global role {0}

Action: Remove global role from principals.
Level: 1

Type: WARNING

Impact: Security

JPS-20005: Cannot delete global role "{0}".

Cause: Global role "{0}" is referenced in a Policy defined in an Application.

Action: Make sure the global role is not referenced in any application policy,then remove it.
Level: 1

Type: WARNING

Impact: Security

JPS-20006: Authorization policy is not supported in global policy.

Cause: Authorization policy is not supported in global policy.

Action: Do not create authorization policies in global policy.
Level: 1

Type: WARNING

Impact: Security

JPS-20007: Permission grant is not supported in global policy

Cause: Permission grant is not supported in global policy.

Action: Do not grant permissions in global policy
Level: 1

Type: WARNING

Impact: Security

JPS-20008: {0} : {1} in global policy which are referenced in application have been changed but not distributed

Cause: {0} : {1} in global policy which are referenced in application have been changed but not distributed.

Action: Distribute global policy firstly
Level: 1

Type: WARNING

Impact: Security

JPS-20010: Attribute name {0} already exist in {1}.

Cause: Attribute name {0} already exist in {1}

Action: Choose another name
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20011: Function name {0} already exist in {1}.

Cause: Function name {0} already exist in {1}

Action: Choose another name
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20012: Global attribute {0} is used in application {1}.

Cause: Global attribute {0} is used in application policy {1}

Action: Make sure the global attribute is not used in any applications including global policy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20013: Global function {0} is used in application {1}.

Cause: Global function {0} is used in application policy {1}

Action: Make sure the global function is not used in any applications including global policy
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20014: Policy domain is not supported in global policy

Cause: Policy domain is not supported in global policy.

Action: Do not use policy domain in global policy
Level: 1

Type: WARNING

Impact: Security

JPS-20020: Resource type name {0} already exists in application {1}.

Cause: Resource type name {0} already exists in application {1}

Action: Choose another name
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20021: Global resource type {0} is used in application {1}.

Cause: Resource type {0} is used in application {1}

Action: Make sure global resource type is not used in any application
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20022: Global policy can not be unbound from SM

Cause: Global policy can not be unbound from SM

Action: Do not unbind global policy from SM
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20050: Combining algorithm {0} not found.

Cause: Combining algorithm not found.

Action: Make sure the used combining algorithm exists.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20050: Combining algorithm {0} not found.

Cause: Combining algorithm not found.

Action: Make sure the used combining algorithm exists.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20050: Combining algorithm {0} not found.

Cause: Combining algorithm not found.

Action: Make sure the used combining algorithm exists.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20051: Exception in converting execution frequency {0}, message is {1}

Cause: Exception in converting value of algorithm execution frequency.

Action: Make sure the execution frequency is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20051: Exception in converting execution frequency {0}, message is {1}

Cause: Exception in converting value of algorithm execution frequency.

Action: Make sure the execution frequency is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20051: Exception in converting execution frequency {0}, message is {1}

Cause: Exception in converting value of algorithm execution frequency.

Action: Make sure the execution frequency is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20052: Exception in converting algorithm usage {0}, message is {1}

Cause: Exception in converting value of algorithm usage.

Action: Make sure the usage is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20052: Exception in converting algorithm usage {0}, message is {1}

Cause: Exception in converting value of algorithm usage.

Action: Make sure the usage is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20052: Exception in converting algorithm usage {0}, message is {1}

Cause: Exception in converting value of algorithm usage.

Action: Make sure the usage is valid.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20053: A combining algorithm must be provided if policy is using more than one rule.

Cause: Policy uses multiple rules, but no combining algorithm provided.

Action: Provide a combining algorithm.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20053: A combining algorithm must be provided if policy is using more than one rule.

Cause: Policy uses multiple rules, but no combining algorithm provided.

Action: Provide a combining algorithm.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20053: A combining algorithm must be provided if policy is using more than one rule.

Cause: Policy uses multiple rules, but no combining algorithm provided.

Action: Provide a combining algorithm.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20054: A acl match type must be provided if policy is a RAS one.

Cause: RAS policy has no acl match type to be provided.

Action: Provide a ACL Match Type.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20055: A list of RAS policy rule must be provided if policy is a RAS one.

Cause: RAS policy has no policy rule to be provided.

Action: Provide policy rule(s).
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20056: A list of RAS resource must be provided if policy is a RAS one.

Cause: RAS policy has no resource to be provided.

Action: Provide resource(s).
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20060: Number of input parameters to the function and provided value types for them are not of same size.

Cause: Number of input parameters to the function and provided value types for them are not of same size.

Action: Parameter value types, if provided, must be provided for all input parameters
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20060: Number of input parameters to the function and provided value types for them are not of same size.

Cause: Number of input parameters to the function and provided value types for them are not of same size.

Action: Parameter value types, if provided, must be provided for all input parameters
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20060: Number of input parameters to the function and provided value types for them are not of same size.

Cause: Number of input parameters to the function and provided value types for them are not of same size.

Action: Parameter value types, if provided, must be provided for all input parameters
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20061: Value collection added to expression is null.

Cause: Value collection added to expression is null.

Action: Provide a non-nulll collection of values to expression.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20061: Value collection added to expression is null.

Cause: Value collection added to expression is null.

Action: Provide a non-nulll collection of values to expression.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20061: Value collection added to expression is null.

Cause: Value collection added to expression is null.

Action: Provide a non-nulll collection of values to expression.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20062: Value collection passed to input parameter when a single object is expected.

Cause: Value collection passed to input parameter when a single object is expected.

Action: Provide a single object as input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20062: Value collection passed to input parameter when a single object is expected.

Cause: Value collection passed to input parameter when a single object is expected.

Action: Provide a single object as input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20062: Value collection passed to input parameter when a single object is expected.

Cause: Value collection passed to input parameter when a single object is expected.

Action: Provide a single object as input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20063: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Cause: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Action: Provide correct type of collection as function input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20063: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Cause: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Action: Provide correct type of collection as function input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20063: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Cause: Wrong type of collection passed as input parameter; expected type is {0}, provided {1}.

Action: Provide correct type of collection as function input parameter.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20064: Function {0} is unknown.

Cause: Function {0} is unknown.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20064: Function {0} is unknown.

Cause: Function {0} is unknown.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20064: Function {0} is unknown.

Cause: Function {0} is unknown.

Action: Provide correct function.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20070: In mixed mode, PDP configuration id could not be null

Cause: PDP configuration id is missing.

Action: Specify the PDP configuration id
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20070: In mixed mode, PDP configuration id could not be null

Cause: PDP configuration id is missing.

Action: Specify the PDP configuration id
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20070: In mixed mode, PDP configuration id could not be null

Cause: PDP configuration id is missing.

Action: Specify the PDP configuration id
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20100: Rules {0} for policy {1} is in use by other policies. It will not be deleted.

Cause: Rule {0} of policy {1} is shared by other policies.

Action: Provide correct Rule.
Level: 1

Type: ERROR

Impact: Security

JPS-20101: Policy {0} is referred by one or more policy sets. It can not be deleted if cascading is set to false.

Cause: Policy {0} is referred by other policie sets.

Action: Either use cascading delete or remove references from policy sets.
Level: 1

Type: ERROR

Impact: Security

JPS-20102: Rule {0} used in policy is not sharable. The policy will not be created or updated.

Cause: Rule {0} used in policy is not sharable.

Action: Provide correct Rule.
Level: 1

Type: ERROR

Impact: Security

JPS-20103: Policy can not have both private rules and sharable rules.

Cause: Policy can not have both private rules and sharable rules.

Action: Provide correct Rule.
Level: 1

Type: ERROR

Impact: Security

JPS-20104: Exclusive rule {0} can not be deleted explicitly.

Cause: Exclusive rule {0} can not be deleted explicitly.

Action: Delete the referred policy.
Level: 1

Type: ERROR

Impact: Security

JPS-20105: The permission {0} has no target name.

Cause: Permission has no target name.

Action: Make sure the usage is valid.If not revoke the permission.
Level: 1

Type: WARNING

Impact: Programmatic

JPS-20200: Adding attributes to data security resource type {0} is not allowed.

Cause: Attributes present in Data Security Resource Type.

Action: Remove Attributes present in Data Security Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-20201: Adding matcher class to data security resource type {0} is not allowed.

Cause: Matcher Class present in Data Security Resource Type.

Action: Remove Matcher Class present in Data Security Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-20202: Hierarchical data security resource type {0} is not allowed.

Cause: Data Security Resource Type is Hierarchial.

Action: Change Data Security Resource Type to Flat. It cannot be Hierarchial.
Level: 1

Type: WARNING

Impact: Security

JPS-20203: Adding both actions and action collection references to data security resource type {0} is not allowed.

Cause: Both Actions and Action Collection References are added to Data Security Resource Type.

Action: Add either Actions or Action Collection References to Data Security Resource Type.
Level: 1

Type: WARNING

Impact: Security

JPS-20204: Adding null data security information object to data security resource type {0} is not allowed.

Cause: Null data security information object found for data security resource type.

Action: Add data security information object to data security resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20205: Data source name is required for a data security resource type {0}.

Cause: Data security information object found for data security resource type has no data source name.

Action: Provide valid data source name for data security information object for data security resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20206: Invalid value for data source type of data security resource type {0}.

Cause: Data security information object found for data security resource type has invalid data source type.

Action: Data Security information object found for data security resource type has invalid data source type
Level: 1

Type: WARNING

Impact: Security

JPS-20207: Constraint required for data security resource type {0} as data source type is virtual.

Cause: Virtual data source type requires data source constraint to be present.

Action: Provide valid data source constraint for virtual data source.
Level: 1

Type: WARNING

Impact: Security

JPS-20208: Actions List cannot contain actions that are inherited by default for resource type {0}.

Cause: Actions list in resource type contains default inherited data security actions.

Action: Remove default data security actions from data security resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20209: Duplicate column definition (same column names) not allowed in data source of resource type {0}.

Cause: Duplicate column definition (same names) in secured data source in resource type.

Action: Remove duplicate column definition from secured data source.
Level: 1

Type: WARNING

Impact: Security

JPS-20210: Action collection reference name {1} referred in resource type {0} not found in policy store.

Cause: Action collection reference in resource type not found in the policy store.

Action: Either create action collection in store or remove the reference from resource type.
Level: 1

Type: WARNING

Impact: Security

JPS-20220: Data Security Resource Type should be present for Data Security Resource {0}.

Cause: No RAS resource type present for RAS resource OR is not of type RAS resource type.

Action: Add RAS resource type for RAS resource.
Level: 1

Type: WARNING

Impact: Security

JPS-20221: For data security resource {0} SQL predicate or XML expression is required.

Cause: Both SQL predicate and XML expression missing in data security resource.

Action: Add either SQL Predicate or XML expression to data security resource.
Level: 1

Type: WARNING

Impact: Security

JPS-20240: Multiple rules not allowed for triton policy {0}.

Cause: Multiple rules in triton data security policy.

Action: Add only one rule to triton data security policy.
Level: 1

Type: WARNING

Impact: Security

JPS-20241: Data security policy {0} has invalid type {1} and category {2}.

Cause: Invalid policy category and type combination.

Action: Provide valid policy category and type combination.
Level: 1

Type: WARNING

Impact: Security

JPS-20242: RAS policy only takes resources with same resource type.

Cause: RAS Policy have resources with different resource types.

Action: Provide resources just with same resource type for RAS policy.
Level: 1

Type: WARNING

Impact: Security

JPS-20243: For RASParameterValue, only EXACT matcher is supported.

Cause: Search RAS Policy by RASParameterValue ONLY support MATCHER.EXACT.

Action: Use MATCHER.EXACT for search by RASParameterValue.
Level: 1

Type: WARNING

Impact: Security

JPS-20244: For RASParameterValue, only EQUALITY comparator is supported.

Cause: Search RAS Policy by RASParameterValue ONLY support COMPARATOR.EQUALITY.

Action: Use COMPARATOR.EQUALITY for search by RASParameterValue.
Level: 1

Type: WARNING

Impact: Security

JPS-20260: RAS Resource type name referred in RAS policy set {0} is Null.

Cause: RAS resource type reference in RAS policy set is Null.

Action: Either create given resource type in store beforehand or use an existing one.
Level: 1

Type: WARNING

Impact: Security

JPS-20261: Data security policy set {0} has invalid type {1} and category {2}.

Cause: Invalid policy set category and type combination.

Action: Provide valid policy set category and type combination.
Level: 1

Type: WARNING

Impact: Security

JPS-20262: Policy set {0} is an ACL protecting an Attribute Collection and cannot be deleted.

Cause: Attempt to delete ACL that is protecting an Attribute Collection.

Action: Check that the ACL is not protecting any Attribute Collection.
Level: 1

Type: WARNING

Impact: Security

JPS-20263: RAS Policy set only takes policies whose ras resources are of same ras resource type.

Cause: RAS policy set only takes policies whose ras resources are of same ras resource type.

Action: Use ras policies with same ras resource type for ras policy set.
Level: 1

Type: WARNING

Impact: Security

JPS-20264: The length of RAS {0} name plus the length of RAS application name can not exceed 29.

Cause: The length of RAS artifact name plus the length of ras application name exceeds 29.

Action: Shorten the RAS artifact name
Level: 1

Type: WARNING

Impact: Security

JPS-20265: The name of RAS {0} is allowed to consist of only alphanumeric characters and the special characters $, _, and #, and MUST begin with a letter.

Cause: The RAS artifact name is allowed to consist of only alphanumeric characters and the special characters $, _, and #, and MUST begin with a letter.

Action: Change the RAS artifact name
Level: 1

Type: WARNING

Impact: Security

JPS-20300: The action or implied action "{0}" already exists in action collection "{1}" or its parent(s).

Cause: Duplicate action or implied action found in action collection or one of its parents.

Action: Verify the action and implied action lists of this action collection and its parents.
Level: 1

Type: WARNING

Impact: Security

JPS-20301: The action collection "{0}" is already referenced in action collection "{1}" or its parent(s).

Cause: Duplicate action collection reference found in action collection or one of its parents.

Action: Verify the action collection reference lists of this action collection and its parents.
Level: 1

Type: WARNING

Impact: Security

JPS-20302: The action collection "{0}" already exists in application policy "{1}".

Cause: Action collection already exists in the application.

Action: Verify the action collection in the application or try modify operation.
Level: 1

Type: WARNING

Impact: Security

JPS-20303: The action collection "{0}" was not found in application policy "{1}".

Cause: Action collection not found in application.

Action: Verify the action collection is present in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20304: The action collection "{0}" is in use by another policy object.

Cause: Action collection is in use by another policy object.

Action: Verify the usages of the action collection.
Level: 1

Type: WARNING

Impact: Security

JPS-20305: Create, modify & delete operations are not permitted on built-in action collection "{0}".

Cause: The action collection being deleted, created or modified is built-in in the database.

Action: Use a different name for the action collection.
Level: 1

Type: WARNING

Impact: Security

JPS-20306: Action {0} referred in implied action {1} is not defined in action collection {2} or any of its parents.

Cause: The mapping specified for given implied action is not found in action collection or its parents.

Action: Check the implied actions mappings.
Level: 1

Type: WARNING

Impact: Security

JPS-20307: The action or implied action "{0}" already exists in implied action "{1}".

Cause: The mapping specified for given implied action contains duplicate actions.

Action: Check the implied actions mappings.
Level: 1

Type: WARNING

Impact: Security

JPS-20308: The implied action "{0}" refers to itself.

Cause: The mapping specified for given implied action contains reference to itself.

Action: Check the implied actions mappings.
Level: 1

Type: WARNING

Impact: Security

JPS-20320: "{0}" is not a RAS target database.

Cause: The SM is not a RAS target database.

Action: make sure the name corresponds to a RAS target database
Level: 1

Type: WARNING

Impact: Security

JPS-20321: "{0}" is not a RAS application.

Cause: The application is not a RAS application.

Action: make sure the name corresponds to a RAS application
Level: 1

Type: WARNING

Impact: Security

JPS-20322: "{0}" is not found or it is not a RAS target database.

Cause: RAS target database not found

Action: make sure the name corresponds to a RAS target database
Level: 1

Type: WARNING

Impact: Security

JPS-20350: All of handlerSchemaName, handlerPackageName and handlerFunctionName must be present or must be null in an attribute collection.

Cause: Atleast one of schema name, package name or function name of handler function is null.

Action: Verify the schema name, package name and function name of handler function.
Level: 1

Type: WARNING

Impact: Security

JPS-20351: The attribute "{0}" already exists in attribute collection "{1}".

Cause: Duplicate attribute found in attribute collection.

Action: Verify the attribute list of this attribute collection and its parents.
Level: 1

Type: WARNING

Impact: Security

JPS-20352: Attributes in attribute collection must be of category DYNAMIC.

Cause: Category of added attribute was wrong.

Action: Verify the added attribute is of category DYNAMIC.
Level: 1

Type: WARNING

Impact: Security

JPS-20353: The attribute collection "{0}" already exists in application policy "{1}".

Cause: Attribute collection already exists in the application.

Action: Verify the attribute collection in the application or try modify operation.
Level: 1

Type: WARNING

Impact: Security

JPS-20354: The attribute collection "{0}" was not found in application policy "{1}".

Cause: Attribute collection not found in application.

Action: Verify the attribute collection is present in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20355: Attributes in attribute collection must be single-valued.

Cause: Multi-valued attributes not supported.

Action: Verify the added attribute(s) are all single-valued.
Level: 1

Type: WARNING

Impact: Security

JPS-20356: The ACE(Policy Rule) "{0}" is not present in the application.

Cause: ACE(policy rule) protecting Attribute collection not found in application.

Action: Verify the ACE(Policy Rule) is present in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20357: The attributes in an attribute collection "{0}" is null or empty.

Cause: RASAttribute list is null or empty

Action: Make sure RASAttribute list is not null or empty.
Level: 1

Type: WARNING

Impact: Security

JPS-20400: The definition for attribute "{0}" exists in the application policy with wrong category. Expected: {1}, Found: {2}

Cause: Attribute definition exists in application with different category than expected.

Action: Verify the attribute definition in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20401: The definition for attribute "{0}" exists in the application policy with wrong type. Expected: {1}, Found: {2}

Cause: Attribute definition exists in application with different type than expected.

Action: Verify the attribute definition in the application.
Level: 1

Type: WARNING

Impact: Security

JPS-20403: Attribute designator functionality is not supported for this schema version.

Cause: Attribute designator functionality is not supported for this schema version.

Action: Don't use designator functionality or upgrade to newer version.
Level: 1

Type: ERROR

Impact: Security

JPS-20411: Invalid match function. Match function for a constraint must take two input parameters, provided function requires {0} input parameters.

Cause: Match function for constraint does not take 2 input parameters.

Action: Provide a corret match function for constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20412: Invalid match function. Both input parameters to a match function must be of same data type; provided function takes input parameters of type {0} and {1}.

Cause: Match function for constraint musts take two input parameters of same data type.

Action: Provide a correct match function for constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20413: Invalid match function. First parameter for a match function must be a single value.

Cause: Match function for a constraint cannot take bag or set of values.

Action: Provide a correct match function for constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20414: Mismatch of attribute category in constraint. Expected {0}, actual {1}.

Cause: Category of attribute provided to the constraint must either be dynamic or match the constraint type.

Action: Provide attribute with correct category type to the constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20415: The data type {0} of attribute "{1}" does not match data type {2} of function second parameter passed to AttributeValueAssertion.

Cause: Attribute data type and expected function parameter data type are different.

Action: Verify the data type of attribute entry passed to AttributeValueAssertion.
Level: 1

Type: WARNING

Impact: Security

JPS-20416: Data type of value and expected input parameter type of function provided for attribute value assertion does not match. Expected type {0}, provided {1}

Cause: Data type of value and expected input parameter type of function provided for attribute value assertion does not match.

Action: Provide value with correct data type to the constraint.
Level: 1

Type: WARNING

Impact: Security

JPS-20417: Constraints are only supported for TargetEntry and SimpleTargetEntry

Cause: Constraints are supported only for TargetEntry and SimpleTargetEntry.

Action: If a constraint must be used, add it using a TargetEntry or SimpleTargetEntry.
Level: 1

Type: WARNING

Impact: Security

JPS-20420: Function Element is not supported as return type of a function.

Cause: Function Element is not supported as return type of a function.

Action: Provide some other return type.
Level: 1

Type: WARNING

Impact: Security

JPS-20421: Data type for a Function Element input parameter must be OpssString.

Cause: Data type for a Function Element input parameter must be OpssString.

Action: Provide correct data type.
Level: 1

Type: WARNING

Impact: Security

JPS-20422: Function Element not supported for this version of policystore.

Cause: Function element not supported for this schema version.

Action: Don't use function element or upgrade.
Level: 1

Type: WARNING

Impact: Security

JPS-20423: AttributeAssignment can not be defined using a Function Element.

Cause: Attribute assignment cannot be defined using a function element.

Action: Don't use function element.
Level: 1

Type: WARNING

Impact: Security

JPS-20500: Quoted name for {0}, must be terminated by double-quote (").

Cause: Quoted id for triton entity needs to be terminated with double-quote(").

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20501: Length of {0} name must be between 1 and 30 characters (excluding the quotes ("), in case of quoted identifier), but was {1}

Cause: Id for triton entity has invalid length.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20502: Quoted name for {0} contains invalid character ''{1}'' at position {2}. Quoted names must not contain null character(\0) or double-quote(") within the name

Cause: Quoted id for triton entity has invalid character.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20503: Unquoted name for {0} contains invalid character ''{1}'' at position {2}. Unquoted names must begin with an alphabet. They may contain a letter, digit, underscore(_), dollar($), hash(#), or dot(.) symbols at other positions.

Cause: Unquoted id for triton entity has invalid character.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20504: The name "{0}" is an implicit object name in the database and cannot be used as a name for {1}.

Cause: Id provided for triton entity is an implicit object name in the database.

Action: Verify the id provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20505: The value "{0}" is of an unsupported type.

Cause: Parameter value is using an invalid type.

Action: Verify the parameter value provided.
Level: 1

Type: WARNING

Impact: Security

JPS-20521: A simple target must have at least one resource action entry or permission set reference.

Cause: A simple target must have at least one resource action entry or permission set reference.

Action: Provide resource actions or permission sets.
Level: 1

Type: WARNING

Impact: Security

JPS-20600: MetaData-Provisioned is true, but no meta data found in policy object {0}.

Cause: MetaData-Provisioned is true, but no meta data found in policy object {0}.

Action: Check the policy store, make sure it is in an consistent state.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20601: Provided version "{0}" is invalid. Only alphabetic characters, digits, underscores, and dots are allowed.

Cause: Provided version {0} is invalid. Only alphabetic characters, digits, underscores, and dots are allowed.

Action: Provide a valid version.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-20602: Provided meta data {0} is invalid. Reason: {1}

Cause: Provided meta data {0} is invalid. Reason: {1}.

Action: Provide a valid meta data.
Level: 1

Type: ERROR

Impact: Programmatic

JPS-90600: Security Module with the configuration id {0} already exists.

Cause: Security Module with the configuration id {0} already exists.

Action: Provide a unique configuration id.
Level: 1

Type: WARNING

Impact: Security

JPS-90600: Security Module with the configuration id {0} already exists.

Cause: Security Module with the configuration id {0} already exists.

Action: Provide a unique configuration id.
Level: 1

Type: WARNING

Impact: Security

JPS-90600: Security Module with the configuration id {0} already exists.

Cause: Security Module with the configuration id {0} already exists.

Action: Provide a unique configuration id.
Level: 1

Type: WARNING

Impact: Security

JPS-90601: Failed to create Security Module with the configuration id {0}, with error {1}

Cause: Failed to create Security Module with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90601: Failed to create Security Module with the configuration id {0}, with error {1}

Cause: Failed to create Security Module with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90601: Failed to create Security Module with the configuration id {0}, with error {1}

Cause: Failed to create Security Module with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90602: Security Module with the configuration id {0} not found.

Cause: Security Module with the configuration id {0} not found.

Action: Make sure the configuration id is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90602: Security Module with the configuration id {0} not found.

Cause: Security Module with the configuration id {0} not found.

Action: Make sure the configuration id is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90602: Security Module with the configuration id {0} not found.

Cause: Security Module with the configuration id {0} not found.

Action: Make sure the configuration id is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90603: AuditService is improperly configured.

Cause: Audit Service is not initializable.

Action: Configure an audit server for audit trails
Level: 1

Type: WARNING

Impact: Security

JPS-90603: AuditService is improperly configured.

Cause: Audit Service is not initializable.

Action: Configure an audit server for audit trails
Level: 1

Type: WARNING

Impact: Security

JPS-90603: AuditService is improperly configured.

Cause: Audit Service is not initializable.

Action: Configure an audit server for audit trails
Level: 1

Type: WARNING

Impact: Security

JPS-90604: Security Module with the configuration id {0} successfully created.

Cause: Security Module with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90604: Security Module with the configuration id {0} successfully created.

Cause: Security Module with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90604: Security Module with the configuration id {0} successfully created.

Cause: Security Module with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90605: Security Module with the configuration id {0} successfully modified.

Cause: Security Module with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90605: Security Module with the configuration id {0} successfully modified.

Cause: Security Module with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90605: Security Module with the configuration id {0} successfully modified.

Cause: Security Module with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90606: Security Module with the configuration id {0} successfully deleted.

Cause: Security Module with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90606: Security Module with the configuration id {0} successfully deleted.

Cause: Security Module with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90606: Security Module with the configuration id {0} successfully deleted.

Cause: Security Module with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90607: Security Module with the configuration id {0} successfully retrieved.

Cause: Security Module with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90607: Security Module with the configuration id {0} successfully retrieved.

Cause: Security Module with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90607: Security Module with the configuration id {0} successfully retrieved.

Cause: Security Module with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90608: Failed to modify Security Module with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90608: Failed to modify Security Module with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90608: Failed to modify Security Module with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90620: PIP with the configuration id {0} already exists.

Cause: PIP with the configuration id/name {0} already exists.

Action: Provide a unique configuration id/name.
Level: 1

Type: WARNING

Impact: Security

JPS-90620: PIP with the configuration id {0} already exists.

Cause: PIP with the configuration id/name {0} already exists.

Action: Provide a unique configuration id/name.
Level: 1

Type: WARNING

Impact: Security

JPS-90620: PIP with the configuration id {0} already exists.

Cause: PIP with the configuration id/name {0} already exists.

Action: Provide a unique configuration id/name.
Level: 1

Type: WARNING

Impact: Security

JPS-90621: Failed to create PIP with the configuration id {0}, with error {1}

Cause: Failed to create PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90621: Failed to create PIP with the configuration id {0}, with error {1}

Cause: Failed to create PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90621: Failed to create PIP with the configuration id {0}, with error {1}

Cause: Failed to create PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90622: PIP with the configuration id {0} not found.

Cause: PIP with the configuration id/name {0} not found.

Action: Make sure the configuration id/name is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90622: PIP with the configuration id {0} not found.

Cause: PIP with the configuration id/name {0} not found.

Action: Make sure the configuration id/name is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90622: PIP with the configuration id {0} not found.

Cause: PIP with the configuration id/name {0} not found.

Action: Make sure the configuration id/name is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90623: PIP with the configuration id {0} successfully created.

Cause: PIP with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90623: PIP with the configuration id {0} successfully created.

Cause: PIP with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90623: PIP with the configuration id {0} successfully created.

Cause: PIP with the configuration id {0} successfully created.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90624: PIP with the configuration id {0} successfully modified.

Cause: PIP with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90624: PIP with the configuration id {0} successfully modified.

Cause: PIP with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90624: PIP with the configuration id {0} successfully modified.

Cause: PIP with the configuration id {0} successfully modified.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90625: PIP with the configuration id {0} successfully deleted.

Cause: PIP with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90625: PIP with the configuration id {0} successfully deleted.

Cause: PIP with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90625: PIP with the configuration id {0} successfully deleted.

Cause: PIP with the configuration id {0} successfully deleted.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90626: PIP with the configuration id {0} successfully retrieved.

Cause: PIP with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90626: PIP with the configuration id {0} successfully retrieved.

Cause: PIP with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90626: PIP with the configuration id {0} successfully retrieved.

Cause: PIP with the configuration id {0} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90627: Failed to modify PIP with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90627: Failed to modify PIP with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90627: Failed to modify PIP with the configuration id {0}, with error {1}

Cause: Failed to modify PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90630: Application Policy with the configuration id {0} not found.

Cause: Application with the id {0} not found.

Action: Make sure the Appplication Policy is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90630: Application Policy with the configuration id {0} not found.

Cause: Application with the id {0} not found.

Action: Make sure the Appplication Policy is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90630: Application Policy with the configuration id {0} not found.

Cause: Application with the id {0} not found.

Action: Make sure the Appplication Policy is valid.
Level: 1

Type: WARNING

Impact: Security

JPS-90631: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90631: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90631: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: SM Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90632: SM with the configuration id {0} to application bindings retrieved.

Cause: SM with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90632: SM with the configuration id {0} to application bindings retrieved.

Cause: SM with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90632: SM with the configuration id {0} to application bindings retrieved.

Cause: SM with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90633: SM with the configuration id {0} and application name {1} successfully unbound.

Cause: SM with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90633: SM with the configuration id {0} and application name {1} successfully unbound.

Cause: SM with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90633: SM with the configuration id {0} and application name {1} successfully unbound.

Cause: SM with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90634: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90634: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90634: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Cause: PIP Binding with the configuration id {0} and application name {1} successfully retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90635: PIP with the configuration id {0} to application bindings retrieved.

Cause: PIP with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90635: PIP with the configuration id {0} to application bindings retrieved.

Cause: PIP with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90635: PIP with the configuration id {0} to application bindings retrieved.

Cause: PIP with the configuration id {0} to application bindings retrieved.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90636: PIP with the configuration id {0} and application name {1} successfully unbound.

Cause: PIP with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90636: PIP with the configuration id {0} and application name {1} successfully unbound.

Cause: PIP with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90636: PIP with the configuration id {0} and application name {1} successfully unbound.

Cause: PIP with the configuration id {0} and application name {1} successfully unbound.

Action: Audit message, no action required
Level: 1

Type: TRACE

Impact: Security

JPS-90637: Failed to create SM binding with the configuration id {0}, with error {1}

Cause: Failed to create SM binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90637: Failed to create SM binding with the configuration id {0}, with error {1}

Cause: Failed to create SM binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90637: Failed to create SM binding with the configuration id {0}, with error {1}

Cause: Failed to create SM binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90638: Failed to create PIP binding with the configuration id {0}, with error {1}

Cause: Failed to create PIP binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90638: Failed to create PIP binding with the configuration id {0}, with error {1}

Cause: Failed to create PIP binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90638: Failed to create PIP binding with the configuration id {0}, with error {1}

Cause: Failed to create PIP binding with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90639: Application {0} already bound to configuration {1}

Cause: Application {0} already bound to configuration {1}

Action: No need to bind again
Level: 1

Type: WARNING

Impact: Security

JPS-90639: Application {0} already bound to configuration {1}

Cause: Application {0} already bound to configuration {1}

Action: No need to bind again
Level: 1

Type: WARNING

Impact: Security

JPS-90639: Application {0} already bound to configuration {1}

Cause: Application {0} already bound to configuration {1}

Action: No need to bind again
Level: 1

Type: WARNING

Impact: Security

JPS-90640: Failed to unbind SM configuration

Cause: Failed to unbind SM with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90640: Failed to unbind SM configuration

Cause: Failed to unbind SM with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90640: Failed to unbind SM configuration

Cause: Failed to unbind SM with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90641: Failed to unbind PIP Configuration

Cause: Failed to unbind PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90641: Failed to unbind PIP Configuration

Cause: Failed to unbind PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90641: Failed to unbind PIP Configuration

Cause: Failed to unbind PIP with the configuration id {0}, with error {1}

Action: Check error message for further details.
Level: 1

Type: WARNING

Impact: Security

JPS-90642: The non-controlled policy distribution mode application {0} can not be bound to SM configuration

Cause: The non-controlled policy distribution mode application can not be bound to SM configuration

Action: Bind controlled policy distribution mode application
Level: 1

Type: ERROR

Impact: Security

JPS-90642: The non-controlled policy distribution mode application {0} can not be bound to SM configuration

Cause: The non-controlled policy distribution mode application can not be bound to SM configuration

Action: Bind controlled policy distribution mode application
Level: 1

Type: ERROR

Impact: Security

JPS-90642: The non-controlled policy distribution mode application {0} can not be bound to SM configuration

Cause: The non-controlled policy distribution mode application can not be bound to SM configuration

Action: Bind controlled policy distribution mode application
Level: 1

Type: ERROR

Impact: Security

30 JRF-10001 to JRF-20036

JRF-10001: Fail to retrieve the application identifier. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the application name.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10002: Fail to retrieve the WebLogic domain adminser server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the admin server name.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10003: Fail to retrieve the current server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the server name based on the current thread.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10004: Fail to check if the current server is admin server. The internal exception is: {0}.

Cause: The MBean server could not be accessed to verify that the server in the current thread is the admin server.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10005: Fail to retrieve the server log path. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the server log path.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10006: Fail to copy the config file from {0} to the server directory {1}. The internal exception is: {2}.

Cause: The server config directory could not be accessed.

Action: Use the applyJRF() wlst command to ensure that the server has been properly configured.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10007: Fail to retrieve the system property domain.home.

Cause: The system property domain.home was not specified during WebLogic server startup.

Action: Specify the system property domain.home when starting the WebLogic server.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10008: I/O exception occurs when aceessing to the JRF template at {0}.

Cause: The specified JRF template was not accessaible.

Action: Verify that the template jar from the template location is present and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10009: I/O exception occurs when parsing config/config.xml from the JRF template at {0}.

Cause: The config.xml might be missing from the JRF template or the JRF template jar might be corrupted.

Action: Verify that the JRF template is properly installed within the Oracle Home.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10010: The file config.xml under domain {0} does not exist.

Cause: The config.xml under domain config was missing or corrupted.

Action: Verify that the domain contains a valid config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10011: Fail to parse the config.xml file from JRF template.

Cause: The domain config.xml might be missing or the JRF template jar might be corrupted.

Action: Verify that the JRF template is properly installed within the Oracle Home and that the domain contains a valid config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10012: Fail to retrieve the property for the Common Components Home.

Cause: The Common Components Home property was not set.

Action: Set the Oracle Home property using the system property common.components.home or the environment variable COMMON_COMPONENTS_HOME.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10013: The specified Oracle Home directory {0} does not exist.

Cause: The Common Components Home directory did not exist.

Action: Verify that Common ComponentsHome, specified through the system property common.components.home or environment variable COMMON_COMPONENTS_HOME, is a valid directory.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10014: Fail to retrieve the current server name. The internal exception is: {0}.

Cause: The MBean server could not be accessed to retrieve the application server platform information.

Action: Verify that the MBean server is running and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10015: The specified application server platform {0} is not supported by JRF.

Cause: JRF does not support the specified platform.

Action: Contact Oracle Support Services for the JRF supported application server platforms.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10016: The initialization of the server config directory from the Oracle Home {0} with domain directory {1} for copying fails. The internal exception is: {2}.

Cause: Could not retrieve the servers from the domain config.xml file.

Action: Verify that the domain contains a valid config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10017: Unable to invoke {0} because the domain {1} has not been extended with JRF template.

Cause: Domain has not been extended with JRF template.

Action: Apply JRF template to the domain.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10018: Server or cluster "{0}" is not found.

Cause: The server or cluster is not found.

Action: Create the server or cluster.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10019: Could not obtain edit lock on the domain

Cause: Domain is being edited by someone else

Action: Wait until the edit lock on the domain is released and retry.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10020: Could not load/instantiate a WebLogic server platform support instance.

Cause: Could not load/instantiate a WebLogic server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10021: Could not load/instantiate a WebSphere server platform support instance.

Cause: Could not load/instantiate a WebSphere server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10022: Could not load system property 'oracle.domain.config.dir'.

Cause: Could not load system property 'oracle.domain.config.dir'.

Action: Verify JRF is installed and provisioned properly and the system property 'oracle.domain.config.dir' is set.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10023: Could not load system property 'oracle.server.config.dir'.

Cause: Could not load system property 'oracle.server.config.dir'.

Action: Verify JRF is installed and provisioned properly and the system property 'oracle.server.config.dir' is set.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10024: JRF is unable to determine the current application server platform.

Cause: JRF is unable to determine the current platform.

Action: Contact Oracle Support Services for the JRF supported application server platforms.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10025: Could not load/instantiate a JBoss server platform support instance.

Cause: Could not load/instantiate a JBoss server platform support instance.

Action: Check if the server platform support class can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10026: Failed to get application server edition

Cause: JRF Failed to retrieve application server edition

Action: Verify that the application server is installed and accessible.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10027: Operation is not supported on this application server edition

Cause: Operation is not supported on this platform edition.

Action: Verify it is the right application server edition.
Level: 1

Type: ERROR

Impact: Configuration

JRF-10028: Invoke startup and shutdown class {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-10029: String {0} is in invalid format . Example of correct string format is {1}

Cause: String format is invalid.

Action: Correct the string format, see example of a correct string format in the exception message
Level: 1

Type: ERROR

Impact: Configuration

JRF-20001: Read domain {0} to applyJRF

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20002: Update JRF changes to domain {0} in {1} mode

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20003: Target JRF components to "{0}"

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20004: Cannot copy {0} to {1}: "{2}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20005: Environment variables {0} not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20006: Copying JRF configuration files from {0} to {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20007: Unable to add help for JRF commands: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20008: No domain has been read

Cause: JRF detects that domain has not been read.

Action: Read the domain offline or connect online before invoke JRF WLST command.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20009: JRF component or service with type "{0}" and name "{1}" is not found on server "{2}".

Cause: Domain has not been extended with JRF or upgraded with new JRF version, or the applyJRF command is out-of-sync with JRF in the domain

Action: Extend domain with JRF template, or invoke upgradeJRF() to upgrade the domain if the install is upgraded.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20010: {0} is not found.

Cause: file not found

Action: Verify oraclehomeproperties.xml exist
Level: 1

Type: ERROR

Impact: Configuration

JRF-20011: Node GUID does not exist or node is empty in {0}.

Cause: node not found or no value

Action: Verify oraclehomeproperties.xml exist
Level: 1

Type: ERROR

Impact: Configuration

JRF-20012: System properties {0} not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

JRF-20013: Target does not exist or not valid : {0}.

Cause: target not found or not valid

Action: Verify target exists and valid
Level: 1

Type: ERROR

Impact: Configuration

JRF-20014: Failed to create library at : {0}.

Cause: Creating shared library failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20015: Failed to create custom service : {0}.

Cause: Creating custom service failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20016: JRF_FAILED_CREATE_URLPROVIDER : {0}.

Cause: Creating URL Provider failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20017: Failed to config jvm args for : {0}.

Cause: Config JVM memory arguments failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20018: Failed to add jvm system property for : {0}.

Cause: Adding system property failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20019: Failed to parse template: {0}.

Cause: Template has error

Action: Verify template
Level: 1

Type: ERROR

Impact: Configuration

JRF-20020: Failed to get variable {0} from {1}.

Cause: Get variable failed

Action: Verify variable.xml
Level: 1

Type: ERROR

Impact: Configuration

JRF-20021: Failed to update targets of application {0}.

Cause: Failed to update application target

Action: Verify application
Level: 1

Type: ERROR

Impact: Configuration

JRF-20022: Failed to update {0}.

Cause: Failed to update oracle jdbc driver path

Action: Verify server
Level: 1

Type: ERROR

Impact: Configuration

JRF-20023: Failed to install application {0}.

Cause: Failed to install application

Action: Verify application
Level: 1

Type: ERROR

Impact: Configuration

JRF-20024: Failed to create variable {0} for {1}.

Cause: Failed to create variable

Action: Verify server
Level: 1

Type: ERROR

Impact: Configuration

JRF-20025: Need to apply jrf template to cell.

Cause: Cell is not jrf enabled

Action: Apply jrf template to the cell since this cell is not jrf enabled
Level: 1

Type: ERROR

Impact: Configuration

JRF-20026: Could not load/instantiate {0} JRFService instance.

Cause: Could not load/instantiate a JRFService implementation class instance.

Action: Check if JRFService implementation class in the error message can be loaded/instantiated by the classloader.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20028: JRFService not supported

Cause: JRFService is not supported.

Action: Check if the server has related JRFService available.
Level: 1

Type: ERROR

Impact: Configuration

JRF-20029: MapModulesToServers is disabled, cannot modify target of application {0}.

Cause: MapModulesToServers is disabled, cannot modify target of application.

Action: Enable MapModulesToServers task for this application
Level: 1

Type: ERROR

Impact: Configuration

JRF-20030: Enable StartupBeansService failed on server {0}.

Cause: Enable StartupBeansService failed

Action: Verify server connection
Level: 1

Type: ERROR

Impact: Configuration

JRF-20031: Initializing sun.awt.AppContext to avoid a redeployment leak. Please see bug 7711331

Cause: Avoid a redeployment leak

Action: Initializing sun.awt.AppContext
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20032: sun.awt.AppContext not found

Cause: sun.awt.AppContext not found

Action: Verify jdk
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20033: JRF startups - {0} failed. JRF is not configured properly. Resolve these issues before continuing. Individual startup stacktrace are included in the error log.

Cause: JRF is not configured properly

Action: Resolve these issues
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20034: JRF shutdowns - {0} failed. JRF is not configured properly. Resolve these issues before continuing. Individual shutdown stacktrace are included in the error log.

Cause: JRF is not configured properly

Action: Resolve these issues
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20035: invalid format.

Cause: invalid url format

Action: fix url format
Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20036: checkIfJRFApplied api failed on target {0} with exception {1}

Cause: The operation that checks if JRF applied to a target server or cluster failed

Action: See message and exception stack trace in admin server log to debug
Level: 1

Type: NOTIFICATION

Impact: Configuration

31 MCS-38601 to MCS-57840

MCS-38601: The diagnostics application encountered an internal error while processing the request.

Cause: Diagnostic Application Internal Error

Action: See the corresponding error message in the server logs for the root cause.
Level: 1

Type: SEVERE

Impact: Other

MCS-38602: Invalid value for request parameter ''{0}'': {1}

Cause: Invalid request parameter

Action: Retry the request with valid parameter values.
Level: 1

Type: SEVERE

Impact: Other

MCS-38610: The custom code container agent is not running, or cannot be reached (host: {0}, port: {1})

Cause: The custom code container agent is not running or cannot be reached

Action: Start the custom code container agent, or verify the system configuration
Level: 1

Type: WARNING

Impact: Other

MCS-15200: Invalid request URI: {0}. Relative URI must be of the form /<api>/<apiVersion>/<resource>.

Cause: The provided request URI is invalid.

Action: Relative URI must be of the form /api/apiVersion/resource.
Level: 1

Type: SEVERE

Impact: Other

MCS-15201: Could not retrieve metadata for the given API name and version.

Cause: Metadata could not be retrieved for the provided API name and version.

Action: Verify that the provided Backend, API and Resource information is correct.
Level: 1

Type: SEVERE

Impact: Other

MCS-15202: An IO exception occurred writing to ResponseContext out stream {0}.

Cause: An IO exception occurred writing to ResponseContext out stream.

Action: Check server diagnostics log for details.
Level: 1

Type: SEVERE

Impact: Other

MCS-15203: Processing of request URI {0} was aborted due to an exception occurring while attempting to access the HttpServletResponse output stream.

Cause: The HttpServletRequest output stream cound not be accessed.

Action: Check server diagnostics log for details.
Level: 1

Type: SEVERE

Impact: Other

MCS-15204: Could not create a request context for URI {0} as an unexpected exception has occurred.

Cause: An exception occurred while attempting to create a RequestContext.

Action: Check server diagnostics log for details.
Level: 1

Type: SEVERE

Impact: Other

MCS-15205: A timeout occured waiting on a response for the request context for URI {0}.

Cause: A timeout occurred waiting on a response from the RequestContext.

Action: Check server diagnostics log for details.
Level: 1

Type: SEVERE

Impact: Other

MCS-15206: Requested URI {0} references an internal API. Internal APIs are only accessable from within the domain.

Cause: An internal API request was made from outside the domain.

Action: Check server diagnostics log for details.
Level: 1

Type: SEVERE

Impact: Other

MCS-15207: 404 - Not Found

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-15208: An authentication failure occurred while processing request URI {0}. An Authorization header with valid credentials is required.

Cause: An authentication failure occurred.

Action: Check server diagnostics log for details.
Level: 1

Type: SEVERE

Impact: Other

MCS-15209: 401 - Unauthorized

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-15240: The RAML parser was unable to parse the supplied RAML for API {0}, version {1}. Error: {2}

Cause: The mobile API testing service was unable to parse the provided RAML

Action: Ensure the RAML provided to the API is correct.
Level: 1

Type: SEVERE

Impact: Other

MCS-15241: The API testing service received a poorly formatted Accept header in the request: {0}

Cause: The mobile API testing service received a poorly formatted Accept header

Action: Ensure the Accept header in the request is correctly formatted.
Level: 1

Type: WARNING

Impact: Other

MCS-15242: The API testing service received an Accept header for which it has no matching results. Available types are : {0}

Cause: The mobile API testing service received an Accept header it could not fulfil

Action: Ensure the Accept header in the request is of a type available in the RAML.
Level: 1

Type: WARNING

Impact: Other

MCS-15280: Service lifecycle listener {0} failed during startup with error: {1}

Cause: A setup or programming error has occurred for the indicated service lifecycle listener that prevented it from starting up correctly.

Action: Look for failures during invocation of this service instance
Level: 1

Type: WARNING

Impact: Other

MCS-15281: Service lifecycle listener {0} failed during shutdown with error: {2}

Cause: A setup or programming error has occurred for the indicated service lifecycle listener that prevented it from shutting down correctly.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: INFO

Impact: Other

MCS-15282: McsCore instance already set and cannot be reset

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-15283: Cannot get large/Reader Body content as a String

Cause: An attempt was made to read a message body as a String when the body had content that did not allow this

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15284: Cannot get large/stream Body content as a byte[]

Cause: An attempt was made to read a message body as a byte[] when the body had content that did not allow this

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15285: Cannot get binary content as a Reader/String (character data)

Cause: An attempt was made to read a message body as a Reader when the body had binary content. This is not allowed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15286: Body content already consumed. Cannot consume again.

Cause: An attempt was made to read a message body that had already been read, where the body is large and cannot be read multiple times.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15287: Cannot find binary content from given types of content

Cause: An attempt to identify binary content for a message body (given current available content types) failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15288: Cannot find character content from given types of content

Cause: An attempt to identify character content for a message body (given current available content types) failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15289: Error draining stream into internal byte[] content

Cause: An attempt to drain a message body stream into an internal byte[] for processing has failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15290: Error draining Reader into internal String content

Cause: An attempt to drain a message body Reader into an internal String for processing has failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15291: Unsupported XML parsed/node type: {0}

Cause: An attempt was made to create an XML message body using an unsupported/unknown XML node/object type.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.
Level: 1

Type: WARNING

Impact: Other

MCS-15292: Service was interrupted by an unchecked Error: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-15293: Service was interrupted by an unchecked Exception: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-15360: Unhandled exception was caught and returned via onException()

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-15361: Unhandled error was caught and callback notified via onError()

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-15362: A second response has been recieved for the request. It has been ignored. {0}

Cause: Multiple responses have been received for a request.

Action: No action required. Only the first response has been returned.
Level: 1

Type: SEVERE

Impact: Other

MCS-15363: Ignoring response because an exception or error has already been returned. {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-15364: Ignoring error because a response, exception or error has already been returned.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-15365: Ignoring exception because a response, exception or error has already been returned.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-15366: Ignoring exception raised when performing callback.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-37000: Server does not support ECID

Cause: The server running MCS does not support ECID

Action: To use ECID deploy MCS to a server that supports ECID
Level: 1

Type: SEVERE

Impact: Other

MCS-37001: The metering event could not be emitted

Cause: The request information could not be interpreted.

Action: Review the reported exception for further details
Level: 1

Type: WARNING

Impact: Other

MCS-37002: Unable to register event listener {0}

Cause: The event listener is not installed properly and cannot be found from the classpath.

Action: Review the reported exception for further details
Level: 1

Type: WARNING

Impact: Other

MCS-37003: Unable to set request context

Cause: The request context cannot be set in the HttpServletRequest

Action: Review the reported exception for further details
Level: 1

Type: WARNING

Impact: Other

MCS-37004: Unable to set request attributes

Cause: The request attributes cannot be set in the HttpServletRequest

Action: Review the reported exception for further details
Level: 1

Type: WARNING

Impact: Other

MCS-37005: Meter Event Processor is interrupted

Cause: The Meter Event Processor is interrupted and cannot process further events

Action: Review the reported exception for further details
Level: 1

Type: WARNING

Impact: Other

MCS-38501: Failed to update derived noun {0}.

Cause: An exception prevented a derived noun from updating one or more of its metrics.

Action: Review the reported exception for further details
Level: 1

Type: WARNING

Impact: Other

MCS-38591: Start of API Invocation

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-38592: End of API Invocation

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-38593: Unserviceable request

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-38594: Request Timeout

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-82701: We can't find an object with key {0} in collection "{1}".

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-82702: We can't find collection "{0}". Verify that {0} is included in your mobile backend.

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-82703: You must specify the content-length HTTP request header (the size of the object in bytes).

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-82704: SQL exception occurred.

Cause:

Action:
Level: 1

Type: INCIDENT_ERROR

Impact: Other

MCS-82705: {0} exceeds maximum object name length of {1} characters.

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-82707: You must specify a device ID (using the {0} HTTP request header) to access a collection with device-level isolation.

Cause: A request was made against a device isolated collection without including the device id

Action: Enusre the M_DEVICE_ID header is specified on the request.
Level: 1

Type: SEVERE

Impact: Other

MCS-82708: We can't find your mobile backend. Verify the name and ID.

Cause: X-Backend-Token header was missing or a mobile backend with the corresponding token was not found

Action: Check that a valid X-Backend-Token header was provided on the request.
Level: 1

Type: SEVERE

Impact: Other

MCS-82709: Your object was last modified on {0}, and hasn't changed since the date specified in the If-Modified-Since HTTP request header: {1}

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-82710: Your object was last modified on {0}, which is after the date specified in the If-Unmodified-Since HTTP request header: {1}

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-82711: Method is not allowed.

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-82712: The {0} query parameter must be an integer greater than or equal to 0. You specified: {1}.

Cause: Invalid value passed in for offset or limit query parameter

Action: Ensure the value of the offset and limit query parameters are valid integers.
Level: 1

Type: SEVERE

Impact: Other

MCS-82713: We can't fill your request for a subset of bytes in this range. Ensure that your range request does not exceed the size of the object in bytes.

Cause: Value provided in the Range header was not valid for this object.

Action: Update the value of the Range header. The range must be valid for the specified object.
Level: 1

Type: SEVERE

Impact: Other

MCS-82715: Object with eTag {0} did not match one of {1} that was specified in the If-Match HTTP request header.

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-82716: Object with eTag {0} matched one of {1} that was specified on the If-None-Match HTTP request header.

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-82717: We can't find an object with the GUID

Cause:

Action:
Level: 1

Type: SEVERE

Impact: Other

MCS-74500: Mobile client id is not specified

Cause: Mobile client id has not been specified.

Action: Ensure that an mobile client id is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74501: Platform is invalid (should be {0})

Cause: Platform is invalid.

Action: The error message indicates the correct platform
Level: 1

Type: SEVERE

Impact: Other

MCS-74502: Certificate is not specified

Cause: APNS certificate has not been specified.

Action: Ensure that an APNS certificate is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74503: Certificate is invalid: {0}

Cause: APNS certificate is invalid.

Action: Ensure that an APNS certificate is valid and encrypted correctly
Level: 1

Type: SEVERE

Impact: Other

MCS-74504: Certificate is empty

Cause: APNS certificate is empty.

Action: Ensure that an APNS certificate actually has a certificate
Level: 1

Type: SEVERE

Impact: Other

MCS-74505: API key is not specified

Cause: GCM API key has not been specified.

Action: Ensure that a GCM API key is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74506: Sender id is not specified

Cause: GCM sender id has not been specified It is required if using XMPP.

Action: Ensure that a GCM sender id is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74507: Method is not specified

Cause: GCM method has not been specified.

Action: Ensure that a GCM method is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74508: Service configuration for {0} ({1}) not found

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-74509: One of message or payload must be specified

Cause: Neither messgae nor payload has been specified. We don't have a message to send.

Action: Specify either message or payload
Level: 1

Type: SEVERE

Impact: Other

MCS-74510: Backend id is not specified

Cause: Backend id has not been specified.

Action: Ensure that a backend id is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74511: Mobile client {0} not found

Cause: Mobile client was not found.

Action: Ensure that a mobile client has been registered
Level: 1

Type: SEVERE

Impact: Other

MCS-74512: The service configuration is invalid: {0}

Cause: The service configuration is invalid. The exception will be provide more exact details.

Action: Update the service configuration to correct the exception.
Level: 1

Type: SEVERE

Impact: Other

MCS-74513: Notification token is not specified

Cause: Notification token has not been specified.

Action: Ensure that a notification token is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74514: Platform is not specified

Cause: Platform has not been specified.

Action: Ensure that a platform is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74515: Mobile client version is not specified

Cause: Moble client version has not been specified.

Action: Ensure that an mobile client version is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74516: Mobile client is not specified

Cause: Mobile client has not been specified.

Action: Ensure that a mobile client is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74517: Device is not specified

Cause: Device has not been specified.

Action: Ensure that a device is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74518: Problem formatting Date

Cause: The date send could not be parsed.

Action: Ensure that date specified are in the correct yyyy-MM-dd'T'HH:mm'Z' format
Level: 1

Type: SEVERE

Impact: Other

MCS-74519: Service configuration is not specified

Cause: Service configuration has not been specified.

Action: Ensure that a service configuration is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74520: Platform {0} does not match the service type {1}.

Cause: Service type in service configuration is not for the mobile client's platform.

Action: Ensure that the platform in the mobile client matches the service type
Level: 1

Type: SEVERE

Impact: Other

MCS-74530: Notification is not specified

Cause: Notification has not been specified.

Action: Ensure that a notification is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74531: Notification id not specified

Cause: Notification id has not been specified.

Action: Ensure that a notification id is specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74532: Notification {0} not found

Cause: Notification was not found.

Action: Ensure that the correct notification id is specified.
Level: 1

Type: SEVERE

Impact: Other

MCS-74533: Notification has already been processed and cannot delete notification {0}

Cause: The notification has already been processed and cannot be deleted.

Action: No action required
Level: 1

Type: SEVERE

Impact: Other

MCS-74534: Unexpected exception occurred

Cause: Unexpected error has occurred

Action: The exception message should provide more details.
Level: 1

Type: SEVERE

Impact: Other

MCS-74535: Error uploading APNS certificate

Cause: There was an unexpected exception uploading the APNS certificate

Action: Take action based on the underlying exception
Level: 1

Type: SEVERE

Impact: Other

MCS-74536: Invalid devices have not been specified

Cause: Invalid devices have not been specified

Action: Ensure that the invalid devices have been specified
Level: 1

Type: SEVERE

Impact: Other

MCS-74537: The value {0} is not a valid integer

Cause: An invalid integer value has been specified

Action: Ensure that the value is an integer
Level: 1

Type: SEVERE

Impact: Other

MCS-74538: The value {0} is not in the correct date format (must be in the form "YYYY-MM-DD[Thh:mm]Z")

Cause: An invalid date format has been specified

Action: Ensure that the expected date format is used.
Level: 1

Type: SEVERE

Impact: Other

MCS-74539: The value {0} is not in the correct date format (must be in the form "YYYY-MM-DDThh:mm:ss.SSSZ")

Cause: An invalid date format has been specified

Action: Ensure that the expected date format is used.
Level: 1

Type: SEVERE

Impact: Other

MCS-74540: The value {0} is not valid for the {1} enumeration. Valid values are {2}

Cause: An invalid enum value has been specified

Action: Ensure that the value is valid for the enum
Level: 1

Type: SEVERE

Impact: Other

MCS-74541: A handler was NOT found for {0}.

Cause: A handler has not been found for the given URI. This shouldn't happen because Asset Catalog should not have forwarded the request if it is unsupported.

Action: Contact Oracle Support Services.
Level: 1

Type: SEVERE

Impact: Other

MCS-74542: The media type was wrong. Expected "{0}" but was "{1}"

Cause: The request has the wrong media type.

Action: Ensure that the request has the correct media type
Level: 1

Type: SEVERE

Impact: Other

MCS-74543: "{0}" is not a valid sort field format. It should be of the form "<field name>[:[asc|desc]]".

Cause: The specified sort is invalid.

Action: Ensure that the sort is in the valid form
Level: 1

Type: SEVERE

Impact: Other

MCS-74544: "{0}" is not a supported sort field. It should be one of {1}.

Cause: The specified sort is unsupported.

Action: Ensure that the sort is supported
Level: 1

Type: SEVERE

Impact: Other

MCS-74560: The device token is in an invalid format: {0}

Cause: The device token is in an invalid format

Action: Ensure that the device token is in a valid format (either a 64 character hex string or 32 byte binary equivalent).
Level: 1

Type: SEVERE

Impact: Other

MCS-74561: The device provider for {0} was not found

Cause: The driver provider for the specified service type was not found

Action: Ensure that the driver provider is registered with the driver registry.
Level: 1

Type: SEVERE

Impact: Other

MCS-74570: Notification sent via APNS using {0}

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-74571: APNS returned a response packet: {0}

Cause: APNS sent a response packet

Action: Take action based on the reason.
Level: 1

Type: SEVERE

Impact: Other

MCS-74572: Unexpected exception thrown while sending via APNS

Cause: Exception thrown while sending an exception via APNS

Action: Take action based on the exception.
Level: 1

Type: SEVERE

Impact: Other

MCS-74573: Payload size ({0} bytes) exceeds limit ({1})

Cause: The payload is too large for APNS

Action: Ensure that the payload is less than the max size.
Level: 1

Type: SEVERE

Impact: Other

MCS-74574: Unexpected exception thrown while checking the feedback service

Cause: Exception thrown while checking the APNS Feedback Service

Action: Take action based on the reason it was rejected.
Level: 1

Type: SEVERE

Impact: Other

MCS-74580: Notification sent via GCM to {0} device(s)

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-74581: Unexpected exception thrown while sending via GCM

Cause: Exception thrown while sending an exception via GCM

Action: Take action based on the exception.
Level: 1

Type: SEVERE

Impact: Other

MCS-74582: Notification was rejected by GCM. Status={0}. Response={1}

Cause: The request was rejected by GCM

Action: Take action based on the reason it was rejected.
Level: 1

Type: SEVERE

Impact: Other

MCS-74583: GCM returned an invalid number of responses (expected={0}; actual={1})

Cause: The response returned by GCM has an invalid no of results. It should equal the number of devices in the notification.

Action: Contact Oracle Support
Level: 1

Type: SEVERE

Impact: Other

MCS-74584: Driver not found for '{0}'

Cause: There is no driver for the specific service type.

Action: Contact Oracle Support
Level: 1

Type: SEVERE

Impact: Other

MCS-74585: Maximum retries exceeded for notification {0} ({1})

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-74590: Feedback service will next check for invalid tokens @ {0}

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-74591: Error getting invalid notification tokens from APNS feedback service for {0}

Cause: An error occurred reading the invalid tokens from the APNS Feedback Service

Action: The exception message will provide more detail
Level: 1

Type: SEVERE

Impact: Other

MCS-74592: Unexpected status ({0}) when sending invalid tokens to environment {0}. Will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-74593: Checking APNS Feedback Service for invalid tokens

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-74594: Unexpected exception thrown while gettign invalid notification tokens from APNS feedback service

Cause: Exception thrown while checking for invalid tokens from the APNS Feedback Service

Action: Take action based on the exception.
Level: 1

Type: SEVERE

Impact: Other

MCS-39500: The MetricFeederAPI cannot be initialized

Cause: The required resources for the MetricsFeederAPI such as JMS cannot be acquired

Action: Check JMS configurations corresponding to Analytics server.
Level: 1

Type: WARNING

Impact: Other

MCS-57800: Implementation file {0} ({1} byte(s)) was uploaded

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

MCS-57801: RAML file validation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-57802: Could not upload implementation; the file with implementation is empty or API not defined.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-57803: Could not upload implementation; the content of the file with implementation is invalid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-57804: Could not upload implementation due to internal server error.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-57805: Exception thrown in AssetCatalog REST API. Mapped to the REST error response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

MCS-57806: Attempted to rename asset ''{0}'' (type: ''{1}'') to ''{2}''. Asset renaming is not allowed

Cause: Asset renaming is not allowed

Action: Avoid renaming asset
Level: 1

Type: SEVERE

Impact: Other

MCS-57807: BindingPolicy can be assigned to Environment only. Got: ' for API ''{1}''.

Cause: BindingPolicy can be assigned to Environment only

Action: Avoid attaching BindingPolicy to other assets
Level: 1

Type: SEVERE

Impact: Other

MCS-57808: Preset metadata references a resource ''{0}'' that can not be found

Cause: Cannot find requested resource

Action: Verify that resource is available at the specified location
Level: 1

Type: SEVERE

Impact: Other

MCS-57809: Can not update read-only Asset (name: {0}, version: {1}, id: {2})

Cause: Read-only assets cannot be updated

Action: Clone read-only asset instead of updating it
Level: 1

Type: SEVERE

Impact: Other

MCS-57810: Asset name (''{0}') is too long. Actual length: ''{1}''. Allowed length: ''{2}''.

Cause: Asset name length is limited

Action: Limit asset name to the suggested value
Level: 1

Type: SEVERE

Impact: Other

MCS-57811: Asset name (''{0}'') contains one of the reserved characters: ''{1}''

Cause: Asset name contains invalid characters

Action: Specify correct asset name
Level: 1

Type: SEVERE

Impact: Other

MCS-57812: Asset ''{0}'' has no version value provided.

Cause: Asset version is missing

Action: Provide version for the asset
Level: 1

Type: SEVERE

Impact: Other

MCS-57813: Asset ''{0}'' has version (''{1}'') in incorrect format. Supported version format is 'major.minor[.extra]+' with only '.'(dot) and digits allowed.

Cause: Asset version is incorrect

Action: Provide correct version for the asset
Level: 1

Type: SEVERE

Impact: Other

MCS-57814: Failed to convert {0} into {1}

Cause: Cannot find appropriate convertor

Action: Register appropriate convertor for required types
Level: 1

Type: SEVERE

Impact: Other

MCS-57815: Failed to merge {0} with {1}

Cause: Cannot find appropriate merger

Action: Register appropriate merger for required types
Level: 1

Type: SEVERE

Impact: Other

MCS-57816: Failed to patch {0} using {1}

Cause: Cannot find appropriate patcher

Action: Register appropriate patcher for required types
Level: 1

Type: SEVERE

Impact: Other

MCS-57817: Failed to load RAML content

Cause: Cannot load RAML content

Action: Verify RAML artifact details
Level: 1

Type: SEVERE

Impact: Other

MCS-57819: Cannot find default Environment

Cause: Cannot find default environment

Action: Create default environment
Level: 1

Type: SEVERE

Impact: Other

MCS-57820: Icon {0} not found

Cause: Cannot find requested icon

Action: Verify icon identifier
Level: 1

Type: SEVERE

Impact: Other

MCS-57821: Artifact {0} not found

Cause: Cannot find requested artifact

Action: Verify artifact identifier
Level: 1

Type: SEVERE

Impact: Other

MCS-57822: Unable to detect default user realm.

Cause: Cannot identify default user realm

Action: Verify that only user realm exist with default name
Level: 1

Type: SEVERE

Impact: Other

MCS-57823: Asset not found: {0}

Cause: Cannot find requested asset

Action: Verify that requested asset exists
Level: 1

Type: SEVERE

Impact: Other

MCS-57824: Policy Specification ''{0}'' does not exist

Cause: Specified policy specification does not exist

Action: Verify that policy specification name is correct, or create a new one
Level: 1

Type: SEVERE

Impact: Other

MCS-57825: Cannot delete missing entity: {0}

Cause: Specified entity does not exist

Action: Verify that correct entity identifier was specified
Level: 1

Type: SEVERE

Impact: Other

MCS-57826: Cannot update missing entity: {0}

Cause: Specified entity does not exist

Action: Verify that correct entity identifier was specified
Level: 1

Type: SEVERE

Impact: Other

MCS-57827: Incorrect token: ''{0}''. The appropriate Mobile Backend cannot be found

Cause: Specified mobile backend token is incorrect

Action: Verify mobile backend token
Level: 1

Type: SEVERE

Impact: Other

MCS-57828: ErrorCode must be a URI: {0}

Cause: Specified error code is incorrect

Action: Verify error code
Level: 1

Type: SEVERE

Impact: Other

MCS-57829: Cannot lookup specified EJB: {0}

Cause: Specified EJB is not found

Action: Verify EJB name
Level: 1

Type: SEVERE

Impact: Other

MCS-57830: Generic error

Cause: Generic error occured

Action: Verify logs
Level: 1

Type: SEVERE

Impact: Other

MCS-57832: No unique collection with a given name ''{0}'' is associated with the Mobile Backend identified by token ''{1}''

Cause: Incorrect collection name given

Action: Verify requested collection name
Level: 1

Type: SEVERE

Impact: Other

MCS-57833: Cannot clone missing entity: {0}

Cause: Specified entity does not exist

Action: Verify that correct entity identifier was specified
Level: 1

Type: SEVERE

Impact: Other

MCS-57834: Asset can not have empty name

Cause: Asset name is empty or not specified

Action: Set name to the asset
Level: 1

Type: SEVERE

Impact: Other

MCS-57835: Resource paths ''{0}'' and ''{1}'' can not be a part of one API, because one of them contains path parameter in place where another has a static value or they differ only by path parameter names or they are completely similar.

Cause: Incorrect API definition

Action: Verify API definition
Level: 1

Type: SEVERE

Impact: Other

MCS-57836: Client could not be published

Cause: Client couldn't be published

Action: Do not publish the Client
Level: 1

Type: SEVERE

Impact: Other

MCS-57837: Name is empty or is not specified in the package.json file

Cause: Name is empty or is not specified in the package.json file

Action: Set name to the implementation
Level: 1

Type: SEVERE

Impact: Other

MCS-57838: Version is empty or is not specified in the package.json file

Cause: Version is empty or is not specified in the package.json file

Action: Set version to the implementation
Level: 1

Type: SEVERE

Impact: Other

MCS-57839: Main entry is empty or is not specified in the package.json file

Cause: Main entry is empty or is not specified in the package.json file

Action: Set main entry to the implementation
Level: 1

Type: SEVERE

Impact: Other

MCS-57840: Keyword {0} not found

Cause: Cannot find requested keyword

Action: Verify keyword name
Level: 1

Type: SEVERE

Impact: Other

32 MFT-02001 to MFT-08003

MFT-02001: Not able to load the MDS repository.

Cause: MDS repository initialization failed.

Action: Check the metadata repository configuration and make sure that they are valid.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02002: No transfer found for the source(ID {0}).

Cause: No transfer found for the source.

Action: Ensure that the source is attached to a transfer.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02006: Data not found in MDS repository.

Cause: Data not found in MDS repository.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error. Make sure the meta data exists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02007: Error while creating new label with value {0} in MDS repository.

Cause: An error while creating new MDS label. Check if the label already exists.

Action: Check the metadata repository configuration and make sure that they are valid. Check if the label already exists in the system.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02008: Not able to resolve the MDS reference for source with ID {0}.

Cause: Reference meta data not exists in repository.

Action: Restore the deleted data in the MDS repository.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02009: Not able to resolve the MDS reference for transfer with ID {0}.

Cause: Reference metadata does not exist in the repository.

Action: Restore the deleted data in the MDS repository.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02010: Not able to resolve the MDS reference for target with ID {0}.

Cause: Referenced metadata does not exist in the repository.

Action: Restore the deleted data in the MDS repository.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02011: Label {0} does not exist in the MDS repository.

Cause: Label no longer exists in the MDS repository.

Action: Problem not recoverable. Contact Oracle Support Services.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-02101: Validation failed for the artifact [{0}].

Cause: Validation failed for the given artifact.

Action: Check the artifact configuration and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02102: Not able to retrieve {0} from the credential store for {1}.

Cause: Not able to retrieve the password from the credential store.

Action: Check the settings and data in the credential store or recreate the password. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02104: No target associated with the transfer.

Cause: No target is associated with the transfer.

Action: Associate at least one target with the transfer and redeploy.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02105: No source associated with the transfer.

Cause: No source is associated with the transfer.

Action: Associate a source with the transfer and redeploy.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02301: Error occurred while exporting the metadata.

Cause: Error during metadata export.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02351: Error occurred while importing the metadata.

Cause: Invalid import metadata.

Action: Make sure that import zip file is proper. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02401: The source [{0}] is currently associated with some transfers and so cannot be deleted.

Cause: The given source is currently referenced in some transfers and so cannot be deleted at this point.

Action: For each associated transfer that is associated with given source, detach the source, associate a new source, or delete the transfer. Then try deleting the source again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02402: The target [{0}] is currently associated with some transfers and so cannot be deleted.

Cause: The given target is currently referenced in some transfers and so cannot be deleted at this point.

Action: For each associated transfer that is associated with given target, detach the target, associate a new target, or delete the transfer. Then try deleting the target again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02403: Error occurred while resetting the metadata with preserved user changes {0}.

Cause: Exception while resetting the metadata.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02404: Error occurred while deleting the source [{0}] from metadata store.

Cause: Exception while deleting the given source from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02405: Cannot delete the domain-info(name {0}) because it is referenced in some B2B source/target types.

Cause: Cannot delete the domain-info because it is referenced in some B2B source/target types.

Action: Detach the domain-info from the referring B2B sources or targets. Then try deleting the domain-info again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02406: Cannot delete the domain-info(name {0}) because it is referenced in some Healthcare source/target types.

Cause: Cannot delete the domain-info because it is referenced in some Healthcare source/target types.

Action: Detach the domain-info from the referring Healthcare sources or targets. Then try deleting the domain-info again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02407: Cannot delete the callout(name {0}) because it is referenced in some transfer preprocessing.

Cause: Cannot delete the callout because it is referenced in some transfer preprocessing.

Action: Detach the callout from the referring transfer preprocessing. Then try deleting the callout again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02408: Cannot delete the callout(name {0}) because it is referenced in some transfer postprocessing.

Cause: Cannot delete the callout because it is referenced in some transfer postprocessing.

Action: Detach the callout from the referring transfer postprocessing. Then try deleting the callout again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02409: Cannot delete the domain-info(name {0}) because it is referenced in some Web Service source/target types.

Cause: Cannot delete the domain-info because it is referenced in some Web Service source/target types.

Action: Detach the domain-info from the referring Web Service sources or targets. Then try deleting the domain-info again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-02410: Error occurred while deleting the transfer [{0}] from metadata store.

Cause: Exception while deleting the given transfer from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02411: Error occurred while deleting the target [{0}] from metadata store.

Cause: Exception while deleting the given target from metadata store.

Action: Check the metadata repository configuration and make sure that they are valid. Also, review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02501: Error occurred while deploying the source artifact with id [{0}].

Cause: Error occurred while deploying the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while deploying the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02502: Error occurred while enabling the source artifact with id [{0}].

Cause: Error occurred while enabling the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while enabling the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02503: Error occurred while disabling the source artifact with id [{0}].

Cause: Error occurred while disabling the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while disabling the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02504: Error occurred while undeploying the source artifact with id [{0}].

Cause: Error occurred while undeploying the given source artifact.

Action: The configuration of the given source artifact may be incorrect or error occurred while undeploying the artifact. Check the source configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02505: Could not delete Deployment record for the currently deployed {0} [{1}] with label [{2}].

Cause: Artifact corresponding to given name and label is currently an Active deployment.

Action: Undeploy the artifact from the MFT console monitoring page and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02506: Deployment record does not exist for {0} [{1}] with label [{2}].

Cause: Artifact corresponding to given name and label is not found.

Action: Review the deployment history from the MFT console deployment page for the given artifact and check if artifact with the given label exists.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02507: Artifact {0} of type {1} is referenced in Transfer {2}.

Cause: Artifact corresponding to the given name is referenced in a transfer and cannot be deleted.

Action: Review deployment history for the given artifact and make sure it is not referenced in Transfer Deployments.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02508: Error deploying source {0}. Another source {1} was found deployed for URL {2}.

Cause: Another source that is already deployed is configured with the same URL.

Action: Configure the source with a different URL and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02509: Error deploying source {0}. Another source {1} was found deployed for folder {2}.

Cause: Another source that already deployed is configured with the same folder.

Action: Configure the source with a different folder and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02510: Error deploying SFTP source {0}. The configured private key is incorrect.

Cause: Error occurred while deploying the sFTP source. The configured private key is incorrect.

Action: Check if the key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02511: Error deploying SFTP target {0}. The configured private key is incorrect.

Cause: Error occurred while deploying the sFTP target. The configured private key is incorrect.

Action: Check if the key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02512: Error deploying source {0}. The configured PGP encryption alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP encryption alias is not valid.

Action: Check if the encryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02513: Error deploying source {0}. The configured PGP decryption alias is incorrect.

Cause: Error occurred while deploying the source. The configured PGP decryption alias is not valid.

Action: Check if the decryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02514: Error deploying transfer {0}. The configured PGP encryption alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP encryption alias is not valid.

Action: Check if the encryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02515: Error deploying transfer {0}. The configured PGP decryption alias for target {1} is incorrect.

Cause: Error occurred while deploying the target. The configured PGP decryption alias is not valid.

Action: Check if the decryption key is imported to the key store. If not, import it and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02516: Error deploying transfer {0}. No Internal server address configured in server properties.

Cause: Error occurred while deploying the Web Service target. The internal server address is not configured.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02517: Error deploying transfer {0}. No External server address configured in server properties.

Cause: Error occurred while deploying the Web Service target. The external server address is not configured.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02518: Error deploying transfer {0}. No internal FTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server FTP port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02519: Error deploying transfer {0}. No external FTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External FTP port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02520: Error deploying transfer {0}. No internal FTPS port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server FTPS port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02521: Error deploying transfer {0}. No external FTPS port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External FTPS port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02522: Error deploying transfer {0}. No internal sFTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The Internal Server sFTP port is not configured in server properties.

Action: Go to the Server Properties page and check the internal server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02523: Error deploying transfer {0}. No external sFTP port configured in server properties.

Cause: Error occurred while deploying the Web Service target. The External sFTP port is not configured in server properties.

Action: Go to the Server Properties page and check the external server information under Advanced Delivery Properties. Enter correct values and try deployment again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02524: Deployment validation failed while deploying source {0}.

Cause: Deployment validation failed while deploying the source.

Action: Check the source configuration and try again. Deploy from the UI again to check what validations failed or deploy the source using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02525: Deployment validation failed while deploying transfer {1}.

Cause: Deployment validation failed while deploying the transfer.

Action: Check the transfer configuration and try again. Deploy from the UI again to check what validations failed or deploy the transfer using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02526: Deployment validation failed while deploying target {1}.

Cause: Deployment validation failed while deploying the target.

Action: Check the target configuration and try again. Deploy from the UI again to check what validations failed or deploy the target using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02527: Deployment of source {0} failed. The password configured is incorrect.

Cause: Deployment of source failed due to invalid password.

Action: Check the key store configuration and ensure the password configured for the source is available in the key store.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02528: Deployment of target {0} failed. The password configured is incorrect.

Cause: Deployment of target failed due to invalid password.

Action: Check the key store configuration and ensure the password configured for the target is available in the key store.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02529: Error deploying source {0}. Transport Endpoint validation failed.

Cause: Error occurred while deploying the source. Transport validation failed due to incorrect configuration of the source endpoint.

Action: Check the source configuration and try again. Deploy from the UI again to check what validations failed or deploy the source using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02530: Error deploying Target {0}. Transport endpoint validation failed.

Cause: Error occurred while deploying the target. Transport validation failed due to incorrect configuration of the target endpoint.

Action: Check the target configuration and try again. Deploy from the UI again to check what validations failed or deploy the target using WLST in interactive mode.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02531: Invalid configuration found in the associated source {0}.

Cause: Error occurred while deploying the transfer because source configuration is invalid.

Action: Go to the source page, fix the invalid configuration, and try redeploying the transfer.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02532: Invalid configuration found in the associated target {0}.

Cause: Error occurred while deploying the transfer because the target configuration is invalid.

Action: Go to the target page, fix the invalid configuration, and try redeploying the transfer.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02533: Error. Could not find a deployment record for source [{0}].

Cause: A deployment record for the given source artifact could not be found in database.

Action: Deploy the source and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02534: Error. Could not find a deployment record for target [{0}].

Cause: A deployment record for the given target artifact could not be found in database.

Action: Deploy the target and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02535: Error. Could not find a deployment record for transfer [{0}].

Cause: A deployment record for the given transfer artifact could not be found in database.

Action: Deploy the transfer and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02536: The transfer [{0}] is already enabled.

Cause: The deployment record for the given transfer artifact is already enabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02537: The source [{0}] is already enabled.

Cause: The deployment record for the given source artifact is already enabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02538: The target [{0}] is already enabled.

Cause: The deployment record for the given target artifact is already enabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02539: The transfer [{0}] is already disabled.

Cause: The deployment record for the given transfer artifact is already disabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02540: The source [{0}] is already disabled.

Cause: The deployment record for the given source artifact is already disabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02541: The target [{0}] is already disabled.

Cause: The deployment record for the given target artifact is already disabled.

Action: No action required.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02542: Error occurred while deploying the transfer artifact with id [{0}].

Cause: Error occurred while deploying the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while deploying the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02543: Error occurred while deploying the target artifact with id [{0}].

Cause: Error occurred while deploying the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while deploying the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02544: Error occurred while enabling the transfer artifact with id [{0}].

Cause: Error occurred while enabling the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while enabling the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02545: Error occurred while enabling the target artifact with id [{0}].

Cause: Error occurred while enabling the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while enabling the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02546: Error occurred while disabling the transfer artifact with id [{0}].

Cause: Error occurred while disabling the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while disabling the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02547: Error occurred while disabling the target artifact with id [{0}].

Cause: Error occurred while disabling the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while disabling the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02548: Error occurred while undeploying the transfer artifact with id [{0}].

Cause: Error occurred while undeploying the given transfer artifact.

Action: The configuration of the given transfer artifact may be incorrect or error occurred while undeploying the artifact. Check the transfer configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02549: Error occurred while undeploying the target artifact with id [{0}].

Cause: Error occurred while undeploying the given target artifact.

Action: The configuration of the given target artifact may be incorrect or error occurred while undeploying the artifact. Check the target configuration and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02550: Error creating source [{0}]. Another source was found with this name.

Cause: Another source found with the same name as the given name.

Action: Configure the source with a different name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02551: Error creating target [{0}]. Another target was found with this name.

Cause: Another target found with the same name as the given name.

Action: Configure the target with a different name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02552: Error creating transfer [{0}]. Another transfer was found with this name.

Cause: Another transfer found with the same name as the given name.

Action: Configure the transfer with a different name and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02553: Incorrect additional http header value. Use key value pair and # as separator.Example pro1=value1#pro2=value2.

Cause: Incorrect additional http header value.

Action: Correct the value and try deploying again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-02554: Payload access is refering to invalid user/groups/roles.

Cause: Payload access is refering to invalid resource.

Action: Associate valid users/groups/roles and try redeploying the transfer.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03001: Error while starting the MFT server.

Cause: Unable to initialize the MFT Server dependent components.

Action: Ensure the infrastructure components like Identity Store, Security Store, Database, JCA are configured properly.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03002: Error while registering the Web Service source {0} with the provider.

Cause: Unable to register the Web Service source with the provider.

Action: Verify the Web Service source configuration and provider availability.Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03003: Error while Initializing Web Service source {0}.

Cause: An error occurred while registering the Web Service sources.

Action: Check the configuration of the deployed Web Service sources.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03004: Error while initializing Security components for Stripe {0}.

Cause: An Error occurred while creating the application policy data in the domain-wide policy store or while obtaining the connection to the default realm identity store.

Action: Ensure that the required permissions are granted to the MFT source and check the config parameters of the Identity Store.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03005: Error while initializing the WebLogic Work Manager {0}.

Cause: Unable to look up the Work Manager from the underlying environment.

Action: Check the Work Manager configuration in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03006: Error while registering the EM Discovery Mbean with Object name {0}.

Cause: An error occurred while registering the Config MBean with the Platform MBean Server.

Action: Review the diagnostic log for the exact error. Check whether management infrastructure is up and MFT MBean details are correct.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03007: Error while shutting down MFT server.

Cause: Unable to stop one or more dependent components of the MFT server.

Action: Review the diagnostic log for the exact error. Failure might be due to configuration of infrastructure components or connection problem.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03008: Error occurred while unsubscribing the Web Service source.

Cause: Unable to unsubscribe the Web Service source.

Action: Failure could be due to unavailability of Web Service registration service or improper Web Service configuration. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03009: Error while getting the Application Properties metadata.

Cause: Unable to get the Application Properties details.

Action: Check the Application Properties configuration in the system.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03010: Error occurred while updating the port {2} for service {1} of server {0} by user {3}

Cause: Exception while updating the port details of databases.

Action: Check the service, server instance and port. If these are correct it could be due to database issue. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03011: Error while loading the MFT Configuration MBean Properties from underlying infrastructure.

Cause: Unable to load the MBean Properties.

Action: Unable to load the MBean config properties from the underlying metadata store. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03012: Error while initializing the MFT persistence context.

Cause: Unable to initialize the persistence units context.

Action: Check the database availability and connection configuration. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03013: Error while initializing the MFT System event manager.

Cause: Unable to initialize the System event manager with required Queue and Topic receiver(s).

Action: Check the JMS system event Queue and Topic configurations in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03014: Error while initializing the MFT Purge event manager.

Cause: Unable to initialize the Purge event manager with required Queue receiver(s).

Action: Check the JMS purge event Queue and Topic configurations in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03015: Error while initializing the source listener {0}

Cause: Unable to start the JCA adapter to poll the files on the source.

Action: Check the source configuration parameters. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03016: Error updating port for server instance [{0}] and service [{1}]. The given server instance or service is incorrect.

Cause: Error occurred while updating port assignment for the given server instance and service in database.

Action: Check the port configuration for the server instance. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03250: Invalid argument(s) {0} provided to MFT utility for method {1}.

Cause: Arguments of the MFT command line utility are either missing or invalid.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03251: MFT utility - Operation {0} failed for parameters {1}.

Cause: EJBException thrown by the MFT utility due to failure in operation.

Action: Refer to MFT utilities documentation to determine the arguments and their types for the given command.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03252: Exception occurred while executing runtime purge for batch id [{0}].

Cause: Exception occurred while executing runtime purge for batch id [{0}].

Action: Try again with the recovery option by passing same batch id. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03253: Error while processing the purge event {0}.

Cause: An error occurred during processing of the purge event by the JCA JMS Adapter.

Action: Check the Purge Event Queue configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03254: Exception occurred while executing runtime archive for batch id [{0}].

Cause: Exception occurred while executing runtime archive for batch id [{0}].

Action: Try again by passing same batch id. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03255: Exception occurred while executing runtime restore from archive file [{0}].

Cause: Exception occurred while executing runtime restore from archive file [{0}].

Action: Try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-03302: Failed to initialize the engine. The engine message queue receivers for queue {0} were not initialized properly.

Cause: Problem with JMS queue settings.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Correct the queue settings and restart the MFT server.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03303: Error while stopping queue receivers for queue {0}.

Cause: An error has occurred while stopping the queue receivers.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03304: Failed to initialize the engine. The engine queue message producer for queue {0} was not initialized properly.

Cause: Problem with JMS queue settings.

Action: Check the MFT specific JMS Queue settings in the WebLogic console.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03305: Error while stopping the message producer for queue {0}.

Cause: An error has occurred while stopping queue message producer.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-03306: Error while initializing the source listeners

Cause: Unable to start the JCA adapter to poll the files on the sources.

Action: Check the source configuration parameters. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03307: Error initializing the MFT message processing engine.

Cause: An error has occurred while starting the message processing engine for MFT.

Action: Check the MFT specific JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03308: Error during shutdown of source listener {0}.

Cause: Unable to stop the JCA Adapter that is polling the source.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03309: Error stopping the MFT message processing engine.

Cause: An error has occurred while stopping the message processing engine for MFT.

Action: Review the diagnostic log for the exact error. Check the MFT specific JMS Queue settings in the WebLogic console.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03601: Error while starting the hosted server {0} with root dir {1} and port {2}.

Cause: An error occurred while starting the hosted server at a specified port and root directory.

Action: Check the root directory and Port assigned to the hosted server. For FTP over SSL and sFTP Servers, verify that all the required keys are configured.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03602: Error while shutting down the Hosted Server {0} running at port {1}.

Cause: An error occurred while stopping the hosted server running at the specified port.

Action: Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03604: Error while allocating the HA ports for the server instance {0}.

Cause: An error occurred while persisting the ports of the hosted servers for a given server instance.

Action: Check the ports definitions in MDS and the database config parameters. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'.Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03605: Error while fetching the Key store configuration from MDS.

Cause: An Error occurred while getting the default key store MO from MDS.

Action: Unable to get the key store information from the underlying metadata store during initialization. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-03606: Error while fetching the ES root directories from path {0} with option {1} for {2} server

Cause: An Error occurred while getting the directories under the ES root directory

Action: Check the Embedded Server root directory configuration and access permissions. Review the diagnostic log for the exact error.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04001: No associated active source found for the incoming file {0} from the endpoint {1}.

Cause: No matching MFT source found for the incoming message.

Action: Create and deploy the matching source. Redeliver the message to MFT.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04002: Multiple matching active sources found for the file {0} from endpoint {1}. Matching sources : {3}.

Cause: Invalid configuration: multiple active deployed sources for the same endpoint.

Action: Activate only one source for a given endpoint configuration.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04003: Not able to find the metadata reference for source with id {0}.

Cause: Reference metadata for the given source id does not exist in repository.

Action: Restore the deleted data in the metadata repository and redeploy the source.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04004: Invalid source message received for source message processing. Source message ID {0}.

Cause: Internal processing error.

Action: Contact Oracle Support Services.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04005: Invalid source configuration.

Cause: Invalid source configuration.

Action: The listening or Web Service source could not be registered due to error while creating the endpoint. Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04007: Associated source {2} for the file {0} from endpoint {1} was disabled.

Cause: Associated source was disabled.

Action: Enable the source and redeliver the message to MFT.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04008: No matching active transfer found for the message.

Cause: There is no associated transfer with a matching content type for the incoming message.

Action: Associate and deploy the matching transfer for the incoming message and resubmit the source message.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04009: Error during source message processing.

Cause: Unexpected error.

Action: Unexpected error encountered during source processing. Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04010: Source {0} is disabled.

Cause: Source is disabled.

Action: Enable the source and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04011: Duplicate source message. Original message id {0}.

Cause: Duplicate message submitted.

Action: Check the status of original message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04012: Directory reference as payload is not allowed for the source if compression processing action is not associated with the source.

Cause: Directory reference as payload is not allowed if compression processing action is not associated with the source.

Action: Associate compression as processing action for the source and redeploy the source. Resubmit the message after that.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04013: Invalid Payload information.

Cause: Bad request or specified payload doesn't exists.

Action: Send valid request, make sure payload information is correct.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04202: File {0} does not exist in the file system.

Cause: File does not exist in the file system.

Action: If the file has been purged, restore the file and resubmit the appropriate message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04204: IO exception encountered during message processing.

Cause: IO exception.

Action: IO exception encountered. Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04205: Error while encrypting the payload using PGP.

Cause: PGP encryption setting error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04206: Error while decrypting payload using PGP.

Cause: Invalid PGP-encrypted payload.

Action: Check the incoming payload.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04207: Error while compressing the payload.

Cause: Compression setting error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04208: Error while decompressing the payload.

Cause: Invalid compressed payload.

Action: Check the incoming payload.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04209: Error while executing source preprocessing

Cause: Unexpected source preprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04210: Error while executing source postprocessing

Cause: Unexpected source postprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04211: Error while executing target preprocessing

Cause: Unexpected target preprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04212: Error while executing target postprocessing.

Cause: Unexpected target postprocessing error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04213: Error during instance message processing.

Cause: Unexpected error.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04214: Unsupported compressed payload content.

Cause: The compression format of the payload is not supported in MFT.

Action: None: compressed format is not supported in MFT.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04215: Multiple file decompression is only supported for web service targets: SOAP, SOA, Service Bus, and ODI

Cause: Compressed payload contains multiple files.Multiple file decompression is only supported for web service targets: SOAP, SOA, Service Bus, and ODI.

Action: Decompress and submit a message for each decompressed file.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04216: No file found after decompression.

Cause: There were no files found after decompression.

Action: None: Invalid input message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04217: PGP private key not found for key alias {0}

Cause: Key for the alias is not present in the key store.

Action: Import the key and resubmit the message.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04218: PGP public key not found for key alias {0}

Cause: Key for the alias is not present in the key store.

Action: Import the key and resubmit the message.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04219: Message cannot be processed as the associated schedule has expired.

Cause: Message cannot be processed as the associated schedule has expired.

Action: Associate valid schedule and redeploy.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04220: PGP private key is invalid or key password is incorrect.

Cause: PGP private key is invalid or key password is incorrect.

Action: Correct the key password if key password is incorrect otherwise import valid PGP private key.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04221: Incoming data is encrypted with different public key.

Cause: PGP public key used for encryption is not corresponding key pair for private key specified.

Action: Associate correct private key alias for the decryption action.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04222: Incoming data is not a valid PGP encrypted data.

Cause: Incoming data is not a valid PGP encrypted data.

Action: Check the incoming data.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04223: Encryption algorithm or key length is restricted under the java policy.

Cause: Encryption algorithm or key length is restricted.

Action: Make sure algorithms and key used is not restricted under java security policy.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04224: PGP Encryption key is not a valid encryption key.

Cause: PGP Encryption key is not a valid encryption key.

Action: Make sure key alias is a correct PGP encryption public key.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04401: Exception encountered during execution of callout {0}.

Cause: Error while executing custom callout.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04501: Payload {0} not found in the MFT data storage.

Cause: Payload does not exist in the MFT data storage.

Action: If the data exists, try to restore the data.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04502: Invalid digest algorithm {0}.

Cause: Invalid algorithm.

Action: Correct the setting for the digest algorithm.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04503: Unexpected Error.

Cause: Unexpected exception occurred.

Action: Review the diagnostic log for the exact error.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-04504: JTA Transaction Error

Cause: JTA Transaction Error

Action: Review the diagnostic log for the exact error.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-04506: The archive {0} does not exist.

Cause: The given archive file could not be found. The file path is incorrect or the archive is empty.

Action: Check the archive file path. If path is correct, then ensure that the archive file is proper and try again.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04507: IP address or name of the host machine could not be determined.

Cause: IP address or name of the host machine could not be determined.

Action: Check if the system and network configuration is correct. Contact Oracle Administrator if problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-04508: Invalid argument.

Cause: Invalid argument.

Action: Check the input arguments provided and try again.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04509: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04510: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04511: External ports in the application properties cannot be null.

Cause: External ports in the application properties are null.

Action: Set the external ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04512: Error creating the directory {0}.

Cause: IO exception.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04513: Invalid in-progress transfer count {0} for source.

Cause: Unexpected error.

Action: Internal error while calculating the progress in transfer count. No action needed.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04514: Invalid in-progress target count {0} for the transfer.

Cause: Unexpected error.

Action: Internal error while calculating the progress in transfer count. No action needed.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04515: Transfer {0} is disabled.

Cause: Transfer is disabled.

Action: Enable the transfer and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04516: Target {0} is disabled.

Cause: Target is disabled.

Action: Enable the target and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04517: No target record found for the instance ID {0}.

Cause: No target record found for the instance.

Action: Try resubmitting the transfer or source instead.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04518: Target {0} is no longer associated with transfer {1}.

Cause: Target is no longer associated with transfer {1}.

Action: Associate the target with the transfer and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04519: Unexpected error occurred while processing message with id [{0}].

Cause: An unexpected error occurred during processing of the message with the given message id.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04520: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04521: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04522: Internal ports in the application properties cannot be null.

Cause: Internal ports in the application properties are null.

Action: Set the internal ports in the application properties.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04523: Error while moving the file [{0}] to location [{1}].

Cause: Issue while moving the file from one location to another.

Action: Check user permissions in the destination location.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-04524: Unexpected error occurred during instance message processing for transfer [{0}].

Cause: An unexpected error occurred during instance message processing for the given transfer.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04525: Unexpected error occurred during message processing for target [{0}].

Cause: An unexpected error occurred during message processing for the given target.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04526: Unexpected error occurred during message processing for source [{0}].

Cause: An unexpected error occurred during message processing for the given source.

Action: Review the diagnostic log for the exact error.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-04801: Error while processing the system event {0}.

Cause: An error occurred during processing of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04802: Error while submitting the system event {0} for service {1}.

Cause: An error occurred during processing of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04803: Error while submitting the system event {0} with resubmit type as {1} for instances {2} by user {3}.

Cause: An error occurred during submission of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04804: Error while submitting the system event {0} with instance ID {1} by user {2}.

Cause: An error occurred during submission of the system event by the JCA JMS Adapter.

Action: Check the System Event Queue and Topic configuration in the server. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-04805: Error while submitting pause transfer request. Target Message with Id [{0}] does not exist.

Cause: The given target message does not exist in database.

Action: Check the target message Id is correct and try again. Use the UI Monitoring Dashboard to verify target message details.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-04806: Error while submitting resume transfer request. Target Message with Id [{0}] does not exist.

Cause: The given target message does not exist in database.

Action: Check the target message Id is correct and try again. Use the UI Monitoring Dashboard to verify target message details.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05001: Unsupported endpoint {0} passed to adapter.

Cause: Unsupported endpoint has been passed to the adapter. Adapter only supports File / FTP / sFTP / JMS.

Action: Check the endpoint that was passed.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05002: Error occurred while creating JCABindingFactoryImpl. Type: {0}, endpoint: {1}.

Cause: An error occurred while initializing the adapter.

Action: Check the adapter properties and try again. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05003: No payload found while delivering to endpoint {0}.

Cause: No payload found while delivering a message.

Action: Try resubmitting the message.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05004: Error occurred while delivering message [{0}] to endpoint [{1}].

Cause: Error occurred while delivering message.

Action: Check the adapter properties and try again. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05005: Error occurred while closing connection after sending file to end point [{0}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05006: Error occurred while trying to open connection for endpoint [{0}], Type [{1}] and interface [{2}].

Cause: Error occurred while trying to open connection.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05007: Exception occurred while sending file [{0}] to endpoint [{1}].

Cause: File [{0}] does not exist.

Action: Ensure that the file [{0}] exists and resubmit.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05008: Exception occurred while creating connection with [{0}] for operation [{1}].

Cause: Error occurred while creating connection.

Action: Check the adapter properties and try again. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05010: Exception occurred while validating adapter binding reference property for end point [{0}].

Cause: Could not validate Binding reference properties.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05011: Value for property 'Physical Directory' is missing.

Cause: No value specified for property 'Physical Directory' in the input connection properties.

Action: Specify a value for 'Physical Directory' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05012: Exception occurred while creating connection for polling to end point [{0}] for operation [{1}]

Cause: Error occurred while creating connection.

Action: Check the adapter properties and try again. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05013: Exception occurred while creating poller service for endpoint [{0}].

Cause: Error occurred while creating poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05014: Exception occurred while starting poller service for endpoint [{0}].

Cause: Error occurred while starting poller service.

Action: Check the adapter properties and try again. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05015: Exception occurred while validating poller service for endpoint [{0}].

Cause: Could not validate adapter properties for poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05017: Error occurred while stopping the adapter polling.

Cause: Exception occurred while trying to close the adapter to stop polling the messages.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05019: Exception occurred while creating file [{0}] received from end point [{1}]

Cause: Could not create the file [{0}], which was received from endpoint [{1}].

Action: Check if the file exists but is a directory rather than a regular file, does not exist but cannot be created, or cannot be opened for any other reason.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05020: IO Exception occurred while writing to file [{0}] received from endpoint [{1}].

Cause: File created, but could not write to the file [{0}], which was received from endpoint [{1}].

Action: Check if write permissions are provided for file [{0}].
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05021: IO Exception occurred while closing file [{0}] after writing. This file was received from endpoint [{1}].

Cause: File [{0}] written, but IO exception occurred while closing the file, which was received from endpoint [{1}].

Action: Check if write permissions are provided for the file [{0}].
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05022: Source Message was found null while transferring to endpoint [{0}].

Cause: Source message found null.

Action: Resubmit the message. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05023: The JNDI queue name specified is null.

Cause: Adapter initialization failed because of invalid queue name.

Action: Try again. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05024: Exception occurred in postprocessing while moving or renaming the file after sending to [{5}]. Source File Name [{1}], Source Folder [{0}], Target Folder [{2}], Target File Name [{3}], Target File Naming Convention [{4}].

Cause: Error occurred while moving or renaming a file after sending.

Action: Check the adapter properties and resubmit the message. If the problem persists, please contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05025: Exception occurred while creating directory [{0}] for storing file [{1}] received from endpoint [{2}].

Cause: Could not create directory [{0}].

Action: Ensure that permissions (for creating directory and files) are assigned to this folder.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05027: Exception occurred while looking for directory for storing file [{0}] received from endpoint [{1}].

Cause: Error occurred while looking for directory for storing file.

Action: Check server properties. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05028: Exception occurred while deactivating poller service for end point [{0}].

Cause: Error occurred while deactivating poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05029: Exception occurred while closing poller service for endpoint [{0}].

Cause: Error occurred while closing poller service.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05030: Configuration mismatch found while polling to endpoint [{0}]. Alert code [{1}].

Cause: Configuration mismatch found while polling to endpoint [{0}].

Action: Ensure that the host name, port, username and password configured are correct and that the server is running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05031: Error occurred while reading metadata of file [{0}] from endpoint [{1}].

Cause: Error occurred while reading metadata of file.

Action: Check the adapter properties and try again. If the problem persists, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05032: Unexpected error during target delivery.

Cause: Unexpected error during target delivery.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05033: Error while creating the B2B/Healthcare endpoint {0} during target delivery.

Cause: Unexpected error while creating a b2b/healthcare endpoint.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05034: Error while delivering the payload to B2B/Healthcare target.

Cause: Unexpected error while delivering the payload.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05035: Error occurred while closing connection after getting size for file [{0}] for end point [{1}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05036: Error occurred while closing connection after pausing transfer for end point [{0}].

Cause: Error occurred while closing adapter connection.

Action: Check adapter properties and try again. If the problem persists,contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05037: Value for property 'Host Name' is missing.

Cause: No value specified for property 'Host Name' in the input connection properties.

Action: Specify a value for 'Host Name' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05038: Value for property 'Port' is missing.

Cause: No value specified for property 'Port' in the input connection properties.

Action: Specify a value for 'Port' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05039: Value for property 'User Name' is missing.

Cause: No value specified for property 'User Name' in the input connection properties.

Action: Specify a value for 'User Name' in the connection properties for the endpoint and try again.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05040: Error occurred during shutting down while clearing JCA resources.

Cause: Unexpected error occurred while clearing JCA resources.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05400: Invalid SOAP request received by MFTService on endpoint {0}.

Cause: SOAP message contains invalid XML.

Action: Review the SOAP request and check if the SOAP message contains invalid XML. This can be done by copying the request to a temporary XML file and opening the file in a web browser.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05401: MFT Service could not deliver message to Web Service endpoint {0}.

Cause: Web Service endpoint configured in MFT Target definition is either invalid or down.

Action: Check the Target configuration in the MFT console and verify the Web Service configuration parameters such as url , Port and Service. Try connecting to the configured endpoint by typing URL in a web browser.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-05402: Invalid SOAP request received by MFT Discovery Service from URL {0}.

Cause: SOAP Message contains invalid XML.

Action: Review the SOAP request and check if the SOAP message contains invalid XML. This can be done by copying the request to a temporary XML file and opening the file in a web browser.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05403: Discovery service is unable to query MFT Sources for the given application {0} and search Filter {1}.

Cause: MFT Source Message Table cannot be queried due to a Persistence Error.

Action: Verify whether the MFT Server is initialized successfully in the MFT Diagnostic Log. If there are issues in loading MFT persistence, try restarting MFT.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05404: Discovery service is unable to create a SOAP response for the given application {0} and search Filter {1}.

Cause: SOAP exception in creating SOAP response.

Action: Contact your Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05405: SOAP Request received on endpoint url {0} contains multiple attachments, which is not supported in MFT.

Cause: SOAP message contains an AttachmentPart that has multiple attachments. MFT does not support multiple attachments inline. Only one attachment is allowed.

Action: Review the SOAP request and make sure that the AttachmentPart has only one attachment.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05406: MFT Service is unable to process the AttachmentPart in the SOAP request received from endpoint url {0}.

Cause: IO error in reading the attachment stream.

Action: Review the SOAP request and make sure the attachment is configured according to SOAP standards.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05407: MFT Service is unable to process inline payload received from endpoint url {0}.

Cause: IO exception in reading inline Payload embedded in the SOAP body.

Action: Review the SOAP request and make sure the inline payload embedded in the SOAP body conforms to the schema defined in the MFT Service wsdl.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05408: MFT Service is unable to process reference payload coming from the endpoint url {0}.

Cause: IO exception in reading Reference payload embedded in the SOAP body.

Action: Review the SOAP request and make sure the FileReference or FTPReference element in the SOAP body conforms to the schema defined in the MFT Service wsdl.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05409: MFT Service is unable to process SOAP Headers coming from the endpoint url {0}

Cause: IO exception in reading SOAP Headers embedded in the SOAP message.

Action: Review the SOAP request and make sure the headers conform to the MFTHeader element schema defined in the MFT Service wsdl.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05410: Invalid url in Reference Payload element received on endpoint url {0} for reference type {1}.

Cause: For an incoming SOAP request containing a Reference Payload element, the URL defined in the message is invalid.

Action: Review the SOAP request and verify that the URL element in the Reference Payload contains a valid URL.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05410:

Cause:

Action:
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05411: Unable to create SOAP message from MessageFactory.

Cause: Unknown error due to the SOAP MessageFactory being unable to create the SOAP message.

Action: Contact the Oracle Administrator.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-05412: MFT Web Service transport is unable to create a SOAP Message with InlinePayload for Web Service endpoint {0}.

Cause: SOAP exception while adding InlinePayload element in the SOAP message. This could be due to invalid inline payload data passed to Transport layer

Action: Review the SOAP target configured in the MFT console to verify the Payload type and message type configuration. Also verify that the InlinePayload being passed to transport layer.
Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05413: MFT Web Service transport is unable to create a SOAP Message with Reference Payload for Web Service endpoint {0}.

Cause: SOAP exception while adding Reference Payload element in the SOAP message. This could be due to invalid Reference payload data passed to Transport layer

Action: Review the SOAP target configured in the MFT console to verify the type of reference defined.
Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05414: MFT Web Service transport is unable to create SOAP Message with Reference of type {0} for Web Service endpoint {1}

Cause: SOAP exception while adding FTP reference Payload element in the SOAP message. This could be due to invalid Reference payload data passed to the transport layer

Action: Review the SOAP target configured in the MFT console to verify the type of reference defined.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05415: MFT Web Service transport is unable to create SOAP Message with Base64 Encoded format for Web Service endpoint {0}

Cause: Error in encoding the SOAP message in Base64 format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05416: MFT Web Service transport is unable to create SOAP Message with SOAP Header {0} for Web Service endpoint {1}.

Cause: SOAP Exception while adding the SOAP headers to SOAP Message.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05417: MFT Web Service transport is unable to create SOAP Message with additional transport headers for Web Service endpoint {0}.

Cause: SOAP Exception while adding the HTTP headers to SOAP Message.

Action: Review Target configuration in MFT console to verify Additional headers field. Headers format is [header1]=[value1]#[header2]=[value2].
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05418: MFT Service is unable process SOAP Message containing Base64 content for Web Service endpoint {0}.

Cause: Error in Decoding the SOAP message containing Inline payload in Base64 format. This could be because the message does not contain a valid Base64 format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the SOAP request to validate the Base64 format.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05419: URL {0} configured for Web Service endpoint is invalid.

Cause: Web Service endpoint configured in MFT Target definition is either invalid or down.

Action: Check the target configuration in the MFT console and verify the Web Service URL. Try connecting to the configured endpoint by typing the URL in a web browser.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05420: MFT webservice Transport has necountered error parsing Inline XML payload for webservice endpoint {0}.

Cause: Error in parsing Inline XML payload. This could be because the Inline payload does not contain a valid XML format.

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the inline payload to validate the XML format.
Level: High

Type: ERROR

Impact: Message

MFT-05421: MFT webservice Transport has necountered error processing the payload stream.

Cause: Error in reading the inlne payload stream. This could be because the the payload stream may is Null or contains invalid data

Action: Review the SOAP target configured in the MFT console to verify the payload type and MessageType. Also check the payload recevied from MFT Source contains valid data.
Level: High

Type: ERROR

Impact: Message

MFT-05501: The {0} record {1} is already persisted.

Cause: The new record you are trying to persist is already available in the database.

Action: Check the details of the record you are trying to insert and try again.
Level: CRITICAL

Type: ERROR

Impact: MESSAGE

MFT-05502: No instance record found for message ID {0}.

Cause: There was no instance record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05503: Error occurred while performing persistence operation.

Cause: Exception occurred while performing the persistence operation.

Action: Review diagnostic log for detailed error message.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05504: Could not perform the persistence lock operation {0} for entity {1}.

Cause: Exception occurred while performing the persistence operation.

Action: The exception may have occurred while performing the corresponding database lock operation. Check the logs for the exception trace.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05505: Error while deleting Data Storage {0}.

Cause: Error occurred while deleting the Data Storage entity in the database.

Action: Make sure the Data Storage is not associated with any entity. Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05506: Error deleting Source Message for source {0}.

Cause: Error occurred while deleting the Source Message entity in the database.

Action: Make sure the source is not associated with any transfer. Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05507: Error deleting transfer instance for transfer {0}.

Cause: Error occurred while deleting the transfer instance entity in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05508: Error deleting Target Message {0}.

Cause: Error occurred while deleting the Target Message entity in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05509: No retry info record exists in database.

Cause: Internal error.

Action: Contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: MESSAGE

MFT-05510: No source lifecycle record exists for source name {0} and label {1} in database.

Cause: No record found.

Action: Redeploy the source and resubmit the message.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05511: No source record found for message ID {0}.

Cause: There was no source record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05512: No transfer instance record found for message ID {0}.

Cause: There was no transfer instance record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05513: No target message record found for ID {0}.

Cause: There was no transfer message record found in the database.

Action: Check the ID of the entity.
Level: LOW

Type: ERROR

Impact: MESSAGE

MFT-05514: Source {0} is not deployed.

Cause: Source is not deployed.

Action: Deploy the source and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05515: Transfer {0} is not deployed.

Cause: Transfer is not deployed.

Action: Deploy the transfer and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05516: Target {0} is not deployed.

Cause: Target is not deployed.

Action: Deploy the target and retry.
Level: LOW

Type: ERROR

Impact: SYSTEM

MFT-05517: Error deleting source {0}.

Cause: Error occurred while deleting the source in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05518: Error deleting transfer {0}.

Cause: Error occurred while deleting the transfer in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05519: Error deleting target {0}.

Cause: Error occurred while deleting the target in the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05520: Error fetching sources with label {0}.

Cause: Error occurred while fetching sources with this label from the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05521: Error fetching transfers with label {0}.

Cause: Error occurred while fetching transfers with this label from the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05522: Error fetching targets with label {0}.

Cause: Error occurred while fetching targets with this label from the database.

Action: Check the logs for the exception trace.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05523: Batch id [{0}] provided by user for purge recovery does not exist.

Cause: Batch id [{0}] provided by user for purge recovery does not exist.

Action: Check the passed batch id and try again. You can start a new purge also by passing the batch id as blank. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05524: Batch id [{0}] provided by user, for filesystem purge, does not exist.

Cause: Batch id [{0}] provided by user, for filesystem purge, does not exist.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05525: Filesystem purge is already run successfully for the provided batch id [{0}].

Cause: Filesystem purge is already run successfully for the provided batch id [{0}].

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05526: Filesystem purge can not be run without a valid Root Directory configured.

Cause: No Root directory configured in the Application Settings.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05527: Runtime Purge is not yet executed for the batch id [{0}]. FS Purge can not be run without first running the Runtime Purge.

Cause: Runtime Purge is not yet executed for the batch id. FS Purge can not be run without first running the Runtime Purge.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05528: Filesystem archive is already run successfully for the provided batch id [{0}].

Cause: Filesystem archive is already run successfully for the provided batch id [{0}].

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05529: Batch id [{0}] provided by user, for filesystem archive, does not exist.

Cause: Batch id [{0}] provided by user, for filesystem archive, does not exist.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05530: Filesystem archive can not be run without a valid Root Directory configured.

Cause: No Root directory configured in the Application Settings.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05531: Error while creating the archive file {0}. Error Message: {1}

Cause: Error while creating the archive file.

Action: Check the Root Directory under Hosted Server properties. Contact Oracle Support if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05532: Filesystem Archive operation started for the provided batch id [{0}] but not complete. Filesystem purge can not continue.

Cause: Filesystem Archive operation started for the provided batch id but not complete. Filesystem purge can not continue.

Action: Check the passed batch id and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05533: Error while adding payload {0} to the archive file. Error Message: {1}

Cause: Filesystem error while adding payload file to the archive.

Action: Check the payload file path, permissions and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05534: Error while working with archive file {0}. Error Message: {1}

Cause: Filesystem error while working with archive file.

Action: Check the archive file path, permissions and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05535: Error while working with archive file {0} for restore. Error Message: {1}

Cause: Filesystem error while working with archive file.

Action: Check the archive file path, permissions and try again. Contact Oracle Support if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-05802: Exception occurred while querying for ESS job definition [{0}].

Cause: Unexpected exception occurred while querying for the ESS job definition [{0}].

Action: Ensure that the MFT Custom Hosting App is properly deployed. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05806: Exception occurred while looking up JNDI context.

Cause: Unexpected exception occurred while looking up the JNDI context.

Action: Check the JNDI configuration for ESS on your application server.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05807: Exception occurred while looking up EJB [{0}].

Cause: Could not look up ESS EJB [{0}].

Action: Ensure that the MFT custom hosting app (MFTCustomHostingApp) is installed properly.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05808: Unexpected error occurred while submitting an ESS job with details: job type [{0}], schedule name [{1}], job description [{2}], schedule time [{3}].

Cause: Unexpected error occurred while submitting an ESS job.

Action: Check the schedule details and deploy again. Also verify that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05809: {0}

Cause: Validation failed for schedule.

Action: Check your schedule details. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05810: Exception occurred while looking for schedule with name [{0}].

Cause: Unexpected exception occurred while looking for schedule with name [{0}].

Action: Ensure that the schedule is attached to the artifact and try deploy again. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05811: Could not find schedule with name [{0}].

Cause: Could not find a schedule with name [{0}].

Action: Ensure that the schedule is attached with artifact and try deploy again. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05812: Exception occurred while opening ESS runtime service. Event: [{0}].

Cause: Could not open ESS runtime service.

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05813: Exception occurred while opening ESS metadata service. Event: [{0}].

Cause: Could not open ESS metadata service

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05814: Exception occurred while closing ESS runtime service. Event: [{0}].

Cause: Could not close ESS runtime service.

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05815: Exception occurred while closing ESS runtime service. Event: [{0}].

Cause: Could not close ESS metadata service.

Action: Check that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05816: Could not find ESS job with id [{0}] while cancelling.

Cause: Could not find the ESS job while cancelling.

Action: Ignore this exception. A new job has been submitted as part of a new deployment.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05817: Exception occurred while cancelling the ESS job with ID [{0}].

Cause: Illegal Job State Found. Cannot be cancelled.

Action: Try again or contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05818: Could not find ESS job request with ID [{0}]. Event [{0}].

Cause: Could not find ESS job request with id [{0}].

Action: Check that the artifact is deployed and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05819: Unexpected error occurred for job request ID [{0}]. Event [{1}].

Cause: Unexpected error occurred for job request ID [{0}].

Action: Check that the artifact is deployed and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05821: Exception occurred while looking up EJB [{0}].

Cause: Could not look up ESS EJB [{0}].

Action: Ensure that the MFT custom hosting app (MFTCustomHostingApp) is installed properly. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05822: Error occurred for schedule name [{1}]. Event: [{0}].

Cause: Error occurred for schedule name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05823: Validation failed for schedule name [{1}]. Event [{0}].

Cause: Validation failed for schedule name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05824: Schedule already exists with name [{1}]. Event: [{0}].

Cause: Schedule already exists with name [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05825: Null schedule passed for event [{0}].

Cause: Null schedule passed for event [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05826: ID in schedule found null for event [{0}].

Cause: ID in schedule found null for event [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05827: Exception occurred for schedule [{1}]. Event: [{0}].

Cause: Unexpected exception occurred for schedule [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05828: Validation failed for schedule [{1}]. Event: [{0}].

Cause: Validation failed for schedule [{1}]. Event: [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05829: Schedule object found null for event [{0}].

Cause: Schedule object found null for event [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05830: Passed schedule name is null for event [{0}].

Cause: Passed schedule name is null for event [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05831: No schedule found with given name [{0}].

Cause: No schedule found with given name [{0}].

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05832: Unexpected error occurred while querying for schedule with name [{0}].

Cause: Unexpected error occurred while querying for schedule with name [{0}].

Action: Check the schedule details and try again. Also verify that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05833: Schedule name passed as NULL while deleting schedule.

Cause: Schedule name passed as NULL while deleting schedule.

Action: Check the schedule details and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05834: Unexpected error occurred while deleting schedule with name [{0}].

Cause: Unexpected error occurred while deleting schedule with name [{0}].

Action: Check the schedule details and try again. Also verify that ESS environment is up and running.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05841: Could not find job definition with name [{0}].

Cause: Could not find job definition with name [{0}].

Action: Ensure that the MFT Custom Hosting App is deployed. For further details, contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05842: Exception occurred while checking if schedule with name [{0}] is in use.

Cause: Unexpected exception occurred while checking if schedule with name [{0}] is in use.

Action: Check the database connection.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05843: Could not find ESS job with id [{0}] while doing operation {1}.

Cause: Could not find the ESS job while doing a specified operation.

Action: Ignore this exception. Job has been cancelled already as part of deployment cleanup.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05844: Exception occurred while doing the operation {1} with ESS job ID [{0}].

Cause: Illegal Job State Found. Cannot do the specified opeation.

Action: Try again or contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05845: Operation {1} with ESS job ID [{0}] is not allowed.

Cause: Specified operation is not allowed on the given job.

Action: Try again or contact Oracle Support Services.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05846: {0}

Cause: Exception occurred while interacting with ESS

Action: Check your ESS environment and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-05847: {0}

Cause: Exception occurred while invoking the ESS through security interceptor.

Action: Check your ESS environment and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06001: Error while initializing security for stripe {0}.

Cause: An error occurred while defining the required policy for the application stripe.

Action: Check whether the application has all the required permissions in the EM and policy store connection properties. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06002: An error occurred while performing the security operation.

Cause: An error occurred while executing the security operation on the specified application stripe.

Action: Check the security store configuration in the WebLogic console or jps-config.xml and default permissions of MFT in the policy store. Review the diagnostic log for the exact error.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06003: Error while initializing the identity store for default realm.

Cause: An error occurred while initializing identity store with default security realm.

Action: Check the security store configuration in the WebLogic console or jps-config.xml and default permissions of MFT in the policy store. Review the diagnostic log for the exact error.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06005: Illegal MFTESPermission resource name {0}.

Cause: The resource name is not in the expected MFT ES Permission format.

Action: Correct the resource name parameter using the format 'resourceName={ResourceName},includeSubfolders=true|false,,serverType=FTP|SFTP'.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06006: Error while performing the SSH Key store operations on key type:{0} and alias {1}.

Cause: An error occurred while getting the SSH key store keys or aliases from the specified location.

Action: Check the key store location in the metadata repository and ensure that the required keys are present in the specified location. Review the diagnostic log for the exact error, and Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06007: Secured Method {0} is not annotated with required parameters.

Cause: An error occurred while checking the access provisioning before executing the method.

Action: Annotate the method with the required parameters.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06008: Error while performing the credential operation {0} for alias {1}.

Cause: An error occurred while performing the credential operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06009: Error while performing the key store operation {0}.

Cause: An error occurred while performing the key store operation.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-06010: An error occurred while performing the security operation on stripe {0}, store {1} and alias {2}.

Cause: An error occurred while executing the security operation on the specified application stripe.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06011: Invalid key file location [{0}]. The given path does not exist.

Cause: The given key file location does not exist or the key file is an empty file.

Action: Provide the correct path for export and while importing make sure that valid non empty key file exists at the given path.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06012: The imported key file {0} has multiple key rings. Importing multiple key rings is not supported.

Cause: The key file being imported has more than one PGP key.

Action: Import a valid key file that has only one key ring.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06013: Unable to get the resource type {0} while granting the permission for resource {1}.

Cause: Internal resource type definition might have failed, there is no associated resource type defined in the policy store.

Action: Resource type should be predefined before granting the permission by the security layer. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06014: Unable to get the Principal of user/group {0} with type {1}.

Cause: The principal type specified for permission grant is invalid.

Action: Grant the permission with the valid principal type which can be a User or Group or Application Role.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06015: Error while granting the permission {2} to resource {0} for principal(s){1}.

Cause: An exception occurred while granting the permission for a resource.

Action: Check the parameters used for granting the permission. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06016: Error while getting principals and actions of resource {0} with type {1}.

Cause: An exception occurred while getting the principals and actions of a resource.

Action: Check the resource name for validity. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06017: Error while revoking the permission {2} of a resource{0} for principal(s){1}.

Cause: An exception occurred while deleting the permissions of a resource.

Action: Check the revoke parameters. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06018: Authorization failure for principal(s) {0} to resource {1} for action {2}.

Cause: Access control exception occurred for a user while doing an operation.

Action: If this error encountered even if the operation was allowed for the user, then check the permissions of the user. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06019: Unable to create the MFT OPSS resource type {0}.

Cause: An error occurred while defining the resource type.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06020: Unable to create the Principal object for principal name {0} and type {1}.

Cause: An error occurred while creating the principal object.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06021: Unable to get the members of the role {0}.

Cause: An error occurred while fetching the members of a role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06022: Error while fetching all the application roles of application stripe {0}.

Cause: An error occurred while fetching the all the application roles.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06023: Error while fetching all the application roles of principal {0} with type {1}.

Cause: An error occurred while fetching the all the application roles of a principal.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06024: Error while fetching the granted resources of a principal {0}.

Cause: An error occurred while fetching the resources of a principal.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06025: Error while deleting all the grants of a resource {0} with type {1}.

Cause: An error occurred while deleting all the grants of a resource.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06026: Error while creating an application role with name {0}.

Cause: An error occurred while creating an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06027: Error while deleting the application role with name {0}.

Cause: An error occurred while deleting an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06028: Error while adding the member(s) {0} to application role {1}.

Cause: An error occurred while adding members to an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06029: Error while removing the member(s) {0} from application role {1}.

Cause: An error occurred while removing members of an application role.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06030: Unable to authenticate the user {0}.

Cause: An error occurred while authenticating the user.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06031: Unable to get the enterprise groups of the user {0}.

Cause: An error occurred while getting the enterprise groups of the user.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06032: Error while retrieving the list of users/groups from identity store with criteria {0}.

Cause: An error occurred while fetching the users from identity store with search criteria.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06033: Invalid value [{0}] for parameter [{1}].

Cause: Parameter value supplied is incorrect.

Action: Provide the expected parameter value.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06034: The imported key file is not having valid encryption/decryption key.

Cause: The key file being imported has no valid PGP key.

Action: Import a key file that has a valid PGP key.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06035: A key already exists for the given key alias {0} in credential store.

Cause: A key is already created for the given key alias in the credential store.

Action: Import the key file again with a different key alias.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06036: Key not found for the given key alias {0} in credential store.

Cause: No key was found for the given key alias in the credential store.

Action: Check if a key for the given key alias has been generated or not in the credential store.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06037: Invalid key file [{0}]. The given key file is an empty file.

Cause: The given key file location to export CSF Key does not exist.

Action: Provide the correct path for export and while importing make sure that valid non empty key file exists at the given path.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-06038: Path {0} specified on MFT embedded server for the resource is invalid.

Cause: No directory exists on MFT Embedded server specified by given path.

Action: Check if path specified is a valid directory on MFT Embedded server. If directory does not exist correct the Path input to point to existing directory OR create a new directory with the given Path.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06039: Error in configuring home directory {0} for user {1}.

Cause: Error in configuring user home directory due to error accessing metadata for User/Group.

Action: Review Metadata repository configuration for MFT Embedded Server users. Try running MFT metadata export command to see if metadata repository configured properly.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06040: Invalid Embedded Server types specified in the input.

Cause: Server Types specified in the input does not belong to one/more of the types FTP,SFTP.

Action: Provide server types which contains one ore more values FTP,SFTP.
Level: MEDIUM

Type: ERROR

Impact: MESSAGE

MFT-06041: Invalid permissions set {0} provided.

Cause: The permissions set provided contains one or more values that are not from the supported set 'READ,WRITE,DELETE,LIST'.

Action: Provide permissions that contains one or more values from supported set 'READ,WRITE,DELETE,LIST'.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06042: Error while registering the WSM Security Policies to endpoint {0}.

Cause: An exception occured while registering the WSM policies with WSM Policy Manager.

Action: Check the endpoint policies and WSM Manager configuration.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06043: Error while unregistering the WSM Security Policies of endpoint {0}.

Cause: An exception occured while unregistering the WSM policies from WSM Policy Manager.

Action: Check the endpoint policies and WSM Manager configuration.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-06044: Error while deleting the WSM assembly file of endpoint {0}.

Cause: An exception occured while deleting the WSM assembly file from the MDS repository.

Action: Check the MDS configuration and endpoint availability.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07001: Error while creating audit record for the event {0}.

Cause: Error while creating audit record for the event .

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07002: Error while initializing audit framework.

Cause: Error initializing audit framework.

Action: Check Audit configuration in EM console. Contact Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07003: Audit enabled method {0} is not annotated with the required parameters.

Cause: An error occurred during auditing after executing a method.

Action: Annotate the method with the required parameters.
Level: CRITICAL

Type: ERROR

Impact: SYSTEM

MFT-07201: Error while sending notification.

Cause: Error while sending notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07202: Error while sending email notification.

Cause: Error while sending email notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07203: Error while sending sms notification.

Cause: Error while sending sms notification.

Action: Check the notification settings. Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, indicates the reason for this exception. Contact Oracle Support Services if the problem persists.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07401: Callout with name: {0} exists in the Metadata Store. Not creating a new one.

Cause: An existing callout with same name was found in the Metadata Store.

Action: Change the callout name and try again. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07402: Exception while creating Callout.

Cause: EJBException thrown by utility while creating callout.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07403: Callout definition XML input file [{0}] not found.

Cause: Callout definition XML input file not found. The given file name or file path is incorrect.

Action: Provide provide a valid file path and try again.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07404: Callout definition XML File validation failed. Please correct the errors and rerun the utility.

Cause: Callout definition XML File validation failed. Please correct the errors and rerun the utility.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07405: Invalid Notification event type: {0}.

Cause: Invalid notification event type.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07406: Contact Information not found. Type: {0} Value: {1}.

Cause: Contact not found. Add the contact to the system and rerun the utility.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07407: An Exception occurred while running MFT utility.

Cause: An Exception occurred while running the MFT utility.

Action: Refer to the MFT utilities documentation to determine arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07408: Contact already exists. Type: {0} # Value: {1}.

Cause: A contact of the given type and value already exists in the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07409: Error while creating contact of type: {0} and value: {1}.

Cause: An error occurred while creating a new contact of the given type and value.

Action: Refer to the MFT utilities help to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07410: Error while deleting callout: {0}.

Cause: An error occurred while deleting the given callout.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07411: Error occurred while listing all the callouts in the system.

Cause: An error occurred while listing all the callouts in the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07412: Error while adding a contact to notification event. Event: {0} # Contact type: {1} # Value: {2}.

Cause: An error occurred while adding a contact to the notification event.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07413: Error while removing a contact from a notification event. Error Message: {0}.

Cause: An Error while removing a contact from a notification event.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07414: Error while deleting a contact from the system. Error Message: {0}.

Cause: An error occurred while deleting a contact from the system.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07415: Unsupported artifact type found. Artifact type: {0}.

Cause: Unsupported artifact type found. Supported values are SOURCE, TARGET and TRANSFER.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07416: Exception while getting the id for source artifact [{0}].

Cause: Exception occurred while getting the source id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07417: Cannot delete the contact. Given contact is associated with a notification event. Contact type: {0} :: Value: {1}.

Cause: Given contact is associated with a notification event. First remove the contact from the event and then try deleting the contact again.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07418: Error while listing contacts from the system. Contact type: {0}.

Cause: Error while listing the contacts of the given type. Try again.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command to make sure correct values are passed to the given method.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07419: Callout with name: {0} not found in MDS. No changes done.

Cause: An existing callout with the given name was not found in the Metadata Store.

Action: Provide a different and correct callout name and try again. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07420: Invalid value supplied for group name. Callout definition for {0} not changed.

Cause: Incorrect value provided for group name.

Action: Valid values for group name can contain any combination of comma-separated values of following: Source-pre,Source-post,Target-pre,Target-post. Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07421: Error while modifying callout {0}. Error Message: {1}.

Cause: An Error occurred while modifying the callout definition.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07422: Error while creating {0} keys. Error Message: {1}.

Cause: An Error occurred while creating sample keys.

Action: Refer to the MFT utilities documentation to determine the arguments and their types for the given command.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07423: Exception while getting the id for target artifact [{0}].

Cause: Exception occurred while getting the target id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07424: Exception while getting the id for transfer artifact [{0}].

Cause: Exception occurred while getting the transfer id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07425: Exception while getting the name for transfer artifact id [{0}].

Cause: Exception occurred while getting the transfer id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07426: Exception while getting the name for target artifact id [{0}].

Cause: Exception occurred while getting the target id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07427: Exception while getting the name for source artifact id [{0}].

Cause: Exception occurred while getting the source id from metadata store for the given name.

Action: Contact the Oracle Administrator.
Level: HIGH

Type: ERROR

Impact: SYSTEM

MFT-07428: Error while retrieving deployment history for transfer [{0}].

Cause: Exception occurred while retrieving deployment history information for the given transfer.

Action: Check the transfer deployment details in UI. Deploy the transfer from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07429: Error while retrieving deployment history for target [{0}].

Cause: Exception occurred while retrieving deployment history information for the given target.

Action: Check the target deployment details in UI. Deploy the target from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07430: Error while retrieving deployment history for source [{0}].

Cause: Exception occurred while retrieving deployment history information for the given source.

Action: Check the source deployment details in UI. Deploy the source from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07431: Error while retrieving deployment history for transfer [{0}].

Cause: Exception occurred while retrieving deployment history information for the transfer source.

Action: Check the transfer deployment details in UI. Deploy the transfer from UI or WLST and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07432: Exception occurrred while checking if transfer [{0}] exists in metadata store.

Cause: Exception occurred while checking if the given transfer exists in metadata store.

Action: Restore the deleted transfer artifact in metadata store and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07433: Exception occurrred while checking if target [{0}] exists in metadata store.

Cause: Exception occurrred while checking if the given target exists in metadata store.

Action: Restore the deleted target artifact in metadata store and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-07434: Exception occurrred while checking if source [{0}] exists in metadata store.

Cause: Exception occurrred while checking if the given source exists in metadata store.

Action: Restore the deleted source artifact in metadata store and try again.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08001: Error while reading metadata archive {0}. Error Message: {1}

Cause: An Error occurred while reading the metadata archive file.

Action: Refer to the plugin logs for more details.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08002: Error while closing metadata archive {0}. Error Message: {1}

Cause: An Error occurred while closing the metadata archive file.

Action: Refer to the plugin logs for more details.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

MFT-08003: Error while processing metadata file {0}. Error Message: {1}

Cause: An Error occurred while either reading or parsing the metadata xml file.

Action: Refer to the plugin logs for more details.
Level: MEDIUM

Type: ERROR

Impact: SYSTEM

33 MDS-00001 to MDS-92006

MDS-00001: exception in Metadata Services layer

Cause: An exception occurred in the Metadata Services layer.

Action: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00002: unexpected internal error

Cause: An unexpected internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00003: error connecting to the database

Cause: A database connection to the metadata repository could not be established.

Action: Contact the database administrator or system administrator to get the problem resolved.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00005: unable to find XML element or text "{0}"

Cause: The XML element with the given local name or the text node containing the given data could not be located by traversing through the document while applying customizations to a metadata object. The internal in-memory MDocument structure may be corrupted.

Action: Retry the operation. Contact Oracle Support Services if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00008: Attribute "{0}" is not allowed for element {1} namespace {2} in metadata object {3}.

Cause: An attempt was made to add an attribute to an element that does not conform to the element"s schema definition.

Action: If the Bean API is being used, then determine if the beans need to be regenerated. Otherwise, inspect the element definition for valid attributes.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00010: DuplicateRefException. In document {0} there are multiple elements with the same ID {1}.

Cause: Either an element was being added with an ID that already existed within the document, or a preexisting document had multiple elements with the same ID.

Action: Change the ID of the elements so that there is no ID duplication.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00011: unable to create configuration object or MDSInstance due to invalid configuration information: {0}

Cause: The MDS configuration was invalid.

Action: Refer to the MDS specification and correct the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00012: invalid value "{0}" for attribute {1} (type = "{2}") in metadata object {3}

Cause: The value provided for the named attribute was invalid. For example, this error could occur if a named JNDI connection name is incorrect.

Action: Provide a valid attribute value.
Level: 1

Type: ERROR

Impact: Data

MDS-00013: no metadata found for metadata object "{0}"

Cause: MDS was unable to locate the given metadata object.

Action: Confirm the name and location of the metadata object, its existence in the configured metadata stores, and that it is in an accessible namespace.
Level: 1

Type: ERROR

Impact: Data

MDS-00015: Translation ignored in document "{0}": element with localRef "{1}" not found

Cause: A translation could not be applied because the underlying element to be translated was not found.

Action: If the element is expected, check the base document and any customizations to locate it.
Level: 1

Type: ERROR

Impact: Data

MDS-00016: Ignoring customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not finding element with local reference "{4}"

Cause: A customization was not applied because the underlying element to be customized was not found.

Action: If the element is expected, examine the base document and any customizations to locate the element.
Level: 1

Type: ERROR

Impact: Data

MDS-00017: Customization instruction generated for "{0}" uses local reference(s) : "{1}" which is not upgrade safe.

Cause: The customization instruction contained a local reference that was not deemed safe for an upgrade operation.

Action: Ensure that the local reference used in the customization instruction would be safe during an upgrade operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00018: Fixed customization for instruction type "{0}" in metadata object "{1}" for customization layer "{2}"/"{3}": not able to find the referenced element with local reference "{4}", inserted the customized element at the best possible location.

Cause: A customization was fixed because the referenced element was not found.

Action: Correct the customized element's position if needed.
Level: 1

Type: ERROR

Impact: Data

MDS-00019: Customization document contains an invalid instruction "{0}".

Cause: A customization document that was being applied contained an unrecognized instruction.

Action: Retry the operation. If necessary, either remove the customization document, or edit it to correct or remove the offending instruction.
Level: 1

Type: ERROR

Impact: Data

MDS-00020: Layer value "{0}" contains an invalid character.

Cause: Using a layer value that has an invalid character.

Action: Layer value should conform to MDS naming standards.
Level: 1

Type: ERROR

Impact: Data

MDS-00029: Invalid namespace: The namespace "{0}" has not been registered with the MetadataManager.

Cause: An attempt was made to access a document in an unknown location or namespace.

Action: Ensure that the namespace reported is registered in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00032: cannot parse the input file: {0}

Cause: An exception occurred while parsing the file.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Data

MDS-00033: cannot load the input file: {0}

Cause: An exception occurred while loading the file.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Files

MDS-00034: cannot write to the output file: {0}

Cause: An attempt to write to the output file failed.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Files

MDS-00035: cannot load the class: {0}.

Cause: The class file could not be loaded.

Action: Ensure the class is available on the classpath so that it can be loaded by the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00036: cannot instantiate the class: {0}

Cause: An exception occurred while instantiating a class.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00037: cannot access the class: {0}

Cause: An attempt was made to access an inaccessible class file.

Action: Record any accompanying errors and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00039: error while attempting to parse the document {0} using SAX.

Cause: A SAX parsing exception occurred while trying to parse a document.

Action: Record the accompanying error and contact the developers of the application.
Level: 1

Type: ERROR

Impact: Data

MDS-00040: There are no namespaces registered.

Cause: The operation attempted requires at least one registered namespace.

Action: Correct the MDS configuration to include the required namespace schemas.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00041: invalid classpath entry "{0}"

Cause: An entry on the application's classpath did not exist or was invalid.

Action: Correct the application's classpath to remove the invalid entry.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00042: Classpath "{0}" does not contain any valid directories or jar files.

Cause: The application's classpath contained no valid entries.

Action: Correct the application's classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00043: A name pattern mapping for path {0} already exists.

Cause: The MDS configuration had duplicate namespace mappings.

Action: The MDS configuration must be corrected to remove the duplicate namespace mappings.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00044: Metadata for MetadataObject with name {0} already exists in the configured store.

Cause: An attempt was made to create a new Metadata Object. However an object with the same MDSReference already existed.

Action: The name or location of one of the objects must be changed.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00047: Use the flushChanges method on the MDSSession to commit the changes.

Cause: Commit was disabled in the PTransaction that was being used.

Action: Use the flushChanges method on the MDSSession to commit the changes.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00054: The file to be loaded {0} does not exist.

Cause: An attempt was made to load a persistent document using a URL but the underlying document was not found in the store.

Action: Check that the document name is correct and that the store is correctly configured.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00058: Invalid Metadata Path: Metadata Path cannot be null.

Cause: The path used to create a FileMetadataStore was empty. It must point to a directory.

Action: Correct the metadata store definition in the application configuration to specify a metadata path.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00068: Unable to find a type definition for: namespace = {0}, local name = {1}, file location = {2}

Cause: A request was made to locate a definition that did not exist in the named schema.

Action: Ensure the document contains only elements which are defined in the schema for the indicated namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00084: Parameter {0} is invalid.

Cause: The supplied parameter was not of the expected type.

Action: Ensure the parameter is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00085: Parameter {0} is missing.

Cause: The named parameter was not supplied.

Action: Ensure that the named parameter is supplied. If transferring documents ensure a parameter file name is supplied.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00089: Parameter {0} must have a value.

Cause: A required parameter was null.

Action: Ensure that the indicated parameter is not null when the method is called.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00090: Error in JNDI lookup operation on MDSInstance name {0}, JNDI name {1}: object found {2} is an instance of class {3} classloader {4}, expected an instance of class {5} classloader {6}.

Cause: An object of an unexpected type was found, and it was bound to the JNDI context as the MDSInstance.

Action: Make sure no user-written code is binding anything to the same JNDI name. If the error occurs again try restarting the application. If the error still occurs, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00091: Unable to customize {0}, empty or null value for tip customization layer {1}

Cause: The customization layer configured as the tip, has a null or empty value.

Action: Ensure that a valid value is supplied for the tip customization layer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00092: DuplicateNodeException. The same bean instance {0} already exists in document {1}.

Cause: An element was being added that already exists as the same bean instance within the document.

Action: Either create a new bean instance or remove the duplicate before attempting to insert in the document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00093: List of values provided for customization layer {0} was empty or null.

Cause: The list of customization layer values was either empty or null.

Action: Ensure that a valid list of layer values for the customiizaton layer is provided.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00094: List of CustLayerUsage objects provided was empty or null.

Cause: The list of CustLayerUsage objects was either empty or null.

Action: Ensure that a valid list of CustLayerUsage objects is provided.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00095: The support to transfer customization documents based on the CustConfig and excluding customization documents of specific customization layers is not yet available.

Cause: CustOption is created to transfer customization documents based on the CustConfig and to exclude customization documents of specific customization layers which is not yet supported in MDS Transfer.

Action: Ensure CustOption is not created to use CustConfig and to exclude customization documents of specific sutomization layers.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00111: The value of the property {0} for the component {1} must be set to the default value.

Cause: The indicated component property did not have a default value.

Action: Ensure the component property is given a default value.
Level: 1

Type: ERROR

Impact: Data

MDS-00153: invalid value for indicator

Cause: The production of merged XML failed.

Action: Verify the validity of XML documents and any schemas. If necessary forward these on to Oracle Support Services with the exception message and stack trace.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

MDS-00154: The ContentHandler {0} does not implement org.xml.sax.ext.LexicalHandler.

Cause: MergedXML was passed a ContentHandler that does not implement org.xml.sax.ext.LexicalHandler.

Action: Use a ContentHandler that implements org.xml.sax.ext.LexicalHandler.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00155: unable to create a JSP file for document {0}

Cause: Oracle MDS was unable to create a JSP source document.

Action: Examine the MDS base document, as well as any customizations and translations. If necessary, forward these to Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Files

MDS-00156: unable to create a JSP output directory {0}

Cause: MDS-JSP integration failed because a problem was encountered while creating a directory.

Action: Verify that you have permission to create this directory.
Level: 1

Type: ERROR

Impact: Files

MDS-00157: unable to write to JSP file {0}

Cause: MDS-JSP integration failed because a problem was encountered while trying to write to a file.

Action: Verify that you have permission to create this file.
Level: 1

Type: ERROR

Impact: Files

MDS-00158: invalid directory: {0}

Cause: MDS-JSP integration failed. An attempt was made to write to an invalid directory.

Action: Verify the value of the invalid directory.
Level: 1

Type: ERROR

Impact: Files

MDS-00159: Invalid value "{0}" for {1} attribute (type = "{2}") in document {4}.

Cause: An attempt was made to write an invalid value to an attribute.

Action: Double-check the value and attribute type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00160: no local name has been specified for a resource

Cause: An attempt was made to create a resource without giving it a name.

Action: Verify that the resource that was created is given a local name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00161: no local name has been specified

Cause: An attempt was made to create a resource without giving it a local name.

Action: Verify that the resource that was created is given a local name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00162: invalid attribute value

Cause: An attempt was made to give to an invalid value to an attribute.

Action: Verify that the attribute has a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00163: property value missing from element

Cause: An element was missing a property value.

Action: Ensure that each parameter used to create the element has a property value.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00164: There is a concurrent "{1}" operation on the document "{0}".

Cause: The document on which modification was being attempted had been updated by another user after it was retrieved.

Action: Retrieve the document again.
Level: 1

Type: ERROR

Impact: Data

MDS-00165: metadata Object "{0}" has changed

Cause: The creation, updating, or renaming of a metadata object failed due to conflicting changes made by another user.

Action: Retrieve the document containing the metadata object again.
Level: 1

Type: ERROR

Impact: Data

MDS-00166: unable to locate the unique identifier, {0}:{1}, that has been configured for the element {2}

Cause: The element that required a unique identifier was created without one.

Action: Add a unique identifier attribute to the element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00167: Invalid local name for mapping "{0}" - an empty string is not allowed.

Cause: A local name was given a null or empty value.

Action: Supply a valid local name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00168: MDS object {0} is being used after it or its MDSInstance or PManager has been released.

Cause: An MDS object was used after it or its MDSInstance or PManager had been released

Action: Create a new MDSInstance and re-create the MDS object.
Level: 1

Type: ERROR

Impact: Session

MDS-00169: The MDS instance is not ready for use because metadata deployment is in progress (status is "{0}"). Deployment messages so far are: "{1}".

Cause: The MDS instance cannot be used until metadata deployment has finished.

Action: Try again later after metadata deployment has completed.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00170: The MDS instance is not usable because metadata deployment failed with status "{0}".

Cause: Metadata deployment failed with the given status.

Action: Please fix the error and redeploy the application's metadata using the importMAR operation on MDS Application Runtime MBean. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00171: Document "{0}" already has unsaved updates on another instance of this metadata object in this session.

Cause: An attempt was made to update metadata using more than one instance of the same metadata object at the same time in the same session.

Action: Save the changes on the metadata object that already has updates before attempting to update it via another metadata object, or make further modifications on the metadata object on which updates have already been made.
Level: 1

Type: ERROR

Impact: Data

MDS-00172: The value "{0}" of local unique attribute {1} on the {2} element that is being inserted or updated in document {3}, is already used by a sibling element.

Cause: An attempt was made to have two local unique attributes with the same value on elements that share the same parent.

Action: Use a different value for the local unique attribute on the element that is being inserted or updated.
Level: 1

Type: ERROR

Impact: Data

MDS-00173: Attribute {0} of element {1} in document {2} has a null value.

Cause: The value of the named attribute was null.

Action: Provide a non-null value for the attribute or remove the attribute.
Level: 1

Type: ERROR

Impact: Data

MDS-00174: A tenant scoped MDSInstance {0} is being requested with a null TenantId.

Cause: A tenant scoped MDSInstance was requested passing null for TenantId.

Action: Supply a non null TenantId or request an unscoped MDSInstance.
Level: 1

Type: ERROR

Impact: Session

MDS-00176: The operation on MDSInstance {0} cannot be performed as it is not tenant scoped.

Cause: The operation performed on the MDSInstance was invalid with a TenantId because it was not a tenant scoped MDSInstance.

Action: Perform the operation on an MDSInstance initialized for multitenant operation.
Level: 1

Type: ERROR

Impact: Session

MDS-00177: The operation on resource {0} cannot be performed as it is not configured to be owned by the current tenant scope.

Cause: The operation performed was illegal as the resource being created, updated or deleted has global scope and the current scope is tenant or the resource has tenant scope and the current tenant is global.

Action: Check that the configuration of the namespaces and CustomizationClasses is correct and that the correct customization class list is being used.
Level: 1

Type: ERROR

Impact: Session

MDS-00178: Multitenant MDSInstance {0} cannot be created with TenantId {1} when multitenant-capable in the persistence configuration = {2} and the JVM flag oracle.multitenant.enabled = {3}.

Cause: A valid TenantId was not provided appropriate to the configuration.

Action: Request an MDSInstance appropriate to the configuration.
Level: 1

Type: ERROR

Impact: Session

MDS-00179: The requested MDSInstance {0} cannot be returned for TenantId {1} as it was originally created with multitenant enabled = {2}.

Cause: The configuration at the time the MDS Instance was requested did not match with the configuration when it was originally created.

Action: Request an MDSinstance appropriate to the original configuration.
Level: 1

Type: ERROR

Impact: Session

MDS-00180: Only a single tenant cache configuration is allowed.

Cause: The number of TenantCacheConfigs was not 1.

Action: Pass a single tenant cache configuration object. Although the constructor for the TenantCacheConfigs class takes an array this is reserved for future use.
Level: 1

Type: ERROR

Impact: Session

MDS-00181: Only a single tenant document cache configuration is allowed.

Cause: The number of TenantDocumentCacheConfigs was not 1.

Action: Pass a single tenant document cache configuration object. Although the constructor for the TenantDocumentCacheConfigs class takes an array this is reserved for future use.
Level: 1

Type: ERROR

Impact: Session

MDS-00182: Tenant cache configuration information cannot be requested for the global tenant.

Cause: Tenant cache configuration information was being requested for the global tenant.

Action: Do not request the tenant cache configuration for the global tenant - use getCacheConfig directly from MDSConfig
Level: 1

Type: ERROR

Impact: Session

MDS-00183: Tenant document cache configuration information cannot be requested for the global tenant.

Cause: Multitenant document cache information was being requested for the global tenant.

Action: Do not request the tenant document cache configuration for the global tenant - use getDocumentCacheConfig from NamespaceConfig
Level: 1

Type: ERROR

Impact: Session

MDS-00184: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with cascade delete enabled.

Cause: Relationships with cascade delete enabled were spanning tenant boundaries.

Action: Reconfigure the relationship with cascade delete disabled or ensure the parent reference is within the same tenant scope.
Level: 1

Type: ERROR

Impact: Session

MDS-00185: The relationship from {0} to {1} is invalid because the latter is configured as a global resource and cannot be referenced from a tenant resource because the corresponding relationship is defined with enforced integrity.

Cause: Relationships with defined referential integrity were spanning tenant boundaries.

Action: Reconfigure the relationship without referential integrity or ensure the parent reference is within the same tenant scope.
Level: 1

Type: ERROR

Impact: Session

MDS-00186: A {0} element is already present in the parent {1} element in document {2}, but with the QNameLUID identification mechanism only one is allowed.

Cause: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.

Action: Remove duplicate instances of elements with same QName
Level: 1

Type: ERROR

Impact: Data

MDS-00187: The existing {0} element in the parent {1} element in document {2} is automatically removed, and new customized {0} element of "{3}"/"{4}" customization layer is inserted since with the QNameLUID identification mechanism, only one is allowed.

Cause: An attempt was made to have two or more elements with same QName under same parent while QNameLUID identification mechanism is used.

Action: Removed duplicate instances of elements with same QName
Level: 1

Type: ERROR

Impact: Data

MDS-00188: The relationship from {0} to {1} is invalid because the latter is configured as a tenant resource and cannot be referenced from a global resource.

Cause: An attempt was made to reference a tenant resource from a global resource.

Action: Ensure all references from global resources are also global.
Level: 1

Type: ERROR

Impact: Session

MDS-00189: The existing {0} element with unique id {1} in the parent {2} element in document {3} is automatically removed, and new customized {0} element with unique id {1} of "{4}"/"{5}" customization layer is inserted since {0} element is type-annotated to overwrite duplicates.

Cause: An attempt was made to have two or more elements with same QName under same parent having the same unique ID value while overwriteDuplicate mechanism is used.

Action: Removed duplicate instances of elements with same QName having the same unique ID value
Level: 1

Type: ERROR

Impact: Data

MDS-00190: A call to {0} on the current MDSSession does not specify the correct transaction key

Cause: The current MDS Session was created using a transaction key and the subsequent operation was either being attempted passing no key or a different one from that originally used.

Action: If the MDS Session is created using a transaction key, then use the MDSSession API's that take a transaction key and use the same key.
Level: 1

Type: ERROR

Impact: Session

MDS-00191: An exception occured in PChangeListener {0}

Cause: The MetadataStoreCommunicator was attempting to notify the listener when an exception ocurred.

Action: Check the HandlePChanges method of the listener.
Level: 1

Type: ERROR

Impact: Session

MDS-00192: Validation of {0} caused a NullPointerException: check there is an MDS bean object set on the MDS bean MO

Cause: This error most typically occurs when a Bean MO has been created but no bean object has been set on it.

Action: Check that an MDS bean is set on this MO. Failing that, examine the stack for clues for alternative causes.
Level: 1

Type: ERROR

Impact: Data

MDS-00193: Document with the MDSReference {0} contains an ID attribute with an invalid value: {1}

Cause: The value of the ID attribute is invalid according to the schema definition.

Action: Ensure that the ID conforms to the schema definition .
Level: 1

Type: WARNING

Impact: Data

MDS-00194: Auditing is disabled for component {0}.

Cause: There was an error registering the audit event definition(s) for the component.

Action: Ensure that the audit event definitions for the component are valid and that the audit service is functional.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-00195: The custom audit event of type "{0}" that was associated with "{1}" is not audited because the MDS object was unmodified since the last time the changes in the MDSSession were committed.

Cause: MDS object associated with the event was unmodified since the last time the changes in the MDSSession were committed. A custom audit event is discarded if the associated MDSObject is not modified.

Action: No action required.
Level: 1

Type: WARNING

Impact: Programmatic

MDS-00196: The MDSSession referenced by the audit component "{0}" is invalid.

Cause: The MDS audit support instance is being used even after the MDSSession that was used to created it is no longer referenced.

Action: Fetch the audit support instance from the MDSSession and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00197: An internal error occurred when processing MetadataObject {0} with cache key {1}.

Cause: An error occurred in the LayeredCache processing.

Action: Check for log messages. If the problem persists, clear the MDS cache and contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Session

MDS-00198: The requested object is deleted in the current PTransaction

Cause: The requested document was deleted in an earlier part of the PTransaction and not replaced.

Action: Review whether the document needed to be deleted or replace with a new version.
Level: 1

Type: ERROR

Impact: Data

MDS-00199: The requested object is deleted in the current MDSSession

Cause: The requested document was deleted in an earlier part of the MDSSession and not replaced.

Action: Review whether the document needed to be deleted or replace with a new version.
Level: 1

Type: ERROR

Impact: Data

MDS-00200: Reference not found in Document

Cause: Unable to locate the reference within the named Metadata Object.

Action: Check that the reference is correct.
Level: 1

Type: ERROR

Impact: Data

MDS-00201: PDocument not found in MetadataStore : {0}

Cause: The requested persistence document was not found in the given MetadataStore.

Action: Check that the requested name is correct and that the store is mapped to the namespace correctly .
Level: 1

Type: ERROR

Impact: Data

MDS-00202: The Document was not found on the classpath

Cause: The requested document was not found on the classpath.

Action: Check that the document is available on the classpath as a resource .
Level: 1

Type: ERROR

Impact: Data

MDS-00500: No metadata store is configured to save the document {0}.

Cause: An attempt was made to save a document, when no writable store was configured.

Action: Provide a writable metadata store to save the document.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00501: Document {0} cannot be deleted because no metadata store is configured.

Cause: An attempt to delete a document failed because there was no writable store configured.

Action: To delete the document, provide a writable metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00503: The metadata path "{0}" does not contain any valid directories.

Cause: Either the metadata path was empty or directories on the metadata path did not exist.

Action: Ensure that the metadata path is not empty and that the directories on the metadata path exist.
Level: 1

Type: ERROR

Impact: Data

MDS-00504: failure to create document {0} because metadata store "{1}" is read-only

Cause: An attempt to create a document on a read-only metadata store failed.

Action: To create the document, provide a writable metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-00505: failure to save document {0} because metadata store "{1}" is read-only

Cause: An attempt to save a document to a read-only metadata store failed.

Action: To save the document, provide a writable metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-00506: failure to get child resources of package {0} because package does not exist in metadata store

Cause: Child resources for the package were not found because specified package did not exist in the metadata store.

Action: Verify that the package exists in the metadata store, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00507: failure to delete document {0} because metadata store "{1}" is read-only

Cause: An attempt to delete a document from a read-only metadata store failed.

Action: To delete the document, provide a writable metadata store and retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00508: There is no content to be read for {0}.

Cause: An attempt was made to read empty metadata.

Action: Verify that the metadata has valid content, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00509: failure to delete document {0} with file {1}

Cause: An error occurred while the document was being deleted.

Action: Verify that the document exists and then retry the operation, or provide a document that exists in the store.
Level: 1

Type: ERROR

Impact: Data

MDS-00510: failure to read document {0} because it is not found in the metadata path "{1}"

Cause: The document to be read was not found.

Action: Verify that the metadata path is correct and that the document exists in the metadata path.
Level: 1

Type: ERROR

Impact: Data

MDS-00511: failure to create document {0} at file {1}

Cause: An error occurred while creating the document in the file store.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Files

MDS-00512: failure to create document {0} because file {1} already exists

Cause: An attempt was made to create a file that already existed in the metadata store.

Action: Provide a different name for the file to be created, or delete the existing file first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Files

MDS-00513: failure to create package {0} because directory {1} already exists

Cause: An attempt to create a package failed because a directory by the same name already existed.

Action: Provide a different name for the package to be created and retry the operation.
Level: 1

Type: ERROR

Impact: Files

MDS-00514: failure to save document {0} to file {1}

Cause: An error occurred while saving the document to a file.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Files

MDS-00515: failure to create document {0} in the metadata repository

Cause: An error occurred while the document was being created in the metadata repository.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00516: failure to create document {0} because it already exists in the metadata repository

Cause: An error occurred while the document was being created in the metadata repository because the document already existed.

Action: Provide a different name or delete the existing document first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00517: failure to create package {0} because it already exists in the metadata repository

Cause: An error occurred while the package was being created in the metadata repository because the package already existed.

Action: Provide a different package name or delete the existing package first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00518: failure to create package {0} in the metadata repository

Cause: An error occurred while the package was being created in the metadata repository.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00519: failure to delete document {0} from the metadata repository

Cause: An error occurred while the document was being deleted from the metadata repository.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00520: failure to read document {0} because it is not in the metadata repository

Cause: The document was not read because it did not exist in the metadata repository.

Action: Verify that the document name is correct and that it exists in the metadata repository, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00521: error while reading document {0} from metadata repository

Cause: An error occurred while the document was being read from the metadata repository.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00522: failure to save document {0} to the metadata repository

Cause: An error occurred while the document was being saved to the metadata repository.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00526: failure to generate SAX parsing events for document {0}

Cause: An error occurred while parsing the XML document.

Action: Verify that the XML document is well-formed. Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00531: failure to write to "{0}" because output to "{1}:" protocol is not supported

Cause: An attempt to write modified metadata to a URL failed because the protocol is not supported.

Action: Retry writing modified metadata to a supported protocol.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00533: Exception: {3} Attribute "{0}" with an invalid MDS reference "{1}" in document "{2}" is not stored as a typed dependency in the database repository.

Cause: An error occurred while adding a typed dependency from the specified attribute.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00534: Exception: {3} Subobject {0} in document {2} has invalid value "{1}" for unique identifier; typed dependencies from this subobject are not stored in the database repository.

Cause: An error occurred because the component had an invalid ID.

Action: Provide the correct ID value for the application metadata. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00535: cannot change TypeManager associated with a PManager after it is initialized

Cause: An attempt was made to associate TypeManager with PManager after it was initialized.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00536: cannot change FileTypeManager associated with a PManager after it is initialized

Cause: An attempt was made to associate FileTypeManager with PManager after it was initialized.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-00537: unable to rename {0} to {1}

Cause: An error occurred during a rename operation.

Action: Retry the rename operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00538: failure to rename document {0} because metadata store "{1}" is read-only

Cause: An error occurred during rename operation because the metadata store was configured as read-only.

Action: To rename a document, provide a store that can be written to, that is not read-only.
Level: 1

Type: ERROR

Impact: Data

MDS-00539: A document can be renamed only within its source store. The new name {1} in this rename operation does not map to the same store as the old name {0}.

Cause: An error occurred during a rename operation. An invalid new name for the rename operation caused the renamed document to be stored in another metadata store.

Action: Provide a new, valid document name that maps to the same metadata store that contains the original document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00541: SAX events cannot be generated for non-XML document {0}.

Cause: An attempt was made to generate SAX events for non-XML documents.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00547: The read operation is not supported for packages from Web content from the servlet context.

Cause: A read operation was attempted for packages from Web content, which is not supported.

Action: The read operation is not supported, therefore no action is required.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00550: Updates across multiple stores are not allowed in the same transaction.

Cause: An attempt was made to perform updates across multiple stores in the same transaction.

Action: Verify that the document is being saved to the same store on which it exists.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00551: failure to delete package {0} because it is not empty

Cause: An attempt was made to delete a package that was not empty.

Action: Delete the contents of the package to be deleted first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00552: failure to delete package {0} with directory {1}

Cause: An error occurred while deleting the directory for the package.

Action: Ensure no files from the directory are opened in other applications and retry the operation. Also, refer to the error messages in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Files

MDS-00554: Package {0} cannot be found in the specified store.

Cause: The requested operation was not completed because the package name that was supplied was invalid.

Action: Provide a valid package name and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00555: The partitionName {0} is invalid.

Cause: The requested operation was not completed because the partition name that was supplied was invalid.

Action: Provide a valid partition name and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00557: Resource {0} is already locked or is being modified.

Cause: An attempt was made to modify a document that was already being modified by another user.

Action: Retry modifying the document after the lock is released by the other users. Also, refer to the error messages in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Session

MDS-00558: The partitionName {0} is not available.

Cause: No partition with that name existed.

Action: Provide a partition name that exists.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00559: A partition with name {0} already exists.

Cause: The name provided for creating a new partition was already in use by another partition.

Action: Provide a different name for the new partition.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00560: The MDS repository is incompatible with the archive. The repository version is {0} whereas archive version is {1}.

Cause: The MDS repository was not compatible with the archive provided.

Action: Upgrade the target MDS repository or use a compatible archive for the operation.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00561: The create operation is not supported for metadata stores of type "{0}".

Cause: An attempt was made to create a new document or package in a read-only metadata store.

Action: Reconfigure the application to use a writable metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00562: The delete operation is not supported for metadata stores of type "{0}".

Cause: An attempt was made to delete a document from a read-only metadata store.

Action: Reconfigure the application to use a writable metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00563: The save operation is not supported for metadata stores of type "{0}".

Cause: An attempt was made to save a document to a read-only metadata store.

Action: Reconfigure the application to use a writable metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00564: GUID feature is not supported for metadata stores of type "{0}".

Cause: An attempt was made to get a document by GUID from a metadata store that does not support GUIDs.

Action: Reconfigure the application to use a metadata store that supports GUIDs, such as DBMetadataStore.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00565: The rename operation is not supported for metadata stores of type "{0}".

Cause: An attempt was made to rename a document or package in a read-only store.

Action: Reconfigure the application to use a writable metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00566: The DOM content is NULL for {0}.

Cause: DOM document content provided was null.

Action: Provide valid DOM content and retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00567: The metadata changes for document "{0}" cannot be written in the underlying store because read-only mode is enabled in the configuration.

Cause: An attempt to change metadata was made while changes were disabled for maintenance operations.

Action: Reconfigure the application to not specify read-only mode in the configuration and use a writable metadata store to persist metadata changes.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00568: MetadataStore initialization failure because "{0}" is invalid

Cause: The URL store mapping was invalid.

Action: Provide a valid URL store mapping.
Level: 1

Type: ERROR

Impact: Files

MDS-00569: unable to read document {0} from "{1}"

Cause: There was an error reading the document from the URL metadata store.

Action: Retry the operation. If the problem persists, verify that the URL metadata store exists.
Level: 1

Type: ERROR

Impact: Data

MDS-00570: The name or content exceeds the MDS repository schema size for {0}.

Cause: The metadata name or the content exceeded the schema size.

Action: Reduce the length of the metadata name or content, and then retry the operation. Refer to the documentation for the allowed sizes for names and content.
Level: 1

Type: ERROR

Impact: Data

MDS-00571: The bean content is NULL for {0}.

Cause: The bean content was null.

Action: Provide valid bean content, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00572: failure to get the ConnectionManager because the DBContext is null

Cause: The DBContext value is null. Also, using any MetadataStore, PManager, or MDSInstance that has already been released might lead to this error.

Action: Do not use any metadata store, PManager, or MDSInstance that is already released.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00573: The metadata store is already associated with a PManager.

Cause: The PConfig provided for creating the PManager or MDSInstance was already used by another PManager or MDSInstance.

Action: Provide a new PConfig when creating the PManager or MDSInstance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00574: The document {0} does not exist in the configured metadata store.

Cause: The document being locked did not exist in the configured metadata store.

Action: Ensure that the document to be locked exists, and that the name of the document is correct.
Level: 1

Type: ERROR

Impact: Data

MDS-00575: failure to acquire write lock for {0}

Cause: An attempt to acquire a write lock for a document failed.

Action: Refer to the cause exception message in application logs for details on the actual cause of the failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00576: failure to process {0} because metadata store "{1}" is read-only

Cause: An attempt was made to modify metadata in a read-only metadata store.

Action: Provide a writable metadata store to allow modification of the document.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00577: Could not acquire read/write lock for {0} within the default waiting time interval

Cause: Read/Write lock could not be obtained for a file within the waiting time interval.

Action: Try the operation again after some time.
Level: 1

Type: ERROR

Impact: Files

MDS-00578: Failed to process document {0} due to a critical error writing to the repository

Cause: A critical error occurred while the metadata document was being written to the repository.

Action: Contact the application administrator with cause exception message details to resolve the repository error.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00579: The document {0} does not have version {1} in the repository.

Cause: Specified version does not exist for the document.

Action: Provide an existing version for the document.
Level: 1

Type: ERROR

Impact: Data

MDS-00580: operation failed for {0} because no metadata-store was defined in the configuration for metadata-store-usage {0}.

Cause: incomplete configuration, no metadata-store was defined for the metadata-store-usage

Action: Define the metadataStore for the empty metadata-store-usage.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00581: error deleting partition {0} in file repository {1}

Cause: The directory represented by the file repository or partition is read only.

Action: Verify that the metadata path to the repository and partition exist and are writable.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00582: The MetadataStore {0} is writable but does override getMetadataStoreCommunicator() method.

Cause: Configuration used a MetadataStore that was writable but not supporting MetadataStoreCommunicator interface.

Action: Override getMetadataStoreCommunicator() in the MetadataStore class to return an appropriate MetadataStoreCommunicator instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00583: Could not release read/write lock for {0} because the lock was not found.

Cause: Read/Write lock could not be released because it was already removed from the lock cache.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Files

MDS-00584: The MDS repository's database platform is different that of the archive. The repository's database platform is {1} whereas the archive's platform is {0}.

Cause: The MDS repository platform was not compatible with the archive provided.

Action: Use a platform compatible archive for the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00585: Failure to create deployment lineage because metadata store "{0}" is read-only

Cause: An attempt was made to create deployment lineage in a read-only metadata store. Deployment lineage in repository represents Application name and MAR module name.

Action: Configure a metadata store that supports deployment management, typically a DBMetadataStore.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00586: ArchiveMetadataStore is restrcited to be used with MDS Transfer operation only. Reading or writing files in ArchiveMetadataStore is not supported ouside of transfer.

Cause: An attempt was made to read or write files in ArchiveMetadataStore outside of transfer.

Action: ArchiveMetadataStore is not supported outside of transfer. Either use this ArchiveMetadataStore for MDS transfer operation or use some other MetadataStore to store your files.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00588: Cannot replace the original archive file {0} with the final archive file {1} because the final archive file could not be renamed to {0}.

Cause: The final archive file could not be renamed to the original archive file name.

Action: Look at the cause exception for more details and take corresponding actions.
Level: 1

Type: ERROR

Impact: Data

MDS-00589: Error occurred while creating the final archive file {0}.

Cause: Some exception occurred while creating the final archive.

Action: Look at the cause exception for more details and take corresponding actions.
Level: 1

Type: ERROR

Impact: Data

MDS-00590: Error occurred while opening or closing the input/output stream for archive file {0}.

Cause: Some exception occurred while opening or closing the inpu/output stream for archive file.

Action: Look at the cause exception for more details and take corresponding actions.
Level: 1

Type: ERROR

Impact: Data

MDS-00591: "{0}" operation is not supported in ArchiveMetadataStore.

Cause: An unsupported operation has been attempted in ArchiveMetadataStore.

Action: Look at the ArchiveMetadataStore javadoc for supported operations.
Level: 1

Type: ERROR

Impact: Data

MDS-00592: Error occurred while initializing FileMetadataStore connection for the temporary directory.

Cause: An error occurred while initializing the FileMetadataStore connection for the temporary directory.

Action: Look at the cause exception for more details and take corresponding actions.
Level: 1

Type: ERROR

Impact: Data

MDS-00593: Unable to read the file {0} from archive {1}.

Cause: Some I/O Exception occurred while reading the given file from archive.

Action: Look at the cause exception for more details and take corresponding actions.
Level: 1

Type: ERROR

Impact: Data

MDS-00594: Unable to write the file {0} to archive {1}.

Cause: Some I/O Exception occurred while writing the given file to archive.

Action: Look at the cause exception for more details and take corresponding actions.
Level: 1

Type: ERROR

Impact: Data

MDS-00595: The parent directory {0} given in archive file path does not exist. Cannot create ArchiveMetadataStore for the archive file {1}.

Cause: The parent directory mentioned in archive file path does not exist.

Action: Provide valid parent directory in archive file path to create ArchiveMetadataStore.
Level: 1

Type: ERROR

Impact: Data

MDS-00596: Failure to read document {0} because it is not found in "{1}"

Cause: The document to be read was not found.

Action: Verify that the document exists in the ArchiveMetadataStore before reading the document.
Level: 1

Type: ERROR

Impact: Data

MDS-00597: Failure to open the archive file {0}. Cannot create ArchiveMetadataStore for the archive file {0}.

Cause: Could not open the given archive file.

Action: Try creating ArchiveMetadata store with a valid archive file.
Level: 1

Type: ERROR

Impact: Data

MDS-00598: Cannot create an intermediary archive during export to the archive file {0}.

Cause: Either the intermediary archive file could not be created in the default temporary-file directory or an I/O error occured.

Action: Look at the cause exception for more details and take action accordingly.
Level: 1

Type: ERROR

Impact: Data

MDS-00599: Cannot obtain a connection to the Archive Metadata Store for archive file {0}.

Cause: There was a problem obtaining a connection to the Archive Metadata Store.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00601: The XLIFF document has invalid target language {0}.

Cause: The target language specified was either null or empty.

Action: Specify a valid target language and retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00703: The name {0} is not a valid name under package {1} because {2} resource not considered child of the package.

Cause: A specified child resource was not a child of the package.

Action: Specify a valid child resource name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Data

MDS-00704: invalid value {0} for property {1} on component {2}

Cause: An invalid property value was provided.

Action: Provide a valid property value and retry.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00771: A component with {0} "{1}" already exists.

Cause: The specified component already existed.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00907: unable to save document "{0}" because either a document or package of the same name already exists

Cause: A document or package with the same name already existed in the repository, perhaps because it was just created by another user.

Action: Retry the operation. If necessary, choose another name for the object being saved.
Level: 1

Type: ERROR

Impact: Data

MDS-00908: unable to create package "{0}" because a document or package of the same name already exists

Cause: A document or package with the same name already existed in the repository, perhaps because it was just created by another user.

Action: Retry the operation. If necessary choose another name for the object being saved.
Level: 1

Type: ERROR

Impact: Data

MDS-00910: unable to save the document because of corrupt MDS database sequences or other internal errors.

Cause: The database sequence used for generating the unique document ID was corrupt or some other internal errors caused violation of unique constraints.

Action: Retry the operation after deploying metadata to another MDS database repository partition. If that still fails, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

MDS-00911: Document with name "{0}" and version {1} [Low CN={2}, High CN={3}] does not exist in the repository.

Cause: The document was not found in the MDS repository.

Action: Specify a correct name for the document and retry the operation. Check if the document is deleted by another user.
Level: 1

Type: ERROR

Impact: Data

MDS-00912: MDS repository is incompatible with the middle tier. Repository version "{0}" is older than minimum repository version "{1}" required.

Cause: The MDS repository was older than minimum version required by the middle tier.

Action: Upgrade the MDS repository to the required version.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00913: MDS repository is incompatible with the middle tier. MDS version "{0}" is older than minimum MDS version "{1}".

Cause: The MDS version was older than the minimum required version for using the MDS repository.

Action: Upgrade the MDS library to the required version.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00914: unable to save document "{0}" because either an already deleted document or package with conflicting name or type already exists

Cause: A document or package with the same name or a parent pacakge of incorrect type already existed in the repository as a deleted version.

Action: Delete the coflicting resource from repository or check if the new resource is invalid. If necessary, choose another name for the object being saved.
Level: 1

Type: ERROR

Impact: Data

MDS-00915: MDS repository is incompatible with the middle tier for dumping or restoring metadata.

Cause: The MDS repository was older than minimum version required by the middle tier to dump or restore metadata.

Action: Retry the operation after upgrading the MDS repository to newer version or use compatible middle tier to perform the operation.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00916: MetadataStore configured for {0} does not support deployment management.

Cause: The metadata store configured for the resource did not support deployment management.

Action: Deployment management is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00918: Connection details for the MDS repository are incomplete. The values for "{0}" are invalid

Cause: The MDS repository connection details were invalid or missing.

Action: Specify correct values for the MDS repository details in the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00919: Internal error: The database context for this repository appears to be corrupt.

Cause: The database context was invalid.

Action: Verify that the repository details are correct in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00922: The ConnectionManager "{0}" cannot be instantiated.

Cause: There was an error instantiating the ConnnectionManager class

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-00923: Unable to create sandbox "{0}"

Cause: An error occurred during creation of sandbox.

Action: Look in the error message log for the exact reason for the failure.
Level: 1

Type: ERROR

Impact: Data

MDS-00928: Invalid document reference, package "cust" should appear before package "trans" in the names of customization translation documents.

Cause: An internal MDS document (one in package mdssys) was found with an invalid name, or an attempt was made to create a name object with such an invalid name.

Action: Avoid using package or document names containing path element "mdssys" which is reserved for internal MDS use. If necessary, remove such invalid documents from the metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-00929: unable to look up name "{0}" in JNDI context

Cause: The implementation class to use for initial context was not found.

Action: Verify that environment properties are configured using system properties or application resources files.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00930: The JNDI location details for the registered datasource are incomplete.

Cause: JNDI location details were found to be incomplete.

Action: Provide complete JNDI location information in the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00931: The database version is {0}.{1}, but MDS requires at least {2}.{3}.

Cause: The database version is older than the minimum database version required for hosting MDS repository.

Action: Upgrade the database to the minimum required version. Contact the database administrator for assistance.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-00932: unknown database vendor {0}

Cause: The database vendor could not be identified.

Action: Verify that the MDS repository is hosted on supported database vendors.
Level: 1

Type: ERROR

Impact: Installation

MDS-00933: cannot create data source using URL "{0}"

Cause: An error occurred while creating the data source using the specified URL.

Action: Verify that the URL specified is correct and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-00934: XDB is not supported on database platform {0}.

Cause: An attempt was made to store XML metadata in a non-XDB database.

Action: Verify that the correct MDS repository is being used.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-00935: Unable to complete operation even after maximum connection retries ({0}).

Cause: An error occurred while performing operation.

Action: Ensure that the database is running. Retry the operation later.
Level: 1

Type: ERROR

Impact: High Availability

MDS-00936: Fast Connection Failover is not supported on the underlying database connection ({0}).

Cause: The underlying database connection did not support fast connection failover, and retry-connection was set to true in either the config file, or programmatically.

Action: Either stop and then restart the database connection and configure it to allow fast connection failover, or do not attempt to set retry-connection to true.
Level: 1

Type: ERROR

Impact: High Availability

MDS-00937: A local transaction operation like commit or rollback cannot be used in a global transaction on connection "{0}".

Cause: The database connection was configured for global transactions, but MDS was not configured to support global transactions.

Action: Reconfigure the database connection to use local transactions. Change "tx-level" attribute on the MDS datasource to "local".
Level: 1

Type: ERROR

Impact: Configuration

MDS-00938: Unable to get an ADF library class loader

Cause: MDS expects to retrieve a resource from an ADF library, but is unable to obtain an ADF library classloader.

Action: Consider whether the resource should be repackaged in an ADF library rather than an ordinary jar.
Level: 1

Type: ERROR

Impact: Data

MDS-01059: document with the name {0} missing in the source metadata store

Cause: The document to be transferred did not exist in the source metadata store.

Action: Verify that the document name is correct, and that it exists in the source metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01061: Listener {0} cannot be instantiated.

Cause: The listener class did not exist.

Action: Verify that the name of the listener class is correct. Ensure that the class is available on the class path.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01104: finding no documents for processing that match the pattern provided

Cause: No documents were found on the source metadata store that matched the pattern provided, or that matched the document name.

Action: Provide another pattern or document name, or provide another metadata store in which to look for the documents.
Level: 1

Type: ERROR

Impact: Data

MDS-01105: invalid label {0}

Cause: The label specified for the source metadata store did not exist.

Action: Verify that the label name is correct, or provide a label that exists in the source metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01106: The TransferTypeRestriction {0} can not be associated with given TransferType {1}.

Cause: The given TransferTypeRestriction can not be associated with the specified TransferType.

Action: Ensure that given TransferTypeRestriction is valid for the specified TransferType.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01107: Post transfer label cannot be created in target store.

Cause: Post transfer label cannot be created in the target store. Examine the cause exception messages to find the root cause of it.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01108: TransferType cannot be null for ExtendedTransferType.

Cause: TransferType provided to create ExtendedTransferType was null.

Action: Provide valid TransferType to create ExtendedTransferType.
Level: 1

Type: ERROR

Impact: Data

MDS-01109: The target archive configured in ArchiveMetadataStore already exists. Cannot export the documents into an existing archive file.

Cause: The target archive already exists. Exporting the documents into an existing archive is not allowed.

Action: Export the documents into a non existing archive file.
Level: 1

Type: ERROR

Impact: Data

MDS-01110: Sandbox export operation allowed only from a database metadata store to an archive metadata store.

Cause: Either source metadata store is not a database or the target metadata store is not an archive in sandbox export operation.

Action: Configure source metadata store to be a database and target metadata store to be an archive in sandbox export operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01111: Sandbox import operation allowed only from Archive Metadata Store to a Database Metadata store.

Cause: Either source metadata store is not an archive metadata store or the target metadata store is not a database in sandbox import operation.

Action: Configure source metadata store to be an archive metadata store and target metadata store to be a database in sandbox import operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01112: Transfer unit list in a Sandbox export/import operation should have atleast one transfer unit.

Cause: Transfer unit list in Sandbox export/import operation empty.

Action: Ensure that there is at least one transfer unit to be transferred in sandbox export/import operation.
Level: 1

Type: ERROR

Impact: Data

MDS-01113: Sandbox metadata file required for import to a new sandbox operation.

Cause: Sandbox metadata file missing in source Archive metadata store in import to a new sandbox operation.

Action: Import to a new sandbox only from an archive store whose contents were exported from a sandbox and contain sandbox metadata document.
Level: 1

Type: ERROR

Impact: Data

MDS-01114: Sandbox with same name as the one imported in a sandbox import operation exists on the target metadata store.

Cause: Sandbox with same name already exists on the target metadata store and the flag to force creation of sandbox is not set to true.

Action: Pass true for forceSBCreation to TransferParams.createForSandboxImport() or destroy sandbox already existing with same name on the target metadata store in sandbox import operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01115: Source sandbox in a sandbox export operation does not contain metadata.

Cause: Source sandbox in export operation was not created with metadata.

Action: Export from a Sandbox that was created with metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01116: Existing target sandbox in import operation does not contain metadata.

Cause: Target sandbox in an import into an existing sandbox operation was not created with metadata.

Action: Import into an existing sandbox that was created with metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01117: Sandbox archive imported into an existing sandbox.

Cause: The archive imported into an existing sandbox contains sandbox metadata.

Action: Import only regular archives(that do not contain sandbox metadata) into an existing sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01118: Sandbox export operation not supported because the source MDS database repository is of older version that does not support this feature.

Cause: Sandbox metadata is needed to transfer documents from sandbox. Source store being used does not support storing metadata for sandbox.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01119: Sandbox import operation not supported because the target MDS database repository is of older version that does not supporit this feature.

Cause: Sandbox metadata is needed to transfer documents from sandbox. But target store being used does not support storing metadata for sandbox.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01120: Sandbox transfer unit list creation not supported because the source MDS database repository is of older version that does not support this feature.

Cause: Sandbox metadata is needed to transfer documents from sandbox. Source store being used does not support storing metadata for sandbox.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01121: Document "mds-transfer-config.xml" cannot be read by MDSTransfer.

Cause: The /meta-inf/mds-transfer-config.xml document cannot be read from source store. Refer to cause exception for more information on the actual reason for failure.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01122: Metadata Object Name "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata object name.

Cause: Metadata object name specified in /meta-inf/mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata object name.

Action: Make sure the document name specified in mds-transfer-config.xml is a valid metadata object name but not a speical document name.
Level: 1

Type: ERROR

Impact: Data

MDS-01123: The metadata path "{0}" specified in the mds-transfer-config.xml to preserve user updated documents in target repository is not a valid metadata path.

Cause: The metadata path specified in /meta-inf/mds-transfer-config.xml to preserve the user updated documents in target repository is not a valid metadata path.

Action: Make sure the metadata path specified in mds-transfer-config.xml is a valid metadata path.
Level: 1

Type: ERROR

Impact: Data

MDS-01150: Reference is null or empty.

Cause: A reference value was null or empty.

Action: Use a valid reference value that is not empty or null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01151: Id/LocationPath reference is null or missing.

Cause: An Id/LocationPath reference value was null or empty.

Action: Use a valid Id/LocationPath reference value that is not empty or null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01153: invalid LocationPath expression "{0}"

Cause: The LocationPath expression was invalid.

Action: Use a valid LocationPath format. The LocationPath expression should follow the format "/text()" or "/text()[x]", where 'x' is the index of "text block".
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01154: invalid LocationPath expression "{0}"

Cause: The node index in the LocationPath expression was invalid.

Action: Change the node index in the LocationPath expression to a number greater than or equal to 1.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01158: Expecting a base document. Reference "{0}" is a special document.

Cause: A base document was expected, but the reference was a special document.

Action: Use a valid base document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01159: Expecting absolute document reference. Reference "{0}" has local element reference portion.

Cause: The supplied reference was not the expected type.

Action: Ensure the reference is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01160: Expecting absolute document reference. Reference "{0}" is a relative reference to the document.

Cause: The supplied reference was not the expected type.

Action: Ensure the reference is of the expected type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01161: Reference "{0}" has an invalid character "{1}".

Cause: The supplied reference did not follow the MDS naming standard.

Action: Use valid characters for the reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01162: Reference "{0}" has an invalid XML attribute character.

Cause: The supplied reference did not follow the MDS naming standard.

Action: Use valid characters for the reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01163: invalid reference "{0}"

Cause: The supplied reference did not follow the MDS naming standard.

Action: Ensure that the reference follows the MDS naming standard.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01164: invalid reference "{0}" for a translation document

Cause: The supplied reference did not have the expected document extension (.xlf).

Action: Use the correct extension, .xlf, for the translation document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01165: invalid reference "{0}" for a customization document

Cause: The supplied reference did not have the expected document extension (.xml).

Action: Use the correct extension, .xml, for the customization document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01166: invalid reference "{0}" for a metadata extension document

Cause: The supplied reference did not have the expected document extension (.rdf).

Action: Use the correct extension, .rdf, for the metadata extension document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01167: There is no namespace declaration for the prefix "{1}" used in LocationPath expression "{0}".

Cause: The LocationPath expression was incomplete.

Action: Use a valid LocationPath format.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01168: Partition name "{0}" starts or ends with character "{1}". Partition name cannot contain leading or trailing spaces, ".", "-"

Cause: The supplied partition name contained leading or trailing spaces, ".", "-".

Action: Ensure that the partition name follows the MDS naming standard for partitions.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01169: Partition name "{0}" has an invalid character "{1}".

Cause: The supplied partition name did not follow the MDS naming standard.

Action: Use valid characters for the partition name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01170: Partition name is null or empty.

Cause: Partition name value was null or empty.

Action: Use a valid partition name that is not empty or null.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01171: The ID prefix generated by concatenating the layer name "{0}" and layer value "{1}" is not a valid MDS ID.

Cause: The ID prefix generated by concatenating the layer name with layer value did not follow the MDS ID naming standard.

Action: Ensure that the ID prefix generated by concatenating the layer name with layer value follows the MDS ID naming standard.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01200: This operation is not supported.

Cause: An MDS query operation was attempted, but this particular operation is not supported.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01201: An invalid parameter cannot be used when constructing a query condition.

Cause: An invalid parameter was passed to the class ConditionFactory.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01205: A SQL error is occurring when performing the query: "{0}" with binds {1}.

Cause: An MDS query on a database store led to a SQL error.

Action: Note the stack backtrace and context of the operation, including the reported SQL query and error, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01206: The array size for the query must be greater than zero.

Cause: An MDS query specified a fetch unit size that was not positive.

Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01207: The namespace mapping for the prefix "{0}" specified in the location path, is missing.

Cause: During XPath evaluation, the namespace prefix was used, but the prefix was not mapped to a namespace.

Action: Note the stack backtrace and context of the operation and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

MDS-01208: MDS query condition produces more than {0} characters of SQL where clause.

Cause: An MDS query condition was so large that it would produce a very large SQL statement.

Action: Note the stack backtrace and context of the operation, and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01250: The file path "{0}" does not exist.

Cause: An invalid path was provided.

Action: Retry the operation with a valid file path.
Level: 1

Type: ERROR

Impact: Files

MDS-01251: The parameter file {0} has no namespace on the document element.

Cause: A namespace was missing from the parameter file provided.

Action: Provide a parameter file with valid namespace information.
Level: 1

Type: ERROR

Impact: Data

MDS-01252: The parameter file {0} must have either {1} or {2} definition.

Cause: No source stores or target stores information were provided in the parameter file.

Action: Check the parameter file to have source and target store information and retry.
Level: 1

Type: ERROR

Impact: Data

MDS-01253: The parameter file {0} must not have both {1} and {2} definitions.

Cause: An attempt was made to transfer from source directory to target directory. Both source and target as directories is not supported.

Action: Provide correct source and target definition. Either source or target should be a metadata store.
Level: 1

Type: ERROR

Impact: Data

MDS-01254: The parameter file {0} contains same store definition for sourceStore and targetStore.

Cause: An attempt was made to transfer from and to the same store. The definition for sourceStore cannot be the same as the definition for targetStore.

Action: Provide correct source and target information. Change either source or target store definition.
Level: 1

Type: ERROR

Impact: Data

MDS-01255: The property {0} has not been supplied.

Cause: The required property was missing from the parameter file.

Action: Check the parameter file and supply the required property. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.
Level: 1

Type: ERROR

Impact: Data

MDS-01258: The value {0} for property {1} is invalid.

Cause: An invalid property value was provided in the parameter file.

Action: Provide a valid property value. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation.
Level: 1

Type: ERROR

Impact: Data

MDS-01259: The metadata store "{0}" cannot be instantiated.

Cause: An error occurred during the instantiation of the class for the metadata store.

Action: Verify that correct values are provided in the parameter file. Refer to the error messages in application logs that describe the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Data

MDS-01260: failure to process command-line arguments

Cause: Invalid command-line parameters were provided.

Action: Provide valid command-line parameters, and retry the operation. Refer to the MDS documentation for syntax of the tool parameters, or run the tool without parameters in order to get the Help message.
Level: 1

Type: ERROR

Impact: Data

MDS-01262: failure of transfer operation on a read-only target metadata store

Cause: The target metadata store used for transfer was read-only, for example a classpath store.

Action: Provide a writable target metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01263: operation failure on the resource {0} because source metadata store is read-only

Cause: An attempt was made to delete, create, update or get a mutable metadata object from a read-only source metadata store.

Action: Provide a writable source metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01264: The given element must contain either "customization" or "translation" configuration.

Cause: A customization or a translation configuration was missing for an element.

Action: Examine the transfer parameter file for valid MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01265: Invalid parameter file {0}. Reason: <{1}:{2}> {3}

Cause: Parameter file provided was not valid.

Action: Provide a valid parameter file. Refer to the MDS documentation for the correct syntax. A sample parameter file is also part of documentation. Refer to sample parameter for correct syntax.
Level: 1

Type: ERROR

Impact: Files

MDS-01266: The associated customization document is missing for a given customization class {0} for the given document name {1}.

Cause: The associated customization document for the given customization class did not exist.

Action: If the associated customization document was to be transferred, verify that it exists. Otherwise, no action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01267: The associated translation document is not found for a given locale {0} for the given document name {1}.

Cause: Associated translation document did not exist for the given locale.

Action: If the associated translation document was expected to be transferred, verify if it exists, otherwise, no action required.
Level: 1

Type: ERROR

Impact: Data

MDS-01268: The associated extended metadata document for the given document name {0} is missing.

Cause: No associated extended metadata document for the given document name existed.

Action: If the document was to be transferred, verify that the document exists. Otherwise, no action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-01270: Opening and closing parentheses do not match.

Cause: Either an opening or closing parentheses was missing.

Action: Check and correct the namespace mappings provided. Each opening parentheses should have an equivalent closing parentheses and vice versa.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01271: Cannot get the dependency registry

Cause: An error occurred while getting the dependency registry.

Action: Retry the operation. If the problem persists, look for messages that describe the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01272: unable to read mds-webapp-config.xml file

Cause: The mds-webapp-config.xml file was invalid.

Action: Confirm that the mds-webapp-config.xml file for the application is well formed, and valid.
Level: 1

Type: ERROR

Impact: Files

MDS-01273: The operation on the resource {0} failed because source metadata store mapped to the namespace {1} is read only.

Cause: An attempt was made to delete, create, update or get a mutable metadata object from a readonly source metadata store.

Action: Provide a writable source metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01301: Element "{1}", namespace "{0}" is not a valid child under parent "{3}", namespace "{2}".

Cause: An attempt was made to add, insert or replace a child element of the wrong type.

Action: Check the schema definition and ensure that the child element is the correct type.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01302: failure to load schema file "{0}"

Cause: An exception occurred in the XMLEF layer during processing of the schema definitions.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01303: failure to register grammar from schema file "{0}"

Cause: An exception occurred in the XMLEF layer during addition of schema definitions.

Action: Look for messages that describe the cause exception, and then take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-01305: failure to locate schema file "{0}".

Cause: The schema definition file was not found.

Action: Verify that the schema file name is correct, and that it is in the correct location.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01306: Grammar from a Web application can be added only once.

Cause: There were multiple method calls to add grammar from a web application.

Action: Verify that a grammar definition has already been added for the given MDSInstance and ServletContext. If it has then remove the calls to add it multiple times.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01307: no schema files for processing

Cause: No schema files were found against which beans can be generated.

Action: Pass an existing schema file to the bean generator.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01308: Event "{0}" is not supported.

Cause: An attempt was made to use event types that are not supported for the selected content model.

Action: Use only the event types that are allowed for the selected content model.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01309: ContentModelPipeline is empty.

Cause: The contentModelPipeline contained an empty or null builder list.

Action: A list of one or more valid builders must be available in the ContentModelPipeline.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01310: Invalid ContentModelPipeline. Missing {0}.

Cause: The expected builder was not available in builder list of the ContentModelPipeline.

Action: Valid builders must be supplied to the ContentModelPipeline.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01311: The DOM tree does not support the DOM event model.

Cause: This DOM Document did not implement EventTarget interface.

Action: Verify whether the Oracle XML Developer's Kit is used.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01312: Change-list transaction state is invalid.

Cause: The current change-list transaction state is invalid for the customization operation performed.

Action: Ensure Change-list to be in valid transaction state to perform the necessary customization operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01313: The argument for document cannot be null.

Cause: The argument for DocumentName was null.

Action: Provide a valid DocumentName.
Level: 1

Type: ERROR

Impact: Data

MDS-01314: TypeAnnotationProvider cannot be null.

Cause: The argument for TypeAnnotationProvider was null.

Action: Provide a valid TypeAnnotationProvider.
Level: 1

Type: ERROR

Impact: Data

MDS-01316: Support for XPath is not implemented yet.

Cause: Support for XPath has not been implemented yet.

Action: Provide a valid Configurable ID.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01319: JAXP support is not available. Falling back to using Oracle XML Developer's Kit for parsing the document {0}.

Cause: JAXP support was not available.

Action: None.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01320: Modifying the prefix declaration for {0} from "{1}" to "{2}" in document {3} through customizations is not supported.

Cause: An attempt was made to change an existing prefix declaration.

Action: Avoid attempts to change existing prefix declarations.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01321: Node type should be one of ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Cause: The node was not of the type ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.

Action: Ensure the node type is one of the following types: ImmutableModelNode.ELEMENT or ImmutableModelNode.TEXT or ImmutableModelNode.CDATA.
Level: 1

Type: ERROR

Impact: Data

MDS-01322: Value "{0}" does not satisfy "{1}" type.

Cause: The data type conversion failed.

Action: Verify that the expected XSD built-in simple data type and the passed-in string value are convertible.
Level: 1

Type: ERROR

Impact: Data

MDS-01323: Value "{0}" has an incorrect number of characters for a base64Binary.

Cause: The value did not represent a valid Base64Binary.

Action: Verify that the input value is valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01324: Unknown XML schema built-in type "{0}"

Cause: An attempt was made to use an unknown XML schema built-in type.

Action: Use only valid XML schema built-in types.
Level: 1

Type: ERROR

Impact: Data

MDS-01325: unable to load type definition "{0}"

Cause: Could not load this type definition because the specified location did not exist.

Action: Ensure that the specified location for the type definition exists.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01326: Loading of type definition from element "{0}" is not supported.

Cause: An attempt was made to load a type definition from the specified element that is not supported in the MDS configuration.

Action: Examine the schema definition to ensure that the entry specified in type definition is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01327: unable to load data from "{0}" into {1}

Cause: An error occurred while loading the content of this configuration element.

Action: Examine the schema definition to ensure that the content of this configuration element is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01328: unable to load element "{0}" into {1}

Cause: An error occurred while loading this configuration element.

Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01329: unable to load element "{0}"

Cause: An error occurred while loading this configuration element.

Action: Examine the schema definition to ensure this configuration element is correctly specified in the MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01330: unable to load MDS configuration document

Cause: An I/O or parsing error occurred while loading the MDS configuration document.

Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.
Level: 1

Type: ERROR

Impact: Files

MDS-01331: unable to load MDS configuration document "{0}"

Cause: An error occurred in loading the content of MDS configuration document.

Action: Verify that the URL is correct, and ensure that the document contains valid MDS configuration information.
Level: 1

Type: ERROR

Impact: Files

MDS-01332: Class {0} is not a subclass or implementation of {1}.

Cause: The class specified in the configuration information did not extend the required class, or implement the required interface.

Action: Ensure that the class specified in the configuration information extends the correct class, or implements the correct interface.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01333: missing element "{0}"

Cause: This element was missing from the MDS configuration information.

Action: Ensure that the element is specified in the configuration information.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01334: missing element "{0}" in document "{1}"

Cause: This element was missing from the MDS configuration information.

Action: Ensure that this element is specified in the configuration document.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01335: namespace "{0}" mapped to metadata-store-usage "{1}" but its definition was not found in MDS configuration.

Cause: Metadata-store-usage element that was referenced by a namespace not found in MDS configuration.

Action: Ensure that this element is specified in MDS configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01336: No XML element is provided to create {0}.

Cause: A null XML element was passed to the constructor of this configuration object.

Action: Ensure that a valid XML element is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01337: No URL is provided to create {0}.

Cause: A null URL was passed to the constructor of this configuration object.

Action: Ensure that a valid URL is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01340: More than one metadata store can be resolved for the namespace "{0}".

Cause: There were multiple namespace to metadata store mappings in the persistence configuration that satisfied the request for the metadata store of a given namespace.

Action: Correct the namespace mapping in persistence configuration to ensure that the namespace is mapped to only one metadata store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01341: Namespace mapping for "{0}" is overridden by namespace mapping for "{1}"; the first mapping is not used.

Cause: A conflicting mapping to this namespace has already been defined in the persistence configuration.

Action: Correct the namespace mapping in the persistence configuration to ensure that there is no conflicting mapping to this namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01342: No metadata store is mapped to the namespace "{0}".

Cause: No namespace mapping could be found in the persistence configuration for the specified namespace.

Action: Ensure that a correct namespace is passed into the method concerned, or alter the application configuration to define the specified namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01343: There is a duplicate file extension mapping for "{0}".

Cause: A mapping to this file extension has already been defined in the file type configuration.

Action: Remove the duplicate file extension mapping from the file type configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01344: cannot create {0} due to null parameter

Cause: A null parameter was passed to the constructor of this configuration object.

Action: Ensure that a valid parameter is provided to create a new instance of this configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01346: The given namespace path "{0}" is not a valid path.

Cause: An invalid path was provided to create a namespace.

Action: Ensure that a valid path is provided to create a namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01347: Base restriction is supported only for classpath store or servlet context store: namespace "{0}" mapped to "{1}".

Cause: The base restriction was specified for a metadata store other than the classpath metadata store and servlet context store.

Action: Correct the namespace mapping in the configuration to ensure that the base restriction is specified only for the classpath store or servlet context store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01348: unable to save configuration document to "{0}"

Cause: An I/O error occurred while writing the configuration to a file.

Action: Check the file system and ensure that the file location is writable.
Level: 1

Type: ERROR

Impact: Files

MDS-01349: unable to read existing configuration document "{0}" to be updated

Cause: An I/O or parsing error occurred while reading the configuration file.

Action: Ensure that the configuration file does exist and has valid contents.
Level: 1

Type: ERROR

Impact: Files

MDS-01350: Adding namespace "{0}" mapped to "{1}" conflicts with existing namespace "{2}" mapped to "{3}".

Cause: An attempt was made to add a new namespace that conflicted with an existing namespace because it mapped to a different repository.

Action: Ensure that the new namespace does not map to a different repository if the new namespace is a super-namespace or sub-namespace of existing namespaces.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01351: Adding namespace "{0}" with "{1}" restriction conflicts with existing namespace "{2}" with "{3}" restriction.

Cause: An attempt was made to add a new namespace that conflicted with an existing namespace in the namespace restriction.

Action: Ensure that the new namespace does not conflict with existing namespaces in the namespace restriction if the new namespace is a super-namespace or sub-namespace of existing namespaces.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01352: Customization configuration with granular mapping "{0}" is unsupported; only the slash, "/", is allowed.

Cause: An attempt was made to add an invalid namespace mapping of the customization configuration. Only one namespace to customization class list mapping is currently allowed, and that namespace has to be a slash (/).

Action: Ensure that only the slash (/) is specified in the namespace mapping of the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01353: unable to retrieve customization layer values from "{0}"

Cause: An I/O or parsing error occurred while reading the specified file to retrieve customization layer values.

Action: Ensure that the file does exist and has valid contents.
Level: 1

Type: ERROR

Impact: Files

MDS-01355: Both TypeConfig parameters contain Grammar Providers. Only one Grammar Provider is allowed.

Cause: A Grammar Provider was specified in multiple type configuration sources.

Action: Ensure that only one Grammar Provider is specified in the type Configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01356: Both TypeConfig parameters contain Metadata Providers. Only one Metadata Provider is allowed.

Cause: A Metadata Provider was specified in multiple type configuration sources.

Action: Ensure that only one Metadata Provider is specified in the type Configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01357: MDS configuration is not compatible with JAXB 1.0.

Cause: JAXB 1.0 jar file (xml.jar) was found on the classpath before any JAXB 2.0 jar files.

Action: Ensure that JAXB 2.0 jar files appear on the classpath before JAXB 1.0 jar file (xml.jar).
Level: 1

Type: ERROR

Impact: Configuration

MDS-01358: Invalid MDS configuration. Configuring multiple metadata stores as the default repository for customizations.

Cause: Multiple metadata stores were configured as the default repository for customizations in the MDS configuration.

Action: Ensure that only a single metadata store is configured as the default repository for customizations.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01359: The namespace used (http://xmlns.oracle.com/mds/config_10_1_3_001) in the configuration document is deprecated. Update the configuration document to use "http://xmlns.oracle.com/mds/config" as the namespace.

Cause: The namespace used (http://xmlns.oracle.com/mds/config_10_1_3_001) in the configuration document is deprecated.

Action: Update the configuration document to use "http://xmlns.oracle.com/mds/config" as the namespace.
Level: 1

Type: WARNING

Impact: Configuration

MDS-01360: Invalid MDS configuration. The attribute file-type-extension on the file-type element is missing for file type configuration.

Cause: The attribute file-type-extension was not specified on the file-type element for file type configuration.

Action: Ensure that a valid file-type-extension attribute is specified for every file-type element.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01361: cannot add XSD grammar

Cause: An attempt was made to add XSD grammar made by passing in a SchemaGrammarProvider.

Action: Ensure that the grammar provider is obtained using oracle.jdeveloper.webapp.runtime.WebAppDesignContext.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01362: Failed to auto-purge MDS respository: "{0}".

Cause: MetadataStore was scheduled for auto-purge after the MDSInstance was released

Action: Try later and contact support if persists.
Level: 1

Type: WARNING

Impact: Other

MDS-01363: Failed to lookup datasource with JNDI name "{0}" configured for the DBMetadataStore, defaulting to use ClassPathMetadataStore.

Cause: Application was configured with DBMetadataStore using JNDI datasource and JNDI lookup failed when running outside application server.

Action: No action required if defaulting to ClasspathMetadataStore is acceptable. Otherwise, use appropriate configuration such as FileMetadataStore.
Level: 1

Type: WARNING

Impact: Configuration

MDS-01365: Multiple metadata stores found with deploy-target attribute set to true, only one allowed per configuration.

Cause: Multiple metadata stores were configured as the deployment target.

Action: Ensure that only a single metadata store is configured for deployment.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01366: Cannot find a metadata store with deploy-target attribute set to true

Cause: A single metadata store must be configured as a deploy target. None was found.

Action: Ensure that a single metadata store is configured for deployment.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01367: Failed to create {0}. Invalid MDS configuration specified in: "{1}"

Cause: Declarative MDS configuration is invalid.

Action: Specify correct mds configuration information and try creating the configuration again.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01368: Variable "{0}" used in configuration document is not defined either as system property or as envrionment variable.

Cause: This variable was not defined.

Action: Ensure that this variable is defined before loading the configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01369: Variable declaration in "{0}" in configuration document is incorrect.

Cause: Variable did not either start with "${" or it did not end with "}".

Action: Ensure that the configuration variable is correctly declared in the form ${var}.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01370: MetadataStore configuration for metadata-store-usage "{0}" is invalid.

Cause: MetadataStore class or some of its properties were not valid.

Action: Ensure that the MetadataStore class exists and all required properties are valid. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01371: ADF security is not configured in "{0}", password can not be securely processed.

Cause: ADF security configuration was not found in the config file.

Action: Set the password using JDeveloper to ensure required configuration is generated.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01373: unable to retrieve password.

Cause: unable to retrieve the password due to exception in security layer.

Action: See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01374: unable to save password.

Cause: unable to save the password due to exception in security layer.

Action: See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01375: No password defined for DBMetadataStore in configuration file or in the wallet file.

Cause: DBMetadataStore uses JDBC based configuration but no password specified.

Action: Set the password for the DBMetadataStore using JDeveloper.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01376: Unable to get database connection from data source "{1}" configured with JNDI name "{0}".

Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.

Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01377: Unable to get database connection from data source configured with JNDI name "{0}".

Cause: Failed to retrieve a database connection from the data source either because the data source is not configured correctly or the database details are not correct.

Action: Test the data source to check if it is correctly configured and if the database can be accessed. See message of the cause exception for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01378: metadata-store-usage attribute should not be set on namespace "{0}" defined in mds-config.xml.

Cause: metadata-store-usage attribute was set on the specified namespace in mds-component-config, but this namespace is always assumed to map to deploy-target metadata store.

Action: Ensure that the metadata-store-usage attribute is removed on specified namespace in mds-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01379: Tenant scope "{0}" is not valid for namespace "{1}" with namespace restriction "{2}".

Cause: Tenant scope configured for the namespace is not supported with the configured namespace restriction.

Action: Resolve the conflict between tenant scope and namespace-restriction in the application configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01380: Tenant scoped base metadata in package "{0}" can not have global customization layer "{1}".

Cause: Tenant scope GLOBAL on the specified customization layer conflicts with tenant scope TENANT on the base namespace.

Action: Resolve the conflicts between the tenant scope on the base namespace and that on the customization layer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01381: Customization layer "{0}" has been configured more than once with the same tenant scope.

Cause: Duplicate configuration for the same customization layer was found.

Action: Remove the duplicate customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01382: Customization layer "{0}" has been configured more than once with conflicting tenant scopes.

Cause: Conflicting tenant scope configurations was found for the same customization layer.

Action: Remove the incorrect customization layer configuration from adf-config.xml of the application or component config (mds-config.xml) on classpath.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01383: Sandbox name should be provided for registering a sandbox change listener.

Cause: No sandbox name was provided for registering the sandbox change listener.

Action: Provide a valid sandbox name when registering the sandbox change listener.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01384: Sandbox change listener is not found when registering the lifecycle listener for sandbox {0}.

Cause: The SendboxChangeListener being registered was null.

Action: Provide a valid sandbox change listener when registering the lifecycle listener for the sandbox.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01385: Tenant scope "{0}" as base tenant scope is not valid for namespace "{1}".

Cause: The specified tenant scope type could not be configured as base tenant scope for the namespace.

Action: Use the correct base tenant scope parameter to create the namespace.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01386: Multitenant application can not be configured with metadata store "{0}" that does not support multitenancy.

Cause: A metadata store that does not support multitenancy was configured for a multitenant enabled application.

Action: Configure a metadata store such as DBMetadataStore that supports multitenancy.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01387: Tenant with id "{0}" is not allowed to change the autopurge settings; only the global admin can change this configuration.

Cause: A tenant cannot change the autopurge configuration..

Action: Only a global admin can change the autopurge configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01388: Unable to set cache size to {0} KiloBytes.

Cause: The cache size requested was invalid either becuase it was negative or it was too large for the Java Object Cache.

Action: Check that the specified size is >0 and within the limit for the cache implementation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01389: ContentType can not be specified for Streamed documents.

Cause: Conflicting settings between ContentType and isStreamed were found in ContentConfig.

Action: Change ContentOptions to use either ContentType or isStreamed.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01390: An audit event name for component "{0}" is not specified.

Cause: An audit event was defined, but a name for the event was not specified.

Action: Give the audit event a valid name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01391: "{0}" is not a valid audit event name.

Cause: An invalid audit event name was found. An audit event name should start with a letter and contain only letters and digits.

Action: Specify a valid name for the audit event.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01392: Conflicting definitions were found for the audit event with name "{0}" and audit-component "{1}".

Cause: Conflicting audit event definitions were found in audit-component element.

Action: Remove or modify one of the conflicting audit events.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01393: Multiple audit events named "{0}" are defined for component "{1}".

Cause: Duplicate audit events were found in audit-component element.

Action: Remove or modify one of the duplicate audit events.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01394: The repository-name property element is not specified for a metadata-store element that does not have the class-name property.

Cause: The repository-name property element was not specified for a metadata-store element. It is required when the class-name property is not specified on the metadata-store element to support look up of the repository details.

Action: Specify the repository name in a child property element of the metadata-store element or specify the class-name property for the metadat-store element in the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01395: Unable to look up the details of the specified repository {0} for the metadata-store configuration.

Cause: The specified repository was not registered in the domain or the repository was not configured properly.

Action: Ensure that the specified repository for the metadata-store is configured and registered properly in the domain.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01396: metadata-store-usage attribute is not set on namespace "{0}" defined in mds-config.xml.

Cause: metadata-store-usage attribute was missing on the specified namespace in mds-component-config.

Action: Ensure that the metadata-store-usage attribute is set on the specified namespace in mds-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01397: Multiple audit events with display name "{0}" are defined for component "{1}".

Cause: More than one audit event was found with the same display name in audit-component element.

Action: Ensure that the display names are unique for all audit events of a component.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01400: Read-only extended metadata resource "{0}" is not writable.

Cause: An attempt was made to update a read-only extended metadata resource.

Action: Ensure that the metadata object is mutable before getting the extended metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01401: Updating a node in one document "{1}" using a node from a different document "{0}" is not allowed.

Cause: The node being added or inserted was from a different metadata object. They must be from the same base document.

Action: Ensure that the node being inserted is from the correct metadata object.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01402: attempting to update an immutable MElement: "{0}"

Cause: The MElement being updated was immutable.

Action: Check that the MElement in question really is mutable.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01403: Updating a mutable MElement using an immutable MElement: "{0}" is not allowed.

Cause: An attempt was made to update a mutable MElement using an immutable MElement.

Action: Verify that the child MElement being used for the update is mutable.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01404: Customization to replace root node of {0} is not allowed.

Cause: An attempt was made to replace the root node as part of a customization.

Action: Replace the root node in the base document, or modify the existing root node instead.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01450: missing GUID

Cause: The application removed an object's GUID while editing its XML metadata content.

Action: Fix the application so it does not tamper with MDS GUIDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01451: GUIDs do not match.

Cause: The application altered an object's GUID while editing its XML metadata content.

Action: Fix the application so it does not tamper with MDS GUIDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01452: GUID is null.

Cause: An attempt was made to retrieve a metadata object or document by GUID, but the given GUID was null.

Action: Fix the application so it passes a valid GUID to the method in question.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01455: multiple GUIDs on metadata object {0}

Cause: The application set multiple GUID values while editing an object's XML metadata content.

Action: Fix the application so it does not tamper with MDS GUIDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01456: invalid GUID on metadata object {0}

Cause: The application set an object's GUID to an invalid value while editing its XML metadata content.

Action: Fix the application so it does not tamper with MDS GUIDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01457: GUID feature not available

Cause: The application attempted to retrieve an object by GUID from a metadata store that does not yet support this.

Action: Fix the application so it does not attempt this, or configure the application to use a different type of metadata store.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01458: GUID must not be present.

Cause: The application set an object's GUID value while editing its XML metadata content.

Action: Fix the application so it does not tamper with MDS GUIDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01460: GUIDs on DOM Document do not match.

Cause: The application set an object's GUID to a different value while editing its XML metadata content.

Action: Fix the application so it does not tamper with MDS GUIDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01461: unable to create document {0} in the metadata repository; a document with the same name or GUID already exists

Cause: An attempt was made to import or create a document with a name or GUID that is already used by an existing document.

Action: Delete the document in the MDS repository prior to import or creation.
Level: 1

Type: ERROR

Impact: Data

MDS-01462: GUID feature is not supported in the classpath store.

Cause: The application attempted to retrieve an object by GUID from the classpath metadata store that does not support this.

Action: Fix the application so it does not attempt retrieval by GUID, or configure the application to use a different type of metadata store.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01464: unable to save GUIDRegister {0}

Cause: The GUID register (GUID index files) could not be written.

Action: Verify that the application has write permission for the given file, and that the disk is not full.
Level: 1

Type: ERROR

Impact: Files

MDS-01465: unable to remove node {0} from the GUIDRegister

Cause: The given node was not removed from the GUID register, possibly because it was not found.

Action: Delete the GUID register files, restart the application and try the operation again. If that fails, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Data

MDS-01466: unable to create GUIDRegister directory {0}

Cause: The owning directories for the GUID register (GUID index files) were not created.

Action: Verify that you have permission to create the parent directories for the given file name.
Level: 1

Type: ERROR

Impact: Files

MDS-01468: A different GUID is already registered for document {0}.

Cause: The GUID register has become corrupted.

Action: Delete the GUID register files and restart the application (the files will then be re-created).
Level: 1

Type: ERROR

Impact: Data

MDS-01469: unable to remove old GUIDRegister store path {0}

Cause: Old GUID register files were not deleted.

Action: Verify that you have permission to delete these files.
Level: 1

Type: ERROR

Impact: Files

MDS-01470: more than one GUID is registered for document {0}

Cause: The GUID register has become corrupted.

Action: Delete the GUID register files and restart the application (the files will then be re-created).
Level: 1

Type: ERROR

Impact: Data

MDS-01471: more than one document is registered for GUID {0}

Cause: The GUID register has become corrupted.

Action: Delete the GUID register files and restart the application (the files will then be re-created).
Level: 1

Type: ERROR

Impact: Data

MDS-01472: GUID is missing in file {0}

Cause: No GUID was found in the given file but the metadata object type definition indicated there should be one.

Action: Re-create the metadata object or correct its type definition not to require a GUID.
Level: 1

Type: ERROR

Impact: Data

MDS-01500: The MDSObject {0} is an XML document and cannot be loaded using StreamedObject API.

Cause: An attempt was made to load an XML document via StreamedObject API.

Action: Retry the operation using MetadataObject API or use a non-XML document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01501: The MDSObject {0} is not an XML document and cannot be loaded from MetadataObject API.

Cause: An attempt was made to load a streamed object (non-XML document) using MetadataObject API.

Action: Retry the operation using StreamedObject API or use a document containing valid XML.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01502: The MDSObject "{0}" is an XML document and cannot be saved using StreamedObject API.

Cause: An attempt was made to save an XML document using StreamedObject API.

Action: Retry the operation using MetadataObject API.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01503: The content of StreamedObject {0} cannot be read.

Cause: An attempt to read the StreamedObject content failed.

Action: Look at the error message and exception stack in the application logs to determine the reason for the failure.
Level: 1

Type: ERROR

Impact: Data

MDS-01504: The document {0} is either registered as a streamed file type or is a non-XML file extension and cannot be created using MetadataObject API.

Cause: An attempt was made to create an MDSObject named with a streamed object (non-XML) extension using MetadataObject API.

Action: Retry the operation using StreamedObject API.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01600: The Dependency Analyzer requires a DependencyFilter.

Cause: Either no filter was supplied, or the filter supplied was null.

Action: Supply a non-null filter.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01601: The relationship role name {0} is a duplicate.

Cause: A role name defined in a relationship had already been used.

Action: Ensure that the toParentRole and toChildRole in a relationship have not already been used by another relationship.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01602: cannot locate the element type {0} in namespace {1} defined for the relationship

Cause: The element type did not exist in the given namespace.

Action: Ensure that the element type exists in the given namespace.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01604: The relationship from {0} to {1} is invalid because the latter is not a valid MDS reference.

Cause: An invalid MDS reference was specified as the parent.

Action: Ensure the parent reference is a valid MDS reference.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01605: The relationship from {0} to {1} is invalid because the latter does not exist.

Cause: No parent element was found matching the MDS reference supplied.

Action: Ensure that the parent reference in the relationship points to an existing element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01606: The relationship from {0} to {1} is invalid because the latter is of incorrect type.

Cause: The child element referenced a parent of the wrong type.

Action: Ensure that the parent type matches the one stipulated in the relationship definition.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01607: The relationship from {0} to {1} is invalid because type information is not available for the latter.

Cause: No type definition could be found for the parent.

Action: Ensure that the parent type information is available.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01608: The relationship from {0} to {1} is invalid because the latter maps to a different store.

Cause: The parent and child objects in the relationship have been mapped to different stores.

Action: Ensure that the parent maps to the same store as the child object.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01609: The document {0} contains relationships that do not conform to the relationship definition.

Cause: Constraints in this document's relationship definitions were violated.

Action: Ensure that the relationships conform to the constraints in the relationship definition.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01610: Some of the changes in the MDS session are not valid.

Cause: A change was made in the MDS session that was not valid.

Action: Check the changes made and ensure each of them is valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01611: not saving changes in MDS session because some changes are not valid

Cause: A change made in the MDS session was not valid.

Action: Check all the changes made and ensure that all changes are valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01612: The object {0} cannot be deleted because it is referenced by {1}.

Cause: An attempt was made to delete an element that was being referenced by a child object.

Action: Remove the child reference to this object so the object can be deleted.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01613: The MetadataObject {0} cannot be deleted because of relationship integrity constraints.

Cause: An attempt was made to delete an object that was still being referenced.

Action: Remove the child references to the metadataObject so that it can be deleted.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01614: Rename is not allowed because integrity checking is not turned on in the object {1} in MetadataObject {0}.

Cause: Integrity checking was switched off so it was not possible to check whether the rename would have broken any relationship integrity constraints.

Action: Ensure that integrity checking is turned on.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01615: failure to rename {0} because there is no reference attribute in MetadataObject {1}, element {2}

Cause: A child object could not reference the renamed object as its current reference was invalid.

Action: Confirm that all the references in the child object are valid.
Level: 1

Type: ERROR

Impact: Data

MDS-01620: The untyped dependency with the following registration details cannot be inserted: {0}, {1}, {2}, {3}.

Cause: The dependency could not be registered in the database repository due to a SQL exception.

Action: Correct the cause of the SQL exception and retry the untyped dependency registration.
Level: 1

Type: ERROR

Impact: Data

MDS-01621: The untyped dependency information for {0} could not be removed.

Cause: An attempt to remove untyped dependency information failed either because the document was invalid or there was a SQL exception.

Action: Verify that the document and its dependencies are valid, or correct the cause of any SQL exceptions.
Level: 1

Type: ERROR

Impact: Data

MDS-01622: There is no analyzer to unregister.

Cause: No analyzers were supplied to be unregistered.

Action: Supply the DependencyAnalyzer to be unregistered.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01630: invalid operation in a customized context on an element that could participate in a relationship: {0}

Cause: Within a customized context there was an attempt to insert an element without first deleting it as part of a composite move.

Action: Within the customized context, do not attempt inserts on elements without first deleting them as part of a composite move.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01631: In a customized context, an element that could participate in a relationship as a child cannot be modified. The reference is {0} on {1}.

Cause: Within a customized context, an attribute being customized could have been a parent reference within a relationship.

Action: Do not attempt to modify or remove an attribute that could be a parent reference within a relationship.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01633: In a customized context, an element that could participate in a relationship cannot be deleted: {0}.

Cause: Within a customized context an attempt was made to delete an element that could participate in a relationship.

Action: Do not attempt to delete an entity while in a customized context.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01634: In {0}, a {1} element that participates in a relationship lacks a configurable ID.

Cause: An operation was attempted on a participant in a relationship that lacked a configurable ID.

Action: Add a configurable ID to the element on which it is missing. If necessary, refer to the element's schema definition to identify the configurable ID attribute.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01635: Skipping the relationship validation for {0} in the metadata object {1} because the element contains an invalid MDS reference.

Cause: Validation of the object's relationships was not performed because the element contained an invalid MDS reference.

Action: Correct the MDS references in the MetadataObject specified.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01700: MElementBeanImpl._setSimpleChild cannot be called on a non-simpleType element: name={0}, namespace{1}

Cause: An attempt was made to set a bean element to a simple type, but the definition in the schema was not a simple type. The generated beans may not have matched the registered schema.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01701: Cannot set the value on an element that is not based on a simpleType: name={0}, namespace={1}

Cause: An attempt was made to set an element to a simple type, but the definition in the schema was not a simple type.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01702: The method getBean() is not valid for metadata object {0} - it is allowed on only bean metadata objects.

Cause: An attempt was made to access the metadata object using the bean API but the metadata object was not a bean metadata object. The schema for the root element may not have been registered with MDS, or the beans were not available on the classpath.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01703: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - no object factory can be found or jaxb.properties cannot be found

Cause: An element was found in the metadata object that did not have a corresponding bean class. The schema for the element may not have been registered with MDS, or the beans were not available on the classpath.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01705: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - object factory class {3} does not have the expected unmarshal() method

Cause: The bean object factory found for the element did not appear to have been generated by the MDS bean generation tool.

Action: Regenerate the beans from the schema definitions and ensure that the correct versions are on the classpath. Check that the schemas are registered with the MDS instance.
Level: 1

Type: ERROR

Impact: Data

MDS-01706: error unmarshalling bean element: name={0}, namespace={1} in metadata object {2} - object factory class {3} failure in unmarshal() method

Cause: An unexpected exception occurred while creating a bean object for the element.

Action: Contact the developers of the application, providing the cause exception.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01707: Error generating relationship method {0} for relationship defined on attribute {1}: incorrect parentType definition

Cause: There was an error in the relationiship definition.

Action: Check the parentType definition on the relationship
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01800: Sandbox is not supported for {0} configured on {1}.

Cause: An underlying metadata store did not support the sandbox feature.

Action: Provide a metadata store that supports sandbox feature.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01801: Document name {0} should not refer to the raw sandbox resource name.

Cause: A resource name pointed directly to a resource in the sandbox component.

Action: Provide a logical document name to resolve the issue.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01802: A sandbox by name {0} already exists in the {1} store.

Cause: A sandbox with the same name already existed in the store.

Action: Use a different name or destroy the existing sandbox before reusing the same name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01803: Sandbox Persistence manager cannot be constructed using an instance of SandboxPManager.

Cause: An attempt was made to construct an instance of sandbox persistence manager using an instance of SandboxPManager.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-01804: Sandbox {0} configured with {1} namespace, {2} store and {3} label from mainline is not compatible with {4} label created on {5} namespace.

Cause: A label was used that is different from the mainline label associated with the sandbox.

Action: Use a label that is compatible with the sandbox and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01805: Sandbox {0} missing in {1}.

Cause: The specified sandbox was not found in the underlying metadata store.

Action: Provide the name of an existing sandbox, or create a new sandbox if necessary.
Level: 1

Type: ERROR

Impact: Data

MDS-01806: failure to remove {0} from {1}, because it is not a valid document in the sandbox

Cause: The specified document to be removed was not found in the sandbox.

Action: Verify that the document exists in the sandbox.
Level: 1

Type: ERROR

Impact: Data

MDS-01807: failure to delete sandbox {0}

Cause: An error occurred while deleting the sandbox.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01808: SandboxUsage with the sandbox name set to {0} does not return any namespaces.

Cause: No namespaces were found on the SandboxUsage.

Action: Configure the SandboxUsage with namespaces that are associated with the sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01809: failure to list sandboxes matching {0}

Cause: An error occurred while listing or querying the sandboxes.

Action: Look for error messages to determine the actual cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01810: failure to refresh sandboxes to target label {0}

Cause: Target label is older than the current source label.

Action: Specify a target label which is later than current label.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01811: failure to list sandboxes matching customization for {0}, layer: {1}, value: {2}

Cause: An error occurred while listing or querying the sandboxes.

Action: Look for error messages to determine the actual cause of the failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01812: sandbox name {0} exceeds the maximum limit of {1} characters

Cause: Sandbox name is more than the supported size.

Action: Use a shorter sandbox name.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01813: sandbox metadata for {0} can not be saved because it is being updated by another user.

Cause: More than one user is updating the sandbox metadata at the same time.

Action: Get the sandbox metadata again and retry saving after making the changes.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01814: sandbox metadata for {0} cannot be changed because it is read only.

Cause: Sandbox metadata is read only and cannot be updated

Action: To update get an instance of sandbox and then get the sandbox metadata from the instance
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01815: store configured for sandbox {0} does not support sandbox metadata.

Cause: Sandbox metadata is not supported on the repository.

Action: Sandbox metadata is supported in MDS repository version 11.1.1.4.0 (11gR1 PS3 patchset) onwards. Upgrade the repository to this version or later to use this feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01816: {0} is not a valid name for a sandbox.

Cause: The specified sandbox name is either an MDS reserved package part name or contains invalid characters.

Action: Ensure that the specified sandbox name is neither an MDS reserved package part name nor does it contain invalid characters as per the MDS Resource name specification.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01817: sandbox {0} is either active or applied to mainline. The undo operation cannot continue.

Cause: The sandbox is either applied or is in the active state.

Action: Check that the sandbox is in the intermediary state
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01818: sandbox {0} is in applied_with_undo state. No further updates except finalized are allowed.

Cause: The sandbox is in applied_with_undo state and no further updates can be done to the sandbox.

Action: The only allowed operations in the intermediary state are: finalize and undo.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01819: Lock on sandbox {0} cannot be taken. A concurrent management operation may be in progress.

Cause: A management operation on the sandbox is in progress and has locked the sandbox.

Action: Retry the operation after a while.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01820: Metadata for sandbox {0} is not available. The sandbox management operation cannot proceed without sandbox metadata.

Cause: Sandbox was created without metadata.

Action: Use the management APIs that are available for sandboxes without metadata.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01821: Lifecycle change notifications for the sandbox {0} cannot be sent out because the change type is not defined.

Cause: The sandbox lifecycle change does not have a valid change type.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

MDS-01900: None of the configured metadata stores support versioning.

Cause: The underlying metadata store did not support versioning.

Action: Configure a metadata store that supports versioning, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01901: specifying multiple labels for a namespace not allowed

Cause: Multiple labels were provided for a namespace that pointed to a metadata store.

Action: Provide a single label to map to a namespace and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01902: Label or namespace is invalid.

Cause: Either the namespace or the label was invalid.

Action: Verify that the namespace and the label are correct, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01903: Specified label {0} does not exist for {1} namespace.

Cause: The specified label did not exist in the metadata store mapped to the namespace.

Action: Verify that the label name is correct and that the label exists, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01906: A label with same name {0} already exists.

Cause: An attempt was made to create a label that already existed.

Action: Create a label with a different name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01907: The label {1} is already configured for the store "{0}", so the same store cannot be configured with another label "{2}".

Cause: An attempt was made to map a label for a store when a label-to-store mapping already existed for that store.

Action: De-associate the existing label mapped to the store first, and then retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01908: failure to delete versions of the document {0}

Cause: An error had occurred while versions were being deleted.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01909: No namespaces are specified for creating label {0}.

Cause: No namespace information was found for creating a label.

Action: Provide a namespace for creating a label, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01910: The namespace {0} is already registered with the label {1}, so the super/sub namespace {2} cannot be assigned with the label {3}.

Cause: An attempt was made to associate multiple labels with a namespace, or an attempt was made to associate multiple namespaces with a single label.

Action: Associate a single label with a single namespace, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01911: failure of the metadata purge operation for the requested repository partition

Cause: An error occurred during a purge operation.

Action: Retry the operation. Also, refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01912: MetadataStore configured for {0} does not support versioning.

Cause: The metadata store configured for the resource did not support versioning.

Action: Configure a metadata store that supports versioning or verify that the resource name is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-01913: A deployment lineage with same application name "{0}" and deployment module name "{1}" already exists.

Cause: An attempt was made to create a lineage that already existed.

Action: Create a lineage with a different application or MAR name, and then retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-01914: The application name and deployment module name cannot be null to create DeploymentInfo.

Cause: An attempt was made to create DeploymentInfo with null values.

Action: Make sure that the values for application name and deployment module name are non-null.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02024: Setting or modifying the unique identifier of an existing node through customizations is not supported.

Cause: An attempt was made to customize a configurable ID.

Action: Remove any customization that is attempting to modify the unique identifier of an XML element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02025: The requested change is incompatible with changes already pending on the MDS session.

Cause: An attempt was made to perform a change operation on the MDS session which would update the same MetadataObject part as another change operation that has been done. For example, if you change a customization of a metadata object then attempt to delete all of its customizations, the latter operation will fail because it conflicts with the former. You must save the former change first before doing the second.

Action: Save the changes that have already been made on the session (by calling flushChanges), then retry the failed operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02100: Illegal permission target: "{0}" - must begin with {1}.

Cause: An attempt was made to create an MDS permission class with an incorrect syntax.

Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02101: Illegal permission action: "{0}" - unknown action.

Cause: An attempt was made to create an MDS permission class with an incorrect syntax.

Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02102: Illegal permission action: "{0}" - customize action takes 0 or 2 parameters.

Cause: An attempt was made to create an MDS permission class with an incorrect syntax.

Action: Permission classes are usually created internally by MDS but may be created by the application directly. Contact the developers of the application to confirm that this is not an application error and if not contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-02201: type validation failure for the metadata object "{0}"

Cause: The content of the metadata object was not valid against the registered XSDs.

Action: Ensure that the metadata object content is valid with respect to the registered XSDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02202: Content of the metadata object "{0}" is not valid.

Cause: The content was not valid either with respect to the registered XSDs or with the registered relationships.

Action: Check the content of the metadata object and correct the content as necessary to make it valid.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02203: type validation error for the metadata object "{0}" at the node "{1}"

Cause: A validation error occurred at the specified node.

Action: Check the content at the specified node for compliance with registered XSDs and relationships.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02204: type validation warning for the metadata object "{0}" at the node "{1}"

Cause: A validation warning occurred at the specified node.

Action: Check the content at the specified node for compliance with registered XSDs.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02301: The rename unit is invalid because either "{0}" or "{1}" is reused in the rename plan.

Cause: The resource name provided in the rename plan was used more than once.

Action: Provide distinct names for source and target names while renaming.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02302: subobjects "{1}" not found in metadata object "{0}"

Cause: The specified subobjects were not found in the metadata object.

Action: Look in the error message log for details.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02303: The given rename plan syntax is invalid

Cause: The rename plan syntax specified was invalid.

Action: Look in the error message log for details.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02304: RenameOperation failed for StreamedObject "{0}" because subobjects were specified for this streamed object.

Cause: Streamed objects do not support subobjects.

Action: Remove the RenameObject that contains reference to the streamed object and subobject references from the RenamPlan.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02401: The operation {0} on the {1} node is not allowed.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02402: The type definition for {1} does not allow customization of {0}.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file, tag library definition file, or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02404: The subelement {1} in the MDX document does not allow customization of {0}.

Cause: An attempt was made to customize a node that was not customizable.

Action: Check the customization restriction information which can be located in the schema definition, standalone xml file or an extended metadata file. Also check the customization policy for the MDSSession in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02405: The attribute {2} in element {1} in the MDX document does not allow customization of {0}.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02406: Customization of {0} is not allowed because it is not explicily allowed by any type definition nor any extended metadata entry.

Cause: An attempt was made to customize a node that was not customizable.

Action: If the attempted customization is valid, the customization restrictions need to be modified to provide this ability. The customization restrictions can be defined in: the XML schema definition, standalone XML file or an extended metadata file. Also check the customization policy for the MDS session in use and the customization configuration.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02407: Customization of {0} is not allowed because the local reference was not found in the document.

Cause: An enquiry about the customizability of a node supplied a local reference that wasn't found in the document.

Action: Ensure that the local reference applies to the document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02408: The operation {0} on the {1} node is not allowed because the metadata object reference was not found in the change event.

Cause: A document change is not allowed because the metadata object reference was null.

Action: Ensure that the change document exists.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02500: Cannot find a valid MDSSession object for accessing the MDS document using ORAMDS URL

Cause: A valid MDSSession object was not set before accessing the document using the "oramds:///" protocol.

Action: Use the MDSURLHelper.setMDSSession() method to set a valid MDSSession object before accessing MDS documents using the oramds protocol.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02501: cannot load the ORAMDS URL "{0}" because MDS session could not be created or resolved

Cause: An error occurred while creating or resolving an MDS session object.

Action: Look for messages describing the cause exception in the error message log for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02600: configuration migration failure because the configuration document contains more than one mds-config element

Cause: The given configuration document contained more than one mds-config element.

Action: Correct the configuration document to contain a single mds-config element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02601: configuration migration failure because it contains more than one persistence-config element

Cause: The configuration document contained more than one persistence-config element.

Action: Correct the configuration document to contain a valid persistence-config element.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02602: configuration migration failure because it contains more than one metadata-stores element

Cause: The configuration document contained more than one metadata-stores element

Action: Correct the configuration document to be a valid 10.1.3 configuration document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02603: configuration migration failure because it contains an invalid metadata-store element

Cause: The configuration document contained an invalid metadata-store element.

Action: Correct the configuration document to be a valid 10.1.3 configuration document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02700: The resource "{0}" cannot be updated by tenant "{1}".

Cause: The given resource could not be updated by the current tenant because it was not available in current tenant's scope.

Action: Verify that the resource is being updated in the same scope of the tenant who updates the resource.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02702: Tenant scoped PManager instance cannot be created for tenant {0} because given PManager instance does not have multitenancy enabled.

Cause: The PManager instance used here did not have multitenancy enabled but an attempt was made to create tenant scoped PManager instance.

Action: Verify that the PManager instance being passed has multitenancy support enabled.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02703: Tenant scoped PManager cannot be created for tenant "null".

Cause: The PManager instance used here had multitenancy support enabled but an attempt was made to create tenant scoped PManager instance with "null" tenant.

Action: Create scoped PManager instance for valid tenant id.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02704: Cannot create tenant scoped PManager instance using another tenant scoped PManager instance.

Cause: An attempt was made to create tenant scoped PManager using another scoped PManager instance.

Action: Create a tenant scoped PManager using an unscoped PManager instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02705: Cannot create PContext using an unscoped PManager instance.

Cause: Creating PContext using an unscoped PManager instance was not allowed.

Action: Use PManager instance that is scoped for a tenant to create PContext.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02706: Cannot create PTransaction using an unscoped PManager instance.

Cause: Creating PTransaction using an unscoped PManager instance was not allowed.

Action: Use PManager instance that is scoped for a tenant to create PTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02707: PContext with tenant id {0} cannot be used in scoped PManager with tenant id {1}.

Cause: Tenant id attached to PContext and the tenant id of tenant scoped PManager to which it was passed did not match.

Action: Create PContext from the tenant scoped PManager to which it is passed.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02708: PManager instance is being used after it has been released.

Cause: PManager instance was being used after it had been released.

Action: Create a new PManager.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02709: Configuration change operation "{0}" on scoped PManager is not allowed for the tenant {1}. Only global tenant is allowed to change the configuration settings in PManager.

Cause: A non global tenant attempted to change configurations in scoped PManager.

Action: Use global tenant scoped PManager to change the configuration settings.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02710: Operation "{0}" is not allowed in unscoped PManager.

Cause: A tenant aware operation was invoked in an unscoped PManager instance.

Action: Use a global or tenant scoped PManager to do the operation.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02711: No tenant operations are allowed on MetadataStoreConnection not associated with any tenant id.

Cause: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.

Action: Create a new MetadataStoreConnection with a valid tenant id.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02712: The operation {0} is not allowed in this MetadataStoreConnection to database store because the MetadataStoreConnection is not attached to any tenant id.

Cause: A tenant aware operation was invoked in MetadataStoreConnection to database store which did not have any tenant id attached.

Action: Create a new MetadataStoreConnection with a valid tenant id.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02713: PContext associated with tenant {0} cannot be used with MetadataStoreConnection associated with different tenant {1}. Operation {2} failure.

Cause: The tenant id attached to PContext and MetadataStoreConnection did not match.

Action: Use PContext with same tenant id as the one attached to metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02714: Creating metadata store connection for tenant {0} is not allowed in non multitenant application.

Cause: An attempt was made to create metadata store connection for non global tenant in non multitenant application.

Action: Use global tenant id to create metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02715: No tenant scoped PManager instances can be created on already released PManager instance.

Cause: An attempt was made to create a tenant scoped PManager instance on already released PManager instance.

Action: Create new PManager instance using a PConfig then try creating scoped PManager instance.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02720: Cannot rename the document {0} to {1} as the new tenant scope does not match the original tenant scope.

Cause: The new name for the document was configured to a different tenant scope to the old document name.

Action: Provide a new valid document name that maps to the same tenant scope as the original document.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02721: PResource {0} for tenant {1} cannot be used with MetadataStoreConnection that is associated with different tenant {2}. Operation {3} failure.

Cause: The tenant ids of the PResource and the MetadataStoreConnection did not match.

Action: Use PResource with same tenant id of the one attached to metadata store connection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02722: Mar Lineage can be created by global tenant only. Creating MAR lineage is not supported for tenant {0}.

Cause: A non-global tenant attempted to create MAR lineage which is not supported. MAR lineage creation is allowed only for global tenant currently.

Action: Create MAR lineage from global tenant context.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02723: Operation "{0}" is not supported in Sandbox currently.

Cause: Unsupported operation was invoked in Sandbox instance.

Action: This operation is not supported in Sandbox currently.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02724: The ResourceName that is attached to tenant scope {0} is not allowed in SandboxPTransaction that is attached to the different tenant scope {1}. Operation {2} failure.

Cause: Tenant scope for ResourceName and SandboxPTransaction did not match.

Action: Use ResourceName with same tenant scope of the one attached to SandboxPTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02725: The Label {0} that is attached to tenant {1} is not allowed in MetadataStoreConnection that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for Label and MetadataStoreConnection did not match.

Action: Use label with same tenant id of the one attached to MetadataStoreConnection.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02726: The tenant {0} that is attached to PDocument {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for PDocument and SandboxPTransaction did not match.

Action: Use PDocument with same tenant id of the one attached to SandboxTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02727: The tenant {0} that is attached to Label {1} is not allowed in SandboxPTransaction that is attached to different tenant {2}. Operation {3} failure.

Cause: Tenant id for Label and SandboxPTransaction did not match.

Action: Use label with same tenant id of the one attached to SandboxPTransaction.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02728: The tenant {0} that is attached to {1} {2} is not allowed in Sandbox that is attached to different tenant {3}. Operation {4} failure.

Cause: Tenant id attached and Sandbox did not match.

Action: Use tenant id same as the one attached to Sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02729: The tenant scope {0} that is attached to {1} is not allowed in Sandbox that is attached to the different tenant scope {2}. Operation {3} failure.

Cause: Tenant scope attached and Sandbox did not match.

Action: Use tenant scope same as the one attached to Sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02730: Error in deprovisioning the tenant {0}. Unable to delete the resources in {1}.

Cause: Tenant resources might be on read-only store.

Action: Verify that tenant resources exist on a writable store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02731: Tenant specific operations cannot be done in multitenant disabled environment for tenant {0}.

Cause: An attempt was made to do tenant specific operations in Multitenant disabled environment.

Action: Enable the multitenant feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02732: TenantId cannot be created for the value "{0}".

Cause: TenantId could not be created with negative values or a value with more than 18 digits.

Action: Use positive values with max of 18 digits in decimal format to create a valid TenantId object.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02733: Rename across multiple tenant stripes is not supported on this store.

Cause: The store does not support writing to multiple tenant stripes or multitenancy is not enabled.

Action: Enable the multitenant feature.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02800: The label "{0}" cannot be provided as null for label based transfer.

Cause: The label was provided as null for label based transfer.

Action: Provide valid label name for label based transfer.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02801: Document {0} with scope {1} cannot be transferred by tenant {2}.

Cause: The given document could not be transferred from source store by current tenant because the document was not in the scope of current tenant.

Action: Ensure that document being transferred mapped to current tenant scope.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02802: Transfer is not supported for multitenant MDSInstance with file store.

Cause: Either source or target MDSInstance has multitenancy enabled and configured with file store.

Action: Use a non multitanant MDSInstance with file store.
Level: 1

Type: ERROR

Impact: Configuration

MDS-02803: List of patterns to select the MOs are either empty or null.

Cause: List of MOPatterns are empty or null.

Action: Ensure that valid list of MOPatterns are provided.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-02804: Layer name "{0}" configured in CustLayerFilter to remove customizations, contains patterns.

Cause: Layer name contains patterns.

Action: Ensure that layer name doesn't contain any patterns.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-05786: Unable to deploy the metadata archive: {0}.

Cause: Metadata archive (MAR) is corrupt.

Action: Validate that the metadata archive (MAR) is valid and readable.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05787: Partition name is not specified in adf-config.xml file.

Cause: A property with name partition-name was not found as a child of the metadata-store element.

Action: Specify the target partition as a child property of the metadata-store element in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05788: Unable to find the JNDI datasource in the file adf-config.xml.

Cause: A property with name jndi-datasource was not found as a child of the metadata-store element.

Action: Specify the JNDI datasource a child property of the metadata-store element in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05789: Unable to deploy the metadata archive.

Cause: Metadata archive (MAR) was not found.

Action: Ensure that the metadata archive (MAR) is packaged with the application.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05790: The metadata store definition is either missing or incorrectly specified in the application configuration.

Cause: The metadata store definition is either missing or incorrectly configured in the file adf-config.xml.

Action: Ensure that the metadata store definition is present and contains the correct repository configuration
Level: 1

Type: ERROR

Impact: Configuration

MDS-05791: An error occurred during the deployment of the metadata archive (MAR) {0}.

Cause: Details are usually given in the cause exception. Look for messages describing the cause exception and take the appropriate action.

Action: Ensure that the metadata store configuration is correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05792: Unable to load MDS configuration from "{0}"

Cause: The MDS configuration is either not defined or incorrect.

Action: Ensure that the MDS configuration is correctly defined.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05793: Metadata path {2} for partition {1} of MDS file repository {0} specified in adf-config.xml is either invalid or unreachable.

Cause: The metadata path named in the error message for the MDS file repository partition cited in the error message was either invalid or unreachable.

Action: Ensure that the MDS file repository named in the error message is registered and that the metadata partition cited in the error message is configured with a valid metadata path in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05794: Unable to load MDS persistence configuration from "{0}"

Cause: The MDS persistence configuration is either not defined or incorrect.

Action: Ensure that the MDS persistence configuration is correctly defined.
Level: 1

Type: ERROR

Impact: Configuration

MDS-05795: Invalid value "{0}" specified in the content-config of the application's configuration

Cause: Only restriction type CUSTOMIZATIONS is supported in content-config. It is only allowed with path "/" and no file extension.

Action: Ensure that the MDS persistence configuration is correctly defined.
Level: 1

Type: ERROR

Impact: Configuration

MDS-10001: Error:

Cause: An error occured. Details are usually given in the accompanying messages.

Action: Look for messages describing the cause and take the appropriate action.
Level: 1

Type: ERROR

Impact: Data

MDS-10003: The specified {0} argument is null or empty.

Cause: A required program argument was null or empty.

Action: Record any accompanying exception messages and contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-10009: The transfer of the document {0} is not successful.

Cause: Document transfer failed

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10010: Deleting the document {0} is not successful.

Cause: Document deletion failed

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10011: The operation on {0} has been rolled back. Total number of documents failed during the operation is {1}.

Cause: The transfer was rolled back

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10012: The operation has failed.

Cause: The operation has failed.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: WARNING

Impact: Data

MDS-10013: {0} operation started.

Cause: Transfer started.

Action: Transfer started, no action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10014: {0} is completed. Total number of documents successfully processed : {1}, total number of documents failed : {2}.

Cause: Transfer complete.

Action: Check any accompanying messages to decide if any action is required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10015: Failure occurred while committing the {0} operation. The operation has been rolled back.

Cause: Failure occurred while committing the operation.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-10016: The operation on {0} has been rolled back. The post transfer label {1} could not be created.

Cause: Failure occurred when creating the post transfer label.

Action: Examine any accompanying messages to decide if further action is required.
Level: 1

Type: ERROR

Impact: Data

MDS-10017: The target store does not support deployment management. Given application name "{0}" and deployment module name "{1}" could not be persisted as deployment information in store.

Cause: The target store does not support deployment management.

Action: No action required. The documents will be transferred without the deployment information attached. If you want to store deployment information as well, configure a metadata store that supports deployment management, typically a DB store.
Level: 1

Type: WARNING

Impact: Data

MDS-10018: The transfer restriction {0} is not supported in target store. All the documents will be transferred to target store.

Cause: Given transfer restriction is not supported in target store.

Action: No action required. The given restriction will not be applied to the transfer, all the documents will be transferred to target store.
Level: 1

Type: WARNING

Impact: Data

MDS-10019: The deployment information for application name "{0}" and module name "{1}" ignored since transfer operation is of type "{2}".

Cause: The deployment information will not be processed in transfer operation type other than "Deployment".

Action: No action required. Given deployment information will not be processed in the current transfer operation.
Level: 1

Type: WARNING

Impact: Data

MDS-10020: Querying checksum data from target repository to avoid transferring unchanged documents.

Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10022: Query to get the checksum of the documents from target repository completed successfully.

Cause: To apply transfer restriction CHANGED, transfer queries the target repository to check whether documents being transferred already exist with same content.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10023: No valid exclusion rules are specified in mds-transfer-config.xml to preserve documents in target store.

Cause: No valid namespaces or metadata object names specified in /meta-inf/mds-transfer-config.xml to preserve the documents in target store.

Action: No action required.
Level: 1

Type: WARNING

Impact: Data

MDS-10024: Preparing the list of documents to be excluded during transfer as per the configuration given in mds-transfer-config.xml.

Cause: To preserve the documents in target store as specified in the given /meta-inf/mds-transfer-config.xml, MDSTransfer prepares the list of documents to be excluded by looking at source and target stores.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Data

MDS-10025: Following metadata paths are configured in mds-transfer-config.xml to preserve existing documents under this metadata path in target repository. Configured metadata paths are as follows {0}:

Cause: Some metadata paths are configured in mds-transfer-config.xml to preserve existing documents in target repository.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10026: Following Metadata object names are configured in mds-transfer-config.xml to preserve existing metadata objects with same name in target repository. Configured metadata object names are {0}:

Cause: Some metadata object names are configured in mds-transfer-config.xml to preserve existing documents in target repository.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10027: To preserve documents in target store, the following documents from source store are marked as excluded by transfer {0}.

Cause: To preserve documents in target store, some documents from source store are marked as excluded by transfer.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-10030: Sandbox {0} created as part of Import operation is not destroyed after import failed.

Cause: A Critical Write error on database side has occured. Look for specific exception in the log file.

Action: Destroy unused sandbox from metadata repository. Contact application administrator for assistance.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11001: The type information for "{0}" is not obtainable though the document exists in the MetadataStore.

Cause: Could not get type information for a document, a possibly non-wellformed XML document.

Action: Examine the document
Level: 1

Type: WARNING

Impact: Data

MDS-11002: The type information for "{0}" is not obtainable because of exception "{1}"

Cause: Failed to get type information because an exception was raised.

Action: Examine the exception and the document.
Level: 1

Type: WARNING

Impact: Data

MDS-11003: Failed to force timestamp advance on file {0}: original timestamp = {1}, new timestamp = {2}.

Cause: Failed to advance the timestamp on a file which is being saved.

Action: Examine the file and its permissions.
Level: 1

Type: WARNING

Impact: Data

MDS-11006: Directory {0} does not exist.

Cause: The value of a name condition package did not have a corresponding file system directory.

Action: Check if the directory was expected and determine why it is not present.
Level: 1

Type: NOTIFICATION

Impact: Files

MDS-11007: Skipping directory {0} because {1} does not match the condition.

Cause: The query considered the given directory, but it could only contain documents that would not match the query.

Action: If you expected results from the directory, check that the query is correctly specified.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

MDS-11008: Skipping directory {0} because it is a filestore root.

Cause: The query considered the directory, but it was another root path of the metadata store. This can arise when file store configuration includes multiple root paths and one of these is contained in another.

Action: If you expected results from the directory, check that the file store is configured correctly.
Level: 1

Type: NOTIFICATION

Impact: Files

MDS-11009: Skipping directory {0} because {1} is not a valid package name.

Cause: The query skipped the directory because the corresponding package name is invalid.

Action: If you expected results from the directory, check the directory name for validity.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

MDS-11010: Document cache {0} exceeds its maximum number of entries {1}, so the cache is cleared.

Cause: The document cache exceeded its defined maximum size so it was cleared. If memory allows, the cache should be large enough for all documents for optimum performance but this is not required.

Action: Edit the adf-config.xml file and increase the size of the document cache.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11011: Attempting to get failover connection to retry the operation because the database connection failed.

Cause: The connection to the database failed.

Action: No action is required. The database is configured with FCF so failover will be attempted.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11012: Cache collision has been detected when adding key {0}, label set {1}, sandbox name {2}, scope {3}.

Cause: The described document was being added to the cache, but it was already present. This can be caused by an incorrect miss in the preceding lookup, or very rarely by the document having been just inserted by another thread.

Action: If this occurs frequently, contact Oracle Support Services.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

MDS-11013: Cannot store the object of type {0} in the Java Object Cache because the cache or cache region is full

Cause: A CacheFullException or RegionFullException was reported when attempting to store an object in the Java Object Cache.

Action: Consider increasing the size of the configured MDS Cache by modifying the cache-config entry in adf-config.xml.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11014: Purge-Repos Diagnostics [auto-purge, partition-name, partition-id, #versions purged]: [{0}, {1}, {2}, {3}].

Cause: An auto-purge occurred on a metadata-store.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11016: MDS JSP Integration has been configured in Developer Mode to allow changes to files to be detected. Do not use this mode for production or performance testing.

Cause: Developer Mode is configured as a servlet initialisation parameter either explicitly or because the application is being run within JDeveloper.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11017: Started creating the final archive file at {0}.

Cause: ArchiveMetadataStore has started to create final archive file with all the changes done on the archive file so far.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11018: The final archive file has been created successfully. The archive file is available at {0}.

Cause: ArchiveMetadataStore has created final archive file with all the changes done on the archive file so far.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Other

MDS-11019: The default CharSet {0} is not a unicode character set. File names with non-ASCII characters may not operate as expected. Check locale settings.

Cause: The Java default CharSet is used to convert file names to and from Java Strings. When this CharSet is a non-unicode character encoding, filenames that contain non-ASCII characters may not be correctly mapped to Java characters.

Action: Check the locale environment variable settings for the process that is running the JVM that MDS is running in to ensure that a UTF encoding is being used. For example, the LC_ALL and LANG settings may be relevant.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11020: Cannot delete the intermediary archive file {0}.

Cause: The intermediary archive file could not be deleted.

Action: Try deleting the file outside of MDS.
Level: 1

Type: WARNING

Impact: Other

MDS-11023: MDS Remote Notifications: Coherence is not configured to use unicast and no cluster name is specified so remote notification is not enabled.

Cause: MDS remote notification only works if the Coherence configuration specifies unicast or a cluster name.

Action: Unicast can be set by either specifying a unicast-listener in your Coherence cluster-config or by system property tangosol.coherence.wk. A cluster-name can be set either as part of a member-identity in your cluster-config or by system property tangosol.coherence.cluster.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11026: Ignoring the duplicate MDS component configuration file URL "{0}" found on the classpath.

Cause: A duplicate URL for an MDS component configuration file was found on the classpath.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11027: Some metadata is configured to be stored as xml-stream. However it will be ignored because no metadata store configured for this application supports storing metadata in that form.

Cause: xml-stream content type was configured for some metadata content, but no metadataStore supports the feature.

Action: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11028: Some metadata is configured to be stored as xml-stream. However it will be ignored because the corresponding metadata store, with class name: {0}, repository name: {1}, partition name: {2}, does not support storing metadata in that form.

Cause: xml-stream content type was configured for some metadata content, but the metadata store did not support the feature.

Action: No action required if not using xml-stream content type is acceptable. Otherwise, to enhance MDS repository performance, ensure that the metadata store supports xml-stream feature.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11029: MetadataStore configuration for metadata-store-usage "{0}" is invalid. However the MetadataStore is ignored because it is not referenced by any namespace mapping.

Cause: MetadataStore class or some of its properties were not valid.

Action: Ensure that the MetadataStore class exists and all required properties are valid.
Level: 1

Type: NOTIFICATION

Impact: Configuration

MDS-11030: Failed to get schema version from registry for repository "{0}" because of exception: {1}

Cause: Either the DataSource definition for the repository is no longer valid or the MDS schema is not created using RCU.

Action: Ensure the DataSource connection is valid or the schema is created using RCU.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11032: Registered grammar using remote schema "{0}". In design time (JDev) environment, it is recommended to use local resources.

Cause: Remote schema was referred with http URI. In design time environment, recommendation is to use local resources.

Action: Replace it with local copy of schema.
Level: 1

Type: WARNING

Impact: Configuration

MDS-11100: MetadataObject.getBaseMO() found a mismatched CacheAccess in the cache. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}, name={8}, GUID={9}].

Cause: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.

Action: Check the MOName and guid are correct and there are no duplicate Guids in the metadata store.
Level: 1

Type: WARNING

Impact: Other

MDS-11101: MetadataObject.getBaseMO() recursing too deep. [refNoGUID={0}, guidRef={1}, mdxLookupKey={2}, isLabelledRead={3}, baseDocLabel={4}, setSandboxName={5}, cacheAccess={6}, doc={7}].

Cause: CacheAcces does not match the the given MOReference/Guid combination. The metadata object will not be cached.

Action: Check the data in the metadata store to determine the cause.
Level: 1

Type: WARNING

Impact: Other

MDS-11102: The MDS session was created by the ADF framework with a transaction key for its "single flush" feature, and the call to {0} is restricted to that framework. This call does not use that transaction key and although working now, will fail with an exception in future. To find the originator of the call, set the log level for logger "oracle.mds.transkey" to FINEST. Note that the ADF framework manages the MDS session created for the request so an explicit call to {0} should be removed.

Cause: A call was made to a restricted method on the MDS session and that call should be removed as it is liable to fail in later releases.

Action: Identify the caller and ensure that the call to this method is removed.
Level: 1

Type: WARNING

Impact: Other

MDS-90013: The metadata partition with name "{0}" does not exist in the metadata repository "{1}".

Cause: The metadata partition with the specified name was not found in the metadata repository.

Action: Create a metadata partition with the specified name in the metadata repository before trying this operation.
Level: 1

Type: ERROR

Impact: Topology

MDS-90014: cannot update the metadata because the application is read-only

Cause: No metadata update was made because the ReadOnlyMode attribute was enabled.

Action: Disable the ReadOnlyMode attribute of the target application configuration.
Level: 1

Type: ERROR

Impact: Topology

MDS-90015: The metadata repository with name "{0}" does not exist.

Cause: The metadata repository with the specified name was not found.

Action: Verify that the repository name is spelled correctly. If the repository does not exist, create one with the specified name and try again.
Level: 1

Type: ERROR

Impact: Topology

MDS-90016: There are no applications deployed to partition "{0}".

Cause: An attempt was made to perform this operation on a partition that is not associated with a deployed application.

Action: Specify a partition that is associated with a deployed application.
Level: 1

Type: ERROR

Impact: Topology

MDS-90017: The application to be used for this operation is not specified.

Cause: Could not determine which application configuration to use for this operation since there is more than one application deployed to partition "{0}".

Action: Specify an application that is deployed to partition "{0}" to be used for this operation.
Level: 1

Type: ERROR

Impact: Topology

MDS-90018: Application "{1}" is not deployed to partition "{0}".

Cause: The specified application was not deployed to the specified partition.

Action: Specify an application that is deployed to the partition.
Level: 1

Type: ERROR

Impact: Topology

MDS-90019: cannot set the user property on the driver: {0}

Cause: A problem occurred while setting the user property on the driver.

Action: Ensure that the database server is running properly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90020: Metadata store cannot be assigned to server "{0}".

Cause: A problem occurred while assigning resource to the server.

Action: Ensure that the server is running properly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90021: Metadata path {0} is invalid.

Cause: The path used to create a FileMetadataStore was invalid. It must point to a directory.

Action: Correct the metadata path.
Level: 1

Type: ERROR

Impact: Topology

MDS-90022: The host name of the database repository cannot be empty.

Cause: The host name of the database repository was empty or null.

Action: Use a valid host name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90023: The database name of the database repository cannot be empty.

Cause: The database name of the database repository was empty or null.

Action: Use a valid database name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90024: The user name of the database repository cannot be empty.

Cause: The user name of the database repository was empty or null.

Action: Use a valid user name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90025: The password of the database repository cannot be empty.

Cause: The password of the database repository was empty or null.

Action: Use a valid password.
Level: 1

Type: ERROR

Impact: Topology

MDS-90026: The server name cannot be empty.

Cause: The server name was empty or null.

Action: Use a valid server name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90027: cannot find server "{1}" to register the metadata repository "{0}"

Cause: The server name was invalid.

Action: Use a valid server name.
Level: 1

Type: ERROR

Impact: Topology

MDS-90028: Metadata repository with name "{0}" already exists.

Cause: Metadata repository with the specified name already exists.

Action: Verify that the repository name is spelled correctly. If the repository already exists, create one with a different name and try again.
Level: 1

Type: ERROR

Impact: Topology

MDS-90029: The metadata db repository with name "{0}" does not exist.

Cause: The metadata db repository with the specified name was not found.

Action: Verify that the db repository name is spelled correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90030: The metadata file repository with name "{0}" does not exist.

Cause: The metadata file repository with the specified name was not found.

Action: Verify that the file repository name is spelled correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90031: The JDBC resource of metadata db repository "{0}" cannot be found.

Cause: The JDBC resource was not found.

Action: Verify that the metadata db repository is set up correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90032: The metadata store of metadata file repository "{0}" cannot be found.

Cause: The metadata store was not found.

Action: Verify that the metadata file repository is set up correctly.
Level: 1

Type: ERROR

Impact: Topology

MDS-90033: unknown DB vendor code: "{0}"

Cause: The DB vendor code is invalid.

Action: Use a valid DB vendor code, such as 0 (ORACLE), 1 (MSSQL), or 2 (IBMDB2).
Level: 1

Type: ERROR

Impact: Topology

MDS-90034: The source directory or archive "{0}" for importing metadata is invalid.

Cause: The directory or archive location used to import metadata was invalid. It must point to a valid, existing directory or archive.

Action: Correct the source directory or archive location.
Level: 1

Type: ERROR

Impact: Topology

MDS-90035: The target directory or archive "{0}" for exporting metadata is invalid.

Cause: The directory or archive location used to export metadata was invalid. It must point to a valid location.

Action: Correct the target directory or archive file location.
Level: 1

Type: ERROR

Impact: Topology

MDS-90036: The application does not have a valid MAR file path.

Cause: The MAR path used to import MAR was invalid. It must point to a valid, existing MAR file.

Action: Make sure the MAR file exists and is located in the correct directory of the application.
Level: 1

Type: ERROR

Impact: Topology

MDS-90037: The archive "{0}" does not contain valid contents.

Cause: The archive used to import metadata was invalid. It must be to a valid, existing zip or jar file.

Action: Make sure the archive is valid.
Level: 1

Type: ERROR

Impact: Topology

MDS-90038: The database authentication alias "{0}" already exists. To reuse the same authentication alias, try the operation again without specifying user and password.

Cause: An attempt was made to configure a database authentication alias that already existed in Websphere server.

Action: Delete the existing authentication alias and try again, or specify a new authebtication alias, or reuse the existing authentication alias by not specifying user and password.
Level: 1

Type: ERROR

Impact: Topology

MDS-90039: The database authentication alias "{0}" cannot be found. To create the authentication alias, try the operation again with user and password specified.

Cause: An attempt was made to use a database authentication alias that was not configured in Websphere server.

Action: Make sure the specified database authentication alias is properly configured in Websphere server, or automatically create the authentication alias by specifying user and password.
Level: 1

Type: ERROR

Impact: Topology

MDS-90040: failed to connect to database

Cause: An error occurred when trying to connect to database.

Action: Make sure the database connection details are correct. Look at the cause exception for more details.
Level: 1

Type: ERROR

Impact: Topology

MDS-90041: Customization layer values are not supported for "excludeCustFor" parameter.

Cause: One or more customization layer values was specified for "excludeCustFor" parameter.

Action: Make sure there are no customization layer values specified for "excludeCustFor" parameter.
Level: 1

Type: ERROR

Impact: Topology

MDS-90042: "{0}" is not a valid tenant name.

Cause: The specified tenant was not provisioned in the specified partition and repository.

Action: Specify a valid tenant name.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90043: This operation cannot be performed by the tenant named "{0}". It can only be invoked by the "{1}" tenant.

Cause: The specified tenant was not provisioned in the partition and repository provided.

Action: Execute this operation as GLOBAL tenant.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90044: This operation cannot be performed because the WebLogic edit session has been locked by a different user.

Cause: The WebLogic edit session has been locked by a different user.

Action: Retry the operation after the edit session lock is released.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90143: "{0}" is not a valid component name.

Cause: The specified component name is invalid.

Action: Specify a valid audit component name that uses only letters.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90144: Error registering audit event definitions for component "{0}".

Cause: The audit event definitions could not be registered.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90145: Error occurred when raising audit event "{0}" for component "{1}".

Cause: The audit event was not registered or an unknown error occurred in the auditing system.

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90146: Error occurred when checking if "{0}" is auditable.

Cause: An unknown error occurred when checking if auditing is enabled for the component "{0}".

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90147: Error occurred when checking if the component "{0}" is auditable.

Cause: An unknown error occurred when checking if auditing is enabled for the event "{1}" defined for the component "{0}".

Action: Refer to the error messages that describe the cause exception in the application logs for more information on the actual reason for failure.
Level: 1

Type: ERROR

Impact: Configuration

MDS-90243: Content auto merge failed for MO part "{0}" with change type "{1}" because its type is not registered for auto merge.

Cause: The specified MOType is not registered for auto merge functionality.

Action: Register the MOType for auto merge functionality.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90244: Content auto merge failed for MO part "{0}" with change type "{1}" because its base document is not accessible for read from any configured metadata stores.

Cause: Base document is not accessible for read.

Action: Make sure base document is available for read through any of configured metadata stores.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90245: Content auto merge failed for MO part "{0}" with change type "{1}" because both base and customization MOParts have conflicts and base MOPart is not a stub.

Cause: Base MOPart is not a stub document.

Action: This is unsupported case. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90246: Content auto merge failed for MO part "{0}" with change type "{1}" because mainline contains conflicting change type "{2}" for the same MOPart.

Cause: There were conflicting changes for MetadataObject between sandbox and mainline and cannot be resolved by content auto merge.

Action: Contact Application Administrator to resolve these conflicts manually or perform the changes again in a new sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90247: Content auto merge failed for MOPart "{0}" with change type "{1}", because conflicts identified for metadata object include changes for non tip or non configured customization layer "{2}".

Cause: Conflicts detected for given metadata object include changes for non tip or non configured customization layer.

Action: This is unsupported case. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90248: Content auto merge failed for MetadataObject "{0}".

Cause: Content auto merge failed for specified MO.

Action: Please check each MOPart exception for detailed reasons.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90249: Content auto merge failed for MetadataObject "{0}", because the MO constitutes more than one customization MOPart for the customization layer "{2}".

Cause: Customization layer yields multiple layer values.

Action: This is unsupported case. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90300: Following metadata content auto-merge exception(s) occurred - * {0}

Cause: One or more metadata content auto-merge exception(s) occurred.

Action: For more details, use getContentAutoMergeExceptions() method on MOPartChangeContentAutoMergeException instance.
Level: 1

Type: ERROR

Impact: Data

MDS-90301: Unexpected content auto-merge error

Cause: An unexpected content auto-merge error occurred.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-90302: Invalid input documents for content auto-merge operation.

Cause: Invalid documents are provided to perform content auto-merge operation.

Action: Provide valid documents.
Level: 1

Type: ERROR

Impact: Data

MDS-90303: Limited support available for XSD content auto-merge operation.

Cause: Unable to auto-merge changes being made by the request or by another user done to XSD metadata object.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

MDS-90304: Unable to auto-merge merge-unit with local reference "{0}" in metadata object "{1}" due to conflicting changes being made by the request or by another user.

Cause: Encountered merge-unit auto-merge conflict while performing content auto-merge.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90305: Type annotation automergeChildListOrderDefault set on element definition of root element in metadata object "{0}" does not have valid value. Valid values are "childListOrderNotImportant" and "childListOrderImportant".

Cause: Invalid value provided for automergeChildListOrderDefault type-annotation.

Action: Provide valid value for automergeChildListOrderDefault type-annotation. Valid values are "childListOrderNotImportant" and "childListOrderImportant".
Level: 1

Type: ERROR

Impact: Data

MDS-90340: Unable to auto-merge changes done to attribute(s) on element with local reference "{0}" in metadata object "{1}" due to conflicting changes being made by the request or by another user.

Cause: Encountered element attribute(s) auto-merge conflict while performing content auto-merge.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90343: Sandbox "{0}" Apply operation failed for MO part "{1}" since conflict were identified with mainline changes for MO Part "{2}" that violates the relationship and dependency constraints.

Cause: Sandbox changes violate some dependency constraints with mainline changes.

Action: Contact Application Administrator to resolve these conflicts manually or perform the changes again in a new sandbox.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90344: Sandbox "{0}" apply operation with content auto merge failed.

Cause: Sandbox apply operation with auto merge failed.

Action: Please check each MO exception for detailed reasons.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90345: Failure to get conflicts for sandbox

Cause: Target label is older than the sandbox mainline label.

Action: Specify a target label which is later than current label.
Level: 1

Type: ERROR

Impact: Programmatic

MDS-90350: Unable to auto-merge changes done to simple type element/simple-base complex type element with local reference "{0}" in metadata object "{1}" due to conflicting changes being made by the request or by another user.

Cause: Encountered simple type element/simple-base complex type element auto-merge conflict while performing content auto-merge.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90360: Element insertion auto-merge failed for element with local reference "{0}" in metadata object "{1}" due to conflicting changes done by another user.

Cause: Encountered element insertion auto-merge conflict while performing content auto-merge.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90361: Content auto-merge failed due to conflicting element insertion with local reference "{0}" in metadata object "{1}" done by another user.

Cause: Encountered element insertion auto-merge conflict while performing content auto-merge.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90370: Unable to auto-merge element deletion with local reference "{0}" in metadata object "{1}" due to conflicting changes being made by the request or by another user.

Cause: Encountered element deletion auto-merge conflict while performing content auto-merge.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90390: No support to auto-merge move operation

Cause: Encountered move operation while performing content auto-merge operation.

Action: Please resolve the conflict before attempting auto-merge operation again.
Level: 1

Type: ERROR

Impact: Data

MDS-90400: Element with local reference "{0}" in metadata object "{1}" does not have childListOrderNotImportant type-annotation

Cause: Child-list of the underlying element was modified as part of content auto-merge operation.

Action: If the child-list of the underlying element should be auto-merged, attach the needed childListOrderNotImportant type-annotation.
Level: 1

Type: ERROR

Impact: Data

MDS-90401: Type annotation "automerge" for child-list order preference on element with local reference "{0}" in metadata object "{1}" does not have valid value. Valid values are "childListOrderNotImportant" and "childListOrderImportant"

Cause: Child-list of the underlying element was modified as part of content auto-merge operation.

Action: Provide valid value for "automerge" type-annotation. Valid values are "childListOrderNotImportant" and "childListOrderImportant".
Level: 1

Type: ERROR

Impact: Data

MDS-91001: MDS domain runtime MBean is not available. "{0}" operation failure.

Cause: MDS domain runtime MBean was not available in the server.

Action: Ensure the MDS domain runtime MBean is available in the server.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91002: MDS Application runtime MBean for "{0}" is not available. "{1}" operation failure.

Cause: MDS Application runtime MBean was not available in the server.

Action: Ensure the MDS Application runtime MBean for the application is available in the server.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91003: Multiple MDSAppRuntimeMBean exist for "{0}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Provide the 'applicationVersion' parameter.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91004: MDS domain runtime MBean commands can be executed only from the Admin server. "{0}" operation failure.

Cause: WLST was not connected to the Admin server.

Action: Connect to an Admin server before executing the command.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91005: No connection to a "{0}" server exists. The operation "{1}" can be executed only in the online mode.

Cause: Command was executed in the offline mode.

Action: Ensure WLST/WSADMIN is connected to the server.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91006: Expecting a "{0}" for parameter "{1}" but encountering "{2}". "{3}" operation failure.

Cause: Parameter type passed to the command was not correct.

Action: Ensure the correct type of parameters are passed to the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91007: dbVendor should be one of ORACLE, MSSQL, IBMDB2, or MYSQL. "{0}" operation failure.

Cause: dbVendor value was not correct.

Action: Ensure the dbVendor value is one of ORACLE, MSSQL, IBMDB2, or MYSQL.
Level: 1

Type: ERROR

Impact: Data

MDS-91008: The "{0}" parameter is required. Provide a valid value and retry the operation.

Cause: Required parameter for the command was not given.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91009: Operation "{0}" failure.

Cause: Exception occurred during the execution of the command.

Action: Provide the required parameters for the command.
Level: 1

Type: ERROR

Impact: Data

MDS-91010: The "adf-config" element is not available in the given archive file. "{0}" operation failure.

Cause: The "adf-config" element is not available in the given archive file.

Action: Ensure the "adf-config" element is available in the adf-config.xml of the given archive file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91011: No "mds-config" element exists in the adf-config.xml of the given archive. "{0}" operation failure.

Cause: No mds-config element existed in the adf-config.xml file of the archive file.

Action: Ensure the "mds-config" element is available in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91012: Metadata repository connection type value should be either "File" or "DB". "{0}" operation failure.

Cause: Metadata repository connection type value is not correct.

Action: Ensure the metadata repository connection type value is either 'File' or 'DB'.
Level: 1

Type: ERROR

Impact: Data

MDS-91013: For the metadata repository''s DB connection type, JNDI location is a required parameter. "{0}" operation failure.

Cause: JNDI location not provided for DB connection type.

Action: Provide the JNDI location string while updating the repository connection to DB.
Level: 1

Type: ERROR

Impact: Data

MDS-91014: For the metadata repository''s File connection type, path location is a required parameter. "{0}" operation failure.

Cause: The path value was not provided for File connection type.

Action: Provide the path location string while updating the repository connection to File.
Level: 1

Type: ERROR

Impact: Data

MDS-91015: All parameters are required to update shared metadata repository configuration in adf-config.xml. At present, source archive has no connection details for the namespace "{0}". "{1}" operation failure.

Cause: Complete connection information was not provided to set the shared repository for the given namespace.

Action: Provide complete connection information in case the adf-config.xml file does not have any metadata repository connection information for the given namespace already.
Level: 1

Type: ERROR

Impact: Data

MDS-91016: All parameters are required to define new application metadata repository configuration in adf-config.xml. The source archive configuration does not contain any application metadata repository at present. "{0}" operation failure.

Cause: Complete connection information was not provided to set the application target repository.

Action: Provide complete connection information in case the adf-config.xml does not have any metadata repository connection information for the application target repository already.
Level: 1

Type: ERROR

Impact: Data

MDS-91017: The given namespace "{0}" to set the shared repository is not valid. Ensure that the namespace is available in the adf-config.xml file and it is not a sub-namespace of any other namespace. "{1}" operation failure.

Cause: The namespace provided to set the shared repository details is not valid.

Action: Ensure that the namespace is available in the adf-config.xml file and it is not a subnamespace of any other namespace in that file.
Level: 1

Type: ERROR

Impact: Data

MDS-91018: No namespaces are mapped to any shared repository in the source archive adf-config.xml configuration file. Shared repository details cannot be set. "{0}" operation failure.

Cause: No namespaces were mapped to any shared repository in the source archive adf-config.xml configuration file.

Action: To set the shared repository connections, ensure at least one namespace is mapped to shared repository in the source archive adf-config.xml file.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91019: Multiple MDSAppRuntimeMBean exist for application "{0}". Ensure that the "application" "node" and "server" parameters are correct. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Ensure that the "application" "node" and "server" parameters are correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91020: MDS Application runtime MBean for "{0}" is not available in server "{2}". Ensure server name and application name are correct. "{1}" operation failure.

Cause: MDS Application runtime MBean was not available in the server.

Action: Ensure the MDS Application runtime MBean for the application is available in the server. Ensure the server name and the application name are correct.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91021: Multiple MDSAppRuntimeMBean exist for "{0}" in server "{2}". To execute the command, parameter "applicationVersion" is required. "{1}" operation failure.

Cause: Multiple MDSAppRuntimeMBean for the application were found in the server.

Action: Provide the 'applicationVersion' parameter.
Level: 1

Type: ERROR

Impact: Configuration

MDS-91022: Parameter "{0}" cannot be an empty string. "{1}" operation failure.

Cause: The parameter is not allowed to be an empty string.

Action: Ensure the parameter has a correct value.
Level: 1

Type: ERROR

Impact: Data

MDS-91023: Parameter "{0}" contains at least one empty element. "{1}" operation failure.

Cause: The parameter is not allowed to contain one or more empty elements.

Action: Ensure every element specified in the parameter is correct.
Level: 1

Type: ERROR

Impact: Data

MDS-92000: Oracle Metadata Services schema upgrade is invalid.

Cause: Specified Metadata Services schema was updated but is invalid.

Action: Restore the Metadata Services schema from a backup and retry. Check the error messages in log file. Correct the problem before running the Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-92001: The upgrade is not supported from Oracle Metadata Services schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Oracle Metadata Services Upgrade Guide for supported versions to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

MDS-92002: Error in upgrading Oracle Metadata Services schema.

Cause: An unexpected error occurred during Oracle Metadata Services schema upgrade.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92003: Error occurred while verifying the character set in target Metadata Services schema

Cause: Some SQL error occurred while verifying the character set in target Metadata Services schema.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92004: Error occurred while closing the resources during Metadata Services schema upgrade

Cause: Some error occurred while closing the resources during Metadata Services schema upgrade.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92005: Error occurred while closing Metadata Services schema upgrade log files.

Cause: An unexpected error occurred while closing Metadata Services schema upgrade log files.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

MDS-92006: Oracle Metadata Service schema status is invalid.

Cause: Specified Oracle Metadata Services database schema was invalid.

Action: Check the error messages in log file. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

34 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:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10001: Case {0} not found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10002: No user {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10004: User is blocked

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10005: No questions registered {0} {1}

Cause:

Action:
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:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10008: Challenge Question Set is already reset.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10009: End Date is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10010: End Date should be in future.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-10011: Valid Application name or user group name is required.

Cause:

Action:
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:

Action:
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:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90010: Start time is required for schedule.

Cause:

Action:
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:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90016: To time is required for data filters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAAM-90017: From date should be before To date for data filters.

Cause:

Action:
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

35 OAB-00015 to OAB-960018

OAB-00015: Invalid name '%s' violates one of the following constraints: (1) must begin with a letter, (2) must be 4-40 characters in length, (3) must consist only of letters, 0-9, '-', and '_' characters

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-00101: Unable to delete a regular file {0}

Cause: (See message)

Action: Check permission of the file
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00102: Unable to make directory at {0}

Cause: (See message)

Action: Check permission of the parent directory
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00103: directory does not exist at {0}

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00105: Unable to create a temp file

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00201: Unable to list files in directory {0}

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00202: Unable to write {0} to zip stream.

Cause: Input resources is not found.

Action: Make sure not to delete any resources while file set creation is in progress.
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00301: No password was entered.

Cause: (See message)

Action: Enter a valid password to use.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-00302: Passwords do not match.

Cause: (See message)

Action: Type matching password.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-00303: Password is too short.

Cause: (See message)

Action: Enter a password with at least 7 characters.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-00304: Password is too long.

Cause: (See message)

Action: Enter a password with at most 75 characters.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-00305: Whitespace is not allowed in password.

Cause: (See message)

Action: Choose a password without whitespaces.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-00307: Failed to encrypt/decrypt a password.

Cause: (See message)

Action: The OVAB instance has been corrupted. Contact Oracle support.
Level: 1

Type: SET_AT_RUNTIME

Impact: Security

OAB-00310: Arithmetic exception occurred for agent={0}, nameOfResource={1}, chunkSize={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-00320: Unable to load native library.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: INCIDENT_ERROR

Impact: Files

OAB-00400: Invalid file path {0}.

Cause: The specified file does not exist.

Action: Ensure that the file at the specified location exists.
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00401: No read and write permissions on the file {0}.

Cause: The application does not have read and write permissions on the specified file.

Action: Ensure that the application has appropriate permissions on the specified file.
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00402: No read permissions on the file {0}.

Cause: The application does not have read permissions on the specified file.

Action: Ensure that the application has appropriate permissions on the specified file.
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00403: No write permissions on the file {0}.

Cause: The application does not have write permissions on the specified file.

Action: Ensure that the application has appropriate permissions on the specified file.
Level: 1

Type: SET_AT_RUNTIME

Impact: Files

OAB-00500: OVAB is unable to start because the AB_INSTANCE is running a different version ({0}/{1}) than the ORACLE_HOME ({2}/{3}).

Cause: (See message)

Action: Update the AB_INSTANCE to use an ORACLE_HOME with the same version.
Level: 1

Type: ERROR

Impact: Other

OAB-02031: Unable to obtain stream size to copy resource to remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-02032: Error while execing command "{0}" on remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-02033: Error while running command "{0}" via shell on remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-02034: Error setting up port forwarding through SSH.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02035: Unable to get SSH Session.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02039: Error attempting to check remote Acknowledgement for command {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02040: Error while copying resource "{0}" to remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02041: Unknown host {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02042: Error in underlying SSH layer while closing port forwarding.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02044: A SSH connection is already established.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02046: Unable to convert Password into byte[] for SSH session.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02050: Remote directory "{0}" does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02052: Unable to create SSH connection to machine {0}. Invalid username and/or private key file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-02053: Unable to create SSH connection to machine {0}. Invalid username and/or password.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05021: Error downloading assembly archive from EM Software Library.

Cause: (See message)

Action: Check the connection to EM Software Library and, if the remote directory is /tmp, specify another directory. Also verify that the permissions of the remote directory allow the EM Software Library user access.
Level: 1

Type: ERROR

Impact: Other

OAB-05023: Error downloading the assembly archive.

Cause: (See message)

Action: Check the connection to EM Software Library and, if the remote directory is /tmp, specify another directory. Also, verify that the permissions of the remote directory allow the EM Software Library user access.
Level: 1

Type: ERROR

Impact: Other

OAB-05030: Unable to download the archive as its state is "{0}" and not READY

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05100: Unable to find assembly archive "{0}" with version "{1}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05101: Error deleting assembly archive"{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05103: Unable to access file at location {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05104: Error copying a stream to file at location {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05105: Unable to obtain assembly archive with name "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05106: Error in accessing local assembly archive file for upload

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05107: Error in uploading assembly archive "{0}" to EM Software Library.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05109: No Assembly exists for version {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05110: Unable to parse the CreatedTime from EM Software Library. Time = "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05111: Unable to parse the UpdatedTime from EM Software Library. Time = "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05112: Unable to get assembly archive versions from EM Software Library

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05113: Unknown error returned from EM.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05120: Unknown status from EM Software Library: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05122: Underlying cause: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05300: A connection to the EM Software Library must be created.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-05301: Unable to describe assembly archives from the EM Software Library

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05302: Unable to extract OVF file from the OVA

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05303: No assembly exists for name "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05304: No assembly archive exists for assembly "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05305: No assembly archive file found for assembly "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05306: No SSH password or keyfile in connection file

Cause: (See message)

Action: Re create the connection to EM Software Library
Level: 1

Type: ERROR

Impact: Other

OAB-05310: The assembly archive "{0}" is not ready for download. Its status is: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05321: FAIL - Invalid remote working directory "{0}", can not be in the /tmp directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-05324: FAIL - Unable to connect via SSH.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05325: Failed to connect via SSH: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05328: Unable to access remote working directory {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05329: FAIL - Unable to access remote working directory {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05331: FAIL - Unable to create test file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05332: Unable to create test file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05340: Unable to verify test file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05341: FAIL - Unable to verify test file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05343: Test file removal failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05344: FAIL - Test file removal failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05356: Unable to upload test OVA file. {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05357: FAIL - Unable to upload test OVA file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05361: Unable to download test OVA file. {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05362: FAIL - Unable to download test OVA file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05366: Unable to delete test OVA. {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05367: FAIL - Unable to delete test OVA.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-05520: Invalid URL for Connection to the Assembly Deployer "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-05521: Unable to download Assembly Artifact from Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05522: Only received {0}% of the Assembly Artifact when downloading

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05523: Error downloading Assembly from Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05524: Unable to delete Assembly from Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05525: Unable to upload and create Assembly "{0}" in Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05526: Unable to create Target named "{0}" to OVM 3.0 from Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05527: Unable to list OVM 3.0 Targets from Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05528: Unable to delete OVM 3.0 Target "{0}" from Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05529: Unable to get operation status for Request ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05530: Incorrect number of statuses returned {0}, expecting 1

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05531: Unable to parse Operation Status from Assembly Deployer. Returned status is "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05532: Unable to register Assembly {0} version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05533: Unable to unregister Assembly {0} version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05534: Unable to get Registration status of Assembly {0} version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05535: Unable to download Assembly OVF metadata

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05536: Unable to download status for target {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05537: Unable to download status for target {0}, expected 1 status but got {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05538: Unable to get Registration status for all Assemblies.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05540: Unable to create deployment for Assembly {0} version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05541: Unable to deploy Assembly {0} version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05542: Unable to describe deployment for Deployment ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05543: Unable to describe deployment for Assembly {0} version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05544: Incorrect number of deployments returned from describeDeployments

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05545: Unable to deploy Assembly instance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05546: Unable to describe deployments for the current deployer connection

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05550: Unable to undeploy Assembly with deployment ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05551: Unable to delete Assembly deployment with deployment ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-05560: Unable to start Assembly with deployment ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05561: Unable to stop Assembly with deployment ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05565: Unable to query for management flag for Assembly {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05570: Unable to describe Instances in Assembly Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05571: Unable to describe Networks for Target "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05572: Unable to describe scaling groups for deployment ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05573: Error scaling appliance with appliance ID {0} to desired target of {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05574: Error deleting a failed scale of an appliance instance. Appliance ID {0}, appliance instance IDs {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05580: Error Validating Assembly {0} against target {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05586: Error downloading OVF from Deployer for Assembly {0}, version {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05590: Error suspending assembly instance {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05591: Error resuming assembly instance {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05592: Could not open socket to url: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05593: Could not create socket for url: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-05594: Could not parse the deployer URL: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-05595: Could not initialize secure connection.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05596: Could not add the certificate for host {0} to the deployer truststore.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05597: Deployer truststore file {0} could not be read.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05598: Deployer truststore file {0} could not be loaded.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05599: Could not open connection to url {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05600: Could not read deployer truststore, invalid password.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-05900: Assembly {0} does not exist in catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-05902: No DeploymentPlan {0} in Assembly {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-05904: Unable to extract OVF from Assembly {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-06002: Missing required parameter '%s'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06003: Parameter '%s' takes no arguments.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06004: Parameter '%s' requires 1 or more arguments.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06005: Parameter '%s' requires exactly 1 argument.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06006: Parameter specified more than once: '%s'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06007: Illegal parameter: '%s'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06008: Missing parameter name for argument: '%s'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06010: The '-' escape argument must be followed by another argument.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06011: Password type parameters should not be entered on the command line. You will be prompted to enter the value.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06012: Cannot specify both ''{0}'' and ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06013: Must specify exactly one of the following parameters: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06033: Command not found: %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-06034: Help command not registered.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-06037: SSH user name or password incorrect, please try again.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Security

OAB-06040: Unable to print usage information. See stack trace in log.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-06042: An unknown error has occurred. See log for additional information.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-06062: Command or category does not exist: '%s'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-06254: No password was entered.

Cause: (See message)

Action: Retry the command and enter a password with at least one character.
Level: 1

Type: ERROR

Impact: User Input

OAB-06255: Passwords do not match.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-06256: Whitespace is not allowed in passwords.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07002: No password was entered.

Cause: (See message)

Action: Retry the command and enter a password with at least one character.
Level: 1

Type: WARNING

Impact: User Input

OAB-07003: Passwords do not match.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07004: Whitespace is not allowed in passwords.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07011: Error obtaining plug-in installer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07012: Error discovering plug-in configurations.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07013: Installed Plug-ins

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07014: No plug-ins currently installed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07015: Lists installed introspector plug-ins.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07016: Lists the set of installed introspector plug-ins and extensions including their status and various other details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07017: Error occured while attempting to disable plug-in ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07018: Plug-in ''{0}'' successfully disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07019: Plug-in not found: ''{0}''

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-07020: Disables an introspector plug-in or extension.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07021: Disables the specified plug-in or extension and recursively any child extensions.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07022: Error occured while attempting to enable plug-in ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07023: Plug-in ''{0}'' successfully enabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07024: Enables an introspector plug-in or extension.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07025: Enables the specified introspector plug-in or extension.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07026: Also enables all possible child extensions recursively if specified.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07027: Plug-in Installation Candidates

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07028: There are no plug-ins at the specified location: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07029: Finds introspector plug-ins to install.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07030: Lists the set of introspector plug-ins and extensions from a product home that can be installed into OVAB.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07031: Full path to the base directory of the product installation. For Oracle product installations, this can be either an ORACLE_HOME or one directory below an ORACLE_HOME to search multiple ORACLE_HOME.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07032: One or more plug-in names separated by spaces.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07033: A single plug-in name.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07034: List all attributes of all plug-ins in long format.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07035: Enter password for the remote SSH user:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07036: Specified plug-in(s) ''{0}'' do not exist in the product home.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07037: Error installing requested plug-ins.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07038: Name

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07039: Version

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07040: Enabled

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07041: Parent Name

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07042: Minimum Parent Version

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07043: Minimum Product Version

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07044: Maximum Product Version

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07045: Description

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07046: Error formatting plug-in table.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07047: Reloads installed plug-ins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07048: Unloads all currently loaded plug-ins and loads all currently available plug-ins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07049: Removes an introspector plug-in or extension.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07050: Recursively removes the specified plug-in or extension and any child extensions.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07051: Plug-in ''{0}'' successfully removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07052: Plug-in not found: ''{0}''

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07053: Error occured while attempting to remove plug-in ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07054: Installs one or more introspector plug-ins.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07055: Installs one or more plug-ins and extensions from a product home.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07056: Installing the following plug-ins: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07057: Warning: failed to configure plug-ins. See assemblybuilder.log.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-07105: Introspection failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07107: Error while preparing catalog for storage of new appliance or assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Data

OAB-07108: Plug-in ''{0}'' must be upgraded to version ''{1}'' available at product root ''{2}'' on target machine.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Upgrade

OAB-07121: Unable to create introspection named ''{0}''.

Cause: An assembly or appliance with that name already exists.

Action: Use "-force" to overwrite.
Level: 1

Type: ERROR

Impact: User Input

OAB-07122: JobParameter.ValueType for parameter {0} cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07148: Illegal value specified for the '%s%s' parameter.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07301: Encrypts prompted values.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07302: Prompts for a value and returns the encrypted form. The original value is not displayed to the screen.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07303: Enter value:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: User Input

OAB-07304: Confirm entered value:

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: User Input

OAB-07305: Encrypts values.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07306: Encrypts one or more values that are obtained by securely prompting without echoing. The encrypted values can either be printed to the screen or appended to a specified file. This command is intended for use when constructing property files used in conjunction with script-based facilities.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07307: Allows for the prompting of multiple values referenced by name.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07308: A set of one or more space-separated property names.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07309: The output file where the specified properties and encrypted values should be written. If the file does not exist then it will be created. If the file exists then all new properties will be appended to the file and any pre-existing properties will be updated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07311: Confirm entered value for property ''{0}'':

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: User Input

OAB-07312: Enter value for property ''{0}'':

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: User Input

OAB-07313: Added property ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07314: Error while editing existing property file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07315: Error while writing to new property file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07316: Creating new property file ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07317: Replaced property ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07318: Applying changes to pre-existing file ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-07326: Failed to list metadata.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07331: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07359: Unable to capture file sets for ''{0}''.

Cause: Element with the specified name was not found in the catalog.

Action: Specify the name of an existing appliance or assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-07360: Unable to capture %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07389: Failed to create an appliance template for %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07390: Platform {0} not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07391: Failed to validate base image for %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07414: Failed to import from {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07417: Nothing to be imported at {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07419: Warning: -importAs causes assembly archive content to be imported, but not the assembly archive itself.

Cause:

Action:
Level: 1

Type: WARNING

Impact: User Input

OAB-07443: Failed to export {0} to {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07454: Incorrect type {0}

Cause: (See message)

Action: Choose a valid type, Deployer or EM Software Library.
Level: 1

Type: ERROR

Impact: Other

OAB-07458: Incorrect source {0}

Cause: (See message)

Action: Choose a valid source, Deployer or EM Software Library.
Level: 1

Type: ERROR

Impact: Other

OAB-07463: Incorrect target {0}

Cause: (See message)

Action: Choose a valid target, Deployer or EM Software Library.
Level: 1

Type: ERROR

Impact: Other

OAB-07468: Incorrect type {0}

Cause: (See message)

Action: Choose a valid type, Deployer or EM Software Library.
Level: 1

Type: ERROR

Impact: Other

OAB-07490: Failed to import template from {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07492: The specified directory {0} does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07493: {0} is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07495: An appliance or assembly ''{0}'' already exists in the catalog.

Cause: (See message)

Action: Choose a different name for imported template or use "-force" to overwrite.
Level: 1

Type: ERROR

Impact: Files

OAB-07499: Specified platform ''{0}'' is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07504: Appliance {0} is a placeholder and may not be operated upon.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07565: No repository connections exist.

Cause: (See message)

Action: Use abctl createDeployerConnection to create a connection.
Level: 1

Type: ERROR

Impact: Other

OAB-07604: No connection to the EM Software Library exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07614: Invalid URL format {0}.

Cause: (See message)

Action: Enter a valid host URL, e.g. "myhost.com:7001"
Level: 1

Type: ERROR

Impact: User Input

OAB-07615: Invalid port {0}.

Cause: (See message)

Action: Enter a valid port number.
Level: 1

Type: ERROR

Impact: User Input

OAB-07619: Connection to {0} is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07624: No connection to EM Software Library exists to delete.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07626: Errors in verification of EM connection:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07634: Unable to describe assembly archives in EM Software Library.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07644: No assembly archive with name {0} and version {1} in EM Software Library to delete.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07672: Unable to delete {0} from catalog.

Cause: Nested appliance or assembly cannot be deleted.

Action: Use AbStudio (GUI) to delete nested appliances or assemblies.
Level: 1

Type: ERROR

Impact: User Input

OAB-07675: No assembly archive is present for {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07676: assembly archive can only be deleted for an assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07677: Unable to delete assembly archive for {0} from catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07688: Failed to create assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07715: Failed to export file set {0} to {1}.

Cause: Cannot export to a regular file at {0}.

Action: Ensure the destination is an empty directory.
Level: 1

Type: ERROR

Impact: User Input

OAB-07716: Failed to export file set {0} to {1}.

Cause: Directory is not empty at {0}.

Action: Ensure the destination is an empty directory.
Level: 1

Type: ERROR

Impact: User Input

OAB-07717: Failed to add {0} to assembly {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07730: No current package was found for appliance.

Cause: (See message)

Action: Ensure file set is packaged before attempting to export.
Level: 1

Type: ERROR

Impact: User Input

OAB-07731: No such assembly "{0}".

Cause: (See message)

Action: Check the appliance path to ensure initial components name assemblies.
Level: 1

Type: ERROR

Impact: User Input

OAB-07733: No such appliance "{0}".

Cause: (See message)

Action: Check the appliance path.
Level: 1

Type: ERROR

Impact: User Input

OAB-07734: No such file set "{0}".

Cause: (See message)

Action: Check the file set name.
Level: 1

Type: ERROR

Impact: User Input

OAB-07736: Copy failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07738: Unzip failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07745: Failed to create assembly archive for %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07754: Archive signing requires both certificate and key file arguments

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07755: File {0} does not exist

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07764: Top-level assembly {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07765: Assembly {0} is not a top-level assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07766: Assembly {0} is atomic.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07770: Unable to clear passwords for assembly {0}.

Cause: Passwords can only be cleared for assembly that does not have an assembly archive.

Action: Delete the assembly archive for assembly {0}.
Level: 1

Type: ERROR

Impact: User Input

OAB-07771: Invalid username and/or password for remote host.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Security

OAB-07773: Bad port number supplied to the {0} parameter: {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07774: Missing remote address.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07775: Literal IPv6 address missing '[' and ']': {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07776: Parameter '-remoteUser' must be supplied when specifying '-remoteHost'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07777: Parameter '-remoteHost' must be supplied when specifying '-remoteUser'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07778: Parameters '-remoteHost' and '-remoteUser' must be supplied when specifying '-remoteWorkingDir'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07779: Parameters '-remoteHost' and '-remoteUser' must be supplied when specifying '-remoteCleanup'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07780: Parameters '-remoteHost' and '-remoteUser' must be supplied when specifying '-privateKeyFile'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07781: Invalid private SSH key file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-07783: Parameters '-remoteHost' and '-remoteUser' must be supplied when specifying '-sudoUser'

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07784: Parameter '-privateKeyFile' can not be used when specifying '-sudoUser'

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07807: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07837: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07838: Endpoint {0} was not found on element {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07839: The specified appliances/assemblies do not belong to the same parent assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07840: The specified input and output do not use the same protocol.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07841: A connection between the two specified endpoints already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07842: The specified output is already connected to a different input.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07843: The specified output must be connected to a singleton input.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07844: The appliance containing the specified input is currently scaled to 0.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07845: Connection could not be created, due to error code {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07846: Cannot create a connection in a top-level atomic assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07847: Cannot create a connection in assembly {0}.

Cause: Cannot modify an assembly that has an assembly archive.

Action: Delete the assembly archive before attempting to modify the assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-07848: The specified input and output do not have compatible properties.

Cause: The output has one or more mandatory connection properties that are not avaialable on the input.

Action: Connect the output to a compatible input.
Level: 1

Type: ERROR

Impact: Other

OAB-07850: Cannot create connection to an unexposed input/output of an atomic assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07858: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07866: Element {0} does not contain an output with name {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07959: Failed to create Vnet {0} in assembly {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07960: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07979: Failed to delete Vnet {0} from assembly {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-07980: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07991: The assembly {0} was not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07992: No external resource with the name {0} was found in assembly {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07993: The element with the name {0} is not an external resource. Only external resources may be renamed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-07995: An assembly archive exists for assembly {0}. {1} may not be renamed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08100: Matching deployment plans not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08130: Failed to create interface {0} for appliance {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08131: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08149: Failed to delete interface {0} from appliance {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08150: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08171: Failed to bind interface {0} on appliance {1} to Vnet {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08172: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08191: Failed to bind input {0} on appliance {1} to interface {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08192: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08223: Unable to initialize the catalog

Cause:

Action:
Level: 1

Type: ERROR

Impact: Data

OAB-08272: An Exception occurred while formating the output of the command into a table.

Cause: (See message)

Action: This is an internal error. Please contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

OAB-08511: Failed to create file set definition {0} on appliance {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08512: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08513: Specification of Free Space is incomplete. The {0} parameter is missing.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08514: The {0} parameter must provide an absolute path.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08515: Unrecognized {0} parameter. See help for correct value list.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08516: Value for {0} must be an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08518: Failed to delete file set definition {0} from appliance {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08520: Failed to create file set definition {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08521: Specification of Quota is incomplete. The {0} parameter is missing.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08522: Assembly {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08523: Value for {0} must be an integer greater than zero.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08527: Specifies mounting options.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08537: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08557: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08559: Cannot describe Vnets for {0}.

Cause: (See message)

Action: Specify a top-level, non-atomic assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-08577: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08705: {0} is an external resource. External resources may not be copied.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08707: The element {0} does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08708: The element {0} is inside an atomic assembly {1}. Elements inside an atomic assembly may not be copied.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08710: {0} is a non-atomic assembly. Only atomic assemblies may be copied.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08712: Failed to copy {0} to {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08739: Unknown container type "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08740: Incorrect boolean value specified. Allowed values are {0} and {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08741: Setting value on a property of type {0} is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08742: Unrecognized property name: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08743: Operation not supported for this property.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08744: Invalid step specification. No path from {0} to {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08745: Container address must start with a slash (/) character.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08747: {0} container not found with name {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08748: {0} container instance not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08749: Invalid step in container address.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-08750: Failed to get property value.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08770: Failed to set property {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08780: Failed to bind file set definition {0} to appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-08790: Failed to unbind file set definition {0} from appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09001: Unable to save ContentResource to location {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09002: Unable to create a temporary file in order to save ContentResource as a file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09003: Unable to return ContentResource as stream because the original file {0} is missing.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09004: Can not delete content resource "{0}" as it doesn't exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09005: Unable to save ContentContainer: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09006: Unable to delete ContentContainer: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09007: Unable to save a ContentResource as the underlying file {0} no longer exists. Continuing instead.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09050: Unable to retrieve XSD file {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09051: Invalid capture ID in xml. UUID = '{0}', Capture ID Reference = '{1}'.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09052: Error in reading appliance.xml stream.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09053: Error while writing appliance XML.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09054: Error in reading assembly.xml stream.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09055: Error while writing assembly XML.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09056: Unable to parse a TypedValue in a property set inside the XML.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09057: Unable to convert {0} to an integer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09058: Unable to parse property {0} of type {1} with a value of {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09060: Unable to parse the XML document as there are {0} root nodes and we expect only 1.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09061: Unable to find schema namespace {0} in XML file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09062: Missing version in XML file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09063: Invalid appliance/assembly version.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09064: Error while creating new {0} XML document.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09065: Cannot SAVE a nested appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09066: Cannot SAVE a nested assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09077: Unable to delete the old appliance metadata

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09078: Unable to save appliance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09079: Unable to delete appliance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09080: Unable to rename appliance {0} with new name {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09081: Unable to rename assembly {0} with new name {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09082: Cannot create sibling appilance as the incoming appliance is of unknown type. {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09083: Unable to add an appliance that is not a top-level appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09084: Unable to add an assembly that is not a top-level assembly

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09085: Unable to delete old assembly metadata

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09086: Unable to save assembly {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09087: Unable to delete assembly {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09088: Unable to delete deployment plan "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09089: Unable to delete deployment plan "{0}" while it is in use

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09090: Cannot clone the specified appliance of unknown type {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09091: Cannot clone the specified assembly of unknown type {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09092: Cannot promote an assembly if it is a top level assembly

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09093: Cannot promote an appliance if it is a top level appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09094: Cannot revert the specified assembly of unknown type {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09095: Cannot revert the specified appliance of unknown type {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09096: Unable to reload assembly as there was a problem with the deployment plans

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09097: Unable to save MetaMetadata for GUI

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09098: Cannot promote the specified appliance of unknown type {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09099: Cannot promote the specified assembly of unknown type {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09100: Unable to create directory {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09101: Appliance file {0} was not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09102: Assembly file {0} was not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09103: Error in creating appliance.xml file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09104: Error in creating assembly.xml file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09105: No appliance.xml or assembly.xml in root directory {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09107: Location {0} is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09108: Unable to load the catalog from disk.

Cause: (See message)

Action: Please check the AB_INSTANCE/logs/assemblybuilder.log for more information.
Level: 1

Type: ERROR

Impact: Other

OAB-09109: Unable to reload appliance {0}

Cause: (See message)

Action: Please contact Customer Support
Level: 1

Type: ERROR

Impact: Other

OAB-09110: Unable to reload appliance {0} as there is no metadata on disk

Cause: (See message)

Action: Verify there is an appliance.xml for this appliance in the catalog
Level: 1

Type: ERROR

Impact: Files

OAB-09111: Unable to reload the deployment plan {0} as it's in use

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09112: Unable to reload the deployment plan {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09115: Unable to reload assembly {0}

Cause: (See message)

Action: Please contact Customer Support
Level: 1

Type: ERROR

Impact: Other

OAB-09116: Unable to reload assembly {0} as there is no metadata on disk

Cause: (See message)

Action: Verify there is an assembly.xml for this assembly in the catalog
Level: 1

Type: ERROR

Impact: Files

OAB-09117: Failed to load catalog id at location:

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09118: Unable to parse the catalog.xml file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09119: Unable to save catalog.xml

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09120: Failed to load Assembly {0}, continuing

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09121: Failed to load Appliance {0}, continuing

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09122: Unable to save SharingManager

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09123: Unable to delete SharingManager

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09124: Unable to save AssemblySharingManager

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09127: Could not read the xsd at location {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09130: The ConnectionType must not be null

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09140: Can not add a Volume link to a top level Appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09201: Unable to write appliance as it does not validate against the schema. Schema error: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09202: Unable to write assembly as it does not validate against the schema. Schema error: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09213: Invalid name: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09215: Error(s) encountered while verifying Assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09216: Error(s) encountered while verifying Appliance {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09217: {0} is required and the value is null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09218: {0} is required and the value is empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09219: Appliance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09223: Appliance {0}''s Resource Requirements cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09224: Appliance {0}''s Creator cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09225: Appliance Name cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09227: Assembly Name cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09228: Child {0} has a circular dependency.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09229: Output {0} has not been connected to an Input.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09232: Protocol {0} on Output {1} does not exist on Input {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09233: Connection between Output {0} and Input {1} does not adhere to singleton rules.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09234: Output {0} cannot be connected to more than one Input.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09235: Appliance {0}''s Type cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09236: Appliance {0}''s scalability information cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09237: Appliance {0}''s scalability target value ({1}) cannot be less than 0.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09238: Appliance {0}''s scalability minimum value ({1}) cannot be less than 0.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09239: Appliance {0}''s scalability maximum value ({1}) cannot be less than 1.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09240: Appliance {0}''s scalability absolute maximum value ({1}) cannot be less than 1.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09241: Appliance {0}''s scalability target value cannot be less than the minimum ( {1} < {2} ).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09242: Appliance {0}''s scalability minimum value cannot be more than the maximum ( {1} > {2} ).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09243: Appliance {0}''s scalability target value cannot be more than the maximum ( {1} > {2} ).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09244: Appliance {0}''s scalability maximum value cannot be more than the absolute maximum ( {1} > {2} ).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09245: At least one interface must be defined.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09246: One interface must be set as the default.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09247: Input {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09248: Output {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09300: An appliance with name {0} already exists. Case is ignored.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09302: An assembly with name {0} already exists. Case is ignored.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09310: Appliance {0} contains a link to a Volume ''{1}'' that doesn''t exist in the root level Assembly {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09311: Appliance {0} contains a volumeLink while there is no parent Assembly to get Volumes for.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09501: Unable to locate decrypt key file at {0}.

Cause: (See message)

Action: Make sure the key file exists at {0}.
Level: 1

Type: ERROR

Impact: Files

OAB-09502: Unable to read the key file at {0}.

Cause: (See message)

Action: Make sure the key file exists and is readable. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-09503: Failed to write key file at {0}.

Cause: (See message)

Action: Make sure the directory is writable. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-09504: Directory does not exist at {0}.

Cause: (See message)

Action: Make sure to import from a valid directory.
Level: 1

Type: ERROR

Impact: Files

OAB-09505: Failed to read metadata file from {0}.

Cause: (See message)

Action: Make sure to import from a valid directory.
Level: 1

Type: ERROR

Impact: Files

OAB-09506: Failed to write export metadata to {0}.

Cause: (See message)

Action: Make sure the directory is writable. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-09507: Corrupt metadata file at {0}.

Cause: (See message)

Action: Import from other directories. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Data

OAB-09508: Invalid directory structure at {0}.

Cause: (See message)

Action: Make sure to import from a valid directory.
Level: 1

Type: ERROR

Impact: Files

OAB-09509: Directory is not empty at {0}. Existing files in directory: {1}

Cause: (See message)

Action: Clean up the directory, or choose an empty directory.
Level: 1

Type: ERROR

Impact: Files

OAB-09510: Exporting nested appliance/assembly is not allowed.

Cause: (See message)

Action: Export top level appliance/assembly only.
Level: 1

Type: ERROR

Impact: User Input

OAB-09511: Cannot export to a regular file at {0}.

Cause: (See message)

Action: Choose an empty directory.
Level: 1

Type: ERROR

Impact: User Input

OAB-09512: Unable to locate {0}.

Cause: (See message)

Action: Make sure named appliance or assembly exist in catalog.
Level: 1

Type: ERROR

Impact: User Input

OAB-09513: Catalog already contains {0} {1}.

Cause: (See message)

Action: Choose a different name to import as.
Level: 1

Type: ERROR

Impact: User Input

OAB-09520: Unable to create a directory at {0}.

Cause: (See message)

Action: Check file permission by attempting to create a directory there.
Level: 1

Type: ERROR

Impact: Files

OAB-09521: Unable to save deployment plan.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-09600: The connection does not have an ApplianceInput.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09601: The connection does not have an ApplianceOutput.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09602: The connection does not have an AssemblyInput.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09603: The connection does not have an AssemblyOutput.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09651: No element found for "{0}" with path "{1}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09652: Failed to unzip file {0} to location {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09659: Unable to return URI for TypedValue with Type "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09660: Unable to return Boolean for TypedValue with Type "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09661: Unable to return Integer for TypedValue with Type "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09662: Unable to return Password for TypedValue with Type "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09663: Unable to return String for TypedValue with Type "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09664: Unable to return a List of Strings for TypedValue with Type "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09665: Unable to create InputStream for file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09666: Unable to create OutputStream for file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09667: Unable to move {0} to {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09668: Unable to recursively copy {0} to {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09669: Unable to recursively delete file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09670: {0} already exists and is not a directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09671: Unable to make directory {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09672: Unable to list files from directory {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09673: Unable to write to file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09680: Unable to delete empty directories under catalog root {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09681: Unable to get canonical paths for comparison

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09682: Unable to create Meta-Metadata handle

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09683: Unable to create Sharing Metadata directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09684: Unable to create Package directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09685: Unable to create PackageDefinition directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09686: Unable to create PackageContainerManager file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09687: Unable to create Template directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09688: Unable to create VmTemplate file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09689: Unable to create TemplateContainerManager file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09690: Unable to load ContentResources for sharing ID {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09691: Unable to create ContentResource file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09692: Failed to create directory for DeploymentPlans

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09693: Unable to create DeploymentPlan handle for file

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09694: Unable to create the root ContentResource directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-09700: Unable to save TemplateContainer {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09701: Unable to delete TemplateContainer {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09702: Unable to save InternalVmTemplate {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09703: Unable to delete InternalVmTemplate {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09704: Unable to save shared template resource

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09705: Unable to delete shared template resource

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09706: Unable to save TemplateContainerManager {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09707: Unable to delete TemplateContainerManager {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09708: Unable to save PackageDefinition

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09709: Unable to delete PackageDefinition

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09711: Cannot initialize PackageDefinitionBuilder with an uknown PackageDefinition class {0}

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

OAB-09712: Unable to save PackageContainer {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09713: Unable to delete PackageContainer {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09717: Unable to save InternalPackage's metadata

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09718: Unable to delete InternalPackage's metadata

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09719: Unable to save shared package resource

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09720: Unable to delete shared package resource

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09721: Unable to save PackageContainerManager {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09722: Unable to delete PackageContainerManager {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09723: Cannot set the introspected PackageDefinition when one is already set

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-09724: The package definition {0} has a root that conflicts with the existing id {1}

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

OAB-09726: The appliance already contains a file set definition with the name {0}

Cause:

Action:
Level: 1

Type: SET_AT_RUNTIME

Impact: Other

OAB-09730: Unable to load deployment plan with underlying persister.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-11014: Error: unable to initialize the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-11017: Error: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-11020: An unexpected error occurred.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-20003: No files in file set definition {0}.

Cause: (See message)

Action: Fix the file set definition so that at least one file is included.
Level: 1

Type: NOTIFICATION

Impact: User Input

OAB-20004: File {0} is not readable.

Cause: (See message)

Action: Create file sets as root, or set read permission of the file, or add it to EXCLUDE.
Level: 1

Type: ERROR

Impact: Files

OAB-20005: File set root {0} does not exist.

Cause: (See message)

Action: Make sure file set root exist.
Level: 1

Type: ERROR

Impact: Files

OAB-20006: File not found at {0}. Most likely it's a transient file that can safely be ignored.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-20007: Broken symbolic link at {0}.

Cause: (See message)

Action: Fix the broken symbolic link.
Level: 1

Type: ERROR

Impact: Files

OAB-20009: Cannot create file sets for external appliance {0}.

Cause: (See message)

Action: Make sure that the appliance you are trying to create file sets for is not external.
Level: 1

Type: ERROR

Impact: Other

OAB-20011: File sets already exist for {0} {1}.

Cause: (See message)

Action: Use -force to override.
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-20012: Template exists for appliance {0}.

Cause: (See message)

Action: Use -force to override.
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-20017: Windows not supported.

Cause: (See message)

Action: Run OVAB on supported platform(s), e.g., Oracle Enterprise Linux 5.4.
Level: 1

Type: ERROR

Impact: Other

OAB-20018: Unable to get dbconsole status.

Cause: (See message)

Action: Check if the following command can be executed: {0}. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-20020: No valid appliance found in {0}.

Cause: (See message)

Action: Make sure introspection was completed successfully. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-20021: {0} is not an atomic assembly.

Cause: (See message)

Action: Create file sets for sub-appliances and sub-assemblies individually.
Level: 1

Type: ERROR

Impact: User Input

OAB-20022: No file set definition was found.

Cause: (See message)

Action: Set or correct the file set definition. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-20023: Invalid file set definition.

Cause: (See message)

Action: Correct the file set definition. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-20024: Cannot create file sets for an individual appliance in an atomic assembly.

Cause: (See message)

Action: Create file sets for the parent atomic assembly.
Level: 1

Type: ERROR

Impact: Other

OAB-20026: The following file set creation validation steps failed for appliance {0}: {1}

Cause: (See message)

Action: Correct the conditions listed above. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-20027: File set root {0} does not appear to be either a directory or a regular file.

Cause: (See message)

Action: Set file set root to a directory or a regular file.
Level: 1

Type: ERROR

Impact: Other

OAB-20028: I/O error occurred while listing files under {0}.

Cause: (See message)

Action: Make sure the file system is healthy. Correct Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-20029: Ignoring non-regular file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Files

OAB-23118: Assembly {0} does not have file sets captured.

Cause: (See message)

Action: Capture file sets for the assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-23119: Appliance {0} does not have file sets captured.

Cause: (See message)

Action: Capture file sets for the appliance or one of its siblings.
Level: 1

Type: ERROR

Impact: User Input

OAB-23120: Appliance {0} already has template for {1}.

Cause: (See message)

Action: Use -force flag to override existing template.
Level: 1

Type: ERROR

Impact: User Input

OAB-23121: Invalid base image at {0}.

Cause: (See message)

Action: Provide a valid base image location.
Level: 1

Type: ERROR

Impact: User Input

OAB-23122: Unable to locate supplied base image at {0}.

Cause: (See message)

Action: Provide a valid base image location.
Level: 1

Type: ERROR

Impact: Files

OAB-23123: Unable to locate vm.cfg for supplied base image.

Cause: (See message)

Action: Provide a valid base image location with vm.cfg.
Level: 1

Type: ERROR

Impact: Files

OAB-23338: Cannot create template for external appliance {0}.

Cause: (See message)

Action: Choose non-external appliance for template creation.
Level: 1

Type: ERROR

Impact: User Input

OAB-23339: Cannot create template for external reference {0}.

Cause: (See message)

Action: Choose non-external reference for template creation.
Level: 1

Type: ERROR

Impact: User Input

OAB-23340: Validator execution context of type {0} is from an incompatible template creation plug-in.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-23343: Unable to locate a valid default base image at {0} or {1}.

Cause: (See message)

Action: Specify a base image location, or place a base image in default location. Refer to user guide for detail.
Level: 1

Type: ERROR

Impact: Files

OAB-23344: Template directory {0} exists but is a regular file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-23345: Failed to create template directory at {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-23346: Failed to create template for assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-23348: Failed to copy from {0} to {1}.

Cause: (See message)

Action: Check the log file for underlying exception. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-23351: User 'oracle' does not exist in the base image.

Cause: (See message)

Action: Make sure the base image contains 'oracle' user.
Level: 1

Type: ERROR

Impact: Other

OAB-23352: Group 'oracle' does not exist in the base image.

Cause: (See message)

Action: Make sure the base image contains 'oracle' group.
Level: 1

Type: ERROR

Impact: Other

OAB-23353: User {0} does not exist in the base image.

Cause: (See message)

Action: Make sure the base image contains the specified user.
Level: 1

Type: ERROR

Impact: Other

OAB-23354: Group {0} does not exist in the base image.

Cause: (See message)

Action: Make sure the base image contains the specified group.
Level: 1

Type: ERROR

Impact: Other

OAB-23355: The specified index file location {0} could not be read.

Cause: (See message)

Action: Specify a valid, readable base image index file location.
Level: 1

Type: ERROR

Impact: Files

OAB-23356: The base image index file is invalid.

Cause: The index file is missing a required entry {0}.

Action: Obtain a valid index file for the intended base image.
Level: 1

Type: ERROR

Impact: Files

OAB-23471: Failed to run template tool binary.

Cause: (See message)

Action: Check the log file for detail. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-23472: Permission for wrapper not set.

Cause: (See message)

Action: Run ORACLE_HOME/oracleRoot.sh script as the root.
Level: 1

Type: ERROR

Impact: Installation

OAB-23473: Wrapper not found at {0}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Installation

OAB-23474: Wrapper is not executable at {0}.

Cause: (See message)

Action: Run ORACLE_HOME/oracleRoot.sh script as the root. Contact Oracle support if necessary
Level: 1

Type: ERROR

Impact: Installation

OAB-23475: Native library is not available.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Installation

OAB-23477: Element {0} was not found in the catalog.

Cause: (See message)

Action: Specify an existing top-level catalog element.
Level: 1

Type: ERROR

Impact: User Input

OAB-23478: Assembly archive already exists.

Cause: (See message)

Action: Use -force to override.
Level: 1

Type: ERROR

Impact: User Input

OAB-23479: Unable to locate an appropriate base image.

Cause: (See message)

Action: Ensure that appliance templates are created.
Level: 1

Type: ERROR

Impact: Files

OAB-23480: Invalid free space request {0} {1}.

Cause: (See message)

Action: Correct the free space request to valid values.
Level: 1

Type: ERROR

Impact: User Input

OAB-23481: Failed to create assembly archive for {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-23482: Failed to generate assembly metadata for {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-23483: Specified platform {0} is not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-23484: Cannot create template for {0} because it belongs to the following assemblies for which assembly archives exist: {1}.

Cause: Cannot recreate templates for a member of any assembly that has an existing assembly archive.

Action: Delete assembly archive for any assemblies that contain the specified element.
Level: 1

Type: ERROR

Impact: User Input

OAB-23485: {0} does not contain any appliances.

Cause: At least one appliance with file sets must exist for template creation to proceed.

Action: Specify an appliance or an assembly that contains at least one appliance.
Level: 1

Type: ERROR

Impact: User Input

OAB-23486: No provider could be found to handle the specified template request.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-23487: Validator ''{0}'' is of unsupported type {1}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-23488: Cannot create an assembly archive for a nested element.

Cause: (See message)

Action: Specify a top-level assembly instead.
Level: 1

Type: ERROR

Impact: User Input

OAB-23489: Cannot create an assembly archive for an appliance or atomic assembly.

Cause: (See message)

Action: Specify a non-atomic assembly instead.
Level: 1

Type: ERROR

Impact: User Input

OAB-23490: Cannot export an assembly archive for a non-atomic assembly.

Cause: (See message)

Action: Omit the 'exportOnly' flag, or specify an atomic assembly or appliance instead.
Level: 1

Type: ERROR

Impact: User Input

OAB-23491: Cannot create an assembly archive for assembly {0}.

Cause: The assembly must have at least one Vnet defined.

Action: Define at least one Vnet for this assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-23492: Cannot create an assembly archive for assembly {0}.

Cause: The following interfaces in the assembly are not bound to any Vnet: [{0}].

Action: Ensure that all interfaces are bound to a Vnet.
Level: 1

Type: ERROR

Impact: User Input

OAB-23493: Cannot create an assembly archive for assembly {0}.

Cause: The following outputs in the assembly are not connected to any input: [{0}].

Action: Connect each output in the assembly to a suitable input.
Level: 1

Type: ERROR

Impact: User Input

OAB-23494: Delete assembly archive for any assemblies that contain the specified element, and specify "-force" option to override existing templates.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-23495: Loop device directory {0} does not exist.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-23496: There are not enough loop devices present to create a template for this appliance.

Cause: {0} loop devices are needed to create a template for this appliance, but only {1} loop devices are present on this system.

Action: Configure additional system loop devices. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-23497: Cannot create an assembly archive for assembly {0}.

Cause: The following Vnets in the assembly are not used: [{0}].

Action: Delete any unused Vnets or bind appliance network interfaces to unused Vnets.
Level: 1

Type: ERROR

Impact: User Input

OAB-23501: Executing external command {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-24001: Unable to create directory at {0}

Cause: (See message)

Action: Check the log file for more information. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-24002: Failed to mount {0}.

Cause: (See message)

Action: Make sure the image is valid. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-24003: Failed to umount {0}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-24004: Failed to build disk {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-24005: Unable to locate jre.zip file at {0}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-24006: Unable to run command {0}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-24007: Appliance in atomic assembly cannot be individually used for template creation.

Cause: (See message)

Action: Create template for the parent atomic assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-24008: Unable to run command {0}; exit value = {1}; output = {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-24101: Unable to create a file or directory at {0}

Cause: (See message)

Action: Check the log file for more information. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-27001: Invalid template location at {0}.

Cause: (See message)

Action: Correct the error and try again.
Level: 1

Type: ERROR

Impact: Other

OAB-27002: Not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-27003: Directory contains sub-directory {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-27004: Directory contains illegal file {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-27005: Directory does not contain disk image file "System.img".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-27006: Directory does not contain vm.cfg file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-27007: Unable to load {0}.

Cause: (See message)

Action: Make sure a valid config file exists.
Level: 1

Type: ERROR

Impact: Files

OAB-27008: Invalid config file. Expected property "{0}" not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-27009: Unable to import with given name {0}.

Cause: Registered appliance {0} exists in catalog.

Action: Choose another name to use or unregister the appliance first.
Level: 1

Type: ERROR

Impact: User Input

OAB-27010: Unable to import with given name {0}.

Cause: Registered assembly {0} exists in catalog.

Action: Choose another name to use or unregister the assembly first.
Level: 1

Type: ERROR

Impact: User Input

OAB-27101: Deleting existing appliance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-27102: Deleting existing assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-40003: Dehydration did not produce a root Assembly or Appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40004: Plug-in ''{0}'' disabled: found multiple occurances of parameter ''{1}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-40005: Extension ''{0}'' missing required dependency ''{1}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-40007: Unable to create root Assembly: root Appliance exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40008: Unable to create root Appliance: root Assembly exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40009: No default interface was set for appliance {0} of type {1}.

Cause: One of the appliance interfaces created during introspection must be designated as the default interface.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OAB-40101: Error executing remote command: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-40102: Unable to connect to remote server with entered password and parameters host={0}, port={1}, and user={2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-40103: Unable to connect to remote server with entered password and parameters host={0}, port={1}, user={2}, and key file={3}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Security

OAB-40104: Unable to copy stream named ''{0}'' to remote file ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-40105: Unable to copy stream named ''{0}'' to remote file ''{1}'' with permissions={2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-40106: Unable to copy file ''{0}'' to remote file ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-40107: Unable to copy file ''{0}'' to remote file ''{1}'' with permissions={2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-40108: Illegal attempt to perform SSH operation on a closed connection: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-40109: Error attempting to close SSH connection: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-40110: Unable to copy remote file ''{0}'' to local directory ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-40111: Error constructing OMA download URL

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40112: Error fetching OMA download script at URL '%s'

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40113: Failure while retrieving EM Agent integer property from appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40114: Failure while retrieving EM Agent password property from appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40115: Failure while retrieving EM Agent string property from appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40116: unable to find 'oracleHome' system property in the appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40117: unable to find 'admin-username' system property on the WLS assembly

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40118: unable to find 'admin-password' user property on the WLS assembly

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40119: unable to register component

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40120: unable to determine hosts for wls input needed for EM regisration

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-40202: Aborting operation due to previous failure during deployment.

Cause: Cannot proceed due to prior error during configuration (rehydrate) phase.

Action: Investigate cause of original error and redeploy, reset all state and manually re-attempt configuration, or set the state to CONFIGURED and reattempt the desired operation.
Level: 1

Type: ERROR

Impact: Other

OAB-40501: Wrapper not found at {0}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Installation

OAB-40502: Native library is not available.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Installation

OAB-40503: Wrapper is not executable at {0}.

Cause: (See message)

Action: Run ORACLE_HOME/oracleRoot.sh script as the root. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Installation

OAB-40504: Permission for wrapper not set.

Cause: (See message)

Action: Run ORACLE_HOME/oracleRoot.sh script as the root.
Level: 1

Type: ERROR

Impact: Installation

OAB-40507: Unable to run command {0}.

Cause: External command ''{0}'' exited with exit code {1}.

Action: Make sure that the external command exists and is executable. Contact Oracle support if necessary
Level: 1

Type: ERROR

Impact: Process

OAB-40508: Failed to mount {0}.

Cause: (See message)

Action: Make sure the image is valid. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40509: Failed to umount {0}.

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40512: Unable to create directory at {0}

Cause: (See message)

Action: Check the permission and see if you can manually create a directory
Level: 1

Type: ERROR

Impact: Files

OAB-40513: Unable to create a disk image at {0}

Cause: (See message)

Action: Ensure that there is enough space on your system and file permissions are correct. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-40514: Unable to read partition table for {0}

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40515: Unable to save partition table for {0}

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40516: Unable to create a file system at {0}

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40517: Unable to get block device attributes for {0}

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40518: Unable to process LVM disk operation for {0}

Cause: (See message)

Action: Make sure LVM support is enabled on your system. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40519: Duplicate physical volume {0} found at {1}

Cause: (See message)

Action: Disable physical volume at {0}. See OVAB user guide for detail.
Level: 1

Type: ERROR

Impact: Process

OAB-40520: Unable to read file system table

Cause: (See message)

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Process

OAB-40521: No device attributes found for {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-42008: Missing required parameter ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42009: Path ''{0}'' in parameter ''{1}'' is not an absolute path.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42010: Directory ''{0}'' does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42011: Directory ''{0}'' is not readable.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42012: Path ''{0}'' is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42016: Bad variable name ''{0}''. Variable names must match regular expression ''[a-zA-Z_]+[a-zA-Z0-9_]*''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42017: Script found at path ''{0}'' is not a file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42018: Script found at path ''{0}'' is not readable.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42019: Missing required resource ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42020: Error writing to property file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42021: Error reading the property names file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42023: A script returned a non-zero exit status ({0}) indicating a failure.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42024: Problem encountered executing script ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42033: Reserved directory ''{0}'' cannot be used for supplying Generic Product scripts.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-42034: Error copying scripts from directory ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42035: Error copying property files from directory ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42201: Unable to find appliance or assembly {0}.

Cause: (See message)

Action: Make sure catalog contains specified appliance or assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-42301: Plugin {0} required by {1} is not available.

Cause: (See message)

Action: Install the plug-in.
Level: 1

Type: ERROR

Impact: Other

OAB-42401: Configuration name space specification must not be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42402: Name space must not contain any whitespace.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42403: Configuration property keys must not be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42404: Specified key ''{0}'' illegal characters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42405: Configuration property values must not be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42406: Configuration property values must not contain line separator characters.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42407: Path ''{0}'' does not point to a readable directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42408: Path ''{0}'' does not point to a readable file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-42409: Error opening configuration file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42410: Problem reading configuration file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42411: Unable to make configuration directory ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42412: Problem writing configuration file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42413: Unable to delete configuration file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-42551: "archive only" flag cannot be used for appliance {0}.

Cause: (See message)

Action: Choose an assembly, or turn off "archive only" flag.
Level: 1

Type: ERROR

Impact: User Input

OAB-42552: No assembly was found for name {0}.

Cause: (See message)

Action: Check your catalog and make sure named assembly exists.
Level: 1

Type: ERROR

Impact: User Input

OAB-42553: Assembly {0} does not have an assembly archive.

Cause: (See message)

Action: Create assembly archive before exporting.
Level: 1

Type: ERROR

Impact: User Input

OAB-42554: Invalid template directory found at {0}.

Cause: Catalog appears to be corrupted.

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-42555: No assembly archive found in template directory at {0}.

Cause: Catalog appears to be corrupted.

Action: Contact Oracle support if necessary.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAB-42556: Destination directory {0} is not empty.

Cause: (See message)

Action: Clean up the directory, or choose an empty directory.
Level: 1

Type: ERROR

Impact: User Input

OAB-42557: Destination file {0} already exists.

Cause: (See message)

Action: Choose a different destination path.
Level: 1

Type: ERROR

Impact: User Input

OAB-42558: Failed to export assembly archive to {0}.

Cause: (See message)

Action: Check your log file for error message. Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Other

OAB-42711: Warning: A file with name {0} already exists in the archives directory. The import operation will proceed, but the assembly archive will not be copied.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-42720: The assembly archive does not contain AB.img.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Data

OAB-42721: Catalog already contains {0} {1}.

Cause: (See message)

Action: Choose a different name to import as.
Level: 1

Type: ERROR

Impact: Other

OAB-42722: The plug-in ''{0}'' is required but is not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-42723: Unable to create directory at {0}.

Cause: (See message)

Action: Check file permissions and attempt to manually create a directory.
Level: 1

Type: ERROR

Impact: Files

OAB-42734: Could not mount disk image {0}.

Cause: Mount operation failed with result ''{0}''.

Action: Contact Oracle support if necessary.
Level: 1

Type: ERROR

Impact: Files

OAB-42735: The assembly archive does not contain an assembly metadata descriptor as its first entry.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Data

OAB-42736: The assembly archive does not contain a disk image matching expected pattern <capture_id>{0}.

Cause: The archive is corrupted, or is not compatible with this version of Oracle Virtual Assembly Builder.

Action: Contact Oracle Support Services if necessary.
Level: 1

Type: ERROR

Impact: Data

OAB-42737: Import source {0} has invalid file extension.

Cause: Import source must have .ova file extension.

Action: Specify a valid archive from which to import.
Level: 1

Type: ERROR

Impact: Other

OAB-42738: No Assembly Builder metadata was extracted from the archive.

Cause: The archive is corrupted or was created by an imcompatible tool.

Action: Supply a valid and compatible assembly archive. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

OAB-42739: An error occured while attempting to import the {0} plug-in.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43001: Appliance does not contain sub-elements.

Cause: (See message)

Action: Specify an assembly instead.
Level: 1

Type: ERROR

Impact: Other

OAB-43002: Type of specified output did not match type of specified element.

Cause: (See message)

Action: Specify an output that belongs to the specified element.
Level: 1

Type: ERROR

Impact: Other

OAB-43003: The specified element does not belong to an assembly.

Cause: Attempted to create external resources for a top-level appliance or assembly.

Action: Add the specified element to an assembly before creating external resources.
Level: 1

Type: ERROR

Impact: Other

OAB-43004: Cannot add external resources to atomic assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43005: The specified output {0} is already connected to another input.

Cause: An output can only be connected to one input at a time.

Action: Remove the existing connection or specify a different output.
Level: 1

Type: ERROR

Impact: Other

OAB-43006: Cannot add external resources to assembly {0}.

Cause: Cannot modify an assembly that has an existing assembly archive.

Action: Delete the assembly's archive before attempting to modify the assembly.
Level: 1

Type: ERROR

Impact: Other

OAB-43007: Cannot create external resource with name {0}.

Cause: Another element with the specified name exists in the assembly.

Action: Specify a name that does not conflict with an existing element in the assembly.
Level: 1

Type: ERROR

Impact: Other

OAB-43010: Unable to create nested assembly {0}.

Cause: Only top-level empty assemblies can be created.

Action: Create a top-level empty assembly.
Level: 1

Type: ERROR

Impact: Other

OAB-43020: Cannot add nested appliance or assembly {0}.

Cause: Only top-level appliances or assemblies can be added to another assembly.

Action: Specify a top-level appliance or assembly to add.
Level: 1

Type: ERROR

Impact: User Input

OAB-43021: Cannot add non-atomic assembly {0}.

Cause: Only atomic assemblies can be added to another assembly.

Action: Specify an atomic assembly to add.
Level: 1

Type: ERROR

Impact: User Input

OAB-43022: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-43023: Cannot add an element to atomic assembly {0}.

Cause: Only non-atomic assemblies can have elements added to them.

Action: Specify a non-atomic assembly to add elements to.
Level: 1

Type: ERROR

Impact: User Input

OAB-43024: An appliance or assembly with name {0} already exists in assembly {1}.

Cause: An appliance or assembly with the specified name already exists in the target assembly.

Action: Specify a different appliance or assembly to add.
Level: 1

Type: ERROR

Impact: User Input

OAB-43025: Cannot add to {0}.

Cause: Specified target element is not an assembly.

Action: Specify a valid assembly to add an element to.
Level: 1

Type: ERROR

Impact: User Input

OAB-43026: Cannot add to assembly {0}.

Cause: Cannot modify an assembly that has an existing assembly archive.

Action: Delete the assembly's archive before attempting to modify the assembly.
Level: 1

Type: ERROR

Impact: User Input

OAB-43027: Cannot add an element to nested assembly {0}.

Cause: Only top-level assemblies can have elements added to them.

Action: Specify a top-level assembly to add to.
Level: 1

Type: ERROR

Impact: User Input

OAB-43028: Cannot modify a nested assembly {0}.

Cause: The specified modification can only be performed on a top-level assembly.

Action: Specify a top-level assembly.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43029: Cannot modify atomic assembly {0}.

Cause: The specified modification can only be performed on a non-atomic assembly.

Action: Specify a non-atomic assembly.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43030: Cannot modify an assembly that has an existing assembly archive.

Cause: (See message)

Action: Delete the assembly's archive before attempting to modify the assembly.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43031: Cannot modify {0}.

Cause: The specified modification can only be performed on an assembly.

Action: Specify an assembly.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43032: Cannot modify element {0} because it belongs to the following assemblies that have assembly archives: {1}.

Cause: Cannot modify a member of any assembly that has an assembly archive.

Action: Delete the assembly archives for all assemblies that contain the specified element.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43033: Cannot modify {0}.

Cause: The specified modification can only be performed on an appliance.

Action: Specify an appliance.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43034: Cannot modify element {0} because its containing assembly {1} has an assembly archive.

Cause: Cannot modify a member of an assembly that has an assembly archive.

Action: Delete any existing assembly archives for the containing assembly.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43035: Cannot modify {0}.

Cause: The specified modification can only be performed on an appliance that belongs to a non-atomic assembly.

Action: Add the appliance to a top-level assembly.
Level: 1

Type: SET_AT_RUNTIME

Impact: User Input

OAB-43036: Cannot bind the file set definition.

Cause: The existing file set {0} in appliance {1} has an identical file set root: {2}.

Action: Check the specified file set root.
Level: 1

Type: ERROR

Impact: User Input

OAB-43040: Cannot create Vnet in the specified assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43041: The assembly already contains a Vnet with name {0}.

Cause: (See message)

Action: Specify a different name for the Vnet.
Level: 1

Type: ERROR

Impact: User Input

OAB-43042: Cannot delete Vnet in the specified assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43043: The assembly does not contain a Vnet with name {0}.

Cause: (See message)

Action: Specify the name of an existing Vnet.
Level: 1

Type: ERROR

Impact: User Input

OAB-43044: Vnet {0} cannot be deleted because the following appliance interfaces are currently bound to it: [{1}].

Cause: A Vnet cannot be deleted if any interfaces refer to it.

Action: Un-bind the above interfaces before deleting the Vnet.
Level: 1

Type: ERROR

Impact: User Input

OAB-43054: The interface name is reserved.

Cause: (See message)

Action: Choose a different interface name.
Level: 1

Type: ERROR

Impact: User Input

OAB-43055: Cannot create an interface in the specified appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43056: The appliance already contains an interface with name {0}.

Cause: (See message)

Action: Specify a different name for the interface.
Level: 1

Type: ERROR

Impact: User Input

OAB-43057: Cannot delete interface in the specified appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43058: The appliance does not contain an interface with name {0}.

Cause: (See message)

Action: Specify the name of an existing interface.
Level: 1

Type: ERROR

Impact: User Input

OAB-43059: Interface {0} cannot be deleted because the following appliance inputs are currently bound to it: [{1}].

Cause: An interface cannot be deleted if any inputs refer to it.

Action: Un-bind the above inputs before deleting the interface.
Level: 1

Type: ERROR

Impact: User Input

OAB-43060: Cannot bind interface to Vnet.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43061: Cannot bind appliance input to interface.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43062: The appliance does not contain an input with name {0}.

Cause: (See message)

Action: Specify the name of an existing appliance input.
Level: 1

Type: ERROR

Impact: User Input

OAB-43063: Cannot create file set definition in the specified appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43064: The appliance already contains a file set definition with name {0}.

Cause: (See message)

Action: Specify a different name for the file set definition.
Level: 1

Type: ERROR

Impact: User Input

OAB-43065: Cannot delete file set definition in the specified appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43066: Cannot perform operation on non-editable file set definition.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-43068: Cannot bind file set definition to appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43069: The appliance is already bound to file set definition {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-43071: Cannot unbind file set definition from appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43072: Cannot create file set definition in the specified assembly.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43073: Assembly already has a file set definition named {0}.

Cause: (See message)

Action: Specify a different name for the new file set definition.
Level: 1

Type: ERROR

Impact: User Input

OAB-43074: Top level assembly has no file set definition named {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-43075: Cannot delete the file set definition from {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-43076: File set definition is bound to one or more appliances, including {0}.

Cause: (See message)

Action: Unbind file set definition from all appliances to which it is bound.
Level: 1

Type: ERROR

Impact: User Input

OAB-43077: The appliance {0} has previously captured file sets and/or template built.

Cause: (See message)

Action: Use -force to enable removal of existing file sets and template from the appliance.
Level: 1

Type: ERROR

Impact: User Input

OAB-44001: Appliance {0} does not have a template for Platform ''{1}'', OS ''{2}''.

Cause: (See message)

Action: Create a template for {0} with the required Platform and OS first.
Level: 1

Type: ERROR

Impact: Other

OAB-44002: Assembly {0} does not have a template for Platform ''{1}'', OS ''{2}''.

Cause: (See message)

Action: Create a template for {0} with the required Platform and OS first.
Level: 1

Type: ERROR

Impact: Other

OAB-44003: Assembly {0} does not contain any Vnets.

Cause: (See message)

Action: Define at least one Vnet for this assembly.
Level: 1

Type: ERROR

Impact: Other

OAB-44004: Interface {0} in appliance {1} is not bound to any Vnet.

Cause: (See message)

Action: Assign the interface to one of the assembly's available Vnets.
Level: 1

Type: ERROR

Impact: Other

OAB-44005: Error in external appliance {0} vm.cfg file

Cause: (See message)

Action: Correct the disk entry of the external appliance's vm.cfg file
Level: 1

Type: ERROR

Impact: Other

OAB-44006: Cannot generate a descriptor for an external resource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-44007: No templates exist for the assembly {0} with Platform ''{1}'', OS ''{2}''.

Cause: (See message)

Action: Create a template for an appliance of {0} with the required Platform and OS first.
Level: 1

Type: ERROR

Impact: Other

OAB-44008: The appliance {0} has ovm-template-config version {1}, whereas appliance {2} has conflicting version {3}.OVF generation must specify a single version.

Cause: (See message)

Action: Re-template appliances using base images with matching ovm-template-config packages.
Level: 1

Type: ERROR

Impact: Other

OAB-45101: Error creating file ''{0}'' for storing properties.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45101: Script directory ''{0}'' is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45102: Error writing properties to file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45102: Script directory ''{0}'' is not readable.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45103: Error opening file ''{0}'' for reading properties.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45103: Unable to open property file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45104: Error reading properties from file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45104: Variable declaration missing ''=''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45105: Error copying plug-in file ''{0}'' to ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45105: Bad variable name ''{0}''. Variable names must match regular expression ''[a-zA-Z0-9_.-]+''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45106: Unable to connect to remote server with parameters host={0}, port={1}, user={2}, and key file={3}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45106: Problem encountered while reading property file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45107: Unable to connect to remote server with entered password and parameters host={0}, port={1}, and user={2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45107: Error editing property file by reading ''{0}'' and writing to ''{1}}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45108: Error closing connection.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-45108: Error parsing property file {0} at line {1}: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45109: Unable to locate the standard temporary directory within the AB_INSTANCE.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45109: Script ''{0}'' already exists in phase directory ''{1}''

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45110: Error creating a temporary file in the standard temporary directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45110: Error adding script: ''{0}'' does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45111: Error creating a temporary directory at path ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45111: Error adding script: ''{0}'' is not a file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45112: Error copying plug-in configuration file from remote directory ''{0}'' to local directory ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45112: Cannot read script file ''{0}''

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45113: Error copying remote file ''{0}'' to local directory ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45113: Cannot read script directory ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45114: The configuration for plug-in named ''{0}'' does not exist in the search tree.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45114: Internal error executing script ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45115: Plug-in ''{0}'' is not installed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45115: Specified endpoint directory does not exist: ''{0}''

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45116: Cannot enable extension ''{0}'' because parent ''{1}'' is disabled.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45116: Internal error creating launch script for executing ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45117: Version of parent ''{0}'' is less than minimum version required by extension ''{1}''.

Cause: Parent version is {0} but extension requires version {1}.

Action: Upgrade the parent to a compatible version.
Level: 1

Type: ERROR

Impact: Other

OAB-45117: Script ''{0}'' completed with non-zero exit code ({1}).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-45118: Operation not permitted on plug-in ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45118: Specified endpoint directory path is not a directory: ''{0}''

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45119: Installed SDK version is {0} but plug-in ''{1}'' requires SDK version {2} or newer.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45119: Unable to read specified endpoint directory: ''{0}''

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45120: Illegal attempt to downgrade plug-in ''{0}'' from version {1} to lesser or equal version {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45120: Error creating input file ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45121: Error attempting to backup directory by renaming {0} to {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45121: Invalid property key ''{0}'' found in propery file for endpoint ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45122: Unable to install plug-in ''{0}'' because parent plug-in ''{1}'' is not installed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45122: Missing required property ''{0}'' in property file for endpoint ''{1}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45123: Unable to create one or more directories in the following path: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45123: Value supplied for key ''{0}'' is not in encrypted form.

Cause: (See message)

Action: Generate encrypted values by executing 'abctl encryptProperties' from the current AB_INSTANCE.
Level: 1

Type: ERROR

Impact: User Input

OAB-45124: Unable to add property named ''{0}'' as it already exists in the appliance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-45126: The path ''{0}'' does not exist or is not a directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45129: Error occurred while reading contents of directory ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45130: Unknown error attempting to remove plug-in directory ''{0}''.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45134: The plug-in configuration file ''{0}'' does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Files

OAB-45135: Error moving introspector plug-in file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45136: Error patching GenericProd plug-in.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45201: Error preparing the catalog for introspection.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45205: Unable to create introspection named ''{0}''.

Cause: An assembly or appliance with that name already exists.

Action: Use "-force" to overwrite.
Level: 1

Type: ERROR

Impact: User Input

OAB-45210: Error initializing the remote connection

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45211: Error initializing local execution context.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45220: Interrupted during introspection execution.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45221: Introspection failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45230: Packaging failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-45231: Cannot capture file sets for assembly {0} because it contains appliances with non-uniform file set definitions.

Cause: The assembly members are divided into {0} groups, each of which shares file set definitions: {1}.

Action: Capture file sets individually for one member of each of the above groups.
Level: 1

Type: ERROR

Impact: User Input

OAB-45232: Cannot capture file sets for {0} because it belongs to the following assemblies that have assembly archives: {1}.

Cause: Cannot capture file sets for a member of any assembly that has an assembly archive.

Action: Delete the assembly archives for all assemblies that contain the specified element.
Level: 1

Type: ERROR

Impact: User Input

OAB-45233: Cannot capture file sets for external appliance {0}.

Cause: (See message)

Action: Make sure that the appliance you are trying to capture file sets for is not an external appliance.
Level: 1

Type: ERROR

Impact: User Input

OAB-45234: Cannot capture file sets for external resource {0}.

Cause: (See message)

Action: Make sure that the appliance you are trying to capture file sets for is not an external resource.
Level: 1

Type: ERROR

Impact: User Input

OAB-45235: File sets have already been captured for {0}.

Cause: (See message)

Action: Use -force to override.
Level: 1

Type: ERROR

Impact: User Input

OAB-90002: Unable to send response to remote side for an incoming ping.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-90005: Remote OVAB process is already running - Started by user "{0}" on host "{1}" at ab_instance "{2}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-90006: Unable to send Ping to remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-90008: Unable to read Ping from remote side.

Cause: The remote process may be running while its directory has been deleted.

Action: Verify the remote process is down on the remote machine.
Level: 1

Type: ERROR

Impact: Network

OAB-90009: Unable to start the remote process.

Cause: Error in starting process.

Action: See AB_INSTANCE/assemblybuilder.log for more information.
Level: 1

Type: ERROR

Impact: Process

OAB-90021: Error in unzip of OVAB on remote machine. Exit code {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-90042: Error in killing remote process. Response from kill -9 was {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Process

OAB-90050: Thread interrupted, thread is continuing.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-90055: Error initializing the remote connection

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-90061: Unable to create connection to remote server.

Cause: Timed out trying to connect to IPV4 and IPV6 sockets. Remote process is not up or there are network connection issues.

Action: Verify port forwarding is enabled on remote machine. If sudoUser option is used, verify the remote user has sudo permissions.
Level: 1

Type: ERROR

Impact: Network

OAB-90102: Unable to obtain socket on address:port {0}:{1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-90204: Unable to initialize RemoteExecutionContext. Remote agent will be shut down.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-90207: Logging error detected during shutdown of remote assemblybuilder. Shutdown of connection will continue.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-90208: Unable to process Method request. Exception will be logged here and sent to caller.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90209: Method parameters are incompatible with method:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90210: Exception thrown by method, {0}. Cause will be sent back to other side.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90211: Unable to invoke inaccessible method, {0}. Cause will be sent back to other side.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90213: Remote AssemblyBuilder agent could not be shut down. Connection to agent will be closed anyway.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90214: Unable to get AbHome from configuration. No directories will be checksummed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90250: Unable to process request with unrecognized method name: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90251: Packaged appliance {0} still has old packageId {1}. None of its files will be copied from remote side.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90252: Ping object {0} cannot be processed. The ping listener is not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90253: Unable to process object {0}. Object type is not recognized.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-90254: Unable to process null object read from stream. Object will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-95526: Appliance {0}''s CaptureId cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96001: Unable to write Remote Instance ID information to file {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96002: Unable to send response to remote side for an incoming ping.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-96003: Unable to send response to remote side for method. Method name: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-96004: Unable to send method to remote side. Method name: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-96050: Thread interrupted, thread is continuing.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96100: Unable to initialize object stream.s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-96101: Error in reading from object stream.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-96200: Unable to create method response.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96201: Error in underlying communication

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-96202: Remoting error thrown.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96203: Unable to dispatch method call '{0}'. Method has no listeners.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96205: Unable to load Remote Instance ID information from file {0}. Keeping original values (which may be empty).

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-96206: Unable to send shutdown signal to other side. The connection will be closed anyway.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-96212: Notifying method callers and listeners that we received an unexpected exception. This side is exiting.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAB-96252: Ping object {0} cannot be processed. The ping listener is not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-96253: Unable to process object {0}. Object type is not recognized.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-96254: Unable to process null object read from stream. Object will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-97100: Unable to close client socket

Cause:

Action:
Level: 1

Type: WARNING

Impact: Network

OAB-97101: Unable to close listening socket

Cause:

Action:
Level: 1

Type: WARNING

Impact: Network

OAB-97102: Failed to acquire listening socket.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-97103: Unable to accept client connection

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-97104: Unable to make new client connection. Attempt will be repeated.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-97105: Remote configuration could not be loaded.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-97106: Unable to process Method request. Exception will be logged here and sent to other side.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-97107: Exception thrown by method, {0}. Cause will be sent back to other side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

OAB-97200: Creating socket listener on address {0} port {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Network

OAB-97201: Remote copy is skipping non-directory '{0}'.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Files

OAB-97202: Unable to process request with unrecognized method name: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-97203: An application 'start' request has been rejected. The application is already started.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

OAB-110001: Another AB client (CLI or GUI) is already running in this environment %s

Cause: Another AB client for this AB_HOME already running. Running concurrent tools is unsupported

Action: Wait for another tool to exit
Level: 1

Type: ERROR

Impact: Deployment

OAB-110002: Catalog %s is in use by another AB client (CLI or GUI)

Cause: Specified catalog is in use by another AB client. Concurrent access to the catalog is unsupported

Action: Wait for another tool to exit
Level: 1

Type: ERROR

Impact: Deployment

OAB-110003: Invalid AB_HOME

Cause: Environment variable AB_HOME is invalid or doesn't exist or unset

Action: Check the underlying cause to take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111001: Configuration is not valid.

Cause: The configuration has the following problems: {0}.

Action: The configuration information may be in assembly metadata, appliance metadata or the deployment plan. Locate and either update or delete the configuration artifacts associated with the listed problems.
Level: 1

Type: WARNING

Impact: User Input

OAB-111002: Invalid path {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-111003: Unknown type {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-111004: Property {0} does not exist in {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-111201: Catalog id must be specified

Cause: Supplied catalog id is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111202: Appliance or assembly name must be specified

Cause: Supplied appliance/assembly name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111203: Invalid or unspecified template name

Cause: Supplied template name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111204: Deployment id must be specified

Cause: Supplied deployment id is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111205: User id must be specified

Cause: Supplied user id is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111206: Key must be specified

Cause: Supplied key is null

Action: Supply non-null key
Level: 1

Type: ERROR

Impact: Deployment

OAB-111207: Cannot release the lock %s

Cause: This member may not be owner of the supplied lock or supplied lock may have locked

Action: Contact Oracle customer support with all log files
Level: 1

Type: ERROR

Impact: Deployment

OAB-111208: Cannot acquire lock on %s

Cause: The specified key is already in use

Action: Wait for the other process to complete
Level: 1

Type: WARNING

Impact: Deployment

OAB-111209: Could not release the lock on %s

Cause: This process may not be the owner of the lock on the specified key

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-111210: Lock must be specified for this operation

Cause: Supplied lock is null

Action: Supply a non-null value
Level: 1

Type: ERROR

Impact: Deployment

OAB-111211: Keys must be specified for this operation

Cause: Supplied keys object is either null or is an empty list

Action: Supply a list with at least one key
Level: 1

Type: ERROR

Impact: Deployment

OAB-111212: Locks must be specified for this operation

Cause: Supplied locks object is either null or is an empty list

Action: Supply a list with at least one lock value.
Level: 1

Type: ERROR

Impact: Deployment

OAB-111213: Keys %s cannot be locked

Cause: Specified keys are already locked

Action: Wait for other process to release the locks.
Level: 1

Type: WARNING

Impact: Deployment

OAB-111214: Locks %s cannot be released

Cause: The specified locks are not currently locked

Action: Contact Oracle customer support with necessary log files
Level: 1

Type: ERROR

Impact: Deployment

OAB-111215: Plan name must be specified

Cause: Supplied plan name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111216: Illegal release call on lock %s. This member %s is trying to release lock while its owner is %s.

Cause: This member is not the owner for the specified lock.

Action: Contact Oracle customer support with necessary log files
Level: 1

Type: ERROR

Impact: Deployment

OAB-111217: Invalid lock %s

Cause: System does not have the specified lock active

Action: Contact Oracle customer support with necessary log files
Level: 1

Type: ERROR

Impact: Deployment

OAB-111218: Cannot lock the deployment plan %s for the assembly %s in the catalog %s

Cause: The specified assembly is already locked by some other process

Action: Try again after it is unlocked
Level: 1

Type: WARNING

Impact: Deployment

OAB-111219: Cannot lock the assembly %s in the catalog %s

Cause: Some of the deployment plans for the specified assembly are currently locked

Action: Try again after they are unlocked
Level: 1

Type: WARNING

Impact: Deployment

OAB-111220: Ova name must be specified

Cause: Supplied ova name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111221: Ova version must be specified

Cause: Supplied ova version is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111222: Acquired lock: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111223: Released lock: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111224: Snapshot id must be specified

Cause: Supplied snapshot id is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-111407: Appliance instance %s - created

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111408: Appliance instance %s - initialized

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111409: Appliance instance %s - started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111410: Appliance instance %s - exited

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111411: Appliance instance %s - destroyed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111412: Appliance instance %s - about to start

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111413: Appliance instance %s - about to suspend

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111414: Appliance instance %s - suspended

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111415: Appliance instance %s - resumed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111416: Initialization of appliance instance {0} has failed. An attempt will be made to cleanup the appliance instance.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111417: An error has occurred while attempting to clean up failed appliance instance %s: Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111418: Failed to restore appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111419: Failed to remove appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111420: Restored appliance instance %s. Appliance instance state after the restoration - %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111424: Error occurred while creating the vNet %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111425: Error occurred while fetching vNets in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111426: Error occurred while attaching the vNet %s to the instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111427: Error occurred while detaching the vNet %s from the instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111428: Error occurred while destroying the vNet %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111429: Error occurred while creating the vNet %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111430: Error occurred while fetching the vNets in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111431: Error occurred while attaching the vNet %s to the instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111432: Error occurred while detaching the vNet %s from the instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111433: Error occurred while destroying the vNet %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111434: Error occurred while finding the vNet %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111435: Error occurred while finding the vNet %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111436: Error occurred while attempting to reserve addresses in the vNet %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111437: Error occurred while attempting to reserve addresses in the vNet %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111438: Error occurred while attempting to release addresses %s to the vNet %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111439: Error occurred while attempting to release addresses %s to the vNet %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111440: Restoring appliance instance %s and it is expected to be in %s state

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111441: Appliance instance %s - creating...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111442: Appliance instance %s - initializing...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111443: Appliance instance %s - stopping...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111444: Appliance instance %s - destroying...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111445: Appliance instance %s - resuming...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111446: Error occurred while attempting to create virtual disk %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111447: Error occurred while attempting to create virtual disk %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111448: Error occurred while attempting to create virtual disks in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111449: Error occurred while attempting to create virtual disks in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111450: Error occurred while attempting to attach virtual disk %s to the appliance instance %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111451: Error occurred while attempting to attach virtual disk %s to the appliance instance %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111452: Error occurred while attempting to delete virtual disk %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111453: Error occurred while attempting to delete virtual disk %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111454: Error occurred while attempting to delete virtual disks %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111455: Error occurred while attempting to delete virtual disks %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111456: Error occurred while attempting to add tags to the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111457: Error occurred while attempting to add tags to the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111458: Error occurred while attempting to add tags to the ova assembly %s:%s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111459: Error occurred while attempting to add tags to the ova assembly %s:%s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111460: Error occurred while attempting to add tags to the appliance instance template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111461: Error occurred while attempting to add tags to the appliance instance template %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111462: Error occurred while attempting to remove tags on the instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111463: Error occurred while attempting to remove tags on the instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111464: Error occurred while attempting to remove tags on the ova assembly %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111465: Error occurred while attempting to remove tags on the ova assembly %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111466: Error occurred while attempting to remove tags on the appliance instance template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111467: Error occurred while attempting to remove tags on the appliance instance template %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111468: Error occurred while attempting to query tags on the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111469: Error occurred while attempting to query tags on the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111470: Error occurred while attempting to query tags on the ova assembly %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111471: Error occurred while attempting to query tags on the ova assembly %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111472: Error occurred while initializing appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111473: Suspend operation is not supported for the target %s

Cause: Suspend operation is not supported for the specified target

Action: Check the target type of the deployment
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111474: Resume operation is not supported for the target %s

Cause: Resume operation is not supported for the specified target

Action: Check the target type of the deployment
Level: 1

Type: ERROR

Impact: Deployment

OAB-111475: Could not find the appliance instance with the specified id %s

Cause: The appliance instance with the specified id no longer exists

Action: The appliance instance with the specified id is deleted
Level: 1

Type: ERROR

Impact: Deployment

OAB-111476: Error occurred while reserving the resources for the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111477: Appliance instance %s is in the invalid state %s. It is expected to be in the state %s

Cause: The specified appliance instance in the invalid state for the operation initiated

Action: Check the initiated operation in conjunction with the specified current state of the appliance instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-111478: Invalid appliance instance

Cause: Contact customer support

Action: Contact customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-111479: Error occurred while performing operation on the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111480: Stage operation on the appliance instance %s timedout

Cause: Operation timedout

Action: Check the appliance instance templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111481: Error occurred while stopping the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111482: Stop operation on the appliance instance %s timed out after %s seconds

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111483: Appliance instance with id %s does not exist

Cause: Appliance instance with the specified id either has been deleted or invalid

Action: Check the log file
Level: 1

Type: ERROR

Impact: Deployment

OAB-111484: Created virtual disk for %s with id %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111485: Attached virtual disk(ovfId=%s, id=%s) to the appliance instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111486: Virtual disk creation for %s failed. Cannot find registration for the assembly %s:%s in the target %s

Cause: No registration found for the corresponding assembly

Action: It might have been unregistered. Check the ovf server logs
Level: 1

Type: ERROR

Impact: Deployment

OAB-111487: Virtual disk creation for %s failed. Cannot find the specific template in the registration %s

Cause: Registration does not contain the specified template

Action: Invalid registration or invalid disk configuration in the assembly descriptor
Level: 1

Type: ERROR

Impact: Deployment

OAB-111488: Error occurred while attempting to check vnics availability in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111489: Error occurred while attempting to check vnics availability in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111490: Error occurred while reconfiguring or getting the network for the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111491: Error occurred while reconfiguring or getting the network for the appliance instance %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111492: Failed to configure the vNets on the appliance instance %s

Cause: Specified appliance instance did not receive vNet configured message in %d seconds

Action: Check to see if the appliance instance is reachable by SSH. If not, check and correct your vNet configuration and retry. For static IP networking, check gateway, netmask, DNS settings and IP address settings in the deployment plan. For DHCP networking, check your network router to insure DHCP is enabled and addresses are available for lease. If the appliance is reachable by SSH, then check the log files in /assemblybuilder and the instance home for errors that may have occurred during rehydration. If all seems well, the phone home timeout may need to be increased.
Level: 1

Type: ERROR

Impact: Deployment

OAB-111493: Appliance instance %s reported an error while configuring the network interfaces: %s

Cause: One or more required network interface configuration parameters was missing or incorrect

Action: Ensure that all required network interface configuration parameters were specified. Check assemblybuilder.log file and ab.out files on the appliance for details
Level: 1

Type: ERROR

Impact: Deployment

OAB-111494: Error occurred while locating the http service for the target %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111495: Error occurred while creating the virtual cdrom for the iso %s with the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111496: Error occurred while creating the virtual cdrom for the iso %s with the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111497: Error occurred while attaching the virtual cdrom %s with the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111498: Error occurred while attaching the virtual cdrom %s with the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111499: Error occurred while deleting the virtual cdrom %s from the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111521: Error obtaining pool metrics for target %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111522: Error obtaining pool metrics for target %s. Error is %s

Cause: Check the error in the message

Action: Take appropriate action for the error in the message
Level: 1

Type: ERROR

Impact: Deployment

OAB-111523: Status of appliance instance %s has changed from %s to %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111524: Appliance instance %s has EXITED

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111525: Error occurred during lookup of the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111526: Error occurred while retrieving all templates. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111527: Error occurred while retrieving the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111528: Error occurred while creating configuration spec for the new appliance instance %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111529: Error occurred while creating the new appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111530: Error occurred while starting the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111531: Error occurred while stopping the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111532: Error occurred while destroying the appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111533: Invalid appliance instance state. Appliance instance %s is in state %s but it is expected to be in %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111534: Error occurred while retrieving available vNet names. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111535: Failed to open client session for the target %s at the url %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111536: Invalid target %s specified to the target %s. Error is: %s

Cause: Check the underlying exception for the root cause

Action: Check the underlying exception to determine appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111537: Could not find the pool %s specified for the target %s

Cause: The pool may have been removed, disabled or deactivated using target specific instance manager

Action: Check the target logs to determine the appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111538: Error occurred while importing the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111539: Error occurred while deleting the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111540: Error occurred while getting the vNets for the target %s. Error is: %s

Cause: Check the underlying error for the root cause

Action: Check the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111541: Error occurred while sending a message with key %s to the appliance instance %s. Error is: %s

Cause: Check the underlying error for the root cause

Action: Check the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111542: Error occurred while receiving a message with key %s from the appliance instance %s. Error is: %s

Cause: Check the underlying error for the root cause

Action: Check the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111543: Error occurred while sending messages to the appliance instance %s. Error is: %s

Cause: Check the underlying error for the root cause

Action: Check the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111544: Error occurred while deleting the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111545: Failed to initialize HttpDownloadService: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111546: Error occurred while importing the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111547: Importing of the template %s timed out after %s seconds.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-111548: Error occurred while suspending appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111549: Error occurred while resuming appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111550: Create vNet is not supported in the target environment

Cause: A request has been initiated to create a private vNet, but the target environment does not support this capability

Action: Do not declare private vNets while using the specified target environment
Level: 1

Type: ERROR

Impact: Deployment

OAB-111551: Cannot find the vNet %s in the target %s

Cause: The specified vNet does not exist in the specified target

Action: Verify the vNet name specified in the ovf descriptor
Level: 1

Type: ERROR

Impact: Deployment

OAB-111552: [%s] Expected appliance instance state: %s - Current appliance instance state: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111553: Found appliance instance with the name %s : %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111554: Could not find the appliance instance %s

Cause: Appliance instance with the specified name does not exist

Action: Provide a valid virtual machine name
Level: 1

Type: ERROR

Impact: Deployment

OAB-111555: Error occured while checking the template %s in the target %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111556: Required template %s is not active. Its current state is %s

Cause: The specified template is not currently active

Action: Make sure that the templates are properly registered
Level: 1

Type: ERROR

Impact: Deployment

OAB-111557: Error occured in creating configuration spec for the new appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111558: Error occured while sending the appliance instance api message %s to the process %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111559: Error occured while receiving the appliance instance api message %s from the process %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111560: Error occured while sending the appliance instance api messages %s to the process %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111561: Error occured while receiving the appliance instance api message %s from the process %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111562: Error occured while looking up the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111563: Appliance instance with the name %s already exists

Cause: The specified appliance instance already exists in the target environment

Action: Check the deployment
Level: 1

Type: ERROR

Impact: Deployment

OAB-111564: Could not find the template for the appliance instance %s in the target %s

Cause: Templates may not have registered

Action: Register the templates
Level: 1

Type: ERROR

Impact: Deployment

OAB-111565: Could not find template %s in the target %s

Cause: Templates may not have registered

Action: Register the templates
Level: 1

Type: ERROR

Impact: Deployment

OAB-111566: Error occured while creating the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111567: Error occured while starting the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111568: Error occured while suspending the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111569: Error occured while resuming the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111570: Error occured while stopping the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111571: Error occured while destroying the appliance instance %s. Error is: %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111572: Appliance instance %s is in an unreachable state %s

Cause: Look at the target instance manager

Action: Look at the target instance manager
Level: 1

Type: ERROR

Impact: Deployment

OAB-111573: Appliance instance %s is in invalid state %s. It is expected to be in %s

Cause: The specified appliance instance is not in the expected state for the operation initiated

Action: Check the operation initiated
Level: 1

Type: ERROR

Impact: Deployment

OAB-111574: Initialize operation on the appliance instance %s timed out

Cause: Operation timed out

Action: Check the templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111575: Start operation on the appliance instance %s timed out

Cause: Operation timed out

Action: Check the templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111576: Suspend operation on the appliance instance %s timed out

Cause: Operation timed out

Action: Check the templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111577: Resume operation on the appliance instance %s timed out

Cause: Operation timed out

Action: Check the templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111578: Stop operation on the appliance instance %s timed out

Cause: Operation timed out

Action: Check the templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111579: Destroy operation on the appliance instance %s timed out

Cause: Operation timed out

Action: Check the templates and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111580: Could not start target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111581: Could not stop target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111582: Unexpected ovmm version %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111583: Created and initialized Virtual Machine %s for the process %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111584: Virtual disk creation for %s failed. Cannot find registration for the assembly %s:%s in the target %s

Cause: No registration found for the corresponding assembly

Action: The assembly might have been unregistered. Check the ovf server logs
Level: 1

Type: ERROR

Impact: Deployment

OAB-111585: Virtual disk creation for %s failed. Cannot find the specific template in the registration %s

Cause: Registration does not contain the specified template

Action: Invalid registration or invalid disk configuration in the assembly descriptor
Level: 1

Type: ERROR

Impact: Deployment

OAB-111586: Could not find server count for the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111587: Some virtual disks, particularly %s, are not created properly.

Cause: Target might have been restarted or creation failed silently

Action: Look at the target log files and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111588: No virtual disks created

Cause: Target might have been restarted or creation failed silently

Action: Look at the target log files and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111589: Insufficient vnics. Required %s but target %s has %s

Cause: The specified target does not contain the required number of vnics

Action: Increase the vnics in the target and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-111590: Target %s returned invalid network name

Cause: Returned network name is empty or null

Action: Check the target and fix it
Level: 1

Type: ERROR

Impact: Deployment

OAB-111591: Failed to register message listener with the appliance instance %s. Error is %s

Cause: Look at the target log files to find the appropriate root cause

Action: Look at the target log files to determine the appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111592: Failed to unregister message listener with the appliance instance %s. Error is %s

Cause: Look at the target log files to find the appropriate root cause

Action: Look at the target log files to determine the appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111593: VM messages for the appliance instance %s timed out

Cause: Operation timedout

Action: Check the target logs and increase the appliance instance operation timeout if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-111594: Invalid disk %s for restoring the appliance instance %s

Cause: The disk with specified ovf disk id is not attached to the specified appliance instance

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-111801: WLOC MSA Service %s started.

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111802: WLOC MSA Service %s stopped.

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111803: WLOC MSA Service %s restarted.

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111804: Warning from managed process: %s.

Cause: Warning from managed process.

Action: As appropriate for the message.
Level: 1

Type: WARNING

Impact: Deployment

OAB-111805: Information message from managed process: %s.

Cause: Information message from managed process.

Action: As appropriate for the message.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111806: Exception thrown from managed process: %s.

Cause: Exception thrown from managed process.

Action: As appropriate for the exception.
Level: 1

Type: ERROR

Impact: Deployment

OAB-111821: Reservation created for the process %s:%s:%s

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111822: Reserved process %s:%s:%s

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111823: Unreserved process %s:%s:%s

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111824: Process %s:%s:%s marked for in-use

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111825: Process %s:%s:%s unmarked for in-use

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111826: Reservation removed for the process %s:%s:%s

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111827: Restored processes from the filestore and added them to the cache.

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111828: Restored processes %s

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111841: Error occurred while reading store %s. Error is: %s

Cause: Check the log file for cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111842: Error occurred while writing to store %s. Error is: %s

Cause: Check the log file for cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111843: Using default filestore configuration.

Cause: Normal.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111844: Using filestore configuration provider %s.

Cause: Normal.

Action: No action required.
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111845: Shutdown on filestore cache %s - Completed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111861: No active pool can satisfy required resource %s

Cause: Normal operation.

Action: No Action Required.
Level: 1

Type: WARNING

Impact: Deployment

OAB-111862: Target name must be specified

Cause: Target name was unspecified

Action: Specify the target
Level: 1

Type: ERROR

Impact: Deployment

OAB-111863: Invalid or unspecified user name

Cause: User ame was unspecified

Action: Specify the user name
Level: 1

Type: ERROR

Impact: Deployment

OAB-111864: Invalid target type %s

Cause: Supplied target type is unsupported

Action: Provide supported target type
Level: 1

Type: ERROR

Impact: Deployment

OAB-111865: Default target is not defined

Cause: Default is not configured

Action: Configure a default target
Level: 1

Type: ERROR

Impact: Deployment

OAB-111881: Error occurred while executing work %s. Error is: %s

Cause: Check the log file for cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111882: Error occurred while executing work %s. Error is: %s

Cause: Check the log file for cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111883: Error occurred while scheduling work %s. Error is: %s

Cause: Check the log file for cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-111884: WorkManager lookup for %s failed with error %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-111885: Creating local workmanager for %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-111886: No thread available to execute the work on the work manager %s

Cause: Check the log file for the appropriate root cause

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112001: Invalid or unspecified assembly name

Cause: Supplied assembly name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112002: Assembly version must be specified

Cause: Supplied assembly version is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112003: Invalid or unspecified assembly archive

Cause: Supplied assembly archive is null

Action: Supply non-null stream
Level: 1

Type: ERROR

Impact: Deployment

OAB-112004: Error occurred while uploading a new archive for the assembly %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112005: Cannot find assembly %s

Cause: Supplied assembly does not exist in the repository

Action: Provide a valid assembly name
Level: 1

Type: ERROR

Impact: Deployment

OAB-112006: Cannot find assembly %s:%s

Cause: Supplied assembly does not exist in the repository

Action: Provide a valid assembly
Level: 1

Type: ERROR

Impact: Deployment

OAB-112007: Error occurred while updating assembly %s:%s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112008: Cannot find configuration for deployer

Cause: Internal error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112009: Failed to create deployer runtime directory %s

Cause: User may not have permissions write permissions or the directory is read only or insufficient disk space

Action: Check the cause and fix it accordingly
Level: 1

Type: ERROR

Impact: Deployment

OAB-112010: Deployer config directory %s does not exist

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112011: Failed to create the directory for the deployer's repository

Cause: User may not have permissions write permissions or the directory is read only or insufficient disk space

Action: Check the cause and fix it accordingly
Level: 1

Type: ERROR

Impact: Deployment

OAB-112012: Error occurred while initializing the directory for the deployer's runtime. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112013: Error occurred while initializing the directory for the deployer's repository. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112014: Cannot find the assembly instance with identifier %s

Cause: The assembly instance for the supplied identifier does not exist. Either it has been removed or never exist

Action: Provide valid assembly instance id
Level: 1

Type: ERROR

Impact: Deployment

OAB-112015: Cannot find assembly instance plan %s for the assembly %s

Cause: No assembly instance plan exists for the supplied assembly instance plan name for the supplied assembly

Action: Provide valid assembly instance plan name
Level: 1

Type: ERROR

Impact: Deployment

OAB-112016: Error occurred while reading assembly instance plan. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112017: Cannot find the member for the identifier %s

Cause: Member for the supplied identifier does not exist. Either it has been removed or never exist

Action: Provide valid member id
Level: 1

Type: ERROR

Impact: Deployment

OAB-112018: The assembly instance %s cannot be undeployed. It is in failed state

Cause: The supplied assembly instance is in failed state. It cannot be undeployed

Action: Use a proper assembly instance indentifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112019: Assembly instance identifier must be specified

Cause: Supplied assembly instance identifier is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112020: Appliance path must be specified

Cause: Supplied appliance path is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112021: Appliance identifier must be specified

Cause: Supplied appliance identifier is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112022: Appliance instance identifier must be specified

Cause: Supplied appliance instance identifier is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112023: Appliance instance path must be specified

Cause: Supplied appliance instance path is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112024: Appliance instance index must be non-negative value

Cause: Supplied appliance instance index is a negative value

Action: Supply non-negative integer
Level: 1

Type: ERROR

Impact: Deployment

OAB-112025: Invalid appliance identifier %s

Cause: Member found for the supplied identifier is not an appliance

Action: Check the supplied appliance path or identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112026: Member %s is not an appliance instance

Cause: Member found for the supplied identifier is not an appliance instance

Action: Check the supplied appliance instance path or identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112027: Cannot find the appliance %s in the assembly instance %s

Cause: Invalid appliance path or id

Action: Check the supplied appliance path
Level: 1

Type: ERROR

Impact: Deployment

OAB-112028: Error occurred while creating the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112029: Invalid assembly instance identifier %s

Cause: Member found for the supplied identifier is not an assembly instance

Action: Check the supplied assembly instance identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112030: Invalid or unspecified assembly instance

Cause: Supplied assembly instance is null

Action: Supply a non-null assembly instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112031: The assembly instance %s is not in any of the states %s. So, it cannot be removed

Cause: The assembly instance for the supplied identifier is not in any valid state for the delete operation

Action: Check the status and try a valid assembly instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112032: Invalid or unspecified member object

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112033: Appliance %s reached its maximum scalability %s

Cause: All appliance instances upto the configured scalability maximum of the appliance are in use. It cannot be scaled up.

Action: No action required.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112034: Error occurred while uploading resources for the assembly %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112035: Assembly instance %s is not currently deployed. Appliance %s cannot be scaled

Cause: An attempt was made to scale the assembly instance that is currently undeployed

Action: Deploy or start the assembly instance before attempting to perform the scale operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112036: Cannot scale the appliance. Appliance %s is already at the requested target %s

Cause: The specified appliance already has instances at the requested target

Action: No action required
Level: 1

Type: ERROR

Impact: Deployment

OAB-112037: Cannot scale because failed %d instances exist in the assembly.

Cause: There are failed appliance instances in the assembly instance.

Action: Correct the problem that caused the appliance instance to fail then undeploy and redeploy the assembly.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112038: Cannot scale the appliance. Supplied target %s for the appliance %s is above its maximum scalability requirement %s

Cause: The target count specified for the supplied appliance is above its maximum scalability requirement.

Action: No action required
Level: 1

Type: ERROR

Impact: Deployment

OAB-112039: Cannot scale the appliance. Supplied target %s for the appliance %s is below its minimum scalability requirement %s

Cause: The target count specified for the supplied appliance is below its minimum scalability requirement.

Action: No action required
Level: 1

Type: ERROR

Impact: Deployment

OAB-112040: Error occurred while reading the configuration for the appliance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112041: Provided key is null or empty

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112042: Template metadata for the appliance %s is invalid. It does not define name.

Cause: Name unspecified in the template

Action: Specify name in the template
Level: 1

Type: ERROR

Impact: Deployment

OAB-112043: Cannot find property named component for the appliance %s

Cause: Incorrect generation of the assembly metadata

Action: Generate the assembly metadata properly or contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112044: Did not receive first boot exited callback on the process %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112045: Error occurred while setting up resource pools configuration

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112046: Cannot find state for the index %s

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112047: State %s is not transitionable

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112048: Hostname for the index %s in the appliance %s does not exist

Cause: Internal Error. Could not resolve host name for the specified index

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112049: Assembly instance %s is in intermediate state %s while being restored from the persistence

Cause: The previous operation was terminated prior to the completion of the operation

Action: Undeploy and/or remove the assembly instance and create and deploy it again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112050: Error occurred while restoring the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112051: Assembly instance request %s for the operation %s on the assembly instance %s - Failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112052: Generate late bindings failed on the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112053: First boot power off for the appliance instance %s failed

Cause: Check the target environment logs for the root cause

Action: Check the target environment logs to take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-112054: First boot PowerOff on the appliance instance %s failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112055: Rehydration on the appliance instance %s failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112056: Stop operation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112057: PowerOn failed on the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112058: Hostname phonehome failed on the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112059: External appliance process %s exited before wait period expired.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112060: Readymetric verification on the appliance instance %s failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112061: Error occurred while sending late bindings for the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112062: Error occurred while sending vNet configuration for the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112063: Error occurred while sending stop reason for the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112064: Assembly instance %s is in an invalid state %s. It will be marked failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112065: Appliance instance %s is in an invalid state %s. It will be removed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112066: Appliance instance %s does not have associated process. It will be removed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112067: Process %s for appliance instance %s is in the state %s but it is supposed to be in %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112068: Failure occurred while receiving the stop-result for the appliance instance %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112069: Registered deployer handler with phonehome listener

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112070: VNet on the appliance instance %s is static and HostName set to %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112071: VNet on the appliance instance %s is DHCP and HostName set to %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112072: Error occurred while invoking callback %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112073: [Deployer Request: %s] %s operation on the assembly instance %s - Succeeded

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112074: Upload assembly request failed. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112075: Update assembly request failed. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112076: Successfully uploaded assembly %s:%s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112077: Successfully updated assembly %s:%s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112078: Error occurred while deleting the assembly %s:%s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112079: Delete assembly request failed. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112080: Error occurred while initiating registration request for the assembly %s:%s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112081: Error occurred while initiating unregistration request for the assembly %s:%s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112082: Registration request for the assembly %s:%s with the target %s failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112083: Unregistration request for the assembly %s:%s with the target %s failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112084: Cannot find request with identifier %s

Cause: No request exists with the identifier %s

Action: Provide a proper request identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112085: Deployer request initiation failed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112086: Appliance instance identifiers must be specified

Cause: Supplied appliance instance identifiers parameter is either null or empty

Action: Provide a valid connection of identifiers
Level: 1

Type: ERROR

Impact: Deployment

OAB-112087: Appliance instance with identifier %s does not exist

Cause: Appliance instance with the supplied identifier does not exist

Action: Provide a valid appliance instance identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112088: Appliance instance with the identifier %s does not belong to the assembly instance %s

Cause: Appliance instance with the supplied identifier does not belong to the supplied assembly instance

Action: Provide a valid appliance instance identifier that belong to the supplied assembly instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112089: Validation errors found. Errors are: %s

Cause: Check the errors for the possible causes

Action: Check the errors and fix as appropriate
Level: 1

Type: ERROR

Impact: Deployment

OAB-112090: Assembly instance %s is not in any expected states %s. Its current state is %s

Cause: The assembly instance for the supplied identifier is not in any valid state for the requested deployer operation

Action: Check the status and try a valid assembly instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112091: Appliance instance %s is not in any expected states %s. Its current state is %s

Cause: The appliance instance for the supplied identifier is not in any valid state for the requested deployer operation

Action: Check the status and try a valid appliance instance identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112092: [Deployer Request: %s] %s operation on assembly instance %s - Initiated

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112093: [Deployer Request: %s] %s operation on the appliance %s in the assembly instance %s - Initiated

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112094: [Deployer Request: %s] %s operation on the appliance instances %s in the assembly instance %s - Initiated

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112095: [Deployer Request: %s] %s operation on the appliance %s in the assembly instance %s - Succeeded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112096: [Deployer Request: %s] %s operation on the appliance instances %s in the assembly instance %s - Succeeded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112097: [Deployer Request: %s] %s operation on assembly instance %s - Failed. Error is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112098: [Deployer Request: %s] %s operation on the appliance %s in the assembly instance %s - Failed. Error is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112099: [Deployer Request: %s] %s operation on the appliance instances %s in the assembly instance %s - Failed. Error is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112100: Appliance %s - Staged

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112101: Appliance %s - Prepared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112102: Appliance %s - Deployed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112103: Appliance %s - Stopped

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112104: Appliance %s - Unprepared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112105: Appliance %s - Undeployed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112106: Appliance %s - Suspended

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112107: Appliance %s - Failed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112108: Appliance %s - Staging

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112109: Appliance %s - Preparing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112110: Appliance %s - Starting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112111: Appliance %s - Stopping

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112112: Appliance %s - Unpreparing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112113: Appliance %s - Unstaging

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112114: Appliance %s - Suspending

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112115: Appliance %s - Resuming

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112116: Oracle Virtual Assembly Builder Deployer successfully started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112117: Cannot delete requests %s

Cause: The specified requests are currently running

Action: Provide requests that are completed
Level: 1

Type: ERROR

Impact: Deployment

OAB-112118: Cannot delete the assembly %s. It has existing assembly instances %s

Cause: The specified assembly has assembly instances

Action: Provide assembly that has no assembly instances
Level: 1

Type: ERROR

Impact: Deployment

OAB-112119: Cannot delete assemblies %s:%s. Assembly instances %s exists for the supplied assemblies

Cause: The specified assemblies has assembly instances

Action: Provide assemblies that has no assembly instances
Level: 1

Type: ERROR

Impact: Deployment

OAB-112120: Cannot find template for the appliance instance %s in the assembly instance %s in the resource pool %s

Cause: The assembly might not have been registered

Action: Register the assembly and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112121: Cannot find template for the appliance %s in the assembly %s:%s in the resource pool %s

Cause: The assembly might not have been registered

Action: Register the assembly and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112122: Resource validation failed: [ %s ]

Cause: Specified resources are not available.

Action: Check the error and take the appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-112123: Insufficient %s resource. Required %s but available %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112124: Cannot deploy the assembly %s:%s. It is not registered with the resource pool %s

Cause: The specified assembly is not registered with the specified resource pool

Action: Register the assembly and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112125: [Registration Request: %s] %s operation on the assembly %s:%s with the target %s - Successful

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112126: [Registration Request: %s] %s operation on the assembly %s:%s with the target %s - Failed. Error is: %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-112127: Appliance instance %s in the assembly instance %s cannot be suspended. It is in %s state.

Cause: Specified appliance instance is in the state that is invalid for transitioning to suspend state

Action: Check the appliance instance state
Level: 1

Type: ERROR

Impact: Deployment

OAB-112128: Appliance instance %s in the assembly instance %s cannot be resumed. It is in %s state.

Cause: Specified appliance instance is in the state that is invalid for transitioning to resume state

Action: Check the appliance instance state
Level: 1

Type: ERROR

Impact: Deployment

OAB-112129: Error while validating assembly instance %s in list assembly instances operation

Cause: Resource pool may be unavailable

Action: Check the resource pool status in target specific manager
Level: 1

Type: ERROR

Impact: Deployment

OAB-112130: Error occurred while unregistering the assembly %s:%s from the resource pool %s:%s. Error is %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112131: Cannot delete assembly %s for the versions %s

Cause: The specified assembly versions are currently registered

Action: Unregister the specified versions and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112132: Assembly %s:%s has already been registered with the resource pool %s

Cause: A given assembly cannot be registered more than once with a given resource pool

Action: Try it with a different assembly name and/or different version
Level: 1

Type: ERROR

Impact: Deployment

OAB-112133: Cannot unregister the assembly %s:%s from the resource pool %s. It has assembly instances %s

Cause: It cannot be unregistered when there are assembly instances

Action: Delete the specified assembly instances prior to attempting to unregister the assembly
Level: 1

Type: ERROR

Impact: Deployment

OAB-112134: The assembly %s isn't registered with the target %s. Nothing to do

Cause: The supplied assembly isn't registered with the supplied target

Action: Try it with a different assembly
Level: 1

Type: ERROR

Impact: Deployment

OAB-112135: Cannot acquire lock on the assembly %s:%s

Cause: The specified assembly is currently in use by some other operation

Action: Try the operation when it is unlocked
Level: 1

Type: ERROR

Impact: Deployment

OAB-112136: Error occurred while initiating registration request for assembly %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112137: The assembly %s:%s isn't registered with the target %s. Nothing to do

Cause: The supplied assembly isn't registered with the supplied target

Action: Try it with a different assembly name and/or different version
Level: 1

Type: ERROR

Impact: Deployment

OAB-112138: Cannot find property named component for the appliance instance %s

Cause: Incorrect generation of the assembly metadata

Action: Generate the assembly metadata properly or contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112139: Cannot resolve hostname for the appliance instance %s

Cause: Eth0 interface is configured for static but it does not define ip_address property

Action: Check the assembly instance plan and fix the above mentioned problem
Level: 1

Type: ERROR

Impact: Deployment

OAB-112140: Target user must be specified

Cause: Supplied target user is either null or empty

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112141: Invalid request id %s

Cause: No request exists for the supplied request id

Action: Supply a valid request id
Level: 1

Type: ERROR

Impact: Deployment

OAB-112142: Invalid time lived seconds parameter

Cause: Supplied parameter value is non-positive integer

Action: Supply a positive integer value
Level: 1

Type: ERROR

Impact: Deployment

OAB-112143: Cannot delete target %s:%s

Cause: The specified target is in use. It has registered assemblies or assembly instances

Action: Make sure the supplied target does not have registered assemblies or deployed assemblies
Level: 1

Type: ERROR

Impact: Deployment

OAB-112144: Phone home request timed out for the phonehome type %s uid %s

Cause: A phone home call from the deployed VM was not received in %d seconds

Action: Check to see if the appliance instance is reachable by SSH. If not, check and correct your vNet configuration and retry. For static IP networking, check gateway, netmask, DNS settings and IP address settings in the deployment plan. For DHCP networking, check your network router to insure DHCP is enabled and addresses are available for lease. If the appliance is reachable by SSH, then check the log files in /assemblybuilder and the instance home for errors that may have occurred during rehydration. If all seems well, the phone home timeout may need to be increased.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112145: [Registration Request: %s] %s operation for the assembly %s:%s with the target %s - Initiated

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112146: Registration identifier must be provided

Cause: Supplied registration identifier is either null or empty

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112147: Invalid assembly instance identifiers: %s

Cause: Above assembly instance identifiers does not exist in the system

Action: Supply valid assembly instance identifiers
Level: 1

Type: ERROR

Impact: Deployment

OAB-112148: Error occurred while loading version file. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112149: Oracle Assembly Builder Deployer Specification Version: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112150: Oracle Assembly Builder Deployer Implementation Version: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112151: Java VM Info: %s (build %s, %s)

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112152: Java Runtime Info: %s (build %s)

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112153: Cannot find disk with the name %s

Cause: Specified disk does not have disk configuration in the assembly metadata

Action: Fix the assembly metadata and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112154: Received empty or null hostname from the appliance %s

Cause: Look at the assemblybuilder.log file and ab.out file on the appliance

Action: Look at the assemblybuilder.log file and ab.out file on the appliance to take the appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-112155: Error occurred while creating the assembly instance for the assembly %s:%s for the target %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112156: Error occurred while deleting the assembly instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112157: Invalid appliance %s. It must contain at least one vNet

Cause: The specified appliance does not have any vNets configured

Action: Fix the assembly metadata and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112158: Removing appliance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112159: Successfully removed appliance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112160: Appliance %s is a black box appliance. Not configuring vNet on the appliance

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112161: Cannot add or delete tags to the appliance instance %s. Specified appliance instance is in FAILED state

Cause: The specified appliance instance is in FAILED state

Action: Supply a valid appliance instance identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112162: Cannot add or delete tags to the appliance instance %s. The assembly instance object for the specified appliance instance is in FAILED stage

Cause: The assembly instance object for the specified appliance instance is in FAILED stage

Action: Supply a valid appliance instance identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112163: Error occurred while adding or deleting the tags to the appliance instance %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112164: Registration identifier must be provided

Cause: Supplied registration identifier is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112165: Invalid Registration identifier

Cause: Registration with the supplied registration identifier does not exist

Action: Supply a valid registration identifier
Level: 1

Type: ERROR

Impact: Deployment

OAB-112166: Member identifier must be provided

Cause: Supplied member id is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112167: Cannot find the registered assembly for the appliance %s

Cause: Supplied appliance is invalid

Action: Supply a valid appliance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112168: Invalid resource identifiers: %s

Cause: The above specified ids are not appliance instance ids or registration ids

Action: Specify valid registration or appliance instance ids
Level: 1

Type: ERROR

Impact: Deployment

OAB-112169: Invalid resource identifier: %s

Cause: The above specified id is not an appliance instance id, registration id or assembly archive name

Action: Specify a valid registration id, appliance instance id or assembly archive name
Level: 1

Type: ERROR

Impact: Deployment

OAB-112170: Address for the vNet %s for the appliance instance %s was not reserved

Cause: An error encountered while reserving the address

Action: Look at the target environment log files
Level: 1

Type: ERROR

Impact: Deployment

OAB-112171: Cannot find static address for the vNet %s for the appliance instance %s

Cause: Assembly instance plan does not contain address for the specified appliance instance

Action: Provide address in the assembly instance plan
Level: 1

Type: ERROR

Impact: Deployment

OAB-112172: Cannot reserve address for the vNet %s for the appliance instance %s

Cause: Look at the target environment log files for the possible root causes

Action: Look at the target environment log files and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-112173: Error occurred while getting file source %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112174: Cleanup operation on the process %s failed. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112175: Cleanup operation on the process %s timed out after %s seconds

Cause: Look at the target environment log files for the possible root causes or timeout value is too short for this operation

Action: Look at the target environment log files and take appropriate action or increase the timeout value
Level: 1

Type: ERROR

Impact: Deployment

OAB-112176: Process %s is in the invalid state %s for the destroy operation.

Cause: Specified process is currently not in PoweredOff state. It might have been updated using target specific manager

Action: Delete the assembly instance and deploy again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112177: No process plan found with id %s

Cause: Internal Error

Action: Contact customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112178: Error occurred while setting the state %s to the appliance %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112179: Error occurred while setting the state %s to the appliance instance %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112180: Error occurred while setting the state %s to the assembly instance %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112181: Error occurred while cloning the appliance %s

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112182: Error occurred while cloning the appliance instance %s

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112183: Error occurred while cloning the assembly instance %s

Cause: Internal Error

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112184: Removing assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112185: Successfully removed assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112186: Removing appliance instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112187: Successfully removed appliance instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112188: Cannot find the registered assembly for the assembly instance %s

Cause: Supplied assembly instance is invalid

Action: Supply a valid assembly instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112189: Cannot find the registered assembly for the appliance instance %s

Cause: Supplied appliance instance is invalid

Action: Supply a valid appliance instance
Level: 1

Type: ERROR

Impact: Deployment

OAB-112190: Assembly instance %s - Staged

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112191: Assembly instance %s - Prepared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112192: Assembly instance %s - Deployed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112193: Assembly instance %s - Stopped

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112194: Assembly instance %s - Unprepared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112195: Assembly instance %s - Undeployed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112196: Assembly instance %s - Suspended

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112197: Assembly instance %s - Failed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112198: Assembly instance %s - Staging

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112199: Assembly instance %s - Preparing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112200: Assembly instance %s - Starting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112201: The assembly path is invalid: %s

Cause: A path representing an assembly element does not exist in the assembly metadata.

Action: Specify a valid path.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112202: The assembly metadata envelope argument is not set.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112203: The assembly metadata envelope has no content

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112204: The content in the assembly metadata envelope has an unknown type: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112205: The assembly metadata envelope contains a virtual system that has no id.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112206: There is no content in the assembly metadata associated with the specified path: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112207: There assembly metadata element %s has no property named %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112208: The property key is not set.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112209: The assembly metadata contains an unknown resource type: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112210: The value %s cannot be converted to %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112211: The property type was not specified

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112212: Value %s is not of type %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112213: The requested value is not of type %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112214: The instance number %d does not exist for %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112215: The property type %s is not a supported type.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112216: Cannot find appliance for the virtual system identifier %s

Cause: Contact Oracle customer support

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-112217: The appliance path is invalid: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112218: The appliance property %s for appliance %s is invalid

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112219: Min for path %s cannot be set to a value smaller than %d. The plan value is %d.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112220: Max for path %s cannot be set to a value larger than %d. The plan value is %d.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112221: The instance count for path %s cannot be set to a value smaller than %d. The plan value is %d.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112222: The instance count for path %s cannot be set to a value larger than %d. The plan value is %d.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112223: OVA was not created by OVAB

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112224: The network property %s for appliance %s must be set when usedhcp is false.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112225: Could not validate the network properties for appliance %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112226: Plan has overrides for unused network definitions: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112227: Error occurred while validating virtual interface definitions: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112228: The name for the virtual interface on eth%d with index %d is not set for %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112229: The ip address for the virtual interface on eth%d with index %d is not set for %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112230: The required property %s for appliance path %s is unset.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112231: The property %s for appliance path %s is not a legal address string: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112232: The property %s for appliance path %s has a value that is not a legal address string: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112233: The property %s for appliance path %s is not allowed to have spaces: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112234: The size for the volume named %s is invalid: %d

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112235: The property %s for appliance path %s is not a legal hostname: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112236: The network %s requires a network name to be set with the plan property %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112237: The network %s must be bound to an existing network by setting either %s or %s in the deployment plan

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112238: The property %s for appliance %s is not a legal netmask: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112239: The property %s for appliance %s (%s) has a network prefix which does not match gateway (%s) or netmask (%s)

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112240: The assembly has an unsupported version, %s. The supported version is %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112241: Inconsistent target platform values among the assembly appliances and deployment plan.

Cause: The deployment plan is not compatible with the assembly archive.

Action: Provide a compatible plan.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112242: You must set either %s or %s for appliance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112243: You must set the property %s for appliance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112244: Error occurred during validation of appliance %s: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112245: Platform is not defined in the deployment plan

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112246: Supported platforms not declared in the OVF metadata of the assembly

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112247: Platform %s declared in the plan is not supported by the assembly. Supported platforms are %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112401: Cannot find assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112402: Cannot find assembly archive {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112403: Assembly archive {0} already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112404: Failed to remove assembly archive {0} after import error.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112405: Failed to import assembly archive {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112406: {0} assembly archive is currently being imported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112407: Failed to read deployment plan file {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112408: {0} deployment plan already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112409: Assembly {0} already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112410: Failed to create assembly folder {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112411: Failed to remove assembly folder {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112412: Failed to cleanup cache for assembly {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112413: Failed to create deployment plan folder {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112414: Failed to remove deployment plan folder {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112415: Cannot find OVF file {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112416: Cannot find deployment plan {0} of assembly {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112417: Failed to read OVF descriptor from file {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112418: Assembly archive file contains no OVF descriptor.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112419: Failed to serialize deployment plan {0} of assembly {1}. Error: {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112420: Cannot add to assembly {0} archive with version {1}, the next expected version is {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112421: Cannot cleanup temporary resources files of assembly archive {0}. Failed to remove {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112422: Cannot remove resources of assembly archive {0}. Failed to move {1} to {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112423: Cannot override resources of assembly archive {0}. Failed to move {1} to {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112424: Cannot restore resources of assembly archive {0}. Failed to remove {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112425: Cannot restore resources of assembly archive {0}. Failed to move {1} to {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112426: Cannot remove files of assembly archive {0}. Failed to remove {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112427: Cannot add resources for assembly archive {0}. Failed to replace overridden file {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112428: Cannot add resources for assembly archive {0}. Failed to add new file {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112429: Failed to create temporary folder {0} for resources of assembly archive {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112430: Failed to create a zip file with resources of assembly archive {0}. Error: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112431: Cannot store resources of assembly archive {0}. Failed to create folder {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112432: Cannot add assembly archive {0}. Failed to create folder {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112433: Interrupted while executing script {0} of assembly archive {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112434: Failed to execute script {0} of assembly archive {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112435: Not authorized to remove scripts.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112436: Not authorized to add scripts.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112437: Failed to import deployment plan {0} for assembly {1}. Error: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112438: Invalid assembly archive name "{0}". It contains special file system characters or is over {1} characters long.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112439: Invalid deployment plan name "{0}". It contains special file system characters or is over {1} characters long.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112440: Failed to close file {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112441: Not enough space on disk

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112442: Cannot remove assembly {0} because it is currently in use.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112443: Cannot remove assembly archive {0} because it is currently in use.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112603: Assembly does not exist at path: {0}

Cause: An assembly file specified does not exist.

Action: Please specify an existing assembly archive file.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112604: File specified by -fileName does not end in .ova: {0}

Cause: An assembly file specified does not end in .ova format.

Action: Please specify an assembly archive file ending in .ova format.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112787: Authentication required. Please provide valid credentials and ensure you are specifying a secure connection with the -connectionName parameter.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112788: Authorization required. Please provide valid credentials and ensure you are specifying a secure connection with the -connectionName parameter. Also ensure that you are authorized to access the resource.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112789: The deployer web service could not be found at : {0} . Please ensure the web service is deployed and started

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112801: No Action parameter in HTTP request query string

Cause: No Action parameter in HTTP request query string

Action: Provide a valid Action parameter in HTTP request query string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112802: Invalid Action %s

Cause: Requested Action is invalid.

Action: See WebService API documentation for list of valid actions.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112803: Invalid Action '%s' for HTTP GET request

Cause: Invalid Action for the HTTP GET request

Action: Provide a valid Action parameter in HTTP GET request query string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112804: Invalid Action %s for HTTP POST request

Cause: Invalid Action for the HTTP POST request

Action: Provide a valid Action parameter in HTTP POST request query string
Level: 1

Type: ERROR

Impact: Deployment

OAB-112805: Invalid HTTP method %s

Cause: HTTP method in request is not allowed

Action: Provide a valid HTTP method in request
Level: 1

Type: ERROR

Impact: Deployment

OAB-112806: Required parameter '%s' not provided for the action '%s'

Cause: Required parameter not provided for the specified action

Action: Provide the required parameter for the specified action
Level: 1

Type: ERROR

Impact: Deployment

OAB-112807: Parameter '%s' does not have a valid boolean value, received '%s'

Cause: Specified parameter does not have a valid boolean value

Action: Valid values for a boolean parameter are : true,false (case ignored)
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112849: Deployer service internal error

Cause: Unexpected error in deployer service

Action: See deployer service log
Level: 1

Type: ERROR

Impact: Deployment

OAB-112850: Deployer WebService initialized

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112851: Admin WebService initialized

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112860: Deployer service returned null object for action '%s'

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112861: Deployer web-service internal error when marshalling the result object. Error is: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112862: Admin service returned null object for action '%s'

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112870: User error. Error is: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112871: Service internal error. Error is: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112872: Service unexpected internal error. Error is: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112890: Deployer download service initialized with url %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112891: Added file to the download registry with path %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112892: Removed file from the download registry with path %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112893: Unsupported JVM detected, OVAB Deployer must run on Sun Microsystems JVM

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112900: Parameter '%s' does not have a valid long value, received '%s'

Cause: Specified parameter does not have a valid long value

Action: Please make sure the specified parameter has a valid long value
Level: 1

Type: ERROR

Impact: Deployment

OAB-112901: Parameter event.type does not have a valid value, received '%s'

Cause: Specified parameter does not have a valid value

Action: Valid values for event.type parameter is VM
Level: 1

Type: ERROR

Impact: Deployment

OAB-112901: Configuration for the deployer admin is not set

Cause: The installation of the deployer did not properly set the configuration

Action: Install the deployer with configuration settings
Level: 1

Type: ERROR

Impact: Deployment

OAB-112902: Failed to close a resource. Error: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112902: FileStoreService is not available

Cause: The deployer is installed in a system without a FileStoreService

Action: Ensure that classes for the FileStoreService are installed in the system
Level: 1

Type: ERROR

Impact: Deployment

OAB-112903: Failed to open a resource file %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112903: Target name is not set

Cause: The request did not include a value for the target name

Action: Set the target name when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112904: Parameter '%s' does not have a valid value to be decoded, received '%s'

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112904: Target type is not set

Cause: The request did not include a value for the target type

Action: Set the target type when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112905: Target properties is not set

Cause: The request did not include a value for the target properties

Action: Set the target properties when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112906: Target %s already exists

Cause: A request to CreateTarget specified a target name that already exists

Action: Choose a different target name for the new target
Level: 1

Type: ERROR

Impact: Deployment

OAB-112907: User name is not set

Cause: The request did not include a value for the user name

Action: Set the user name when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112908: User properties is not set

Cause: The request did not include a value for the user properties

Action: Set the user properties when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112909: There is no target named %s

Cause: A non-existent target was specified for an operation.

Action: Use a valid target name when performing the operation.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112910: The OVAB Deployer config MXBean

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112910: User list is not set

Cause: The request did not include a value for the user list

Action: Set the user list when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112911: Set the web server url in the OVAB deployer

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112911: The user %s is not registered for target %s

Cause: The user must be registered for the target in order to perform the operation

Action: Register the user with the target
Level: 1

Type: ERROR

Impact: Deployment

OAB-112912: Retrieve the web server url from OVAB depoyer

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112912: Target information for user %s is not available for target %s

Cause: The is no target information configured for the user on the target

Action: Configure target information for the user
Level: 1

Type: ERROR

Impact: Deployment

OAB-112913: Cannot initialize the Ovab Deployer MBean {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112913: The target type %s is not one of %s

Cause: An invalid target type was specified in the request

Action: Specify a valid target type
Level: 1

Type: ERROR

Impact: Deployment

OAB-112914: Fail to register the Ovab Deployer MBean {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112914: Request for %s did not include all required properties. Required Properties are %s

Cause: The request did not include all required properties

Action: Specify all required properties in the request
Level: 1

Type: ERROR

Impact: Deployment

OAB-112915: Fail to unregister the Ovab Deployer MBean {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112915: Invalid value for the property %s: %s

Cause: The value for the specified property must be a numeric value

Action: Specify a numeric value
Level: 1

Type: ERROR

Impact: Deployment

OAB-112917: Invalid or unspecified assembly name(s)

Cause: The request did not include a value for the assembly name or names

Action: Set the assembly name or names when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112918: Assembly list is not set

Cause: The request did not include a value for the assembly list

Action: Set the user list when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-112921: Access Denied: User %s unable to access %s

Cause: The user does not have access to the resource

Action: Grant access to the user for the resource
Level: 1

Type: ERROR

Impact: Deployment

OAB-112922: Target %s is in use.

Cause: The operation against the target configuration cannot be performed because the target is in use.

Action: Undeploy any assembly instances for the target and unregister any assemblies registered for the target.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112923: Access Denied: user %s does not have access to this operation.

Cause: The user is not allowed to perform this operation

Action: Connect with a user identity having the proper privileges.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112924: There is no appliance with id %s

Cause: The request indicated an appliance id that does not exist

Action: Specify a valid appliance id.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112925: Request for %s included invalid properties: %s. Valid properties are %s.

Cause: The request included invalid properties

Action: Specify only valid properties in the request
Level: 1

Type: ERROR

Impact: Deployment

OAB-112926: Deployer not initialized

Cause: The deployer subsystem is not yet initialized

Action: Check deployer log for initialization failures
Level: 1

Type: ERROR

Impact: Deployment

OAB-112927: This is an ExaLogic OVAB Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112928: This is a generic OVAB Deployer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112929: Failed to initialize ExaLogic connection configuration: %s

Cause: An error occurred while reading the ExaLogic configuration

Action: See underlying exception to determine the reason for failure.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112930: No such target: %s

Cause: The target specified does not exist

Action: Specify a valid target
Level: 1

Type: ERROR

Impact: Deployment

OAB-112931: Reading properties from %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112932: No properties file at %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-112933: Configuration is not initialized

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-112934: Operation not allowed for ExaLogic: %s. Target configuration for Exalogic is performed at installation time.

Cause: On Exalogic systems, the target configuration is defined at installation time and may not be changed.

Action: None. Dynamic configuration of targets is not necessary on Exalogic systems.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112935: Dynamic creation of ExaLogic targets is not allowed.

Cause: An attempt was made to dynamically create an ExaLogic target

Action: None. Exalogic targets are defined at install time.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112936: OVAB Directory is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112937: OVAB Assembly Directory is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112938: OVAB State Directory is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112939: OVAB Configuration Directory is %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-112940: A failure occurred while attempting to lock a resource

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112941: %s is not set in the configuration.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112942: Version file does not exist at %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112943: Version file at %s is unreadable.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112944: User %s already exists for the target %s

Cause: The specified user already exists for the specified target

Action: Use another user name
Level: 1

Type: ERROR

Impact: Deployment

OAB-112945: Users %s does not exist in the target %s

Cause: The specified users does not exist in the specified target

Action: Fix the users list and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-112946: Invalid VMM Version: %s. Supported version(s): %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-112947: User properties not allowed for target %s which is type %s

Cause: The target specified does not allow user properties.

Action: Do not specify user properties when adding user to target
Level: 1

Type: ERROR

Impact: Deployment

OAB-112948: Storage targets %s are invalid.

Cause: The specified storage targets does not exist in the system

Action: Specify a valid storage target or configure the specified storage targets
Level: 1

Type: ERROR

Impact: Deployment

OAB-112949: Storage target %s is in use by the targets %s. It cannot be deleted

Cause: Specified target is in use.

Action: Perform this operation when it is not in use.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112950: Specified target %s cannot be set as a default target because it is not a deployment target.

Cause: Specified target is not a deployment target and cannot be used as a default deployment target.

Action: Specify a deployment target to be used by default instead.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112951: Cannot connect to the target %s using specified connection properties.

Cause: Specified target connection properties are invalid, the target is down, or secure connection cannot be established because of deployer or target SSL configuration.

Action: Make sure the target connection properties are valid, the target is running and that deployer and target SSL configurations would allow for secure connection.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112952: OVAB Deployer app is not yet fully initialized.

Cause: The ovab.directory required to fully initialize the deployer app is not yet set.

Action: Please set ovab.directory through OVAB deployer MBean.
Level: 1

Type: ERROR

Impact: Deployment

OAB-112953: Value of %s is too small: %s

Cause: The property value was set to 0 or a negative number

Action: Please set property to value greater than 0
Level: 1

Type: ERROR

Impact: Deployment

OAB-113001: Request Handler {0} - registered

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113002: Request Handler {0} - unregistered

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113003: Request {0} is cancelled

Cause: Either user cancelled the specified request or it has been cancelled due to an error occurred

Action: See log files for more details
Level: 1

Type: ERROR

Impact: Deployment

OAB-113004: Request {0} is cancelled due to the error: {1}

Cause: See the error specified in the message

Action: Check the log files and reinitiate the request if necessary
Level: 1

Type: ERROR

Impact: Deployment

OAB-113005: Cancelling the request due to repartitioning

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-113101: Assembly name is not set

Cause: An operation requiring the assembly name was invoked without specifying the assembly name

Action: Specify the assembly name when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113102: Assembly archive source is not set

Cause: An operation requiring the assembly archive source was invoked without specifying the assembly source

Action: Provide the assembly source when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113103: Assembly deployer storage not initialized

Cause: A deployer operation was invoked before the system was initialized

Action: Ensure the system is initialized
Level: 1

Type: ERROR

Impact: Deployment

OAB-113104: Assembly version is not set

Cause: An operation requiring the assembly version was invoked without specifying the assembly version

Action: Specify the assembly version when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113105: Assembly description is not set

Cause: An operation requiring the assembly description was invoked without specifying the assembly description

Action: Specify the assembly description when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113106: Assembly name is not set with version

Cause: You must set the assembly name when the assembly version is specified.

Action: Specify name and version, name alone or neither name nor version, but do not specify version alone.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113107: No resources given in request

Cause: The request requires one or more resource identifiers

Action: Specify a resource identifier in the request
Level: 1

Type: ERROR

Impact: Deployment

OAB-113108: No tags given in request

Cause: The request requires one or more tag settings

Action: Specify a tag setting in the request
Level: 1

Type: ERROR

Impact: Deployment

OAB-113109: No resource given in request

Cause: The request requires a resource id

Action: Specify a resource identifier in the request
Level: 1

Type: ERROR

Impact: Deployment

OAB-113110: One or more tags are missing values

Cause: A tag must have a name and value

Action: Specify values for all tags
Level: 1

Type: ERROR

Impact: Deployment

OAB-113111: Unable to connect to target %s.

Cause: The deployer was not able to connect to the target.

Action: Ensure target configuration is valid and the target is accessable from the deployer.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113112: Assembly instance %s does not exist.

Cause: A request was made for an assembly instance that does not exist

Action: Specify a valid assembly instance id for this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113113: The configuration for target %s is not valid.

Cause: An error occurred while trying to interact with the target due to invalid configuration settings

Action: Review the target configuration and ensure it is consistent with the target setup
Level: 1

Type: ERROR

Impact: Deployment

OAB-113114: Plan name is not set

Cause: An operation requiring the plan name was invoked without specifying the plan name

Action: Specify the plan name when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113115: Request for upload of assembly archive %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113116: Request for upload of assembly resource %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113117: Request for upload of deployment plan for assembly %s with name %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113118: Request to add users %s to assembly %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113119: Request to remove users %s to assembly %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113120: Request to describe users for assembly %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113121: Request for download of assembly archive %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113122: Request for download of assembly resource %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113123: Request for delete of assembly resource %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113124: Request for download of deployment plan %s for assembly %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113125: Request for delete of deployment plan %s for assembly %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113126: Request for download of metadata for assembly %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113127: Request for update of assembly %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113128: Request for delete of assembly %s version(s) %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113129: Request for registration of assembly %s version %s to target %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113130: Request for unregistration of assembly %s version %s to target %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113131: Request to create instance of assembly %s version %s to target %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113132: Request to delete assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113133: Request to deploy assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113134: Request to undeploy assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113135: Request to stop assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113136: Request to start assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113137: Request to hibernate assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113138: Request to resume assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113139: Request to restart assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113140: Request to redeploy assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113141: Request to describe assembly archive(s) %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113142: Request to describe registrations for assembly %s version %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113143: Request to describe assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113144: Request to downloadDeploymentPlan for assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113145: Request to describe appliance instances with deployments=%s, appliances=%s, ververs=%s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113146: Request to describe requests with ids %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113147: Request to delete requests with ids %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113148: Request to delete failed appliance instances with appliance id %s and instance ids %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113149: Request to describe scaling groups %s for appliance instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113150: Request to scale appliance %s to %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113151: Request to describe target(s) %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113152: Request to create tags %s on %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113153: Request to delete tags %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113154: Request to describe tags for resource %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113155: Request to describe vNets %s for target %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113156: Request to describe deployer

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113157: Request to validate assembly instance resources for %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113158: Request to describe resources with tags %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113159: Request to describe log events

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113160: Request to delete log events

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113161: Request to describe vserver metrics

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113162: Assembly archive may not contains spaces

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113163: Invalid target type %s

Cause: Deployment target is expected for this operation while storage target was specified.

Action: Specify a valid deployment target.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113164: Assembly archive file path is not set

Cause: The assembly archive file path was specified when invoking this operation

Action: Provide the assembly file path when invoking this operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-113165: There is no appliance with id %s

Cause: The request indicated an appliance id that does not exist

Action: Specify a valid appliance id.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113166: Invalid appliance id: %s

Cause: The request indicated an invalid appliance id

Action: Specify a valid appliance id.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113167: There is no appliance instance with id %s

Cause: The request indicated an appliance instance id that does not exist

Action: Specify a valid appliance instance id.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113168: Invalid appliance instance id: %s

Cause: The request indicated an invalid appliance instance id

Action: Specify a valid appliance instance id.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113373: Insufficient freespace in assembly store.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113409: Invalid deployer response returned.

Cause: An invalid response was returned by the deployer.

Action: Please check the deployer log for additional details.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113446: Unable to connect to deployer {0}

Cause: The command line abctl was unable to connect to the address specified.

Action: Please ensure the address is reachable and that the deployer is active.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113547: Assembly archive already exists at: {0}

Cause: An assembly archive with the same name already exists at the location specified.

Action: Please choose a different name and/or location to download the assembly archive to using the 'fileName' parameter.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113552: Value specified for pollTime parameter is not an integer value: {0}

Cause: The value specified for pollTime is not an integer value.

Action: Please specify a valid integer value for 'pollTime'
Level: 1

Type: ERROR

Impact: Deployment

OAB-113568: Connection [ {0} ] does not exist.

Cause: A connection name that does not exist was specified.

Action: Specify a connection name that does exist, or create the specified connection.
Level: 1

Type: ERROR

Impact: Deployment

OAB-113701: Error occurred while looking up vserver %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113702: Error occurred in running instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113703: Error occurred while starting instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113704: Error occurred while stopping instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113705: Error occurred while destroying instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113706: Invalid vserver state. VServer %s is in state %s but it is expected to be in %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113707: Failed to open IaaS client session to %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113708: Error occurred when retrieving all vserver templates. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113709: Error occurred when retrieving the vserver template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113710: Failed to close IaaS client session to %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113711: Status of vserver %s has changed from %s to %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113712: There are %s unprocessed events in queue at the time of executor shutdown

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-113713: Exception occurred while disconnecting from State Change Thread Pool. Error is %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-113714: Exception occurred in IaaS state watcher thread. Error is: %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-113715: VServer %s Current state = %s; New state = %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113716: IaaS state watcher thread is Starting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113717: IaaS state watcher thread is Interrupted

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113718: IaaS state watcher thread is Exiting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-113719: Failed to initialize HttpDownloadService: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113720: Error occurred when deleting the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113721: Importing of the template %s timed out after %s seconds.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113722: Error occurred when importing the template %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113723: Error occurred while sending the appliance instance api messages %s to the process %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113724: Error occurred while receiving the appliance instance api message %s from the process %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113725: Receive message for the key %s on the appliance instance %s timed out after %s seconds.

Cause: Operation timedout. Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113726: Failed to retrieve instance-id of newly created instance %s from process.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113727: Error occurred with running new instance %s from process. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113728: Error occurred starting instance %s from process. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113729: Could not find vserver from process %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113730: Could not find network %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113731: Could not start resource pool service for %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113732: Error occurred shutting down resource pool services

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113733: Start operation by IaaS account %s on the process %s for vserver name - %s vserver UUID - %s timedout after %s seconds

Cause: Operation timedout. Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113734: Error occurred while waiting for the status on the process %s with vserver %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113735: Operation on vserver for process %s failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113736: Could not obtain an access key for the key manager at %s for cloud %s for user %s. Error is %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113737: Could not obtain a client binding for the IaaS at %s for cloud %s. Error is %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113738: IaaS URL not valid. Error is %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113739: Failed to create shared volumes %s. Timedout after %s seconds

Cause: Operation timedout. Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113740: Error occurred while creating shared volumes %s. Error is %s

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113741: Failed to create shared volumes %s

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113742: Create operation on vNet %s timedout after %s seconds

Cause: Operation timedout. Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113743: Failed to create vNet %s

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113744: Error occurred while waiting for the status of the create operation for vNet %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113745: Failed to delete shared volumes %s. Timedout after %s seconds

Cause: Operation timedout. Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113746: Error occurred while deleting shared volumes %s. Error is %s

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113747: Failed to delete shared volumes %s

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113748: There are no vserver types which satisfy the requirements for instance %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113749: Could not stop target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113750: Create operation on distribution group %s timedout after %s seconds

Cause: Operation timedout. Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113751: Failed to create distribution group %s

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113752: Error occurred while waiting for the status of the create operation for distribution group %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-113753: Delete operation on distribution group %s timedout after %s seconds.

Cause: Check the target logs for the root cause

Action: Check the target logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-113754: Error occurred while waiting for the status of the delete operation for distribution group %s. Error is %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114201: VM template {0} already exists in resource pool {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114202: VM template {0} could not be found in resource pool {1} after it got successfully imported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114203: VM {0} already exists in resource pool {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114204: Unknown folder is included with assembly resources: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114208: Exception occurred in VM state watcher thread for resource pool {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114209: VM state listener failed to handle state change notification for VM {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114210: Error occurred while loading the adapters for the VMM targets. Error is: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114211: Exception occured while disconnecting from VirtualMachineManager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114212: Could not locate VMM Adapter for type {0} api version {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114601: Cannot find server pool {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114602: Cannot find the pool repository {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114603: Cannot find a repository shared by pool servers.

Cause: No single repository was found that is presented to all the servers in the pool {0}

Action: Configure OVM environment so that at least one repository is presented to all the servers in the pool {0}
Level: 1

Type: ERROR

Impact: Deployment

OAB-114604: Cannot find worker server for repository {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114605: Failed to import assembly archive {0} from URL {1}.

Cause: Download of assembly to the repository failed, possibly due to the OVS host connection isues.

Action: Make sure OVS hosts have access to the OVA file at the specified URL and try again.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114606: Timed out after {0} seconds while importing assembly archive {1} from URL {2}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114607: Failed to remove assembly and templates created during failed attempt to import {0} assembly archive.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114608: Cannot delete virtual disk {0} because it is still in use by a VM.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114609: Cannot find VirtualDisk {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114610: Cannot find EthernetNetwork {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114611: Cannot find VM template {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114612: Cannot find VNIC for attaching network to VM.

Cause: No more VNICs are currently available.

Action: Generate more VNICs using OVM Vnic Manager.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114613: Cannot find VNIC for this MAC address: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114614: VNIC with specified MAC {0} is currently in use.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114615: Cannot find another server for VM {0} in the pool {1}. Minimum {2} servers are required for this VM anti-affinity group and only {3} servers are used.

Cause: Not enough servers are available in the pool to satisfy VM anti-affinity group minimum servers requirement.

Action: Increase the number of servers in the pool {0}, deploy to a different pool or lower minimum servers requirement of VM the anti-affinity group and try again.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114616: Request to receive messages from VM {0} timed out after {1} seconds.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114617: Cannot find {0} object with ID {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114618: Cannot find a server in the pool {0} that can host VM {1}.

Cause: Pool {0} servers don't have enough resources to host VM {1}.

Action: Increase the number of servers in the pool or amount of resources available to the pool servers and try again.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114619: Timed out after {0} seconds while creating templates from imported assembly archive {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114620: Failed to unassign VM from server after failed attempt to start VM {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114621: Timed out after {0} seconds while starting VM {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114622: Timed out after {0} seconds while creating VM {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114623: Failed to delete created VM {0} after failed attempt to configure it.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114624: Failed to connect to OVM manager at {0}.

Cause: OVM manager is down or its version is not supported by the client.

Action: Verify that OVM manager is running at specified URL and has the compatible version.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114625: Failed to login to OVM manager at {0}.

Cause: Access to OVM manager was denied.

Action: Configure correct user name and password and try again.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114626: Cannot delete virtual disk {0} because it does not exist.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114627: Failed to delete virtual disk {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114628: Failed to delete virtual machine template {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114629: Error while trying to refresh repository after failed import of assembly archive {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114630: Failed to import virtual cdrom {0} from URL {1}.

Cause: Download of virtual cdrom to the repository failed, possibly due to the OVS host connection isues.

Action: Make sure OVS hosts have access to the virtual disk file at the specified URL and try again.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114631: Timed out after {0} seconds while importing virtual cdrom from URL {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114632: Failed to delete virtual cdrom {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114633: Timed out after {0} seconds while deleting virtual cdrom {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114634: No VirtualMachine found from OVM based on vm id {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114635: Failed to logout from OVM manager at {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114636: Failed to clear messages received from VM {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114637: Failed to clear message received from VM. Error: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114638: Error while receiving messages from VMs

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114639: SSL handshake failed while trying to establish secure connection to OVM manager at {0}.

Cause: The client was not able to establish secure connection.

Action: Check deployer and OVM manager SSL configuration. Make sure OVM manager certificate is trusted by deployer.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114640: Cannot find storage element {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114801: Assembly instance %s - Stopping

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114802: Assembly instance %s - Unpreparing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114803: Assembly instance %s - Unstaging

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114804: Assembly instance %s - Suspending

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114805: Assembly instance %s - Resuming

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114806: Appliance instance %s - Staged

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114807: Appliance instance %s - Prepared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114808: Appliance instance %s - Deployed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114809: Appliance instance %s - Stopped

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114810: Appliance instance %s - Unprepared

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114811: Appliance instance %s - Undeployed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114812: Appliance instance %s - Suspended

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114813: Appliance instance %s - Failed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114814: Appliance instance %s - Staging

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114815: Appliance instance %s - Preparing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114816: Appliance instance %s - Starting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114817: Appliance instance %s - Stopping

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114818: Appliance instance %s - Unpreparing

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114819: Appliance instance %s - Unstaging

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114820: Appliance instance %s - Suspending

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114821: Appliance instance %s - Resuming

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-114822: Invalid operation attempted. Cannot perform delete failed appliance instances operation since the assembly instance {0} is currently deployed

Cause: The corresponding deployment is not running

Action: This operation is only meant for deleting the failed instances resulted by the scale operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-114823: Invalid instance identifiers %S

Cause: The specified instance identifiers are not failed instances

Action: This operation is only meant for deleting the failed instances resulted by the scale operation
Level: 1

Type: ERROR

Impact: Deployment

OAB-114824: Assembly instance %s is being operated by another process

Cause: Another process is operating the supplied assembly instance

Action: Wait for the other process to complete
Level: 1

Type: ERROR

Impact: Deployment

OAB-114825: Some or all versions of %s of assembly archive %s are being operated by another process

Cause: Another process is operating the supplied assembly instance

Action: Wait for the other process to complete
Level: 1

Type: ERROR

Impact: Deployment

OAB-114826: Assembly archive %s:%s is being operated by another process

Cause: Another process is operating the supplied assembly instance

Action: Wait for the other process to complete
Level: 1

Type: ERROR

Impact: Deployment

OAB-114827: Assembly archive %s is being operated by another process

Cause: Another process is operating the supplied assembly instance

Action: Wait for the other process to complete
Level: 1

Type: ERROR

Impact: Deployment

OAB-114828: Error occurred while uploading assembly resources. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114829: Error occurred while uploading plan %s for the assembly %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114830: Appliance %s does not define %s property

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114831: Invalid network properties. Errors are %s

Cause: Network configured for the specified appliances are static but does not defined required properties for the static network or specified properties are invalid

Action: Fix the errors specified in the error message
Level: 1

Type: ERROR

Impact: Deployment

OAB-114832: Appliance %s has invalid address %s for the property %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114833: Assembly instance %s does not contain deployment requirement instances after restoration

Cause: Some or all appliance instances of the assembly instance in the corresponding target environment are either managed by the external tools or could not be recovered

Action: Delete the assembly instance and create it again
Level: 1

Type: ERROR

Impact: Deployment

OAB-114834: Restoration of the assembly instance %s failed. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114835: Plan validation failed. Errors are %s

Cause: Check the errors in the messsage for the root causes.

Action: Fix the errors specified in the error message
Level: 1

Type: ERROR

Impact: Deployment

OAB-114836: Target %s does not have servers required for the appliance %s. Appliance require %s servers but the target has %s servers

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114837: Anti-affinity validation failed. Errors are %s

Cause: Check the errors in the messsage for the root causes.

Action: Fix the errors specified in the error message
Level: 1

Type: ERROR

Impact: Deployment

OAB-114838: Invalid assembly archive %s:%s

Cause: Either it is being uploaded or it has been removed due to other operation

Action: Check the status of the supplied assembly archive
Level: 1

Type: ERROR

Impact: Deployment

OAB-114839: Deployer must always be executed by the same user '%s', while the current user is '%s'

Cause: WebLogic and its applications are now executed by a different OS user, which can cause problems with Deployer file based store and is not allowed.

Action: Restart WebLogic as the original user, or reinstall Deployer.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114840: Failed to load deployer environment properties file: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114841: Failed to update user in deployer environment properties file: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114842: Plan name must be specified

Cause: Supplied plan name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: ERROR

Impact: Deployment

OAB-114843: Plan stream must be specified

Cause: Supplied plan stream is null

Action: Supply non-null stream
Level: 1

Type: ERROR

Impact: Deployment

OAB-114844: Resources stream must be specified

Cause: Supplied resources stream is null

Action: Supply non-null stream
Level: 1

Type: ERROR

Impact: Deployment

OAB-114845: Error occurred while uploading plan. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114846: Error occurred while downloading resources for the assembly %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114847: Error occurred while writing late bingings of the instance %s to the file script params file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114848: Invalid update resources request for the assembly archive %s:%s with append option

Cause: No resources exist for the specified assembly archive

Action: Run the request without append option
Level: 1

Type: ERROR

Impact: Deployment

OAB-114849: Invalid plan name %s. Assembly archive %s:%s does not have the specified plan

Cause: Plan does not exist in the specified assembly archive

Action: Try with an existing plan or upload a plan
Level: 1

Type: ERROR

Impact: Deployment

OAB-114850: Cannot delete the deployment plan %s for the assembly archive %s:%s. It's currently in use.

Cause: The specified deployment plan has assembly instances

Action: Delete the deployments and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-114851: Cannot delete resources for the assembly archive %s:%s. It's currently in use.

Cause: The specified assembly has assembly instances

Action: Delete the deployments and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-114852: Delete scripts access not allowed on the assembly %s:%s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114853: Invalid resources %s specified for the assembly %s:%s

Cause: The specified resources does not exist for the specified assembly

Action: Check the supplied resource set and try with a valid resource set
Level: 1

Type: ERROR

Impact: Deployment

OAB-114854: Invalid delete resources request for the assembly archive %s:%s

Cause: No resources exist for the specified assembly archive

Action: Verify assembly resources with describeAssemblyResources command
Level: 1

Type: ERROR

Impact: Deployment

OAB-114855: Error occurred while creating ISO shares for the assembly %s:%s in the storage target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114856: No resources exist for the assembly archive %s:%s

Cause: No resources exist for the specified assembly archive

Action: Run the request without append option
Level: 1

Type: ERROR

Impact: Deployment

OAB-114857: Error occurred while creating ISO shares for the assembly instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114858: Error occurred while deleting ISO shares for the assembly instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114859: Cannot find cdrom for plan file-refs for the appliance instance %s

Cause: Error might have occurred while creating corresponding cdrom

Action: Contact oracle customer support with the appropriate log files
Level: 1

Type: ERROR

Impact: Deployment

OAB-114860: Could not create temporary directory %s

Cause: File system might be read-only or user does not have write-permissions or insufficient enough disk resources

Action: Check the cause and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-114861: Error occurred while creating ISO file for the appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114862: ISO file creation for the appliance instance %s failed with exit code %s

Cause: Check the log file for the root cause

Action: Check the log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-114863: Error occurred while opening the session to the storage target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114864: Use storage target argument must be specified

Cause: The supplied assembly contains shared ISO files and use storage target was not specified

Action: Supply non-null, non-empty and valid storage target
Level: 1

Type: ERROR

Impact: Deployment

OAB-114865: Error occurred while performing cleanup on the registration %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114866: Cannot use storage target %s with the deployment target %s

Cause: The supplied storage target is not configured in the allowed storage targets list for the specified deployment target

Action: Provide a valid and configured allowed storage target for the specified deployment target
Level: 1

Type: ERROR

Impact: Deployment

OAB-114867: Cannot find assembly deployment plan %s for the assembly %s with version %s

Cause: No assembly deployment plan exists for the specified assembly name, plan name and version

Action: Provide valid assembly name, plan name and version
Level: 1

Type: ERROR

Impact: Deployment

OAB-114868: Error occurred while restoring the assembly instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114869: Invalid download resources request for the assembly archive %s:%s

Cause: No resources exist for the specified assembly archive

Action: Verify assembly resources with describeAssemblyResources command
Level: 1

Type: ERROR

Impact: Deployment

OAB-114870: Error occurred while adding or deleting the tags to the registration %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114871: Invalid network configuration for the interface %s in the appliance %s

Cause: Network name unspecified

Action: Fix the deployment plan with network name property
Level: 1

Type: ERROR

Impact: Deployment

OAB-114872: Invalid network configuration for the interface %s in the appliance %s

Cause: Network name and network id are unspecified

Action: Fix the deployment plan with network name or network id property
Level: 1

Type: ERROR

Impact: Deployment

OAB-114873: Network with the identifier %s does not exist in the target %s

Cause: Specified network identifier does not exist

Action: Fix the deployment plan with a valid and existing network id
Level: 1

Type: ERROR

Impact: Deployment

OAB-114874: Network with the name %s does not exist in the target %s

Cause: Specified network name does not exist

Action: Fix the deployment plan with a valid and existing network name
Level: 1

Type: ERROR

Impact: Deployment

OAB-114875: Assembly %s:%s has not been uploaded yet.

Cause: Specified assembly is being uploaded to the repository

Action: Wait till upload is complete or specify a different assembly version
Level: 1

Type: ERROR

Impact: Deployment

OAB-114876: Invalid assembly names supplied

Cause: Supplied empty list of assembly names

Action: Specify one or more assembly names
Level: 1

Type: ERROR

Impact: Deployment

OAB-114877: Invalid assembly names supplied. Particularly %s

Cause: Specified assembly names does not exist in the repository

Action: Supply valid assembly names
Level: 1

Type: ERROR

Impact: Deployment

OAB-114878: Error occurred while restoring the assembly instance %s. Error is %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114879: Error occurred while releasing the addresses on the vnet %s. Error is %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114880: Error occurred while releasing the addresses for the instance {0}. Error is {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114881: The value %s cannot be converted to %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114882: The value type was not specified

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114883: Value %s is not of type %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114884: The requested value is not of type %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114885: There is an illegal value type: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114886: Assembly instance {0} does not contain the required appliance instances. Particularly, the instance {1} either went down or has been operated externally

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114887: Assembly instance {0} does not meet the deployment requirement

Cause: One or more instances of the assembly instance in the corresponding target environment are either managed by the external tools or would have gone down

Action: Delete the assembly instance and create it again
Level: 1

Type: WARNING

Impact: Deployment

OAB-114888: Invalid metric service type: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114889: Found multiple action handling services of type: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114890: Cannot find action handling service of type: {0}

Cause: ActionHandler of type {0} is not found in Deployer classpath.

Action: Make sure ActionHandler of type {0} is in the classpath and restart the deployer.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114891: Required parameter {0} was not specified for action {1}

Cause: Required parameter {0} was not specified for action {1}.

Action: Specify all the parameters required by the rule action {1}.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114892: Specified parameter {0} value is not a number

Cause: Wrong non-numeric parameter {0} value was specified for action {1}.

Action: Correct the {0} parameter value passed to action {1}.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114893: Either parameter {0} or {1} must be specified for action {2}, but not both

Cause: Both {0} and {1} parameters were specified for action {2} while only one can be set.

Action: Update rule definition to specify only {0} or {1} parameter for action {2}.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114894: Either parameter {0} or {1} must be specified for action {2}

Cause: None of the required {0} or {1} parameters were specified for action {2}.

Action: Specify either {0} or {1} parameter in the rule definition invoking action {2}.
Level: 1

Type: ERROR

Impact: Deployment

OAB-114895: Invalid metric context specified with deploymentId {0}, appliancePath {1} and instanceId {2}

Cause: Invalid metric context specified

Action: Please provide the either deploymentId, appliancePath or instanceId in the metric context
Level: 1

Type: WARNING

Impact: Deployment

OAB-114896: Aggregation has to be specified for appliance metric collection

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114897: Metric item has to be specified in metric reference

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114898: For metric aggregation, the poll range in watch control has to be specified

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114899: Specified value for parameter '{0}' of action {1} is invalid. The following values are expected: {2}

Cause: Invalid parameter value was specified in the rule definition.

Action: Update rule definition and specify correct action parameter.
Level: 1

Type: WARNING

Impact: Deployment

OAB-114900: The poll period has to be specified in watch control

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114901: Invalid appliance instance watch control: aggregation {0}, pollRange {1}

Cause: Invalid appliance instance watch control specified

Action: For appliance instance, both aggregation and pollRange have to be specified.
Level: 1

Type: WARNING

Impact: Deployment

OAB-114902: Invalid appliance instance watch control: aggregation {0}

Cause: Invalid aggregation specified in appliance instance watch control

Action: For appliance instance, only average aggregation is supported.
Level: 1

Type: WARNING

Impact: Deployment

OAB-114903: {0} operation request {1} for the appliance {2} in the assembly instance {3} is cancelled

Cause: The deployer server handling the specified request is either crashed or has been shutdown

Action: Look at the logs for corresponding appliance and perform any cleanup if necessary
Level: 1

Type: WARNING

Impact: Deployment

OAB-114904: Error occurred while cleanuping the cancelled deployment request {0} for the assembly instance {1}. Error is {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114905: Error occurred while cleanuping the cancelled registration request {0} for the assembly archive {1}:{2} on the target {3}. Error is {4}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114906: {0} operation request {1} for the assembly instance {2} is cancelled

Cause: The deployer server handling the specified request is either crashed or has been shutdown

Action: 1. Look at the logs for corresponding assembly instance and perform any cleanup if necessary 2. Delete the specified deployment
Level: 1

Type: WARNING

Impact: Deployment

OAB-114907: {0} operation request {1} for the assembly archive {2}:{3} on the target {4} cancelled

Cause: The deployer server handling the specified request is either crashed or has been shutdown

Action: Look at the logs for corresponding registration and perform any cleanup if necessary
Level: 1

Type: WARNING

Impact: Deployment

OAB-114908: Invalid appliance instance id {0}

Cause: Contact Oracle customer support

Action: No native instance can be found with the specified id
Level: 1

Type: WARNING

Impact: Deployment

OAB-114909: The poll period {0} specified is below the minimally allowed value 5 sec

Cause: The poll period specified in below the minimally allowed value

Action: Please correct the poll period to be above the minimally allowed value
Level: 1

Type: WARNING

Impact: Deployment

OAB-114910: The target {0} does not support platform {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114911: Assembly archive file path must be specified

Cause: Supplied assembly archive file path is null

Action: Supply non-null assembly archive file path
Level: 1

Type: ERROR

Impact: Deployment

OAB-114912: Error occurred while generating snapshot for the assembly instance {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114913: Cannot find disk {0} in the appliance instance {1}

Cause: Disk with the supplied name isn't a valid disk for the supplied appliance instance

Action: Check the specified disk is a valid disk attached to the supplied appliance instance against the ovf descriptor of the assembly and try again with the valid disk name
Level: 1

Type: WARNING

Impact: Deployment

OAB-114914: Cannot find disk {0} in the assembly instance {1}

Cause: Disk with the supplied name isn't a valid disk in the assembly instance

Action: Check the specified disk is a valid disk the ovf descriptor of the assembly and try again with the valid disk name
Level: 1

Type: WARNING

Impact: Deployment

OAB-114915: Invalid disk {0} for the snapshot generation. Its not attached to the appliance instances in the assembly instance {1}

Cause: The disk with the supplied name isn't configured to attach any appliance instance

Action: Check the specified disk is a valid disk the ovf descriptor of the assembly and it is configured to attach to one or more appliances
Level: 1

Type: WARNING

Impact: Deployment

OAB-114916: Invalid snapshot generation request. The appliance instance {0} doesn't have any disks attached

Cause: The supplied applaince instance doesn't have any disks attached

Action: Check the specified appliance instance against the ovf descriptor of the assembly and try again with the valid appliance instance
Level: 1

Type: WARNING

Impact: Deployment

OAB-114917: Cannot generate snapshot to the appliance instance {0}. It has shared disks {1}

Cause: The supplied appliance instance has shared disks. The appliance alone cannot be snapshotted when it has shared disks.

Action: Generate snapshot to the assembly instance when there are shared disks
Level: 1

Type: WARNING

Impact: Deployment

OAB-114918: Invalid snapshot identifier {0}

Cause: The snapshot with the supplied identifier does not exist in the deployer

Action: Use a valid and existing snapshot id for the restoration
Level: 1

Type: WARNING

Impact: Deployment

OAB-114919: Cannot find native appliance instance for the identifier {0}

Cause: Appliance instance identifier is invalid

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-114920: No snapshot disks found in the snapshot {0} for the appliance instance {1}. The appliance instance is new after the snapshot is generated. This appliance instance cannot be restored to the snapshot. Continuing the assembly restoration of rest of the appliance instances.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114921: Error occurred while generating the snapshot

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114922: Error occurred while restoring snapshot {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114923: Snapshot generation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114924: Successfully generated snapshot %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114925: Snapshot restoration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114926: Successfully restored snapshot %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114927: Invalid request type {0}

Cause: Unknown cause

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-114928: Error occurred while restoring the snapshot {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114929: Error occurred while restoring the assembly instance {0} to the original state

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114930: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114931: Insufficient disk resource. Required %s but available %s

Cause: Snapshot generation require the disk size more than the availability in the target

Action: Try snapshot generation when there is sufficient enough disk size available on the target
Level: 1

Type: WARNING

Impact: Deployment

OAB-114932: Invalid snapshot generation request. The assembly instance {0} doesn't have any disks attached

Cause: The supplied assembly instance doesn't have any disks attached

Action: Check the ovf descriptor of the assembly instance
Level: 1

Type: WARNING

Impact: Deployment

OAB-114933: Invalid or unspecified Disk name

Cause: Supplied disk name is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: WARNING

Impact: Deployment

OAB-114934: Snapshot identifier(s) must be specified

Cause: Supplied snapshot identifier is either null or empty string

Action: Supply non-null and non-empty string
Level: 1

Type: WARNING

Impact: Deployment

OAB-114935: Invalid snapshot identifiers {0}

Cause: Snapshots with the specified identifiers does not exist in the system

Action: Specify valid snapshot identifiers
Level: 1

Type: WARNING

Impact: Deployment

OAB-114936: Error occurred while deleting the snapshot %s. Error is %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114937: Invalid metric item: {0}

Cause: Invalid metric item is specified

Action: Specify valid metric item
Level: 1

Type: WARNING

Impact: Deployment

OAB-114938: Invalid network names/ids {0}. These networks are private to the other assembly instances

Cause: Specified networks are private to the other assembly instances

Action: Specify valid public networks
Level: 1

Type: INCIDENT_ERROR

Impact: Deployment

OAB-114939: The received stop-result for the appliance instance %s is %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-114940: Failed to populate NFS share {0}. Error is: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114941: Failed to clone NFS share {0}. Error is: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114942: Failed to list NFS shares of project {0}. Error is: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-114943: Failed to create NFS share {0}. Error is: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-115001: Insufficient %s resource. Required %s but available %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-115002: Target %s does not contain the network %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-115003: Resource validations for the appliance %s against the target %s failed. Errors are %s

Cause: Check the errors in the messsage for the root causes.

Action: Fix the errors specified in the error message
Level: 1

Type: ERROR

Impact: Deployment

OAB-115004: Resource validations for the assembly %s against the target %s failed. Errors are %s

Cause: Check the errors in the messsage for the root causes.

Action: Fix the errors specified in the error message
Level: 1

Type: ERROR

Impact: Deployment

OAB-115005: Resource validations for the appliance instance %s against the target %s failed. Errors are %s

Cause: Check the errors in the messsage for the root causes.

Action: Fix the errors specified in the error message
Level: 1

Type: ERROR

Impact: Deployment

OAB-115006: Ovf file path must be provided

Cause: Did not provide ovf file path

Action: Provide ovf file path and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-115007: Invalid ovf file %s

Cause: Supplied ovf file does not exist

Action: Provide a valid ovf file
Level: 1

Type: ERROR

Impact: Deployment

OAB-115008: Error occurred while parsing the ovf file %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-115009: Deployment plan file path must be provided

Cause: Did not provide deployment plan file path

Action: Provide deployment plan file path and try again
Level: 1

Type: ERROR

Impact: Deployment

OAB-115010: Invalid deployment plan file %s

Cause: Supplied deployment plan file does not exist

Action: Provide a valid deployment plan file
Level: 1

Type: ERROR

Impact: Deployment

OAB-115011: Error occurred while parsing the deployment plan file %s. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-115157: Assembly resources file already exists at: {0}

Cause: An assembly resources file with the same name already exists at the location specified.

Action: Please choose a different name and/or location to download the assembly archive to using the 'fileName' parameter
Level: 1

Type: ERROR

Impact: Deployment

OAB-115261: Assembly name {0} is not valid

Cause: Assembly name specified is not valid

Action: Correct the assembly name so that it begins with an alphabetic character and only contains alphanumeric characters, underscore or hyphen
Level: 1

Type: ERROR

Impact: Deployment

OAB-115262: Request {0} has failed. Error is {1}

Cause: Check the error and the deployer logs to find the root cause

Action: Check the error and the deployer logs and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-115263: Invalid assembly archive - no OVF descriptor present

Cause: Specify a valid assembly archive file

Action: The specified assembly archive does not contain a valid OVF descriptor file
Level: 1

Type: ERROR

Impact: Deployment

OAB-115264: Assembly name {0} is not within length of 4 ~ 40 characters

Cause: Assembly name specified is not within length of 4 ~ 40 characters

Action: Please correct and use the correct length
Level: 1

Type: ERROR

Impact: Deployment

OAB-115432: The platform type {0} is not valid

Cause: Platform type used is not valid

Action: Please correct and use the correct platform type
Level: 1

Type: ERROR

Impact: Deployment

OAB-117036: Element {0} was not found in the catalog.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-117037: Unrecognized JobParameter.ValueType {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-117038: Top level assembly {0} already exists in catalog.

Cause: (See message)

Action: Delete assembly or use -force flag.
Level: 1

Type: ERROR

Impact: User Input

OAB-117040: Bad port number supplied to the {0} parameter: {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-117041: Missing remote address

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-117042: Literal IPv6 address missing '[' and ']': {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: User Input

OAB-117501: Member %s - Joined

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117502: Member %s - Leaving

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117503: Member %s - Left

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117504: Member %s has become primary cluster member

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117505: Could not connect to the ovab cluster

Cause: Check the server log file for possible root cause

Action: Check the server log file and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117506: Error occurred while connecting to the ovab cluster

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117507: Aborting due to unable to connect to the ovab cluster in %s seconds. Error is %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117508: Successfully connected to the ovab cluster %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117509: Could not create cache config for %s

Cause: Ovab application incorrectly packaged

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-117510: Successfully created cache factory %s for the config URI %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117511: Could not create cache %s

Cause: Ovab application incorrectly packaged

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-117512: Successfully created cache %s with the cache service %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117513: Shutdown completed on bootstrap service

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-117601: member path passed in is null

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117602: type is not an INTEGER

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117603: type is not a LONG

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117604: type is not a BOOLEAN

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117605: type is not a PASSWORD

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117606: name passed in is null

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117607: Property name is null

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117608: Duplicate property name %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117609: MemberPlan %s is invalid

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117610: Invalid Type

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117611: Value is not a string

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117612: Value is not an integer

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117613: Value is not a long

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117614: Value is not a boolean

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117615: Value is not a character array

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117616: MemberProperty is not a password

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117617: Error reading password from credential store

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117618: Credential store has been already initialized

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117619: Error updating password in credential store

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117620: Could not get resource: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117621: Error getting schema: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117622: Plan file not found at %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117623: Deployment Plan is not valid

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117624: Error reading plan file: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117625: Error reading plan file: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117626: Error opening Credential Store for %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117627: %s member property value is not valid

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117801: Error occurred while uploading the assembly archive

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117802: Error occurred while downloading the assembly archive

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117803: Error occurred while downloading the assembly metadata

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117804: Error occurred while creating the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117805: Error occurred while deleting the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117806: Error occurred while deleting the deployment plan

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117807: Error occurred while undeploying the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117808: Error occurred while registering the assembly archive

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117809: Error occurred while unregistering the assembly archive

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117810: Error occurred while updating the assembly archive

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117811: Error occurred while describing the assembly instances

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117812: Error occurred while describing the assembly archives

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117813: Error occurred while describing the requests

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117814: Error occurred while starting the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117815: Error occurred while stopping the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117816: Error occurred while downloading the deployment plan

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117817: Error occurred while describing the deployer

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117818: Error occurred while creating the target

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117819: Error occurred while updating the target

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117820: Error occurred while describing the target names

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117821: Error occurred while deleting the target

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117822: Error occurred while setting the default target

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117823: Error occurred while describing the assembly instances

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117824: Error occurred while adding the target user

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117825: Error occurred while describing the target user

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117826: Error occurred while removing the target user

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117827: Error occurred while describing the user targets

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117828: Error occurred while creating the deployer connection

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117829: Error occurred while deleting the deployer connection

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117830: Error occurred while describing the deployer connections

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117831: Error occurred while getting the deployer connection

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117832: Error occurred while getting the default target

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117833: Error occurred while getting the target type

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117834: Error occurred while describing the scaling groups

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117835: Error occurred while initiating the scaling operation

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117836: Error occurred while describing the vnets

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117837: Error occurred while describing the targets

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117838: Error occurred while describing the registrations

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117839: Error occurred while describing the target configurations

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117840: Error occurred while restarting the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117841: Error occurred while redeploying the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117842: Error occurred while deleting the requests

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117843: Error occurred while describing the assembly users

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117844: Error occurred while adding the assembly user

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117845: Error occurred while deleting the assembly user

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117846: Error occurred while creating the tags

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117847: Error occurred while deleting the tags

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117848: Error occurred while deleting the log events

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117849: Error occurred while describing the tags

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117850: Error occurred while describing the resources

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117851: Error occurred while describing the log events

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117852: Error occurred while deleting the failed appliances

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117853: Error occurred while validating the resources

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117854: Error occurred while suspending the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117855: Error occurred while resuming the assembly instance

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117856: Error occurred while uploading the assembly plan

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117857: Error occurred while uploading the assembly resources

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117858: Error occurred while downloading the assembly resources

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117859: Error occurred while describing the assembly resources

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117860: Error occurred while deleting the assembly resources

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117861: Error occurred while pinging the deployer

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117862: Error occurred while waiting for the deployer request completion

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: No action required as deployment operation is in-progress on the deployer server
Level: 1

Type: ERROR

Impact: Deployment

OAB-117863: Error connecting to deployer

Cause: An unexpected exception was thrown when connecting to the deployer.

Action: Review the exception message appended to the error text
Level: 1

Type: ERROR

Impact: Deployment

OAB-117864: Invalid deployer connection. A deployer connection with name {0} already exists

Cause: Specify a non-existing deployer connection name

Action: A connection with the specified name already exists
Level: 1

Type: ERROR

Impact: Deployment

OAB-117865: Invalid deployer connection. The deployer connection {0} does not exist

Cause: Specify a valid deployer connection

Action: The specified deployer connection does not exist
Level: 1

Type: ERROR

Impact: Deployment

OAB-117866: Credential validation failed: Error is {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-117867: FILEREF property does not point to an existing file {0}

Cause: Invalid value for a FILEREF property

Action: Please correct the value of a FILEREF property to point to an existing file
Level: 1

Type: ERROR

Impact: Deployment

OAB-117868: Error occurred while describing the vserver metrics

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117869: You do not have permission to upload assembly with name %s

Cause: Another user is using the name for the assembly being uploaded

Action: Use another name for the assembly
Level: 1

Type: ERROR

Impact: Deployment

OAB-117870: Error occurred while starting metrics polling

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117871: Error occurred while stopping metrics polling

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117872: Error occurred while updating assembly rules

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117873: Error occurred while describing assembly rules

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117874: Error occurred while downloading the rule set

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117875: Error occurred during assembly snapshot creatiion

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117876: Error occurred while deleting snapshots

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117877: Error occurred while describing snapshots

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117878: Error occurred while restoring the assembly from the snapshot

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117879: Error occurred while describing snapshot disks

Cause: An unexpected exception occurred. Look at the underlying error for the root cause.

Action: Look at the underlying error and take appropriate action
Level: 1

Type: ERROR

Impact: Deployment

OAB-117901: Cannot find the vNet %s in the target %s

Cause: The specified vNet does not exist in the specified target

Action: Verify the vNet name specified in the ovf descriptor
Level: 1

Type: ERROR

Impact: Deployment

OAB-117902: Error occurred while attempting to query vserver metrics on the vm %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117903: Error occurred while attempting to query vserver metrics on the vm %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117904: Error occurred while attempting to clone virtual disk %s in the target %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117905: Error occurred while attempting to clone virtual disk %s in the target %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117906: Error occurred while attempting to restore disk %s appliance instance %s. Error is: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117907: Error occurred while attempting to restore disk %s appliance instance %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-117908: Invalid disk clone operation attempted. Disks must be provided

Cause: Supplied disk(s) is null or empty

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-117909: Invalid appliance instance restore operation attempted. Disks must be provided

Cause: Supplied disk(s) is null or empty

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-117910: Invalid restore operation attempted. Invalid or unspecified appliance instance

Cause: Supplied appliance instance is null

Action: Contact Oracle customer support
Level: 1

Type: ERROR

Impact: Deployment

OAB-118001: Could not get resource: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-118002: Error getting schema: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-118003: Error reading rule file: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-118004: Add metric: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118005: Add rule: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118006: Parsed rule set %s for assembly instance %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118007: Inserted metric %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118008: Deleted metric %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118009: Updated metric %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118010: Inserted rule %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118011: Deleted rule %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118012: unused

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118013: Metric handler got unexpected event %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-118014: Rule handler got unexpected event %s

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-118015: Metric %s does not exist. %s will be unavailable until it is defined

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

OAB-118016: Rule %s in rule set %s for assembly instance %s has been triggered. Action %s will be performed

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118017: There is no rule %s in rule set %s for assembly instance %s

Cause: The specified rule does not exist

Action: Specify a valid rule
Level: 1

Type: ERROR

Impact: Deployment

OAB-118019: Rules Engine Debug: %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118020: Restored rule %s

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

OAB-118101: Error extracting disk image from assembly archive.

Cause: (See message)

Action: Ensure the assembly archive is not corrupt.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118102: Assembly archive does not appear to be a valid OVA.

Cause: Could not read assembly archive as tar format.

Action: Ensure the assembly archive is not corrupt.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118103: The specified S3 bucket does not belong to the configured user.

Cause: The specified bucket belongs to another user.

Action: Specify a different S3 bucket in the target configuration.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118104: Failed to parse base image index from assembly archive.

Cause: The base image index is not a valid JSON object.

Action: Contact Oracle support.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118105: Appliance %s does not have an IP address property defined for interface %s.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-118106: The Elastic IP address %s assigned to %s is not allocated to the current AWS account.

Cause: The Elastic IP address is not allocated to the current AWS account.

Action: Ensure that an allocated Elastic IP address is assigned to the appliance.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118107: The Elastic IP address %s assigned to %s is not available because it is assigned to another instance.

Cause: The Elastic IP address is already assigned to another instance.

Action: Ensure that an available Elastic IP address is assigned to the appliance.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118108: Error initializing instance user-data.

Cause: One of the required fields could not be generated.

Action: Ensure that the assembly metadata is valid. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118109: Error generating appliance instance message payload.

Cause: (See message)

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118110: Timed out while waiting for message from appliance instance.

Cause: The appliance instance did not send an expected message within the allowed timeout period.

Action: Check the appliance instance logs.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118111: Unknown error while waiting for message from appliance instance.

Cause: (See message)

Action: Check the appliance instance logs.
Level: 1

Type: ERROR

Impact: Deployment

OAB-118596: Failed to describe target %s: %s

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

OAB-120551: Error obtaining plug-in installer

Cause:

Action:
Level: 1

Type: WARNING

Impact: Installation

OAB-120552: Error discovering plug-in configurations.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Installation

OAB-120553: Error while installing plug-in {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Installation

OAB-900015: Exception received from remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-960015: Exception received from remote side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-960016: Exception from the underlying communication layer on local side.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-960017: Unable to obtain the ab_instance directory.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAB-960018: Unable to obtain the local machines IP address.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Network

36 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

37 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

38 ODI-01100 to ODI-999999

ODI-01100: Agent {0} successfully cleaned up {1} stale sessions from work repository {2}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01101: Agent {0} successfully completed session {1} ({2}) (for scenario {3}) on {4} using context {5} with statistics: Rows {6} Inserts {7} Updates {8} Deletes {9} Errors {10}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01102: Agent {0} successfully completed session {1} ({2}) on {3} using context {4} with statistics: Rows {5} Inserts {6} Updates {7} Deletes {8} Errors {9}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01103: Agent {0} successfully completed step {1} in session {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01104: Agent {0} successfully connected to master repository using {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01105: Agent {0} successfully connected to work repository {1} using {2}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01106: Agent {0} created load plan {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01107: Agent {0} created session {1} ({2}) in work repository {3}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01108: Agent {0} created session {1} ({2}) from scenario {3} in work repository {4} using context {5}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01109: Agent {0} is delegating session {1} on work repository {2} to agent {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01110: Agent {0} successfully retrieved {1} schedules from work repository {2} using {3}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01111: Agent {0} started. Agent version: {1}. Port: {2}. JMX Port: {3}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01112: Agent {0} received a request to recalculate its schedule on work repository {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01113: Agent {0} received a data server test request for {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01114: Agent {0} received a request to stop load plan instance {1} on work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01115: Agent {0} received a ping request.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01116: Agent {0} received a request to retrieve its schedule on work repository {1}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01117: Agent {0} received a request to restart load plan instance ({1}) in work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01118: Agent {0} received a request to start load plan {1} on work repository {2} using context {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01119: Agent {0} received a request to start scenario {1}.{2} on work repository {3} using context {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01120: Agent {0} received a request to restart session {1} on work repository {2} using context {3}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01121: Agent {0} received a request to stop session {1} on work repository {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01122: Agent {0} successfully restarted {1} queued sessions from work repository {2} using {3}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01123: Agent {0} sent a request to agent {1}.

Cause: null

Action: null
Level: 16

Type: TRACE

Impact: Other

ODI-01124: Agent {0} started load plan {1}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01125: Agent {0} started session {1} ({2}) from scenario {3} in work repository {4} using context {5}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01126: Agent {0} started session {1} ({2}) in work repository {3} using context {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01127: Agent {0} started step {1} in session {2}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01128: Agent {0} is starting. Container: {1}. Agent Version: {2}. Port: {3}. JMX Port: {4}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01129: Agent {0} stopped.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01130: Agent {0} is stopping.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01131: Agent {0} encountered an error: {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01132: Agent {0} encountered a warning: {1}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01133: Agent {0} detected that the work repository {1} went down.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01134: Agent {0} encountered an error: {1}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01135: Agent {0} detected that the master repository went down.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01136: Starting Schedulers on Agent {0}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01137: Scheduler started for work repository {0} on Agent {1}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01138: Migrating Schedulers for Agent {0}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01139: The current task of the session ({0}) does not support stop immediate. This session will be stopped normally by the Agent ({1}) before next task begins.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01140: Unable to stop session ({0}) immediately. This session will be stopped by the agent ({1}) before next task begins.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01141: Agent {0} started load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01142: Agent {0} successfully completed load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01143: Agent {0} started computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01144: Agent {0} completed computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01145: Agent {0} not found when trying to stop session with id {1} in work repository {2}.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01146: Agent {0} invocation error when trying to stop session with id {1} in work repository {2}: {3}

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01147: Agent {0} stopped load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01148: Agent {0} executing load plan log purge for work repository {1} at {2}.

Cause: null

Action: null
Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01151: Agent {0} cannot continue load plan instance {1} ({2}), run {3} in work repository {4}, because the instance has been deleted.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01152: Agent {0} continuing processing for load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01153: An exception occurred while processing scheduled job for scenario {0} and version {1}. The exception message is : {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01154: An exception occurred while processing scheduled job for loadplan {0}. The exception message is : {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01155: Invalid repetition interval {0} specified in scheduled job for scenario {1} {2}. The schedule would not be repeated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01156: Invalid repetition interval {0} specified in scheduled job for loadplan {1}. The schedule would not be repeated.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01157: Coherence cluster property {0} is not found in the system properties for Agent {1}. Agent may connect to an unintended coherence cluster.

Cause: null

Action: null
Level: 1

Type: WARNING

Impact: Other

ODI-01158: Agent {0} started invoking load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}. Caused by: step {6}: {7}

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01159: Agent {0} completed load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01160: Agent {0} started processing load plan step {5} of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01161: Agent {0} completed load plan step {5} (status={6}) of load plan instance {1} ({2}), run {3} in work repository {4}.

Cause: null

Action: null
Level: 1

Type: TRACE

Impact: Other

ODI-01162: Scheduled task failed with id {0} of work repository {1} on Agent {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01163: The load plan logs purge operation failed on Agent {0}: {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01165: Client requires a repository with version {0} but the repository version found is {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01200: Session start failure: the request is incorrectly formed.

Cause: A malformed request was sent to the agent.

Action: Verify the request format and parameters sent to the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01201: Session start failure on agent {0}: JDBC connection error occurs while connecting to the master repository.

Cause: An incorrect connection was used for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01202: Session start failure on agent {0}: data source for master repository does not contain a master repository.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01203: Session start failure on agent {0}: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections. This is the case if an upgrade was being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01204: Session start failure on agent {0}: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01205: Session start failure on agent {0}: an authentication error occurred while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01206: Session start failure on agent {0}: the agent is not defined in the topology for master repository.

Cause: The session was not found in the master repository.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01207: Session start failure on agent {0}: JDBC connection error occurs while connecting to the work repository {1}.

Cause: An incorrect connection was used for the work repository database, or repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01208: Session start failure on agent {0}: database schema {1} does not contain a work repository.

Cause: The work repository connection information pointed to a database schema that did not contain a work repository.

Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01209: Session start failure on agent {0}: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections. This is the case if an upgrade was being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01210: Session start failure on agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01211: Session start failure on agent {0}: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.

Action: Verify that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01212: Session preparation failure: scenario {0} does not exist in work repository {1}.

Cause: The session request was received, but the agent was unable to find the named scenario in the work repository.

Action: Verify that the scenario name matches an existing scenario name in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01213: Session preparation failure: scenario {0} version {1} does not exist in work repository {2}.

Cause: The session request was received, and the scenario existed in the work repository, but not with the specified version.

Action: Ensure that the scenario version matches an existing scenario version in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01214: Session preparation failure: context {0} does not exist in the master repository.

Cause: The session request was received, but the agent was unable to find the context in the master repository.

Action: Ensure that the context matches an existing context code in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01215: Session preparation failure: privileges are insufficient to run scenario {0}.{1} in repository {2}.

Cause: User privileges were not sufficient for running this scenario in this repository.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01216: Session preparation failure: insufficient privileges to use Context {0} ({1}).

Cause: User privileges were not sufficient for using this context.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01217: Session {0} ({1}) fails with return code {2}.

Cause: The session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01218: Session preparation failure: database error occurs while connecting to the master repository.

Cause: The agent received a database error from the master repository while creating the session.

Action: Verify the state of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01219: Session preparation failure: database error while connecting to work repository {0}.

Cause: The agent received a database error from the work repository while creating the session.

Action: Verify the state of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01220: Session preparation failure: an unexpected exception occurred.

Cause: The remote agent faced an unexpected error while attempting to create the session.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Other

ODI-01221: Unable to restart session {0}: session is not found in work repository {1}.

Cause: The session to restart did not exist in the repository. This session may have been deleted, or an incorrect session ID or work repository was supplied.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01222: Session start failure on agent {0}: logical schema {1} cannot be found in the master repository.

Cause: The object to be executed referred to a logical schema not present in the master repository.

Action: Ensure that the logical schema configuration exists in your master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01223: Database error while connecting to the master repository.

Cause: The connection for the master repository database was incorrect, or the repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01224: Database error while connecting to work repository {0}

Cause: The connection for the work repository database was incorrect, or the repository database was down.

Action: Verify the work repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01225: An unexpected exception occurred.

Cause: The agent faced an unexpected exception.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Other

ODI-01226: Step {0} fails after {1} attempt(s).

Cause: This is an execution warning. The session step failed to execute after the maximum number of retries. If step failure was not handled in the package design, the session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01227: Task {0} fails on the source connection {1}.

Cause: This is an execution warning. The command on the source for this task finished with an error.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01228: Task {0} fails on the target connection {1}.

Cause: This is an execution warning. The command on the target for this task finished with an error.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01229: An error occurred while performing a {0} operation on model code {1}.

Cause: This is an execution warning. The operation specified failed on the model.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01231: An error occurred while performing a {0} operation on datastore {1}.

Cause: This is an execution warning. The operation specified failed on the datastore.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01232: Procedure {0} execution fails.

Cause: This is an execution warning. The procedure execution failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01233: Error while evaluating variable the following expression: {0} {1} {2}

Cause: This is an execution warning. The variable evaluation failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01235: Error while incrementing variable {0} to value {1}

Cause: This is an execution warning. The variable increment failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01236: Error while refreshing variable {0}.

Cause: This is an execution warning. The variable refresh failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01237: Error while setting variable {0} to value {1}.

Cause: This is an execution warning. The set variable operation failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01238: Flow {0} fails because the maximum number of allowed errors ({1} rows) is exceeded during the flow check. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because the number of errors detected in the flow exceeded the value defined in the interface.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
Level: 1

Type: WARNING

Impact: Other

ODI-01239: Flow {0} fails because the maximum percentage of allowed errors ({1} %) is exceeded during the flow check. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because the percentage of errors detected in the flow exceeded the value defined in the interface.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
Level: 1

Type: WARNING

Impact: Other

ODI-01240: Flow {0} fails while performing a {1} operation. This flow loads target table {2}.

Cause: This is an execution warning. The interface failed because one of the statements returned an error return code.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01241: Oracle Data Integrator tool execution fails.

Cause: This is an execution warning. The tool execution failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01242: Operating system command execution fails.

Cause: This is an execution warning. Execution of the operating system command failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01243: Session {0} ({1}) fails because work repository {2} went down.

Cause: Work repository database went down while session was being executed.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01244: Session {0} {1} was prepared successfully but fails because work repository {2} went down before execution could begin.

Cause: Work repository database went down while session was starting its execution.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01245: Session preparation failure: work repository {0} went down during session preparation.

Cause: Work repository went down while session was being prepared.

Action: Verify the state of the work repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01246: The Logical Schema has not been set for {0}.

Cause: Because the logical schema had not been set, the object could not be executed.

Action: Verify the object that you are trying to execute, and set the logical schema for this object.
Level: 1

Type: ERROR

Impact: Other

ODI-01247: Session {0} {1} was prepared successfully but fails because master repository went down before execution could begin.

Cause: Master repository database went down while session was starting its execution.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01248: Session preparation failure by Agent {0}: master repository went down during session preparation.

Cause: Master repository went down while session was being prepared.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01249: Session {0} ({1}) fails because master repository went down.

Cause: Master repository database went down while session was being executed.

Action: Verify the state of the master repository database. The session must be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01250: Session {0} ({1}) could not be stopped by Agent {2} because session {0} {1} already completed execution.

Cause: The session has already completed and cannot be stopped.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01251: Session ({0}) could not be stopped by Agent {1} because session ({0}) was not found in work repository {2}.

Cause: The session was not found in the work repository.

Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01252: Session ({0}) could not be stopped by Agent {1}: insufficient privileges to access session.

Cause: User privileges were not sufficient for accessing this session in this agent.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01253: Session {0} ({1}) could not be stopped by Agent {2}: an unknown error occurred.

Cause: An unexpected Exception occurred.

Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01254: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on work repository {3}.

Cause: The agent had incorrect connection for the work repository database, or repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01255: Session {0} ({1}) could not be stopped by Agent {2}: insufficient privileges to stop the session.

Cause: User privileges were not sufficient for stopping this session in this agent.

Action: Ensure that the user has sufficient privileges for this task.
Level: 1

Type: ERROR

Impact: Other

ODI-01256: Session {0} ({1}) stopped (Normal) by user {2}.

Cause: Session was stopped by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01257: Session {0} ({1}) stopped (Immediate) by user {2}.

Cause: Session was stopped by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01258: Session {0} ({1}) stopped (Abort) by user {2}.

Cause: Session was aborted by the user.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01259: Session Task {0} stopped (Normal) by user {1}.

Cause: Task was stopped by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01260: Session Task {0} stopped (Immediate) by user {1}.

Cause: Task was stopped by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01261: Session Task {0} stopped (Abort) by user {1}.

Cause: Task was aborted by the user.

Action: Review the task execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01262: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on master repository.

Cause: The agent had incorrect connection for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01263: Step {0} stopped (Normal) by user {1}.

Cause: Step was stopped by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01264: Step {0} stopped (Immediate) by user {1}.

Cause: Step was stopped by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01265: Step {0} stopped (Abort) by user {1}.

Cause: Step was aborted by the user.

Action: Review the step execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01266: Agent {0} detected Session as stale session and set to error status.

Cause: The agent detected a stale session and the session status was set to error status.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01267: Session ({0}) could not be stopped by Agent {1} because stop type {2} provided in the request is an invalid stop type.

Cause: The agent attempted to stop a session with an invalid stop type.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01268: Agent {0} does not support stopping asynchronous child sessions.

Cause: The agent attempted to stop an asynchronous child session and this is not supported.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01269: Session {0} ({1}) could not be stopped by Agent {2}: session is being run by another Agent with the same name.

Cause: The agent attempted to stop a session that is being run by a different agent.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01270: Session {0} ({1}) could not be stopped by Agent {2}: session {0} ({1}) is being run by {3} Agent which is not a listener Agent.

Cause: The agent attempted to stop a session that is being run by the internal agent and this is not supported.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01271: The asynchronous jndi name cannot be null for asynchronous jobs. The ESS job status cannot be updated.

Cause: The agent attempted to set the status of the asynchronous ESS job and its jndi name was not set.

Action: Review the jndi name supplied to the Enterprise Scheduler job.
Level: 1

Type: WARNING

Impact: Other

ODI-01272: The Logical Schema has not been set on {0} for {1}.

Cause: The logical schema for this object has not been set.

Action: Verify that the logical schema has been set in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01273: The selected technology {0} is not supported on source for {1}.

Cause: The selected technology is not supported for this object.

Action: Verify that the object has a valid technology.
Level: 1

Type: ERROR

Impact: Other

ODI-01274: Agent Exception

Cause: An error was detected by the agent when performing an operation.

Action: Review the underlying exception for more details.
Level: 1

Type: ERROR

Impact: Other

ODI-01275: An error occurred while performing a {0} operation on submodel step {1} of the model code {2}.

Cause: This is an execution warning. The operation specified failed on the submodel operation.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01276: An error occurred while executing the OnConnect command on JDBC connection created for data server {0} with transaction label {1}.

Cause: An error was occurred while executing the OnConnect command on the JDBC connection created to the data server.

Action: Review the underlying exception and update the OnConnect command definition configured for the data server.
Level: 1

Type: ERROR

Impact: Other

ODI-01277: An error occurred while executing the OnDisconnect command on JDBC connection created for data server {0} with transaction label {1}.

Cause: An error was occurred while executing the OnDisconnect command on the JDBC connection created to the data server.

Action: Review the underlying exception and update the OnDisconnect command definition configured for the data server.
Level: 1

Type: ERROR

Impact: Other

ODI-01278: Load plan instance {0}, run {1} does not exist in work repository {2}.

Cause: The Load Plan Instance run does not exist in the repository. This Load Plan Instance run may have been deleted, or an incorrect instance ID/run number or work repository was supplied.

Action: Verify that a load plan instance run with this instance ID and run number exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01279: The Source Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.

Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.

Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01280: The Target Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.

Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.

Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01281: Source Technology {0} of task {1} is not of JDBC Type. When both Source and Target commands are specified, the Source Technology should be of JDBC type.

Cause: When Source and Target commands are specified, the Source Technology should always be of JDBC type.

Action: Make Sure that you modify your Procedure or KM to either use a JDBC Source Technology or edit your step to use only the Target command.
Level: 1

Type: ERROR

Impact: Other

ODI-01282: Invalid log level {0} is specified. A valid log level value is between {1} and {2}.

Cause: Invalid log level specified for scenario/session invocation or for session restart.

Action: Please specify a valid log level.
Level: 1

Type: ERROR

Impact: Other

ODI-01283: Owb preparation failure: Owb object {0} of type {1} in location {2} does not exist in Owb repository {3}.

Cause: The session request was received, but the agent was unable to find the named Owb object in the Owb repository.

Action: Verify that the Owb object name matches an existing Owb object in the location in the Owb repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01284: Session {0} ({1}) with Owb audit Id {2} fails.

Cause: The session finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01285: Session {0} ({1}) Retreival of audit for auditId {2} failed in the {3} phase {4}. Please use OWB Design Client or Browser for further information.

Cause: An error was raised during the retreival of the Owb audit data.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01286: Session {0} ({1}) could not find Owb job for this session.

Cause: The session being aborted is not an Owb Job.

Action: Review the session being aborted in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-01287: Session {0} ({1}) with Owb audit Id {2} is in an invalid state to be aborted.

Cause: The session being aborted is not in a state that can be aborted.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01288: Session {0} ({1}) with Owb audit Id {2} abort fails.

Cause: The session abort finished in an error state.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01289: Agent {0} detected Session as stale session and set to error status. Please use OWB Design Client or Browser for further information.

Cause: The agent detected a stale OWB session and the session status was set to error status.

Action: Review the session execution details in the OWB Design Client or Browser.
Level: 1

Type: ERROR

Impact: Other

ODI-01290: Session {0} ({1}) Loading of audit for auditId {2} failed in the {3} phase {4}.

Cause: An error was raised during the loading of the Owb audit data.

Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1

Type: ERROR

Impact: Other

ODI-01291: Workspace {0} cannot be resolved to a physical workspace using context {1}.

Cause: The context does not contain a mapping for the logical workspace.

Action: Review the mappings defined in the context.
Level: 1

Type: ERROR

Impact: Other

ODI-01292: An execution context cannot be determined for this job.

Cause: An execution context cannot be determined for this job.

Action: Use the Context to provide an explicit context for this execution.
Level: 1

Type: ERROR

Impact: Other

ODI-01293: Exception occurred during spawning of ECID to child session.

Cause: Spawning of ECID from parent session to child session failed.

Action: Review the exception raised to get more detail.
Level: 1

Type: WARNING

Impact: Other

ODI-01294: Unwrapping of a wrapped ECID [{0}] failed.

Cause: Unwrapping of ECID failed.

Action: Review the exception raised and the format of wrapped ECID to get more detail on unwrap failure
Level: 1

Type: WARNING

Impact: Other

ODI-01295: Cleanup of Session {0} ({1}) raised the following {2} messages: {3}

Cause: Messages were raised during the Cleanup phase.

Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1

Type: WARNING

Impact: Other

ODI-01296: The Cleanup Tool encountered the following {0} nested errors when executing the Cleanup tasks: {1}

Cause: Messages were raised during the Cleanup tool execution.

Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1

Type: ERROR

Impact: Other

ODI-01297: Parallel task "{0}" failed; {1} child task(s) in error; Failed child tasks: {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01298: Serial task "{0}" failed because child task "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01299: A task "{0}" from one of the parallel branches has failed. Hence aborting the current branch

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01300: ASYNC_JNDI_NAME cannot be null for async job.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01301: Unable to submit Job Definition: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01302: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01303: RuntimeSessionfactory must not be null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01304: Unable to find request for ID {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01305: jobDefinitionId must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01306: scheduleDefinitionId must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01307: ContextCode is null, cannot lookup physical agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01308: SchedulingService object was created without an EntityManager, cannot lookup physical agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01309: Unable to find logical agent : {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01310: Unable to find context : {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01311: JobDefinition with name {0} already exists.

Cause: JobDefinition already exists.

Action: Check JobDefinition name.
Level: 32

Type: ERROR

Impact: Other

ODI-01312: Schedule with name {0} already exists.

Cause: Schedule already exists.

Action: Check Schedule name.
Level: 32

Type: ERROR

Impact: Other

ODI-01313: Unable to find job definition for ID {0}.

Cause: Wrong ID.

Action: Check ID.
Level: 32

Type: ERROR

Impact: Other

ODI-01314: Unable to find job definition with name {0}.

Cause: Wrong name.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-01315: Unable to update job definition.

Cause: Exception during updating.

Action: Check cause exception details.
Level: 32

Type: ERROR

Impact: Other

ODI-01316: Unable to remove job request.

Cause: Exception was thrown.

Action: Check cause exception details.
Level: 32

Type: ERROR

Impact: Other

ODI-01317: Unable to find scheduler definition with name {0}.

Cause: Wrong name.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-01318: jobDefnition is required to have a not null ID.

Cause: Metadata Object ID is null.

Action: Check job definition.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-01319: Error while refreshing variable {0}. Null/Empty refresh query is provided.

Cause: This is an execution warning. The variable refresh failed.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01350: Credential map key ''{0}'' not found in credential map ''{1}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01351: An unexpected error was thrown during execution of the scenario ''{0} - {1}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01352: An unexpected error was thrown during job execution

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01353: RequestId={0} Scenario={1} : Agent URL must be specified. The Job Definition must include the LocalAgent or the job submission must include a physical agent url ({2}) parameter.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01354: Load plan must be asynchronous

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01355: username ''{0}'' from credential map ''{1}'' does not match currentSubjectName ''{2}''

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01356: Credential map key parameter ''{0}'' not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01357: Error resolving ADF connection for connectionId=''{0}''.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01400: Agent {0} start failure: JDBC connection error occurs while connecting to the master repository.

Cause: The master repository information was incorrect, or the repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01401: Agent {0} start failure: data source for master repository did not contain a master repository.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01402: Agent {0} start failure: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections. This is the case when an upgrade is being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01403: Agent {0} start failure: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01404: Agent {0} start failure: an authentication error occurred while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01405: Agent {0} start failure: the agent is not defined in the topology for master repository.

Cause: This agent was not declared in the topology.

Action: Add this physical agent in the list of agents in the ODI topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01406: Agent {0} started with warning: JDBC connection error occurs while connecting to the work repository {1}.

Cause: The work repository information was incorrect, or the repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01407: Agent {0} started with warning: connection details of {1} do not contain a work repository.

Cause: The work repository connection information pointed to a database schema that did not contain a work repository.

Action: Review the work repository connection information and revise it as necessary.
Level: 1

Type: ERROR

Impact: Other

ODI-01408: Agent {0} started with warning: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections. This is the case when an upgrade is being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01409: Agent {0} started with warning: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01410: Agent {0} started with warning: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.

Action: Ensure that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01411: Agent {0} started with warning: a database error occurs while cleansing stale sessions.

Cause: The agent encountered a database error while attempting to close stale sessions.

Action: Review the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01412: Agent {0} started with warning: an unexpected error occurs while cleaning stale sessions.

Cause: The agent encountered an unexpected error while attempting to close stale sessions.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Verify the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01413: Request is incorrectly formed.

Cause: A malformed request was sent to the agent.

Action: Review the request format and parameters sent to the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01414: Error connecting to agent {0}: a JDBC error occurs while connecting to the master repository.

Cause: The remote agent had incorrect connection for the master repository database, or repository database was down.

Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01415: Error connecting to agent {0}: data source for master repository did not contain a master repository.

Cause: The master repository connection information for the remote agent pointed to a database schema that did not contain a master repository.

Action: Review the master repository connection information and revise it as necessary.
Level: 1

Type: ERROR

Impact: Other

ODI-01416: Error connecting to agent {0}: the master repository is in an invalid state.

Cause: The master repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.

Action: Verify the state of the master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01417: Error connecting to agent {0}: the master repository version {1} is not compatible with the agent version {2}.

Cause: The master repository was upgraded but not the remote agent, or the remote agent was upgraded but not the master repository.

Action: Upgrade the master repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01418: Error connecting to agent {0}: an authentication error occurs while connecting to the master repository.

Cause: An incorrect ODI user or password was specified for this master repository.

Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01419: Warning connecting to Agent {0}: JDBC connection error occurs while connecting to the work repository {1}.

Cause: The remote agent had incorrect connection for the work repository database, or the repository database was down.

Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01420: Warning connecting to Agent {0}: connection details of {1} do not contain a work repository.

Cause: The work repository connection information for the remote agent pointed to a database schema that did not contain a work repository.

Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01421: Warning connecting to Agent {0}: work repository {1} is in an invalid state.

Cause: The work repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.

Action: Verify the state of the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01422: Warning connecting to Agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.

Cause: The work repository was upgraded but not the remote agent, or the remote agent was upgraded but not the work repository.

Action: Upgrade the work repository version or the agent version.
Level: 1

Type: ERROR

Impact: Other

ODI-01423: Warning connecting to Agent {0}: work repository {1} is not bound to the master repository.

Cause: The work repository specified in the request was not found in the list of work repositories attached to the master.

Action: Verify that work repository name matches an existing one.
Level: 1

Type: ERROR

Impact: Other

ODI-01424: Agent host or port cannot be reached using {0}.

Cause: Incorrect host or port information was provided, or the agent was not started on the remote host.

Action: Correct the host or port information or start the agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01425: Agent application cannot be reached using {0}.

Cause: An incorrect application name was provided for this agent, or the agent application was not started on the host.

Action: Correct the application name used in the URL or verify the agent status.
Level: 1

Type: ERROR

Impact: Other

ODI-01426: Agent {0} is not defined in the topology for the master repository.

Cause: This agent was not declared in the topology.

Action: Add this physical agent to the list of agents in the ODI topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01427: invalid parameters

Cause: Invalid parameters were supplied in the request.

Action: Check the parameters that were supplied as part of the request. Ensure that parameter names and cases are correct.
Level: 1

Type: WARNING

Impact: Other

ODI-01428: internal error

Cause: An agent internal error occurred.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: FATAL

Impact: Other

ODI-01429: The user {0} is not authorized to perform request {1} on Agent {2}.

Cause: The user had insufficient privileges for performing this request against the remote agent.

Action: Amend the user privileges.
Level: 1

Type: ERROR

Impact: Other

ODI-01430: Agent {0} cannot clean the stale sessions in work repository {1} due to a database error.

Cause: The remote agent faced a database error while attempting to close stale sessions.

Action: Examine the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01431: Agent {0} cannot clean the stale sessions in work repository {1} because the work repository {1} is still down.

Cause: The remote agent was not able to connect to the work repository while attempting to close stale sessions.

Action: Determine the status of the repository. Once this repository is running, manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01432: Agent {0} cannot clean the stale sessions in work repository {1} due to an unexpected error.

Cause: The remote agent faced an unexpected error while attempting to close stale sessions.

Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Determine the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01433: The Internal agent does not support cleaning stale sessions from multiple work repositories.

Cause: Empty string value was passed for the work repository name in the Clean Stale Sessions request sent to the Internal Agent.

Action: Specify a non-empty valid work repository name in the Clean Stale Sessions request sent to the Internal Agent. If you want to clean the stale sessions across the work repositories, perform this operation on a Remote physical Agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01434: Agent {0} start failure: error while trying to use JMX Port {1}.

Cause: JMX Registry was unable to use the given port.

Action: Specify a different port by using the command-line parameter JMXPORT.
Level: 1

Type: ERROR

Impact: Other

ODI-01435: Storage space for the IDs of some object types is low in Repository {0}. When no storage space is available, it will not be possible to create obects of these types. Consider creating a new repository for the following object types (Object Type: Number Remaining) {1}.

Cause: Storage space was low for some IDs in this repository.

Action: Consider creating a new repository.
Level: 1

Type: WARNING

Impact: Other

ODI-01436: Error retrieving ID statistics for repository {0}.

Cause: The ID statistics for this repository could not be verified.

Action: Verify the statistics for this repository manually.
Level: 1

Type: WARNING

Impact: Other

ODI-01437: Error retrieving information from the credential store map.

Cause: Could not retrieve information from the credential store map.

Action: Verify that the credentials have been entered correctly into the credential store map.
Level: 1

Type: ERROR

Impact: Other

ODI-01438: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on master repository {2}.

Cause: Some SQL Exception occurred on the Master Repository.

Action: Verify that other operations on the Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01439: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on work repository {2}.

Cause: Some SQL Exception occurred on the Work Repository.

Action: Verify that other operations on the Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01440: Agent {0} cannot be stopped by user {1}: an unknown error occurred.

Cause: An unexpected Exception occurred.

Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.
Level: 1

Type: ERROR

Impact: Other

ODI-01441: Unable to connect to the master repository at JBDC URL={0} with USER={1}.

Cause: An SQLException occurred while creating connection to the master repository with the given parameters.

Action: Verify your Agent configuration and make sure the master repository connection parameters are correct.
Level: 1

Type: ERROR

Impact: Other

ODI-01442: Unable to load JBDC Driver {0} configured for master repository connection.

Cause: ClassNotFoundException occurred while loading the driver class.

Action: Verify your Agent configuration and make sure the driver specified for master repository connection is correct and the corresponding jar is present under driver folder.
Level: 1

Type: ERROR

Impact: Other

ODI-01443: Error while starting agent : {0}

Cause: Error occurred while starting the embedded web container.

Action: Verify your Agent configuration and make sure that the specified ports are available.
Level: 1

Type: ERROR

Impact: Other

ODI-01444: The master repository signature specified by the client {0} does not match the master repository signature of the agent {1}.

Cause: The client and the agent are not using the same master repository

Action: Verify the client and the agent are using the same master repository. Verify that the client is calling the correct agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01445: Invalid HTTP/S URL retrieved from the JRF utility : {0}

Cause: JRF utility has returned an invalid HTTP/S URL for the agent.

Action: Verify if ODI agent's dependent modules are successfully deployed on the container.
Level: 1

Type: ERROR

Impact: Other

ODI-01460: Unable to insert into table {0} for concurrent execution control. Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem. Error message: {1}

Cause: An exception was raised when inserting a record into the concurrent execution control table.

Action: Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem.
Level: 1

Type: WARNING

Impact: Other

ODI-01461: {0} job status has changed unexpectedly from {1} to {2} while waiting for its turn to run under concurrent execution control.

Cause: The status of a job was likely changed outside of the control of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.

Action: The job may have been changed outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
Level: 1

Type: WARNING

Impact: Other

ODI-01462: {0} job [{1}] should be the last one in the following waiting {0} list: {2}

Cause: The job may have been changed or deleted outside of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.

Action: The job may have been changed or deleted outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
Level: 1

Type: WARNING

Impact: Other

ODI-01463: {0} job [{1}] blocked by the following {0} job(s) due to potential concurrent execution condition: {2}{3}

Cause: The job was under concurrent execution control with Raise Error violation behavior, and there were existing runnable and/or waiting jobs submitted ahead of the job.

Action: Start the job when other concurrently running and waiting jobs are completed, or change the job's violation behavior to Wait To Execute before starting the job.
Level: 1

Type: WARNING

Impact: Other

ODI-01500: SQL Exception when accessing work repository {0} while executing load plan instance {1} - {2}

Cause: A SQLException was thrown when trying to update the work repository

Action: The same set of updates will be attempted later, potentially from a different agent
Level: 1

Type: ERROR

Impact: Other

ODI-01501: Cannot find variable "{0}" in the definition of load plan instance {1}.

Cause: The start/restart load plan request contained startup values for variables that are not defined in the load plan

Action: User error or problem in the IDE invocation code
Level: 1

Type: ERROR

Impact: Other

ODI-01502: Load plan instance {0} is in an inconsistent state: {1}

Cause: Indicates a problem in the ODI code, like a wrapped IllegalStateException

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01503: Load plan logs for instance {0}, run {1} are corrupted: {2}

Cause: Indicates a problem in the ODI code, it is a wrapped IllegalStateException

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01504: Trying to update variables during execution of step "{0}" (load plan instance {1}, run {2}), as part of the exception handler for step "{3}", but variable updates during exception handlers are not supported.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01505: Current value "{0}" of variable "{1}" (while evaluating When clause "{2}") is not a valid value of type {3} (load plan instance {4}, run {5}).

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01506: "Comparison value of step "{2}" ("{0}") is not a valid value of type {3} (load plan instance {4}, variable tested "{1}").

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01507: Load Plan Instance restart called for instance {0}, but no previous runs were found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01508: Load Plan Instance start called for instance {0}, but previous runs have been found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01509: Load Plan Instance {0} cannot be restarted because the previous run ({1}) status "{2}" is not in "{3}" status.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01510: The same load plan instance {0} simultaneously started by two agents.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01511: Step "{0}" should have already been marked as started before adding value for variable "{1}" (load plan instance {2}, run {3}).

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01512: Variable "{0}" is defined as having datatype "{1}" in Load Plan instance {2}, but as having type "{3}" in scenario "{4}" (version {5}), Load Plan instance step "{6}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01513: Error reading load plan information for session number {0}: "{1}"

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01514: Error trying to stop load plan, instance {0} not found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01515: Load Plan instance {0} could not be stopped by agent {1} because stop type ({2}) provided in the request is invalid.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01516: Can not start load plan: load plan with name "{0}" does not exist in work repository {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01517: Load Plan instance {0}, run {1} could not be stopped because that run is already completed (with status "{2}").

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01518: Parallel step "{0}" failed; {1} child step(s) in error, which is more than the maximum number of allowed errors ({3}) defined for the parallel step. Failed child steps: {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01519: Serial step "{0}" failed because child step "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01520: Case-When/Else step "{0}" failed because child step "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01521: Case step "{0}" failed; the selected child "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01522: Run Scenario step failed during invocation. Error message was: {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01523: Exception handler for step "{0}" failed, because the root exception serial step "{1}" is in error.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01524: Physical agent {0} could not be found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01525: Physical agent not found for logical agent name "{0}" and context "{1}" while executing step "{2}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01526: Error encountered while trying to start scenario "{1}{2}" (step "{3}"): {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01527: Error refreshing variable "{0}": the associated SQL query returned no results.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01528: Error refreshing variable "{0}": {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01529: Refresh of variable "{0}" failed : {1} {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01530: Load plan instance was stopped by user request.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01531: Timeout triggered while executing step "{0}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01532: Timeout triggered on a parent step "{0}" while executing step "{1}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01533: Error refreshing variable "{0}": could not get a connection to the logical schema "{1}" using context {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01534: Could not get SQL query text for variable "{0}" while trying to refresh it.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01535: Can not continue load plan instance {0}, run {1}, because the instance has been deleted.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01536: Load plan instance {0}, run {1} failed to launch scenario: scenario {2} does not exist in work repository {3}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01537: Load plan instance {0}, run {1} failed to launch scenario: Version {3} of scenario {2} does not exist in work repository {4}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01538: Unexpected Exception occurred while executing Load plan instance {0}, run {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01539: Agent {0} cannot continue load plan processing for instance {1}, run {2} on work repository {3}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01540: Agent {0} start failure: error while trying to use Http Port {1}.

Cause: Http service was unable to use the given port.

Action: Specify a different port by using the command-line parameter PORT.
Level: 1

Type: ERROR

Impact: Other

ODI-01541: Load Plan start failure on agent {0}: ODI User and Password not specified.

Cause: ODI user and password are not set.

Action: Please specify ODI user and password.
Level: 1

Type: ERROR

Impact: Other

ODI-01542: Start Scenario failure on agent {0}: ODI User and Password not specified.

Cause: ODI User and password are not set.

Action: Please specify ODI user and password.
Level: 1

Type: ERROR

Impact: Other

ODI-01543: RuntimeAgent cannot be used inside an opened transaction, it must be used outside a TransactionTemplate

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01544: None of the agents in Load Balancing list is able to handle this execution ({0}).

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01545: Missing odi supervisor credentials in credential store map [{0}] with key [{1}].

Cause: Could not retrieve information from the credential store map.

Action: Verify that the credentials have been entered correctly into the credential store map.
Level: 1

Type: ERROR

Impact: Other

ODI-01546: The dbms_lock acquisition with lock handle {0} timed out.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01547: The Agent detected deadlock on dbms_lock acquisition with lock handle {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01548: The dbms_lock acquisition failed with illegal lock handle {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01549: The dbms_lock acquisition with lock handle {0} failed with illegal params error. The parameters are {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01550: The dbms_lock acquisition with lock handle {0} failed with unknown return code {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01551: The dbms_lock acquisition failed with a sql exception {0}. Please check if the work repository db user has EXECUTE privilege on DBMS_LOCK package.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01552: The dbms_lock release failed with illegal lock handle {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01553: The dbms_lock release for lock handle {0} failed with invalid parameters.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01554: The dbms_lock release for lock handle {0} failed because you do not own the lock.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01555: The dbms_lock release for lock handle {0} failed with an unknown return code {1}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01556: The lock acquisition failed. The lock is already locked by other connection object.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01557: Error refreshing variable "{0}": the associated SQL query returned a NULL value.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01558: The session {0} corresponding to the load plan step {1} of load plan instance {2}, run {3} is not found. We assume this step to be in error status.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01559: Load Plan Instance {0} cannot be restarted because the context {1} was not found in the work repository {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01560: Load Plan {0} cannot be started because the context {1} was not found in the work repository {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01561: Load Plan {0} cannot be started because the user {1} does not have view privileges to the execution context {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01562: Load Plan Instance {0} cannot be restarted because the user {1} does not have view privileges to the execution context {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01563: Load Plan {0} cannot be started because the user {1} does not have execute privileges to the Load Plan {0}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01564: Load Plan Instance {0} cannot be restarted because the user {1} does not have restart privileges.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01565: Load Plan {0} cannot be started because an unknown exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01566: Load Plan Instance {0} cannot be restarted because an unknown exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01567: Load Plan {0} cannot be started because a SQL Exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01568: Load Plan Instance {0} cannot be restarted because a SQL Exception occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01569: Error trying to stop load plan, instance {0} run {1} not found.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01570: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop the Load Plan Instance.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01571: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop Sessions.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01572: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because a SQL Exception occurred while accessing the Repository.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01573: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because an Unknown error has occurred.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01574: Day of week is not specified for the schedule.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01575: Invalid value specified for the excluded days of month filter: {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01576: LoadPlan Operation {0} on Agent {1} failed with the exception {2}.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01577: Parallel step error triggered on a parent step "{0}" while executing step "{1}".

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01578: Invalid load plan log level value specified: {0}. A valid load plan log value is between {1} and {2}.

Cause: Invalid load plan log level value was supplied in the request.

Action: Check that the load plan log level value supplied was valid (1 - 6) for the request.
Level: 1

Type: ERROR

Impact: Other

ODI-01579: Agent {0} start failure: data source for master repository did not contain a master repository using JDBC URL={1} with USER={2}.

Cause: The master repository connection information pointed to a database schema that did not contain a master repository.

Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01580: Unable to set the role OWB_USER for this user.

Cause: An attempt was made to set the role OWB_USER for the connected user.

Action: Check that the role exists and the connected user is an OWB user.
Level: 1

Type: ERROR

Impact: Other

ODI-01581: Unable to set the workspace {0} for this user.

Cause: An attempt was made to select the OWB workspace for the connected user.

Action: Check that the workspace exists and the connected user has got privilege to access it.
Level: 1

Type: ERROR

Impact: Other

ODI-01582: Unexpected error when connecting to Owb workspace {0}.

Cause: An unexpected error occurred when connecting to workspace.

Action: Verify that the Owb repository is up and running.
Level: 1

Type: ERROR

Impact: Other

ODI-01583: Owb workspace {0} does not contain components that enable execution from Odi.

Cause: A component that is required by ODI has not been found in this workspace.

Action: Verify that the Owb repository contains the correct patch for ODI.
Level: 1

Type: ERROR

Impact: Other

ODI-01584: Mandatory parameter {0} is missing for https protocol.

Cause: A parameter that is required to start ODI agent to enable https protocol is missing.

Action: Verify that the parameter is specified in odiparams.[sh|bat].
Level: 1

Type: ERROR

Impact: Other

ODI-01585: A Step with Id {0} does not exist in the Session {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01586: A Task with Id {0} does not exist in the step {1} of the Session {2}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01587: An execution context cannot be determined for OGG operation {0}.

Cause: An execution context cannot be determined for OGG operation.

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01588: The specified operation {0} provided is not supported by this tool.

Cause: The operation provided is not supported by this tool.

Action: Verify the parameters
Level: 1

Type: ERROR

Impact: Other

ODI-01589: The execution of the OdiOggCommand operation {0} failed.

Cause: The execution of the OdiOggCommand operation failed.

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01590: The execution of the script failed. {0}

Cause: The execution of the script failed in the BSF Engine.

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-01591: The ODI agent name {0} specified in the client request does not match with the ODI agent {1} serving the request.

Cause: The client and the agent are not using the same physical agent name.

Action: Verify the client and the agent are using the same agent name. Verify that the client is calling the correct agent.
Level: 1

Type: ERROR

Impact: Other

ODI-01592: Error occurred testing connection to dataserver with agent {0}

Cause: Dataserver connection test failed on the agent

Action: Verify that dataserver connection configuration is valid. Verify that dataserver is available
Level: 1

Type: ERROR

Impact: Other

ODI-01593: The following bind parameters ({0}) in the task command {1} are not bound to any value. All the bind parameters should be bound for the command to be successful.

Cause: Either the source command is not providing values for some of the bind parameters in target command or the Odi Variables and/or Odi Sequence meta-data is not generated for the Scenario.

Action: Verify that either the source command is correct or the Odi Variables and/or Odi Sequences meta-data is generated in the Scenario.
Level: 1

Type: ERROR

Impact: Other

ODI-01594: The connection to the data server {0} failed.

Cause: The data server might be down or the data server connectivity settings are not correct.

Action: Verify that you are able to test the data server using the Studio successfully.
Level: 1

Type: ERROR

Impact: Other

ODI-01595: The command script failed with trace {0}.

Cause: There was a failure in the Ftp or Sftp command script.

Action: Verify the trace and resolve the error in the command script passed to the tool.
Level: 1

Type: ERROR

Impact: Other

ODI-01600: Unable to update Opmn Xml file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01601: Unable to parse Opmn xml file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01602: Please provide all arguments

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01603: Syntax: java DeleteAgentFromOpmn <Instance Home> <OracleOpmnHome> <Agent Name>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01604: Unable to parse Opmns Snippet Xml

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01605: Component already exists in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01606: Please provide the value for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01607: Error reading file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01608: No of values provided for component name and port number are not equal. Please provide the same no of values for both.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01609: No of values provided for component name and JMXport number are not equal. Please provide the same no of values for both.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01610: ODI environment variable {0} is not set and ODI Tool startcmd not launched from interactive console.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01611: Must provide username for {0} before obtaining password.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01612: Unknown parameter ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01613: Unknown parameter value pair ignored: {0}={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01614: {0} is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01615: DESCRIPTION Resumes an execution session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> [<log_level>] ["-AGENT_URL=<agent_url>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01616: DESCRIPTION Starts an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agent.(cmd|sh) -NAME=<agent name> [-PORT=<port>] [-PROTOCOL=<protocol>] [-JMXPORT=<jmxport>] [-ODI_CONNECTION_RETRY_COUNT=<nn>] [-ODI_CONNECTION_RETRY_DELAY=<nn>] PORT represents the listening port. It should match the port value specified against the physical agent defined in Topology. PROTOCOL represents the listening protocol, HTTP or HTTPS. Its default value is HTTP. NAME represents the name of this physical agent. It should match the name of a physical agent defined in Topology. User must have created an agent with this name using configuration wizard. JMXPORT represents the JMX port used for JMX notifications etc. Its default value is calculated as PORT + 1000, or 20810 if the calculated value is greater than 65535 ODI_CONNECTION_RETRY_COUNT represents the number of times a connection to the ODI Repository will be retried. Its default value is 10 ODI_CONNECTION_RETRY_DELAY represents the number of milliseconds between connection retries to the ODI Repository. Its default value is 7000

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01617: DESCRIPTION Stops an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agentstop.(cmd|sh) "-NAME=<agent name>" ["-AGENT_URL=<agent_url>"] ["-IMMEDIATE=<true(default)|false>" ["-MAX_WAIT=<stop timeout in millis>"]]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01618: DESCRIPTION Restarts execution of a load plan instance. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartloadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01619: DESCRIPTION Starts a Oracle Data Integrator command. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startcmd.(cmd|sh) "-INSTANCE=<instance_name>" <Command Name> ["<command parameter>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01620: DESCRIPTION Starts a load plan. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startloadplan.sh "-INSTANCE=<instance_name>" <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01621: DESCRIPTION Starts a scenario. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startscen.(cmd|sh) "-INSTANCE=<instance_name>" <scenario_name> <scenario_version> <context_code> [<log_level>] ["-SESSION_NAME=<session_name>"] ["-KEYWORDS=<keywords>"] ["-AGENT_URL=<agent_url>"] ["-ASYNC=(no|yes)"] ["-DEBUGGABLE=(no|yes)"] ["-SUSPEND_FIRST_STEP=(no|yes)"] ["-DESCENDANTS_DEBUGGABLE=(no|yes)"] ["-BREAK_ON_ERROR=(no|yes)"] ["<variable>=<value>"]* -ASYNC=no is default; -ASYNC=yes is valid only if -AGENT_URL is specified.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01622: DESCRIPTION Stops a load plan instance execution. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stoploadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" ["-STOP_LEVEL=<normal(default)|immediate>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01623: DESCRIPTION Stops the execution of a running session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stopsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> "-AGENT_URL=<agent_url>" ["-STOP_LEVEL=<normal(default)|immediate>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01624: DESCRIPTION Encode a password. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX encode.(cmd|sh) "-INSTANCE=<instance_name>" <password>

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01625: This must be executed from a domain. System property domain.home cannot be null"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01626: "Neither parameter {0} nor {1} is specified"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01627: "Error getting instance properties"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01628: {0} (arg[{1}]) "{2}" should not be blank.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01629: {0} (arg[{1}]) "{2}" should specify a valid integer.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01630: {0} (arg[{1}]) "{2}" should specify a valid long number.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01631: -STOP_LEVEL parameter value must be one of: {0}, {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01632: Session "{0}" is being stopped ({1})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01633: OracleDI: Starting scenario {0} {1} in context {2} ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01650: -AGENT_URL=<agent_url> is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01651: Agent {0} error while executing: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01652: Unknown parameter ignored: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01653: Unknown parameter value pair ignored: {0}={1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01654: load_plan_instance_id is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01655: Usage: RestartLoadPlan -INSTANCE=<instance_name> <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01656: Load plan instance "{0}", run {1} has restarted

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01657: load_plan_name and context_code are mandatory parameters

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01658: Usage: StartLoadPlan -INSTANCE=<instance_name> <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01659: Load plan "{0}", instance "{1}", run {2} has started

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01660: load_plan_instance_id is a mandatory parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01661: Usage: StopLoadPlan -INSTANCE=<instance_name> <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" [-STOP_LEVEL=<normal (default) | immediate>]

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01662: Load plan instance "{0}", run {1} has stopped ({2})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01663: -STOP_LEVEL parameter value must be one of: {0}, {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01664: Waiting for completion of load plan execution.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01665: Load plan execution completed in {0} status.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01700: SessionId is not valid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01701: The session was not found in the repository: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01702: This operation is not supported on this platform

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01800: Exception {0} has occurred as ESS-EM linking is disabled.

Cause: Unable to connect to master repository.

Action: Check if the master repository is accessible and up. This is not mandatory since master repositories can be down.
Level: 1

Type: ERROR

Impact: Configuration

ODI-01801: Agent target discovery mbean registration has failed due to {0}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error and take corrective action.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01802: Agent target discovery mbean unregistration has failed due to {0}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error and take corrective action.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01803: Error {0} has occurred during mbean registration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01804: Error {0} has occurred during mbean deregistration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01805: Error {0} has occurred during notification listener registration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01806: Error {0} has occurred during notification listener deregistration.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01807: Error {0} has occurred during deregistration of ODI Service Mbean {1}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01808: Error {0} has occurred during registration of Agent Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the server and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01809: Error {0} has occurred during registration of Master Repository Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01810: Error {0} has occurred during registration of Work Repository Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01811: Error {0} has occurred during registration of Session Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01812: Error {0} has occurred during registration of Event Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01813: Error {0} has occurred during registration of Session Search Service Mbean.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the error and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01814: No repository definition found for work repository {0} in repositories.xml. Search will be disabled for this repository.

Cause: A configuration error has occurred.

Action: Add the jndi entries for all the work repositories for each of the master repositories in repositories.xml.
Level: 1

Type: ERROR

Impact: Configuration

ODI-01815: Exception {0} has occurred during Session Search by id.

Cause: A runtime error has occurred.

Action: No action is required. The session id mentioned for search is not available.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01816: Session status passed {0} is invalid.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01817: Error {0} has occurred while fetching statistics for agents. Statistics shown might not be complete.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01818: Agent Service Mbean is not initialized. Re-initialization of agents in tree is disabled.

Cause: A runtime error has occurred.

Action: Check the log for details on the error, fix the same and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01819: Event Service Mbean is not initialized. Re-initialization of event notification listeners is disabled.

Cause: A runtime error has occurred.

Action: Check log for details on the error, fix the same and restart the OdiConsole application.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-01820: Agent {0} is not up at {1} for reason {2}.

Cause: A runtime error has occurred.

Action: Check the log for details on the error.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03000: error in creating repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03001: error in updating repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03002: error in deleting repository connection {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03003: Failed to connect to the error table {0}. Check the connection details and retry.

Cause: The table might no longer exist or the structure of the table might not be correct.

Action: Check the connection details and retry.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03016: Creation of Work Repository failed because a previous Work repository was found, and the user had asked not to overwrite any existing repository.

Cause: Work repository already exists and overwriting of the repository was not chosen

Action: Select overwriting of Work Repository
Level: 1

Type: ERROR

Impact: Data

ODI-03017: Exception occurred while creating Work Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03018: Test connection failed due to {0}.

Cause: Connection to DB failed

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03019: Exception occurred while exporting Master Repository. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03020: Only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: A file with extension other than zip was uploaded.

Action: Make sure file uploaded has zip as extension
Level: 1

Type: ERROR

Impact: Data

ODI-03021: Exception occurred while importing Work Repository. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03022: Attaching of Work Repository failed due to error: {2}

Cause: Errored out due to {2} and overwriting of the repository was not chosen

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03023: Attaching of Work Repository failed

Cause: An unexpected error occured and overwriting of the repository was not chosen

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03024: Exception occurred while attaching Work Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03031: Creation of Master Repository failed at {0}.

Cause: Creation of Master Repository Failed

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03032: Exception occurred while creating Master Repository at {0} failed. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03033: Supervisor Password and Confirm Supervisor Password fields should match.

Cause: Supervisor Password and Confirm Supervisor Password fields must match

Action: Input same passwords
Level: 1

Type: ERROR

Impact: Data

ODI-03034: Test connection failed due to {0}.

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03035: Supervisor Password and Confirm Supervisor Password fields should match and only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: Both the password match and zip files to be uploaded conditions failed

Action: Make sure both the passwords are same and file uploaded is zip file
Level: 1

Type: ERROR

Impact: Data

ODI-03036: Only zip files can be uploaded , the {0} upload was unsuccessful.

Cause: zip files to be uploaded condition failed

Action: Make sure file uploaded is zip file
Level: 1

Type: ERROR

Impact: Data

ODI-03037: Exception occurred while exporting Master Repository. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03038: Exception occurred while exporting Physical Topology. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03039: Exception occurred while Importing Master Repository. Failure reason {1}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03040: Unable to connect to the Repository User. {0}

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03041: Unable to connect to the DBA User. {0}

Cause: Testing of DB connection failed

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03046: unable to find the agent for given logical agent and context code

Cause: Physical Agent mapping was not defined for selected logical agent and context.

Action: A different set of credentials is required or the mapping needs to be defined.
Level: 1

Type: ERROR

Impact: Data

ODI-03047: exception while executing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03048: Only XML files can be uploaded: the {0} upload fails

Cause: File selected for import was not a XML file.

Action: Provide the XML file.
Level: 1

Type: ERROR

Impact: Data

ODI-03049: exception while importing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03050: failed to start scenario : {0} ? {1} in debug mode.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03075: Error in purging Load Plans Executions/Sessions {0}

Cause: An exception has occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03076: exception while killing {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03077: Selected Session {0} is in {1} State, and therefore cannot be killed.

Cause: The selected session was in Done, Error, or Warning state.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Data

ODI-03078: Selected Session {0} is in {1} State, and therefore cannot be restarted.

Cause: The selected session was not in Error state.

Action: No action is required.
Level: 1

Type: ERROR

Impact: Data

ODI-03079: exception while restarting {0}. Failure reason {1}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03080: exception while clearing stalesessions. Failure reason {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03081: Error fetching records from error table {0}. The table might no more exist or the format of the table is not correct

Cause: The table might no longer exist or the structure of the table might not be correct

Action: Upgrade the CKM
Level: 1

Type: ERROR

Impact: DATA

ODI-03082: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.

Cause: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.

Action: Future release will have the ODI_PK primary key column incorporated in CKM SQL.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03083: Scenario "{0}" parent not found.

Cause: Trying to get the Odi Object which does not exist or has been deleted.

Action: Check the logs
Level: 1

Type: ERROR

Impact: Data

ODI-03090: failed to restart session : {0} in debug mode.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03101: import of {1} from {0) failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03102: export of {1} to {0) failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03103: failed to stop a loadplan instance id : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03104: failed to start a loadplan : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03105: failed to start a scenario : {0} ? {1}

Cause: An unexpected error occured

Action: Check the logs1
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03106: failed to restart session : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03107: failed to clean stale sessions for repository : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03108: failed to stop session : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03109: Creation of work runtime repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03110: Update of work runtime repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03111: failed to read config.properties

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03112: shared config dir path is not valid : {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03114: {0} not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03115: {0} is not correct

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03116: failed to read

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03117: datasource not located at {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03118: Could not get the service locator. JpsServiceLocator service is not configured.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03119: JPS Exception {0} was thrown. Credential Store might not be configured.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03120: Credential store could not be found.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03121: Not populating any values in credential store

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03122: Exception in purging Session/Load Plan Executions

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03123: Exception occured while inserting usedInContext in Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03124: Exception occured while deleting usedInContext in Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03125: Exception occured while inserting usedInContext in Edit Physical Schema

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03126: Exception in adding an entity

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03127: Odi object not found

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03128: Exception in update

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03129: Unable to find odi object {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03130: Loading of entity failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03131: Unauthorized to delete entity of type

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03132: error occurred while executing method

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03133: no repository definition found for alias {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03134: login failed for user {0}=

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03135: version mismatch

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03136: unable to connect to repository with alias {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03137: Error occurred in EMIntegrationServlet.doOperation() - {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03138: failed to init jview diagrammer

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03139: repositories.xml path not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03140: {0} file does not exist at {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03141: failed to create RepositoryDefinitionRegistry

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03142: error logging out a user after session expired

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03143: Creation of work dev repository at {0} failed. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03144: Creation of Master Repository failed at {0}. Failure reason {1}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03145: Check the logsPrivilegedActionException {0} was thrown. system-jazn-data.xml might not have the privileges specified.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03146: ???

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03147: Delete operation failed

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03148: Maximum number of sessions should be in between 1 and 99999.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03149: Port Number should not be non negative.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03150: Invalid Context code. Context code cannot have lower case characters and white spaces. Though, it can contain '$' and '_' special characters.

Cause: A validation error occured

Action: Context code cannot have lower case characters and white spaces
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03184: Maximum Cache Entries cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03185: Unused Blueprint Lifetime cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03186: Maximum Threads Number cannot be less than Max Threads Per Session.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03187: Max Threads Per Session cannot be less than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03188: Maximum Threads Number should be greater than zero.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03189: Maximum Threads Number cannot be less than Maximum Session Number.

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03190: Exception fetching connector points. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03191: Exception fetching model. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03192: Exception fetching physical schema. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03193: Exception fetching Data Server. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03194: Exception fetching Catalog. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03195: Exception fetching Constraints. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03196: Exception fetching connector point properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03226: Parameter File could not be Loaded.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03260: Failed to apply settings for agent: {0}

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03261: Exception while applying settings for agent: {0}. Failure reason: {1}

Cause: An unexpected error occurred

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03265: Exception occurred while creating Datasource. Failure reason {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03266: Data Source already exists for {0}.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03267: No valid repository alias is found. Click on management link on top right corner to create one.

Cause: Either there were no repository connection aliases, or those that were created did not have a valid JNDI name

Action: Create a new repository connection alias.
Level: 1

Type: ERROR

Impact: Data

ODI-03276: Tab limit reached.Please close at least one tab.

Cause: Max limit on the number of tabs that can be open has been met.

Action: Close at least one tab
Level: 1

Type: ERROR

Impact: Data

ODI-03277: Object cannot be found.

Cause: The object might have been deleted.

Action: Refresh your view.
Level: 1

Type: ERROR

Impact: Data

ODI-03278: View operation fails with the following exception {0}. See the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03279: Add operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03280: Edit operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03281: Delete operation failed with the following exception {0}. Please see the server log for details.

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Data

ODI-03290: You are not authorized to add a new entity of this type.

Cause: User doesn't have required privileges to add an new entity of a particular type

Action: No action
Level: 1

Type: ERROR

Impact: Data

ODI-03326: Please specify a valid search text

Cause: Invalid search text was specified

Action: Provide a valid search text
Level: 1

Type: ERROR

Impact: Data

ODI-03327: Please choose at least one model or project type.

Cause: No model or project type was selected

Action: Select at least one model or project type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03328: Please choose at least one topology type.

Cause: No topology type was selected

Action: Select at least one topology type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03329: Please choose at least one runtime type.

Cause: No runtime type was selected

Action: Select at least one runtime type so that search criteria is valid
Level: 1

Type: ERROR

Impact: Data

ODI-03330: Exception while importing attrbutes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03331: Exception while importing properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03332: Exception while fetching attributes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03333: Exception while fetching properties. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03334: Exception while importing propeties and expressions of attributes. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03335: Exception while loading components. Reason: {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03336: Error in persisting user preferences {0}

Cause: An unexpected error occurred.

Action: Check the logs.
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03337: UserPref.xml path is not set

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03338: Failed to get User Preferences

Cause: An unexpected error occured

Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-05000: Task {0} ({1}) on logical schema {2} with Context Id {3} fails since scripting technology name could not be discovered.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Other

ODI-05001: Session {0} ({1}) could not be stopped by Agent {2}: Session run on an 'Internal' agent cannot be stopped from another process.

Cause: Stopping a session being run by an internal agent from another process is not possible.

Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: ERROR

Impact: Other

ODI-10000: Method setObject class DwgObjectRepresentor does not support object class: {0}.

Cause: Java method was not found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10001: Action unauthorized for this license: {0}

Cause: Action was unauthorized for this license.

Action: Choose another license.
Level: 32

Type: ERROR

Impact: Security

ODI-10002: Only one local repository can be defined; {0} were found.

Cause: More than one local repository was found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10003: No connection set.

Cause: No connection was set.

Action: Set connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10004: File already exists.

Cause: File already existed.

Action: Choose another file.
Level: 32

Type: ERROR

Impact: File

ODI-10005: Repository is expected to be a master repository.

Cause: Repository was expected to be a master repository.

Action: Choose master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10006: Repository is expected to be enterprise repository.

Cause: Repository was expected to be an enterprise repository.

Action: Choose enterprise repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10007: Object must be in editable state before using set methods.

Cause: The object was not in editable state.

Action: Edit this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10008: Object must be in consult mode before using methods get.

Cause: The object was not in consult mode.

Action: Consult the object.
Level: 32

Type: ERROR

Impact: Other

ODI-10009: Object does not exist in the repository.

Cause: The repository did not contains this object.

Action: Choose another object or create first this one.
Level: 32

Type: ERROR

Impact: Other

ODI-10010: This type of object cannot be updated.

Cause: Object could not be updated.

Action: Do not update this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10011: Invalid object; it has been updated by another user.

Cause: Object was updated by another user.

Action: Refresh the object.
Level: 32

Type: ERROR

Impact: Other

ODI-10012: Object cannot be inserted

Cause: Object could not be inserted.

Action: Check object.
Level: 32

Type: ERROR

Impact: Other

ODI-10013: This import action has been cancelled because it could damage your repository. This is due to an {0} object that has object identifier {1} that is greater than that for the current {0} id sequence. Importing this object would lead to primary key violations in the future.

Cause: Import could damage your repository.

Action: Check identifier sequences.
Level: 32

Type: ERROR

Impact: Other

ODI-10014: Method must be redefined in derived classes. It cannot be called for DwgObject

Cause: Method must be redefined in derived classes.

Action: Call redefined method.
Level: 32

Type: ERROR

Impact: Other

ODI-10015: The work repository {0} is not declared in this master repository, the import process has been cancelled.

Cause: Work repository was not declared in this master repository.

Action: Declare work repository and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10016: Import aborted.

Cause: Import was aborted.

Action: Check objects and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10017: This import is forbidden: the text {0} has a different origin in the repository and in the import file.

Cause: The text has a different origin in the repository and in the import file.

Action: Check import file and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10018: The repository {0} is not coherent between the current repository and the import file.

Cause: The repository was not coherent between the current repository and the import file.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10019: Impossible to create the directory {0}.

Cause: I was not possible to create the directory.

Action: Check your system rights for creating directory; directory's path and name.
Level: 32

Type: ERROR

Impact: File

ODI-10020: Impossible to replace the file

Cause: It was not possible to replace the file.

Action: Check, if you have enough rights for this operation.
Level: 32

Type: ERROR

Impact: File

ODI-10021: Unspecified save directory.

Cause: Directory to save environment information was unspecified.

Action: Specify the directory for saving the environment information file.
Level: 32

Type: ERROR

Impact: Other

ODI-10022: You must specify all options.

Cause: Missed one or more options.

Action: Specify missed options.
Level: 32

Type: ERROR

Impact: Other

ODI-10023: Invalid license. This license is suitable for {0}.

Cause: Invalid license.

Action: Check license.
Level: 32

Type: ERROR

Impact: Security

ODI-10024: Your installation of Oracle Data Integrator is corrupted.

Cause: The technology description file contains errors.

Action: Reinstall Oracle Data Integrator.
Level: 32

Type: ERROR

Impact: Other

ODI-10025: Your installation of Oracle Data Integrator is corrupted.

Cause: The technology description file is missing.

Action: Reinstall Oracle Data Integrator.
Level: 32

Type: ERROR

Impact: Other

ODI-10026: Error while testing the Master Repository technology.

Cause: Error occurred while testing the Master Repository technology.

Action: Check parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10027: The import is canceled because at least one object is locked by another user.

Cause: At least one object was locked by another user.

Action: Check objects' locks.
Level: 32

Type: ERROR

Impact: Other

ODI-10028: It is forbidden to import a log into a repository having the same ID.

Cause: The log had the same ID as repository.

Action: Check log and/or repository id.
Level: 32

Type: ERROR

Impact: Other

ODI-10029: Version {0} for object {1} already exists.

Cause: Version already existed.

Action: Choose another version.
Level: 32

Type: ERROR

Impact: Other

ODI-10030: DwgBeanWrapper can only wrap DwgObjects

Cause: DwgBeanWrapper can only wrap DwgObjects

Action: Choose correct type of objects.
Level: 32

Type: ERROR

Impact: Other

ODI-10031: Object {0}: {1} is locked by user {2}

Cause: Object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-10032: You cannot import this object ({0}). A referenced object ({1}) does not exist in the repository.

Cause: A referenced object does not exist in the repository.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10033: You cannot delete this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-10034: The technology hosting your master repository does not support Versioning.

Cause: The technology did not support versioning.

Action: Choose another repository or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-10035: {0} : ''{1}'' (with global id: {5} and internal id: {6}) violates alternate key constraint {2} {3} for values {4}

Cause: Object violated alternate key constraint.

Action: Check object properties and constraint's values.
Level: 32

Type: ERROR

Impact: Other

ODI-10036: Importing object {0} : {1} (with global id: {2} and internal id: {3}) failed.

Cause: Import failed.

Action: Check import file and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10037: Import-replace for this node is supported for action groups only. The import file is invalid.

Cause: Import-replace for this node was supported for action groups only.

Action: Check import file.
Level: 32

Type: ERROR

Impact: Other

ODI-10038: The interface you are trying to use ({0}) is related to a logical schema ({1}) that no longer exists.

Cause: Logical schema was not found.

Action: Check interface.
Level: 32

Type: ERROR

Impact: Other

ODI-10039: Bad ID for an object representer

Cause: Bad ID for an object representer

Action: Check object`s ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10040: Cannot create directory

Cause: Directory could not be created.

Action: Check directory path/name.
Level: 32

Type: ERROR

Impact: File

ODI-10041: Oracle Data Integrator Remote Object (SnpRemoteObject) must inherit from SnpsFunction.

Cause: Oracle Data Integrator Remote Object (SnpRemoteObject) did not inherit from SnpsFunction.

Action: Use SnpsFunction as parent.
Level: 32

Type: ERROR

Impact: Other

ODI-10042: SnpsQuery must be connected prior to execution

Cause: SnpsQuery was not connected.

Action: Set a connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10043: Security token is a mandatory parameter

Cause: Security token was not specified.

Action: Check security parameters.
Level: 32

Type: ERROR

Impact: Security

ODI-10044: Unable to save the interface. Maximum number of source datastores exceeded.

Cause: Maximum number of source datastores was exceeded.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10045: a2.getCargo() not instance of SAPSegment

Cause: a2.getCargo() not instance of SAPSegment

Action: Check SAP Tree.
Level: 32

Type: ERROR

Impact: Other

ODI-10046: No IDoc.

Cause: Missed IDoc.

Action: Check IDoc.
Level: 32

Type: ERROR

Impact: Other

ODI-10047: Repository is not a development work repository

Cause: Repository was not a development work repository.

Action: Choose development work repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10048: No work repository found.

Cause: No work repository was found.

Action: Check your connection settings or database.
Level: 32

Type: ERROR

Impact: Other

ODI-10049: Missing parameter

Cause: Parameter was missing.

Action: Check all parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10050: Missing parameter at: {0} SQL: {1}

Cause: Parameter was missing.

Action: Check all parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-10051: Some objects cannot be exported because they do not exist in the repository: {0} {1}

Cause: Objects did not exist in the repository.

Action: Check objects state.
Level: 32

Type: ERROR

Impact: Other

ODI-10052: A problem occurred in your repository.

Cause: A problem occurred in your repository.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-10053: Problem retrieving JCOFunction object. {0}

Cause: Problem occurred retrieving JCOFunction object.

Action: Check JCO Function object.
Level: 32

Type: ERROR

Impact: Other

ODI-10054: Unable to find the XML file corresponding to your technology.

Cause: XML file corresponding to your technology was not found.

Action: Check technology and/or XML file for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-10055: This ID is already in use in the repository

Cause: This ID was already in use in the repository.

Action: Change ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10056: This repository ID already exists. This repository cannot be created.

Cause: Repository ID already existed.

Action: Change repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10057: Unrecognized export type.

Cause: Export type was unrecognized.

Action: Check export type.
Level: 32

Type: ERROR

Impact: Other

ODI-10058: You are trying to import objects from a master repository of an older version into {0} version. This action is forbidden. Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.

Cause: You tried to import objects from a master repository of an older version.

Action: Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.
Level: 32

Type: ERROR

Impact: Other

ODI-10059: Repository is null

Cause: Repository was null.

Action: Check repository.
Level: 32

Type: ERROR

Impact: Other

ODI-10060: Saputil is mandatory.

Cause: Saputil was mandatory.

Action: Check Saputil
Level: 32

Type: ERROR

Impact: Other

ODI-10061: Empty XML Character Set

Cause: XML Character Set was empty.

Action: Fill XML Character Set.
Level: 32

Type: ERROR

Impact: Other

ODI-10062: Unable to find license key {0}. An exception {1} occurred with message: {2}

Cause: An exception occurred.

Action: Check license key.
Level: 32

Type: ERROR

Impact: Other

ODI-10063: Unable to check the license key. An exception {0} occurred with message: {1}

Cause: An exception occurred.

Action: Check license key.
Level: 32

Type: ERROR

Impact: Other

ODI-10064: The interface must have a JMS datastore as a source or target. Another license is required otherwise.

Cause: The interface must have a JMS datastore as a source or target.

Action: Check datastore type and/or license.
Level: 32

Type: ERROR

Impact: Other

ODI-10065: You license does not include these features. Please contact your reseller.

Cause: You license does not include these features.

Action: Please contact your reseller.
Level: 32

Type: ERROR

Impact: Other

ODI-10066: The interface is using a Datastore defined in Model "{0}" which is linked to a logical schema "{1}" that no longer exists.

Cause: Logical schema was not found.

Action: Correct interface.
Level: 32

Type: ERROR

Impact: Other

ODI-10067: Target file already exists.

Cause: Target file already existed.

Action: Choose another target file name.
Level: 32

Type: ERROR

Impact: File

ODI-10068: SnpsConnection: Current Isolation level: {0}. The new Isolation level: {1}, not supported

Cause: Isolation level not supported.

Action: Check isolation level.
Level: 32

Type: ERROR

Impact: Other

ODI-10069: Unsupported XML Character Set: {0}

Cause: Unsupported XML Character Set.

Action: Check XML charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10070: Cannot delete this object. It is being edited or viewed

Cause: Object was being edited or viewed.

Action: Stop edit or view object and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10071: Cannot delete this object

Cause: Could not delete this object.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10073: A repository already exists on this data server

Cause: A repository already existed on this data server.

Action: Choose another data server.
Level: 32

Type: ERROR

Impact: Other

ODI-10074: An object with the wrong type was given to an object representative

Cause: An object with the wrong type was given to an object representative

Action: Check object type.
Level: 32

Type: ERROR

Impact: Other

ODI-10075: An object is in an unidentified state {0}

Cause: An object is in an unidentified state.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10076: A collection object is the wrong class

Cause: A collection object is the wrong class.

Action: Check collection object's class
Level: 32

Type: ERROR

Impact: Other

ODI-10077: Undefined action performed on an object: {0}

Cause: An undefined action was performed on an object.

Action: Check action and object.
Level: 32

Type: ERROR

Impact: Other

ODI-10078: An object will be in an unidentified state (it is in the state "{0}" and "{1}" is currently being performed on it)

Cause: An object would have been in an unidentified state.

Action: Check object state.
Level: 32

Type: ERROR

Impact: Other

ODI-10080: Incorrect License ....

Cause: Incorrect License.

Action: Contact your seller.
Level: 32

Type: ERROR

Impact: Other

ODI-10081: You are not authorized to Insert the Object: {0}: {1} / {2}

Cause: You were not authorized to Insert the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10082: You are not authorized to View the Object: {0}: {1}

Cause: You were not authorized to View the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10083: You are not authorized to Delete the Object: {0}: {1} / {2}

Cause: You were not authorized to Delete the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10084: You are not authorized to Edit the Object: {0}: {1} / {2}

Cause: You were not authorized to Edit the Object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10085: You cannot consult this object

Cause: You could not consult this object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10086: You cannot edit this object

Cause: You could not edit this object.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10087: You can only give Supervisor Access Privileges if you are a Supervisor.

Cause: You could only give Supervisor Access Privileges if you are a Supervisor.

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10088: Empty Java Character Set.

Cause: Java Character Set was empty.

Action: Fill Java charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10089: You cannot modify another user''s password

Cause: You cannot modify another user''s password

Action: Login with user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-10090: Object {0} {1} is referenced by: {2}. Cannot remove.

Cause: Object was referenced by another one.

Action: Check object''s references.
Level: 32

Type: ERROR

Impact: Other

ODI-10091: not connected

Cause: not connected

Action: Check connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10092: Some objects cannot be exported. They do not exist in the repository.

Cause: Objects did not exist in the repository.

Action: Check objects'' state.
Level: 32

Type: ERROR

Impact: Other

ODI-10093: You are importing an object from another repository with the same identifier. It is forbidden.

Cause: You tried to import an object from another repository with the same identifier.

Action: Change repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-10094: Problem while computing new name.

Cause: A problem occurred while computing new name.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10095: Exception while getting the children list

Cause: Exception while getting the children list.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-10096: Error while parsing fields

Cause: Error occurred while parsing fields.

Action: Check fields value.
Level: 32

Type: ERROR

Impact: Other

ODI-10097: Impossible to find text with ID {0} in text list.

Cause: Text was not found.

Action: Check text ID
Level: 32

Type: ERROR

Impact: Other

ODI-10098: No connection available. Check connection parameters.

Cause: No connection was available.

Action: Check connection parameters.
Level: 32

Type: ERROR

Impact: Network

ODI-10099: Object cannot be exported because the file with name {0} could not be created.

Cause: Object could not be exported because the file could not be created.

Action: Check your system rights to write files and file name.
Level: 32

Type: ERROR

Impact: Other

ODI-10100: Empty XML Version

Cause: XML version was empty.

Action: Fill XML Version.
Level: 32

Type: ERROR

Impact: Other

ODI-10101: Invalid XML Version: {0}

Cause: XML Version was invalid.

Action: Check XML version.
Level: 32

Type: ERROR

Impact: Other

ODI-10102: Alias with the name {0} already exists.

Cause: Alias already exists.

Action: Change alias.
Level: 32

Type: ERROR

Impact: Other

ODI-10103: Alias with the name {0} does not exist.

Cause: Alias doesn't exit.

Action: Check alias name ant try again.
Level: 32

Type: Error

Impact: Other

ODI-10104: File {0} is not a Smart Export file and cannot be imported by Smart Import.

Cause: Smart Export file not specified for Smart Import.

Action: Specify a Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10105: Smart Import file name cannot be null.

Cause: Smart Export file name not specified for Smart Import.

Action: Specify a Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10106: Smart Import response file name cannot be null.

Cause: Smart import response file name not specified for Smart Import.

Action: Specify a Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10107: Smart Import file {0} not found.

Cause: File does not exist.

Action: Specify an existing Smart Export file for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10108: Smart Import response file {0} not found.

Cause: Response file does not exist.

Action: Specify an existing Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10109: File {0} is not a valid Smart Import Response file.

Cause: File is not a valid Smart Import response.

Action: Specify an existing Smart Import response file.
Level: 32

Type: ERROR

Impact: Other

ODI-10110: {0} with the same {1} exists.

Cause: An object with the same alternative key value(s) exists.

Action: Change the alternative key value to be unique.
Level: 32

Type: ERROR

Impact: Other

ODI-10111: {0} <{1}> referenced by {2} <{3}> is missing.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10112: Project code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing project code.

Action: Determine whether the change to project code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10113: {0} with {1} <{2}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10114: {0} with {1} id <{2}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10115: {0} with the same name <{1}> already exists.

Cause: A different object with the same name already exists.

Action: Either change the name of the object being imported or use match by name to match to the already existing object with the same name.
Level: 32

Type: WARNING

Impact: Other

ODI-10116: Model code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing model code.

Action: Determine whether the change to model code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10117: Sub-model code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing sub-model code.

Action: Determine whether the change to sub-model code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10118: A different Physical Schema is already set as the default physical schema for the same data server.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-10119: A different Context is already set as the default Context.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-10120: Context code will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing context code.

Action: Determine whether the change to context code is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10121: Logical schema name will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing logical schema name.

Action: Determine whether the change to logical schema name is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10122: Logical agent name will be changed from <{0}> to <{1}>.

Cause: The import will make a change to an existing logical agent name.

Action: Determine whether the change to logical agent name is desired or not.
Level: 32

Type: WARNING

Impact: Other

ODI-10123: {0} with {1} <{2}> and {3} <{4}> does not exist.

Cause: A referenced object does not exist.

Action: Either import the missing object or change to reference a different object.
Level: 32

Type: WARNING

Impact: Other

ODI-10124: Smart import of file {0} cannot be run due to unfixed critical issues.

Cause: Critical issues exist for objects in the Smart Import.

Action: A fix must be provided for all critical issues before the Smart Import can be run.
Level: 32

Type: ERROR

Impact: Other

ODI-10125: Smart Export file name cannot be null.

Cause: Smart Export file name not specified for Smart Export.

Action: Specify a Smart Export file via Smart Export.
Level: 32

Type: ERROR

Impact: Other

ODI-10126: File {0} already exists.

Cause: The file already exists.

Action: Specify another file name.
Level: 32

Type: ERROR

Impact: Other

ODI-10127: Column position {0} is being used by another object <{1}>.

Cause: The position value is already in use.

Action: Specify a unique position value.
Level: 32

Type: ERROR

Impact: Other

ODI-10128: Multiple primary keys found. Only one primary key can be defined per datastore.

Cause: Multiple primary keys defined.

Action: Delete or match primary keys so that only one is defined.
Level: 32

Type: ERROR

Impact: Other

ODI-10129: Object with id {0} and type {1} is not a smart exportable object.

Cause: Smart Export does not support the type of object specified.

Action: Do not export this object.
Level: 32

Type: ERROR

Impact: Other

ODI-10130: Smart Import Response file {0} is not valid for Smart Export file {1}.

Cause: Smart Import Response file was not generated for the Smart Export file being imported.

Action: Specify a Smart Import response file that belongs to the Smart Export file being imported.
Level: 32

Type: ERROR

Impact: Other

ODI-10131: Entity of type {0} cannot be merged.

Cause: Wrong entity type.

Action: Check entity type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10132: Entity of type {0} cannot be removed.

Cause: Wrong entity type.

Action: Check entity type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10133: Cannot create a transaction against the extended persistent context [{0}].

Cause: Another persistence context is already bound to the current thread.

Action: Unbound persistence context from current thread.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10134: You don't have READ permission on at least one object from the collection/list.

Cause: Insufficient level of permissions.

Action: Check your permissions
Level: 32

Type: ERROR

Impact: Security

ODI-10135: Max value ({1}) reached for sequence {0} and reset is not allowed.

Cause: Reset is not allowed.

Action: Check configuration of sequence behaviour.
Level: 32

Type: ERROR

Impact: Other

ODI-10136: Illegal transaction state: transaction synchronization is active but entity manager is not synchronized within the transaction.

Cause: Entity manager is not synchronized within the transaction.

Action: Synchronize entity manager and try again.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10137: Your program needs to set authentication first.

Cause: There is no authentication set.

Action: Set authentication via odiInstance.getSecurityManager().setGlobalAuthentication(.) or odiInstance.getSecurityManager().setCurrentThreadAuthentication(.), see the SecurityManager API for more detail.
Level: 32

Type: ERROR

Impact: Security

ODI-10138: Unable to create DwgConnectConnection to {0} repository.

Cause: Exception during connection.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10139: {0} must not be null or empty.

Cause: Parameter is null or empty.

Action: Check parameter name.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10140: {0} must be greater or equal 0.

Cause: Parameter is negative.

Action: Check parameter value.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10141: Unable to create datasource provider from class [{0}].

Cause: Exception during creation.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10142: Active transaction is required to use the method {0} on the TransactionalOdiEntityManager.

Cause: Transaction isn't active.

Action: Check transaction state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10143: Error while accessing the {0} repository.

Cause: Network problems.

Action: Check the network connection and the database status.
Level: 32

Type: ERROR

Impact: Network

ODI-10144: OdiInstance is closed.

Cause: OdiInstance is closed.

Action: Check OdiInstance status.
Level: 32

Type: ERROR

Impact: Other

ODI-10145: Limited persistence support.

Cause: Limited persistence support.

Action: Check OdiInstance configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10146: Cannot create JDBC DataSource for this type of DataServer.

Cause: Invalid connection provider.

Action: Check connection provider.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10147: Repository type mismatches.

Cause: Wrong repository type.

Action: Check repository type.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10148: Repository is in error install/upgrade state and needs to be repaired. Connection has been disabled.

Cause: Repository install/upgrade did not complete successfully.

Action: Check install/upgrade log files and/or ODI user documentation for information on reparation process.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10149: Local Repository table is empty.

Cause: Local Repository table is empty.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10150: Work repository with ID {0} is not bound to master: Definition in master ID:{0}, Name:{1}, Timestamp:{2} Definition in work ID:{3}, Name:{4}, Timestamp:{5}.

Cause: Work repository with ID is not bound to master repository.

Action: Check work and master repositories configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10151: Unable to get ID for entity {0}.

Cause: Wrong entity ID.

Action: Check entity properties.
Level: 32

Type: ERROR

Impact: Security

ODI-10152: I_OBJECTS for entity class {0} is not found.

Cause: Entity type is not mapped to I_OBJECTS.

Action: Check entity class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10153: {0} is denied.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10154: {0} is denied for {1}.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10155: You don't have {0} permission on at least one object from the collection/list.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10156: Impossible to connect to JPS MBean Server.

Cause: Exception during connection.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10157: {0}: must call preWebLogic() before postWebLogic().

Cause: Wrong API usage.

Action: Call preWebLogic() before postWebLogic().
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10158: The credential with map name {0} and key {1} already exists.

Cause: Wrong credential.

Action: Check credential configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10159: The user {0} hasn't required CONNECT profile.

Cause: The user hasn't required profile.

Action: Grant the user CONNECT profile first.
Level: 32

Type: ERROR

Impact: Security

ODI-10160: Unable to load user.

Cause: Exception during user loading.

Action: Check repository connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10161: Trying to create authentication with Subject parameter which should be applicable when OPSS authentication is used, but ODI shows it is using ODI internal authentication.

Cause: ODI internal authentication is used instead of OPSS authentication.

Action: Check authentication type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10162: This OPSS user ''{0}'' is not registered to Oracle Data Integrator.

Cause: The user is not registered to ODI.

Action: Check user name.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10163: This OPSS user ''{0}'' has different GUID than the one found in Oracle Data Integrator repository.

Cause: OPSS user differs from ODI user in GUID.

Action: Check user GUID.
Level: 32

Type: ERROR

Impact: Security

ODI-10164: Only supervisor user can invoke this API.

Cause: Insufficient level of permissions.

Action: Check user role.
Level: 32

Type: ERROR

Impact: Security

ODI-10165: The RunAsUser {0} is not a valid user from external user identity store.

Cause: User isn't valid.

Action: Check user.
Level: 32

Type: ERROR

Impact: Security

ODI-10166: The RunAsUser: {0} has different GUID in ODI repository and external user identity store.

Cause: User from external user identity store differs from ODI user in GUID.

Action: Check user.
Level: 32

Type: ERROR

Impact: Security

ODI-10167: Authentication is missing.

Cause: Authentication is missing.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10168: There is already an Authentication bound to this thread.

Cause: There is already an Authentication bound to this thread.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10169: Trying to set authentication object which is not created by this security manager.

Cause: Authentication object isn't created by this security manager.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10170: There is currently no Authentication bound to this thread.

Cause: There is currently no Authentication bound to this thread.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10171: There is already an Authentication bound as global Authentication.

Cause: There is already an Authentication bound as global Authentication.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10172: There is currently no global Authentication bound to this SecurityManager.

Cause: There is currently no global Authentication bound to this SecurityManager.

Action: Check authentication configuration.
Level: 32

Type: ERROR

Impact: Security

ODI-10173: You are not authorized to change the password for external user ''{0}''.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10174: You are not authorized to change the password for user ''{0}''.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10175: You are not authorized to change the password for external user.

Cause: Insufficient level of permissions.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10176: Authentication is needed to change password.

Cause: Authentication is missed.

Action: Authenticate first.
Level: 32

Type: ERROR

Impact: Security

ODI-10177: ODI was not able to load the jdbc driver class "{0}" provided on {1}.

Cause: Wrong jdbc driver class.

Action: Check that the driver class name is correct and that this driver is available to ODI classloader.
Level: 32

Type: ERROR

Impact: Other

ODI-10178: The jdbc URL "{1}" was not accepted by the jdbc driver class "{0}" provided on {2}.

Cause: Insufficient jdbc URL.

Action: Check that the jdbc URL and the driver class name are matching.
Level: 32

Type: ERROR

Impact: Other

ODI-10179: Client requires a repository with version {0} but the repository version found is {1}.

Cause: Insufficient repository version.

Action: Check repository configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-10180: ODI was not able to load the jdbc driver class {0} specified in ODI topology for work repository {1}.

Cause: Wrong jdbc driver class.

Action: Check that the driver class name is correct and that this driver is available to ODI classloader. If the driver class name is incorrect please connect to ODI topology to fix it.
Level: 32

Type: ERROR

Impact: Other

ODI-10181: Uncategorized configuration exception.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10182: Uncategorized exception during repository access.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10183: {0} is an invalid finder class.

Cause: Wrong finder class.

Action: Check finder class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10184: Could not get ESS {0}.

Cause: Exception during session retrieving.

Action: Check configuration and try again.
Level: 32

Type: ERROR

Impact: Session

ODI-10185: Operation is not granted.

Cause: Current level of permission is not sufficient.

Action: Check your permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10186: User {0} is inactive.

Cause: There is no GUID defined for this User in ODI repository

Action: Check user GUID.
Level: 32

Type: ERROR

Impact: Security

ODI-10187: The authentication API is used in wrong way.

Cause: The authentication API is used in wrong way.

Action: Check usage of API.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10188: Error while login from OPSS.

Cause: Exception was thrown during login process.

Action: Make sure OPSS is configured correctly for this installation.
Level: 32

Type: ERROR

Impact: Other

ODI-10189: The password violates the following rule: "Password policy {0}". Select another password.

Cause: Weak password

Action: Check password policy and correct password.
Level: 32

Type: ERROR

Impact: Security

ODI-10190: The user {0} has its account expired.

Cause: Account expired

Action: Request supervisor for account unlocking.
Level: 32

Type: ERROR

Impact: Security

ODI-10191: Unable to create datasource provider.

Cause: Exception during creation.

Action: Check configuration.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10192: Unable to retrieve user GUID.

Cause: Exception during GUID retrieving.

Action: Check repository connection.
Level: 32

Type: ERROR

Impact: Other

ODI-10193: Unexpected null value in port.

Cause: JPS port value is null.

Action: Check JPS configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10194: Uncategorized security exception.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10195: CsfAccessor is only available for CsfPasswordStorageConfiguration

Cause: Password storage configuration is internal.

Action: Check storage configuration.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10196: Error while accessing the repository.

Cause: Network problems.

Action: Check the network connection and the database status.
Level: 32

Type: ERROR

Impact: Network

ODI-10197: Instance is not connected to a work repository

Cause: Work datasource is null.

Action: Check work datasource.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10198: Context with code '{0}' wasn''t found.

Cause: Context wasn't found.

Action: Check context code.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10199: Incorrect ODI username or password.

Cause: Incorrect ODI username or password.

Action: Check username and password.
Level: 32

Type: ERROR

Impact: Security

ODI-10200: Work repository {0} wasn''t found.

Cause: Wrong repository name or repository isn't defined.

Action: Check repository name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10201: The user {0} has its password expired.

Cause: Account expired

Action: Request supervisor for changing password.
Level: 32

Type: ERROR

Impact: Security

ODI-10202: Supervisor privilege is required to setup repository.

Cause: Insufficient level of permissions.

Action: User supervisor account for this operation.
Level: 32

Type: ERROR

Impact: Security

ODI-10203: Transaction state is illegal.

Cause: Transaction state is illegal.

Action: Check transaction state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10204: Inappropriate usage of a ODI transaction API.

Cause: Inappropriate usage of a ODI transaction API.

Action: Check ODI transaction API.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10205: Unexpected rollback.

Cause: Attempt to commit a transaction resulted in an unexpected rollback.

Action: Check transaction.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10206: Transaction can't be created.

Cause: Exception was thrown during transaction creation.

Action: Check transaction.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10207: Uncategorized exception during transaction system usage.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10208: Error when changing password for user {0}.

Cause: An unexpected error occurred.

Action: Check exception cause for details.
Level: 32

Type: ERROR

Impact: Other

ODI-10209: Cannot access a closed IOdiEntityManager.

Cause: IOdiEntityManager has been closed.

Action: Check IOdiEntityManager state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-10210: File {0} does not contain any objects to be imported by Smart Import.

Cause: Smart Export file specified for Smart Import is empty.

Action: Specify a Smart Export file with objects for importing via Smart Import.
Level: 32

Type: ERROR

Impact: Other

ODI-10211: Unsupported Java Character Set: {0}

Cause: Unsupported Java Character Set.

Action: Check Java charset.
Level: 32

Type: ERROR

Impact: Other

ODI-10212: Parent object {0}: ''{1}'' already has child {2}: ''{3}''. Technical details: {2} : ''{3}'' (with global id: {7} and internal id: {8}) violates alternate key constraint {4} {5} for values {6}

Cause: Object violated alternate key constraint.

Action: Check object properties and constraint's values.
Level: 32

Type: ERROR

Impact: Other

ODI-10213: Fixed format file field {0} (starts at {1} ends at {2}) has a file position that overlaps with the file position of field {3} (starts at {4} ends at {5}).

Cause: Two fields from a fixed format file have overlapping file positions.

Action: Modify the file positions or remove a field if the overlapping file positions are not correct.
Level: 32

Type: ERROR

Impact: Other

ODI-10214: Fixed format file fields {0} (starts at {1} ends at {2}) and {3} (starts at {4} ends at {5}) have unused file positions between them.

Cause: Two fields from a fixed format file have unused file positions between them.

Action: Modify the file positions if having unused file positions is not correct.
Level: 32

Type: ERROR

Impact: Other

ODI-10215: It is forbidden to import a log into a repository using any other import mode except "Synonym Mode Insert".

Cause: Import mode is not "Synonym Mode Insert".

Action: Correct import mode.
Level: 32

Type: Error

Impact: Other

ODI-10216: Upgrade key cannot be null when importing objects from before ODI 12C.

Cause: Upgrade key is not set for import that must upgrade objects to have global ids.

Action: Specify the upgrade key to be used.
Level: 32

Type: Error

Impact: Other

ODI-10217: Permission check failed for instance object {0}.

Cause: Permission check failed for instance object.

Action: Need to grant initial permission for creator on object.
Level: 32

Type: NOTIFICATION

Impact: Other

ODI-10218: Invalid WAS_HOME ("{0}") set or WebSphere library jar ({1}) not found under WAS_HOME/plugins.

Cause: Wrong WAS_HOME set (or) WebSphere libraries (com.ibm.ws.admin.core.jar, com.ibm.ws.admin.services.jar, com.ibm.ws.runtime.jar) are moved

Action: Check that the environment-variable WAS_HOME is set properly to point to WebSphere Application Server root. Also, ensure the libraries exist under WAS_HOME/plugins.
Level: 32

Type: ERROR

Impact: Other

ODI-10219: ODI Library for WebSphere access ({0}) not found.

Cause: Library could be moved / deleted

Action: Check that the specified library present
Level: 32

Type: ERROR

Impact: Other

ODI-10220: ODI was unable to find the technology "{0}".

Cause: Missing technology.

Action: Check that this technology is defined in the repository. .
Level: 32

Type: ERROR

Impact: Other

ODI-10221: It's taken {0} second to synchronize Snp_Ent_Principal table content.

Cause:

Action:
Level: INFO

Type: NOTIFICATION

Impact: Other

ODI-10222: The compatible Mapping/ReusableMapping {0} can only be modified by 11g SDK.

Cause: An attempt was made to modify compatible Mapping using 12c SDK.

Action: Modify compatible Mapping using 11g Interface SDK.
Level: 32

Type: ERROR

Impact: Other

ODI-10223: A non-legacy compatible import source cannot be imported into a legacy compatible repository.

Cause: An attempt was made to import a non-legacy compatible import source into a legacy compatible repository.

Action: Import a legacy compatible import source or make repository not legacy compatible.
Level: 32

Type: Error

Impact: Other

ODI-10224: You are not authorized to create new user.

Cause: Only SUPERVISOR could create users.

Action: Check permissions.
Level: 32

Type: ERROR

Impact: Security

ODI-10225: Invalid wallet password: A valid password must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.

Cause: Invalid wallet password.

Action: Please choose a valid wallet password accordingly.
Level: 32

Type: ERROR

Impact: Security

ODI-10226: Wallet already exists.

Cause: Try to create a wallet which already exists.

Action: Please stop creating a wallet. Instead use the existing one.
Level: 32

Type: ERROR

Impact: Security

ODI-10227: Wallet new password is same as old password.

Cause: You provide a new wallet password which is the same as the old one.

Action: Please choose different wallet password than the old one.
Level: 32

Type: ERROR

Impact: Security

ODI-10228: Repository with id ''{0}'' or with name ''{1}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same name or id.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10229: Repository with id ''{0}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same id.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10230: Repository with name ''{0}'' has been already used in your master repository.

Cause: Master repository has already work repository with the same name.

Action: Check your master repository and work repository.
Level: 32

Type: ERROR

Impact: Configuration

ODI-10231: Interface {0} cannot be imported because source temporary interface / mapping {1} is not found.

Cause: An attempt was made to import an interface with a source temporary interface / mapping that cannot be found in the import source or target repository.

Action: Import the missing source temporary interface / mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-10232: The password violates the following rule: "New password must be different from old one". Select another password.

Cause: Weak password

Action: Check password policy and correct password.
Level: 32

Type: ERROR

Impact: Security

ODI-10234: Object cannot be imported since it contains non XML files

Cause: ZipFolder to be imported should not contain non XML files

Action: Check ZipFolder to be imported
Level: 32

Type: ERROR

Impact: Other

ODI-10235: No Importable files found

Cause: None of XML files imported from ZipFolder

Action: Check XML files to be imported from Zip Folder
Level: 32

Type: ERROR

Impact: Other

ODI-10236: Object must be replaced with an object of same KM type

Cause: KM of different type to the existing KM was selected for import replace.

Action: Import Replace KM with existing KM type
Level: 32

Type: ERROR

Impact: Other

ODI-10237: Object not replaced

Cause: A KM was selected for the Import Replace with a different type to the current KM.

Action: Select a KM of the same type for import replace.
Level: 32

Type: WARNING

Impact: Other

ODI-10238: Object must be replaced with an object of same type

Cause: Different ODI object is used to Import Replace KM

Action: Import Replace KM with Same type
Level: 32

Type: ERROR

Impact: Other

ODI-10239: Importing file "{0}"...

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Files

ODI-10240: Updating dataservers...

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Topology

ODI-10241: Removing Error Tables for Physical Schema with id '{0}'

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Topology

ODI-10242: Removing Error Table "{0}"

Cause:

Action:
Level: 32

Type: NOTIFICATION

Impact: Topology

ODI-10243: Cannot import an export file with parents using regular import and INSERT_UPATE mode. Use smart import instead.

Cause: An attempt was made to import an export file created with parent objects using regular import and INSERT_UPATE mode. This would cause all other objects under the parent objects and not in the import file to be deleted.

Action: Use smart import to import an export file created with parent objects when INSERT_UPDATE functionality is needed.
Level: 32

Type: ERROR

Impact: Other

ODI-10244: Cannot import {0} {1} (with global id: {2} and internal id: {3}) because referenced {4} with global id {5} does not exist.

Cause: The referenced object for a foreign key cannot be found in order to set the reference and a missing reference cannot be created.

Action: Import the missing referenced object before importing the referencing object.
Level: 32

Type: ERROR

Impact: Other

ODI-10245: Cannot import {0} {1} (with global id: {2} and internal id: {3}) belonging to {4} {5} (with global id: {6} and internal id: {7}) because its referenced object is not found in the target repository.

Cause: The object was imported in a SYNONYM UPDATE mode and the referenced object was not found in the repository.

Action: Change the import mode to INSERT_UPDATE or import the file twice first in INSERT MODE and then in UPDATE mode.
Level: 32

Type: ERROR

Impact: Other

ODI-10246: No Exportable objects found in the repository.

Cause: No objects are present in the repository for export

Action: Create repository objects
Level: 32

Type: ERROR

Impact: Other

ODI-10247: Specified project {0} does not exist in the repository.

Cause: The repository did not contain the specified project.

Action: Choose another project or create the project with the specified name.
Level: 32

Type: ERROR

Impact: Other

ODI-10248: {0} : Not an ODI special driver.

Cause: Invalid Special driver.

Action: Check that this technology is part of the special driver list.
Level: 32

Type: ERROR

Impact: Other

ODI-13700: Unable to set the role OWB_USER for this user.

Cause: An attempt was made to set the role OWB_USER for the connected user.

Action: Check that the role exists and the connected user is an OWB user.
Level: 1

Type: ERROR

Impact: Other

ODI-13701: Unable to set the workspace {0} for this user.

Cause: An attempt was made to select the OWB workspace for the connected user.

Action: Check that the workspace exists and the connected user has got privilege to access it.
Level: 1

Type: ERROR

Impact: Other

ODI-13702: Unexpected error when connecting to OWB workspace {0}.

Cause: An unexpected error occurred when connecting to workspace.

Action: Verify that the Owb repository is up and running.
Level: 1

Type: ERROR

Impact: Other

ODI-13703: Unexpected error when locating object {0} in OWB workspace {1}.

Cause: An unexpected error occurred when locating an object in a workspace

Action: Verify that the Owb repository is up and running and the object exists.
Level: 1

Type: ERROR

Impact: Other

ODI-13704: Could not locate the physical schema associated with OWB workspace {0} in context {1}.

Cause: An error occurred when finding the schema related to an OWB workspace in a context.

Action: Verify that the OWB workspace is related to a physical schema in the context.
Level: 1

Type: ERROR

Impact: Other

ODI-13800: Cannot locate the monitor configuration file: {0} using JVM argument: {1}={2} or the environment variable: {3}={4}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13801: Cannot locate the monitor configuration file at: {0}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13802: Cannot access the monitor configuration file: {0}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13803: The contents of the monitor configuration file: {0} are invalid.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13804: The runtime performance monitoring has been turned off due to invalid monitor configuration.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Configuration

ODI-13805: An error occured while updating the monitor status for the Agent:{0}, Master repository external id:{1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13806: An error occurred while starting the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13807: An error occurred while stopping the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13808: An error occurred while starting the request processing monitor for Agent={0}, Master repository external id={1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13809: An error occurred while stopping the request processing monitor for Agent={0}, Master repository external id={1}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13810: An error occurred while starting the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13811: An error occurred while stopping the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13812: An error occurred while starting the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13813: An error occurred while stopping the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13814: An error occurred while starting the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13815: An error occurred while stopping the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13816: An error occurred while starting the Step execution monitor for Agent={0}, Scenario={1}, Step={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13817: An error occurred while stopping the Step execution monitor for Agent={0}, Scenario={1}, Step={2}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13818: An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13819: An unexpected error occurred while updating the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13820: An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13821: An error occurred while registering the Agent Discovery Mbean, mbeanName={0}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13822: An error occurred while de-registering the Agent Discovery Mbean, mbeanName={0}

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-13823: Could not find the Server MBean for server {0} on platform {1}.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-14000: Importing Object

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14001: Importing Profile

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14002: Importing User

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14003: Importing InstObj

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14004: Importing Local Repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14005: Importing Techno

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14006: Importing Data Types

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14007: Importing Data Types Conversions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14008: Importing Language

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14009: Importing Open Tools

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14010: Importing Pwd Policies

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14011: Importing Pwd Rule

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14012: Importing Connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14013: Importing Agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14014: Importing LBAgent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14015: Importing Logical Agent

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14016: Importing Context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14017: Importing Pschema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14018: Importing Lschema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14019: Importing Entity

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14020: Importing Link

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14021: Importing Field

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14022: Importing FieldLook Up

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14023: Importing Look Up

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14024: Importing Look Up Value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14025: Importing Action

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14026: Importing Action Group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14027: Importing Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14028: Importing Solutions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14029: Cleaning connections

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14030: Importing:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other{0}

ODI-14031: Importing Session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14032: Importing Global Sequences

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14033: Importing Global Variables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14034: Importing Global User Functions

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14035: Importing Global Group of States

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14036: Importing Model Folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14037: Importing Models

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14038: Importing Scenario folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14039: Importing Projects

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14040: Importing Scenario

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14041: Importing Folders

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14042: Importing Packages

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14043: Importing Interfaces

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14044: Importing Procedures

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14045: Importing Knowledge Modules

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14046: ODI Master Repository Upgrade: Upgrading Repository Structure...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14047: ODI Master Repository Upgrade: Upgrading Repository Data...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14048: ODI Master Repository Upgrade: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14049: Master repository creation is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14050: ODI Work Repository Attach: Attaching Repository...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14051: ODI Work Repository Attach: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14052: ODI Work Repository Upgrade: Upgrading Repository Structure...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14053: ODI Work Repository Upgrade: Upgrading Repository Data...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14054: ODI Work Repository Upgrade: Done.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14055: Work repository creation is successful.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14056: Importing SubModels

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14057: Importing Tables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14058: End importing {1}. Import time (milliseconds): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14059: End importing {1}. Import time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14060: End importing {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14061: Master repository already up to date nothing to do.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14062: Upgrading master repository from {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14063: Applying DDL from file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14064: Error while applying DDL from file {0}

Cause: Exception during execution of session.

Action: Check session.
Level: 32

Type: ERROR

Impact: Other

ODI-14065: Work repository already up to date. Nothing to do.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Upgrade

ODI-14066: upgrade error while executing {0} params = {1}

Cause: Wrong parameters at Sql query.

Action: Check parameters.
Level: 32

Type: ERROR

Impact: Upgrade

ODI-14067: Exporting {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14068: End exporting {1}. Export time (milliseconds): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14069: End exporting {1}. Export time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14070: Import failed. The parent object was not found in the repository.

Cause: The object was imported in a SYNONYM mode and the parent object was not found in the repository.

Action: Change the import mode or restore the parent object in the repository
Level: 32

Type: ERROR

Impact: Other

ODI-14071: Getting Dependencies

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14072: End getting dependencies. Time (milliseconds): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14073: End getting dependencies. Time (hh:mm:ss): {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14074: Parent folder already has the release tag set.

Cause: Setting the release tag when the parent already has the release tag set.

Action: Set the release tag in parent.
Level: 32

Type: ERROR

Impact: Other

ODI-14075: Seed data for property missing.

Cause: Seed data for property {0} is missing.

Action: Contact Oracle Support Services
Level: 32

Type: ERROR

Impact: Other

ODI-14077: Importing Mappings/Reusable Mappings

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14078: Importing Mapping Component Types

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14079: Importing Enterprise Scheduler

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14080: Importing Enterprise Principals

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14081: User Function syntax is not unique.

Cause: Work repository already has User Function with the same syntax.

Action: Check your user function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-14082: Folder or sub-folder name is not unique.

Cause: Duplicate folder name. Folder with the same name already exists in this project/folder.

Action: Choose another folder name.
Level: 32

Type: ERROR

Impact: Other

ODI-14083: Profile name is not unique.

Cause: Profile with the same name already exists.

Action: Check your profile name.
Level: 32

Type: ERROR

Impact: Other

ODI-14084: Diagram name is not unique.

Cause: Diagram with the same name already exists.

Action: Check your diagram name.
Level: 32

Type: ERROR

Impact: Other

ODI-14085: Object cannot be Imported since it contains non XML file

Cause: Folder to be imported should not contain non XML files

Action: Check Folder to be imported
Level: 32

Type: ERROR

Impact: Other

ODI-14086: Begin importing: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14087: Total Time For Import (before Upgrade of Interfaces) : {0} (milliseconds)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14088: Total Time For Import (before Upgrade of Interfaces) : {0} (hh:mm:ss)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14089: Total Time for Import:{0} (milliseconds)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14090: Total Time for Import: {0} (hh:mm:ss)

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14091: Work repository is already attached to another master repository.

Cause: Attempt to attach already attached work repository was made while work repository can be attached to only one master repository at the moment.

Action: Work repository should be first detached from the master repository it is attached to at the moment.
Level: 32

Type: ERROR

Impact: Other

ODI-14092: Loading Master Repository Info

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14093: Cannot Connect To Master Repository

Cause: Cannot Connect To Master Repository

Action: Check your connection settings or database
Level: 32

Type: ERROR

Impact: Other

ODI-14094: Master Repository Is In Invalid State.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14095: Master Repository Already Up To Date.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14096: Error While Upgrading Master Repository {0}

Cause: Exception caught while upgrading Master Repository

Action: Please check the Logs.
Level: 32

Type: ERROR

Impact: Other

ODI-14097: Importing Technology Seed Data

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14098: Error While Importing Technology Seed Data {0}

Cause: Exception caught while importing technology Seed Data

Action: Please check the logs
Level: 32

Type: ERROR

Impact: Other

ODI-14099: Scanning Export Files

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14100: Loading Technology

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14101: Checking for Pre 4.3.3.2 Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14102: Upgrading To Master Repository Till 4.3.3.2 Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14103: Upgrading Master Repository Post 4.3.3.2 Version

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14104: Reimporting Metadata

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14105: Reimporting Security Seed Data

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14106: Getting Work Repositories

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14107: Found {0} Work Repositories to Upgrade

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14108: Upgrading {0} Work Repository

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14109: Cannot Connect To Work Repository

Cause: Cannot Connect To Work Repository {0}

Action: Check your connection settings or database
Level: 32

Type: ERROR

Impact: Other

ODI-14110: Work Repository {0} Is In Invalid State.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14111: Work Repository Already Up To Date.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14112: Converting All Interface to Mapping

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14113: Work repository is already attached to the master repository.

Cause: Attempt to attach already attached work repository was made.

Action: Please do not attach the work repository again to the master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-14114: Incorrect wallet password.

Cause: Provided wallet password is incorrect.

Action: Please enter correct wallet password.
Level: 32

Type: ERROR

Impact: Security

ODI-14115: Wallet file is not found at specified location : {0}

Cause: Wallet file is not present in $HOME/.odi/oracledi/ewallet directory.

Action: Please check wallet file is present at specified location.
Level: 32

Type: ERROR

Impact: Security

ODI-14116: No registry database provided

Cause: Registry database not provided.

Action: Please provide registry database.
Level: 32

Type: ERROR

Impact: Other

ODI-14117: No repository database in URL: {0}

Cause: Repository database missing from the jdbc url.

Action: Please provide repository database in the jdbc url.
Level: 32

Type: ERROR

Impact: Other

ODI-14118: Not a valid jdbc mysql url: {0}

Cause: Invalid JDBC mysql url

Action: Please provide a valid jdbc url.
Level: 32

Type: ERROR

Impact: Other

ODI-14119: The database you are connecting to, is a more recent than the supported version. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14120: The database you are connecting is not a supported version. refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14121: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 11.2.0.3.0 in 11g. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14122: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.5.3.0. Refer to the certification matrix for supported DB versions

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14123: DB Init Param Prerequisite failure for INNODB_FILE_FORMAT. Its value should be 'Barracuda'.

Cause: INNODB_FILE_FORMAT value is not 'Barracuda'.

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14124: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 5.5.14. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14125: DB Init Param Prerequisite failure for INNODB_FILE_PER_TABLE. Its value should be 'ON'.

Cause: INNODB_FILE_PER_TABLE value is not 'ON'

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14126: DB Init Param Prerequisite failure for INNODB_LARGE_PREFIX. Its value should be 'ON'.

Cause: INNODB_LARGE_PREFIX value is not 'ON'

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14127: DB Init Param Prerequisite failure for log_bin_trust_function_creators. Its value should be 'ON'.

Cause: log_bin_trust_function_creators value is not 'ON'

Action: Refer to the certification matrix for supported DB init parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-14128: The database you are connecting is a CDB which is not supported.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14129: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 12.1.0.1.0 in 12c. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-14130: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to or higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for supported DB versions

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14131: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 2008 R2. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14132: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 9.7 in 9 series and equal to or higher than 10.1 FP2 in 10 series. Refer to the certification matrix for supported DB versions.

Cause: Database version is not supported

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14133: User should have sysdba or dba privilages.

Cause: User does not have sysdba or dba privilages

Action: Grant user sysdba or dba privilages.
Level: 32

Type: ERROR

Impact: Other

ODI-14134: The database you are connecting is with non-AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the database character set.

Cause: The database you are connecting is with non-AL32UTF8 character set

Action: Use AL32UTF8 as the database character set.
Level: 32

Type: ERROR

Impact: Other

ODI-14136: Database does not match the requirement.

Cause: Database validation failed

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14137: Error occurred while validating database {0}.

Cause: Database validation failed

Action: Refer to the certification matrix for supported DB versions.
Level: 32

Type: ERROR

Impact: Other

ODI-14138: Could not perform validation of the database.Please check the database user privileges.

Cause: Database validation failed

Action: Check if database user has sufficient privileges or required table/view/file exist .
Level: 32

Type: NOTIFICATION

Impact: Other

ODI-14139: Encryption Standard is not set in Master Repository.

Cause: Master Repository configured with invalid or no Encryption Standard.

Action: Set the Encryption Standard to be used in the Master Repository, with valid value for algorithm ('AES') and key-length ('128' / '256').
Level: 32

Type: ERROR

Impact: Security

ODI-14140: Master key data is not set in Master Repository

Cause: Master Repository does not have the master key data.

Action: Set the Master key data to be used in the Master Repository.
Level: 32

Type: ERROR

Impact: Security

ODI-14141: The provided key is not matching the key-specification. Key must : be of length 8-100, contain at least one alphabet (lower/uppercase), contain at least one numeric-digit (or) a special-character from: [@ # $ % + / =].

Cause: The provided key is not matching the key-specification.

Action: Provide key that matches the key-specification
Level: 32

Type: ERROR

Impact: Security

ODI-14142: The Security Policy currently in force, does not allow the use of AES-256.

Cause: The Security Policy in force does not allow using AES-256 Encryption Standard.

Action: To use AES-256, please replace the security policy files in JRE_HOME/lib/security, with Unlimited Strength Policy Files available at Java SE downloads at http://www.oracle.com/technetwork/java. Refer Java SE documentation for more information.
Level: 32

Type: ERROR

Impact: Security

ODI-14143: Encryption Standard persisted in master repository is not AES-128 or AES-256.

Cause: The Encryption Standard configured in the repository is not supported.

Action: Edit the master repository configuration to set the Encryption Standard as AES-128 or AES-256.
Level: 32

Type: ERROR

Impact: Security

ODI-14144: An Error occurred while parsing the ODI Tool Command

Cause: An error occurred while parsing the ODI Tool Command text.

Action: Refer to stack trace for more details.
Level: 32

Type: ERROR

Impact: Security

ODI-14145: An Error occurred while setting parameter {0} in ODI Tool Command.

Cause: Unable to set parameter in ODI Tool Command.

Action: Refer to stack trace for more details.
Level: 32

Type: ERROR

Impact: Security

ODI-14146: Incorrect Export Key

Cause: The Export Key provided is incorrect for the import source

Action: Provide a valid Export Key that was used during Export of object
Level: 32

Type: ERROR

Impact: Security

ODI-14147: An error occurred while migrating cipher text in object {0} - '{1}' (with Internal ID: {2} and Global ID: {3})

Cause: Invalid Cipher content or Invalid Export Key

Action: If exporting, check if the cipher data present in the object is correct. If importing, check if Export Key is correct.
Level: 32

Type: ERROR

Impact: Security

ODI-14148: An Error occurred while creating Cipher for migration.

Cause: An error occurred while creating ODI Cipher.

Action: Refer to stack trace for more details
Level: 32

Type: ERROR

Impact: Security

ODI-14149: Invalid Encoder/Decoder for Cipher Text Migration.

Cause: The ODI Encoder/Decoder is invalid.

Action: Create valid Encoder/Decoder for Cipher Text Migration.
Level: 32

Type: ERROR

Impact: Security

ODI-14150: An Error occurred while migrating password cipher text

Cause: An error occurred while migrating the password cipher text

Action: Refer to stack trace for more details
Level: 32

Type: ERROR

Impact: Security

ODI-14151: An error occurred while retrieving parameters from ODI Tool Command.

Cause: Invalid ODI Tool Command.

Action: Check ODI Tool Command text.
Level: 32

Type: ERROR

Impact: Security

ODI-14152: Package name is not unique.

Cause: Duplicate package name. Package with the same name already exists in this folder.

Action: Choose another package name.
Level: 32

Type: ERROR

Impact: Other

ODI-14153: Procedure name is not unique.

Cause: Duplicate procedure name. Procedure with the same name already exists in this folder.

Action: Choose another procedure name.
Level: 32

Type: ERROR

Impact: Other

ODI-14154: Context name is not unique.

Cause: Context with the same name already exists.

Action: Check your context name.
Level: 32

Type: ERROR

Impact: Other

ODI-14155: Context code is not unique.

Cause: Context with the same code already exists.

Action: Check your context code.
Level: 32

Type: ERROR

Impact: Other

ODI-14156: KM name is not unique.

Cause: Duplicate KM name. KM with the same name already exists.

Action: Choose another KM name.
Level: 32

Type: ERROR

Impact: Other

ODI-14157: Procedure option name is not unique.

Cause: Duplicate procedure option name. Procedure option with the same name already exists.

Action: Choose another procedure option name.
Level: 32

Type: ERROR

Impact: Other

ODI-14158: A Supervisor user can be updated only by another Supervisor user.

Cause: The logged-in user is not a Supervisor user, but trying to update another Supervisor user.

Action: Login as a user with right privileges.
Level: 32

Type: ERROR

Impact: Security

ODI-14159: An error occurred while validating the Export Key.

Cause: An error occurred while validating the export key

Action: Please check the Logs
Level: 32

Type: ERROR

Impact: Security

ODI-14160: Skipping Data migration on IP Text {0} . Failed with Exception : {1} . Please fix manually.

Cause: An error occurred while migrating the password cipher text

Action: Refer to Error Message for more details
Level: 32

Type: ERROR

Impact: Security

ODI-14161: Duplicate name objects are found in the repository. Please check the upgrade log file.

Cause: Some objects with same names are under same parents

Action: Check the log file for the duplicate name objects. Remove them before upgrade
Level: 32

Type: ERROR

Impact: Other

ODI-14162: User cannot login ODI with blank password. Please contact SUPERVISOR to reset the password.

Cause: User cannot login ODI with blank password. Please contact SUPERVISOR to reset the password.

Action: Please contact SUPERVISOR to reset the password.
Level: 32

Type: ERROR

Impact: Security

ODI-14163: User cannot create master repository through import with blank supervisor password.

Cause: User cannot create master repository through import with blank supervisor password.

Action: Please provide valid supervisor password to the API while create master repository thorugh import.
Level: 32

Type: ERROR

Impact: Security

ODI-14164: Work repository name must not be null or empty

Cause: Work repository name is null or empty.

Action: Check Work repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-15000: BSF Not Present

Cause: Bean Scripting Framework manager cannot be found.

Action: Ensure that class org.apache.bsf.BSFManager is available in the classpath.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15001: No End Separator for the following text:

Cause: No end delimiter found for a delimited text in the expression.

Action: Add an end delimiter to the delimited text.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15002: The string to be transformed cannot be null.

Cause: Parsing failed for an expression reference tag.

Action: Fix the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15003: Error during Code Interpretor creation

Cause: Code generator internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15005: The datatype "{0}" does not exist in technology: {1}.

Cause: The datatype for a column is not supported by the technology.

Action: Change the datatype or the technology of the execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15006: The source datatype is null for the column: {0}, and the technology: {1}

Cause: The datatype for a column is null for the technology.

Action: Change the datatype or the technology of the execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15007: Syntax not set for 'Create Table' for the datatype: {0} for the technology: {1}.

Cause: The execution location technology does not have any "Create Table" syntax set up.

Action: Edit the technology definition and add "Create Table" syntax.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15009: No text for the 'Writable Datatype Syntax' for the datatype: {0} in technology: {1}

Cause: The datatype does not have a "Writable Datatype Syntax" property value set up for the execution location technology.

Action: Edit the datatype in the technology to add a "Writable Datatype Syntax".
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15010: No conversion for the datatype {0}, for the source technology {1} and for the target technology {2}

Cause: No conversion is defined for the source technology datatype to the target technology datatype.

Action: Edit the source or target technology datatype to add a conversion from the source to the target datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15011: The variable does not exist in the database.

Cause: A variable is being referenced but it does not exist in the repository.

Action: Create the variable in the repository.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15012: Sequence does not exist in database

Cause: A sequence is referenced but does not exist in the repository.

Action: Create the sequence in the repository.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15013: The table {0} has fatal errors.

Cause: The table cannot be processed.

Action: Check the table for inconsistencies.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15014: The referenced text does not exist in the database.

Cause: The text reference in the expression does not exist in the repository.

Action: Repository corruption has occurred, contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15015: Too much recursion in this text resolution.

Cause: The expression text references other text recursively too many times.

Action: Review the expression and try to simplify.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15016: Commands Undefined.

Cause: KM is missing a block of lines.

Action: Check the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15017: Table not selected (null).

Cause: Target table not found.

Action: Check interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15018: CKM not selected.

Cause: The CKM is not selected for the object.

Action: Select a CKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15019: Missing context

Cause: The context object cannot be found.

Action: Check the context selection.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15020: No JKM available

Cause: JKM has not been set or is not found.

Action: Set a valid JKM for the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15021: Journalizing requires a Primary Key on the Table:

Cause: Journalizing is enabled, but the target table has no primary key.

Action: Add a primary key to the target table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15022: No RKM Set.

Cause: RKM has not been set or is not found.

Action: Set a valid RKM for the object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15023: Cannot perform standard reverse. Choose customized reverse and set RKM.

Cause: Standard reverse engineering is not supported for this object.

Action: Select customized reverse engineering for the object and select an RKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15025: The interface clause text does not exist.

Cause: The interface clause refers to text that does not exist.

Action: Check interface clauses for (join, filter, etc.) for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15026: Interface clauses are missing.

Cause: The code generator cannot find the clause collection for the interface.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15027: Interface source tables are missing.

Cause: The code generator cannot find the source table collection for the interface.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15028: Interface result collection is null.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15029: Interface error clause collection is missing.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15030: Interface is missing the integration work table collection.

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15031: Technology not selected.

Cause: No technology is selected for the interface target execution location.

Action: Check the technology selection for the interface target.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15032: Unknown object in interface source table collection

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15033: The expression: {0} does not have an associated column.

Cause: The expression should represent a column, but no column is found for the name.

Action: Fix the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15034: A scenario with the same name and the same number already exists. Please select other values.

Cause: Cannot create a duplicate scenario with the same name and version number as an existing scenario.

Action: Give the scenario a different name or version.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15036: Scenario''s name and/or number are missing.

Cause: A scenario must have a name and version, but the name or version is missing.

Action: Set values for name and version for the scenario.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15037: The interface {0} has fatal errors.

Cause: The interface has fatal errors.

Action: Check and fix interface issues.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15038: The scenario name substitution pattern {0} is not supported. Please check the user parameter for the scenario naming convention.

Cause: Invalid substitution pattern used for scenario name.

Action: Change the substitution pattern.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15039: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)

Cause: Native sequence was used in a sub-select or derived interface.

Action: Remove the native sequence usage.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15040: Errors detected when building SQL clauses.

Cause: An error occurred when generating code for the SQL clauses.

Action: Fix the interface clauses.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15041: An aggregation function may not be used in a join condition. Please use a separate interface for the aggregation and join the result in this interface.

Cause: An aggregation function was used inside a join condition expression.

Action: Change the join condition to remove the aggregation function.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15042: Unable to regenerate this scenario. It references an package that does not exist.

Cause: The scenario must reference a package, but it doesn't.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15043: Unable to regenerate this scenario from a Runtime repository.

Cause: The scenario must cannot be regenerated from the runtime repository.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15044: Invalid pScenSource type when calling SnpGeneratorSQLCIT.mainGenScenSourceScenario

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15045: Invalid value for KM type.

Cause: An invalid value was specified for the KM type.

Action: Specify a valid value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15046: The column cache is null during code generation.

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15047: The cached column is null in the column cache during code generation.

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15050: Flow Control not possible if no key is declared in your target datastore

Cause: Flow control is enabled for the interface, but the target datastore has no primary key defined.

Action: Define a primary key for the target datastore object, and re-add the target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15051: Missing mapping instance for interface.

Cause: The target column does not have any mapping.

Action: Add a mapping expression for the target column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15052: The interface is missing a dataset.

Cause: There is no dataset for the interface source.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15054: Scenario generation error: Cannot regenerate the scenario. The physical mapping design used to generated the scenario is not found.

Cause: The physical mapping design used to generated the scenario is not found.

Action: Choose to create or replace the scenario.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15055: Character '']'' missing in: {0}.

Cause: A bracketed tag inside a KM line is missing a closing bracket ("]") character.

Action: Fix the KM line.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15057: Non-ordered outer join not supported for technology.

Cause: Non-ordered outer join syntax disabled for technology.

Action: Correct join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15058: Variable scenario generation error: Logical schema is required.

Cause: Variable scenario cannot be generated if logical schema is not set.

Action: Set the logical schema.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15059: I_TXT is mandatory.

Cause: A call was made to SnpTxtCachedHashMap.getInstance, but the pITxt parameter was null.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15060: The JKM line {0} uses an unsupported execution channel: {1}

Cause: A line in the JKM uses an execution channel that is not supported.

Action: Change the line in the JKM to use a supported channel.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15061: The JKM line {0} uses an unsupported commit type: {1}

Cause: A line in the JKM uses a commit type that is not supported.

Action: Change the line in the JKM to use a supported commit type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15062: Invalid commit type: {0}

Cause: An invalid commit type was passed to SnpServiceGenerator.convertCommitType

Action: Contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15063: The alternate key {0} is not unique.

Cause: An alternate key defined by the repository is found to be non-unique.

Action: Check the data or the alternate key definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15064: The primary key {0} is not unique.

Cause: A primary key defined by the repository is found to be non-unique.

Action: Check the data or primary key definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15065: Join error ({0}) between the table {1} and the table {2}.

Cause: A foreign key relationship is not found.

Action: A foreign key relationship between 2 tables defined in the repository is not valid.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15066: The column {0} cannot be null.

Cause: The column is marked in the repository as not nullable.

Action: Check the data, or change the not null value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15067: The datatype value ''{0}'' is incorrect.

Cause: An invalid datatype has been found.

Action: The repository table contains an invalid datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15068: Unknown flexfield code {0}.

Cause: An undefined flex field code is being referenced

Action: Check the flex field references in the KM, and the flex field definitions
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15069: {0} Is not valid without session context.

Cause: A current session context does not exist.

Action: Check session definition.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15070: Unable to find method object: PythonInterpreter.initialize(Properties, Properties, String[]) method

Cause: The python method used by the script is not found.

Action: Check the KM step.
Level: 32

Type: ERROR

Impact: Other

ODI-15071: Error occurred

Cause: An exception was thrown while executing a python script in the KM step.

Action: Check the cause.
Level: 32

Type: ERROR

Impact: Other

ODI-15072: There is no PK constraint

Cause: There is a call to "getPK" in the KM, but no PK is found.

Action: Check the KM and the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15073: There is no index

Cause: There is a call to "getIndex" in the KM, but no index is found.

Action: Check the KM and the index definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15076: no dataset

Cause: A KM line is calling "getDataSet", but no data set is found.

Action: Check the KM or the DataSet definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15077: No Current Model Set

Cause: There is a call to "getModel" in the KM, but no model is found.

Action: Check the KM and the model definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15078: There is no Not Null column

Cause: There is a call to "getNotNullCol" in the KM, but no not null column is found.

Action: Check the KM and the not null column definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15079: There is no current Pop.

Cause: There is a call to "getPop" in the KM, but no interface is found.

Action: Check the KM and the interface definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15080: There is no Step

Cause: There is a call to "getStep" in the KM, but no step is found.

Action: Check the KM and the step definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15081: There is no Target Table

Cause: There is a call to "getTargetTable" in the KM, but no target table is found.

Action: Check the KM and the interface target table definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15083: Multiple Primary Keys have been detected for {0} .

Cause: A repository table can only have one primary key defined, but multiple primary keys are defined.

Action: Edit the table's primary key definitions and remove all but one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15084: There is no session

Cause: There is a call to "getSession" in the KM, but no session is found.

Action: Check the KM and the session definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15085: The value : ''({0})'' is unknown.

Cause: A KM line has a templated call which contains an unknown bracketed property.

Action: Fix the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15086: There is no Temporary Index

Cause: There is a call to "getTemporaryIndex" in the KM, but no temporary index is found.

Action: Check the KM and the temporary index definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15087: There is no current execution context defined.

Cause: There is a call to "getContext" in the KM, but no context is found.

Action: Check the KM and the context definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15088: Not in designer mode

Cause: A KM line has a call to access design information, but the interpretation location is not set to designer.

Action: Make sure that the interpretation location is set to designer when this line is executed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15089: asked '({0})' and available value are between 0 and ({1}).

Cause: A KM line is calling "getDataSet", but the specified index is out of range.

Action: Fix the KM or the DataSet definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15090: Table "{0}" not found on model "{1}", schema "{2}"

Cause: Attempt to initialize data services from a table that cannot be found

Action: Change data services reference or make sure that table exists
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15091: Impossible to connect to JPS MBean Server

Cause: Cannot connect to JPS MBean server.

Action: Internal Error.
Level: 32

Type: ERROR

Impact: Other

ODI-15092: Unable to generate data service - the column {0} does not exist in the database.

Cause: A data service references a column that does not exist

Action: Fix the data service reference or make sure that the column exists
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15093: Unable to regenerate this scenario. It references a null package.

Cause: The scenario must reference a package, but the package is null.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15094: You must give a name for the published entity for each datastore.

Cause: A web services data store does not have a name.

Action: Give the data store a name.
Level: 32

Type: ERROR

Impact: Other

ODI-15095: Invalid entity for datastore: {0}

Cause: A web services data store has an invalid entity.

Action: Associate the data store with a valid entity.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15096: Property name must not be null.

Cause: The KM line is calling "isColAttrChanged", but the property value is null.

Action: Internal error, contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15097: Unknown value {0} for property

Cause: The KM line is making a templated call, but the property value is unknown.

Action: Fix the KM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15098: You must define a data source for the model.

Cause: The model used by a web service does not have any data source.

Action: Define a data source for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15099: You must specify a JKM for the model.

Cause: The model used by a web service does not have an associated JKM.

Action: Define a JKM for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15100: You must define a Java package for the model.

Cause: The model used by a web service does not have an associated Java package.

Action: Define a Java package for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15101: Invalid Java package format: {0}

Cause: The Java package associated with a model has an invalid package format.

Action: Correct the package format for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15102: You must specify an XML namespace for the model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15103: Invalid namespace: {0}

Cause: A model namespace used by a web service is invalid.

Action: Correct the namespace for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15104: You must specify an SKM for the model.

Cause: A model used by a web service does not have an associated SKM.

Action: Add an SKM to the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15105: You must specify which schema the model will be deployed to.

Cause: No web service deployment schema is specified for the model.

Action: Specify a schema to which the model will be deployed.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15106: You must specify a name for the Data Service for the model.

Cause: The data service for the model does not have a name.

Action: Set a valid name for the data service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15107: Invalid model code: {0}. It should follow the Java identifiers naming conventions.

Cause: The web service model name does not follow the standard Java identifier naming convention.

Action: Set a valid name for the model.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15108: Invalid model Data Service name: {0}. It should follow the Java identifiers naming conventions.

Cause: The web service model Data Service name does not follow the standard Java identifier naming convention.

Action: Set a valid name for the model Data Service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15109: Invalid web service name for datastore: {0}

Cause: The web service model data store has an invalid name.

Action: Set a valid name for the model data store.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15110: SKM is empty

Cause: The web service SKM has no valid lines.

Action: Add some lines to the SKM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15111: Problem during deployment

Cause: Internal error.

Action: Contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Deployment

ODI-15113: Reverse table {0} for model {1} already exists.

Cause: An attempt was made to reverse engineer a table, but it already exists in the model.

Action: Move or rename the data store in the model, or skip reverse engineering for the table.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15116: There is not enough data in the target file to proceed with the reverse-engineering. Please make sure the file has at least one non-empty line and number of rows to skip is correct.

Cause: An attempt was made to reverse engineer a target file that is empty, or the number of skipped rows is larger than the number of rows in the file.

Action: Set the number of skipped lines to a lower value, or add some data to the file.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15117: Not allowed (OLD and NEW are involved)

Cause: The KM line is calling "getColumn", but the ADH action origin is not ''NEW'' or ''OLD''.

Action: Change the ADH action origin.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15118: Invalid FTP URL

Cause: The URL given for a web services FTP connection is not correct.

Action: Check the URL for the FTP connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-15119: Column {0} has no Java datatype.

Cause: The column being processed has no java datatype.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15120: Column {0} has no String datatype.

Cause: The column being processed has no string datatype.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15121: Selector must be not null

Cause: The ADH selector value must not be null when "getColumn" is called from the KM line.

Action: Change the ADH selector value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15122: Exception getPKColList

Cause: An exception was found when calling "getPKColList" during KM execution.

Action: Fix the KM or the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15123: There is no AK constraint

Cause: There is a call to "getAK" in the KM, but no AK is found.

Action: Check the KM and the AK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15124: Unable to regenerate the following scenario:

Cause: Cannot regenerate the scenario.

Action: Delete the scenario and create a new one.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15125: Missing DataSet.

Cause: The interface is missing a dataset.

Action: Check interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15126: The sub-model must be set.

Cause: The sub-model is not set for the source or target.

Action: Check the interface for consistency.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15127: There is no CK constraint

Cause: There is a call to "getCK" in the KM, but no CK is found.

Action: Check the KM and the CK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15128: There is no FK constraint

Cause: There is a call to "getFK" in the KM, but no FK is found.

Action: Check the KM and the FK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15129: Selector value must be 'OLD' or 'NEW'

Cause: The ADH selector value must be 'OLD' or 'NEW' when "getColumn" is called from the KM line.

Action: Change the ADH selector value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15130: Unknown object in interface source table list

Cause: Internal Error.

Action: Contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15131: You must define the name of each web service to be generated for each datastore.

Cause: A web service associated with a data store has no name.

Action: Give a name to the web service.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15132: Exception getPK

Cause: An exception was found when calling "getPK" during KM execution.

Action: Fix the KM or the PK definitions.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15135: There is no current index.

Cause: The current index can not be found for the property name.

Action: Check the reference.
Level: 32

Type: ERROR

Impact: Other

ODI-15141: Repository is not a development work repository

Cause: When getting a connection used to execute the KM, it was determined that the provided connection information does not point to a development work repository

Action: Fix the connection information
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15142: [PROPERTY: {0} not found.]

Cause: The bracketed property in the KM line (e.g. "[COL_NAME]") is not found.

Action: Fix the KM line to specify a correct property name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15143: Invalid isolation level : {0}

Cause: An invalid isolation level value was passed to SnpServiceGenerator.convertIsolationLevel

Action: Contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15144: KM not encrypted since it is empty.

Cause: KM was not encrypted since it is empty.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-15146: Data Type can't be null

Cause: null DataType passed.

Action: Pass non null DataType.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15147: The changes on this target column will be lost since it is not saved (it has no mapping text)

Cause: Target column will not be saved.

Action: Enter mapping text if the column requires to be saved.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15148: The target datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Target datastore is not on Oracle.

Action: Move target datastore to an Oracle schema.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15149: The staging area is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Staging Area is not on Oracle.

Action: Move Staging Area to an Oracle schema.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15150: The source datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler

Cause: Source DataStore not on Oracle.

Action: Use only DataStores located on an Oracle technology.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15151: Non ordered outer joins cannot be used with the platform compiler

Cause: An outer join is not ordered.

Action: Make the join ordered.
Level: 32

Type: WARNING

Impact: Interface Issue

ODI-15152: Unhandled Action {0}

Cause: This shouldn't happen. Programmer added an action in the enum and forgot to add it in switch.

Action: Add action in switch.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15153: The column is already the first column and cannot be moved up

Cause: Column already first and cannot be moved up.

Action: Do not try to move first column up.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15154: The column is already the last column and cannot be moved down

Cause: Column already last and cannot be moved down.

Action: Do not try to move last column down.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15155: Cannot move a target column to a position that is 0 or negative: {0}

Cause: Trying to move a column beyond the boundaries of column positions.

Action: Use a value between 1 and the number of columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15156: Cannot move a target column to a position beyond the size of the column list: {0} is greater than {1}

Cause: Trying to move a column beyond the boundaries of column positions.

Action: Use a value between 1 and the number of columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15157: Cannot remove the only dataset of interface {0}

Cause: Trying to remove the last dataset of an interface is not permitted.

Action: Make sure there are more than one dataset in the interface before deleting it.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15159: Cannot move target columns on a non temporary DataStore.

Cause: Trying to move columns on a non temporary DataStore.

Action: Make sure that the target DataStore is temporary before attempting to move target columns.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15160: Native Sequences may not be supported by the target technology after transforming with the Platform Compiler

Cause: Using Native Sequence and Platform Compiler Enabled User Param Set

Action: Make sure that all target technologies will support native sequences
Level: 32

Type: WARNING

Impact: Programmatic

ODI-15162: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)

Cause: Using native sequence in derived sub interface

Action: Make sure that none sub interface using native sequence
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15200: Tried to retrieve an int with an {0} object

Cause: Attempted to read the column from RDB as an integer, but the column type is not integer

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15201: Tried to retrieve a short with an {0} object

Cause: Attempted to read the column from RDB as a short type, but the column type is not short

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15202: This resultset accepts only FETCHFORWARD requests

Cause: Attempted to set the fetch direction to something other than FETCH_FORWARD for a RDB result set read

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15203: This function is unsupported: the software you are using might not be compatible with this driver.

Cause: A jdbc call was made that is not supported by the currently loaded jdbc driver for RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15204: The {0} call is not implemented in this result set class.

Cause: A result set call was made that is not implemented by the ODI RDB result set class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15205: The call is not supported in this result set class.

Cause: A result set call was made that is not supported by the ODI RDB result set class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15206: Unmanaged numeric type {0}

Cause: The RDB inserter class was passed a data value of a numeric type that is not handled

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15207: Strange: a PK has multiple lines

Cause: When selecting a parent row based on a primary key, multiple rows were returned

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15208: The PK column of the root table has an unknown type: {0}

Cause: When unloading data from the RDB, the PK column of the parent table has an unknown type

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15209: Unsupported technology (Driver: {0}, Url: {1})

Cause: The jdbc driver is not supported by the ODI RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15210: Unsupported technology: HSQL cannot create FKs after the tables have been created

Cause: The Hypersonic SQL engine cannot create FK after the table is already created

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15211: Unsupported technology: HSQL cannot create PKs after the tables have been created

Cause: The Hypersonic SQL engine cannot create PK after the table is already created

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15212: Datatype NULL (0) unsupported

Cause: The Hypersonic SQL engine does not support the null datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15213: JDBC Datatype '{0}' unsupported

Cause: The Hypersonic SQL engine does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15214: JDBC Datatype '{0}' with length parameter unsupported

Cause: The Hypersonic SQL engine does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15215: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The Hypersonic SQL engine does not support the datatype with scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15216: JDBC Datatype '{0}' unsupported

Cause: The internal MS Sql Server database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15217: JDBC Datatype '{0}' with length parameter unsupported

Cause: The internal MS SQL Server database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15218: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The internal MS SQL Server database engine does not support the datatype with length and scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15219: Please transform your URL into: {0};SelectMethod=cursor

Cause: The internal MS SQL Server database engine does not recognize the supplied URL

Action: Change the format of the connection URL
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15220: need length param

Cause: The internal Oracle database does not support the selected type without a length param

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15221: Datatype NULL (0) unsupported

Cause: The internal Oracle SQL engine does not support the null datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15222: JDBC Datatype '{0}' unsupported

Cause: The internal Oracle database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15223: JDBC Datatype '{0}' with length parameter unsupported

Cause: The internal Oracle database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15224: JDBC Datatype '{0}' with length and scale parameters unsupported

Cause: The internal Oracle database engine does not support the datatype with length and scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15225: No key found on table {0}

Cause: The internal database table does not have a key

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15226: The root table {0} has no data

Cause: The internal database table does not have any data

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15227: Multiple keys found on table {0}

Cause: The internal database table has multiple keys

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15228: *** FATAL *** Table {0} could not be validated

Cause: The internal database cannot validate the table

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15229: *** FATAL *** Table {0} could not be found

Cause: The internal database cannot find the table

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15230: Could not convert object {0} to a {1}

Cause: The internal database cannot convert the datatype of the selected column

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15231: No '=' sign found on line {0} of bundle {1}

Cause: The internal database engine encountered a syntax error when reading the property file

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15232: The alias {0} for table {1} is already used by another table, when reading bundle {2}

Cause: The internal database found a duplicate table alias in a property file

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15233: Table {0} is used twice. Make sure that the table names and aliases do not conflict.

Cause: The internal database found a duplicate table name in the property bundle

Action: Fix the property file
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15234: Internal RDB database table {0} not found

Cause: The requested table cannot be found in the internal database

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15235: Internal RDB database key {0} not found

Cause: The requested key cannot be found in the internal database

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15236: Unknown table {0}

Cause: The requested table cannot be found in the internal database

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15237: Duplicate table

Cause: The internal database table is a duplicate table

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15238: Could not find table although we should have created it!

Cause: The newly created table cannot be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15239: Only SnpsRDBDiffActionImportDifference are supported for now.

Cause: When processing diff actions in a diff operation, an unsupported diff action class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15240: Unknown key {0}

Cause: When processing diff actions in a diff operation, a nonexistent key was specified by the diff action

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15241: This type of difference is not managed for now: {0}

Cause: When processing diff actions in a diff operation, an unsupported diff action class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15242: Unknown difference type: {0}

Cause: When processing diff actions in a diff operation, an unknown diff class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15243: Bad model number: {0}

Cause: When processing diff actions in a diff operation, the 2 models that are being compared are internally numbered as model 1 and 2. A model number other than 1 or 2 was used internally in a call to getModel.

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15244: Could not add a key because {0} is not an ID key.

Cause: When building a model, the specified key class instance was not an id key

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15245: Unknown key type: {0}

Cause: When building a model, an unknown key class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15246: Key {0}.{1} is of unknown type: {2}

Cause: When building a model, an unknown key class was found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15247: The table {0} cannot be found. It is referenced by key: {1}.

Cause: When building a model, an table name is referenced by a key, but the table cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15248: The column {0} in table {1} cannot be found. It is referenced by key: {2}.

Cause: When building a model, an column name is referenced by a key, but the column cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15249: An {0} was caught while adding a key which is not an FK. Very strange.

Cause: When building a model, an column name is referenced by a key, but the column cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15250: The key {0} referenced by table {1} cannot be found.

Cause: When building a model, a key name is referenced by a table, but the key cannot be found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15251: A duplicate key was found: {0}

Cause: When dropping a model, a duplicate key was found in the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15252: Key already exists: {0}

Cause: When updating a model, a duplicate key was found in the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15253: Key not found: {0}

Cause: When updating a model, the key was not found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15254: Could not find a constructor with a key name for class {0}

Cause: When creating a key class instance, the constructor could not be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15255: Could not instantiate an object of class {0}

Cause: Could not instantiate the key class

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15256: Could not create an object for class {0} for security reasons

Cause: Could not instantiate the key class, due to a security failure

Action: Check security settings
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15257: Could create an object for class {0} because a {1} occurred saying {2}

Cause: Could not instantiate the key class, due to an invocation target exception

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15258: Column {0} not found

Cause: The column could not be found

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15259: The key class {0} is not an ID key class.

Cause: The specified key class instance was not a SnpsRDBIdKey instance

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15260: Could not add column {0}: Unsupported datatype: {1}

Cause: Cannot add the column to the model because the datatype is not supported by the technology

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15261: Unsupported action: {0}

Cause: The action class is not supported by the ODI RDB

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15262: Cannot drop column {0}. It is used in a foreign key!

Cause: An attempt was made to drop a column that participates in a foreign key

Action: Drop the key first, then the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15263: Cannot drop column {0}. It is used in a primary key!

Cause: An attempt was made to drop a column that participates in a primary key

Action: Drop the key first, then the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15264: Cannot modify this column. It is used in a foreign key!

Cause: An attempt was made to modify a column that participates in a foreign key

Action: Drop the key first, then modify the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15265: Cannot modify this column. It is used in a primary key!

Cause: An attempt was made to modify a column that participates in a primary key

Action: Drop the key first, then modify the column
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15268: Table not found: {0}

Cause: When attempting to drop a table during an update, the table name is not found

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15270: Key type {0} is not supported here.

Cause: The key type is not supported

Action: Correct the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15272: An error occurred while executing a RDB command: {0}

Cause: When executing a command action, an exception was thrown

Action: Check root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15273: {0}: action is not accepted: {1}

Cause: Attempt to execute a command action, but it is not accepted

Action: Check root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15274: Multiple PKs are not allowed on a table

Cause: When reverse engineering a primary key, multiple primary keys were found for the table

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15275: An exception ocurred while retrieving a table primary key: {0}

Cause: When reverse engineering a table, a primary key could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15276: An exception occurred while retrieving the indexes of a table: {0}

Cause: When reverse engineering a table, the indexes could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15277: An exception ocurred while retrieving a table foreign keys: {0}

Cause: When reverse engineering a table, the foreign keys could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15278: An exception occurred while retrieving the check constraints of a table: {0}

Cause: When reverse engineering a table, the check constraints could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15279: An exception occurred while retrieving the alternate keys of a table: {0}

Cause: When reverse engineering a table, the alternate keys could not be retrieved

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15280: *** FATAL *** Table {0} is duplicate as root

Cause: The table is duplicated as the root when determining the root tables of the model

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15281: *** FATAL ** Table {0} is unknown

Cause: The root table is unknown

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15282: Table {0} is unknown though it was reversed

Cause: The table cannot be found in the ODI model, although it was reversed

Action: Retry the reverse engineering
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15283: Duplicate declaration for table {0}

Cause: The model XML contains a duplicate table declaration

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15285: FK {0} references a table with no PK.

Cause: The model XML contains a foreign key that references a table with no defined primary key

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15286: Unknown PK table for foreign key {0}: please check the name and order of the tables and FK.

Cause: The model XML contains a foreign key that references an unknown primary key table

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15287: Unknown element: {0}

Cause: The model XML contains an unknown element

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15288: An {0} error occurred with the following message: {1}

Cause: An error occurred when writing the model to a file

Action: See root cause
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15290: Column {0} was not found in table {1}

Cause: The column was not found when building the columns from column names

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15291: *** FATAL *** Could not rename table {0} to {1}

Cause: Could not rename table

Action: Check permissions and security settings
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15292: *** FATAL *** Could not rename table {0} because it was not found in the model!

Cause: Could not rename table, because the table to be renamed does not exist

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15293: Unknown FK table for foreign key {0}: please check the name and order of the tables and FK.

Cause: The model XML contains a foreign key that references an unknown table

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15294: unknown element: {0}

Cause: The model XML contains an unknown XML element

Action: Fix the XML
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15295: Unsupported datatype: {0}

Cause: The datatype is unsupported when creating the column from attributes

Action: Check the model
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15300: A {0} occurred while creating the helper of class {1}. Error message: {2}

Cause: INTERNAL ERROR: A helper cannot be created.

Action: Internal error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Other

ODI-15301: Choose: {0}

Cause: Choose one of the displayed options.

Action: Choose one of the displayed options.
Level: 32

Type: ERROR

Impact: Other

ODI-15302: FK is null: {0}

Cause: The FK is null, may indicate repository corruption.

Action: Internal error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Other

ODI-15303: JDBC Datatype '{0}' with length '{1}' parameter unsupported

Cause: MySQL database does not support the datatype with length

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15304: JDBC Datatype '{0}' with length '{1}' and scale '{2}' parameter unsupported

Cause: MySQL database does not support the datatype with scale

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15305: JDBC Datatype '{0}' unsupported

Cause: MySQL database does not support the datatype

Action: Internal Error: contact Oracle support
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15306: Column data type "{0}" not supported. Refer documentation for supported types.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15307: Metadata format of element with identifier "{0}" is incorrect. Found value "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15308: Error unloading CLOB for column "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15309: Error unloading BLOB for column "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15400: Error in generating data service

Cause: Exception thrown when creating the data service used for DDL generation and reverse engineering.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15401: Unknown key {0}

Cause: Unknown key encountered when processing diff class instances during DDL generation.

Action: Check the model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15402: Exception thrown in the DDL generation service: {0}

Cause: An exception was thrown while generating DDL.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15403: The method is not supposed to sort something else than the expected actors. Attempting to sort class instances: {0}, {1}

Cause: While sorting action commands, the DDL generator service encountered an unknown class instance type.

Action: Internal Error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15404: Scenario generation has not been implemented for this container.

Cause: During DDL generation, an attempt was made to generate a scenario for an object that does not support it.

Action: Internal Error: contact Oracle support.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15405: Scenario generation exception: {0}

Cause: An exception was thrown during scenario generation.

Action: Check root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15406: Oozie workflow generation exception: {0}

Cause: An exception was thrown during Oozie workflow generation.

Action: Check root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15500: Column {0} is executed on the target

Cause: Possible Cause

Action: Suggested Action
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15501: Cannot attach a data store to a target mapping because column {0} is not found.

Cause: The specified target column was not found.

Action: Verify that the correct column has been specified.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15502: Target mapping not found for column {0}

Cause: The specified column is not mapped.

Action: Map the specified column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15503: Cannot set the attached datastore because the mapping is not executed on the SOURCE

Cause: The mapping has been configured for execution on the target.

Action: Configure the mapping for execution on the source.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15504: Unknown indicator type: {0}

Cause: An invalid indicator type has been specified.

Action: Specify one of the following indicator types from the IndicatorType enumeration: CHECK_NOT_NULL, INSERT, UPDATE, or UPDATE_KEY.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15505: Invalid UD number: {0}

Cause: An invalid UD number has been specified.

Action: Specify a UD number 1 to 10.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15506: The specified target column was not found: {0}

Cause: The specified target column was not found when attempting to remove a column from a temporary data store.

Action: Only remove columns which exist in the temporary target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15507: Column {0} may not be removed. It is used in other mappings, join clauses, or filter clauses

Cause: The specified target column is used in other mappings, filters, or joins. This dependency prevents removal of the column.

Action: Only remove a column after mapping, filter, or join dependencies have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15508: Column {0} may not be removed because it is referenced in interface {1}.

Cause: The specified target column is referenced in a filter or join clause in another interface. This dependency prevents removal of the column.

Action: Only remove a column after other references have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15509: The specified target column was not found: {0}

Cause: The specified target column was not found.

Action: Verify the column name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15510: A column was not found while updating the key

Cause: The update key contains a column that does not exist.

Action: Check the columns of the update key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15511: The join must be attached to the datastore to expand a lookup.

Cause: The join is not attached to a datastore, so a valid lookup does not exist.

Action: Only use the lookup expansion, with a pCreateLookup parameter value of false, on valid lookups.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15512: Cannot transform a normal datastore into a normal lookup.

Cause: The data store is already a non-lookup data store.

Action: Do not use this transformation on a non-lookup data store. If the datastore and join are non-lookup, use a pCreateLookup parameter value of true to create a lookup from a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15513: Cannot transform a normal, non-lookup join into a normal join.

Cause: The join is already a normal join, not a lookup join, so expansion to a normal, non-lookup join is not possible.

Action: Do not use this transformation on a normal join. If the datastore and join are non-lookup, use a pCreateLookup parameter value of true to create a lookup from a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15514: Cannot transform a lookup datastore into a lookup.

Cause: The data store is already designated as a lookup, so transforming to a lookup is not possible.

Action: Do not use this transformation on a lookup. If the datastore and join are designated for lookup, use a pCreateLookup parameter value of false to expand a lookup to a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15515: Cannot transform a lookup join into a lookup.

Cause: The join is already designated as a lookup, so transforming to a lookup is not possible.

Action: Do not use this transformation on a lookup. If the datastore and join are designated for lookup, use a pCreateLookup parameter value of false to expand a lookup to a normal join and normal datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15516: The join must be attached to the datastore to make a lookup.

Cause: The join is not properly attached to data sources, so transforming to a lookup is not possible.

Action: Designate data sources for the join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15517: Cannot add a column with the same name as an existing target column: {0}.

Cause: The column being added already exists.

Action: Add a column with a unique name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15518: A dataset is already assigned the order: {0}.

Cause: Another dataset has already been assigned the order that is being set.

Action: Assign a unique order to the dataset.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15519: The target datastore cannot be changed. Interface {0} is used in interface(s) {1} as a source datastore.

Cause: The interface is used as a source datastore of another interface, so the target datastore cannot be changed.

Action: Create a separate interface to avoid the source datastore dependency in the other interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15520: Temporary interface from another project is not allowed.

Cause: The interface is used as a source datastore of another interface, so the target datastore cannot be changed.

Action: Create a separate interface to avoid the source datastore dependency in the other interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15521: A source datastore with alias {0} already exists.

Cause: The datastore alias has already been used.

Action: Specify a unique alias.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15522: Cannot transform a join into a CrossJoin or natural join if it does not have both attached datastores set.

Cause: The join does not have datastores attached yet.

Action: Attach both join datastores before transforming to a cross join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15523: LKM {0} not accepted for source set {1}

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15524: LKM {0} not accepted for staging area to target

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15525: CKM {0} not accepted for target technology

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15526: IKM {0} not accepted for staging and target technology

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15527: IKM {0} not accepted for target technology

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15528: Mapping expression cannot be set because the target column {0} was not found.

Cause: The column was not found when setting the expression for a mapping.

Action: Specify a valid column for the expression.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15529: Action was not reversible.

Cause: The actions causing an impact are not reversible.

Action: Avoid the sequence of actions causing the impact.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15530: The interface does not have a source set.

Cause: The interface does not have a source set.

Action: Add a source set to the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15531: The execution location parameter for the computeExpression method is invalid.

Cause: The execution location parameter for the computeExpression method is invalid.

Action: Specify an execution location parameter of ExecutionLocation.SOURCE, ExecutionLocation.WORK, or ExecutionLocation.TARGET.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15532: The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.

Cause: The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.

Action: Specify an execution location parameter of ExecutionLocation.SOURCE, ExecutionLocation.WORK, or ExecutionLocation.TARGET.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15533: The physical schema could not be mapped from logical schema {0} and context {1}.

Cause: The getPhysicalSchema method failed to map and logical schema and context to a physical schema.

Action: Ensure that logical to physical schema mappings are created or check the logical schema and context parameters.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15534: Sub interface must not be null.

Cause: The pSubInterface parameter passed to the checkSubInterfaceValid method is null.

Action: A non-null sub interface parameter is required for the checkSubInterfaceValid method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15535: The technology {0} of the source temporary interface {1} used as a derived table does not support derived tables.

Cause: The pSubInterface parameter passed to the checkSubInterfaceValid method is null.

Action: A non-null sub interface parameter is required for the checkSubInterfaceValid method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15536: Source temporary interface {0} cannot be used as a derived table. Its source datastore {1} defined in logical schema {2} has no associated physical schema in the optimization context {3}.

Cause: The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the source.

Action: Create a mapping between the logical schema, context, and physical schema for the source data store.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15537: Source temporary interface {0} cannot be used as a derived table. The logical schema of the target datastore {1} has no associated physical schema in context {2}.

Cause: The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the target.

Action: Create a mapping between the logical schema, context, and physical schema for the target data store.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15538: Source temporary interface {0} cannot be used as a derived table. The logical schema of the staging area {1} has no associated physical schema in the optimization context {2}.

Cause: The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the staging area.

Action: Create a mapping between the logical schema, context, and physical schema.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15539: Source temporary interface {0} cannot be used as a derived table. Source datastore {1} is not on the same data server as the target.

Cause: The temporary interface cannot be used because the source data store is not on the same data server as the target.

Action: Ensure that the source and target datastores are on the same data server.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15540: Source temporary interface {0} cannot be used as a derived table. Staging area and target datastores are not in the same data server. You may have forced the target context to a different context than the optimization context.

Cause: The temporary interface cannot be used because the staging data store is not on the same data server as the target.

Action: Ensure that the staging and target datastores are on the same data server.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15541: Source temporary interface {0} uses a journalized datastore and cannot be used as a derived table.

Cause: The temporary interface cannot be used because it uses a journalized datastore.

Action: Use only non journalized data stores in temporary interfaces.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15542: Source temporary interface {0} cannot be used as a derived table. All source datastores of this interface should be in the same data server as the target and should not be journalized.

Cause: The temporary interface cannot be used because it uses a journalized datastore.

Action: Use only non journalized data stores in temporary interfaces.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15543: Another interface with the same name already exists in this folder. Please choose a unique interface name.

Cause: Another interface with the same name already exists in this folder.

Action: Specify a unique interface name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15544: The interface must have a name.

Cause: The interface does not have a name.

Action: Specify a unique interface name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15545: Temporary target datastore has no name.

Cause: The temporary target datastore has no name

Action: Specify a unique datastore name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15546: The interface must have a logical schema.

Cause: The interface does not have a logical schema.

Action: Specify a logical schema for the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15547: Could not fix a missing reference correctly.

Cause: The interface is missing one or more references.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15548: The source datastore has already been set.

Cause: The source datastore has already been set.

Action: Only invoke setSourceDataStore once.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15549: Cannot set the source filter because the source datastore is not set.

Cause: The source datastore has not been set prior to setting the filter.

Action: Set the source datastore prior to setting the filter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15550: The target datastore has already been set.

Cause: The source datastore has already been set.

Action: Only invoke setSourceDataStore once.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15551: Mappings on the target are not allowed in this helper.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15552: A source filter requires a source datastore.

Cause: The interface cannot be saved because it contains a filter without a source datastore.

Action: Create a source datastore before creating a source filter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15553: The target datastore must be set.

Cause: The target datastore for the interface has not been set.

Action: Set the target datastore before saving the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15554: An LKM must be set on the source set.

Cause: A loading knowledge module has not been assigned to the source set.

Action: Set the LKM for the source set before saving the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15555: Target IKM must be set on the target table.

Cause: An integration knowledge module has not been assigned to the target table.

Action: Set the IKM for the target before saving the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15556: Unknown generic clause type: {0}

Cause: An unknown generic clause class was passed to the createSnpPopClauseFromGenericClause method.

Action: Pass only generic clause classes for join or filter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15557: Unknown execution location type: {0}

Cause: An unknown execution location enumeration was passed to the getStringExeDbFromExecutionLocation method.

Action: Pass only location enumerations of ExecutionLocation.SOURCE, ExecutionLocation.WORK, ExecutionLocation.TARGET.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15558: There is a conflict between physical schemas

Cause: There is a conflict between the various physical schemas used to obtain the data, such as multiple data stores in the same source set connected using different physical schemas.

Action: Ensure that physical schemas of a source set have consistent connection information.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15559: Unsupported component: {0}

Cause: An unsupported component was passed as a parameter to createDataAccessinfo.

Action: For the pInterfaceSubComponents parameter, supported components are SourceDataStore, ISourceColumn, TargetMapping, and GenericClause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15560: Fatal interface condition: {0}

Cause: A fatal issue was discovered while saving or verifying an interface.

Action: Correct the interface issue before saving it.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15561: Could not find column {0} which choosing a mapping.

Cause: The MappingChooserFirst.chooseMapping method was called with an column name that does not exist.

Action: Check the column name passed to chooseMapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15562: Source sets cannot be computed because one execution area doesn't have a physical schema. Check the errors on the interface.

Cause: Source sets cannot be computed because one execution area doesn't have a physical schema.

Action: Check the errors on the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15563: Source sets cannot be computed because the staging area is not properly defined. Check your target datastore and the staging area's physical schema in the Definition tab.

Cause: Source sets cannot be computed because the staging area is not properly defined.

Action: Check your target datastore and the staging area's physical schema in the Definition tab.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15564: There should be one source set on the interface.

Cause: The interface has more than one source set.

Action: Ensure that only one source set is defined.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15565: Column {0} not found while setting the update key.

Cause: A column specified for the update key does not exist.

Action: Recheck the column names used to define the update key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15566: No target column was found while setting the target data store.

Cause: No target column was found while setting the target data store.

Action: Define columns before setting the target datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15567: Target column {0} was not found.

Cause: No specified target column was not found in the target data store.

Action: Check the column name parameter in the RealBasicInterfaceCreationHelper.getTargetColumn method call.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15568: Column {0} not found on datastore {1}.

Cause: A referenced column was not found in a source data store.

Action: Check the source datastore columns and references for a mismatch.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15569: Cannot create a data source.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15570: Cannot add a datastore of type {0} as source.

Cause: An invalid datastore type has been specified.

Action: Specify a datastore of type TargetDataStore, SourceDataStore, or OdiDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15571: Unexpected join type {0}

Cause: An invalid join type has been specified when setting join properties.

Action: Specify a join type of INNER, CROSS, or NATURAL.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15572: Unexpected join state.

Cause: An invalid join state has been reached. The expected join type is CROSS or NATURAL.

Action: .
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15573: Failed to create an interface helper instance.

Cause: A general exception was encountered while constructing an interface helper.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15574: General exception encountered in the interface helper while preparing to persist.

Cause: General exception encountered in the interface helper while preparing to persist.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15575: Two journalized datastores have been found. There should be only one.

Cause: Two journalized datastores have been found. There should be only one.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15576: Two journalized filters have been found. There should be only one.

Cause: Two journalized filters have been found. There should be only one.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15577: Unmanaged type: {0}

Cause: An invalid element type was passed to the prepareSQLStatement method.

Action: Pass only valid element types such as GenericClause, SourceDataStore, TargetDataStore, ISourceColumn, TargetMapping, SourceSet, DataSet, or TargetColumn.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15578: No interface was found in the elements.

Cause: No interface could be traced to the elements passed to the prepareSQLStatement method.

Action: Create an interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15579: No dataset was found in the elements.

Cause: No data set could be traced to the elements passed to the prepareSQLStatement method.

Action: Ensure that a dataset has been created first.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15580: The target is a temporary table.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15581: Cannot build the query because the ordered joins are not correct.

Cause: The SQL clause cannot be generated because the ordered joins are not correct.

Action: Ensure that all joins are correct.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15582: This operation is not supported on joined file datastores.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15583: This operation is not supported on multiple file datastores.

Cause: More than one source datastore was found.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15584: Elements are from different interfaces.

Cause: The components passed to prepareSQLStatement are from different interfaces.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15585: Elements are from different datasets.

Cause: The components passed to prepareSQLStatement are from different data sets.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15586: Unsupported component: {0}

Cause: An invalid component type was passed to connectionForData.

Action: Only pass components of type SourceDataStore, ISourceColumn, TargetMapping, TargetColumn, GenericClause, or TargetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15587: Journalization filter not found for the journalized table.

Cause: The journalized table does not have a filter.

Action: Define a journalizing filter for the table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15588: The SQL join clause is not valid for a cross join.

Cause: A join clause has been specified for a cross join.

Action: Remove the join condition or change the join type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15589: Cannot change the ON_TARGET indicator on a temporary interface.

Cause: An attempt was made to set the ON_TARGET indicator for a temporary datastore.

Action: Do not change the ON_TARGET indicator for a temporary datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15590: Unknown indicator type: {0}

Cause: An unknown value was passed to the constructor for InterfaceActionOnStagingAreaSetIndicator.

Action: Use valid values of DISTINCT_ROW, ON_TARGET, or ON_USER_DATABASE_SCHEMA for the pIndicatorType parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15591: Staging Area is on the target and cannot be switched to another logical schema.

Cause: The staging area is on the target and uses the target schema. It cannot be switched.

Action: Do not attempt to switch the schema, or use a separate staging area.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15592: GenericClause is of unknown type: {0}

Cause: InterfaceActionRemoveGenericClause was constructed with an invalid generic clause.

Action: Use a generic clause type of JOIN or FILTER.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15593: Could not set LKM for object of type {0}

Cause: An LKM is being set for a TargetDataStore or some other invalid type.

Action: Only set an LKM for a SourceSet or StagingArea.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15594: Could not set the CKM for a holder of type {0}

Cause: A CKM is being set for a SourceSet, StagingArea, or some other invalid type.

Action: Only set a CKM for a TargetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15595: Could not set the IKM for a holder of type {0}

Cause: An IKM is being set for a SourceSet, StagingArea, or some other invalid type.

Action: Only set an IKM for a TargetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15596: Invalid KM type: {0}

Cause: An invalid object type is being used to set a KM.

Action: Only set a KM of type LKM, CKM, or IKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15597: Could not set the LKM option for a holder of type {0}

Cause: An LKM is being set for a TargetDataStore or some other invalid type.

Action: Only set an LKM option for a SourceSet or StagingArea.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15598: Could not set the CKM option for a holder of type {0}

Cause: A CKM option is being set for a SourceSet, StagingArea, or some other invalid KM holder type.

Action: Only set a CKM option for a KM holder of type TagetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15599: Could not set the IKM option for a holder of type {0}

Cause: An IKM option is being set for a SourceSet, StagingArea, or some other invalid KM holder type.

Action: Only set an IKM option for a KM holder of type TagetDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15600: Dataset 1 was not found in the list of the interface datasets used with the interface.

Cause: The first dataset given as a parameter in the construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.

Action: Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15601: Dataset 2 was not found in the list of the datasets used with the interface.

Cause: The second dataset given as a parameter in the construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.

Action: Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15602: Dataset 2 was not found in the list of the datasets used with the interface.

Cause: An unimplemented method has been called. This is an ODI internal error.

Action: Do not call this method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15603: Cannot create an alias for a datastore of type {0}

Cause: The method computeAliasForDataStore was called with an invalid datastore type.

Action: Only call computeAliasForDataStore for datastores of type TargetDataStore or OdiDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15604: A non ordered clause was passed to the buildTreeSet method.

Cause: A non ordered clause is passed to the construction of ordered joins trees method.

Action: Use ordered join clauses with this method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15605: Multiple ordered joins in this dataset use the same order number.

Cause: One or more join clauses uses the same order number in the call to buildTreeSet.

Action: Ensure that all clauses of an ordered join have unique order numbers.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15606: Join references the same table twice (directly or indirectly).

Cause: A join clause contains two references to the same table.

Action: Ensure that the join clause only references one table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15607: Join references the same table twice through other joins.

Cause: A join clause contains two references to the same table.

Action: Ensure that the join clause only references one table.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15608: Subcomponent type of {0} is not supported.

Cause: An unsupported type was passed to getIssuesComputer.

Action: Only pass types of OdiInterface, DataSet, SourceDataStore, Filter, Join, StagingArea, TargetDataStore, SourceSet, TargetMapping, or TargetColumn.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15609: Invalid KM holder type: {0}

Cause: An invalid KM holder type was passed to InterfaceKMHolderFactory.getKMHolderFor

Action: Only pass KM holder types of SOURCE_SET_LKM, STAGING_AREA_LKM, TARGET_CKM, or TARGET_IKM.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15610: Component must be a source datastore or a source column.

Cause: ReferenceManagerAbstract.getReferencesTo was called with an invalid subcomponent.

Action: Only pass subcomponent types of SourceDataStore or ISourceColumn.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15611: Column not found from an xref.

Cause: A column referenced in an expression was not found in a datastore. It may have been deleted.

Action: Ensure that all columns referenced in the expression exist.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15612: Failed to attach an element of type {0} to a source set.

Cause: An invalid type of component was found when attaching elements to a source set.

Action: Elements being attached to a source set must be of type SourceDataStore, Join, Filter, or TargetMapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15613: Interface must have only one dataset.

Cause: This sourceset computer can only handle a single dataset, and more than one was found.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15614: Interface must have only one source table.

Cause: This sourceset computer can only handle a single table, and more than one dataset was found.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15615: Interface must not have joins.

Cause: This sourceset computer can only handle a single table, and the interface contains a join.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15616: Source datastore must be a real table

Cause: This sourceset computer can only handle a single, real table.

Action:
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15617: Invalid type for a TextHolder: {0}

Cause: The method getExecutableTextHolderFor was called with an invalid TextHolder component type.

Action: Valid types are TargetMapping, TargetColumn, Filter, and Join.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15618: Cannot set a source set on a target column.

Cause: SetSourceSet was called for a target column, which is not a valid usage. This method is specified for the interface, but is not valid for this class.

Action: SetSourceSet should never be invoked for this class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15619: Inconsistent filter with a clauseType of {0}

Cause: The Filter.getFilterType method was called, but the clause type was not a filter type.

Action: Ensure that the filter has a type of SnpPopClause.CLAUSE_TYPE_FILTER or SnpPopClause.CLAUSE_TYPE_JRN_FILTER.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15620: Execution location is null. Target technology cannot be determined

Cause: The execution filter for the location was not set.

Action: The execution location should be set in the Filter constructor or by invoking setExecutionLocation.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15621: Attached dataStore is null. Target technology cannot be determined

Cause: The attached datastore for the execution location was not set.

Action: The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15622: Staging area does not have a logical schema. Target technology cannot be determined

Cause: The attached datastore for the execution location was not set.

Action: The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15623: Invalid technology for the given index type

Cause: The technology of the clause and index type do not match.

Action: Ensure that the index type technology matches the clause technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15624: Inconsistent join with clauseType = {0} and joinType = {1}

Cause: The join clause type is invalid.

Action: This exception is thrown from a deprecated method. Use isCross or isOrdered methods instead.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15625: Cannot set OdiDataType on a journalized source column

Cause: The setDataType method has been invoked for a journalized source column, but the datatype cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15626: Cannot set the length on a journalized source column

Cause: The setLength method has been invoked for a journalized source column, but the length cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15627: Cannot set the scale on a journalized source column

Cause: The setScale method has been invoked for a journalized source column, but the scale cannot be set for journalized columns.

Action: Do not invoke this method for a journalized column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15628: Cannot set the data type on a source column

Cause: The setDataType method has been invoked for a source column, but the datatype cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15629: Cannot set the length on a source column

Cause: The setLength method has been invoked for a source column, but the length cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15630: Cannot set the scale on a source column

Cause: The setScale method has been invoked for a source column, but the scale cannot be set for source columns.

Action: Do not invoke this method for a source column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15631: Connection information is not available.

Cause: The physical schema has not been set.

Action: Define physical and logical schemas.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15632: Column {0} may not be removed because it is mapped in interface {1}.

Cause: The specified target column is mapped in another interface. This dependency prevents removal of the column.

Action: Only remove a column after mapping dependencies have been removed.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15633: Data Type must be set first.

Cause: Data Type is null.

Action: Set Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15634: Length is not allowed for the current Data Type

Cause: Data Type doesn't support length.

Action: Check Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15635: Scale is not allowed for the current Data Type.

Cause: Data Type doesn't support scale.

Action: Check Data Type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15636: Cannot change the column because it's not a temporary column.

Cause: Column isn't temporary.

Action: Check column state.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15637: Execution location must be either null or target.

Cause: Wrong Execution location state.

Action: Check Execution location.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15638: Scenario {0} contains invalid characters. Try {1}.

Cause: String contains invalid characters.

Action: Check scenario name.
Level: 32

Type: ERROR

Impact: Other

ODI-15639: Scenario version is not set.

Cause: Scenario version is not set.

Action: Set scenation version.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15640: No Scenario was found through the Tag : {0}.

Cause: No Scenario was found.

Action: Check tag.
Level: 32

Type: ERROR

Impact: Other

ODI-15641: The refresh SQL statement of a variable cannot contain sequence references when the variable is added to a load plan.

Cause: SQL statement contains sequence references.

Action: Check refresh SQL statement.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-15642: Scenario name must be {0} characters long max.

Cause: Scenario name is too long.

Action: Check name length.
Level: 32

Type: ERROR

Impact: Other

ODI-15643: No Physical Mapping Design from Mapping: {0}.

Cause: Cannot find any Physical Mapping Design from Mapping.

Action: Check there is valid Physical Mapping Design.
Level: 32

Type: ERROR

Impact: Other

ODI-15644: The physical data server for the source code and for sequqnce(s) {0} is not the same, this may result in the same sequence value being used for each row.

Cause: The sequence may be remote so a single nextval is calculated and reused per row.

Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 32

Type: INFO

Impact: Other

ODI-15645: The physical data server for the target code and for sequence(s) {0} is not the same, this may result in the same sequence value being used for each row.

Cause: The sequence may be remote so a single nextval is calculated and reused per row.

Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 32

Type: INFO

Impact: Other

ODI-15700: Exception thrown in the Odi shortcut service: {0}

Cause: An exception was thrown while materializing a shortcut object.

Action: Check the root cause.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-16000: Dataset has no sources: {0}

Cause: The Dataset has no source or the source is not available.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16001: Dataset {0} contains only one source.

Cause: The Dataset has only one source.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16002: Dataset has added default join condition with cartesian product: {0}

Cause: Dataset has added default join condition with cartesian product.

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16003: Multiple joins in the same dataset have the same order number: {0}

Cause: Multiple joins in the same dataset have the same order number.

Action: Check the order numbers of join components in the dataset.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16004: ANSI join: {0} has no user-defined order. The default order -1 (meaning "random order") is assigned.

Cause: An ANSI join component does not have a join order assigned to it.

Action: Assign an order number that is not -1.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16005: Join component inside dataset has no valid source references in the join condition. Join: {0} , condition = {1}.

Cause: Join component inside dataset has no valid source references in the join condition.

Action: Check source references in the join condition.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16006: Join component inside dataset has only one source references in the join condition, must have at least 2 references. Join: {0}, condition = {1}

Cause: Join component inside dataset has only one source references in the join condition, must have at least 2 references.

Action: Check join condition.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16008: There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.

Cause: There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.

Action: Check both the join condition references and the user order numbers.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16009: Lookup component creation is not complete: it misses either driving and/or lookup source information.

Cause: Lookup component: {0} in dataset: {1} is incomplete. (Driving source: {2}, lookup source: {3})

Action: Set the missing driving and/or lookup source on the lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16010: Dataset has sources that are not referenced by any join condition. Dataset: {0} , unconnected sources: {1}.

Cause: Dataset has sources that are not referenced by any join condition.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16011: INTERNAL ERROR: Dataset error when connecting joins in order. Cannot find source for join: {0}, referenced source name: {1}.

Cause: Dataset error when connecting joins in order. Cannot find source for join.

Action: Check sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16012: Cannot find ordered join connection in dataset for: {0}

Cause: Cannot find ordered join connection in dataset.

Action: Check ordered join connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16013: Cannot find a valid pairwise tree of join connections for dataset: {0} unconnected join: {1} ({2})

Cause: Cannot find a valid pairwise tree of join connections for dataset.

Action: Check join connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16014: Cannot find a valid pairwise tree of join connections for dataset: {0}

Cause: Cannot find a valid pairwise tree of join connections for dataset.

Action: Check join connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16015: Missing expression for aggregate component {0}, attribute: {1}

Cause: Missing expression for aggregator attribute.

Action: Check aggregator attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16016: Could not find an output signature for point: {0}

Cause: Could not find an output signature for point.

Action: Check output signature for the connection point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16017: The join component: {0} has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.

Cause: The join component has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.

Action: Check the join component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16018: The join condition for component: {0} only references {1} sources, but there are {2} input connector points. Expression text: {3}

Cause: The number of references sources is less than the number of input connector points.

Action: Check the join condition and input connector points.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16019: Set component output attribute {0} contains {1} expressions, but there are only {2} input connector points.

Cause: The number of input expressions is greater than the number of input connector points.

Action: Check expressions and input connector points.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16020: Set component output attribute expression for attribute: {0} does not have a scoping input connector point specified. Set component input expressions must have an associated scoping input connector point.

Cause: A scoping input connector point need to be specified.

Action: Check If set component input expressions have an associated scoping input connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16021: The immediate downstream node {0} of the AP node {1}, which uses a push style LKM, is not a target.

Cause: A push style LKM is assigned to an AP node but its immediate downstream node is not a target.

Action: Either change the LKM to a pull style LKM or move some physical nodes to source execution unit(s).
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16022: Set component output attribute: {0} does not have an expression that references through input: {1}.

Cause: Not all input connector points have been referenced by one expression.

Action: Check input connector points and expressions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16023: Expression cross reference object is null: {0}.

Cause: Expression cross reference object is null.

Action: Check expression cross reference object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16024: The expression contains unresolved attribute references. {0} Expression: {1} Unresolved identifiers: {2}.

Cause: The expression contains identifiers that were not resolved as attribute references.

Action: Check all identifiers in the expression for accessibility through a valid input connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16025: An access point (AP) node has been created in the physical graph, but it does not have any columns: {0}.

Cause: ERROR: An access point (AP) node has been created in the physical graph, but it does not have any columns.

Action: Check access points.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16026: Cannot move an existing physical node to a different physical design! Node: {0}.

Cause: Cannot move an existing physical node to a different physical design! .

Action: The action attempted is not supported.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16027: No path exists from physical node: {0} to: {1}.

Cause: No path exists between physical nodes.

Action: Check paths between physical nodes.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16028: Expression push is not allowed because it would push the expression through projector node: {0}.

Cause: Expression push is not allowed because it would push the expression through projector node.

Action: The action attempted is not supported.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16029: Expression {0} ({1}) owned by: {2} has blank value, but a non-blank value is required.

Cause: Expression has blank value, but a non-blank value is required.

Action: Check the expression text.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16030: An attribute expression must reference only one projector or joiner source. Attribute: {0}.

Cause: An attribute expression must reference only one projector or joiner source.

Action: Check attribute expressions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16031: The lookup component must have a driver and a lookup source input connection.

Cause: The lookup component is not properly connected, it must have 2 input connections.

Action: Connect the lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16032: Unsupported component type: {0}: component: {1} in dataset: {2}.

Cause: The dataset does not support the component type.

Action: Remove the component from the dataset.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16033: Aggregate filter: {0} is not supported in dataset: {1}.

Cause: The dataset does not support aggregate filters.

Action: Remove the aggregate filter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16034: A transparent target LKM was picked for: {0}, but the AP node has more than one downstream target component.

Cause: An AP node with a transparent target LKM can only have one downstream target.

Action: Pick a different LKM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16035: Target node {0} has assigned IKM {1}. The IKM will be ignored.

Cause: A target node that is loaded by an upstream AP node with a transparent target LKM assigned does not need an IKM assigned, since the loading functionality will be handled by the LKM transparent push.

Action: Set IKM to null.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16036: No target connected to AP node: {0} with SQL multi-connect LKM assigned.

Cause: An AP node with SQL multi-connect LKM assigned has no target.

Action: Add a target component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16037: Only one target allowed for AP node: {0} with SQL multi-connect LKM assigned.

Cause: An AP node with multi-connect LKM assigned cannot have multiple targets.

Action: Pick different LKM, or remove all but one of the targets in the mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16038: No extra logical components are allowed downstream from AP node: {0} with SQL multi-connect LKM assigned. The AP node must have a direct connection to target.

Cause: An AP node with multi-connect LKM assigned must be connected directly to the target, with no intervening nodes.

Action: Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16039: The AP node: {0} has a transparent target LKM assigned, but it is not connected directly to the target.

Cause: An AP node with transparent target LKM assigned must be connected directly to the target, with no intervening nodes.

Action: Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16040: Non-ANSI full outer join for component: {0} is not supported.

Cause: Full outer join is set to generate non-ANSI syntax.

Action: Check the box for "Generate ANSI Syntax" under Join properties.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16041: The manual group by clause is missing a required attribute: {0}

Cause: The maual group-by expression is missing one or more attributes required for the SQL group-by clause.

Action: Edit the manual group-by expression to included the missing attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16042: The expression for attribute: {0} does not contain an aggregate function, but the group by column setting is NO. Non aggregate attributes should be part of the group-by clause.

Cause: The group-by column setting for an attribute is NO, but it should be part of the group-by clause because the expression does not contain an aggregate function.

Action: If the attribute expression does not contain an aggregate, set the group by column setting to YES.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16043: The expression for attribute: {0} contains an aggregate function, but the group by column setting is YES. Only non aggregate attributes should be included in the group-by clause.

Cause: The group by column setting for an attribute is YES, but it should not be part of the group-by clause because the expression contains an aggregate function.

Action: If the attribute expression contains an aggregate, set the group by column setting to NO.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16044: The having clause references aggregate attribute: {0}, but an aggregate function is not specified.

Cause: An aggregated attribute is used in a having clause without an aggregate function.

Action: If the having clause references an aggregated attribute, include the aggregate function used with that attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16045: Input connector point {0} is not referenced by any attribute expression. That input to the set component is unused.

Cause: An input connector point for a set component is unused because no attribute expressions reference attributes scoped through that connector.

Action: At least one attribute expression should reference an attribute through the input connector in order to use that input to the set.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16046: Set components must have a minimum of two input connector points.

Cause: The set component has less than two input connector points.

Action: Add an input connector point. Set components must have at least two sources.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16047: Set component output attribute: {0} must have a non empty expression for input connector point {1}.

Cause: The number of input expressions is less than the number of input connector points.

Action: Specify a non empty expression for each input. Specify null if no attribute reference is used.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16048: Reusable mapping component: {0} must have a connection for input connector point {1}.

Cause: An input connector point is not connected to another map component.

Action: Connect the input connector point to a source component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16049: Reusable mapping component {0} has one or more output connector points, but none are connected or contain target components. DML cannot be generated without a target component connected downstream or within the reusable mapping.

Cause: None of the output connector points for the reusable mapping component are connected or contain target components.

Action: Add a connection for at least one output connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16050: Native sequence and ORDER BY operation are performed on the same flow. This might not be allowed in some technologies such as Oracle.

Cause: Sequence is used before order by, this is now allowed in Oracle.

Action: Remove sorter component or place sorter in an execution unit different from the sequence expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16051: The Sub select option may not be set for reusable mappings having an input signature.

Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if an input signature is present.

Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16052: The Sub select option may not be set for reusable mappings having more than one output signature.

Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if more than one output signature is present.

Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16053: Mixed non-ordered (outer) join and ordered join is not supported.

Cause: Outer join is set to non-ordered.

Action: Change the join to ordered join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16054: An unparsed identifier, {0}, was found in the aggregate HAVING clause. This identifier was not found in any other aggregate or group by expressions.

Cause: An identifier was found in the HAVING clause, but is invalid because it is not present in any aggregation or group by expression.

Action: Remove this expression from the HAVING clause or use it in one of the aggregate output attribute expressions.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16055: Reusable mapping {0} for reusable mapping component {1} contains errors or warnings.

Cause: A reusable mapping used by this mapping has errors or warnings.

Action: See following error or warning messages regarding the reusable mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16056: The driver connection for lookup component {0} is not connected to any source.

Cause: A connection has not been made between the source and driving connection of the lookup component.

Action: Connect a source to the lookup component driver connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16057: The lookup connection for lookup component {0} is not connected to any source.

Cause: A connection has not been made between the source and lookup connection of the lookup component.

Action: Connect a source to the lookup component lookup connection.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16058: Output signature {0} of reusable mapping {1} is not connected to any input source.

Cause: An output signature is not connected to any upstream component.

Action: Connect the output signature to an upstream component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16059: Error adding lines to task container for KM {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16060: Error finding helper component KM for AST processing of a node with 11g KM assigned: node={0}, helper KM={1}, error={2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16061: Error when calling generation delegate for component KM {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16062: Cannot create node variable binding map for component KM {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16063: No target multi-connect IKM found when processing an AP node with a SQL multi-connect LKM assigned.

Cause: A multi-connect IKM could not be found for a target.

Action: Check the target IKM assignment.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16064: When processing an AP node with SQL multi-connect LKM assigned, the downstream target node does not have a multi-connect IKM assigned.

Cause: The IKM assigned to the target is not a multi-connect IKM. If an AP node uses a multi-connect LKM, a multi-connect IKM is required on the target.

Action: Assign a multi-connect IKM to the target.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16065: Cannot get an entity manager for the mapping object. The entity manager must be set for the owning mapping or reusable mapping by calling IOdiEntityManager.persist() or Mapping.setEntityManager(), before this operation can be done. Mapping object= {0}

Cause: An mapping operation is being performed that requires the mapping to resolve a reference, but the mapping entity manager has not been set.

Action: Set the entity manager for the mapping, by calling IOdiEntityManager.persist() or Mapping.setEntityManager().
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16066: Target datastore column {0} is mandatory column and should be mapped.

Cause: Missing expression for mandatory target datastore column.

Action: Check target datastore mandatory column expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16067: The Sub select option may not be set for reusable mappings having no output signature.

Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if no output signature is present.

Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16068: A parse error was encountered when parsing the expression: {0}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.

Cause: Expression is syntactically incorrect.

Action: Make sure the expression is well-formed.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16069: Technology {0} does not support the WHERE clause and cannot process the join.

Cause: Technology "Where" indicator is set to false.

Action: Check the technology setting or remove the join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16070: Ordered joins are not supported in technology {0}.

Cause: Technology Join Support Ordered indicator is set to false.

Action: Set join to non-ordered (Generate ANSI syntax = false).
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16071: Cross joins are not supported in technology {0}.

Cause: Technology Cross Join indicator is set to false.

Action: Set join type to non-cross join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16072: Natural joins are not supported in technology {0}.

Cause: Technology Natural Join indicator is set to false.

Action: Set join type to non-natural join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16073: Non-ordered natural joins are not supported.

Cause: Natural Join is set to non-ordered (generate ANSI syntax = false).

Action: Set 'Generate ANSI syntax' to true.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16074: Non-ordered joins are not supported in technology {0}.

Cause: Join is set to non-ordered (generate ANSI syntax = false).

Action: Set join to ordered (Generate ANSI syntax = true).
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16075: Non-ordered outer joins are not supported in technology {0}.

Cause: Outer Join is set to non-ordered (generate ANSI syntax = false).

Action: Set 'Generate ANSI syntax' to true.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16076: Outer joins are not supported in technology {0}.

Cause: Join is set to outer join.

Action: Set join to non-outer join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16077: Full outer joins are not supported in technology {0}.

Cause: Join is set to full outer join.

Action: Set join to non-full outer join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16078: Inner joins are not supported in technology {0}.

Cause: Join is set to inner join.

Action: Set join to non-inner join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16079: Reusable mapping {0} is not compatible with dataset {1}. A reusable mapping within a dataset must have no input signatures and exactly one output signature.

Cause: An incompatible reusable mapping is being added to the dataset. The reusable mapping must have no input signatures and exactly one output signature.

Action: Choose a different compatible reusable mapping or modify the resuable mapping to contain just a single output signature and no input signatures.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16080: Mapping component type {0} is not supported within a {1}.

Cause: An unsupported component is being added to a mapping or composite component.

Action: Use a supported component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16081: Physical Mapping Design {0} cannot be calculated with no optimization context.

Cause: The optimization context of the physical design is not set, or it becomes invalid because the referenced context is deleted.

Action: Check the optimization context of the physical design and specify an appropriate context.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16082: The physical node {0} cannot be supported by technology {1} on execution unit {2} of mapping {3}.

Cause: The physical node cannot be moved to the execution unit because its technology does not support the node.

Action: Do not move the physical node to this execution unit.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16083: Input Attribute {0} of reusable mapping component {1} does not have an expression to connect it to any source, but is referenced in the reusable mapping.

Cause: An input signature attribute in a reusable mapping is referenced by another component, but the input is not connected in the parent mapping.

Action: Assign an expression to the reusable mapping component input attribute.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16084: The proposed connection would create a circular graph.

Cause: The proposed connection would create a logical graph which contains a circular path, which connects a source component through some other components and back to itself.

Action: Fix the connections to get rid of the circular path.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16085: Cannot set an expression for attribute {0} because the attribute was not found. Available attributes: {1}.

Cause: SetAttributeExpressionText was called with an invalid attribute name.

Action: Specify a valid attribute name.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16086: Set component {0} input connector point {1}: set operator {2} is not valid for {3} technology.

Cause: The set operation chosen for the connector point is not valid for the technology.

Action: Choose a set operation valid for the technology.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16087: Generation of set component {0} failed because of an incompatibility with the technology.

Cause: The set operation chosen for the connector point is not valid for the technology.

Action: Choose a set operation valid for the technology.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16088: Map component {0}, attribute {1} contains an aggregate function. Aggregate functions are only supported by the aggregate component.

Cause: An aggregate function is used in the expression of a datastore attribute. The Datastore component does not support aggregate functions and will not generate the required GROUP BY clause.

Action: Create an aggregate component to contain the aggregate function.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16089: "Cannot connect to component {0}, no input connector points are available.

Cause: An attempt was made to connect to the component, but no input connector points are available.

Action: Fix the connection graph.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16090: "Attempt connect a component to itself. from={0}, to= {1}

Cause: An attempt was made to connect an output of the component back into an input of the same component.

Action: Do not connect a component to itself.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16091: Expression component {0} has no attributes.

Cause: An expression has no attributes. Expression components are projectors and must have attributes in order to be referenced by downstream components.

Action: Add one or more attributes to the expression component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16092: Datastore component {0}, attribute {1} is mandatory but not active.

Cause: A datastore attribute is mandatory, but has been tagged as non active.

Action: Set the mandatory attribute to active.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16093: The subselect option is not valid for reusable mapping component {0} because the reusable mapping contains an expression referencing a native sequence.

Cause: The reusable mapping has an expression referencing a native sequence, and the subselect option has been chosen for the reusable mapping component.

Action: Avoid using the subselect option for reusable mappings having expressions which reference native sequences.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16094: Physical node {0} is associated with logical schema {1}, but it is not mapped to a physical server in context {2}.

Cause: The physical schema of the physical node cannot be resolved, as its logical schema is not mapped in the execution context.

Action: Associate the logical schema with a physical schema in the context specified.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16095: "Scenario Generation failed for mapping {0} because no physical design was found.

Cause: No physical design was found during scenario generation for a mapping.

Action: Correct any errors preventing physical design generation.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16096: A mapping with name {0} already exists in folder {1}.

Cause: A mapping with the same name already exist in the same folder.

Action: Use a different name for the mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16097: A reusable mapping with name {0} already exists in folder {1}.

Cause: A reusable mapping with the same name already exist in the same folder.

Action: Use a different name for the reusable mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16098: A reusable mapping with name {0} already exists in global project.

Cause: A reusable mapping with the same name already exist in the global project.

Action: Use a different name for the reusable mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16099: Name {0} already exists in {1} {2}.

Cause: The given name is already used. Object name needs to be unique with the parent object.

Action: Provide a different name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16100: Name cannot be an empty string.

Cause: Name of an object cannot be empty.

Action: Provide a name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16101: Name {0} contains invalid characters. Only letters, digits or underscore characters are allowed.

Cause: Proposed name contains invalid characters, such as space. Only letters, digits or underscore characters are allowed.

Action: Provide a different name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16102: Name {0} contains invalid characters. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.

Cause: Proposed name contains invalid characters, such as space. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.

Action: Provide a different name for the object.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16103: Name {0} is longer than {1} characters.

Cause: Proposed name is too long.

Action: Shorten the proposed name.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16104: The expression for attribute {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.

Cause: An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.

Action: Check all input connector points for correct upstream connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16105: Expression of attribute {0} does not refer to any upstream attribute. If {0} is an attribute of an input signature component, the corresponding attribute of the reusable mapping component does not have an expression text, or the input connector point of the reusable mapping component is not properly connected.

Cause: The expression is not set or the input connector point is not properly connected.

Action: Verify the expression or the connection to the input connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16106: No columns are set to update column in Target datastore {0}.

Cause: The update indicator is not set in target datastore.

Action: Verify the targetDatastore attribute and set the update indicator.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16107: The data type for datastore component {0}, attribute {1} is not defined.

Cause: The data type of the column to which the datastore attribute is bound is null. This may occur when reverse engineering an unknown data type.

Action: Add the data type to the technology and set the data type of the column.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16108: Preset Staging Location explicitly set to target location. This may result in the addition of another execution unit and decreased performance. Consider using the default Preset Staging Location, which is already set to use the target location.

Cause: The preset staging location has been explicitly set, instead of using the default value. When an explicit value is set, and execution unit will be created, even if the location is the same as the target location.

Action: Consider using the default value for the preset staging location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16109: Encountered {0} at line {1} column {2}. Was expecting one of: {3}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.

Cause: A parser error was encountered when parsing the expression.

Action: Fix the syntax of the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16110: Non-ANSI natural join for component: {0} is not supported.

Cause: Natural join is set to generate non-ANSI syntax.

Action: Check the box for "Generate ANSI Syntax" under Join properties.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16111: Cannot remove {0} connector point for component {1} due to minimum connector point count violation.

Cause: Removal of connector point will result in connector point count less than minimum count.

Action: Do not remove connector point.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16112: Reusable mapping component {0}, output connector point {1} is not connected.

Cause: An output connector point of a reusable mapping component is not connected.

Action: Check that connections from all output connector points are optional.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16113: Mapping component {0} has no input or output connections.

Cause: An mapping component has not been connected.

Action: Connect the component to a source and/or target component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16114: Error when ordering the components for physical design:{0}, component re-ordering is not valid. A skipped component was not able to be placed in an execution unit because of dependency errors.

Cause: When attempting to reorder the component nodes in the physical graph, an eror was found.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16115: Cannot reorder an outer join node around another kind of node.

Cause: Cannot reorder an outer join node around another kind of node.

Action: Cannot reorder an outer join node around another kind of node.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16116: Cannot reorder a join around another join if one of the joins does not have at least 2 references in its join condition.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16117: Cannot reorder a join around another join if one is generating ANSI and the other is not.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16118: Cannot reorder a join around another join if one is a left or right outer join and the other is not the same type, for non-ANSI joins.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16119: Cannot reorder a join around another join if either one is a left outer or right outer join, for ANSI joins.

Cause: Illegal reordering.

Action: Do not reorder the component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16120: Warning: Target Load Order -- Child component is ordered before parent component.

Cause: A datastore component with foreign key relationships is ordered before its parent datastore component.

Action: Change the load order to put parent component before child component or keep the load order knowing that it may result in error in loading due to missing primary record.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16121: Error: Target Load Order -- Load order is not consistent with processing graph from source to target. Please modify the graph or change the load order.

Cause: A target component is ordered before its source component.

Action: Change the load order to put source component before target component or change the mapping design.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16122: Cannot create physical design due to mapping validation errors: {0}.

Cause: Validation errors.

Action: Fix the mapping.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16123: Node pushed upstream causes conflicts due to multiple upstream connections from different execution units. Pushed node={0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16124: Not allowed to reorder node {0}: {1}

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16125: Not allowed to push node {0} past node {1}: {2}

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16126: Physical graph re-ordering is causing a referencing problem for component: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16127: Cannot reorder component that is not a selector:{0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16128: Cannot reorder component that does not have at least one input and output connector point: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16129: Cannot reorder a component that has multiple downstream targets: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16130: Cannot reorder an outer join component: {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16131: The node will not be moved.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16132: Cannot reorder node {0} downstream of {1}, since {1} has expression references to {0}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16133: Cannot reorder node {0} upstream of {1}, since {0} has expression references to {1}.

Cause: Illegal node push.

Action: Do not push the node to this location.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16134: Cannot set journalizing for datastore component {0}, since its bound datastore is not journalized.

Cause: Cannot set journalizing since the bound datastore is not journalized.

Action: Make sure the bound datastore is CDC enabled.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16135: File technology has limited capability to serve as a staging area. Consider switching the staging area to another technology, such as in-memory engine.

Cause: File technology unit set as staging area.

Action: Set staging area to non-file technology.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16136: Join {0} has type {1}, so its non-blank {2} will be ignored.

Cause: With Join Type CROSS or NATURAL, the Join Condition will be ignored.

Action: Check the Join Type. If correct, set the Join Condition to blank.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16137: IKM {0} is selected for physical node {1}, but the corresponding logical component {2} of reusable mapping {3} is not marked as derived sub-select.

Cause: An IKM is used for extraction of a physical node, but derived sub-select is not enabled.

Action: Change the KM selected for the physical node, or mark the logical component as derived sub-select.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16138: Internal error occurred during mapping metadata conversion. Please check the original 11g interface to see if it is complete and valid. Only interfaces that pass validation are supported during the upgrade process. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.

Cause: Internal error occurred or unexpected exception received during mapping metadata conversion.

Action: Make sure the original 11g interface is valid. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16139: Execution unit {0} does not have a location.

Cause: The execution unit does not have a logical schema selected for its location.

Action: Select a logical schema as the location of the execution unit.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16140: Mapping component {0} must have a connection for input connector point {1}.

Cause: An input connector point is not connected to another map component.

Action: Connect the input connector point to a source component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16141: Mapping component {0} must have a connection for output connector point {1}.

Cause: An output connector point is not connected to another map component.

Action: Connect the output connector point to a downstream component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16142: Cannot bind a datastore component to file model datastore {0}, use a file component instead.

Cause: Attempt to bind a datastore component to a datastore with file technology.

Action: Use a file component instead, and bind the file object to it.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16143: Cannot bind a file component to non-file model datastore {0}, use a datastore component instead.

Cause: Attempt to bind a file component to a datastore with non-file technology.

Action: Use a datastore component instead, and bind the file object to it.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16144: The expression cannot be pushed to execution unit {0} because its references would be out of scope.

Cause: Illegal push-to target execution unit for expression.

Action: Do not push the expression to this execution unit.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16145: The lookup match nth rows for lookup component {0} should be positive number.

Cause: The match nth row property has not been correctly configured for lookup component.

Action: Correct the match nth row property for lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16146: The join condition for component {0} contains a filter expression that does not reference a different schema on each side of the equality operator: {1}. Filter expressions may not behave as expected in joins.

Cause: The join condition contains a filter expression. Filter expressions may not be effective in joins, and are inherently problematic in outer joins.

Action: Move the extra filter condition to a separate filter component to eliminate interaction with the join.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16147: The join condition for component {0} does not contain an identifiable equality operator to join the input sources: {1}.

Cause: The join condition may be missing an equality operator needed to match rows when joining the input sources.

Action: Check the join expression for a valid equality operator.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16148: The size of map attribute {0} ({1}) is greater than the size of attribute {2} ({3}), to which it is mapped. Truncation or runtime errors are possible, depending on the technology.

Cause: A map attribute is mapped to an attribute of smaller size. This may result in data truncation or DML errors.

Action: Verify the size of both attributes and make any adjustments necessary to avoid truncation. Add an expression to explicitely truncate the data if necessary.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16149: For lookup component {0}, the option {1} for non matching rows may only be selected if option {2} is selected for multiple matching rows.

Cause: The no match rows property has not been correctly configured for lookup component. It may only be used if the multiple matching rows option specifies all rows.

Action: Correct the no match rows property for lookup component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16150: Multiple non-ANSI outer joins exist within a dataset for the same datastore {0}.

Cause: A datastore is outer joined to more than one datastore. This may result in execution errors.

Action: Create joins outside of datasets.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16151: The context value {0} for map component {1} does not map to a physical location.

Cause: The forced context value of a data storage component, combined with the model and logical schema, does not map to a physical schema. A map physical design cannot be created.

Action: Use the logical schema editor or SDK to set a physcial schema for the chosen component context.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16152: Error processing KM target expression for mapping: {0}, KM line: {1}, KM error: {2}

Cause: An exception was thrown during KM processing of the target expression for a particular line.

Action: Review the KM line and error to determine the cause.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16153: Error processing KM source expression for mapping: {0}, KM line: {1}, KM error: {2}

Cause: An exception was thrown during KM processing of the source expression for a particular line.

Action: Review the KM line and error to determine the cause.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16154: No expressions have been defined on the attributes for map component {0}.

Cause: A target datastore is connected, but none of its attributes have expressions defined.

Action: Create expressions to map one or more attributes to a source.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16155: Join or Lookup component {0} is inactive. Components joining sources must be active.

Cause: A join or lookup component has been set to inactive. Components which join sources must be active because all sources will not be in scope without the join.

Action: Set the component to active.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16156: Join type {0} in {1} cannot be supported due to circular relationships in Dataset {2}.

Cause: If a circle of relationships exist in a Dataset, one of the joinis must be reduced to a filter. The join type defined on it could be lost.

Action: Examine the logic in the Dataset and try to reduce the number of outer joins if possible as the currently specified logic in Dataset cannot be translated to a SQL query.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16157: Ambiguous expression reference due to split path. {0} Expression: {1}, Available paths: {2}

Cause: The connection path to the referenced attribute is split and the reference does not include a path specifier with a sufficient number of connector names to specify an unambiguous path..

Action: Add a path specifier qualifier to the expression reference.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16158: Component in path specifier has multiple output connector points. {0} Expression: {1}, Component={2}

Cause: A map component specified in the expression path specifier has multiple output connector points.

Action: A specific connector point must be specified in the path specifier.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16159: Path specifier contains nonexistent identifier. {0} Expression: {1}, Identifier={2}

Cause: An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.

Action: Fix the path specifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16160: Path specifier contains out-of-scope identifier. {0} Expression: {1}, Identifier={2}

Cause: An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.

Action: Fix the path specifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16161: No matching path can be found. {0} Expression: {1}

Cause: A path specifier is included in the expression, but it does not match any actual path in the map.

Action: Fix the path specifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16162: Final parsing of {0} command {0} failed with exception {1}.

Cause: A final parsing of the command was performed and hit an error.

Action: Report as an ODI bug.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16163: Cannot parse identifier "{0}" because there are multiple instances of "{1}" in the mapping.

Cause: An identifier in the expression can not be parsed because it refers to multiple components.

Action: Fix the identifier in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16164: Internal Error: Cannot find input query select item for expression cross reference: {0}

Cause: The code generator cannot generate code for the map expression cross reference because the upstream query does not include the referenced object.

Action: Fix the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16165: An attribute input expression for a set component must reference upstream attributes through only one input connector point. Attribute: {0}.

Cause: An attribute input expression for a set component must reference upstream attributes through only one input connector point.

Action: Check input expressions for the set component.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16166: Cannot parse the syntax of user defined function or language element {0}: {1}.

Cause: The syntax text of the user defined function or language element cannot be parsed by the code generator.

Action: Check the syntax text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16167: The function call {0} does not match the number of parameters defined for user defined function or language element {1}.

Cause: The function call in the expression text does not match the number of parameters of the user defined function or language element.

Action: Check the function call in the expression.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16168: Invalid parameter syntax in the syntax text of user defined function or language element {0}: {1}.

Cause: One of the parameters in the syntax text contains invalid parameter syntax.

Action: Check the syntax text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16169: Invalid parameter syntax in the implementation text of user defined function or language element {0}: {1}.

Cause: One of the parameters in the implementation text contains invalid parameter syntax.

Action: Check the implementation text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16170: Cannot locate calling parameter {0} in implementation text from the syntax text of user defined function or language element {1}.

Cause: The calling parameter in the implementation text does not match any parameters that are defined in the syntax of the user defined function or language element.

Action: Check the implementation text of the user defined function or language element.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16171: KM {0} is not valid for physical node {1}. The default KM is {2}.

Cause: The KM being set is not valid for the physical node.

Action: Set the KM using the default KM or another compatible KM.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-16172: An expression in map component {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.

Cause: An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.

Action: Check all input connector points for correct upstream connections.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-17500: Invalid old password.

Cause: Old password did not match current password.

Action: Provide the correct password.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17501: Temporary table has no column.

Cause: No column have been defined for the temporary table.

Action: Define a column mapping to the temporary table.
Level: 32

Type: ERROR

Impact: Other

ODI-17502: No next value returned.

Cause: No sequence next value was found for given context code.

Action: Verify sequence definition or context code.
Level: 32

Type: ERROR

Impact: Other

ODI-17503: Internal error: object ConnectConnection

Cause: Missed connection.

Action: Try reconnect.
Level: 32

Type: ERROR

Impact: Other

ODI-17504: An ordered join references the same table twice (directly or indirectly).

Cause: A same table was referenced twice by a join.

Action: Check interface definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17505: An ordered join references the same table twice through another join.

Cause: A join was referencing the same table twice through another join.

Action: Check interface definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17506: Variable has no value

Cause: Variable had no value.

Action: Provide value for variable.
Level: 32

Type: ERROR

Impact: Other

ODI-17507: Key does not exist

Cause: Key was unknown.

Action: Provide a known key.
Level: 32

Type: ERROR

Impact: Other

ODI-17508: No conversion for data type "{0}" from source technology "{1}" to destination technology "{2}"

Cause: No data type conversion between technology was found.

Action: Define corresponding data type conversion.
Level: 32

Type: ERROR

Impact: Other

ODI-17509: Query to access value for specific sequence {0} has failed. Query="{1}"

Cause: Query for sequence has failed.

Action: Check sequence definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17510: Driver does not exist.

Cause: Driver was not found.

Action: Check repository.
Level: 32

Type: ERROR

Impact: Other

ODI-17511: No value to be set to variable ''{0}''.

Cause: No value was returned to be set to the variable.

Action: Check variable value.
Level: 32

Type: ERROR

Impact: Other

ODI-17512: Sequence is already locked

Cause: The sequence was already locked.

Action: Unlock the sequence.
Level: 32

Type: ERROR

Impact: Other

ODI-17513: Variable ''{0}'' does not exist.

Cause: Variable was not found.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Other

ODI-17514: Unrecognized Oracle Data Integrator built-in function: {0}

Cause: Oracle Data Integrator built-in function was not recognized.

Action: Check function syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17515: Invalid loading command (INSERT,UPDATE...).

Cause: Loading command was invalid.

Action: Check loading command.
Level: 32

Type: ERROR

Impact: Other

ODI-17516: Internal error within the connection list

Cause: Internal error within the connection list.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17517: Error during task interpretation. Task: {0} {1} Text: {2}.

Cause: A task interpretation error has occured.

Action: Check tasks and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17518: Error while interpreting the user name.

Cause: User name interpretation has failed.

Action: Check user name.
Level: 32

Type: ERROR

Impact: Other

ODI-17519: Error while interpreting the URL

Cause: URL interpretation has failed

Action: Check URL.
Level: 32

Type: ERROR

Impact: Other

ODI-17520: Error while interpreting the password

Cause: Password interpretation has failed.

Action: Check password.
Level: 32

Type: ERROR

Impact: Other

ODI-17521: Error while interpreting the driver

Cause: Driver interpretation has failed.

Action: Check driver.
Level: 32

Type: ERROR

Impact: Other

ODI-17522: Empty column name are not allowed

Cause: A empty column name was found.

Action: Fill column name.
Level: 32

Type: ERROR

Impact: Other

ODI-17523: There is no connection for this logical schema / context pair: {0} / {1}.

Cause: No connection was found for this logical schema / context pair.

Action: Check schema and context assignment.
Level: 32

Type: ERROR

Impact: Other

ODI-17524: Cannot set an empty alias for a source table.

Cause: Source table''s alias was empty.

Action: Fill alias of source table.
Level: 32

Type: ERROR

Impact: Other

ODI-17525: Cannot set an empty source set name.

Cause: Source set name was empty.

Action: Fill alias of a source table.
Level: 32

Type: ERROR

Impact: Other

ODI-17526: Cannot set Longc value in a PopCol having a column

Cause: Cannot set Longc value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17527: Cannot set SourceDt value in a PopCol having a column

Cause: Cannot set SourceDt value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17528: Cannot set Scalec value in a PopCol having a column

Cause: Cannot set Scalec value in a PopCol having a column.

Action: Check interface`s columns.
Level: 32

Type: ERROR

Impact: Other

ODI-17529: Reference check failure

Cause: Reference check has failed.

Action: Check control conditions.
Level: 32

Type: ERROR

Impact: Other

ODI-17530: Incomplete join may result in partial cross join

Cause: An incomplete join was found.

Action: Check joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17531: KM already encrypted.

Cause: KM has been already encrypted.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-17532: KM not encrypted.

Cause: KM was not encrypted.

Action: Check KM.
Level: 32

Type: ERROR

Impact: Other

ODI-17533: Clause set to cross join on a technology that does not support cross joins.

Cause: Technology did not support cross joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17534: Clause set to full join on a technology that does not support full joins.

Cause: Technology did not support full joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17535: Clause set to outer join on a technology that does not support left outer joins or right outer joins.

Cause: Technology did not support left outer joins.

Action: Correct joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17536: Incomplete clause (Missing order number).

Cause: Order number was missing.

Action: Correct clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17537: Incomplete clause (table1 and/or table2 must be set).

Cause: Table1 and/or table2 were undefined.

Action: Set clause''s table1 and/or table2 tables.
Level: 32

Type: ERROR

Impact: Other

ODI-17538: Filter is not properly set (The table must be defined)

Cause: The table must have been set.

Action: Set filter''s table.
Level: 32

Type: ERROR

Impact: Other

ODI-17539: Clause is ordered on a technology that does not support it

Cause: Technology did not support ordering.

Action: Remove ordering.
Level: 32

Type: ERROR

Impact: Other

ODI-17540: Connection is not set for this source set {0}.

Cause: Source set''s connection was not set.

Action: Set connection.
Level: 32

Type: ERROR

Impact: Other

ODI-17541: Method SnpTrt::getAllTrtOfTypeForTechnosAndProject requires not null parameters for technologies

Cause: Method requires not null parameters

Action: Specify correct parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-17542: Sequence must be locked before using this function

Cause: Sequence was not locked.

Action: Lock sequence and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17543: Technology does not support joins

Cause: Technology did not support joins.

Action: Check technology and/or joins.
Level: 32

Type: ERROR

Impact: Other

ODI-17544: This Technology does not support the WHERE clause

Cause: Technology did not support the WHERE clause

Action: Check technology and/or clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17545: Technology not set for this source set {0}

Cause: Source set''s technology was undefined.

Action: Set technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17546: Specified variable not found in the Repository

Cause: Variable was not found in the Repository.

Action: Define variable and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17547: Data type "{0}" for the technology "{1}" does not exist.

Cause: Data type for the technology did not exist.

Action: Check data type and/or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17548: The file reverse-engineering is only possible for delimited files.

Cause: The file reverse-engineering was performed against a not delimited file.

Action: Use delimited files.
Level: 32

Type: ERROR

Impact: Other

ODI-17549: Source data type "{0}" for the technology "{1}" does not exist.

Cause: Source data type was not found.

Action: Check data type and/or technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17550: Missing default Physical Schema for Data Server "{0}"

Cause: Default Physical Schema was undefined.

Action: Specify default Physical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17551: Duplicate clause order numbers

Cause: Duplicated order numbers were found.

Action: Check clause definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17552: Duplicate join order numbers

Cause: Duplicated join order numbers were found.

Action: Check join.
Level: 32

Type: ERROR

Impact: Other

ODI-17553: Exceeded the maximum number of errors allowed.

Cause: The maximum number of errors allowed were exceeded.

Action: Check maximum error numbers.
Level: 32

Type: ERROR

Impact: Other

ODI-17554: Agent "{0}" does not exist.

Cause: Agent was not found.

Action: Check agent definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17555: You cannot unlock this object. Only the lock owners and Supervisors can unlock objects.

Cause: An attempt was made to unlock objects that were locked by another user.

Action: Login as Supervisor or as the lock owners and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17556: Error during decryption of text.

Cause: Text decryption has failed.

Action: Try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17557: No condition defined for this rule.

Cause: No condition have been defined for this rule.

Action: Define conditions.
Level: 32

Type: ERROR

Impact: Other

ODI-17558: The field for this rule is not specified.

Cause: The field was unspecified.

Action: Specify field for this rule.
Level: 32

Type: ERROR

Impact: Other

ODI-17559: The operator for this rule is not specified.

Cause: The operator was unspecified.

Action: Specify operator for this rule.
Level: 32

Type: ERROR

Impact: Other

ODI-17560: The value to test is not defined.

Cause: The value to test was not defined.

Action: Specify value.
Level: 32

Type: ERROR

Impact: Other

ODI-17561: This operator is not supported.

Cause: This operator was not supported.

Action: Correct operator.
Level: 32

Type: ERROR

Impact: Other

ODI-17562: This operator cannot be used with this field.

Cause: The operator could not be used with the given field.

Action: Correct operator.
Level: 32

Type: ERROR

Impact: Other

ODI-17563: There is no work repository matching the name "{0}".

Cause: Work repository was not found.

Action: Check work repository with the given name exists.
Level: 32

Type: ERROR

Impact: Other

ODI-17564: More than one work repository found with the name "{0}" for this master repository.

Cause: More than one work repository with the specified name was found for this master repository.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-17565: Scenario has been already encrypted. No encryption was performed.

Cause: Scenario has been already encrypted.

Action: Decrypt and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17566: Scenario is not encrypted. No decryption was performed.

Cause: Scenario was not encrypted.

Action: Check Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-17567: A Scenario generated from a Variable cannot be encrypted or decrypted.

Cause: An attempt was made to encrypte or decrypte a Scenario generated from a Variable.

Action: Change Scenario'' source component.
Level: 32

Type: ERROR

Impact: Other

ODI-17568: Could not connect to the database referenced by the context and the logical schema

Cause: Connection to the database failed.

Action: Check context and logical schema.
Level: 32

Type: ERROR

Impact: Network

ODI-17569: Unable to update sequence''s next value.

Cause: Updating sequence was not possible.

Action: Check sequence definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17570: Your text is too long. Please shorten it or choose the ''LONG TEXT'' datatype.

Cause: Text was too long.

Action: Shorten the text or choose the LONG TEXT data type.
Level: 32

Type: ERROR

Impact: Other

ODI-17571: Password does not respect the following rule: "{0}".

Cause: The password did not respect the rule.

Action: Choose another password.
Level: 32

Type: ERROR

Impact: Security

ODI-17572: This SnpFfValuee does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17573: This SnpFfValuem does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17574: This SnpFfValuew does not exist.

Cause: Value was not found.

Action: Check FlexField value.
Level: 32

Type: ERROR

Impact: Other

ODI-17575: SnpLicense does not exist.

Cause: SnpLicense was not found.

Action: Check License.
Level: 32

Type: ERROR

Impact: Other

ODI-17576: Unknown actual constraint type for an interface constraint.

Cause: Interface constraint type was unknown.

Action: Check constraint type.
Level: 32

Type: ERROR

Impact: Other

ODI-17577: Unknown variable data type.

Cause: Variable data type was unknown.

Action: Check variable data type.
Level: 32

Type: ERROR

Impact: Other

ODI-17578: Name "{0}" is already used.

Cause: Name was already used.

Action: Use another name or change mode of import.
Level: 32

Type: ERROR

Impact: Other

ODI-17579: Type of clause is not set.

Cause: Type of clause was not set.

Action: Set type of clause.
Level: 32

Type: ERROR

Impact: Other

ODI-17580: Type of join is not set.

Cause: Type of join was not set.

Action: Set type of join.
Level: 32

Type: ERROR

Impact: Other

ODI-17581: A non ordered clause is passed to the construction of ordered joins trees method.

Cause: A non ordered clause was passed to the construction of ordered joins trees method.

Action: Check clauses.
Level: 32

Type: ERROR

Impact: Other

ODI-17582: Missing order number for an ordered clause.

Cause: Clause order was not set.

Action: Set the clause order.
Level: 32

Type: ERROR

Impact: Other

ODI-17583: More than one unique constraint associated to an interface constraint.

Cause: More than one unique constraint associated to an interface constraint was found.

Action: Check constraints.
Level: 32

Type: ERROR

Impact: Other

ODI-17584: URL does not exist.

Cause: URL was not found.

Action: Check URL.
Level: 32

Type: ERROR

Impact: Other

ODI-17585: Key cannot be checked.

Cause: Key could not be checked.

Action: Check key definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17586: Field separator is mandatory for a delimited file.

Cause: Field separator was missing.

Action: Check separator and/or file type.
Level: 32

Type: ERROR

Impact: Other

ODI-17587: Object name "{0}" is too long for the technology "{1}" (Logical schema : "{2}" ; Context Code : "{3}")

Cause: Object name was too long.

Action: Correct object name.
Level: 32

Type: ERROR

Impact: Other

ODI-17588: Unable to load work repository info.

Cause: Work repository was not found.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-17589: Logical schema has not been specified for sequence "{0}"

Cause: Logical schema was not specified.

Action: Specify logical schema.
Level: 32

Type: ERROR

Impact: Other

ODI-17590: Code {0} for model "{1}" is already used by another model.

Cause: An already used code was assigned.

Action: Change code for model.
Level: 32

Type: ERROR

Impact: Other

ODI-17591: Name "{0}" is already used.

Cause: A name already used was assigned.

Action: Change name.
Level: 32

Type: ERROR

Impact: Other

ODI-17592: Object is not in execution work repository.

Cause: Object was not in execution work repository.

Action: Check object and/or repository.
Level: 32

Type: ERROR

Impact: Other

ODI-17593: Maximum number or source/target technologies exceeded. Current limit is {0}.

Cause: Maximum number or source/target technologies was exceeded.

Action: Check limit and number of technologies.
Level: 32

Type: ERROR

Impact: Other

ODI-17594: Cannot encrypte already encrypted action.

Cause: This action has been already encrypted.

Action: Skip encryption.
Level: 32

Type: ERROR

Impact: Other

ODI-17595: This action is not encrypted.

Cause: This action was not encrypted.

Action: Check parameters and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-17596: Query to retrieve value for native sequence "{0}" has failed Query="{1}"

Cause: Query has failed.

Action: Check query.
Level: 32

Type: ERROR

Impact: Other

ODI-17597: Cannot mix ordered and non-ordered join syntax within a dataset for technology.

Cause: Mixed join not allowed within a dataset.

Action: Change all joins in dataset to same join syntax (either ordered or non-ordered).
Level: 32

Type: ERROR

Impact: Other

ODI-17598: Non-ordered natural join is not supported.

Cause: Non-ordered natural join is not supported.

Action: Change natural join to use ordered syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17599: Ordered inner join is not supported.

Cause: Ordered inner join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17600: Ordered left outer join is not supported.

Cause: Ordered left outer join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17601: Ordered right outer join is not supported.

Cause: Ordered right outer join is disabled for technology.

Action: Change join type.
Level: 32

Type: ERROR

Impact: Other

ODI-17602: Non-ordered full outer join is not supported.

Cause: Non-ordered full outer join is not supported.

Action: Change full outer join to use ordered syntax.
Level: 32

Type: ERROR

Impact: Other

ODI-17603: Sql error checking a condition. {0}

Cause: Sql error checking a condition.

Action: Correct the Sql in the condition.
Level: 32

Type: ERROR

Impact: Other

ODI-17604: Reference column isn't associated with this instance of reference.

Cause: Reference column isn't associated with this instance of reference.

Action: Check reference column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17605: Column is not associated to this datastore.

Cause: Datastore doesn't have this column.

Action: Check datastore and column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17606: {0} already belongs to another OdiDataStore.

Cause: Object belongs to another datastore.

Action: Check object and datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17607: Parameter pReference is not an outbound reference for this OdiDataStore.

Cause: Parameter is not an outbound reference for OdiDataStore.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17608: Invalid technology for the given data type.

Cause: Invalid technology for the given data type.

Action: Check technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17609: Invalid data type code.

Cause: Invalid data type code.

Action: Check data type code.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17610: Found NULL in STEP_TYPE.

Cause: Step type is null.

Action: Check step type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17611: STEP_TYPE is not valid.

Cause: Step type isn't valid.

Action: Check step type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17612: MultiConnectionSupported is not settable for {0}.

Cause: MultiConnectionSupported is not settable.

Action: Check knowledge module.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17613: Cannot handle {0} of type {1}.

Cause: Cannot handle object.

Action: Check object's type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17614: Unknown key type: {0}.

Cause: Unknown key type.

Action: Check key.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17615: The command is not an ODI Tool command.

Cause: Wrong command.

Action: Check command.
Level: 32

Type: ERROR

Impact: Other

ODI-17616: No WorkTextOrig was found for ID: {0}.

Cause: Invalid ID.

Action: Check ID.
Level: 32

Type: ERROR

Impact: Other

ODI-17617: Class descriptor for WorkTextOrig [ {0} ] is null.

Cause: Descriptor is null.

Action: Check class descriptors.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17618: Unable to deal with an AliasedColumnCrossRef with type {0}.

Cause: Incorrect column type.

Action: Check column type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17619: Unexpected CrossRef {0} type.

Cause: Incorrect CrossRef type.

Action: Check CrossRef.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17620: Object type is not valid.

Cause: Object type is not valid.

Action: Check object type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17621: Unable to manage crossRef for object from class [ {0} ].

Cause: Illegal object type.

Action: Check object type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17622: pSqlIndGroup is not a valid group type.

Cause: Invalid group type.

Action: Check type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17623: Too many parameters for function {0}, Object {1}, Language {2}.

Cause: Too many parameters.

Action: Check parameters count.
Level: 32

Type: ERROR

Impact: Other

ODI-17624: Missing parameter for function {0}, Object {1}, Language {2}.

Cause: Missing parameter.

Action: Check parameters count.
Level: 32

Type: ERROR

Impact: Other

ODI-17625: Only OdiColumns are currently supported for SnpsExpressionTag.

Cause: Wrong column type.

Action: Check column type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17626: Cannot reassign a DataType.

Cause: Technology has been assigned yet.

Action: Check DataType
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17627: Inconsistent connection settings.

Cause: Inconsistent connection settings.

Action: Check connection settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17628: Unknown IConnectionSettings implementation.

Cause: Unknown IConnectionSettings implementation.

Action: Check settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17629: Connection Settings for repository server must be instanceof JdbcSettings.

Cause: Wrong settings type.

Action: Check settings type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17630: Unknown OptionType.

Cause: Unknown OptionType.

Action: Check option type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17631: The given class has no matching OverridenOptionOrig.

Cause: The given class has no matching OverridenOptionOrig.

Action: Check class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17632: Unexpected variable type.

Cause: Unexpected variable type.

Action: Check variable type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17633: {0} datatype is expected.

Cause: Wrong value datatype.

Action: Check value datatype.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17634: Parameter must have text; it must not be null or empty.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17635: Parameter must have text; it must not be null, empty, or blank.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17636: Parameter {0} must be false.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17637: Parameter must not be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17638: Parameter {0} must be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17639: Parameter must be null.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17640: Parameter {0} must have text; it must not be null or empty.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17641: No {0} matches this IObject: {1}.

Cause: IObject is not matched.

Action: Check class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17642: No Entity Class matches this Snp Class: {0}.

Cause: No Entity Class matches Snp Class.

Action: Check Entity Class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17643: No Snp Class matches this Entity Class: {0}.

Cause: No Snp Class matches Entity Class.

Action: Check Snp Class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17644: Unknown FlexFieldType.

Cause: Unknown FlexFieldType.

Action: Check FlexFieldType type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17645: Parameter must be instance of {0}.

Cause: Wrong parameter type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17646: It is forbidden to use a variable of one project in a package of another project.

Cause: Variable and package have different parents.

Action: Check variable and package.
Level: 32

Type: ERROR

Impact: Other

ODI-17647: Unable to create the expression element, Object {0}, Language {1}.

Cause: Unable to create the expression element.

Action: Check expression parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-17648: A mapping cannot be on the target.

Cause: A mapping cannot be on the target.

Action: Check execution location.
Level: 32

Type: ERROR

Impact: Other

ODI-17649: Can't create join between 2 source datastore from different DataSet.

Cause: Source datastores are from different DataSet.

Action: Correct join.
Level: 32

Type: ERROR

Impact: Other

ODI-17650: A {0} was expected as value since {1} is {2}.

Cause: Wrong type.

Action: Check type.
Level: 32

Type: ERROR

Impact: Other

ODI-17651: Parameter {0} must be instance of [{1}].

Cause: Wrong parameter class.

Action: Check parameter class.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17652: Class {0} is not assignable to {1}.

Cause: Inconsistent classes.

Action: Check classes.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17653: {0} line isn't found.

Cause: Missed line.

Action: Check line count.
Level: 32

Type: ERROR

Impact: Other

ODI-17654: Parameter {0} must be not null.

Cause: Parameter must be not null.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17655: Parameter {0} must be {1} characters long max.

Cause: Parameter length is too long.

Action: Check parameter length.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17656: Can't define variable override for steps in exception tree.

Cause: Step is in exception tree.

Action: Check step and variable for consistency.
Level: 32

Type: ERROR

Impact: Other

ODI-17657: Cannot add a reference column to an OdiReference with type [{0}].

Cause: Reference type isn't ReferenceType.COMPLEX_REFERENCE.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Other

ODI-17658: Cannot change the target table because it's not a temporary datastore.

Cause: Datastore isn't temporary.

Action: Check target table and datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17659: Cannot get the journalized columns of a non-journalized datastore.

Cause: Datastore isn't journalized.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17660: Cannot set a clause on the target.

Cause: Wrong execution location.

Action: Check execution location.
Level: 32

Type: ERROR

Impact: Other

ODI-17661: {0} is not supported for this Technology.

Cause: Object is not supported for this Technology.

Action: Check topology.
Level: 32

Type: ERROR

Impact: Other

ODI-17662: Parameter {0} must have text; it must not be null, empty, or blank.

Cause: Incorrect parameter.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17663: Parameter {0} must be uppercase.

Cause: Parameter is lower case.

Action: Check parameter case.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17664: Parameter {0} must not contain whitespaces.

Cause: Parameter contains whitespaces.

Action: Consider to replace whitespace with another symbold (e.g. underscore)
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17665: Column is not associated with this instance of OdiKey.

Cause: Column is not associated with instance of OdiKey.

Action: Check column and OdiKey.
Level: 32

Type: ERROR

Impact: Other

ODI-17666: Column is not present in the key.

Cause: Column is not present in the key.

Action: Check column and key.
Level: 32

Type: ERROR

Impact: Other

ODI-17667: Data type should be set before accessing value.

Cause: Illegal method usage.

Action: Set Data type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17668: Datastore already has a Primary Key.

Cause: Datastore already has a Primary Key.

Action: Remove the current primary key before adding a new one.
Level: 32

Type: ERROR

Impact: Other

ODI-17669: {0} must be set before calling method {1}.

Cause: Illegal method usage.

Action: Set actual value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17670: Default implementation already exists.

Cause: Default implementation already exists.

Action: Check function implementation.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17671: {0} must not be negative.

Cause: Wrong parameter value.

Action: Set value to 0 or greater.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17672: FlexFields isn''t initialized.

Cause: FlexFields isn''t initialized.

Action: Call initFlexFields method first.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17673: Foreign key column''s datastore must be equals to this reference''s foreign datastore.

Cause: Inconsistent datastores.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17674: IncrementValue is not set.

Cause: IncrementValue is not set.

Action: Set IncrementValue with setVariable method.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17675: Invalid step log's status.

Cause: Step status is not RUNNING.

Action: Check step status.
Level: 32

Type: ERROR

Impact: Other

ODI-17676: Invalid value type.

Cause: Invalid value type.

Action: Check value type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17677: Cycle could be defined in {0} hierarchy.

Cause: It is forbidden to define cycle in {0} hierarchy.

Action: Check hierarchy.
Level: 32

Type: ERROR

Impact: Other

ODI-17678: It is forbidden to fill a key with columns from another datastore.

Cause: It is forbidden to fill a key with columns from another datastore.

Action: Check datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-17679: It is forbidden to link two steps from different packages.

Cause: Steps are from different packages.

Action: Check steps and packages.
Level: 32

Type: ERROR

Impact: Other

ODI-17680: Line wasn't found.

Cause: Line wasn't found.

Action: Check procedure lines.
Level: 32

Type: ERROR

Impact: Other

ODI-17681: Maximum number of sessions must be positive.

Cause: Wrong value.

Action: Check maximum number.
Level: 32

Type: ERROR

Impact: Other

ODI-17682: Method is not valid unless MultiConnectionSupported.

Cause: MultiConnectionSupported is true.

Action: Check procedure.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17683: Model must be in Customized mode.

Cause: Wrong model mode.

Action: Call setReverseType(ReverseType.CUSTOMIZED).
Level: 32

Type: ERROR

Impact: Other

ODI-17684: Name can't be set.

Cause: Name is computed.

Action: Check name.
Level: 32

Type: ERROR

Impact: Other

ODI-17685: No {0} is defined for this model.

Cause: Missed definition.

Action: Define CKM for model.
Level: 32

Type: ERROR

Impact: Other

ODI-17686: No valid {0} name was found from this qualified name.

Cause: Valid name wasn't found.

Action: Check qualified name.
Level: 32

Type: ERROR

Impact: Other

ODI-17687: No valid qualified name was provided.

Cause: Name is invalid.

Action: Check qualified name.
Level: 32

Type: ERROR

Impact: Other

ODI-17688: OdiScenario is undefined.

Cause: OdiScenario is undefined.

Action: Check OdiScenario definition.
Level: 32

Type: ERROR

Impact: Other

ODI-17689: Option must be in the same procedure as line.

Cause: Option procedure is inconsistent.

Action: Check option procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-17690: Package and procedure must be owned by the same project.

Cause: Procedure parent is inconsistent.

Action: Check procedure parent.
Level: 32

Type: ERROR

Impact: Other

ODI-17691: Primary key column's datastore must be equals to this reference's primary datastore.

Cause: Column datastore is inconsistent.

Action: Check datastores.
Level: 32

Type: ERROR

Impact: Other

ODI-17692: Reference column doesn't belong to this reference.

Cause: Column is inconsistent.

Action: Check column.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17693: Reference's foreign datastore is not equal to this datastore.

Cause: Datastores are inconsistent.

Action: Check datastores.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17694: Steps can't be moved from one package to another.

Cause: Steps can't be moved from one package to another.

Action: Conside not to move steps.
Level: 32

Type: ERROR

Impact: Other

ODI-17695: The new position is not valid.

Cause: The new position is not valid.

Action: Check new position.
Level: 32

Type: ERROR

Impact: Other

ODI-17696: The option already exists.

Cause: The option already exists.

Action: Check option.
Level: 32

Type: ERROR

Impact: Other

ODI-17697: The option owner has already been set.

Cause: The option owner has already been set.

Action: Check option owner.
Level: 32

Type: ERROR

Impact: Other

ODI-17698: The reference type must be [ {0} ] in order to define a complex SQL expression.

Cause: Wrong reference type.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17699: The reference type must be [ {0} ] in order to obtain the complex SQL expression.

Cause: Wrong reference type.

Action: Check reference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17700: The string value length should not exceed MAX_SHORT_TEXT_LENGTH since FlexFieldType is SHORT_TEXT.

Cause: FlexFieldType is SHORT_TEXT.

Action: Check FlexFieldType and string value length.
Level: 32

Type: ERROR

Impact: Other

ODI-17701: This OdiLoadPlanInstanceRun is not ESS Job related.

Cause: OdiLoadPlanInstanceRun is not ESS Job related.

Action: Check OdiLoadPlanInstanceRun.
Level: 32

Type: ERROR

Impact: Other

ODI-17702: This session is not ESS Job related.

Cause: Session is not ESS Job related.

Action: Check session.
Level: 32

Type: ERROR

Impact: Other

ODI-17703: This OdiReference must be from type [{0}] in order to access the primary DataStore alias.

Cause: Wrong OdiReference type.

Action: Check OdiReference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17704: This OdiReference must be from type [{0}] in order to set the primary DataStore alias.

Cause: Wrong OdiReference type.

Action: Check OdiReference type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17705: This file descriptor is not consistent with the parent model's technology.

Cause: File descriptor is not consistent.

Action: Check file descriptor and parent technology.
Level: 32

Type: ERROR

Impact: Other

ODI-17706: This setVariable is used for increment.

Cause: Increment value is set.

Action: Use method getIncrementValue().
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17707: Unable to add an alien main partition.

Cause: Main partition datastore is inconsistent.

Action: Check main partition.
Level: 32

Type: ERROR

Impact: Other

ODI-17708: Unable to compute name.

Cause: Name has been set on this physical schema.

Action: Do not compute name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17709: Parameter must be false.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17710: Parameter {0} must be true.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17711: Undefined ODI work repository name.

Cause: Undefined repository name.

Action: Check repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-17712: Variable and Step should be defined in the same Load Plan.

Cause: Variable and Step have different parent Load Plans.

Action: Define variable and step in the same Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-17713: VariableDataType should be set before accessing DefaultValue.

Cause: VariableDataType is undefined.

Action: Set VariableDataType.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17714: You can only set KMs contained in the OdiProject containing of the OdiInterface.

Cause: KM has different parent project than OdiInterface.

Action: Check KM.
Level: 32

Type: ERROR

Impact: Other

ODI-17715: Can't add a null variable to load plan.

Cause: Variable is null.

Action: Check variable value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17716: DataTypes must be consistent.

Cause: DataTypes is inconsistent.

Action: Check DataTypes.
Level: 32

Type: ERROR

Impact: Other

ODI-17717: Constraint is not a condition.

Cause: Inconsistent constraint type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17718: Constraint is not a key.

Cause: Inconsistent constraint type.

Action: Check constraint.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17719: Option is not associated to this procedure.

Cause: Option is not associated to this procedure.

Action: Check option and procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-17720: Constraint is not a reference.

Cause: Inconsistent constraint type.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17721: Parameter {0} already belongs to {1}.

Cause: Parameter has parent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17722: Parameter {0} does not belong to this instance of {1}.

Cause: Parameter has different parent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17723: Parameter {0} must belong to this {1}.

Cause: Parameter parent is inconsistent.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17724: Parameter {0} can't be moved to an other {1}.

Cause: Parameter can't be moved.

Action: Do not move parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-17725: Parameter {0} must start with {1} prefix.

Cause: Parameter has wrong prefix.

Action: Check parameter prefix.
Level: 32

Type: ERROR

Impact: Other

ODI-17726: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}.

Cause: Agent is null.

Action: Check agents.
Level: 32

Type: ERROR

Impact: Other

ODI-17727: pDataServiceContainer is not a data service.

Cause: pDataServiceContainer is not a data service.

Action: Check pDataServiceContainer.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17728: Package and interface must be owned by the same project.

Cause: Package and interface have different parents.

Action: Check package and interface.
Level: 32

Type: ERROR

Impact: Other

ODI-17729: Parameter must be true.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17730: Not legal for shortcut.

Cause: Object is shortcut.

Action: Use getShortcutBaseObject() to access the real object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17731: Not legal to construct a shortcut from a datastore in a model with a different technology.

Cause: Inconsistent technologies.

Action: Check model and datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17732: Odi object Must be shortcut after materialize.

Cause: Object isn't shortcut.

Action: Check object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17733: Reference's primary datastore must be not null in order to define a ReferenceColumn.

Cause: Primary DataStore is null.

Action: Check DataStore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17734: pDataServiceContainer {0} has no technology defined.

Cause: Data Service Container has no technology defined.

Action: Define technology.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17735: Reference's foreign datastore is not equals to this datastore.

Cause: Reference's foreign datastore is not equals to this datastore.

Action: Check DataStores.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17736: You can only set global KMs or KMs contained in the OdiProject containing the OdiInterface.

Cause: Wrong KM.

Action: Check KM and project.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17737: StepLog and Variable don't belong to the same session.

Cause: Inconsistent session.

Action: Check Session value for StepLog and Variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17738: Unable to find '{0}' as variable used by the scenario '{1}' in version '{2}'.

Cause: Variable is null.

Action: Check variable name.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17739: Unable to override '{0}' variable for execution. It is marked as read-only for scenario '{1}' in version '{2}'.

Cause: Variable is read-only.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17740: Error while connecting to the Application Server at URL {0}.

Cause: Exception was thrown during connection.

Action: Ensure that the Application Server is running and accepting requests.
Level: 32

Type: ERROR

Impact: Network

ODI-17741: Datastore isn't used as a lookup source.

Cause: Datastore isn't used as a lookup source.

Action: Check Datastore.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17742: Parameter {0} must be greater or equal than {1} and less or equal than {2}.

Cause: Wrong parameter value

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17743: Variable should be related to the same {0}.

Cause: Wrong parent for variable.

Action: Check variable.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17744: The status can only be switched from ERROR to DONE or from DONE to ERROR.

Cause: Wrong status

Action: Check status.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17745: Parameter {0} must be greater or equal than {1}.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17746: Parameter {0} must be greater than {1}.

Cause: Wrong parameter value.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17747: Array {0} must not be empty.

Cause: Array length is 0.

Action: Check array.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17748: Parameter {0} is not relevant to this schedule.

Cause: Wrong parameter.

Action: Check parameter.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17749: Invalid value was specified. Cannot create {0} with the value {1}.

Cause: Invalid value was specified.

Action: Check value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17750: Parent folder already has the release tag set.

Cause: Setting the release tag when the parent already has the release tag set.

Action: Set the release tag in parent.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17751: Shortcut and the base object are under same folder.

Cause: Cannot create shortcut {0} with the base object under same folder {1}.

Action: Create shortcut in different folder.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17752: Shortcut and the base object are in different projects.

Cause: Cannot create shortcut {0} in project {1} which is different from the project of the base object.

Action: Create shortcut in same project as the base object.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17753: Shortcut with same reference object in same folder.

Cause: There is other shortcut object with same reference object as {0} in the same folder.

Action: Create shortcut in different folder.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17754: Shortcut and the base object are under same model.

Cause: Cannot create shortcut {0} with the base object under same model {1}.

Action: Create shortcut in different model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17755: Shortcut with same reference object in same model.

Cause: There is other shortcut object with same reference object as {0} in the same model.

Action: Create shortcut in different model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17756: Scenario "{0}", which is referenced by RunScenario step "{1}", has variable "{2}" but LoadPlan does not have variable with the same name.

Cause: Missed variable in Load Plan

Action: Check Load Plan''s variables.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17757: Scenario "{0}", which is referenced by RunScenario step "{1}", has a newer version "{2}" in the repository

Cause: Scenario has newer version.

Action: Consider to use latest version.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17758: LoadPlan Variable "{0}" SQL is different than the design repository Variable "{1}" SQL.

Cause: Variable's SQL was redefined.

Action: Check LoadPlan's variable.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17759: LoadPlan Variable "{0}" LogicalSchema "{1}" is different than the design repository Variable "{2}" LogicalSchema "{3}".

Cause: Variable's Logical Schema was redefined.

Action: Check LoadPlan's variable.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17760: Exception "{0}" is not used in the Load Plan.

Cause: Exception is not used.

Action: Consider to delete or disable unused exception.
Level: 32

Type: NOTIFICATION

Impact: Programmatic

ODI-17761: LoadPlan Variable "{0}" is refreshed at step "{1}", but it has no SQL.

Cause: LoadPlan Variable doesn't have refresh SQL.

Action: Check variable''s SQL or disable variable refreshing.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17762: Context is specified on a step "{0}", but it''s no longer present in the topology.

Cause: Context was removed.

Action: Check step's context.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17763: Logical Agent is specified on a step "{0}", but it is no longer present in the topology

Cause: Logical Agent was removed.

Action: Check step's Logical Agent.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17764: Context "{0}" and Logical agent "{1}" on a step "{2}" does not map to any physical agent.

Cause: Physical Agent doesn''t exist.

Action: Check agents'' mapping.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17765: Scenario variable "{0}" type and LoadPlan variable "{1}" type mismatch.

Cause: Variables have different datatype.

Action: Check variables.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17766: Scenario "{0}" wasn''t found.

Cause: Scenario doesn''t exist

Action: Check scenario and Load Plan step.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17767: LoadPlan has variable "{0}", but repository doesn't have variable with the same name.

Cause: Variable was deleted.

Action: Check variables.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17768: LoadPlan Variable "{0}" has SQL, which could not be validated.

Cause: OdiVariableTextGeneratorException during validation.

Action: Check variable and variable text generator.
Level: 32

Type: WARNING

Impact: Programmatic

ODI-17769: OdiRef: Internal ID {0} of IObjects {1} should not be used when the repository is 12c mode.

Cause: Internal ID is used in 12c mode.

Action: Use Global Id instead of internal id.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17770: Profile {0} is not assigned to role {1}.

Cause: Profile is not assigned to role.

Action: Check role's profiles.
Level: 32

Type: ERROR

Impact: Security

ODI-17771: Enterprise principal with unique ID/name {0} is not mapped to role {1}.

Cause: Enterprise principal is not mapped to role.

Action: Check role's mapped enterprise principals.
Level: 32

Type: ERROR

Impact: Security

ODI-17772: Parameter {0} should be {1} or {2}.

Cause: Wrong parameter value.

Action: Check parameter value.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17773: Enterprise User or Role {0} does not exist.

Cause: Enterprise principla with such name could be found at LDAP server.

Action: Check principal name and LDAP server.
Level: 32

Type: ERROR

Impact: Security

ODI-17774: Maximum number of concurrent threads must be positive.

Cause: Wrong value.

Action: Check maximum number provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17775: Maximum number of threads per session can not be negative.

Cause: Wrong value.

Action: Check maximum number provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17776: Maximum number of concurrent threads must not be less than maximum session count.

Cause: Wrong value.

Action: Check maximum numbers provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17777: Maximum number of threads per session must be not greater than maximum number of threads.

Cause: Wrong value.

Action: Check maximum numbers provided.
Level: 32

Type: ERROR

Impact: Other

ODI-17778: Maximum number of cache entries in Session Blueprint queue cannot be negative.

Cause: Wrong value.

Action: Check value.
Level: 32

Type: ERROR

Impact: Other

ODI-17779: Maximum idle time for Session Blueprint in cache cannot be negative.

Cause: Wrong value.

Action: Check value.
Level: 32

Type: ERROR

Impact: Other

ODI-17780: Package and mapping must be owned by the same project.

Cause: Package and mapping have different parents.

Action: Check package and mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-17781: Physical Mapping Design must be owned by the mapping.

Cause: Physical Mapping Design is not owned by mapping.

Action: Check mapping and physical design.
Level: 32

Type: ERROR

Impact: Other

ODI-17782: OdiRef: Internal ID is retrieved in method {0}.{1} for 12c repository.

Cause: Internal ID is retrieved in 12c mode.

Action: Retrieve Global Id instead of internal id.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17783: Mapping metadata version mismatch. Expected {0}, but was {1}.

Cause: Mapping metadata version mismatch.

Action: Check the expected and actual Mapping metadata version.
Level: 32

Type: ERROR

Impact: Other

ODI-17784: Reusable Mapping metadata version mismatch. Expected {0}, but was {1}.

Cause: Reusable Mapping metadata version mismatch.

Action: Check the expected and actual Reusable Mapping metadata version.
Level: 32

Type: ERROR

Impact: Other

ODI-17785: Option positions in knowledge module must be unique.

Cause: Option position undefined or multiple option in knowledge module has same position.

Action: Modify the position of options to be unique and not null.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17786: JKM is not Oracle Golden Gate JKM.

Cause: Model doesn't have JKM set or JKM is not Oracle Golden Gate JKM.

Action: Set Oracle Golden Gate JKM for the model.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17787: Extract and initial extract processes cannot be the same.

Cause: Extract and inital extract processes are the same.

Action: Choose another extract or initial expract process.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17788: Replicat and initial replicat processes cannot be the same.

Cause: Replicat and initial replicat processes are the same.

Action: Choose another replicat or initial replicat process.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17789: Positions must be set positive.

Cause: Position is not a positive integer.

Action: Set the position to be a positive integer.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-17790: {0} should be {1}

Cause: Type is not correct

Action: Set the correct type.
Level: 32

Type: ERROR

Impact: Programmatic

ODI-20001: ODI-20001: Cannot check the key because the Datastore does not exist in the database.

Cause: The Datastore referenced by this key did not exist in the database.

Action: Ensure the Datastore refers to an existing database table.
Level: 32

Type: ERROR

Impact: Other

ODI-20002: ODI-20002: The selected file is not a valid key file.

Cause: An invalid encryption key file was selected.

Action: Select a valid encryption key file.
Level: 32

Type: ERROR

Impact: Other

ODI-20003: ODI-20003: Cannot edit the condition

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20004: ODI-20004: Cannot edit the reference

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20005: ODI-20005: Cannot edit the variable

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20006: ODI-20006: Cannot display table's data. Data is probably already displayed.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20007: ODI-20007: Cannot display table's data.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20008: ODI-20008: You cannot Display this Attribute Data. Data is probably already displayed

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20009: ODI-20009: Cannot display data. The datastore resource name is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.

Cause: The datastore resource name exceeded the limit allowed by its technology.

Action: Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing the datastore resource name to comply.
Level: 32

Type: ERROR

Impact: Other

ODI-20010: ODI-20010: Cannot display this Attribute Data

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20011: ODI-20011: Cannot perform this action: a Column of this Datastore is currently being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20012: ODI-20012: Cannot perform this action: the Datastore containing this Column is currently being modified

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20013: ODI-20013: Unable to perform the action because the package is currently being modified

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20014: ODI-20014: Cannot encrypt the Procedure: it is currently being modified

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20015: ODI-20015: Cannot initialize the Flexfields values

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20016: ODI-20016: Unable to add project user functions

Cause: An unsupported action was attempted.

Action: No action required as Project user functions are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-20017: ODI-20017: Unable to add project sequences

Cause: An unsupported action was attempted.

Action: No action required as Project sequences are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-20018: ODI-20018: Unable to add project variables

Cause: An unsupported action was attempted.

Action: No action required as Project variables are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-20019: ODI-20019: Unable to get GBO object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20020: ODI-20020: Cannot change CKM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20021: ODI-20021: Cannot change the order of this Command because you do not have 'Edit' privileges on this Object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20022: ODI-20022: Could not change the KM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20023: ODI-20023: Cannot Duplicate a Command

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20024: ODI-20024: Cannot create the cross reference for the condition

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20025: ODI-20025: Cannot create the cross references for the reference

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20026: ODI-20026: Cannot view this Datastore: one of its Columns is currently being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20027: ODI-20027: Cannot view this Column: its Datastore is currently being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20028: ODI-20028: Cannot start execution.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20029: ODI-20029: Cannot move a line

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20030: ODI-20030: Cannot start the generation. The file is probably already open.

Cause: Attempt to open report file for output failed.

Action: Ensure the specified file is not currently open and the file permissions allow for write access before retrying the operation. Consider choosing a different file for output.
Level: 32

Type: ERROR

Impact: Other

ODI-20031: ODI-20031: Cannot Delete a Command being Edited.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20032: ODI-20032: Cannot Delete a Command

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20033: ODI-20033: Cannot find the KM description

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20034: ODI-20034: Cannot find the Options list for a Command

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20035: ODI-20035: Could not find a description for the KM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20036: ODI-20036: Impossible to find the technology name, please check your privileges.

Cause: The ODI security permissions were insufficient to allow access to the specified technology.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20037: ODI-20037: Cannot find data transferred by the Drag'n'Drop

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20038: ODI-20038: Could not connect

Cause: A connection was not established to the selected Logical Schema.

Action: Ensure the connection data for the Physical Schema of the selected Logical Schema is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20039: ODI-20039: Incorrect context

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20040: ODI-20040: Problem encountered when determining the context

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20041: ODI-20041: No candidate datastore was found.

Cause: There were no datastores in the current model usable as candidates for generating OUT mappings.

Action: Consider creating an mapping to load data into a datastore of the current model.
Level: 32

Type: ERROR

Impact: Other

ODI-20042: ODI-20042: Property key is empty

Cause: The Property key for one of the specified Data Server's properties was not specified.

Action: Ensure a non-empty key value is supplied or remove the property with this key.
Level: 32

Type: ERROR

Impact: Other

ODI-20043: ODI-20043: Invalid property key entered. Property key maximum length is 250 characters

Cause: The Property key for one of the specified Data Server's properties had a length greater than 250 characters.

Action: Ensure a key value with the valid length is supplied or remove the property with this key.
Level: 32

Type: ERROR

Impact: Other

ODI-20044: ODI-20044: Invalid property value entered. Property value maximum length is 250 characters

Cause: The Property value for one of this Data Server's properties had a length greater than 250 characters.

Action: Ensure a value with the valid length is supplied or remove the property with this value.
Level: 32

Type: ERROR

Impact: Other

ODI-20046: ODI-20046: Unable to change an open object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20047: ODI-20047: Unable to change Value

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20048: ODI-20048: Invalid Value entered. Value maximum length is 250 characters

Cause: The Value for one of this object's Flexfields had a length greater than 250 characters.

Action: Ensure the value supplied has a valid length.
Level: 32

Type: ERROR

Impact: Other

ODI-20049: ODI-20049: You cannot copy a folder into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20050: ODI-20050: You cannot copy a knowledge module into another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20051: ODI-20051: You cannot copy a package into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Packages cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20052: ODI-20052: You cannot copy an interface into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20053: ODI-20053: You cannot copy a procedure into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20054: ODI-20054: You cannot move a folder into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20055: ODI-20055: You cannot move a knowledge module into another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20056: ODI-20056: You cannot move a package into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Packages cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20057: ODI-20057: You cannot move an interface into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20058: ODI-20058: You cannot move a procedure into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20059: ODI-20059: You cannot copy a knowledge module into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be copied into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20060: ODI-20060: You cannot copy an interface into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be copied into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20061: ODI-20061: You cannot copy a procedure into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20062: ODI-20062: You cannot move a knowledge module into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20063: ODI-20063: You cannot move an interface into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20064: ODI-20064: You cannot move a step into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Package steps cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20065: ODI-20065: You cannot move a procedure into a package belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into packages from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20066: ODI-20066: You cannot copy a folder into another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20067: ODI-20067: You cannot copy a procedure into another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20068: ODI-20068: You cannot copy a variable into another project.

Cause: An unsupported operation was attempted.

Action: Variables cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20069: ODI-20069: You cannot move a folder into another project.

Cause: An unsupported operation was attempted.

Action: Folders cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20070: ODI-20070: You cannot move a sequence into another project. Copy the sequence instead.

Cause: An unsupported operation was attempted.

Action: Sequences cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20071: ODI-20071: You cannot move a procedure into another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20072: ODI-20072: You cannot move a variable into another project.

Cause: An unsupported operation was attempted.

Action: Variables cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20073: ODI-20073: You cannot copy a schedule into a scenario belonging to another project.

Cause: An unsupported operation was attempted.

Action: Schedules cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20074: ODI-20074: You cannot move a schedule into a scenario belonging to another project.

Cause: An unsupported operation was attempted.

Action: Schedules cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20075: ODI-20075: You cannot move a folder into one of its subfolders.

Cause: An unsupported operation was attempted.

Action: Folders cannot be moved into their subfolders.
Level: 32

Type: ERROR

Impact: Other

ODI-20076: ODI-20076: You cannot copy a knowledge module into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be copied into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20077: ODI-20077: You cannot copy an interface into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be copied into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20078: ODI-20078: You cannot copy a procedure into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be copied into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20079: ODI-20079: You cannot move a knowledge module into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Knowledge modules cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20080: ODI-20080: You cannot move an interface into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Interfaces cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20081: ODI-20081: You cannot move a step into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Steps cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20082: ODI-20082: You cannot move a procedure into a package step belonging to another project.

Cause: An unsupported operation was attempted.

Action: Procedures cannot be moved into package steps from another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20083: ODI-20083: Unable to perform the operation. {0} is being edited.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20084: ODI-20084: Only variables from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Variables from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20085: ODI-20085: Only mappings from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Mappings from another project cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20086: ODI-20086: Only procedures from the same project can be placed in a package.

Cause: An unsupported operation was attempted.

Action: Procedures from another projects cannot be placed in packages.
Level: 32

Type: ERROR

Impact: Other

ODI-20087: ODI-20087: Error while duplicating

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20088: ODI-20088: Error while generating the scenario

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20089: ODI-20089: Error during parameter initialization

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20090: ODI-20090: Error while duplicating

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20091: ODI-20091: An unexpected error occurred.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20092: ODI-20092: An error occurred while replacing the version.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20093: ODI-20093: Scenario generation is not allowed for non-saved object

Cause: Scenario generation could not be performed because the source object was not saved.

Action: Ensure the source object is saved before attempting scenario generation for it.
Level: 32

Type: ERROR

Impact: Other

ODI-20094: ODI-20094: Specify the object name to generate Scenario

Cause: Scenario generation could not be performed because the source object's name was not specified.

Action: Ensure the source object's name is specified before attempting scenario generation for it.
Level: 32

Type: ERROR

Impact: Other

ODI-20095: ODI-20095: Marker Group save was cancelled

Cause: Marker group save was cancelled by a user.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20096: ODI-20096: Unable to edit the action line.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20097: ODI-20097: The line Name is mandatory

Cause: A value for the Action Line Name field was not specified.

Action: Enter a non-empty value for the Action Line Name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20098: ODI-20098: Some Datatype Conversions between current and new Technologies are absent

Cause: Changing the selected Model's Technology failed because the Physical Architecture did not provide datatype conversion rules for datatypes used by attributes of datastores belonging to the selected model.

Action: Ensure datatype conversion rules exist for all datatypes used by attributes of datastores belonging to the selected model or do not use datatypes that cannot be converted.
Level: 32

Type: ERROR

Impact: Other

ODI-20099: ODI-20099: Unable to create execution window

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20100: ODI-20100: Unable to access a join or a filter

Cause: Access to a join or filter failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the join or filter object.
Level: 32

Type: ERROR

Impact: Other

ODI-20101: ODI-20101: Unable to find mapping alias

Cause: Access to the target mapping failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the target mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-20102: ODI-20102: Unable to find source table alias

Cause: Access to the source table failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the source table.
Level: 32

Type: ERROR

Impact: Other

ODI-20103: ODI-20103: Unable to access a target column

Cause: Access to the target column failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the target column.
Level: 32

Type: ERROR

Impact: Other

ODI-20105: ODI-20105: "Schema", "Table", "Column" and "Filter" are mandatory fields.

Cause: Values for the mandatory "Schema", "Table", "Column" and "Filter" fields were not supplied.

Action: Ensure values are supplied for these mandatory fields.
Level: 32

Type: ERROR

Impact: Other

ODI-20106: ODI-20106: Schema and Native sequence name are mandatory fields

Cause: Values for the mandatory Schema and Native sequence name fields were not supplied.

Action: Ensure values are supplied for these mandatory fields.
Level: 32

Type: ERROR

Impact: Other

ODI-20107: ODI-20107: A project sequence with the name "{0}" already exists in the project "{1}"

Cause: Saving the project sequence failed because the Sequence name was not unique within the Project.

Action: Ensure the sequence name entered is unique.
Level: 32

Type: ERROR

Impact: Other

ODI-20108: ODI-20108: A global sequence with the name "{0}" already exists

Cause: Saving the Global sequence failed because the Global Sequence name was not unique.

Action: Ensure the sequence name entered is unique.
Level: 32

Type: ERROR

Impact: Other

ODI-20109: ODI-20109: Error while restoring the version

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20110: ODI-20110: No version of this element exist.

Cause: The selected version of this object was not found in version repository.

Action: Create or restore the selected version of the object.
Level: 32

Type: ERROR

Impact: Other

ODI-20111: ODI-20111: Sub-model code cannot be empty.

Cause: A value of the mandatory Sub-model code field was not supplied.

Action: Enter a non-empty value for the Sub-model code field.
Level: 32

Type: ERROR

Impact: Other

ODI-20112: ODI-20112: The path defined in the logical schema is incorrect.

Cause: Incorrect path was specified in physical schema which is linked to the logical schema of this datastore in the current context.

Action: Ensure the path specified in physical schema is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20113: ODI-20113: The GUID that was supplied does not match the GUID for this user in the external identity store. Please retrieve the correct GUID before saving.

Cause: The supplied GUID did not match GUID from external identity store.

Action: Provide a valid GUID.
Level: 32

Type: ERROR

Impact: Other

ODI-20114: ODI-20114: Error while subscribing

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20115: ODI-20115: Error while stopping journalizing

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20116: ODI-20116: Aliases are specified and are not unique.

Cause: Duplicate Alises were detected.

Action: Change the name of the join key alias.
Level: 32

Type: ERROR

Impact: Other

ODI-20117: ODI-20117: Error while executing command line.

Cause: An unexpected error occurred while trying to open the Report.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20118: ODI-20118: Error while building the menu.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20119: ODI-20119: Error during generation.

Cause: An unexpected error occurred during the report generation.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20120: ODI-20120: Error while journalizing

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20121: ODI-20121: Error while saving the diagram

Cause: An unexpected error occurred during the saving the diagram.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20122: ODI-20122: Error while unsubscribing

Cause: An unexpected error occurred during the unsubscribing action.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20123: ODI-20123: Error while executing query

Cause:

Action: Check the error details for further actions.
Level: 32

Type: ERROR

Impact: Other

ODI-20124: ODI-20124: Operation cancelled by user.

Cause: Operation cancelled by user

Action: Review the other messages for further actions.
Level: 32

Type: WARNING

Impact: Other

ODI-20126: ODI-20126: TreeTableColumn cannot be added

Cause: TreeTableColumn with this order number already exists

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20127: ODI-20127: This TreeTableColumn cannot be removed.

Cause: TreeTableColumn does not exist.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20128: ODI-20128: Could not rollback.

Cause: An error occurred during rollback operation.

Action: Review other messages for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20129: ODI-20129: Exception occurred.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20130: ODI-20130: You must select a folder.

Cause: A folder was not selected.

Action: Select a folder before attempting this action.
Level: 32

Type: ERROR

Impact: Other

ODI-20131: ODI-20131: Cannot retrieve the table list

Cause: An error occured while trying to retrieve a list of tables.

Action: Review the message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20132: ODI-20132: An interface cannot be moved to another project

Cause: An unsupported drag and drop operation was attempted.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20133: ODI-20133: A procedure cannot be moved to another project

Cause: An unsupported drag and drop operation was attempted.

Action: No action required.
Level: 32

Type: ERROR

Impact: Other

ODI-20134: ODI-20134: A variable cannot be moved to another project

Cause: An unsupported drag and drop operation was attempted.

Action: No action required
Level: 32

Type: ERROR

Impact: Other

ODI-20135: ODI-20135: A step cannot be moved to another package

Cause: An unsupported drag and drop operation was attempted.

Action: No action required
Level: 32

Type: ERROR

Impact: Other

ODI-20138: ODI-20138: An error occured during: dragGesture

Cause: An unexpected error occurred while dragging an object.

Action: Review the message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20139: ODI-20139: An error occured during: dragEnter

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20140: ODI-20140: An error occured during: Drop

Cause: An unexpected error occurred while dropping an object.

Action: Review the message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20141: ODI-20141: Login Creation Error

Cause: An unexpected error occurred while creating a new Login.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20142: ODI-20142: Popup Menu Creation Error

Cause: An unexpected error occurred while creating a popup menu.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20144: ODI-20144: Error while Deleting

Cause: An unexpected error occurred while deleting a tree object.

Action: Review the error details for further information.
Level: 32

Type: ERROR

Impact: Other

ODI-20145: ODI-20145: Error while Opening splitframe.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20146: ODI-20146: Error occured during duplication

Cause: An unexpected error occurred while duplicating an object.

Action: Review the error details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20148: ODI-20148: An error occured during: drag over the object

Cause: An unexpected error occurred while dragging an object over another object.

Action: Review the error details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20149: ODI-20149: Logical schema can't be undefined

Cause: A Logical schema was not defined.

Action: Define a Logical schema.
Level: 32

Type: ERROR

Impact: Other

ODI-20150: ODI-20150: KM or Procedure already encrypted. No encryption was performed.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20151: ODI-20151: File is not found. Invalid file location

Cause: The specified file could not be located in the file system.

Action: Ensure file location specified is valid and accessible.
Level: 32

Type: ERROR

Impact: Other

ODI-20152: ODI-20152: Object cannot be deleted

Cause: The specified object could not be deleted.

Action: Ensure the specified object exists and the security permissions permit deletion.
Level: 32

Type: ERROR

Impact: Other

ODI-20153: ODI-20153: The following field is missing: Syntax

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20155: ODI-20155: Changing the Logical Schema may require a re-generation of your Mappings. It may be better to modify the Topology information instead.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-20158: ODI-20158: Datastores distribution failed.

Cause: An error occured during the datastore distribution process.

Action: Review the message details and message log for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20159: ODI-20159: The Attribute {0} is used as a Reference

Cause: An attempt was made to delete an attribute referenced by another object.

Action: Delete the object which references this attribute then retry deleting this attribute.
Level: 32

Type: ERROR

Impact: Other

ODI-20160: ODI-20160: The table {0} does not exist.

Cause: An error occured while executing the SQL request

Action: Review the message details for more information. If problem persists contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20161: ODI-20161: Standard reverse-engineering failed.

Cause: An error occured during the standard reverse-engineering process.

Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-20162: ODI-20162: The context is not valid.

Cause: A Context was not specified.

Action: Specify a Context.
Level: 32

Type: ERROR

Impact: Other

ODI-20163: ODI-20163: Unable to add object

Cause: An error occurred while dragging and dropping an object.

Action: Review the message details and message log for more information.
Level: 32

Type: ERROR

Impact: Other

ODI-20164: ODI-20164: The line Name is mandatory

Cause: A name was not specified.

Action: Specify a Line name.
Level: 32

Type: ERROR

Impact: Other

ODI-20165: ODI-20165: The project name {0} is a reserved word.

Cause: A reserved word was used as the name of a project.

Action: Enter a different project name.
Level: 32

Type: ERROR

Impact: Other

ODI-20166: ODI-20166: The project code {0} is a reserved word.

Cause: A reserved word was used as the project code.

Action: Enter a different project code.
Level: 32

Type: ERROR

Impact: Other

ODI-20167: ODI-20167: Logical schema is not set for the current context

Cause: A Logical schema was not set for the current context.

Action: Ensure the Logical Schema is not set to "Undefined" in the Context editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20168: ODI-20168: Logical schema is not set for the current context

Cause: A Logical schema was not set for the current context.

Action: Ensure the Logical Schema is not set to "Undefined" in the Context editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20169: ODI-20169: The field {0} is mandatory.

Cause: A mandatory field was not specified.

Action: Enter a value for this field.
Level: 32

Type: ERROR

Impact: Other

ODI-20170: ODI-20170: You are trying to insert this versioned object but the version was deleted. Please re-create a version for this object.

Cause: The requested version of the object did not exist in the repository.

Action: Recreate the required version of this object.
Level: 32

Type: ERROR

Impact: Other

ODI-20171: ODI-20171: The solution already contains a child of {0}. To add {1} to the solution, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the solution's coherence.

Cause: The solution already contained the specified object as a child.

Action: Delete the child object from the solution before retrying the addition. Consider using the synchronize option to verify the solution's coherence.
Level: 32

Type: ERROR

Impact: Other

ODI-20172: ODI-20172: The solution already contains a parent of {0}. To add {1} to the solution, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the solution's coherence.

Cause: The solution has already contained the specified object as a parent of {0}.

Action: Delete the parent object from the solution before retrying the addition. Consider using the synchronize option to verify the solution's coherence.
Level: 32

Type: ERROR

Impact: Other

ODI-20173: ODI-20173: An error occurred while generating the procedure

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20174: ODI-20174: Folder {0} already contains an mapping named {1}

Cause: An mapping of the same name already existed in the specified folder.

Action: Specify another name for the mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-20175: ODI-20175: You cannot give an empty name to an mapping

Cause: The Mapping's name was not specified.

Action: Enter a non-empty value for the mapping's name.
Level: 32

Type: ERROR

Impact: Other

ODI-20176: ODI-20176: You cannot create multiple mappings with the same name

Cause: An mapping of the same name already existed.

Action: Specify a different name for the mapping.
Level: 32

Type: ERROR

Impact: Other

ODI-20177: ODI-20177: You must select a generation folder

Cause: The Generation folder was not selected.

Action: Select a generation folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20180: ODI-20180: You cannot choose an expiration date in the past.

Cause: Entered expiration date was in the past.

Action: Enter valid expiration date.
Level: 32

Type: ERROR

Impact: Other

ODI-20181: ODI-20181: You cannot set an expiration date if there is no password.

Cause: No password was entered.

Action: Enter a password before setting an expiration date.
Level: 32

Type: ERROR

Impact: Other

ODI-20182: ODI-20182: Error while opening window

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20183: ODI-20183: Error while refreshing Solution

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20184: ODI-20184: The request to retrieve the sequence list has not been defined on the technology.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20185: ODI-20185: Error while opening window

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20186: ODI-20186: Error while saving

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20187: ODI-20187: Error while adding the marker

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20188: ODI-20188: This object is locked by another user. You cannot edit its markers.

Cause: The object was locked by another user.

Action: Wait until the object is unlocked. Consider contacting the user who has the object locked.
Level: 32

Type: ERROR

Impact: Other

ODI-20189: ODI-20189: You do not have the sufficient privileges to reverse-engineer a model

Cause: The model could not be reverse-engineered due to insufficient privileges.

Action: Ensure the SUPERVISOR or owner of model grants the appropriate permissions.
Level: 32

Type: ERROR

Impact: Other

ODI-20190: ODI-20190: You cannot reverse engineer a model in 'Standard' mode: the model technology assumes RKM to be selected.

Cause: No RKM was specified for this model.

Action: Select an RKM for this model.
Level: 32

Type: ERROR

Impact: Other

ODI-20191: ODI-20191: The model you want to reverse-engineer references a logical schema that no longer exists.

Cause: The referenced Logical Schema for the Model was not found.

Action: Ensure a valid Logical Schema is assigned for the Model.
Level: 32

Type: ERROR

Impact: Other

ODI-20192: ODI-20192: Error while replacing versioned object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20193: ODI-20193: An error occurred during the versioning operation.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20194: ODI-20194: Your license does not allow Versioning operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20195: ODI-20195: Unable to unlock this object

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20196: ODI-20196: You must select an object version

Cause: No version selected for checkout.

Action: Select version for checkout.
Level: 32

Type: ERROR

Impact: Other

ODI-20197: ODI-20197: Your license does not allow Versioning operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20198: ODI-20198: Error while creating the version.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20199: ODI-20199: Your license does not allow Versioning operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20200: ODI-20200: An error happened while comparing the versions

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20201: ODI-20201: Error while refreshing.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20202: ODI-20202: Synchronisation was stopped by the user.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20203: ODI-20203: The current version for this object no longer exists. Please create a new version for this object.

Cause: The current version for this object was not found in the repository.

Action: Create a new version for this object.
Level: 32

Type: ERROR

Impact: Other

ODI-20205: ODI-20205: Could not delete object. This object is being used.

Cause: The object deletion failed because it was already in use.

Action: Remove the usage of the selected object before retrying the deletion.
Level: 32

Type: ERROR

Impact: Other

ODI-20206: ODI-20206: Could not delete object. This object is being displayed.

Cause: The object deletion failed because it was being displayed.

Action: Close object before retrying the deletion.
Level: 32

Type: ERROR

Impact: Other

ODI-20208: ODI-20208: A code was duplicated:

Cause: A Flex field with the same code already existed.

Action: Enter another Flex field code.
Level: 32

Type: ERROR

Impact: Other

ODI-20209: ODI-20209: An error occurred.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20210: ODI-20210: Error When Printing...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20211: ODI-20211: Error When Displaying Node...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20212: ODI-20212: An error occurred while checking errors

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20213: ODI-20213: An error occurred while recovering an object in a node

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20214: ODI-20214: An error occurred while deleting

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20216: ODI-20216: Error while deleting

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20217: ODI-20217: Error while executing the reverse-engineering

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20218: ODI-20218: Error during duplication ...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20219: ODI-20219: Error while opening

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20220: ODI-20220: Error during data loading ....

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20221: ODI-20221: Error during execution ...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20222: ODI-20222: Error during scenario creation ...

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20223: ODI-20223: Error When Purging Log

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20224: ODI-20224: An interface with the same name already exists in this folder. Please change the name of the new interface.

Cause: An interface with the same name already existed in this folder.

Action: Specify another name for the interface.
Level: 32

Type: ERROR

Impact: Other

ODI-20225: ODI-20225: Error while creating the popup menu

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20226: ODI-20226: Error while applying the changes

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20227: ODI-20227: You cannot copy this attribute. Attribute name already in use.

Cause: Attribute copy failed because the Datastore already contained an attribute with the same name.

Action: Select another attribute to drop to datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-20228: ODI-20228: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the column failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20229: ODI-20229: Unable to create condition.

Cause: The editor for the Condition could not be opened.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20230: ODI-20230: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the Condition failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20231: ODI-20231: Unable to create a synonym for this table.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20232: ODI-20232: Error while deleting attributes

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20233: ODI-20233: Error during the drag-and-drop operation

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20234: ODI-20234: You do not have the sufficient privileges to add this object.

Cause: The operation failed due to insufficient ODI security on Attribute.

Action: Ensure the ODI user security permissions are correct specifically the Attribute Duplication setting.
Level: 32

Type: ERROR

Impact: Other

ODI-20235: ODI-20235: Error during the drag-and-drop operation

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20236: ODI-20236: You do not have the sufficient privileges to add this object.

Cause: The operation failed due to insufficient ODI security on Datastore.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20237: ODI-20237: Unable to duplicate the attribute.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20238: ODI-20238: Unable to duplicate the table.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20239: Error during the action

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20240: ODI-20240: Error while deleting

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20241: ODI-20241: Unable to apply changes.

Cause: The changes to the filter could not be applied.

Action: Save the object before retrying to apply the filter.
Level: 32

Type: ERROR

Impact: Other

ODI-20242: ODI-20242: Error while creating the popup menu

Cause: Retrieval of the Available Methods for the filter failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20243: ODI-20243: Unable to add an attribute.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20244: ODI-20244: Unable to add reference

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20245: ODI-20245: Unable to add table

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20246: ODI-20246: Error while applying the changes

Cause: The reference to the Model could not be created.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20247: ODI-20247: Unable to add key.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20248: ODI-20248: Error while opening window

Cause: The editor could not be opened.

Action: Save the object before retrying the edit.
Level: 32

Type: ERROR

Impact: Other

ODI-20249: ODI-20249: Error while creating the popup menu

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20250: ODI-20250: Error while

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20251: ODI-20251: An unexpected error has occurred

Cause: Unable to acess the Security Authorization settings.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20252: ODI-20252: Unable to apply changes.

Cause: Saving the model condition failed.

Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20253: ODI-20253: The object was deleted by another user

Cause: The operation could not be performed because the specified object could not found.

Action: Refresh the view and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-20254: ODI-20254: The marker was deleted by another user

Cause: The operation could not be performed because the specified Marker object was in an Inconsistent state.

Action: Refresh the view and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-20255: ODI-20255: Marker name is mandatory

Cause: Marker could not be saved because the mandatory Name field was not entered.

Action: Enter a value in the Marker name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20256: ODI-20256: You do not have the sufficient privileges to change the marker

Cause: Modification of the Marker failed due to insufficient ODI security privileges.

Action: Ensure the ODI user security permissions are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20257: ODI-20257: The Where text is mandatory when the Filter is active for a static control.

Cause: The WHERE clause was null or empty.

Action: Ensure the WHERE clause is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-20258: ODI-20258: It is not possible to check the expression due to DBMS connection failure

Cause: Connection to the DBMS failed.

Action: Ensure the DBMS is available and the connection information to it is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20259: ODI-20259: cannot show the data since the join points to different connections

Cause: Unable to retrieve data due to a conflict between the physical schemas involved.

Action: Ensure the Topology or Context settings are correct and multiple data stores in the same Source Set are not connected using different Physical Schemas.
Level: 32

Type: ERROR

Impact: Other

ODI-20260: ODI-20260: Name and Code columns of the FlexField cannot be empty.

Cause: FlexField name or code were found to be empty or null.

Action: Enter a name and a code for the FlexField.
Level: 32

Type: ERROR

Impact: Other

ODI-20261: ODI-20261: The "Procedure Name" is mandatory.

Cause: The "Procedure Name" field value was not specified.

Action: Enter a value for the "Procedure Name" field.
Level: 32

Type: ERROR

Impact: Other

ODI-20262: ODI-20262: Logical Schema is not selected.

Cause: There is no Logical Schema selected for this variable.

Action: Select a Logical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-20300: ODI-20300: Error while printing the diagram

Cause: An unexpected condition has occurred in the print system.

Action: Check the printer settings and physical printer.
Level: 32

Type: ERROR

Impact: Other

ODI-20301: ODI-20301: Error while saving the diagram

Cause: The save file could not be created.

Action: Check the destination folder is writable and that their is sufficient disk space.
Level: 32

Type: ERROR

Impact: Other

ODI-20310: Unsupported Flavor

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20311: ODI-20311: An unexpected exception occurred while reading or writing a text in a business object. Please contact Oracle technical support.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20312: ODI-20312: An error occurred while printing.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20313: ODI-20313: Could not double click

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20315: ODI-20315: Invalid Password

Cause: The Password is incorrect.

Action: Correct the password and try again.
Level: 32

Type: ERROR

Impact: Other

ODI-20316: ODI-20316: A timeout occurred while trying to establish a connection.

Cause: A timeout error occurred while connecting to the database.

Action: Verify that the Database Connection details are correct and the database is available.
Level: 32

Type: ERROR

Impact: Other

ODI-20317: ODI-20317: The field "{0}" is mandatory.

Cause: A value has not been provided for a required field.

Action: Enter a value for the named field.
Level: 32

Type: ERROR

Impact: Other

ODI-20318: ODI-20318: The icon {0} cannot be found.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20319: ODI-20319: {0} is not a valid date for field {1}. The format is: {2}

Cause: The format of the date does not match the required format.

Action: Enter a valid date using the correct date format.
Level: 32

Type: ERROR

Impact: Other

ODI-20320: ODI-20320: Error when applying changes.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20321: ODI-20321: Error when initializing the panel.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20322: ODI-20322: Unable to add a Step.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20323: ODI-20323: Unable to execute the step

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20324: ODI-20324: Cannot execute the Package

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20325: ODI-20325: Unable to open the linked object.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20326: ODI-20326: Unable to edit the text

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20327: ODI-20327: Unable to modify the value.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20328: ODI-20328: Unable to define the next Step.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20329: ODI-20329: Unable to delete Steps(s). You do not have Edit privileges.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20330: ODI-20330: Unable to delete Link(s). You do not have Edit privileges.

Cause: You must have Edit privilege on each steps of the link.

Action: Review the Security settings for the steps and ensure that you have the correct permissions.
Level: 32

Type: ERROR

Impact: Other

ODI-20331: ODI-20331: The Step diagram is not be accessible.

Cause: You do not have permission to access this step.

Action: Check the diagram security settings and verify that you have permission to access the diagram.
Level: 32

Type: ERROR

Impact: Other

ODI-20332: ODI-20332: Cannot change the position of this object

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20333: ODI-20333: Cannot view this Step because the Package is being edited

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20335: ODI-20335: Printing Options not accessible.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20336: ODI-20336: Unknown event sent to the Package event manager.

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20337: ODI-20337: A Knowledge Module cannot be added as a Step.

Cause: Only a DataStore,Model,Sub Model,Interface,Procedure or Variable can be added as a Step.

Action: Use a valid object type for your step creation.
Level: 32

Type: ERROR

Impact: Other

ODI-20338: ODI-20338: A starting Step must be defined.

Cause: A Starting step has been defined.

Action: Select the first step in the package and mark is the starting step.
Level: 32

Type: ERROR

Impact: Other

ODI-20339: ODI-20339: One or more Steps are not linked.

Cause: All steps must be linked.

Action: Ensure that all steps are linked .
Level: 32

Type: ERROR

Impact: Other

ODI-20340: ODI-20340: Only one starting Step can be defined.

Cause: A package must have one and only one starting steps.

Action: Ensure that you have only one starting step defined .
Level: 32

Type: ERROR

Impact: Other

ODI-20341: ODI-20341: You don't have the appropriate privileges.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20342: ODI-20342: Cannot open the Expression Editor

Cause: An unexpected error has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20343: ODI-20343: There are errors in your diagram

Cause: The diagram may contain objects that are not connected, or objects that are not completely defined.

Action: Check the diagram and ensure that all objects are connected and fully defined.
Level: 32

Type: ERROR

Impact: Other

ODI-20344: ODI-20344: Cannot launch the editor for this expression

Cause: An error occured while retrieving the language for the expression. This may be due to an unexpected exception, or the language may not be available for the schema's technology.

Action: Review the message log for additional errors. Ensure that the schema has a valid technology for which the language is set.
Level: 32

Type: ERROR

Impact: Other

ODI-20345: ODI-20345: Cannot change the clause position

Cause: An unexpected internal exception has occured.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-20346: ODI-20346: Cannot get the boolean value of an option

Cause: The boolean value of the option could not be retrieved due to a security error.

Action: Review the message log and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20347: ODI-20347: Error during data transfer for drag and drop

Cause: An internal error occured while dropping the object into the diagram.

Action: Review the message log for additional information and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20348: ODI-20348: An interface with the same name already exists in this folder. Please change the name of the new interface.

Cause: An interface with the specified name exists in the folder. The interface name must be unique within a folder.

Action: Enter a new interface name that is unique within the folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20349: ODI-20349: Unknown event detected by the event manager. Please contact Oracle Support Services.

Cause: The Package Event Manager was called to action an unknown event.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20350: ODI-20350: Your diagram contains one or more FATAL/CRITICAL errors preventing display of the Flow Editor

Cause: The diagram is incomplete or contains errors that prevent the Flow Editor being displayed.

Action: Return to the diagram tab and review the error messages using the errors and warnings button in the toolbar. Fix the errors in order to access the Flow Editor.
Level: 32

Type: ERROR

Impact: Other

ODI-20351: ODI-20351: Error adding source to Quick Edit source table.

Cause: An internal error occured which prevented the source being added.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20352: ODI-20352: Error adding target datastore to Quick Edit mapping table.

Cause: An internal error occured which prevented the target being added.

Action: Contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-20353: ODI-20353: Only a single column may be pasted into a Quick Edit table.

Cause: The clipboard contains multiple columns. Quick Edit only supports pasting a single cell into a table.

Action: Select the cells to be copied and paste them one at a time.
Level: 32

Type: ERROR

Impact: Other

ODI-20354: ODI-20354: Paste targets must be in the same column as the previous copy. This does not apply to Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).

Cause: You have selected a value from one column, and tried to paste it into a different column. This is only supported for Expression Columns.

Action: Please enter the values into the cell manually.
Level: 32

Type: ERROR

Impact: Other

ODI-20355: ODI-20355: Duplicate value is not supported on this column.

Cause: The paste operation is not permitted in the Alias and Target Column Name fields as these fields must contain a unique value.

Action: Please enter the Alias or Name field manually.
Level: 32

Type: ERROR

Impact: Other

ODI-20356: ODI-20356: Can not perform paste into a read-only column.

Cause: The Paste operation is not permitted on read-only columns.

Action: You may not update this value in the table.
Level: 32

Type: ERROR

Impact: Other

ODI-20357: ODI-20357: Can not perform deletion because the target datastore is not temporary.

Cause: An attempt was made to delete a row in the target, but the target datastore is not a temporary table. Only rows in a temporary target table may be deleted.

Action: You cannot delete the row.
Level: 32

Type: ERROR

Impact: Other

ODI-20358: ODI-20358: Interface cannot be saved because it has a fatal error: {0}.

Cause: The Interface could not be saved because it contains a fatal error which must be resolved.

Action: Review the errors in the Diagram tab and resolve the fatal errors.
Level: 32

Type: ERROR

Impact: Other

ODI-20359: ODI-20359: Only one cell can be copied one at a time.

Cause: More than one cell was selected. Quick Edit only supports copying a single cell.

Action: Select and copy a single cell.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20360: ODI-20360: Only Expression columns support Copy and Paste from other applications. For all other columns, please perform a copy first on that column before pasting.

Cause: Only values from other applications may be copied into Expression columns.

Action: For all other columns, perform a copy first on that column before pasting.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20361: ODI-20361: Can not perform Copy and Paste across tables, except for Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).

Cause: Values may not be copied between tables in Quick Edit, apart from between Expression columns.

Action: Please enter the values manually.
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20362: ODI-20362: Couldn't connect to Web Service

Cause: An error occured while creating a connection to the Web Service.

Action: Ensure that the Web Service is accessible and WSDL URL is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-20363: ODI-20363: Error while exporting request

Cause: The request could not be exported

Action: Check that there is sufficient disk space and that the target directory is accessible.
Level: 32

Type: ERROR

Impact: Other

ODI-20364: ODI-20364: Error while parsing the XML file

Cause: An error occured while parsing the XML file

Action: Ensure that the correct XML file is specified and that it is correctly structured
Level: 32

Type: ERROR

Impact: Other

ODI-20365: ODI-20365: There is no port with SOAP binding defined on this service

Cause: The referenced service does not support the specified port

Action: Specify a valid port for the service
Level: 32

Type: ERROR

Impact: Other

ODI-20366: ODI-20366: The timeout must be an integer value.

Cause: The value entered for the timeout is not a valid integer

Action: Enter a valid integer value
Level: 32

Type: ERROR

Impact: Other

ODI-20367: ODI-20367: Export directory {0} does not exist.

Cause: The specified directory does not exist

Action: Create the directory and repeat the operation
Level: 32

Type: ERROR

Impact: Other

ODI-20368: ODI-20368: WSDL URL is null or empty, ODI can not initialize the current request.

Cause: WSDL URL is null

Action: Set the WSDL URL or remove the soap request.
Level: 32

Type: ERROR

Impact: Other

ODI-20370: ODI-20370 : Shortcuts within a project can only refer to objects that belong to that same project

Cause: Shortcuts within a project can only refer to objects that belong to that same project

Action: =Try another folder destination
Level: 32

Type: ERROR

Impact: Other

ODI-20371: ODI-20371 : No two shortcut objects within a folder may refer to the same base object

Cause: No two shortcut objects within a folder may refer to the same base object

Action: Try another folder destination or fix folder contents
Level: 32

Type: ERROR

Impact: Other

ODI-20372: ODI-20372 : The source and destination models must be defined with the same Technology

Cause: The source and destination models must be defined with the same Technology

Action: Try another model destination or fix model properties.
Level: 32

Type: ERROR

Impact: Other

ODI-20373: ODI-20373 : No two shortcuts within a model may contain the same base object

Cause: No two shortcuts within a model may contain the same base object

Action: Try another folder destination or fix model contents.
Level: 32

Type: ERROR

Impact: Other

ODI-20374: ODI-20374 : A model cannot contain a datastore and a datastore shortcut to another datastore with the same datastore name

Cause: A model cannot contain a datastore and a shortcut to another datastore with the same datastore name

Action: Try another folder destination or fix model contents.
Level: 32

Type: ERROR

Impact: Other

ODI-20701: ODI-20701: The Name field is mandatory.

Cause: The Name field was not entered.

Action: Enter a name for the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20702: ODI-20702: The name given for the Load Plan is already used by another load plan. Please provide another name.

Cause: The name provided for the Load Plan was not unique.

Action: Enter a unique name for the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20703: ODI-20703: Variable "{0}" is not found.

Cause: The variable could not be found.

Action: Provide another name for the variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20704: ODI-20704: Datatype of variable "{0}" has been changed.

Cause: The datatype of the original variable is different to the datatype of the load plan variable.

Action: Verify the datatype of the variable and ensure that the types of the original and load plan variables match.
Level: 32

Type: ERROR

Impact: Other

ODI-20705: ODI-20705: This variable is used in one or more case steps. Removing it will trigger deletion of those case steps, and all of their child steps. Do you want to continue?

Cause: An attempt was made to remove a variable which is used in one or more case steps.

Action: To remove the variable and its associated case steps, click Yes. Otherwise, click No, and nothing will be removed.
Level: 32

Type: WARNING

Impact: Other

ODI-20706: ODI-20706: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Enter a name for the Step.
Level: 32

Type: ERROR

Impact: Other

ODI-20707: ODI-20707: The Variable is mandatory.

Cause: A Variable was not selected.

Action: Select a variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20708: ODI-20708: The Scenario is mandatory.

Cause: A Scenario was not selected.

Action: Select a Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20709: ODI-20709: The Value is mandatory.

Cause: A Value was not provided.

Action: Enter a Value.
Level: 32

Type: ERROR

Impact: Other

ODI-20710: ODI-20710: The Value format is not valid.

Cause: An incorrect format was given for the Value.

Action: Check the format of the Value and correct it.
Level: 32

Type: ERROR

Impact: Other

ODI-20711: ODI-20711: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Provide the name of the Step.
Level: 32

Type: ERROR

Impact: Other

ODI-20712: ODI-20712: The Variable is mandatory.

Cause: A Variable was not selected.

Action: Select a Variable.
Level: 32

Type: ERROR

Impact: Other

ODI-20713: ODI-20713: The Scenario is mandatory.

Cause: A Scenario was not selected.

Action: Select a Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20714: ODI-20714: The Context is mandatory.

Cause: A Context was not selected for execution.

Action: Select an execution Context.
Level: 32

Type: ERROR

Impact: Other

ODI-20715: ODI-20715: The Logical Agent is mandatory.

Cause: A Logical Agent was not selected for execution.

Action: Select a Logical Agent.
Level: 32

Type: ERROR

Impact: Other

ODI-20716: ODI-20716: No Physical Agent is defined for the selected Logical Agent and Context. Edit Logical Agent "{0}", and define a Physical Agent for Context "{1}".

Cause: There was no Physical Agent associated with this Logical Agent in the specified context.

Action: Associate a Physical Agent with the Logical Agent in the selected context.
Level: 32

Type: ERROR

Impact: Other

ODI-20717: ODI-20717: No Physical Agents are running. A Physical Agent must be running in order to Restart a Load Plan.

Cause: There were no Physical Agents running.

Action: Start a Physical Agent before restarting the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20718: ODI-20718: No Physical Agents are running. A Physical Agent must be running in order to Stop a Load Plan.

Cause: There were no Physical Agents running.

Action: Start the Agent before executing the Load Plan.
Level: 32

Type: ERROR

Impact: Other

ODI-20719: ODI-20719: Scenario "{0}" is not found.

Cause: The scenario was not found.

Action: Specify an existing scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-20720: ODI-20720: Physical Agent "{0}" - which is defined in Logical Agent "{1}" to be used for Context "{2}" - is not responding. Verify that Physical Agent "{0}" has been started.

Cause: The Physical Agent was not reachable.

Action: Check the Physical Agent and start it.
Level: 32

Type: ERROR

Impact: Other

ODI-20721: ODI-20721: Interface contains one or more errors. You should correct the errors before attempting to execute it

Cause: The interface contains errors which prevent it from being executed.

Action: Review the errors shown in the interface editor and update the interface to fix the problems.
Level: 32

Type: ERROR

Impact: Other

ODI-20722: ODI-20722: Cannot display data. Source alias is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.

Cause: Source alias exceeded the limit allowed by its technology.

Action: Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing source alias to comply.
Level: 32

Type: ERROR

Impact: Other

ODI-20723: ODI-20723: There is no any version of scenario {0} found. A scenario of the step {1} cannot be refreshed.

Cause: The scenario of step was not found.

Action: Check if specified scenario for this step is correct.
Level: 32

Type: WARNING

Impact: Other

ODI-20724: ODI-20724: Journalized data not found. Journal data view: {0}

Cause: Journal is not started or is stopped.

Action: Ensure the journal is started: select Changed Data Capture > Journal Data.
Level: 32

Type: ERROR

Impact: Other

ODI-20726: ODI-20726: The Step Name is mandatory.

Cause: The Step Name field was not entered.

Action: Enter a name for the Step.
Level: 32

Type: WARNING

Impact: Other

ODI-20727: ODI-20727: Scenario "{0}" parent is not found.

Cause: The Scenario source object does not exist.

Action: Check if the source object, from which the Scenario was generated, does exist.
Level: 32

Type: ERROR

Impact: Other

ODI-20728: ODI-20728: The attribute name is mandatory

Cause: The datastore attribute could not be saved because the mandatory Name field was not entered.

Action: Enter a value in the attribute name field.
Level: 32

Type: ERROR

Impact: Other

ODI-20729: ODI-20729: {0} is a dependant object of the following object(s) {1} and cannot be removed

Cause: Selected object for removal is a dependent object.

Action: Remove the dependent object first.
Level: 32

Type: ERROR

Impact: Other

ODI-20731: ODI-20731: The parent from which this scenario is generated does not exist anymore so the editor couldn't show the parent related information.

Cause: The editor couldn't show the parent related information because the scenario parent does not exist anymore. This could happen, for example, if you imported the scenario, but didn't import it's parent object.

Action: Try to figure out, why the scenario parent object does not exist. Try to restore the parent.
Level: 32

Type: ERROR

Impact: Other

ODI-20732: ODI-20732: You cannot move a submodel into another model.

Cause: An unsupported operation was attempted.

Action: Submodels cannot be moved into hierarchy of another models.
Level: 32

Type: ERROR

Impact: Other

ODI-20733: ODI-20733: You cannot copy a submodel into another model.

Cause: An unsupported operation was attempted.

Action: Submodels cannot be copied into hierarchy of another models.
Level: 32

Type: ERROR

Impact: Other

ODI-20734: ODI-20734: Changing the name of a user function only impacts the user function itself; Users need to manually change object(s) which reference the old user function name.

Cause: The user function name has been updated

Action: It is the user's responsibility to determine where the user function is referenced and to manually change the name of the user function in those places
Level: 32

Type: WARNING

Impact: Other

ODI-20735: ODI-20735: The name given for the Physical Agent is already used by another agent. Please provide another name

Cause: The name provided for the Physical Agent was not unique.

Action: Enter a unique name for the Physical Agent.
Level: 32

Type: ERROR

Impact: Other

ODI-20736: ODI-20736: The Name field is mandatory.

Cause: The value for the Name field was not specified.

Action: Enter a name for the Object.
Level: 32

Type: ERROR

Impact: Other

ODI-20737: Could not build WSDL Model.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-20741: ODI-20741: This is not a valid Cobol Copybook.

Cause: The file chosen in the Reverse Engineering Cobol Copybook process is not a valid Cobol Copybook.

Action: Ensure the file is a valid Cobol Copybook.
Level: 32

Type: ERROR

Impact: Other

ODI-20742: ODI-20742: You cannot copy a mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Mappings cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20743: ODI-20743: You cannot copy a reusable mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Reusable mappings cannot be copied into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20744: ODI-20744: You cannot move a mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Mappings cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20745: ODI-20745: You cannot move a reusable mapping into a folder belonging to another project.

Cause: An unsupported operation was attempted.

Action: Reusable mappings cannot be moved into hierarchy of another projects.
Level: 32

Type: ERROR

Impact: Other

ODI-20746: ODI-20746: You cannot move a global reusable mapping into a folder.

Cause: An unsupported operation was attempted.

Action: Global Reusable mappings cannot be moved into a folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20747: ODI-20747: You cannot copy a global reusable mapping into a folder.

Cause: An unsupported operation was attempted.

Action: Global Reusable mappings cannot be copied into a folder.
Level: 32

Type: ERROR

Impact: Other

ODI-20748: ODI-20748: Open is not valid for this node.

Cause: The editor is not applicable for this node.

Action: Editor cannot be opened for this node.
Level: 32

Type: ERROR

Impact: Other

ODI-20749: ODI-20749: Selected Capture/Initial Load Capture process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.

Cause: Selected Goldengate Capture/Initial Load Capture process is used in a different model.

Action: Select a different set of process instances for this model.
Level: 32

Type: ERROR

Impact: Other

ODI-20750: ODI-20750: Selected Delivery/Initial Load Delivery process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.

Cause: Selected Goldengate Delivery/Initial Load Delivery process is used in a different model.

Action: Select a different set of process instances for this model.
Level: 32

Type: ERROR

Impact: Other

ODI-20751: ODI-20751: Load Plan Debugging is not supported: {0}.

Cause: An unsupported operation was attempted.

Action: Load Plan can't be debug.
Level: 32

Type: ERROR

Impact: Other

ODI-20752: ODI-20752: Format can not be empty for File datastore's Date type column

Cause: Column added for the File datastore has Date as type but Format is not given

Action: Ensure the Format is entered for File datatsore's column of type Date.
Level: 32

Type: ERROR

Impact: Other

ODI-20753: ODI-20753 : Shortcuts in a Model can not be moved

Cause: Shortcuts in a Model can not be moved to another Model

Action: Please get the base object of the shortcut first and then try to move
Level: 32

Type: ERROR

Impact: Other

ODI-20754: ODI-20754 : Driver name cannot be empty

Cause: Driver is not assigned for the Data Server

Action: Please choose the appropriate driver for the datastore.
Level: 32

Type: ERROR

Impact: Other

ODI-20755: ODI-20755: A Data Server with the name {0} already exists. Please provide another name.

Cause: The name provided for the Data Server is not unique.

Action: Enter a unique name for the Data Server.
Level: 32

Type: ERROR

Impact: Other

ODI-20756: ODI-20756: A Logical Schema with the name {0} already exists. Please provide another name.

Cause: The name provided for the Logical Schema is not unique.

Action: Enter a unique name for the Data Server.
Level: 32

Type: ERROR

Impact: Other

ODI-20757: ODI-20757: If logical schema is specified, WSDL URL can not differ from physical schema's WSDL URL.

Cause: You have specified different WSDL URL compared to physical schema WSDL URL.

Action: WSDL URL and physical schema WSDL URL should be same when logical schema is specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20758: ODI-20758: If logical schema is specified, HTTP User can not differ from physical schema's/data server's HTTP User.

Cause: You have specified different user compared to physical schema/data server HTTP user.

Action: User and physical schema/data server HTTP user should be same when logical schema is specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20759: ODI-20759: If logical schema is specified, Port Type can not differ from physical schema's port type.

Cause: You have specified different port type compared to physical schema port type.

Action: Port type and physical schema port type should be same when logical schema is specified.
Level: 32

Type: ERROR

Impact: Other

ODI-20760: ODI-20760: Choice names should be unique.

Cause: You have added duplicate choice names.

Action: Ensure only unique choice names are used.
Level: 32

Type: ERROR

Impact: Other

ODI-23001: ODI-23001: The import process failed

Cause: The work repository export file specified could not be imported.

Action: Ensure the specified file is readable and is a valid work repository export file.
Level: 32

Type: ERROR

Impact: Other

ODI-23006: ODI-23006: Agent Test failed

Cause: Agent could not be contacted using the specified connection details.

Action: Ensure the Agent connection details are correct and the Agent is running.
Level: 32

Type: ERROR

Impact: Other

ODI-23007: ODI-23007: Data Source already exists for "{0}".

Cause: The Data Source has already been associated with this Agent.

Action: No action is necessary as the Data Source is already associated with this Agent. Consider removing the Data Source from this Agent and retrying this action.
Level: 32

Type: ERROR

Impact: Other

ODI-23010: ODI-23010: Please enter first a name, an expression and a help text for this language element.

Cause: The Name, Expression or Help Text parameter values for this Language Element were not entered in the Definition panel. These are mandatory parameters.

Action: Return to the Definition panel and ensure the Name, Expression and Help Text parameters have valid values.
Level: 32

Type: ERROR

Impact: Other

ODI-23011: ODI-23011: Name is empty

Cause: A value for the Name parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a valid value for the Name parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23012: ODI-23012: Expression is empty

Cause: A value for the Expression parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a valid value for the Expression parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23013: ODI-23013: Help is undefined

Cause: A value for the Help Text parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a value for the Help Text parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23014: ODI-23014: Technology is undefined

Cause: A value for the Technology parameter of the Language Element Implementation was not entered. This is a mandatory parameter.

Action: Enter a value for the Technology parameter before saving this Language Element.
Level: 32

Type: ERROR

Impact: Other

ODI-23015: ODI-23015: Logical Schema {0} is already linked to a physical schema in context {1}.

Cause: A Physical Schema has already been defined for this Context and Logical Schema combination.

Action: Remove the Context and Logical Schema combination from the Context editor, then retry saving the Physical Schema.
Level: 32

Type: ERROR

Impact: Other

ODI-23016: ODI-23016: The context is either invalid or no longer exists in the database.

Cause: One of the Contexts used by the Physical Schema is invalid or no longer exists in the Master Repository.

Action: Ensure the Context for the Physical Schema is correct by either selecting a valid Context for the Physical Schema or recreating the missing Context.
Level: 32

Type: ERROR

Impact: Other

ODI-23017: ODI-23017: This Physical Schema already exists for this data server.

Cause: A Physical Schema referencing this Data Server has already been defined in the Master Repository.

Action: Specify the correct Physical Schema for this Data Server to use.
Level: 32

Type: ERROR

Impact: Other

ODI-23018: ODI-23018: Unable to connect to Work Repository

Cause: The Work Repository could not be accessed using the connection details defined for it. This may be due to the database or host not being available, or the password could have changed.

Action: Ensure the Work Repository host and database are active. Using the Work Repository editor, ensure the connection details for it are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-23019: ODI-23019: Error Detected during Repository Installation. Invalid connection parameters.

Cause: The repository installation process was unable to connect to the repository database.

Action: Correct any errors identified in the installation log and retry the installation. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23020: ODI-23020: Error Detected during Repository Installation. Invalid External Authentication credentials.

Cause: The ODI Supervisor credentials supplied did not match the credentials held in the External Password Store.

Action: Retry the installation, ensuring the Supervisor user name and password match those held in the external store.
Level: 32

Type: ERROR

Impact: Other

ODI-23021: ODI-23021: Error Detected during Repository Installation. Invalid External Authentication configuration.

Cause: A connection to the External Authentication Store could not be established.

Action: Ensure the External Authentication Store is available and the connection details specified in the JPS configuration file are valid.
Level: 32

Type: ERROR

Impact: Other

ODI-23022: ODI-23022: An error occurred during the generation of the Data Service.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-23023: ODI-23023: The Schema path ({0}) is not supported

Cause: The Model's Physical Schema attempted to define the Schema path using an unsupported protocol (ftp, http or file).

Action: Change the Physical Schema to not use ftp, http or file protocol to reference the file.
Level: 32

Type: ERROR

Impact: Other

ODI-23024: ODI-23024: The URL is mandatory.

Cause: The URL field has not been entered and is a mandatory parameter.

Action: Enter the URL parameter. A template chosen from the drop down list may help to ensure the syntax is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-23025: ODI-23025: The ID is mandatory.

Cause: The Repository ID parameter has not been entered and is a mandatory parameter.

Action: Enter an integer value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23026: ODI-23026: The ID must be an integer value.

Cause: The value entered for the Repository ID is not a valid integer.

Action: Enter an integer value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23027: ODI-23027: The driver is mandatory.

Cause: A JDBC Driver was not specified and is a mandatory parameter.

Action: Select a JDBC Driver from the list of values.
Level: 32

Type: ERROR

Impact: Other

ODI-23028: ODI-23028: The password is mandatory.

Cause: The Supervisor user's Password parameter was not specified.

Action: Enter the Supervisor password.
Level: 32

Type: ERROR

Impact: Other

ODI-23029: ODI-23029: The confirm password is mandatory.

Cause: The Supervisor user's Confirm Password parameter was not specified.

Action: Enter the Supervisor user's password in the Confirm Password parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23030: ODI-23030: Password and Confirm Password are different

Cause: The Password and Confirm Password parameters are not the same.

Action: Ensure the same value is entered for both the Password and Confirm Password parameters.
Level: 32

Type: ERROR

Impact: Other

ODI-23031: ODI-23031: The Supervisor username is mandatory.

Cause: The Supervisor User parameter was not entered.

Action: Enter a value for the Supervisor User parameter ensuring it matches a user in the external enterprise identify store, or switch to ODI Authentication.
Level: 32

Type: ERROR

Impact: Other

ODI-23032: ODI-23032: Maximum number of sessions cannot be less or equal to 0.

Cause: The Maximum Number of Sessions parameter value was specified as 0.

Action: Change the Maximum Number of Sessions parameter in the Agent Definition tab to a value greater than 0.
Level: 32

Type: ERROR

Impact: Other

ODI-23033: ODI-23033: The file reverse-engineering is only possible for delimited files.

Cause: The file format for the specified file was not delimited.

Action: Select a delimited format file and retry the reverse-engineering action.
Level: 32

Type: ERROR

Impact: Other

ODI-23035: ODI-23035: Can not update the scheduling - This agent may not be running

Cause: The Update Scheduling action could not be performed because the ODI Client could not connect to the Agent.

Action: Check that the Agent connection details are correct and that the agent is running. Use the Agent Test button to check the connection details.
Level: 32

Type: ERROR

Impact: Other

ODI-23036: ODI-23036: Logical Schema not set for this Context

Cause: A Logical Schema entry in the Physical Schema's Context was specified as <Undefined>.

Action: Ensure none of the Logical Schemas on the Physical Schema's Context tab are set to <Undefined>.
Level: 32

Type: ERROR

Impact: Other

ODI-23037: ODI-23037: To use scheduling please associate a Logical Agent to a Physical Agent via the Logical Architecture Accordion in the Topology Navigator

Cause: There are no logical agents available to use for scheduling.

Action: Associate a logical agent with a physical agent using the Topology Navigator and then resubmit your schedule request.
Level: 32

Type: ERROR

Impact: Other

ODI-23038: ODI-23038: Cannot resolve the table name. Check the masks defined for this physical schema.

Cause: The table and schema format could not be calculated. This is because the object mask has not been set for the Physical Schema that contains this table.

Action: From the Topology Navigator edit the Physical Schema containing this table and ensure the Masks parameter value is valid for the schema based on its technology (for example "%SCHEMA.%OBJECT").
Level: 32

Type: ERROR

Impact: Other

ODI-23039: ODI-23039: You cannot carry out this type of export.

Cause: The export type specified is not supported.

Action: Retry the export. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23040: ODI-23040: Import file "{0}" error

Cause: An error occured during the import file process.

Action: Correct any errors identified in the error log and retry the import process. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23042: ODI-23042: An error occurred while changing the repository number.

Cause: An error occured while changing the repository number.

Action: Correct any errors identified in the message log and retry the action. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23043: ODI-23043: The Repository ID must be numeric.

Cause: The value specified for the Repository ID parameter was not a valid numeric value.

Action: Enter a valid numeric value for the Repository ID parameter.
Level: 32

Type: ERROR

Impact: Other

ODI-23044: ODI-23044: The new ID you have chosen is already in use as a table "{0}" primary key. The renumbering has been aborted. No changes have been made.

Cause: The Repository ID specified is already used by an existing object.

Action: Enter a different value for the Repository ID parameter ensuring it is unique within the repository.
Level: 32

Type: ERROR

Impact: Other

ODI-23045: ODI-23045: You may not renumber a repository before version 11. Please upgrade your repository first.

Cause: The renumber functionality is not supported for ODI Repository versions prior to version 11.

Action: Upgrade the repository to version 11 (or higher) and then renumber it.
Level: 32

Type: ERROR

Impact: Other

ODI-23046: ODI-23046: An error was encountered during the test.

Cause: An attempt to connect a Work Repository failed.

Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32

Type: ERROR

Impact: Other

ODI-23047: ODI-23047: Could not connect to the work repository. The renumbering process has been aborted. No changes have been made.

Cause: An attempt to connect a Work Repository failed.

Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32

Type: ERROR

Impact: Other

ODI-23048: ODI-23048: Import report generation error

Cause: The import was performed, but there was an unexpected error while opening the Import Report.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23049: ODI-23049: Error Detected during Repository Installation

Cause: An error occured during the creation or import of the Master Repository.

Action: Correct any errors described in the message log and retry the installation process. If the problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-23050: ODI-23050: The password you entered doesn't match the actual password

Cause: The password you entered doesn't match the actual password

Action: Ensure that the password entered matches the actual password
Level: 32

Type: ERROR

Impact: Other

ODI-23051: ODI-23051: Maximum number of threads must be greater than zero.

Cause: Values for maximum number of threads is not valid

Action: Enter valid value for maximum number of threads
Level: 32

Type: ERROR

Impact: Other

ODI-23052: ODI-23052: Maximum number of thread per session cannot be less than 0.

Cause: Values for maximum number of thread per session is not valid

Action: Enter valid value for maximum number of threads per session
Level: 32

Type: ERROR

Impact: Other

ODI-23053: ODI-23053: Maximum number of threads cannot be less than maximum number of threads per session.

Cause: Maximum number of threads less than maximum number of threads per session

Action: Enter valid values for maximum number of threads and maximum number of threads per session
Level: 32

Type: ERROR

Impact: Other

ODI-23054: ODI-23054: Maximum number of cache entries cannot be less than zero.

Cause: Values for maximum number of cache entries is not valid

Action: Enter valid values for maximum number of cache entries
Level: 32

Type: ERROR

Impact: Other

ODI-23055: ODI-23055: Session Blueprint Lifetime cannot be less than zero.

Cause: Value for session blueprint lifetime is not valid

Action: Enter valid values forsession blueprint lifetime
Level: 32

Type: ERROR

Impact: Other

ODI-23056: ODI-23056: Syntax of condition "{0}" is not valid.

Cause: The entered condition has invalid syntax.

Action: Specify the valid condition expression.
Level: 32

Type: ERROR

Impact: Other

ODI-23057: ODI-23057: The Registry Database is mandatory for MySQL Technology.

Cause: The Registry Database was not specified for MySQL Technology.

Action: Enter the Registry Database for MySQL Technology.
Level: 32

Type: ERROR

Impact: Other

ODI-23058: ODI-23058: This Technology does not support multiple schemas.

Cause: Attempt to create multiple Physical Schemas for Technologies that support only one Schema.

Action: The solution for Technologies that do not support multiple Physical Schemas is to create separate Data Dervers from the Physical Schemas.
Level: 32

Type: ERROR

Impact: Other

ODI-23059: ODI-23059: No Agent selected

Cause: No Agent has been selected for the selected DataSource.

Action: Make sure an Agent is selected for the DataSource.
Level: 32

Type: ERROR

Impact: Other

ODI-23060: ODI-23060: Update Import Modes are not valid for Interfaces

Cause: An invalid import mode of Update is selected for an Interface export file.

Action: Use an import mode other than Update or alternatively only import Mapping export files
Level: 32

Type: ERROR

Impact: Other

ODI-23061: ODI-23061: Syntax of expression "{0}" is not valid.

Cause: The entered expression has invalid syntax.

Action: Specify the valid expression.
Level: 32

Type: ERROR

Impact: Other

ODI-23062: ODI-23062: Maximum number of threads cannot be less then the maximum number of sessions.

Cause: Value for maximum number of threads is less than the maximum number of sessions

Action: Ensure that maximum number of threads is equal to or greater than the maximum number of sessions
Level: 32

Type: ERROR

Impact: Other

ODI-23064: ODI-23064 Language Name must be specified

Cause: Language name is not specified.

Action: Enter Language name on the Languages table.
Level: 32

Type: ERROR

Impact: Other

ODI-23065: ODI-23065 Invalid Parameter values. Key names not unique

Cause: Invalid values.

Action: Parameter values need to be valid including uniquenames for keys.
Level: 32

Type: ERROR

Impact: Other

ODI-23066: ODI-23066: Letter used in the icon input "{0}" is not valid. No Special Characters are allowed to be entered.

Cause: The entered input is invalid.

Action: Enter the valid value.
Level: 32

Type: ERROR

Impact: Other

ODI-23068: ODI-23068 : Degree Of Parallelism For Target has to be in the range of 1 to 99.

Cause: Value entered for Degree Of Parallelism is not in the range 1-99.

Action: Please choose the appropriate Degree Of Parallelism For Target.
Level: 32

Type: ERROR

Impact: Other

ODI-23069: ODI-23069 : Web Application Context must be provided

Cause: No value entered for the Web Application Context.

Action: Please enter value for the Web Application Context.
Level: 32

Type: ERROR

Impact: Other

ODI-23070: ODI-23070: Port number must be an integer between 0 and 65535.

Cause: The value for the Port Number was not valid.

Action: Enter a valid integer value between 0 and 65535 for the Port Number.
Level: 32

Type: ERROR

Impact: Other

ODI-23071: ODI-23071: Invalid Override Endpoint URL.

Cause: Override Endpoint URL enterred is invalid.

Action: Please enter a valid Override Endpoint URL.
Level: 32

Type: ERROR

Impact: Other

ODI-23072: ODI-23072: Invalid WSDL URL.

Cause: WSDL URL enterred is invalid.

Action: Please enter a valid WSDL URL.
Level: 32

Type: ERROR

Impact: Other

ODI-24004: ODI-24004: There are no supervisor accounts in the ODI repository with matching entries in the identity store. Please provide a suitable supervisor account.

Cause: The ODI repository does not have any supervisor account that matches the entries in the identity store.

Action: Create a supervisor account in the ODI repository that matches an entry in the identify store.
Level: 32

Type: ERROR

Impact: Other

ODI-24005: ODI-24005: An error occurred while checking the status of the master repository.

Cause: An unexpected error occurred.

Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-24006: ODI-24006: An error occurred while switching the authentication mode for the master repository.

Cause: An unexpected error occurred.

Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-24007: ODI-24007: Rules should not have empty conditions.

Cause: Rules associated with policy have empty conditions.

Action: Create rules with conditions associated with them.
Level: 32

Type: ERROR

Impact: Other

ODI-25001: ODI-25001: Unable to input a larger element

Cause: The total length of all keywords exceeds the maximum length.

Action: Remove one or more of the keywords, or decrease their lengths.
Level: 32

Type: ERROR

Impact: Other

ODI-25002: ODI-25002: The end date cannot be before the start date.

Cause: The end date is before the start date.

Action: Set the end date to be after the start date.
Level: 32

Type: ERROR

Impact: Other

ODI-25003: ODI-25003: Error while starting session

Cause: An unexpected error occured while starting the session.

Action: Check the error details for further information and contact Oracle Support Services for further assistance.
Level: 32

Type: ERROR

Impact: Other

ODI-25004: ODI-25004: Date Format Not Valid

Cause: One of the Date fields is invalid. This may be the From or To Date.

Action: Click the button to the right of the field to invoke a dialog for entering a valid Time and Date.
Level: 32

Type: ERROR

Impact: Other

ODI-25005: ODI-25005: Incorrect date format . The format is {0}.

Cause: The date format is incorrect.

Action: Use the format that is presented in the error message.
Level: 32

Type: ERROR

Impact: Other

ODI-25006: ODI-25006: At least one agent must be selected.

Cause: Agent selection is mandatory.

Action: Select at least one agent to clean stale sessions.
Level: 32

Type: ERROR

Impact: Other

ODI-25007: ODI-25007: At least one work repository must be selected.

Cause: Work repository selection is mandatory.

Action: Select at least one work repository to clean stale sessions.
Level: 32

Type: ERROR

Impact: Other

ODI-25008: ODI-25008: You are not allowed to delete session variable.

Cause: User attempt to delete session variable.

Action: Cancel deleting session variable.
Level: 32

Type: ERROR

Impact: Other

ODI-25009: ODI-25009: You are not allowed to delete scenario variable.

Cause: User attempt to delete scenario variable.

Action: Cancel deleting scenario variable.
Level: 32

Type: ERROR

Impact: Other

ODI-26001: ODI-26001: Boolean does not correspond to the Field Update Object Layer.

Cause: The repository contained an invalid value of the Field Update property for a checkbox or radio group.

Action: Ensure the repository value is a boolean for checkbox or a valid action command for a radio group.
Level: 32

Type: ERROR

Impact: Other

ODI-26002: ODI-26002: This object is referenced by another object. View the details for more information. You may also see where this object is used in the hierarchy.

Cause: The specified object could not be used because it is referenced by another object.

Action: Remove references to this object. The "Uses" hierarchy may be useful in finding objects references.
Level: 32

Type: ERROR

Impact: Other

ODI-26003: ODI-26003: This object cannot be removed: it is referenced by another object.

Cause: The specified object could not be deleted because it is referenced by another object.

Action: Remove references to this object before deleting it. The "Uses" hierarchy may be useful in finding objects references.
Level: 32

Type: ERROR

Impact: Other

ODI-26004: ODI-26004: Action denied:

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26005: ODI-26005: You are importing an object from another repository with the same identifier. It is forbidden.

Cause: An object in the import file has an identifier which already exists in the repository.

Action: Consider manually changing the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.
Level: 32

Type: ERROR

Impact: Other

ODI-26006: ODI-26006: The specified encryption key is invalid.

Cause: The encryption key specified was found to be invalid during the decrypting phase.

Action: Ensure a valid encryption key is utilized.
Level: 32

Type: ERROR

Impact: Other

ODI-26007: ODI-26007: KM or Procedure not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted KM or Procedure.

Action: Do not attempt to decrypt a non-encrypted KM or Procedure.
Level: 32

Type: ERROR

Impact: Other

ODI-26008: ODI-26008: Scenario not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted Scenario.

Action: Do not attempt to decrypt a non-encrypted Scenario.
Level: 32

Type: ERROR

Impact: Other

ODI-26009: ODI-26009: Action not encrypted. No decryption was performed.

Cause: Decryption was requested for a non-encypted Action.

Action: Do not attempt to decrypt a non-encrypted Action.
Level: 32

Type: ERROR

Impact: Other

ODI-26010: ODI-26010: Decryption failed due to incompatible key.

Cause: The key provided to decrypt was an invalid key.

Action: Ensure the decryption key is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26011: ODI-26011: unable to find specified encryption API

Cause: The specified cryptographic algorithm requested was not available in the environment.

Action: Ensure the environment can access the DES/ECB/PKCS5Padding algorithms and padding.
Level: 32

Type: ERROR

Impact: Other

ODI-26012: ODI-26012: invalid encrypted data.

Cause: The BASE64 content may be invalid or the zip file contents may be corrupted.

Action: Ensure the encrypted data is correct and the decryption key is correctly specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26013: ODI-26013: Your security parameters are insufficient to perform this action.

Cause: The ODI user security parameters do not specifically permit the user to perform this particular action.

Action: Ensure this ODI user is granted the security access to perform this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26014: ODI-26014: The code of your {0} is already used by another {1}. Please give another code to save this {2}.

Cause: The value entered for code must be unique for the entire work repository.

Action: Ensure the a unique value is entered.
Level: 32

Type: ERROR

Impact: Other

ODI-26015: ODI-26015: You do not have sufficient privileges to perform this operation.

Cause: The ODI user security parameters do not specifically permit the user to perform this particular operation.

Action: Ensure this ODI user is granted the security access to perform this operation.
Level: 32

Type: ERROR

Impact: Security

ODI-26016: ODI-26016: The requested operation cannot succeed. The object no longer exists.

Cause: The specified ODI object cannot be accessed because it no longer exists in the repository (it may have been deleted by another ODI user).

Action: Recreate the specified ODI object. Consider importing the object from a backup.
Level: 32

Type: ERROR

Impact: Other

ODI-26017: ODI-26017: Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26018: ODI-26018: Key Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26019: ODI-26019: Action Denied.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26020: ODI-26020: Retrieve method incorrect.

Cause: Retrieve method is incorrect. Must be "set" or "get".

Action: Please change the retrieve method to "set" or "get".
Level: 32

Type: ERROR

Impact: Other

ODI-26021: ODI-26021: Object initialization denied.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26022: ODI-26022: Unrecoverable error during object saving.

Cause: The object could not be saved. This is possibly due to a repository connection error, or inconsistent data values supplied. It's also possible that the object was modified by another user.

Action: Ensure the repository database is available and the data values supplied are valid. Try to save changed data, then refresh edited object and apply changed data again.
Level: 32

Type: ERROR

Impact: Other

ODI-26023: ODI-26023: Cannot create object.

Cause: An unexpected error occured during the object creation process.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26024: ODI-26024: Cannot stop update operation.

Cause: An unexpected error occured during the update operation.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26025: ODI-26025: Display Initialization denied.

Cause: An unexpected error occured during the display initialization process.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26026: ODI-26026: Cannot refresh.

Cause: An unexpected error occured during the refresh process.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26027: ODI-26027: Security not set for the instance. The instance will not be added to the tree.

Cause: Instance security permissions "By repository" were choosen but a concrete repository is not specified.

Action: Ensure a repository is specified.
Level: 32

Type: ERROR

Impact: Security

ODI-26028: ODI-26028: Cannot save your modifications.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26029: ODI-26029: Could not deploy the datasource automatically.

Cause: Weblogic Administration server is not up and running, the server connection parameters are wrong.

Action: Please check Weblogic Administration server connection parameters and the server state.
Level: 32

Type: ERROR

Impact: Other

ODI-26030: ODI-26030: The new password does not meet the password policy. Your change could not be saved.

Cause: The new password does not meet the password policy.

Action: Please verify that the new password meets the password policy (go to the "Security Navigator -> Password policies...").
Level: 32

Type: ERROR

Impact: Other

ODI-26031: ODI-26031: You may not delete work repository {0} because you are connected to it. To delete this repository, reconnect to a different work repository or use a master repository only connection.

Cause: Deletion of a work repository which is currently connected is not supported.

Action: Disconnect from the repository and then connect utilizing a Master Repository Only connection or a different work repository before attempting to delete the specified work repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26032: ODI-26032: This object was modified by {0} on {1} at {2}. Your changes cannot be saved.

Cause: The object was changed in the repository after the editor was opened for this object.

Action: Close the editor without saving changes. Open the editor again and reapply the edits and save. Note: consider using the lock object facility to disallow current modifications to an object.
Level: 32

Type: ERROR

Impact: Other

ODI-26033: ODI-26033: You cannot edit this object because it is locked by another user ({0}). You can only view it.

Cause: The ODI object opened for editing is locked by another user. Other ODI users can only view such objects.

Action: Try to edit the object later.
Level: 32

Type: ERROR

Impact: Other

ODI-26034: ODI-26034: An error occurred while deleting executions.

Cause: The specified executions could not be deleted. This is possibly caused by the repository database connection problems.

Action: Retry to delete the executions. If problem persists, contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26035: ODI-26035: Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26036: ODI-26036: Error while encrypting.

Cause: A general error occured during the ecrypting process, possibly caused by caused by repository database access problems, lack of security permissions, or encryption engine failures,

Action: Retry the encrypt action again.
Level: 32

Type: ERROR

Impact: Other

ODI-26037: ODI-26037: Encryption key is not valid.

Cause: An invalid encryption key was entered causing an encryption engine failure.

Action: Enter a valid encryption key and retry the action.
Level: 32

Type: ERROR

Impact: Other

ODI-26038: ODI-26038: Unable to execute, the selected Logical Agent is not associated to a Physical Agent in the desired Context.

Cause: A Logical Agent was not associated with this Physical Agent in this Context.

Action: Ensure a valid "Logical Agent - Physical Agent" association exists in the desired Context.
Level: 32

Type: ERROR

Impact: Other

ODI-26039: ODI-26039: Connection failed.

Cause: The attempt to connect to the repository failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.

Action: Ensure the repository database is available and acceccesible and the repository connection parameters are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26040: ODI-26040: error while updating

Cause: Failed to update the ODI logins file: snps_login_work.xml.

Action: Ensure write-access is granted to the ODI logins file: snps_login_work.xml.
Level: 32

Type: ERROR

Impact: Other

ODI-26041: ODI-26041: Error while attempting to get FieldData from ObjectDisplay.

Cause: An unexpected error occured obtaining FieldData from ObjectDisplay.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26042: ODI-26042: Error while attempting to set FieldUpdate from ObjectUpdate.

Cause: An unexpected error occured updating FieldUpdate from ObjectUpdate.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26043: ODI-26043: Window closing cancelled by the User.

Cause: User asked to close the parent window where child lines were modified.

Action: No action performed on that.
Level: 32

Type: ERROR

Impact: Other

ODI-26044: ODI-26044: Host Variable Not Found.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26045: ODI-26045: Unable to perform the drop operation.

Cause: Dropped entity is invalid.

Action: Check whether the dropped entity is valid and perform the drag-n-drop action again.
Level: 32

Type: ERROR

Impact: Other

ODI-26046: ODI-26046: MethodGetter was not found

Cause: An unexpected error occured obtaining the getter method.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26047: ODI-26047: Object on method setObjectDisplay(Object pObjectDisplay) is not an array.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26048: ODI-26048: Object on method setObjectDisplay(Object pObjectDisplay) is not a vector.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26049: ODI-26049: Parameters not valid.

Cause: An unexpected error occured due to an invalid parameter value.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26050: ODI-26050: Master repository not installed on this connection.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26051: ODI-26051: XML Export Error.

Cause: An error occured during the creation of the XML Export file.

Action: Ensure the repository is accessible and the export file and its directory are writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26052: ODI-26052: XML Import Error.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26053: ODI-26053: An error occurred during initialization.

Cause: Initialization failed possibly due a repository access failure or insufficient ODI security permissions.

Action: Ensure the repository database is available, and the ODI user security permissions permit connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26054: ODI-26054: Page not available.

Cause: The selected page number was invalid.

Action: Ensure the page number entered is greater than 0 and less than the total number of pages.
Level: 32

Type: ERROR

Impact: Other

ODI-26056: ODI-26056: Error while disconnecting.

Cause: This error is occured while closing the repository database connection after "Test query" action completed.

Action: This error may be ignored.
Level: 32

Type: ERROR

Impact: Other

ODI-26057: ODI-26057: Unable to connect the agent. The agent is probably not started.

Cause: The connection request to the agent failed.

Action: Ensure the agent is started and available. Ensure the connection information is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-26058: ODI-26058: Unable to connect the agent. The agent URL cannot be found.

Cause: The connection request to the agent failed using the given URL.

Action: Ensure the agent is started and available. Ensure the connection URL information is valid.
Level: 32

Type: ERROR

Impact: Other

ODI-26059: ODI-26059: Object on method setObjectDisplay(Object pObjectDisplay) is not a List.

Cause: An unexpected error occured setting ObjectData.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26060: ODI-26060: The Password and Confirmation Password do not match.

Cause: The values entered for Password and Confirmation Password did not match.

Action: Enter the same value for Password and Confirmation Password.
Level: 32

Type: ERROR

Impact: Other

ODI-26061: ODI-26061: The minimum password length is {0} characters.

Cause: The length of the Password entered is less than specified in password policy rule.

Action: Enter a Password whose length is greater than or equal to the specified minimum length.
Level: 32

Type: ERROR

Impact: Other

ODI-26062: ODI-26062: The password violates the following rule: "{0}". Select another password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26063: ODI-26063: Invalid password.

Cause: The password supplied was invalid.

Action: Enter a valid password.
Level: 32

Type: ERROR

Impact: Other

ODI-26064: ODI-26064: Error while exporting.

Cause: An error occured during the creation of the Export file.

Action: Ensure the repository is accessible and the export file and its directory are writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26065: ODI-26065: You must specify all the options.

Cause: This is caused by programmatic error.

Action: ODI users should normally never see this message.
Level: 32

Type: ERROR

Impact: Other

ODI-26066: ODI-26066: An unexpected error has occurred.

Cause: An unexpected error occured this process.

Action: Retry action. If problem persists then contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26067: ODI-26067: mandatory field "Java charset" not entered

Cause: A value for the "Java character set" field was not entered.

Action: Enter a value for the "Java character set" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26068: ODI-26068: unable to load export list in the module: {0}

Cause: The contents of the export file list was not formatted correctly.

Action: Correct the format of the export list file specified.
Level: 32

Type: ERROR

Impact: Other

ODI-26069: ODI-26069: The specified export directory does not exist.

Cause: The specified export directory is invalid.

Action: Ensure the specified export directory exists and is writable.
Level: 32

Type: ERROR

Impact: Other

ODI-26070: ODI-26070: The Open Tool class name must not begin with "Snp" or "Odi".

Cause: The Open Tool class name begins with "Snp" or "Odi".

Action: Ensure the Open Tool class name does not begin with "Snp" or "Odi".
Level: 32

Type: ERROR

Impact: Other

ODI-26071: ODI-26071: Open Tool not activated. Your Open Tool references a class which not found.

Cause: The class name specified in this Open Tool was not found.

Action: Ensure the Open Tool class name specified is valid and available in the class path.
Level: 32

Type: ERROR

Impact: Other

ODI-26072: ODI-26072: Your Open Tool has been installed. You can now use it in a procedure or package.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26073: ODI-26073: Could not activate Open Tool. Check that it is in the "oracledi/userlib" directory.

Cause: The Open Tool references a class which was not found.

Action: Ensure the Open Tool class exists in the "oracledi/userlib" directory.
Level: 32

Type: ERROR

Impact: Other

ODI-26074: ODI-26074: Policy "Name" is a mandatory field.

Cause: A value for the Policy "Name" field value was not entered.

Action: Enter a value for the Policy "Name" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26075: ODI-26075: Policy "Name" must be unique.

Cause: A Policy with the same name already exists.

Action: Enter a unique value in Policy "Name" field.
Level: 32

Type: ERROR

Impact: Other

ODI-26076: ODI-26076: You do not have enough memory to generate this report. Increase the maximum Java heap size value (-Xmx).

Cause: There was not enough memory allocated to generate the report.

Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32

Type: ERROR

Impact: Other

ODI-26077: ODI-26077: Target file name is not specified.

Cause: The Target file name is mandatory and was not specified.

Action: Enter a value for the target file name.
Level: 32

Type: ERROR

Impact: Other

ODI-26078: ODI-26078: Error while creating the version

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26079: ODI-26079: Version already exists, versioning aborted.

Cause: A version with the specified version number already exists.

Action: Enter a unique version number.
Level: 32

Type: ERROR

Impact: Other

ODI-26080: ODI-26080: Unable to delete version {0} for {1} {2}. It is referenced by solution {3}

Cause: Deletion of a version of an object referenced by a Solution was attempted.

Action: Delete the solution referencing the object version. Then retry deleting the object version.
Level: 32

Type: ERROR

Impact: Other

ODI-26081: ODI-26081: Unable to delete version {0} for {1} {2}. It is referenced by version {3} of solution {4}

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26082: ODI-26082: No difference found

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26083: ODI-26083: No difference found.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26084: ODI-26084: Could not compare versions of different objects.

Cause: Objects of different types were selected for comparison.

Action: Select objects of the same type before performing comparison.
Level: 32

Type: ERROR

Impact: Other

ODI-26085: ODI-26085: You cannot restore several versions of the same object.

Cause: Multiple versions were selected for restoring.

Action: Select a single version when performing this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26086: ODI-26086: You cannot select more than one version at the same time.

Cause: Multiple version were selected for this action.

Action: Select a single version when performing this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26087: ODI-26087: You must select a version.

Cause: A version was not selected.

Action: Select a version before performing this action.
Level: 32

Type: ERROR

Impact: Other

ODI-26088: ODI-26088: You must select the version to restore.

Cause: A version to restore was not selected.

Action: Select a version to restore.
Level: 32

Type: ERROR

Impact: Other

ODI-26089: ODI-26089: This object is currently locked by user: {0}. Version restoration cancelled.

Cause: The object selected for restoration was locked by another user.

Action: Ensure the selected object is not locked by another user before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26090: ODI-26090: Object version list is empty.

Cause: The object selected was not versioned.

Action: Select a versioned object before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26091: ODI-26091: An array with an invalid size was passed to SnpsObjectTableColumnTextIntrospectMapper.createMapFromArrayOfArrays.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26092: ODI-26092: Table Model must have at least one Column.

Cause: The Model for this Table did not contain any Columns.

Action: Add at least one Column to the Table's Model.
Level: 32

Type: ERROR

Impact: Other

ODI-26093: ODI-26093: Unable to open window.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26094: ODI-26094: Your license does not allow Changed Data Capture operations.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26095: ODI-26095: This object is locked by {0}. You cannot edit it unless it is unlocked.

Cause: Object could not be opened for write access because it was already locked by another user.

Action: Ensure the selected object is not locked by another user before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26096: ODI-26096: Replacement of object failed.

Cause: The file specified did not contain correctly formed XML.

Action: Ensure the XML in the specified file is valid before retrying the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26097: ODI-26097: Replace failed due to an SQL exception.

Cause: The file used to replace this object is not a valid XML format.

Action: Select a valid XML file format before performing this replace object action.
Level: 32

Type: ERROR

Impact: Other

ODI-26098: ODI-26098: You must specify an Export Path or File.

Cause: Either the Export Path or File was not specified.

Action: Specify a value for either the Export Path or File.
Level: 32

Type: ERROR

Impact: Other

ODI-26099: ODI-26099: You don't have the appropriate license to use this KM

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26100: ODI-26100: You don't have the appropriate privileges on Step objects.

Cause: Package Steps operation failed due to insufficient ODI security permissions.

Action: Ensure the ODI user security permissions are correct for the Package Steps object.
Level: 32

Type: ERROR

Impact: Other

ODI-26101: ODI-26101: The Data Check cannot be performed. A CKM is not selected on the Model.

Cause: No CKM was assigned to the Model.

Action: Enter a CKM for the Model before performing the Data Check. Consider using the Model editor to make this entry.
Level: 32

Type: ERROR

Impact: Other

ODI-26102: ODI-26102: The Service cannot be generated. An Application Server is not selected on the Model.

Cause: No Application Server was assigned to the Model.

Action: Enter an Application Server for the Model before performing Generate Service. Consider using the Model editor to make entry.
Level: 32

Type: ERROR

Impact: Other

ODI-26103: ODI-26103: You must specify a connection parameter

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26104: ODI-26104: You must specify a query parameter

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26105: ODI-26105: Test failed

Cause: The value of Schema, Table, Column or Filter was invalid.

Action: Ensure the Schema, Table, Column and Filter are valid. Consult the details for additional information.
Level: 32

Type: ERROR

Impact: Other

ODI-26106: ODI-26106: Decryption failed. Data has been restored.

Cause: The Decryption process failed.

Action: Consult the details for additional information.
Level: 32

Type: ERROR

Impact: Other

ODI-26107: ODI-26107: Cannot find this {0} icon

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26108: ODI-26108: The specified path is not valid.

Cause: The specified path was invalid or was not found on the file system.

Action: Ensure a valid file system path is entered.
Level: 32

Type: ERROR

Impact: Other

ODI-26109: ODI-26109: Error while reading the search criteria. Invalid file

Cause: The selected file did not contain search criteria in a valid format.

Action: Ensure the selected file is one exported from the ODI search UI and contains correctly formatted search criteria information.
Level: 32

Type: ERROR

Impact: Other

ODI-26110: ODI-26110: An error occurred while saving.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26111: ODI-26111: Error while accessing the file

Cause: The specified file could not be opened.

Action: Ensure the specified file exists and is accessible.
Level: 32

Type: ERROR

Impact: Other

ODI-26112: ODI-26112: Error while performing the search

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26113: ODI-26113: XML parser configuration error

Cause: The selected file is not a valid search criteria file format.

Action: Select a valid search criteria file exported from the ODI search UI.
Level: 32

Type: ERROR

Impact: Other

ODI-26114: ODI-26114: Host cannot be empty.

Cause: The Host field is mandatory and was not specified.

Action: Enter a valid Host name.
Level: 32

Type: ERROR

Impact: Other

ODI-26115: ODI-26115: Port number must be an integer between 1024 and 65535.

Cause: The value for Port Number was not valid.

Action: Enter a valid integer value between 1024 and 65535 for Port Number.
Level: 32

Type: ERROR

Impact: Other

ODI-26116: ODI-26116: User cannot be empty.

Cause: The User field is mandatory and was not supplied.

Action: Enter a valid User Name.
Level: 32

Type: ERROR

Impact: Other

ODI-26117: ODI-26117: Connection failed. Reason:

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26118: ODI-26118: External password storage connection test failed.

Cause: Could not connect to the external password storage with the specified connection details.

Action: Ensure the external password storage is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26119: ODI-26119: Exception when computing the value

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26120: ODI-26120: Fields compared are not the same

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26121: ODI-26121: Error while exploring version

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26122: ODI-26122: Exception when getting the children list

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26123: ODI-26123: Cannot connect to the repository with the provided login information.

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26124: ODI-26124: Exception during connection to the repository with the provided login information:

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26125: ODI-26125: The configured external password storage is still accessible. Instead, use the Password Storage Switch service to change the configuration.

Cause: Could not connect to the external password storage with the specified connection details.

Action: Ensure the external password storage is available and valid connection details are supplied. Consider using the Password Storage Switch service to change the configuration.
Level: 32

Type: ERROR

Impact: Other

ODI-26126: ODI-26126: Error while opening window.

Cause: An unexpected error occured while opening window.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26127: ODI-26127: The selected master repository configured to use internal password storage. Recovery is possible only for external storages.

Cause: Recovery was attempted for a master repository configured to use internal password storage.

Action: Select a master repository not configured to use internal password storage.
Level: 32

Type: ERROR

Impact: Other

ODI-26128: ODI-26128: Unable to open Editor

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26129: ODI-26129: Unable to open Editor: Technology could not be opened twice

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26130: ODI-26130: Could not connect to repository

Cause: Could not connect to a repository with the specified connection details.

Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32

Type: ERROR

Impact: Other

ODI-26131: ODI-26131: Specify Import Path

Cause: A value for Import Path is a mandatory and it was not supplied.

Action: Enter the correct value for the Import Path.
Level: 32

Type: ERROR

Impact: Other

ODI-26132: ODI-26132: Repository id {0} or Repository name {1} is already used in your master repository.

Cause: The ID or Name specified for the master repository were already used.

Action: Enter valid unique values for Repository ID and Repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-26134: ODI-26134: Invalid number format for port number.

Cause: The value specified for Port Number was not in a valid format and number range.

Action: Enter a valid Port Number. See SQL*Net documentation for additional information regarding format and range.
Level: 32

Type: ERROR

Impact: Other

ODI-26135: ODI-26135: The Network Adapter could not establish the connection.

Cause: Connection via the Network Adapter could not be established.

Action: Ensure the network resource is available and the connection details in the Network Adapter are correct..
Level: 32

Type: ERROR

Impact: Other

ODI-26136: ODI-26136: The specified character set is not supported.

Cause: The specified character set was not supported.

Action: Select a supported character set.
Level: 32

Type: ERROR

Impact: Other

ODI-26137: ODI-26137: The context or type are incorrect.

Cause: The selected ODI context is invalid: it was probably removed from the repository database.

Action: Reopen Execution dialog again so that the list of ODI contexts will be reloaded.
Level: 32

Type: ERROR

Impact: Other

ODI-26150: ODI-26150: Incorrect Context.

Cause: A valid Context was not specified.

Action: Select a Context from the list. If none are available then create one from the Topology Navigator.
Level: 32

Type: ERROR

Impact: Other

ODI-26153: ODI-26153: Connection failed; JDBC Error

Cause: An unexpected JDBC error was encountered during the connection process.

Action: Ensure the resource referenced is available and the connection information is correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26155: ODI-26155: No Master Repository on this connection

Cause: A connection to the Master Repository could not be established.

Action: Ensure the Master Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26156: ODI-26156: Designer cannot connect to an Execution repository. The operation will be canceled.

Cause: Unable to establish a connection to the Execution repository.

Action: Ensure the Execution repository is available and the connection details are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26157: ODI-26157: Connection Error

Cause: A connection to the Master Repository could not be established.

Action: Ensure the Master Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26158: ODI-26158: Work Repository Attachment Error

Cause: A connection to the Work Repository could not be established.

Action: Ensure the Work Repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26159: ODI-26159: Error while creating Work Repository

Cause: An unexpected error occurred while creating the Work Repository.

Action: Correct any issues described in the error details.
Level: 32

Type: ERROR

Impact: Other

ODI-26160: ODI-26160: URL not referenced in the list.

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26161: ODI-26161: File Not Found

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26162: ODI-26162: Connection failure

Cause: A connection to the repository could not be established.

Action: Ensure the repository is available and valid connection details are provided.
Level: 32

Type: ERROR

Impact: Other

ODI-26163: ODI-26163: Access Denied

Cause: A connection to the repository could not be established because of insufficient user privilege.

Action: Ensure the ODI user has sufficient privilege to connect to the specified repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26164: ODI-26164: The reverse cannot be executed. Your Model will be created.

Cause: The specified technology or driver did not support standard reverse-engineering.

Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32

Type: ERROR

Impact: Other

ODI-26165: ODI-26165: This driver has no match in the URL list

Cause:

Action:
Level: 32

Type: ERROR

Impact: Other

ODI-26166: ODI-26166: The template was not generated: {0}

Cause: The WLS Template could not be generated.

Action: Correct any errors identified in the error log and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26167: ODI-26167: File System Error: {0}

Cause: Creation of the Server Template file failed due to an error detected by the file system.

Action: Correct any errors identified in the error log. Ensure the file system location is accessible and retry the operation.
Level: 32

Type: ERROR

Impact: Other

ODI-26168: ODI-26168: Client requires a repository with version {0} but the repository version found is {1}

Cause: Could not connect to the repository due to the old repository version.

Action: Update repository to the latest version.
Level: 32

Type: ERROR

Impact: Other

ODI-26169: ODI-26169: JDBC driver is mandatory.

Cause: JDBC driver was not entered.

Action: Provide JDBC driver for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26170: ODI-26170: JDBC URL is mandatory.

Cause: JDBC URL was not entered.

Action: Provide JDBC URL for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26171: ODI-26171: User is mandatory.

Cause: User was not entered.

Action: Provide user for database connection.
Level: 32

Type: ERROR

Impact: Other

ODI-26172: ODI-26172: Id is mandatory.

Cause: Id was not entered.

Action: Provide work repository ID.
Level: 32

Type: ERROR

Impact: Other

ODI-26173: ODI-26173: Name is mandatory.

Cause: Name was not entered.

Action: Provide work repository name.
Level: 32

Type: ERROR

Impact: Other

ODI-26174: ODI-26174: Database connection is not available.

Cause: Connection error occurred while connecting to the database.

Action: Verify that the Database Connection details are correct and the database is available.
Level: 32

Type: ERROR

Impact: Other

ODI-26175: ODI-26175: Import folder does not exist or not a valid folder.

Cause: Non-existing or invalid folder was specified.

Action: Ensure the specified folder path is correct and refers to an existing folder.
Level: 32

Type: ERROR

Impact: Other

ODI-26176: ODI-26176: Import file does not exist or not a valid file.

Cause: Non-existing or invalid file was specified.

Action: Ensure the specified file path is correct and refers to an existing file.
Level: 32

Type: ERROR

Impact: Other

ODI-26177: ODI-26177: Unable to connect to the DBA user.

Cause: Unable to connect to the DBA account.

Action: Check that the DBA username and password are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26178: ODI-26178: Unable to connect to the Repository user.

Cause: Unable to connect to the Repository account.

Action: Check that the Repository connection details are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26179: ODI-26179: Invalid Date Format

Cause: An Invalid Date format was entered in the date filter.

Action: Ensure the date entered is of the required format.
Level: 32

Type: ERROR

Impact: Other

ODI-26180: ODI-26180: Changing the name of a sequence only impacts the sequence itself; Users need to manually change object(s) which reference the old sequence name.

Cause:

Action:
Level: 32

Type: WARNING

Impact: Other

ODI-26181: ODI-26181: Unable to add a Project knowledge module

Cause: An unsupported action was attempted.

Action: No action required as Project knowledge modules are not a valid selection to be added to a solution.
Level: 32

Type: ERROR

Impact: Other

ODI-26182: ODI-26182: Object was modified by another user and cannot be saved.

Cause: The object could not be saved. It's possible that the object was modified by another user.

Action: Try to save changed data, then refresh edited object and apply changed data again.
Level: 32

Type: ERROR

Impact: Other

ODI-26183: ODI-26183: The maximum password length is {0} characters.

Cause: The entered work repository password length is greater than allowed.

Action: Provide a shorter password.
Level: 32

Type: ERROR

Impact: Other

ODI-26184: ODI-26184: SQL error occurred. See error details for more information.

Cause: SQL error occurred while performing UI action.

Action: If this error is not expected, contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26185: ODI-26185: File does not exist or cannot be created. See error details for more information.

Cause: UI action tried to open a file which did not exist, or create a file which could not be created due to some reasons.

Action: Make sure the file path is typed correctly. Make sure application has enough file system permissions in order to create a file at the specified path.
Level: 32

Type: ERROR

Impact: Other

ODI-26186: ODI-26186: Character set is not supported. See error details for more information.

Cause: UI action tried to use character encoding which is not supported.

Action: Make sure character set is typed correctly.
Level: 32

Type: ERROR

Impact: Other

ODI-26187: ODI-26187: Unexpected I/O error occurred. See error details for more information.

Cause: UI action caused unexpected I/O error.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26188: ODI-26188: There is no enough memory to perform this UI action. Increase the maximum Java heap size value (-Xmx).

Cause: UI action requires more memory than available at the current moment.

Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32

Type: ERROR

Impact: Other

ODI-26189: ODI-26189: Unexpected report generation error occurred. See error details for more information.

Cause: UI action caused unexpected report generation error.

Action: Contact Oracle Support Services.
Level: 32

Type: ERROR

Impact: Other

ODI-26190: ODI-26190: A user with same name {0} already exists in ODI. Note: LDAP user name is case insensitive. You have to first drop that user prior to registering or changing this one.

Cause: Due to LDAP user name is case insensitive so ODI will follow same rule in external authenticaiton mode.

Action: Please drop the existing user with same name(ingoring case) first prior to registering this one.
Level: 32

Type: ERROR

Impact: Other

ODI-26191: ODI-26191: You cannot move this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked.
Level: 32

Type: ERROR

Impact: Other

ODI-26192: ODI-26192: You cannot drag & drop this object because it is locked by another user ({0}).

Cause: This object was locked by another user.

Action: Wait until object is unlocked .
Level: 32

Type: ERROR

Impact: Other

ODI-26193: ODI-26193: You are not allowed to delete master repository.

Cause: User attempt to delete master repository.

Action: Cancel deleting master repository.
Level: 32

Type: ERROR

Impact: Other

ODI-26194: ODI-26194: Database Connection User is mandatory.

Cause: Database Connection User was not entered.

Action: Provide Database Connection User.
Level: 32

Type: ERROR

Impact: Other

ODI-26195: ODI-26195: Database Connection Password is mandatory.

Cause: Database Connection Password was not entered.

Action: Provide Database Connection Password.
Level: 32

Type: ERROR

Impact: Other

ODI-26196: ODI-26196: Failed to migrate login information to new format.

Cause: ODI was not able to migrate login information from old format into the new format.

Action: Make sure that directory %ODI_HOME%/oracledi has write permissions. Try manually copying %ODI_HOME%/oracledi/snps_login_work.xml into %ODI_HOME%/oracledi/snps_login_work_12.xml file.
Level: 32

Type: ERROR

Impact: Other

ODI-26197: ODI-26197: Failed to delete old login information.

Cause: ODI was not able to delete old login information after migration from old format into the new format.

Action: Make sure that directory %ODI_HOME%/oracledi and file %ODI_HOME%/oracledi/snps_login_work.xml have write permissions. Try manually removing %ODI_HOME%/oracledi/snps_login_work.xml file.
Level: 32

Type: ERROR

Impact: Other

ODI-26198: ODI-26198: Passwords do not match.

Cause: Password confirmation doesn't match the entered password.

Action: Make sure that password and password confirmation are the same.
Level: 32

Type: ERROR

Impact: Other

ODI-26199: ODI-26199: User {0} is not authorized to grant object {1}.

Cause: Current user is not authorized to grant generic object privileges

Action: Assign generic object privileges to user.
Level: 32

Type: ERROR

Impact: Security

ODI-26200: ODI-26200: User {0} is not authorized to grant method {1}.

Cause: Current user is not authorized to grant generic method privileges

Action: Assign generic method privileges to user.
Level: 32

Type: ERROR

Impact: Security

ODI-26201: ODI-26201: Invalid Export Key. Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).

Cause: Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).

Action: Provide a valid Export Key
Level: 32

Type: ERROR

Impact: Other

ODI-26202: ODI-26202: The Export Key and the confirmed Export Key are not the same.

Cause: Export Key confirmation doesn't match the entered Export Key.

Action: Make sure that the Export Key and confirmed Export Key are the same.
Level: 32

Type: ERROR

Impact: Other

ODI-26203: ODI-26203: The provided Export Key is not correct for the selected file.

Cause: The provided Export Key is not the same as the Export Key of this selected file.

Action: Provide a correct Export Key
Level: 32

Type: ERROR

Impact: Other

ODI-26204: ODI-26204: The incorrect Export Key is entered three times. The Export Key field will be disabled now. You can Import this file without an Export Key (the cipher data will not be imported) or Cancel import.

Cause: The incorrect Export Key entered 3 times.

Action: Continue import this file without importing cipher data or Cancel import.
Level: 32

Type: ERROR

Impact: Other

ODI-26205: ODI-26205: The incorrect Export Key is entered three times. The Export Key field will be disabled now. Please consider other options or Cancel import.

Cause: The incorrect Export Key entered 3 times.

Action: Continue import this file or all files without importing cipher data, or Skip the file, or Cancel import.
Level: 32

Type: ERROR

Impact: Other

ODI-26206: ODI-26206: Unable to connect Registry Database to the DBA user.

Cause: Unable to connect Registry Database by DBA Account.

Action: Check Registry Database and the DBA username and password are correct.
Level: 32

Type: ERROR

Impact: Other

ODI-26207: ODI-26207: An Option with the name {0} already exists. Please provide another name.

Cause: The name provided for the Option is not unique.

Action: Enter a unique name for the Option.
Level: 32

Type: ERROR

Impact: Other

ODI-26208: ODI-26208: Unable to perform move because {0} already exists in folder {1}.

Cause: A folder already consists a such type of object with the same name as a moving object.

Action: Rename an object, which you want to move, or rename, or delete an existing object from a folder.
Level: 32

Type: ERROR

Impact: Other

ODI-26209: ODI-26209: The repository contains map component definitions that are newer than the ones supported by the current client version. Certain operations involving mappings may not function correctly. It is recommended to update your client to a newer version. Do you want to continue?

Cause: A client of an older version is used to connect to a repository containing newer map component definitions.

Action: Update the current client by downloading and installing the latest patch. Insure other clients that connect to the same repository are also at the same patch version.
Level: 32

Type: WARNING

Impact: Other

ODI-26210: ODI-26210: The repository contains map component definitions that are older than the ones supported by the current client version. Clicking Yes will continue the login and the map component definitions will be updated. Clicking No will disconnect from the repository without updating. Do you want to continue?

Cause: The current client contains map component definitions that are newer than the ones recorded in the repository.

Action: Continuing the connection will update the repository with map component definitions at the same version as the client. Check and update other clients that connect to the same repository to the same patch version as the current client.
Level: 32

Type: WARNING

Impact: Other

ODI-30000: Error while parsing request file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30001: One of the following parameters: {0} or {1} must be defined.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-30002: Parameters {0} and {1} cannot be set at the same time.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-30003: OdiOSCommand not supported for this operating system. Use tool "OS Command".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: OperatingSystem

ODI-30004: Agent unreachable

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-30005: One or more child sessions has failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30006: No table matches the specified pattern.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30007: No table matches the specified list.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30008: No variable with this name is used in the session.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30009: Can''t rename file: {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30010: Can''t delete old file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30011: Parameter cannot be null:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30012: This user does not have the privilege to execute this scenario

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Security

ODI-30013: Context not allowed for this user

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Security

ODI-30014: Cannot create directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30016: Internal error: Invalid datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30017: Unable to create persistence table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30018: Unable to find the tables

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30019: The Object id is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30020: The command is not valid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30021: Value 0 is not allowed for -GLOBAL_ROWCOUNT.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30022: Version is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30023: Scenario name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30024: File name is mandatory...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30025: Agent name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30026: Either the "{0}" or the "{1}" parameter is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30027: The parameter -LSCHEMA is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30028: The parameter -SUBSCRIBER_NAME is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30029: Parameter -RESUME_KEY_COL is mandatory when -RESUME_KEY_VAR is used

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30030: Please do not pass values for both "{0}" and "{1}" options together. These two options together are not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30031: The parameter "{0}" is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30032: Unrecognized ODI object type "{0}". Please check the value passed to the parameter "{1}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30033: The parameter "-CONTEXT" is mandatory when running from command line.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30034: Only positive integer values are valid for {0} parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30035: Only non-negative integer values are valid for {0} parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30036: This step cannot be executed in execution work repository because the model meta data does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30037: The specified marker does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30038: OS command returned {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30039: Parameter -RESUME_KEY_VAR is mandatory when -RESUME_KEY_COL is used

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30040: The -TABLE_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30041: LSCHEMA parameter is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30042: SUBSCRIBER_NAME parameter is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30043: You cannot use the OPTIMIZED_WAIT option with the current journalizing method.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30044: Invalid parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30045: Impossible to find a valid name on this machine for the "{0}" file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30046: Session stopped

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30047: You cannot select more than one source.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30048: Unable to find the object with type {0} and identifier {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30049: Version is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30050: The same file cannot be used as the source and the target.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30051: File does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30052: No file found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30053: File name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30054: It is not possible to delete sessions in the queue.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30055: Context is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30056: Sequence name is mandatory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30057: The position is a mandatory parameter.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30058: -SCEN_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30059: The number of child sessions in error state is greater or equal to the MAX_CHILD_ERROR parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30060: The parent session "{0}" does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30061: "{0}" is not a correct value for -OBJECT_TYPE

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30062: There's no table matching the pattern in the database

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30063: -TABLE_NAME and -CDC_SET_NAME cannot be used simultaneously.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30064: You must specify -TABLE_NAME or -CDC_SET_NAME

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30065: Incorrect length at position :{0} for value : {1} expected max size of {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30066: All child sessions have failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30067: -UNIT_ROW_COUNT and -CDC_SET_NAME cannot be used simultaneously.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30068: Unable to find the table(s): {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30069: You must specify a Project

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30070: You have not specified the export scenarios location.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30071: You have not specified the export location.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30072: Unable to delete a running session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30073: Unable to delete a waiting session

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30074: {0}: Illegal value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30075: Cannot be specified at the same time: {0} and {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30076: Unable to save the line number sum

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30077: The variable in use is null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30078: No message.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30079: Mandatory Parameter "{0}" is missing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30080: Cannot copy a directory "{0}" to a regular file "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30081: The source directory file "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30082: The source directory file "{0}" is not a directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30083: Invalid value "{0}" passed for parameter "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30084: File "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30085: Cannot copy file with a regular expression to a regular file "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30086: The FROMDATE {0} should be earlier than the TODATE {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30087: Import failed. No work repository name was defined and the import failed in the master repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30088: Timed out. No result.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30089: Source file "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30090: Scenario name is mandatory ...

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30091: Invalid internal object transition

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30092: Cannot create directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30093: PORT and NAME parameters can''t be used together.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30094: Log files can only be imported in synonym mode INSERT.

Cause: The value of parameter -IMPORT_MODE is invalid for this type of object.

Action: Modify the value of parameter -IMPORT_MODE to SYNONYM_INSERT
Level: 32

Type: ERROR

Impact: Other

ODI-30095: PROMPT option can only be used when ReverseManageShortcut tool is run from ODI UI and on a Local Agent.

Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid for this mode of execution.

Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP
Level: 32

Type: ERROR

Impact: Other

ODI-30096: Invalid shortcut handling mode.

Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid.

Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP or PROMPT.
Level: 32

Type: ERROR

Impact: Other

ODI-30097: -LOCATION parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30098: -OBJECT_NAME parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30099: -OBJECT_TYPE parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30100: -WORKSPACE parameter is mandatory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30101: Enterprise Data Quality project {0} not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30102: Enterprise Data Quality Job {0} not found in Enterprise Data Quality project {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30103: Enterprise Data Quality matching query returned with empty or ambiguous result for {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30104: Model Internal ID is not supported when Legacy ID Compatible Mode is switched off.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30105: Internal ID is not supported for "{0}" when Legacy ID Compatible Mode is switched off. Only Global ID is supported.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30106: JAX-WS Dispatch proxy object could not be created. Check ODI Agent log for error messages.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30107: Upgrade key is required for pre-12.x object import.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30108: Target directory "{0}" does not exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-30109: Error while polling run status of load plan {0} (instance id {1}, run {2}) for execution completion. Last polled status value: {3}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30110: Execution of load plan {0} (instance id {1}, run {2}) ended in status "{3}" instead of "{4}". {5}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30111: Value for mandatory parameter {0} is missing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30112: Invalid logical schema "{0}" selected for PROCESS_LSCHEMA parameter. Oracle Golden Gate process logical schema is expected.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30113: Values for mandatory parameters PROCESS_LSCHEMA and OPERATION are missing.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30114: Oracle GoldenGate process logical schema with the name {0} does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30115: All selected load plan runs ({0}) have completed, with {1} in Error status.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30116: The number of load plan runs in error status ({0} in error out of {1} completed runs), is at or above the MAX_LP_ERROR limit of {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30117: The parent session "{0}" does not exist.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30118: The value "{0}" specified for the -NB_PROCESS parameter is invalid. A valid value must be a positive integer.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30119: Error while splitting XML file. Target file {0} already exists.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30120: Authentication mechanisms (parameter: AUTHMECHANISMS) is required when Use Authentication (parameter: AUTH) is set to Yes.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30121: This operation {0} is not to be invoked

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30122: Error while writing output XML file - {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30124: Error while parsing input XML file - {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30125: Error while creating SystemID using the XML file input - {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30126: Error on parsing header.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30127: Error on parsing footer.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30128: Error while joining XML files.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30129: The user {0} does not have privileges to export Scenario {1} ({2})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30130: The user {0} does not have privileges to import a Scenario.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30131: The user {0} does not have privileges to generate a Scenario.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30132: The user {0} does not have privileges to export Scenarios.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30133: Specified folder with ID {0} does not exist in repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30134: Specified scenario {0} of version {1} does not exist in repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30135: Invalid arguments for OdiExportObject tool. EXPORT_DIR="{0}",FILE_NAME="{1}". When EXPORT_DIR value is not specified, FILE_NAME value must contain absolute path.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30136: Incorrect EDQ server domain name {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-30137: Invalid arguments for OdiExportAllScen when connected to Runtime Repository. Design repository parameters cannot be used on runtime repository.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40001: Cannot join two journalized sets of data: {0} and {1}.

Cause: The generated query object has detected multiple journalized data sources, only one is allowed.

Action: Switch off journalizing for one of the sources, in the logical or physical graph.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-40100: Invalid JDBC URL {0} . No XSD or DTD was provided.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-40101: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40102: The parameter {0} has already been specified for {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40103: No value provided for JMS_DESTINATION

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40104: The URL {0} does not start with {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40105: Connecting to JMS using URL {0} failed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40106: JNDI protocol not specified after the JMS XML protocol prefix : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40107: Path separator ":" after JNDI protocol not found {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40108: "//" after colon not found : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40109: Need more information than JNDI hostname. eg: port, provider : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40110: Could not find JNDI host, port, provider info : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40200: Cannot create the initial JNDI context. Check that the JNDI server is running, and that the following URL is correct ({0}).

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40201: Cannot create the initial JNDI context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40202: Cannot find the target in JNDI ({0})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40203: Cannot find the Connection Factory ({0}) in JNDI

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40204: The URL cannot be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-40205: No connection.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-40206: Problem with getInternalSession

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40207: You must specify the URL parameter

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Configuration

ODI-40208: This function has no effect for this connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40209: Unable to create the table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40210: Unable to drop the table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40212: Missing file structure in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40213: Error performing update

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40214: Error creating prepared statement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40215: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40216: Error performing update

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40217: Error closing resultset

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40218: Error getting next element in resultset

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40219: Error opening file for insert

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40220: Error creating prepared statement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40221: Error writing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40222: Error initializing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40223: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40224: Error obtaining connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40225: Error performing rollback

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40226: Error initializing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40227: Error performing commit

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40228: Error obtaining connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40229: Error performing rollback

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40300: File is read-only.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40301: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40302: Invalid format description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40303: XML/LDAP driver encountered exception during decryption of password for DB connection

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40304: The URL can not be null.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40305: Invalid property "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40306: Property {0} has invalid value {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40400: Invalid format description

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40401: Mis-matched start/end delimiters

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40402: File metadata could not be obtained for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40403: Unable to obtain row structure for file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40404: Array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40405: End must be greater than begin: {0} > {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40406: Bytes are too big for array

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40407: Begin interval must be >= 0: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40408: End interval must not go beyond the size of the pointed array: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40409: Array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40410: End must be greater than begin: {0} > {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40411: Begin interval must be >= 0: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40412: End interval must not go beyond the size of the pointed array: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40413: Bytes are too long for array

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40414: Reader has been closed

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40415: File {0} already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40416: Could not create file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40417: An IOException was caught while creating the file saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40418: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40419: Could not delete file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40420: Bad String size, hex Strings should have an even size

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40421: Cannot code String {0} into {1} bytes using the encoding {2}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40422: The array of bytes is not a valid number:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40423: A bad number was found in a COMP3 format: {0} at position {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40424: Cannot code value {0} on {1} bytes.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40425: Bad number in a ZONED format: {0} at position {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40426: URL must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40427: Unknown property: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40428: Could not write header rows to file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40429: An IOException occured while writing a row saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40430: Unknown property

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40431: Could not close output file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40432: File {0} is read-only

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40433: File {0} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40434: Could not clone a row of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40435: Could not transform data for column {0} value {1} because: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40436: JVM 1.4 at least is required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Compliance

ODI-40437: Number of bad rows actually detected: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40438: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40439: Could not read heading rows from file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40440: Could not close file: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40441: Error reading file: {0} said {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40442: Could not translate value for column {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40443: Could not convert value of type {0} to BigDecimal

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40444: Column not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40445: Column {0} > {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40446: Column {0} negative or zero.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40447: This type is not valid datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40448: File is read-only.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40449: File not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40450: An IOException occured saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40451: Column Not Found:

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40452: Missing file structure in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40453: Missing JMS properties in the request

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40454: Missing host variable at index

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40455: Not a numeric value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40456: A Number datatype was expected instead of :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40457: Parsing error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40458: Unknown column datatype

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40459: An IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40460: Could not transform the data: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40461: A Date datatype was expected instead of :

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40462: File already exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40463: Invalid cursor state

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40464: Invalid descriptor index

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40465: Data array must not be null

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40466: String is too long: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40467: Too many columns on this row

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40468: Row rejected because column {0} contains a bad value.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40469: Value was incorrect for column {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40470: EOF reached but not expected

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40471: Tried to retrieve an int with an {0} object.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40472: Tried to retrieve a short with an {0} object.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40473: This resultset accepts only FETCHFORWARD requests

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40474: This function is unsupported: the software you are using might not be compatible with this driver.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40475: Invalid column name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40476: Expected a comma.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40477: Cannot have a parameter inside a bare statement: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40478: Could not transform data.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40479: Unrecognized command.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40480: Malformed INSERT statement.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40481: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40482: Two selected columns have the same alias: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40483: Could not read value {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40484: Could not read null value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40485: Not a ?

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40486: Could not read value {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40487: Unknown file format

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40488: Invalid COL ALIAS "{0}" for column "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40489: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-40490: Datatype {0} is not implemented for now

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40491: ResultSet already closed. Cannot call next() on it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40492: Property "{0}" is having invalid value "{1}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40500: Unknown parameter : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40501: Syntax: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40502: Can''t begin loading while loading another context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40503: Creating a new element {0} from the object {1} in DN {2} which contains attributes {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40504: Found the key {0} for the element {1} in DN {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40505: Entry {0} in {1} has a key {2} which is different from the original key found: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40506: Adding new attribute {0} for object {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40507: Model Builder

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40508: Not finished loading!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40509: Can''t begin loading while loading another context

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40510: Not finished loading!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40511: Bad element {0} while in level

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40512: Because an element {0} is not supposed to appear here. Please check your data model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40513: Entry {0} in {1} has a key {2} which is different from the original key found: {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40514: Not implemented

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40515: Not implemented

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40516: Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40517: Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40518: The table {0} already exists in the model and could not be added

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40519: The table {0} is a duplicate root

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40520: The table {0} doesn''t exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40521: A NamingException occurred saying {0} because of {1} with the remaining name {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40522: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40523: Property {0} is invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40524: Property {0} from the URL is invalid

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40525: Internal connection is null. This shouldn''t happen that way.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40526: A NamingException occured saying: {0} with this explanation: {1} and this remaining name: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40527: Could not read alias bundle because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40528: A {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40529: Could not write alias bundle because an IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40530: The schema is now in a read only mode because the technology is not HSQL

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40531: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40532: Could not find the element for row of table {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40533: Element {0} has no identifier so this row could not be updated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40534: Exception getting original attributes of baseDN={0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40535: Key column {0} has a null value though it''s required

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40536: Deleting attribute {0} from Object {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40537: Deleting object {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40538: Creating attribute value {0} in attribute {1} from Object {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40539: Adding object {0} to the database from row {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40540: Modifying attribute value {0} to {1} in attribute {2} from Object {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40541: Adding attribute value {0} in attribute {1} from Object {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40542: This update is not permitted because it would move the element to another location in the hierarchy.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40543: This update is not permitted because it would move this attribute to another element.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40544: The attribute {0} cannot exist in an element of class {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40545: Modifying attribute value {0} to {1} in attribute {2} from Object {3}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40546: A user has not been provided

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40547: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40548: Parameter {0} has already been specified. Old value : {1} New value : {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40549: Invalid value specified for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40550: Unable to create IntialLdapContext for {0}. Pagination is not possible. Is LDAP server LDAPv3?

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40551: LdapContext needed for pagination. Found {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40552: Invalid page size : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40553: Unable to get cipher without instance

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40554: Unable to encrypt LDAP2 password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40555: Unable to encrypt LDAP2 password

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40556: URL must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40700: Schema {0} cannot be dropped because it is referenced by one or more connections.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40701: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40702: XSD is required for processing flat files

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40703: Root element name is required for processing flat file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40704: The schema {0} already exists. Use the "REPLACE" option to replace the schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40705: The schema parameter is required in the command SET SCHEMA

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40706: This schema doesn''t exist: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40707: No existing schema with this name: "{0}". Please verify that it is the same schema name than the one you specified in your URL connection.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40708: Error synchronizing automatically the schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40709: The xml file is required in a LOAD FILE command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40710: The schema name is mandatory for the CREATE SCHEMA command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40711: This schema has no DTD and cannot be saved to a XML file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40712: This table doesn''t exist in the schema so it can''t be the root table: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40713: The file parameter is required to write a file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40714: Could not find a file to verify: make sure you are on a schema associated with a file or use the "VALIDATE FILE <FileName>" syntax.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40715: Exception {0} occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40716: Parameter {0} has been declared twice. Old value : {1} New value : {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40717: Unknown parameter : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40718: Could not read the input XML data

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40719: Could not read the XML data because a SAXException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40720: Could not read the XML data because the parser is not configured correctly: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40721: Could not read the XML data because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40722: The data has been altered: {0} !!!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40723: XmlParser not validated.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40724: The same connection should have been returned but I got another one

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40725: Custom varchar column size was not correct: {0} instead of 300

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40726: Truncate did not truncate a table

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40727: Custom numeric column size was not correct: {0} instead of 12

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40728: Could not find the row with a pk=20

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40729: Error: Dropping of a schema that is referenced by another connection is allowed!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40730: Standalone schema type is not compatible with external database storage

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40733: Creating a data inserter which uses prepared statements

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40734: An UnsupportedDatatypeException occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40735: Model type not supported: {0}. Expecting one of dtd, xsd.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40736: IOException occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40737: A parsing exception occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40738: A SAXException was caught while reading the model saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40739: A ParserConfigurationException was caught while reading the model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40740: A duplicate element was found in the DTD/XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40741: A duplicate type was found in the DTD/XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40742: An unknown element was found in the DTD/XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40743: Namespace not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40744: Ambiguous name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40745: Malformed QName

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40746: Unsupported model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40747: Duplicate attribute

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40748: Duplicate reference to an element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40749: Conflicting namespaces

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40750: The model generated by the model mapper was not accepted by a validator

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40751: An XMLUnsupportedException was caught

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40752: The DTD file "{0}" doesn''t exist: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40753: No DTD is associated to the file {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40754: File {0} is already locked by another instance of the XML driver.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40755: Could not lock file {0}: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40756: No DTD was found so no data was retrieved

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40757: An exception occurred while reading the file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40758: Malformed qualified name in root properties: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40759: Both the schema "{0}" and the file "{1}" have been modified!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40760: The root table ({0}) doesn''t exist!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40761: Not enough memory to read the XML file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40762: Cannot write the file because this schema is opened in a read-only mode.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40763: Invalid property definition: "{0}" in "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40764: File {0} is not locked or cannot be unlocked.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40765: Cannot write to an URL.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40766: Could not delete existing file {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40767: Could not rename existing file {0} to make a backup

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40768: Could not save the file {0} because a {1} occurred and said: {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40769: Could not close the file. You should probably close your application: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40770: Could not delete the output file after an error occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40771: Could not restore the original file after an error occurred

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40772: No DTD was found so no data was retrieved

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40773: Connection type not supported: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40774: No DTD was found so no data was retrieved

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40775: Should not occur for prefix generation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40776: Could not free the file {0}. Verify that no .lck file is left.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40777: Found PCDATA in element {0} with values ({1})

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40778: Attribute {0} of element {1} doesn''t exist in the DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40779: Root element was not found in the XML Model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40780: Root element is ambiguous in the XML Model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40781: Could not find the prefix {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40782: Could not find the namespace for the root element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40783: Root element has a malformed name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40784: Prefix {0} should exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40785: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40786: Prefix not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40787: Ambiguous qname for an attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40788: Element {0} is ambiguous and was found in more than one namespace: {1}, {2}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40789: Element {0} doesn''t match the DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40790: Could not find parent element {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40791: Element {0} doesn''t match the DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40792: Prefix not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40793: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40794: Element {0} is ambiguous and was found in more than one namespace

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40795: Element {0} is ambiguous and was found in more than one namespace

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40796: Conflicting namespaces: {0} => {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40797: Namespace {0} was not declared in the model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40798: Unknown type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40799: Root element {0} doesn''t match the DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40800: No root found!

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40801: Ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40802: Namespace not found for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40803: Malformed qualified name {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40804: Empty table for multiple links in attribute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40805: Unknown link type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40806: Multiple roots found: {0} and {1}. Use the parameter 'root_elt' in the URL to choose the root element.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40807: No root found in the DTD file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40808: Should not occur {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40809: Creating a RDB model from an XML model is currently not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40810: Creating an XML model from a RDB model is currently not supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40811: No root on model

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40812: The table {0} which is linked to attribute {1} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40813: Unknown attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40814: Unknown link type: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40815: Ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40816: Bad attribute: {0} in element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40817: Namespace not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40818: Internal error: expected to find PCData in element {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40819: Malformed QName: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40820: *** FATAL *** A duplicate root has been found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40821: *** FATAL *** The potential root is not in the model: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40822: Duplicate attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40823: Type unsupported for PCDATA attribute of element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40824: Two namespaces are in conflict and we cannot build aliases: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40825: *** FATAL *** Could not create a table because it already exists in the model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40826: A Qualified name cannot begin with a colon

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40827: A Qualified name cannot end with a colon

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40828: SnpsXmlNamespaceNotFoundException occured: Should not occur while setting prefixes

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40829: This is a fixed namespace and elements cannot be added to it

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40830: The request type is different

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40831: The request command is different

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40832: A parameter is missing

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40833: A parameter has a bad value

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40834: This token was not expected anymore: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40835: Function not implemented yet: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40836: Cannot drop the default schema

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40837: An error occurred during the creation of the schema: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40838: An error occurred in the cleanup of the schema: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40839: InvalidTableException said: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40840: The table {0} already exists in the schema {1}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40841: Could not create schema with URL "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40842: As no XML and no DTD were provided, the XML schema cannot be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40843: No DTD found and no XML file provided: the XML schema cannot be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40844: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40845: While generating the DTD from the XML file, a "{0}" exception occurred saying: {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40846: Could not close the file because an IOException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40847: An UnupportedDatatypeException occurred saying: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40848: Could not find the file called {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40849: IOException reading file called {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40850: Unsupported DB property "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40851: Table {0} not found in schema {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40852: The default schema cannot be read/write

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40853: The schema {0} cannot be set read/write because it has no associated file

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40854: No file provided for synchronization. Use CREATE FILE <file> FROM <schema> command

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40855: Table {0} already exists but it doesn''t have the correct number of columns

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40856: Column {0} doesn''t exist in table {1}, it is required for this DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40857: Expected one of auto, xml or xsd for parameter ns_prefix_generation

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40858: Found that the file references the DTD or XSD: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40859: Could not read the file to get its associated schema because an IOException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40860: Could not read the file to get its associated schema because a SAXException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40861: Could not read the file to get its associated schema because a ParserConfigurationException occurred saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40862: No DTD was provided and the property "generate_dtd" is set to no

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40863: The parameter generate_dtd has a bad value: {0} . One of 'AUTO', 'YES', 'NO' was expected

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40864: XSD {0} was found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40865: No DTD named {0} was found so the XML schema could not be created

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40866: This schema is in a {0} state and cannot be opened in another state.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40867: Could not connect on schema because it is {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40868: The path {0} doesn''t exist

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40869: The path {0} is not a directory

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40870: You already have a schema opened on this file with another name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40871: Duplicate attribute where no attribute should have been set yet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40872: Unsupported exception saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40873: There are several root tables and the unload is not supported in this case

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40874: Expected to find attribute {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40875: Something unexpected occured. Expected to find datatype {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40876: Extension found in an object of type {0} is not permitted.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40877: Cannot merge types for element {0}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40878: Restriction violated : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40879: An IOException occured while including another schema saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40880: A ParserConfigurationException occured while including another schema saying {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40881: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40882: Cannot add a restriction!: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40883: Cannot add a restriction on a non simple type or attribute

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40884: Extension found outside an element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40885: Type {0} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40886: Cannot merge types for element "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40887: Unexpected element of type {0} in hierarchy before simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40888: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40889: Could not affect complex type to object of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40890: Unexpected element of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40891: An element has no name and doesn''t refer to another element

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40892: Cannot add an element to an attributeGroup (wanting to add {0} to group {1} )

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40893: Cannot add an element to an object of type {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40894: Could not find namespace: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40895: Conflicting Namespace Error: Should not occur: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40896: Unknown prefix: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40897: Cannot handle type [{0}] as a simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40898: Element {0} referenced in group {1} was not found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40899: Attributes' group {0} not found in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40900: Duplicate attribute: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40901: Unsupported exception: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40902: Element group {0} not found in the file.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40903: Duplicate reference while adding an element of a group: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40904: Unsupported exception while adding an element of a group: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40905: Namespace {0} for element {1} referenced in group {2} was not found.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40906: Element {0} referenced in group {1} has an ambiguous name

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40907: An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40908: No more pending objects left in hierarchy

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40909: An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40910: Cannot add element {0} to type {1} because it doesn''t handle references.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40911: One pending element was not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40912: Simple type {0} has a restriction on a type {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40913: The object of type {0} is missing type {1} but don't know how to deal with it.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40914: Element {0} is missing but is referenced

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40915: Type {0} is missing but is needed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40916: Element {0} has no type.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40917: One pending element's namespace was not found: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40918: One pending element has an ambiguous name: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40919: Cannot add element {0} to type {1} because it doesn''t handle references.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40920: An attribute must have a simple type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40921: Could not find the root element that we've just set.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40922: This qualified name is malformed: {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40923: Inner type of element {0} is not defined or is not a complex type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40924: Renamed column {0} to {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40925: Should not occur

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40926: Internal error

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40927: Not Supported

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40928: Not supported for XML driver commands

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40929: Property {0} has invalid value {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40930: Root element {0} specified by user not a global element in the NXSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40931: Unrecognised request type for {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40932: Unable to find root element in DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40933: Unable to build XSD from DTD.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40934: The schema {0} is not created using the appropriate compatibility mode.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40935: The schema {0} was created with correct compatibility mode, but has incorrect XML model type

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40936: Namespace URI for the prefix {0} was not found in the XSD/DTD or XML

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40937: Encountered one more close tag while no more open tags were found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40938: Error splitting prefixed string {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40939: The XML construct "{0}" in element "{1}" from type "{2}" is not supported by XML JDBC driver

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40940: No global elements were found in the XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40941: Requested root element {0} was not found in the XSD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40942: Ending on "{0}" but needed to find "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40945: XSD parser ecnountered error parsing XSD/DTD. Check validity.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40946: Error processing XSD/DTD

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40947: Unable to write xpath mapping information

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40948: Could not find namespace URI {0} in XML model for {1}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40949: Old object type found for namespace {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40951: Unable to find namespace URI : {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40952: Element {0} of type {1} at xpath {2} appears to be same as element {3} of type {4} at xpath {5}.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40953: Prefix "{0}" is already mapped to "{1}" in current XML scope. New uri : "{2}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40956: Root element {0} is substitutionGroup head. This is not allowed.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40957: Unable to resolve path of XSD "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40958: Illegal state. Currently coalescing for "{0}".

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40959: Illegal state. Not coalescing yet.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40960: Unknown object "{0}" found

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40961: You cannot use v1 compatibility flag along with v3 mode

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40962: Error occurred checking if table "{0}" exists

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40963: XSD does not define "anyAttribute" for {0}, but found it in DB.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40964: Element "{0}" is defined in XSD to have "any" element child, but could not find it in model.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40965: Illegal metadata on element "{0}". Element results in column, but has table metadata.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40966: Column metadata set on element with xpath "{0}" while it has child : "{1}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40967: Illegal metadata on attribute "{0}" with xpath "{1}". Attribute may only have column metadata.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40968: Property only supported for complex file driver when inxb/is_nxsd_based=true.

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40969: Trying to use "{0}" data type with Statement not supported. {1} xPath "{2}". Either user has requested not to use PreparedStatement or your DB/driver does not support PreparedStatement

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40970: Trying to use table "{0}" used by "{1}" for "{2}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40971: When user specifies DB type, length and scale must also be specified. Not done for "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40972: More than one "any" associated with element "{0}"

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-40973: URL must start with {0}

Cause:

Action:
Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-50000: Java exception thrown: {0}.

Cause: A java exception was thrown during processing.

Action: Internal Error: contact Oracle support.
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-999999: Expression reference not found: {0}.

Cause: The expression being parsed has a column reference that cannot be found.

Action: Check the expression
Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

39 ODL-52001 to ODL-52816

ODL-52001: deleting log file: {0}, size: {1} bytes

Cause: A log file was deleted because of the rules defined in the current configuration.

Action: This is an information message, no action is needed.
Level: 16

Type: NOTIFICATION

Impact: Logging

ODL-52002: invalid value for parameter {0}: {1}. Value must be greater than zero.

Cause: An invalid value was assigned to a numeric parameter that require a positive value.

Action: Use a value that is greater than zero value for the parameter.
Level: 1

Type: ERROR

Impact: Logging

ODL-52003: invalid value for parameter maxLogSize: {0}. Value must be greater than the value of maxFileSize ({1}).

Cause: The value used for the maxLogSize parameter is smaller than the value used for the maxFileSize parameter, which is not valid.

Action: Enter a value for the maxLogSize parameter that is greater than the value of the maxFileSize parameter.
Level: 1

Type: ERROR

Impact: Logging

ODL-52004: invalid encoding: {0}

Cause: The value used for encoding parameter is not valid.

Action: Enter a valid encoding value.
Level: 1

Type: ERROR

Impact: Logging

ODL-52005: invalid path: {0}. This path is already being used by another log writer instance of a different type.

Cause: There was an attempt to create a log using a path that is already being used by another log, but the two logs are of different types.

Action: Contact Oracle support services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52006: Path cannot be null.

Cause: A null value was used for the log file path.

Action: Enter a non-null value for the path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52007: The log path is not a directory: {0}.

Cause: The value used for the log path is not a directory. Some log types require that the log path be a directory, not a file, because the log file name is fixed.

Action: Enter a directory path instead of a file path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52008: unable to create log directory: {0}

Cause: One or more directories that were used in the log path could not be created.

Action: Make sure that the process has permission to create the directories, or enter a different path. It may also be possible to create the directories manually.
Level: 1

Type: ERROR

Impact: Logging

ODL-52009: The log directory is not writable: {0}.

Cause: The process could not write to the log directory.

Action: Make sure that the process has permission to write to the log directory, or enter a different path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52010: no permission to access log directory: {0}

Cause: The process could not access the log directory.

Action: Make sure that the process has permission to access the log directory, or enter a different path.
Level: 1

Type: ERROR

Impact: Logging

ODL-52011: attempting to operate on a closed LogWriter

Cause: There was an attempt to perform an operation on a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52012: attempting to write to a closed LogWriter

Cause: There was an attempt to writea a message to a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52013: attempting to flush a closed LogWriter.

Cause: There was an attempt to flush a log writer that is already closed.

Action: This is possible a programming error. Contact Oracle Support Services. If the problem occurs during process shut down, it is possible that some component is attempting to log a message after the logging system has already shut down.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52014: Maximum log size is reached.

Cause: The maximum size for the log defined in the configuration was reached and the current configuration does not enable automated removal of older log messages.

Action: Review the logging configuration. It may be necessary to increase the maxLogSize parameter, or enable a policy for the automatic removal of older messages.
Level: 1

Type: ERROR

Impact: Logging

ODL-52015: unable to delete old archived file

Cause: There was an attempt to delete an old log file, but the file could not be deleted.

Action: Check that the process has permission to delete the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52016: failure to rotate log file: {0}

Cause: There was an attempt to rename a log file, but the operation failed.

Action: Check that the process has permission to rename files.
Level: 1

Type: ERROR

Impact: Logging

ODL-52017: out of log file names

Cause: There was an attempt to rename a log file, but there are no more names that can be used.

Action: Remove some or all of the archived files.
Level: 1

Type: ERROR

Impact: Logging

ODL-52018: unable to write to log ''{0}'': {1}

Cause: There was an error when writing messages to a log file.

Action: See the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52019: unable to close log ''{0}'': {1}

Cause: There was an error when closing a log file.

Action: See the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52020: failed to get a lock on file ''{0}'' after {1} milliseconds

Cause: A log file lock could not be acquired within the specified time period, and the log write operation has time-out.

Action: Check that other processes are not holding a lock to the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52021: thread interrupted while waiting to lock file ''{0}''

Cause: The thread was interrupted while waiting to acquire a lock on a lock file.

Action: Check that other processes are not holding a lock to the log file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52029: recursive logging detected that exceeds the recursion depth limit of {0}. The handler will not log the message.

Cause: The handler detect recursive logging calls that exceed that maximum configured recursion depth limit.

Action: Review the source code to eliminate logging calls within code that may be called while formatting a log message.
Level: 1

Type: ERROR

Impact: Logging

ODL-52030: invalid property name: {0}

Cause: An invalid property name was used in the logging configuration.

Action: Review the configuration and enter a valid property name.
Level: 1

Type: ERROR

Impact: Logging

ODL-52031: required property ''{0}'' is not found

Cause: A required property was not present in the configuration of a log handler.

Action: Review the configuration and add the required property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52032: invalid format: {0}. Valid formats are: {1}.

Cause: An invalid value for the 'format' property was used in the configuration of an ODLHandler.

Action: Review the configuration and add a valid value for the format property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52033: invalid value for property {0}: {1}.

Cause: An invalid value for used for an ODLHandler property.

Action: Review the configuration and add a valid value for the property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52034: Configuration is invalid: {0} cannot be less than {1}.

Cause: An invalid value for used for a size property in an ODLHandler configuration.

Action: Review the configuration and make sure that the value of the 'maxFileSize' property is not greater than the value of the 'maxLogSize' property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52035: failure to create ODLHandler: {0}

Cause: An ODLHandler instance could not be created.

Action: Check the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52036: invalid level: {0}. Check spelling and verify that the value is a valid ODL or Java level.

Cause: An invalid level was used in the configuration of a logger or handler.

Action: Review the configuration and enter a valid level.
Level: 1

Type: ERROR

Impact: Logging

ODL-52040: failure to initialize class {0}: property {1} must be defined.

Cause: A required system property was not defined.

Action: Review the process configuration and make sure that the required system property is defined.
Level: 1

Type: ERROR

Impact: Logging

ODL-52041: Use of {0} in logging configuration is deprecated; replacing it with {1}. (File: {2}).

Cause: A deprecated property was used in the logging configuration.

Action: Review the logging configuration and consider replacing the deprecated property. While the configuration may be valid, use of deprecated properties should be avoided.
Level: 1

Type: WARNING

Impact: Logging

ODL-52042: undefined property: {0}.

Cause: An undefined property was used in the logging configuration.

Action: Review the logging and process configuration and either replace the invalid property in the logging configuration, or define a value for the property.
Level: 1

Type: ERROR

Impact: Logging

ODL-52043: expecting one element of type ''{0}''

Cause: The logging configuration contained more than one XML element of a given type, when only one was expected.

Action: Review the logging configuration and remove the extra XML elements.
Level: 1

Type: ERROR

Impact: Logging

ODL-52044: cannot find handler: {0}

Cause: The logging configuration assigned a handler to one or more loggers, but the handler was not defined.

Action: Review the logging configuration and either add the missing handler, or remove any references to the handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52045: invalid class: {0}

Cause: The logging configuration defined an invalid class for a handler.

Action: Review the logging configuration and make sure that the handler class is valid. The handler class must be either a subclass of java.util.logging.Handler, or implement the oracle.core.ojdl.logging.HandlerFactory interface.
Level: 1

Type: ERROR

Impact: Logging

ODL-52046: cannot find class: {0}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be found.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes.
Level: 1

Type: ERROR

Impact: Logging

ODL-52047: cannot load or link class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but that class could not be loaded due to a linkage error.

Action: Review the logging and process configuration and make sure that the class is available in the system classpath, or that the class is visible to the classloader that loads the ODL configuration classes, or that the correct version of the class is being used..
Level: 1

Type: ERROR

Impact: Logging

ODL-52048: Class ''{0}'' is not of expected type ''{1}''.

Cause: The logging configuration defined a handler, filter, or error manager class, but that class is not a handler, filter or error manager instance.

Action: Review the logging and process configuration and make sure that the class is of the correct type.
Level: 1

Type: ERROR

Impact: Logging

ODL-52049: cannot create instance of class ''{0}'': {1}

Cause: The logging configuration defined a handler, filter, or error manager class, but an instance of that class could not be created.

Action: Review the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52050: unable to process file ''{0}'', XML parse exception (line: {1}, column: {2}): {3}

Cause: The logging configuration could not be processed due to an XML error in the configuration file.

Action: Review the error message for a description of the XML error, and correct the problem in the configuration file.
Level: 1

Type: ERROR

Impact: Logging

ODL-52051: unable to process file ''{0}''; exception: {1}

Cause: The logging configuration could not be processed due to a unexpected XML parser error.

Action: Review the error message for a description of the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52052: unable to find resource: {0}

Cause: The logging configuration could not be processed due to a missing XML schema or DTD.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52053: unable to create handler instance using class ''{0}''; exception: {1}

Cause: The creation of a handler instance failed because the handler factory threw an exception.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52054: The logger ''{0}'' is already defined.

Cause: There was an attempt to add a new logger to the configuration file, but the logger is already defined.

Action: Verify that the logger name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52055: The handler ''{0}'' is already defined.

Cause: There was an attempt to add a new handler to the configuration file, but a handler is already defined.

Action: Verify that the handler name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52056: The logger ''{0}'' is not defined.

Cause: There was an attempt to access a logger in the logging configuration but the logger is not defined.

Action: Verify if the logger name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52057: The handler ''{0}'' is not defined.

Cause: There was an attempt to access a handler in the logging configuration but the handler is not defined.

Action: Verify if the handler name is correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52058: The handler ''{0}'' cannot be removed because it is being used by logger ''{1}''.

Cause: There was an attempt to remove a handler from the logging configuration, but the handler could not be removed because it is being used by a logger.

Action: Verify that the handler name is correct, or remove the handler from all the loggers first before attempting to remove the handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52059: The logger ''{0}'' already has handler ''{1}''.

Cause: There was an attempt to add a handler to a logger but the logger already has the given handler.

Action: Verify if the logger and handler names are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52060: The logger ''{0}'' does not have handler ''{1}''.

Cause: There was an attempt to remove a handler from a logger, but the logger does not contain the given handler.

Action: Verify if the logger and handler names are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52061: The handler ''{0}'' does not have property ''{1}''.

Cause: There was an attempt to remove a property from a handler, but the handler does not have a property with the given name.

Action: Verify if the handler and property are correct.
Level: 1

Type: ERROR

Impact: Logging

ODL-52062: Illegal value for ''{0}'': {1}

Cause: There was an attempt to set a property for a handler or logger, but the value of the property is not valid.

Action: Verify if the handler or loggers properties are valid.
Level: 1

Type: ERROR

Impact: Logging

ODL-52063: Unable to load logging configuration from ''{0}''; exception: {1}

Cause: There was an error while loading the logging configuration file.

Action: Review the error message for the root cause.
Level: 1

Type: ERROR

Impact: Logging

ODL-52064: The handler ''{0}'' is already defined in the target logging configuration document.

Cause: There was an attempt to add a handler to a logging configuration file, but a handler with the given name already exists in the target file.

Action: Review the definition of the new handler.
Level: 1

Type: ERROR

Impact: Logging

ODL-52065: The logger ''{0}'' or a descendant is already defined in the target logging configuration document.

Cause: There was an attempt to add a logger to a logging configuration file, but the logger or one of its descendants is already defined in target logging configuration.

Action: Review the definition of the new logger.
Level: 1

Type: ERROR

Impact: Logging

ODL-52080: Reading logging configuration from ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ODL-52081: unable to read logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reading the logging configuration from the given file.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52082: unable to register logging runtime MBean; exception: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Logging

ODL-52083: unable to register log dump; exception: {0}

Cause: There was an error registering the log dump with the FMW Diagnostics Framework.

Action: Review the error message for the root cause. The system may still work, but the log dump will not be available.
Level: 1

Type: WARNING

Impact: Logging

ODL-52084: unable to initialize ODL; exception: {0}

Cause: There was an error initializing Oracle Diagnostic Logging (ODL).

Action: Review the error message for the root cause. Oracle Diagnostic Logging is not properly configured in this system.
Level: 1

Type: ERROR

Impact: Logging

ODL-52085: Reloading logging configuration from ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Logging

ODL-52086: unable to reload logging configuration from file ''{0}''; exception: {1}

Cause: There was an error reloading the logging configuration from the given file.

Action: Review the error message for the root cause.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52087: suspicious logging configuration reload. The original configuration was read from file ''{0}'', but the new configuration is being read from ''{1}''.

Cause: The logging configuration is being reloaded, but the configuration file is different from the configuration file used for the initial configuration.

Action: This is probably an error, there should only be one configuration file.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52088: The java.util.logging configuration was reloaded.

Cause: The java.util.logging configuration was reloaded, probably via the invocation of LogManager.readConfiguration.

Action: The java.util.logging configuration should not be reloaded programmatically, as this can override the ODL configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Logging

ODL-52501: Unable to get OPMN connection for instance ''{0}''; check that the instance name is valid and that OPMN is running.

Cause: There was an attempt to invoke an operation on a OPMN managed target, but a connection to that target could not be created.

Action: Check the target argument and make sure that the instance and component names are valid, and that OPMN is running.
Level: 1

Type: ERROR

Impact: Logging

ODL-52502: Invalid target. The server name ''{0}'' is not a valid server name, the server is not running, or JRF is not enabled on the server.

Cause: There was an attempt to invoke an operation on a Java EE server target, but the target does not exist or is not valid for the operation.

Action: Check the target argument and make sure that the server name is correct, the server is running, and that JRF is enabled on the server.
Level: 1

Type: ERROR

Impact: Logging

ODL-52801: There is already an active trace with ID ''{0}''. Use a different trace ID or stop the active trace first before starting a new trace with the same ID.

Cause: There was an attempt to start a trace using an ID value that is already being used by another active trace.

Action: Use a different trace ID or disable the existing active trace first before starting a new one with the same ID.
Level: 1

Type: ERROR

Impact: Logging

ODL-52802: There is already an active trace for attribute ''{0}'' with value ''{1}''. The existing active trace must be disabled first before a new one can be started for the same attribute value.

Cause: There was an attempt to start a trace using an attribute value that is already used by an active trace.

Action: Use a different attribute value or disable the existing active trace first before starting a new one with the same attribute value.
Level: 1

Type: ERROR

Impact: Logging

ODL-52803: Unable to complete the start tracing operation. The operation failed on target ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because one or more servres are unable to complete the operation.

Action: See the error message for more information on the cause of the server failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52804: The start tracing operation failed for provider ''{0}''; cause: {1}

Cause: The start tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the cause for the provider failure.

Action: See the error message for more information on the cause of the provider failure. You may try to disable the failing provider to obtain trace data from the other trace providers.
Level: 1

Type: ERROR

Impact: Logging

ODL-52805: Unable to complete the start tracing operation. The operation failed for one or more providers and could not be rolled back. The tracing configuration may be in an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.

Cause: The start tracing operation failed for one or more providers or servers but could not be rolled back on all servers or providers.

Action: The tracing system may be on an inconsistent state. Disable all active traces or restart the servers to reset the selective tracing configuration.
Level: 1

Type: ERROR

Impact: Logging

ODL-52806: The stop tracing operation failed for provider ''{0}''; cause: {1}

Cause: The stop tracing operation cannot be completed because a trace provider is unable to complete the operation. See the error message for more information on the reason for the provider failure.

Action: See the error message for more information on the cause of the provider failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52807: Unable to create incident for trace with ID ''{0}''; cause: {1}

Cause: A trace was stopped but an incident could not be created for the trace data.

Action: See the error message for more information on the root causeof the incident creation failure.
Level: 1

Type: ERROR

Impact: Logging

ODL-52808: Invalid expression: {0}

Cause: An invalid expression was passed as a parameter to the startTracing operation.

Action: Review the list of active traces and disable some of the duplicate traces.
Level: 1

Type: ERROR

Impact: Logging

ODL-52809: Multiple active traces match the current request. The request is already being traced with ID ''{0}'' and it will not be traced with ID ''{1}''.

Cause: There are multiple active traces that can be started for the current request, but the request can only be associated with one trace. One or more traces will not be started.

Action: Review the expression and check for incorrect spelling or syntax. See the documentation for details on the expression syntax.
Level: 1

Type: WARNING

Impact: Logging

ODL-52810: A new trace cannot be started because there are too many traces currently active in the system.

Cause: A new trace cannot be started because there are too many traces currently active in the system.There are multiple active traces that can be started for the current request.

Action: Wait until some of the other traces are stopped before trying to start a new one. Contact your system administrator for more information.
Level: 1

Type: ERROR

Impact: Logging

ODL-52811: A new trace cannot be started or stopped for the current HTTP session because there is no current HTTP session.

Cause: A request to start or stop tracing the current HTTP session cannot be executed because there is no HTTP session associated with the current request.

Action: The HTTP session must be already active before tracing operations can be executed for the session.
Level: 1

Type: ERROR

Impact: Logging

ODL-52812: A new trace cannot be started for the current HTTP session because the session is already being traced.

Cause: A request to start tracing the current HTTP session cannot be executed because the session is already being traced.

Action: Stop the active trace before starting a new trace for the same session.
Level: 1

Type: ERROR

Impact: Logging

ODL-52813: A request to stop tracing an HTTP request cannot be executed because the request is not being traced.

Cause: A request to stop tracing an HTTP request cannot be executed because the request is not being traced.

Action: Check if the HTTP request is being traced before trying to stop tracing.
Level: 1

Type: ERROR

Impact: Logging

ODL-52814: Unable to send notification for start tracing event. Tracing will continue on the local server, but may not be enabled on other servers. Cause: {0}

Cause: A JMX notification for a start tracing event could not be sent due to an unexpected exception.

Action: See the error message for more information on the root cause.
Level: 1

Type: WARNING

Impact: Logging

ODL-52815: Unable to send notification for stop tracing event. Tracing is stopped on the local server, but may not be stopped on other servers. Cause: {0}

Cause: A JMX notification for a stop tracing event could not be sent due to an unexpected exception.

Action: See the error message for more information on the root cause.
Level: 1

Type: WARNING

Impact: Logging

ODL-52816: Unable to propagate a {0} event; cause: {0}

Cause: A selective tracing event originating from one server could not be propagated to other servers.

Action: See the error message for more information on the root cause.
Level: 1

Type: WARNING

Impact: Logging

40 OHS-03506 to OHS-04854

OHS-03506: OHS audit configuration load failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03506: OHS audit configuration load failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03507: OHS audit configuration save failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03507: OHS audit configuration save failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03508: Unable to set Custom Log configuration

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03508: Unable to set Custom Log configuration

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03509: CustomLog configuration is wrong

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03509: CustomLog configuration is wrong

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03526: Failed to read file {0}, because of {1} exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03526: Failed to read file {0}, because of {1} exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03570: ThreadLimit may not exceed MaxThreadLimitValue.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03570: ThreadLimit may not exceed MaxThreadLimitValue.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03571: ServerLimit may not exceed MaxServerLimitValue.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03571: ServerLimit may not exceed MaxServerLimitValue.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03572: MaxClients exceeds range, raise ServerLimit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03572: MaxClients exceeds range, raise ServerLimit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03573: MaxClients exceeds range, raise ServerLimit or ThreadPerChild.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03573: MaxClients exceeds range, raise ServerLimit or ThreadPerChild.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03575: The value of ThreadLimit cannot be less than the value of ThreadsPerChild.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03575: The value of ThreadLimit cannot be less than the value of ThreadsPerChild.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03576: The value of ThreadsPerChild cannot be greater than the value of ThreadLimit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03576: The value of ThreadsPerChild cannot be greater than the value of ThreadLimit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03577: The value of ServerLimit cannot be less than the value of MaxClients.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03577: The value of ServerLimit cannot be less than the value of MaxClients.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03578: The value of ServerLimit * ThreadsPerChild cannot be less than the value of MaxClients.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03578: The value of ServerLimit * ThreadsPerChild cannot be less than the value of MaxClients.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03579: Virtual Host Already Exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03579: Virtual Host Already Exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03580: Not a proper Virtual Host Name

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03580: Not a proper Virtual Host Name

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03581: Error enabling module "{0}" : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03581: Error enabling module "{0}" : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03582: The specified module "{0}" is not installed. Module has to be installed before configuring it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03582: The specified module "{0}" is not installed. Module has to be installed before configuring it.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03583: Register child MBean api failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03583: Register child MBean api failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03584: Proxy Port MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03584: Proxy Port MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03585: Audit MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03585: Audit MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03586: Parsing error while loading MBeans

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03586: Parsing error while loading MBeans

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03587: Exception occurred while loading MBeans

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03587: Exception occurred while loading MBeans

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03588: Virtual Host creation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03588: Virtual Host creation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03589: Duplicate virtual host found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03589: Duplicate virtual host found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03590: Base Virtual host creation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03590: Base Virtual host creation failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03594: Unregister of configuration MBeans failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03594: Unregister of configuration MBeans failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03595: Unable to get VH objects from root OHS MBean

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03595: Unable to get VH objects from root OHS MBean

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03596: Load wallets failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03596: Load wallets failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03597: Removal of Virtual Host failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03597: Removal of Virtual Host failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03598: Removal of Listen failed while removing VH

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03598: Removal of Listen failed while removing VH

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03601: Load failed with IOException

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03601: Load failed with IOException

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03602: Module name can not be null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03602: Module name can not be null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03604: Unable to find Server Name, Setting it to default AdminServer

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03604: Unable to find Server Name, Setting it to default AdminServer

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03605: Virtual host MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03605: Virtual host MBean registration failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03606: The current MPM does not support directive {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03606: The current MPM does not support directive {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03607: Port {0} for {1} is already in use on machine "{2}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03607: Port {0} for {1} is already in use on machine "{2}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03608: No ports for {0} were available for auto-assignment on machine "{1}" in the range {2}-{3}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03608: No ports for {0} were available for auto-assignment on machine "{1}" in the range {2}-{3}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03609: Port {0} for {1} is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03609: Port {0} for {1} is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03610: Error disabling module "{0}" : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03610: Error disabling module "{0}" : {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03611: Instance "{0}" is in state "{1}" and cannot be deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03611: Instance "{0}" is in state "{1}" and cannot be deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03612: The port value, {0}, has already been used and cannot be configured for {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03612: The port value, {0}, has already been used and cannot be configured for {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03701: Error log configuration not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03701: Error log configuration not valid

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03702: Saving wallet is null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03702: Saving wallet is null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03703: P12 Wallet is null; Possibly because the wallet is absent/not configured.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03703: P12 Wallet is null; Possibly because the wallet is absent/not configured.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03704: CWallet is null, not able to load cwallet

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03704: CWallet is null, not able to load cwallet

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03705: Directive does not exist

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03705: Directive does not exist

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03707: WLHost not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03707: WLHost not configured; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03708: WLCluster not configured; Not allowed to call listWLCluster

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03708: WLCluster not configured; Not allowed to call listWLCluster

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03709: DynamicServerList is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03709: DynamicServerList is not configured ; Illegal Usage

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03710: SSLCARevocationPath is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03710: SSLCARevocationPath is not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03711: SSLCRLCheck or SSLCARevocationFile is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03711: SSLCRLCheck or SSLCARevocationFile is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03712: SSLWallet is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03712: SSLWallet is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03713: SSLVerifyClient is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03713: SSLVerifyClient is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03714: SSLCipherSuite is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03714: SSLCipherSuite is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03715: SSLProtocol is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03715: SSLProtocol is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03716: SSLEngine is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03716: SSLEngine is not configured properly

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03717: Value cannot start with '#'.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03717: Value cannot start with '#'.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03718: The file requested, "{0}", is not part of the current OHS configuration. Please enable the file first.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03718: The file requested, "{0}", is not part of the current OHS configuration. Please enable the file first.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03719: Cannot register virtual host :

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03719: Cannot register virtual host :

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03720: No virtual host name specified. Invalid virtual host name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03720: No virtual host name specified. Invalid virtual host name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03721: Default Virtual Host name must be a port number or * or an empty string.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03721: Default Virtual Host name must be a port number or * or an empty string.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03722: Virtual Host "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03722: Virtual Host "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03723: Syntax Error in Log configuration: operation failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03723: Syntax Error in Log configuration: operation failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03724: Could not parse configuration file template value "{0}" on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03724: Could not parse configuration file template value "{0}" on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03725: Key "{0}" is not a valid configuration file template value on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03725: Key "{0}" is not a valid configuration file template value on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03726: Configuration file template value "{0}" does not contain a valid port number on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03726: Configuration file template value "{0}" does not contain a valid port number on createInstance() invocation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03728: Instance name invalid. "{0}" is longer than 30 characters.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03728: Instance name invalid. "{0}" is longer than 30 characters.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03729: Instance name invalid. "{0}" does not start with a letter.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03729: Instance name invalid. "{0}" does not start with a letter.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03730: Instance name invalid. "{0}" contains an invalid character.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03730: Instance name invalid. "{0}" contains an invalid character.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03731: Instance name invalid :"{0}". The following reserved names (ignoring letter case) are not allowed as instance names : "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03731: Instance name invalid :"{0}". The following reserved names (ignoring letter case) are not allowed as instance names : "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03732: OHS instance already exists ("{0}").

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03732: OHS instance already exists ("{0}").

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03733: OHS instance does not exist ("{0}").

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03733: OHS instance does not exist ("{0}").

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03734: Invalid port number "{0}" is specified. Port number must be between 1 and 65535 inclusive.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03734: Invalid port number "{0}" is specified. Port number must be between 1 and 65535 inclusive.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03735: Invalid log level :"{0}". Valid log levels are : "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03735: Invalid log level :"{0}". Valid log levels are : "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03736: File {0} could not be read

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03736: File {0} could not be read

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03737: Property file {0} could not be loaded; using defaults

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03737: Property file {0} could not be loaded; using defaults

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03738: NodeManager is unreachable for the instance "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03738: NodeManager is unreachable for the instance "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03739: NodeManager is unreachable for the machine "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03739: NodeManager is unreachable for the machine "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03801: Load Operation failed in VH SSLResource

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03801: Load Operation failed in VH SSLResource

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03802: Load Operation finished in VH SSLResource for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03802: Load Operation finished in VH SSLResource for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03804: Load operation success for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03804: Load operation success for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03805: The specified module "{0}" is already enabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03805: The specified module "{0}" is already enabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03806: Unregistered all configuration MBeans for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03806: Unregistered all configuration MBeans for instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03807: Wildcard char, allow processing

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03807: Wildcard char, allow processing

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03808: Error log configuration mode is not apache

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03808: Error log configuration mode is not apache

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03809: Error log Mode is apache

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03809: Error log Mode is apache

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03810: Listen Directive not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03810: Listen Directive not configured

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03811: Listen Directive already exist for specified port

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03811: Listen Directive already exist for specified port

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03814: An error occured while setting the file contents for the config file "{0}". Make sure that the specified configuration file content is of valid format.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03814: An error occured while setting the file contents for the config file "{0}". Make sure that the specified configuration file content is of valid format.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03815: It is not permitted to edit "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03815: It is not permitted to edit "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03816: The specified configuration file "{0}" is not part of the configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03816: The specified configuration file "{0}" is not part of the configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03817: An error occurred setting the contents of config file "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03817: An error occurred setting the contents of config file "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03818: An error occurred updating the instance "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03818: An error occurred updating the instance "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03819: The specified module "{0}" is already disabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03819: The specified module "{0}" is already disabled.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03820: Directory "{0}" is missing from the Oracle HTTP Server installation. The instance cannot be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03820: Directory "{0}" is missing from the Oracle HTTP Server installation. The instance cannot be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03821: The ohs.product.home property is not set. The instance cannot be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03821: The ohs.product.home property is not set. The instance cannot be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03822: The fully qualified domain name for host "{0}" could not be resolved. ServerName will be set to "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03822: The fully qualified domain name for host "{0}" could not be resolved. ServerName will be set to "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03823: No parameter found on include

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03823: No parameter found on include

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03828: Can not find directive in new DirectiveLine

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03828: Can not find directive in new DirectiveLine

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03829: Failed to find < in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03829: Failed to find < in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03830: Failed to find space in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03830: Failed to find space in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03831: Failed to find > in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03831: Failed to find > in Container directive

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03832: IOException reading file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03832: IOException reading file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03833: Never found container terminator for

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03833: Never found container terminator for

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03834: Element to add after not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03834: Element to add after not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03835: Element to add before not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03835: Element to add before not found

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03836: Can't find element to remove

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03836: Can't find element to remove

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03837: Can't clear the container

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03837: Can't clear the container

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03838: Comment must be empty string or start with #.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-03838: Comment must be empty string or start with #.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04001: Error while starting the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04001: Error while starting the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04002: Error while stopping the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04002: Error while stopping the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04003: Graceful stop of server {0} failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04003: Graceful stop of server {0} failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04004: Error while restarting the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04004: Error while restarting the server {0}: server start/stop is already in progress

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04005: Check the instance log file for more information: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04005: Check the instance log file for more information: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04006: Error while restarting the server {0}: server is not currently running

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04006: Error while restarting the server {0}: server is not currently running

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04007: Failed to start the server {0} successfully: attempting to cleanup the process

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04007: Failed to start the server {0} successfully: attempting to cleanup the process

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04008: Failed to stop the server {0} gracefully: attempting to kill

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04008: Failed to stop the server {0} gracefully: attempting to kill

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04009: Failed to re-start the server {0} completely: attempting to cleanup the process

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04009: Failed to re-start the server {0} completely: attempting to cleanup the process

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04010: Server {0} is in an inconsistent state -- the process could not be stopped or killed. This issue must be manually resolved

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04010: Server {0} is in an inconsistent state -- the process could not be stopped or killed. This issue must be manually resolved

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04011: Property file {0} could not be loaded; using defaults

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04011: Property file {0} could not be loaded; using defaults

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04012: Invalid property {0} was configured in file {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04012: Invalid property {0} was configured in file {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04013: Property {0} has value {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04013: Property {0} has value {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04014: Property {0} was configured with invalid value {1} in file {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04014: Property {0} was configured with invalid value {1} in file {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04015: Invalid instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04015: Invalid instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04016: Failed to start the server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04016: Failed to start the server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04017: Failed to restart the server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04017: Failed to restart the server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04018: Starting server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04018: Starting server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04019: Restarting server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04019: Restarting server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04020: Stopping server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04020: Stopping server {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04021: Corrupted value {0} for property

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04021: Corrupted value {0} for property

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04022: File {0} could not be read

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04022: File {0} could not be read

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04023: Invalid property specified: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04023: Invalid property specified: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04024: Valid properties are {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04024: Valid properties are {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04025: Invalid value {0} for property {1} specified:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04025: Invalid value {0} for property {1} specified:

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04026: Valid values are {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04026: Valid values are {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04027: Valid values are between {0} and {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04027: Valid values are between {0} and {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04028: Unexpected validator type

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04028: Unexpected validator type

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04029: {0}: command timed out; the process has been terminated

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04029: {0}: command timed out; the process has been terminated

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04030: {0}: command stdout/stderr IO error

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04030: {0}: command stdout/stderr IO error

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04031: Check log file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04031: Check log file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04032: Invalid property environment variable name {0} configured in {1}: {2}. Property environment name syntax is {3}, where {4} is the optional append flag, {5} is the optional numeric order value, and {6} is the name of the environment variable

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04032: Invalid property environment variable name {0} configured in {1}: {2}. Property environment name syntax is {3}, where {4} is the optional append flag, {5} is the optional numeric order value, and {6} is the name of the environment variable

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04101: Instance {0} already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04101: Instance {0} already exists

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04102: InstanceDirectory {0} does not contain a valid OHS instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04102: InstanceDirectory {0} does not contain a valid OHS instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04103: Unable to delete the directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04103: Unable to delete the directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04104: Failed to create instance directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04104: Failed to create instance directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04106: Unable to delete the file: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04106: Unable to delete the file: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04107: No instance root: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04107: No instance root: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04108: Instance {0} is alive; cannot delete

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04108: Instance {0} is alive; cannot delete

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04109: Errors occured while commiting changes for the following instances: {0}. Check {1} for details

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04109: Errors occured while commiting changes for the following instances: {0}. Check {1} for details

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04110: ohs.product.home system property is not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04110: ohs.product.home system property is not set

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04111: Unable to find a valid OHS installation at {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04111: Unable to find a valid OHS installation at {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04112: Creating instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04112: Creating instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04113: Deleting instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04113: Deleting instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04114: Updating instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04114: Updating instance {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04115: Synchronization copy of {0} to {1} failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04115: Synchronization copy of {0} to {1} failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04116: Failed to make directory {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04116: Failed to make directory {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04117: Failed to create file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04117: Failed to create file {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04118: Failed to delete {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04118: Failed to delete {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04251: Failed to reach the OHS instance: {0} Make sure that instance is up and running

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04251: Failed to reach the OHS instance: {0} Make sure that instance is up and running

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04252: OHS instance failed to respond to the requested URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04252: OHS instance failed to respond to the requested URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04401: Unable to find template directory {0} within OHS installation at {1}. Make sure that {1} contains a valid OHS installation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04401: Unable to find template directory {0} within OHS installation at {1}. Make sure that {1} contains a valid OHS installation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04402: Unable to copy template directory {0} to directory {1} within new instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04402: Unable to copy template directory {0} to directory {1} within new instance

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

OHS-04501: Connect to a WebLogic server before using this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04501: Connect to a WebLogic server before using this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04502: Unexpected error: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04502: Unexpected error: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04503: createOHSInstance() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04503: createOHSInstance() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04504: deleteOHSInstance() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04504: deleteOHSInstance() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04505: Machine "{0}" does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04505: Machine "{0}" does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04506: Instance "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04506: Instance "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04507: Instance "{0}" is in state "{1}" and cannot be deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04507: Instance "{0}" is in state "{1}" and cannot be deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04508: Instance "{0}" does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04508: Instance "{0}" does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04511: Port {0} is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04511: Port {0} is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04512: Argument "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04512: Argument "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04513: The following required arguments are missing :{0} .

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04513: The following required arguments are missing :{0} .

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04514: Port {0} was specified more than once for the new instance.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04514: Port {0} was specified more than once for the new instance.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04515: The new instance uses a privileged port. Refer to the privileged port configuration information in the product documentation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04515: The new instance uses a privileged port. Refer to the privileged port configuration information in the product documentation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04516: Instance name "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04516: Instance name "{0}" is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04517: Instance names are limited to thirty characters, must begin with a letter, may contain letters, numbers, -, or _, and must not be one of the following reserved names(ignoring letter case): {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04517: Instance names are limited to thirty characters, must begin with a letter, may contain letters, numbers, -, or _, and must not be one of the following reserved names(ignoring letter case): {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04519: OHS instance "{0}" was successfully created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04519: OHS instance "{0}" was successfully created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04520: OHS instance "{0}" was successfully deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04520: OHS instance "{0}" was successfully deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04521: addOHSAdminProperties() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04521: addOHSAdminProperties() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04522: addOHSNMProperties() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04522: addOHSNMProperties() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04523: createOHSTestDomain() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04523: createOHSTestDomain() failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04524: Domain "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04524: Domain "{0}" already exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04525: Privileged ports are not supported with this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04525: Privileged ports are not supported with this command.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04526: NodeManager is unreachable. "{0}" might be in undeletable state because the NodeManager is unreachable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04526: NodeManager is unreachable. "{0}" might be in undeletable state because the NodeManager is unreachable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Configuration

OHS-04701: Failed to introspect OHS.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04701: Failed to introspect OHS.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04702: Failed to save HTTPD configuration file as a content resource.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04702: Failed to save HTTPD configuration file as a content resource.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04705: Failed to parse HTTPD configuration file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04705: Failed to parse HTTPD configuration file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04706: Failed to process OHS configuration directive - "{0} Directive"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04706: Failed to process OHS configuration directive - "{0} Directive"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04709: Failed to save OHS configuration file(s).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04709: Failed to save OHS configuration file(s).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04710: Failed to change the ownership of configuration file "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04710: Failed to change the ownership of configuration file "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04711: Failed to configure OHS instance to run on a privileged port

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04711: Failed to configure OHS instance to run on a privileged port

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04712: Invalid configuration. WebLogicHost and WebLogicPort must be adjacent to each other.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04712: Invalid configuration. WebLogicHost and WebLogicPort must be adjacent to each other.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04713: Listen directive has unresovable address: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04713: Listen directive has unresovable address: "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04714: OHS dehydration starting.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04714: OHS dehydration starting.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04715: HTTPD processing completed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04715: HTTPD processing completed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04716: OHS dehydration completed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04716: OHS dehydration completed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04717: Failed to create the content resource 'rehdyrate.properties'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04717: Failed to create the content resource 'rehdyrate.properties'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04801: OHS HTTPD Configuration parsed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04801: OHS HTTPD Configuration parsed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04802: OHS HTTPD configuration transformed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04802: OHS HTTPD configuration transformed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04803: OHS HTTPD configuration processed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04803: OHS HTTPD configuration processed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04804: OHS HTTPD configuration written.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04804: OHS HTTPD configuration written.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04851: Failed to read the content resource 'rehdyrate.properties'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04851: Failed to read the content resource 'rehdyrate.properties'

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04852: Failed to start OHS Instance - "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04852: Failed to start OHS Instance - "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04853: Failed to start Node Manager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04853: Failed to start Node Manager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04854: Failed to stop OHS Instance - "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

OHS-04854: Failed to stop OHS Instance - "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Ovab

41 ORABPEL-00006 to ORABPEL-20511

ORABPEL-00006: failure to load the JCE cipher "{0}"

Cause: The environment may not have been set correctly.

Action: JCE library files must be installed in the JRE installation as an extension. Copy the jar files from "{1}\install\java\jce1.2.2" directory to "(jdk_path)\jre\lib\ext" directory (where jdk_path is JDK installation directory).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00007: failure to decrypt cipher text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00008: failure to encrypt plain text with transformation "{0}"; exception reported is: {1}

Cause: This was an internal error. It may have been caused by an incorrect cipher state or an invalid padding size being specified.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00015: failure to create jar file {0}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00016: failure to execute javac compiler on file(s) "{0}"; exception reported is: {1}

Cause: The Sun tools.jar may not have been installed on the local machine or included in the class path.

Action: Verify that tools.jar is installed on this machine and is included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00017: failure to compile file(s) "{0}"; exception reported is: {1}

Cause: The generated Java class(es) had errors and/or all the required libraries to compile the class(es) were not available.

Action: Verify that the file named in the error message is valid Java file and that all required libraries are included in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00018: cannot find the Java source directory "{0}"

Cause: The specified Java source directory did not exist or it could not be written to.

Action: Create the source directory named in the error message and set the write permission accordingly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00019: cannot create the Java destination directory "{0}"

Cause: The parent directory permissions prevented the creation of this directory.

Action: Verify that the parent directory for the directory named in the error message is writable.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00020: failure to write the Javadoc argument file "{0}"; exception reported is: "{2}"

Cause: The Javadoc file named in the error message was not written to the directory "{1}".

Action: Verify that the directory "{1}" can be written to.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00021: failure to execute Javadoc with the argument file "{0}"

Cause: The Javadoc executable was not found in the system path or was not executed.

Action: Verify that Javadoc is installed on this machine in the <JDK>\bin directory and that this directory is included in the machine system path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00024: failure to schedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not schedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00025: failure to unschedule the "{0}" agent with the scheduler; exception reported is: {1}

Cause: The Quartz scheduler did not unschedule the job named in the error message. This is typically an internal scheduler error.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00026: error while attempting to execute the job "{0}" for agent "{1}"; exception reported is: {2}

Cause: This error was a wrapper for an internal exception thrown by the underlying scheduler job.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00201: cannot return system authentication token for caller "{0}"

Cause: This was an internal error. The agent "{0}" was not added to the allowed callers list for the system token.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00209: The domain identifier "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00210: domain ref "{0}" is not registered with the server.

Cause: All domain identifiers were kept in the domain table; this table may have been modified incorrectly.

Action: Restart the application server; if the domain directory is present, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00214: The OraBPEL server has not finished initializing yet; the initialization process may be complete in a few moments.

Cause: A request was sent to the server before it finished initializing.

Action: Resubmit the request. If this does not solve the problem, check the logs (with logging level set to debug mode) for error messages.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00215: error while attempting to instantiate the JDK adapter class "{0}" for run-time version "{1}"; exception reported is: {2}

Cause: The JDK adapter class named in the error message was not in the system class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00216: JDK adapter class "{0}" for run-time version "{1}" does not implement the IJDKAdapter interface

Cause: This was an internal error. All JDK adapters registered with the system must conform to the IJDKAdapter interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00217: JDK version "{0}" is not supported by the OraBPEL run-time; currently only JDK versions 1.4 and 1.5 are supported

Cause: A JDK adapter was not specified for the JVM version with which the container was started.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00219: cannot instantiate an instance for the class "{0}"

Cause: The class "{1}" was not granted sufficient permissions by the JVM to instantiate the class "{0}".

Action: Verify that the OraBPEL run-time class "{1}" has the necessary security permissions to access the class specified in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00220: class "{0}" (for the platform adapter for platform "{1}") does not implement the IPlatformAdaptor interface

Cause: This was an internal error. All platform adapters registered with the system must conform to the IPlatformAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00221: error while attempting to instantiate the class "{0}" as the adapter for platform "{1}"; exception reported is: {2}

Cause: The platform adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00222: class for platform adapter "{0}" (platform "{1}") cannot be found

Cause: The platform adapter class "{0}" was not in the system class path.

Action: Ensure that Oracle BPEL libraries are set correctly in the system class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00227: class "{0}" (for the database adapter for "{1}") does not implement the IDatabaseAdaptor interface

Cause: This was an internal error. All database adapters registered with the system must conform to the IDatabaseAdaptor interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00228: error while attempting to instantiate the class "{0}" as the database adapter, data source "{1}"; exception reported is: {3}

Cause: The database adapter class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00229: database adapter class name for data source "{0}" has not been specified

Cause: The database adapter class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00230: adapter resource file "{0}" cannot be found in the current class path

Cause: The resource file named in the error message contained all the JNDI mappings required for the BPEL process domain to initialize.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00231: error while attempting to instantiate the class "{0}" as the adapter manifest for "{1}", data source "{2}"; exception reported is: {3}

Cause: The adapter manifest class "{0}" was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00232: class "{0}" (for the adapter manifest for "{1}", data source "{2}") does not implement the IServerAdaptorManifest interface; all adapter manifests used by the OraBPEL server must implement this interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00233: adapter manifest class name for "{0}", data source "{1}" is not specified.

Cause: The adapter manifest class "{0}" was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files may have been modified incorrectly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00235: The component identifier "{0}" has not been registered with the server.

Cause: All component identifiers were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the identifier will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00236: The component reference "{0}" is not registered with the server.

Cause: All component references were kept in the "component" table; this table may have been modified incorrectly.

Action: Restart the application server; when the component is loaded, the reference will be automatically registered again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00237: failure to create the component reference for "{0}"

Cause: The maximum number of components ({1}) were reached.

Action: Contact Oracle Support Services. At the current time, the maximum number of components has been set to 32767.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-00238: exception while reading the component index from the data source; the exception reported is: {0}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00239: exception while writing the component index (application_name "{0}", composite_name"{1}", revision "{2}", label "{3}", component_name "{4}") to the data source; the exception reported is: {5}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-00240: exception occurs while removing the component index (dn "{0}", ref "{1}") from the data source; the exception reported is: {2}

Cause: There was a problem with connecting to the data source where the component index is stored.

Action: There are three things to verify. Verify that the machine hosting the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for the OraBPEL server has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01005: failure to compile the generated BPEL classes for BPEL process "{0}" of composite "{1}"

Cause: The class path setting is incorrect.

Action: Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01007: build directory "{0}" for the BPEL process "{1}" of composite "{2}" cannot be found or accessed

Cause: The compiler could not find or create the directory "{0}".

Action: Ensure that the parent directory of "{0}" is a valid directory and that it is not read-only.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01010: failure to generate the BPEL process file "{0}".

Cause: Could not generate named BPEL process file. The exception reported was "{1}".

Action: Ensure that the file "{0}" is a valid file to be generated.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-01027: trying to manipulate the nonexistent part "{1}" in a message of type "{0}"

Cause: An invalid request was made to manipulate the invalid part "{1}".

Action: Ensure that the client request is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01028: cannot find propertyAlias definition that associates the BPEL correlation "{0}" of correlationSet "{1}" to messageType "{2}"

Cause: A propertyAlias must be defined to associate the BPEL correlation to a correlationSet. The run time could not find it.

Action: Ensure that the mentioned propertyAlias is in one of the WSDL files that are referenced by the composite. Redeploy the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01029: cannot find property definition for "{0}" in any of the WSDL files

Cause: The BPEL correlation property needs to be defined. But the run time could not find it.

Action: Define the mentioned BPEL property in one of the WSDL files referenced by the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01030: cannot generate debug model file "{0}"

Cause: The named BPEL debug model file was not generated. The exception reported was: "{1}".

Action: Correct the error reported by the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-01032: specified process ID "{0}" is invalid

Cause: The specified process identifier did not follow the naming constraints.

Action: Valid process identifiers might start with a letter, a '$' or '_' character; process characters (other than the first character) include a letter, a digit, a '$', a '_' or '-' character. The max length permitted is 100. Ensure that the component name specified in the composite descriptor conforms to the above mentioned constraints.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02000: The class "{0}" for the block element "{1}" does not implement the ICubeBlock interface.

Cause: This was an internal error. All block elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02001: error while attempting to instantiate the class "{1}" for the block element "{0}"; exception reported is: {2}

Cause: This was an internal error. The block class "{0}" was not in the composite class path, or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02002: block element "{0}" missing its class name; this element cannot be created without its class name

Cause: This was an internal error. The block element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02003: A Cube element is missing its "ID" property. Every Cube element in the process domain is uniquely identified by its "ID" property.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02005: The parent block element "{0}" specified by node or block element "{1}" is not defined in the service class map. All nodes or blocks contained in the map must be bound to a valid parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02006: The node or block element "{0}" is missing a parent block identifier. All nodes or blocks contained in the service class map must be bound to a parent block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02007: Multiple method block elements are specified in the service class map. A valid map can only contain one method block element.

Cause: This was an internal error. The element was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02008: No block elements are specified in the service class map. All valid maps must contain at least one block element (the root block).

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02009: No node elements are specified in the service class map. All valid maps must contain at least one node element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02010: No method block element is specified for the service class map. All valid maps must contain one method block element.

Cause: This was an internal error. The block map was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02011: The class "{0}" for the node element "{1}" does not implement the ICubeNode interface.

Cause: This was an internal error. All node elements contained within the process domain must implement this interface.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02012: error while attempting to instantiate the class "{1}" for the node element "{0}"; the exception reported is: {2}

Cause: This was an internal error. The node class "{0}" was not in the composite class path or there was an incompatibility with the JDK used to the compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02013: The class "{0}" cannot be found in the current class path.

Cause: This was an internal error. The node element class "{0}" was not in the composite class path.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02014: The node element "{0}" is missing its class name; this element cannot be created without its class name.

Cause: This was an internal error. The node class name should be generated by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02015: The BPEL process "{0}" (revision "{1}") has been compiled with an older version of SCAC; current BPEL process domain cannot execute this process.

Cause: An attempt to deploy a process that was compiled with an older version of SCAC failed.

Action: Recompile the BPEL process using the SCAC tool bundled with the current process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02016: The process "{0}" is not initializing because of the error: "{1}".

Cause: This error contained the exceptions thrown by the underlying process loading module.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02017: cannot compress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02018: cannot uncompress the data stream with GZIP algorithm; exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying compression layer.

Action: Please enable DEBUG log level for logger oracle.soa.bpel.engine.data. Please check for message "Byte value passed is:" and exception stack trace in soa server diagnostic log and provide this information to Oracle Support
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02019: cannot compute the md5 checksum; exception reported is: {0}

Cause: This error contained exceptions thrown by the underlying digest layer.

Action: Check for possible cause in the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02020: failure to serialize the audit trail for instance "{0}" to its binary representation; exception reported is: {1}

Cause: This was an internal error. This error contained the exceptions thrown by the underlying XML marshalling module.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02022: The value "{0}" for the tag "{1}" in the XML serialized text for the audit trail for instance "{2}" is not a numeric value.

Cause: The tag "{1}" did not contain a numeric value.

Action: Ensure that the value for tag "{1}" conforms to the expected numeric format.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02023: failure to activate the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02024: failure to invoke the method "until" on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02025: failure of the block "{0}" to handle a business exception for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02026: failure to invoke the canActivate method on the block "{0}" for the instance "{1}"; exception reported is: {2}

Cause: This error contained the exceptions thrown by the underlying routing system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02027: failure to deserialize the instance "{0}" from binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02028: failure to serialize the instance "{0}" to binary format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02029: The process domain cannot create the bean "{0}"; this bean is responsible for generating a unique key for a new instance. The exception reported is: "{1}".

Cause: The SOA application or class path was not configured correctly.

Action: Verify that the instance key generator bean has been properly deployed to the server and can be properly mounted from a java class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02030: failure to marshall the instance "{0}" to XML format; exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization system.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02031: The instance "{0}" is created from the domain "{1}"; the current domain is "{2}". A process can be loaded only from the domain from which it was created.

Cause: The instance was not accessed because it was created in a different domain.

Action: If this instance is being accessed from the API, try looking up the instance "{0}" from the "{1}" domain (change the domain ID parameter to the Locator initializer).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02032: The instance "{0}" is created with process guid "{1}"; the current guid for the process "{2}" (revision "{3}") is "{4}".

Cause: Whenever a process is deployed on top of an existing process with the same process ID and revision tag, all instances created from the previous process are marked as stale.

Action: If this instance is being accessed from the console, the browser may be referring to an out-of-date page; click the Instances tab to get the current list of active instances.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02033: failure to construct a valid instance key from the string "{0}"; exception reported is: {2}

Cause: The instance did not consist of a single integer value.

Action: If the instance key has not been constructed by the process domain, ensure that the key format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02037: exception while trying to create a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02038: The process domain is unable to look up the context object using the bind name "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the JNDI identifier is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02040: exception while trying to destroy a context object; the exception reported is: {0}

Cause: This error contained the exceptions thrown by the underlying JNDI environment.

Action: Verify that the directory service on the application server has been configured correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02041: The action "{0}" cannot be performed on the instance "{1}" because of its current state ("{2}").

Cause: The current instance state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on an instance when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02042: The action "{0}" cannot be performed on the work item "{1}" because of its current state ("{2}").

Cause: The current work item state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a work item when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02043: The action "{0}" cannot be performed on the scope "{1}" because of its current state ("{2}").

Cause: The current scope state did not allow the requested action to be performed.

Action: Consult the product documentation for a list of all the permissible actions that can be performed on a scope when it is in the "{2}" state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02044: The process domain is failing to write the audit trail for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying persistence framework.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02046: The process domain is failing to write the debug trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02047: The process domain is failing to write the instance trace for instance "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying serialization layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02048: The process domain is unable to handle the work item "{0}"; the exception reported is: {1}

Cause: This error contained the exceptions thrown by the underlying process execution layer.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02050: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is cancelled. The return value for this method cannot be determined in this case.

Cause: The instance "{1}" was cancelled or aborted.

Action: Check the audit trail for instance "{1}" for more information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02051: The invocation for method "{0}" on the instance "{1}", process "{2}" (revision "{3}") is not complete. The return value for this method cannot be fetched until the method has completed.

Cause: The instance "{1}" was not complete yet.

Action: Resubmit this request after several minutes. Note that the method may contain some asynchronous interactions that could take an indeterminate amount of time to complete.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02052: The BPEL domain "{0}" is missing.

Cause: The BPEL domain "{0}" may not have initialized properly.

Action: Check the log for the underlying exception trace after setting the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02053: The BPEL domain "{0}" is not finished initializing yet.

Cause: The domain initialization procedure was not finished yet.

Action: Resubmit the request in few minutes. The initialization progress can be monitored in the server log; set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02054: The BPEL domain "{0}" is currently uninitializing; the domain may not be accessed.

Cause: The domain was uninitializing.

Action: Restart the application server. If the domain uninitialized due to an exception, check the server log for the underlying exception trace (be sure to set the logging level to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02055: failure to handle a fault thrown from a scope, by any blocks in the scope chain

Cause: This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.

Action: A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02057: The block element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02058: The node element "{0}" is not defined in the service class map.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02059: The process domain is unable to fetch the work item "{0}" from the memory repository.

Cause: This was an internal error. The work item was not correctly registered from the previous transaction.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02060: failure to activate the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02061: failure to finalize the node "{0}" for the work item "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02062: failure to invoke the canActivate method on the node "{0}" for the instance "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying routing subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02063: failure to deserialize the delivery callback messages for conversation "{0}", message "{1}" from the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02064: failure to serialize the delivery callback messages for conversation "{0}", message "{1}" to the binary format; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02065: failure to serialize the delivery properties for conversation "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02066: failure to deserialize the delivery properties for conversation "{0}" from the binary format; the exception reported is: {1}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02067: failure to marshall the delivery callback messages for conversation "{0}", message "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying delivery subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the conversation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02068: Failure to call method "{0}" of the delivery persistence service with parameter "{1}". This operation is not supported.

Cause: This was an internal error. Delivery persistence service does not support advanced persistence features such as lazy loading. The persistence manager should not have used those related operations.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02069: The delivery service fails to load the message content from the data store; the exception reported is: {0}

Cause: This was an internal error. Either the load() method was not working properly if the object type was imported into the process, or the delivery message content might have been edited manually in the data store.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02070: The delivery service fails to store the object "{0}" of type "{1}" to the data source. The exception reported is: {2}

Cause: This was an internal error. The save() method was not working properly if the object type was imported into the process.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02071: failure to copy the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02072: failure to release the moniker "{0}"; the exception reported is: {1}

Cause: An attempt was made to remove the last reference to a moniker before the object referred to by the moniker had been loaded.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02073: failure to delete the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02074: The target element with ID "{0}" cannot be located in the current XML document. The node "{1}" has a reference link to this element.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02075: The element "{0}" does not have an "xsi:type" attribute specifying the schema type of the underlying Java object. An XML fragment cannot be properly unmarshalled to its Java representation without this information.

Cause: The document was corrupt; it might have been edited manually.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02076: failure to deserialize an object from its moniker format; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the deserialization failure.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02077: Assertion failure: object "{0}" has negative reference count "{1}".

Cause: This was an internal error. An object had a reference count less than zero because it fell out of scope and had its reference count decremented.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02078: failure to marshall the object "{0}" of type "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02079: failure to prepare the object "{0}" of type "{1}" for marshalling; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02080: failure to prepare the object "{0}" of type "{1}" for saving; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02081: failure to read an object''s moniker from the deserializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02082: failure to save the object "{0}" of type "{1}"; the exception reported is: {2}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02083: failure to unmarshall the object "{0}" of type "{1}" from XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02084: failure to write an object''s moniker into the serializer stream; the exception reported is: {0}

Cause: An exception was thrown by the underlying persistence subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02085: The metadata for object "{0}" is not registered with the persistence service.

Cause: This was an internal error. Every Java object type in the scope must be registered.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02086: The metadata for object "{0}" does not contain an embedded moniker.

Cause: This was an internal error. One or more of the linked variants in the scope did not contain an embedded moniker that contained the actual bytes defining the object.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the object.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02087: The node "{0}" is missing its reference identifier.

Cause: This was an internal error. Any element with an "href" attribute did not contain a non-empty reference ID that could be resolved to another element in the document.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02088: An instance's root scope cannot be routed.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02089: failure to construct a valid scope activation key from the string "{0}".

Cause: This was an internal error. The expected format was: "param1-param2", where the two parameters were: instance ID (integer) and scope ID (string) respectively.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02090: failure to unmarshall the metadata for the scope tree of instance "{0}"; the exception reported is: {1}

Cause: This was an internal error. A variant's metadata did not contain "guid", "class name" and "ref-count" attributes; or the "ref-count" attribute was not an integral value while it should be.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02091: failure to release an instance's root scope from the scope tree.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02092: failure to unmarshall a scope for the instance "{0}" from an XML document; the exception reported is: {1}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02093: The tag "{0}" is missing from the serialized XML text for the scope data for the instance "{1}".

Cause: This was an internal error. The XML document for this instance did not contain a value for the tag named in the error message.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02094: The scope "{0}" is not defined for cikey {1}.

Cause: This was an internal error. The scope was either closed or released, and it was not reachable.

Action: Please enable debug log level for logger oracle.soa.bpel.engine.delivery and provide soa diagnostics logs
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02095: The scope associated with the block element "{0}" is not defined in the current instance.

Cause: This was an internal error. The scope metadata was corrupt.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02096: The value "{0}" for the tag "{1}" in the serialized XML text for instance "{2}" is not a parseable integral value.

Cause: This was an internal error. The value for tag named in the error message did not conform to the expected format.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02097: cannot read the XML model file for process "{0}" (revision "{1}"); the exception reported is: {2}

Cause: An exception was thrown by the underlying operating system.

Action: Verify that the BPEL archive for the process named in the error message (for the cited revision) has been deployed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02100: cannot find the content file "{0}" for process "{1}" (revision "{2}").

Cause: The content file named in the error message might not have been deployed with the process named in the error message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02101: cannot read the content file "{0}" for process "{1}" (revision "{2}"); the exception reported is: {3}

Cause: The content file named in the error message might not have been deployed with the process named in the erorr message.

Action: Verify that the path named in the error message is correct, and that it refers to a file that has been included as a part of the deployment archive.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02102: Method "{0}" is missing.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02103: The map for node element "{0}" is not defined in the process class.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02104: New instances cannot be created when the process "{0}" is not active; existing instances are permitted to complete as usual.

Cause: The process named in the error message was not active and therefore could not create new instances.

Action: The process life cycle can be changed to active through the EM console.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02106: The process "{0}" has not been turned on. No operations can be performed on the process or any instance belonging to the process if the process is turned off.

Cause: The process named in the error message was not turned on; therefore it did not process any requests.

Action: Consult the administrator if this process has not been turned on.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02107: The process domain is unable to fetch the scope activation message with key "{0}" from the data source.

Cause: The scope activation message with the key named in the error message was not found in the data source.

Action: This row may have been manually removed from the data source; in which case the instance should be aborted.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02108: cannot create a copy of the scope "{0}"

Cause: This was an internal error. Scopes are not cloneable.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02109: The process domain is unable to deserialize the scope data for instance "{0}" from its binary representation; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02110: failure to marshall the scope data for instance "{0}" into XML; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02111: failure to serialize the scope data for instance "{0}" into a binary byte stream; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02112: The absolute scope ID "{0}" does not conform to the expected format for a scope identifier.

Cause: This was an internal error. The expected scope ID format is (block id + relative scope id).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02113: failure to fetch the return or header value from the root scope.

Cause: This was an internal error. Only top-level scopes can contain return or header values.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02114: The requested variant "{0}" is not a primitive variant type. Reference variants cannot be cast to a primitive type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a reference variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02115: The requested variant "{0}" is not a reference variant type. Primitive variants cannot be cast to a reference type.

Cause: This was an internal error. The code accessing the variant named in the error message was assuming that that variant was a primitive variant.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02116: The variant object associated with key "{0}" in the scope tree is neither a primitive nor a reference variant.

Cause: This was an internal error. The type of the declared variant "{0}" in the scope tree is not contained in the list of supported types (serializable and deserializable), including primitive (all Java primitive types) and reference (java.lang.String, java.util.Date, BPEL documents, EJB entity beans and one-dimensional arrays of any primitive or reference type).

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02117: A variable with key "{0}" is already declared in the current scope.

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02118: The variable "{0}" is not declared in the current scope. All variables must be declared in the scope before being accessed. Component DN is "{1}" and corresponding Instance Id is {2}

Cause: This was an internal error. The flow was not generated correctly by the BPEL compiler.

Action: Contact Oracle Support Services. Please provide component definition of "{1}" and audit trail of instance id {2} using enterprise manager console.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02121: failure to marshall the object "{0}" of class "{1}" to XML; the exception reported is: {2}

Cause: An exception was thrown by the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the marshalling failure.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02122: The type class "{0}" is missing a "{1}" tag.

Cause: The XML fragment for this type was missing a required tag; the XML document might have been edited manually.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02123: The value "{0}" of the tag "{1}" in the serialized XML text for the type class "{2}" is not a parseable integral value.

Cause: The value for the tag named in the error message did not conform to the expected format.

Action: Set the logging level to debug mode. Check the log for the any exception related to the type class.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02124: failure to deserialize the work item "{0}" from the binary format; the exception reported is: {1}

Cause: This error contained the exceptions thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02125: failure to serialize the work item "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02126: failure to deserialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02127: failure to serialize the work items for instance "{0}" to the binary format; the exception reported is: {1}

Cause: An exception was thrown from the underlying serialization subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02128: failure to marshall the work item "{0}" to the XML format; the exception reported is: {1}

Cause: An exception was thrown from the underlying marshalling subsystem.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02129: cannot construct a valid work item key from the string "{0}"

Cause: The string was of wrong format to construct a valid work item key. The expected key format is: "param1-param2-param3-param4", where the parameters are: instance ID (integer), node ID (string), scope ID (string) and count ID (integer) respectively.

Action: If the work item key string has not been constructed by the process domain, ensure that the key format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02130: The tag "{0}" is missing from the serialized XML text for work item "{1}".

Cause: The XML document for this instance was missing a value for the tag named in the error message.

Action: Set the logging level to debug mode. Check the log for the any exception related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02131: The activity "{0}" is throwing a null exception.

Cause: This was an internal error. Exceptions thrown from the activity cannot be null.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02132: The value "{0}" for the tag "{1}" in the serialized XML text for work item "{2}" is not a parseable integral value.

Cause: The value for tag "{1}" was not an integer.

Action: If the work item XML has not been constructed by the process domain, ensure that the XML format is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02133: error while attempting to expire the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02134: error while attempting to extend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02135: error while attempting to execute the manage method on the work manager for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02136: error while attempting to resume the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02137: error while attempting to suspend the work item "{0}" (located at node "{1}"); the exception reported is: "{2}"

Cause: An exception was thrown from the underlying process execution subsystem.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the work item.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02138: The method invocation "{0}" is returning an invalid number of callback arguments.

Cause: This was an internal error. More than one return value was returned. Currently, a maximum of one return value is permitted from a method invocation; the actual number of values returned for this invocation was "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02139: The method invocation "{0}" is throwing an invalid exception object.

Cause: This was an internal error. The exception object did not extend the Throwable class. The object thrown was of class "{1}".

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02140: failure to invoke the method "{0}" on the performer "{1}"; the exception reported is: "{2}"

Cause: An exception was thrown while performing a callback to an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the performer.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02141: error while attempting to execute the cancelPerform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while canceling an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02142: error while attempting to execute the perform method on the work performer for node "{0}"; the exception reported is: "{1}"

Cause: An exception was thrown while executing an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the node.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02143: error while attempting to throw the exception "{0}" from the activity "{1}"; the exception reported is: "{2}"

Cause: An exception is thrown while throwing an exception from an activity.

Action: Set the logging level to debug mode. Check the log for the underlying exception stack trace related to the activity.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02149: The instance identifier "{0}" is missing its domain ID; this ID specifies the BPEL domain from which the instance is generated.

Cause: This was an internal error. The instance domain ID was not set upon creation and rehydration.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02150: The process domain is unable to fetch the activity "{0}" from the data source.

Cause: The activity key "{0}" did not refer to a valid activity, or the activity was removed from the data source.

Action: Check the work_item database table with the activity key; if the referred row cannot be found, check the audit trail for the instance.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02151: More than one activity from domain "{1}" is returned when querying with the key "{0}".

Cause: Multiple activities were bound to the custom key "{0}". Only one activity should be returned per key.

Action: If the key is a user-specified custom key, ensure that the key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02152: The process domain is unable to fetch the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the cube_instance database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key. You could run select count(*) from cube_instance where cikey = {0}; on soainfra schema; If this query does not return any result, cube instance was not saved due to some error, most likely because of rollback of transaction. Please check soa server logs for any exception/error prior to this error. If query returns one row, the error could be some temporary error or race condition which can only be analyzed by Oracle Support.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02154: Multiple instances are returned when querying with the key "{0}", while only one instance is expected.

Cause: Multiple instances of a business process were created with the key "{0}". Each instance should be uniquely identified by a key.

Action: If the key is a user-specified custom key, ensure that the key is unique.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02155: The process domain is unable to fetch the bytes for the business document "{0}" from the data source.

Cause: The document key "{0}" did not refer to a valid document, or the document was removed from the data source.

Action: Check the xml_document database table with the document key; if the referred row cannot be found, check the server logs for traces related to this document key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02156: The process domain is unable to fetch the scope context data for the instance with key "{0}" from the data source.

Cause: The instance key "{0}" did not refer to a valid instance, or the instance was removed from the data source.

Action: Check the cube_scope database table with the instance key; if the referred row cannot be found, check the server logs for traces related to this instance key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02157: failure to read the audit trail for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while writing the audit trail bytes to the in-memory buffer after those bytes were read from the data store.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this in-memory buffer writing problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02158: failure to create the scope deserializer object for instance "{0}"; the exception reported is: {1}

Cause: An exception was thrown while creating a deserializer from the scope bytes.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace related to this deserializer creation problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02159: The process domain is unable to fetch the invocation content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid invocation message, or the invocation message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the invoke_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02160: The process domain is unable to fetch the callback content for the message "{0}" from the data source.

Cause: The message key "{0}" did not refer to a valid callback message, or the callback message was removed from the data source (this might have been the case if the BPEL global transaction was modified by an external source).

Action: Check the dlv_message database table with the message key; if the referred row cannot be found, check the server logs for traces related to this message key.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02161: The process domain is unable to fetch the audit detail bytes for the instance "{0}", detail ID "{1}" from the data store.

Cause: The instance identifier "{0}" or detail identifier "{1}", or both, did not refer to a valid entry in the audit_details table; this row might have been manually removed from the table.

Action: Check the audit_details database table with the identifiers named in the error message; if the referred row cannot be found, check the server logs for traces related to these identifiers.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02162: The instance index "{0}" is not within the valid range.

Cause: The index "{0}" for instance "{1}" was out of range.

Action: Change the index value in the xpath function or the facade API call to conform to the valid index range. Try a value between 1 and {2} (inclusive).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02163: cannot access scope "{0}"; scope is already released

Cause: This was an internal error. An attempt was made to access a scope that has already been released.

Action: Contact Oracle Support Services. Provide the error message, the composite source, and the exception stack trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-02164: An unknown cache policy "{0}" is specified for property "{1}".

Cause: The cache policy "{0}" was not recognized. The list of valid cache policies is { lru, auto, soft-filo, soft-lru, hybrid }.

Action: Change the cache policy configuration property to one of the recognized values. The valid cache policies are lru, auto, soft-filo, soft-lru, and hybrid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02165: cannot initialize connection pool for connection factory "{0}"; the reason is {1}

Cause: An exception was thrown while initializing the JMS connection pool.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02166: failure to finalize the compensation node "{0}" for the second time; the exception reported is: {1}

Cause: An exception was thrown while attempting to execute a compensation activity.

Action: Set the logging level to debug mode, check the log for the underlying exception stack trace.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02167: The process ("{1}", revision "{2}") for instance "{0}" is not loaded by the domain; the instance is marked as stale.

Cause: The archive for process "{1}" of revision "{2}" might have been deleted from the domain manually. In this case, the domain would not have been able to mark all instances that belonged to the process as being stale.

Action: Check if the process has been manually deleted from the domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02168: A problem occurs while reading the sensor file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor file named in the error message.

Action: Ensure that the file exists. If it has been manually deleted, then redeploy the process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02169: A problem occurs while reading the sensor action file "{0}"; the exception reported is: {1}

Cause: An exception was thrown while trying to access the sensor action file named in the error message.

Action: Ensure that the file exists. If the file has been manually deleted, then redeploy the process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02171: A problem occurs while updating the label status "{0}" in instance "{1}".

Cause: This label was not detected during process compilation.

Action: Redeploy the process and try again. If the redeployment step does not work, then contact Oracle Support Services. Provide the error message, the composite source, and the exception trace in the server log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02177: failure to create the data source "{0}"; the exception reported is: {1}

Cause: An exception was thrown while attempting to create a data source.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this data source creation problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02178: the BPEL process "{0}" with revision "{1}" is not loaded.

Cause: The process was not initialized properly, or the process was disabled.

Action: Set the logging level to debug mode, check the log for the underlying exception trace related to this process loading problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02180: The current JTA transaction is aborting due to a user rollback fault being thrown.

Cause: This exception was caused by a bpelx:rollback fault being thrown or a ROLLBACK_ONLY FabricInvocationException being thrown. BPEL engine is directed to roll back the current JTA transaction.

Action: There is no action recommended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02181: The current JTA transaction is marked as rollback-only when performing the activity "{0}".

Cause: The reason was {1}.

Action: Check on the activity which invokes a subprocess or downstream process that results in the JTA transaction being marked as rollback-only.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02182: catching unhandled fault "{0}" when processing instance "{1}" for process "{2}"

Cause: The exception was {3}.

Action: Check the error log file and the audit trail for instance "{1}" for more information. Try to use BPEL fault handlers to catch the faults in the BPEL process "{2}". If this is a system exception, please report this to the system administrator.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02183: bpel engine can not execute activities without an active transaction. please debug the invoked subsystem on why the tranasction is not in active status. the bpel instance id is "{0}".

Cause: The reason was {1}.

Action: Consult the system administrator regarding this error.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02184: The process domain was unable to serialize the activity guide milestone state data for instance "{0}" into a binary byte stream. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02185: The process domain was unable to deserialize the activity guide milestone state data for instance "{0}" from its binary byte representation. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown from the underlying serialization sub-system.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02186: The process domain was unable to fetch the activity guide instance with key "{0}" from the datasource.

Cause: The instance key "{0}" does not refer to a valid activity guide instance, or the instance has been removed from the datasource (this may be case if the BPEL global transaction has been modified by an external source).

Action: Check the "ag_instance" database table; if the row cannot be found, check the server logs.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02187: Failed to load activity guide instance with key "{0}" from the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while loading activity guide instance from the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02188: Failed to insert activity guide instance with key "{0}" to the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while inserting activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02189: Failed to update activity guide instance with key "{0}" in the datasource. The exception reported is: {1}

Cause: This error is a wrapper for exceptions thrown while updating activity guide instance to the datasource.

Action: Please check the log for the underlying exception trace. Be sure to set the logging level to debug mode.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02190: Failed to evaluate expression "{0}" in field "{1}" in activity guide instance with key "{2}". The exception reported is: "{3}"

Cause: The expression may not have been constructed correctly.

Action: Make sure that the expression is constructed correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02191: The activity guide definition at "{0}" could not be read.

Cause: The activity guide definition either is missing or invalid.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02192: The activity guide definition at "{0}" does not conform to the activity guide definition XML schema definition. The errors are "{1}"

Cause: The activity guide definition does not conform to the activity guide definition XML schema.

Action: Make sure that the activity guide definition conforms to the activity guide definition XML schema definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02193: The activity guide definition at "{0}" could not be validated against the activity guide definition XML schema definition.

Cause: The activity guide definition is missing.

Action: Make sure that the activity guide definition is available at the specified URL and that it is a valid XML document.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02194: The milestone instance with name "{0}" cannot be found in activity guide instance with ciKey "{1}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02195: The "{0}" operation on milestone "{1}" with status "{2}" in activity guide instance "{3}" is invalid. This operation can only be performed on milestones with status "{4}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02196: The "{0}" operation on activity guide instance "{1}" with status "{2}" is invalid. This operation can only be performed on activity guide instances with status "{3}".

Cause: This is an internal error. This may have been caused by some logical errors in the program.

Action: Please contact Oracle support. Be sure to provide the error message, the composite source and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02197: The "{0}" operation on activity guide instance "{1}" for milestone "{2}" is invalid.

Cause: The milestone's expiration date is not set or milestone is configured to continue post expiration

Action: Please check configuration settings for the milestone "{2}") in BPEL designer.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02198: The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new JTA transaction upon catching this fault.

Cause: This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.

Action: There is no action recommended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02199: The transaction became inactive when executing activity "{0}" for instance "{1}", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "{2}".

Cause: The reason was {3}.

Action: Consult the system administrator regarding this error.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02200: Master conversation ID is not available in context when executing work item "{0}" in component "{1}".

Cause: Master conversation ID was not supplied by the master process when initiating the call to the detail process.

Action: Make sure the master process's invoke activity to have bpelx:invokeAsDetail and bpelx:detailLabel attributes properly supplied.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02201: The process "{0}" has been suspended. No operations can be performed on the process or any instance belonging to the process if the process is suspended.

Cause: The process is suspended; therefore it did not process any requests.

Action: Consult the administrator if this process has been suspended.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02202: The process domain is unable to create Workitem for the activity "{0}"

Cause: Refer to cause

Action: Refer to cause for an action
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02203: The sub-process named "{0}" cannot be resolved. The sub-process is referred to by the process "{1}"

Cause: The previously resolved sub-process was undeployed while this process was dehydrated.

Action: Consult the system administrator regarding this error. The sub-process needs to be re-deployed.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02205: The sub-process named "{0}" cannot be resolved. The sub-process is referred to by the process "{1}".

Cause: The sub-process is not deployed, or the specified version of the sub-process in not deployed.

Action: Consult the system administrator regarding this error. The sub-process needs to be deployed, or the sub-process caller revised to use a different deployed sub-process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02206: Model.xml file not found for component "{0}"

Cause: Model.xml file was not generated for the component

Action: If component is BPEL 2.0, Model.xml file is not needed and thus does not get generated and this error is expected
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-02207: Transaction associated with bpel.config.transaction=notSupported setting.

Cause: Transaction was associated with business flow that was executing with bpel.config.transaction=notSupported configuration setting.

Action: Please enable application server transaction logs and BPEL engine logs and provide logs to Oracle Support for further analysis.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03001: The process domain is unable to determine the database type. The version table contains the vendor type for the current data source. The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information was stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03002: The server is unable to look up the database schema version.The exception reported is: {0}

Cause: There was a problem with connecting to the data source where the version information is stored.

Action: Check all of the following to determine the location of the problem with connecting to the data source. Verify that the machine that hosts the data source is physically connected to the network. Verify that the connection pool properties as defined in the application server startup properties are valid. Verify that the database schema for OraBPEL has been installed in the data source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03003: The database schema version {0} from the database does not match the version {1} expected by the server.

Cause: The database schema for the SOA installation was not properly installed, or the installation was using a database schema installed for a prior release.

Action: The database schema currently in place has probably been configured for a previous release. Reinstall the database schema and start the server again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03004: The database table "version" does not contain a data source vendor type

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the process domain again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03005: The database table "version" does not contain a version guid.

Cause: The database schema may have been modified by hand.

Action: Reinstall the database schema and start the server again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03010: error while trying to instantiate the class {0} as the adapter manifest for {1}, data source {2}, the exception reported is: {3}

Cause: The adapter manifest class named in the error message was not in the system class path, or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03011: The class {0} (for the adapter manifest for {1}, data source {2}) does not implement the IServerAdaptorManifest interface

Cause: This was an internal error. All adapter manifests registered with the system must conform to the IServerAdaptorManifest interface, and this one does not.

Action: Contact Oracle Support Services. Be sure to provide the error message and the exception trace in the log files (with loggers set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03012: The adapter manifest class name for {0}, data source {1} is not specified

Cause: The adapter manifest class named in the error message was not in the system class path.

Action: Ensure that the Oracle BPEL libraries are set correctly in the system class path. If the libraries are configured correctly, the adapter configuration files might have been modified.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03013: cannot instantiate an instance for the class {0}

Cause: This was an internal error. Java class {0} that must be dehydrated or rehydrated within the OraBPEL server must implement the java.io.Serializable interface. And it must implement a default constructor.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03410: error while trying to instantiate the agent class {0}; The exception reported was: {1}

Cause: The agent class might have relied on a class that was not found in the class path, or it might have relied on a JDK feature that was not compatible with the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03411: invalid agent class

Cause: This was an internal error. The agent class {0} did not implement the IAgent interface. All agents managed by the system must implement this interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03800: The process domain is not able to resolve which correlation set definition to apply to the received callback message for the operation {0}.

Cause: Correlation set definitions were registered with the process domain using operation name and process ID. The callback message was most likely missing the process ID.

Action: If the callback client is external, check that the callback URL contains the process identifier. If the client is another BPEL process, check that the correlation set is defined correctly in the receiving BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03801: The received callback message is missing the operation name parameter. The process domain cannot resolve which correlation set definition to apply to the message without this parameter.

Cause: The callback message did not pass the operation name in the SOAP action property.

Action: If the callback client is external, check that the operation name is being passed in the message correctly. If the client is another BPEL process, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03802: The correlation set definition for operation {0}, process {1}, is not registered with the server.

Cause: The correlation set was not defined in the process.

Action: Redeploy the process to the container.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03803: The process domain cannot look up the engine bean; this bean is responsible for processing the callback of a received message. The exception reported is: {0}

Cause: This was an internal error. The SOA installation was not configured properly.

Action: Check that the engine bean has been properly deployed to the server and can be properly mounted from a Java class.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03804: The synchronous polling thread is timing out waiting for a result from instance "{0}".

Cause: The callee was a durable synchronous process that had not reached its reply activity within the allotted timeout period.

Action: There may be a problem completing instance named in the error message. Check the process console for more information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03805: The process domain is unable to find the protocol handler for the conversation type "{0}".

Cause: This was an internal error. Only the SOAP protocol handler is active by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-03806: The process domain is unable to process the callback for received message "{0}", for conversation "{1}", and the subscriber "{2}". The exception reported is: {3}

Cause: This error contained exceptions thrown from the underlying callback handler layer.

Action: Check the exception trace in the log (with the logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03810: A similar receive activity is being declared in the same process.

Cause: Another receive activity or equivalent (currently, onMessage branch in a pick activity) has already been enabled with the partnerLink "{0}", operation name "{1}" and correlation set "{2}" (or conversation ID). Appendix A - Standard Faults in the BPEL 1.1 specification specifies a fault should be thrown under these conditions.

Action: Redeploy the process after removing the conflicting receive activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03811: No correlation sets are defined for operation "{0}" (process "{1}").

Cause: There were no correlation sets defined for the operation and process named in the error message. All receive operations that do not use WS-Addressing to correlate messages must define at least one correlation set.

Action: Check the BPEL source to ensure that at least one correlationSet is defined for the operation named in the error message.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03812: cannot find the property alias "{0}", message type "{1}"

Cause: The property alias named in the error message was not defined in the BPEL/WSDL source.

Action: Check the BPEL/WSDL source to ensure that the property alias named in the error message has been defined.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03813: failure to evaluate the correlationAlias query "{0}" on the element "{1}".

Cause: The property alias was not defined correctly in the BPEL/WSDL source, or the payload is not as expected.

Action: Check the BPEL/WSDL source to ensure that property alias is defined correctly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03850: Not able to acquire lock on entity, Db query for update NoWait(QoS is configured DirectWrite), or object lock in Coherence cache(QoS is configured CacheEnabled)

Cause: More than one thread is contending for this entity

Action: rescheduled for auto recovery
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03851: Not able to acquire lock on entity, Db query for update NoWait(QoS is configured DirectWrite), or object lock in Coherence cache(QoS is configured CacheEnabled)

Cause: More than one thread is contending for this entity

Action: rescheduled for auto recovery
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03852: Not able to acquire lock on entity, Db query for update NoWait(QoS is configured DirectWrite), or object lock in Coherence cache(QoS is configured CacheEnabled)

Cause: More than one thread is contending for this entity

Action: rescheduled for auto recovery
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-03853: Could not load Database Object of type "{1}" for key "{2}".

Cause: Dispatcher message was pre-maturely scheduled while global transaction had not committed.

Action: Engine will automatically retry. If all engine attempts fail, manual/auto recovery may be required.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04000: The process domain is unable to count the number of instances. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04001: The process domain is unable to count the number of instances for the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04002: An attempt to fetch the instances using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement was constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04003: An attempt to fetch the work items using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04004: The process domain is unable to insert the current log entries for the instance "{0}" to the audit trail table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04005: The process domain is unable to insert the current audit trail detail entries for the instance "{0}" to the audit details table. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04006: The process domain is unable to store the work items for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04007: The process domain is unable to store the audit trail for the synchronous instance "{0}" to the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04008: Unable to set the auto commit level for the current data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04009: unable to commit the current data source transaction; the exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04010: The process domain is unable to purge the instances from the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04011: The process domain is unable to delete the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04012: The process domain is unable to delete all the instances for the process "{0}" (revision "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04013: The process domain is unable to fetch a list of the expired work items in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04014: The process domain is unable to look up the type for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04017: The process domain is unable to find the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04018: The process domain is unable to find the audit trail entry for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04019: The process domain is unable to find the work items for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04020: The process domain is unable to find the audit trail for the synchronous instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04025: The process domain is unable to decode the properties for message GUID {0}, which are stored in column {1}; the exception reported is: {2}

Cause: This is an internal error. The properties have not been encoded properly.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with the logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-04026: The process domain is unable to find any pending callback messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04027: The process domain is unable to find any pending invoke messages in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04028: The process domain is unable to find any pending subscriptions in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04029: The process domain is unable to mark all instances (and activities) with process GUID {0} as stale. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04030: An attempt to fetch the audit details for the instance "{0}" (detail ID {1}) from the data source fails. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04031: An attempt to fetch the audit details for the instance "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04032: The process domain is unable to read the audit detail for detailId "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibit this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04033: The process domain is unable to fetch the document "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04034: The process domain is unable to find the closed instances for the domain "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04035: The process domain is unable to fetch the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04036: The process domain is unable to fetch the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04037: The process domain is unable to fetch the work item "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04038: The process domain is unable to update or insert the document "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04039: The process domain is unable to update the key table "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04040: The process domain is unable to update the LOB column "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04041: The process domain is unable to update or insert the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04042: The process domain is unable to update or insert the serialized scope for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04043: The process domain is unable to delete or insert the scope activation message with key "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04044: The process domain is unable to update or insert the work item "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04045: The process domain is unable to batch update or insert the work items for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04046: The process domain is unable to batch insert a series of synchronous work items into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04048: The process domain is unable to insert the delivery data for conversation "{0}", subscriber "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04049: The process domain is unable to select the delivery data for conversation "{0}" (subscriber "{1}") from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04050: The process domain is unable to select the delivery data for conversation "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04052: The process domain is unable to select the delivery data for subscriber "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04053: The process domain is unable to update the state of the delivery subscription "{1}" for conversation "{0}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04054: The process domain is unable to update the state of the delivery subscription "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04055: The process domain {0} is unable to delete handled delivery subscriptions. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04056: The process domain is unable to insert the delivery data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04057: The process domain is unable to delete the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04058: The process domain "{0}" is unable to delete the handled delivery data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04059: The process domain is unable to select the delivery data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04060: The process domain is unable to select the delivery data for the message {0} and the operation {1} from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04061: The process domain is unable to update the state of the delivery the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04062: The process domain is unable to delete the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04063: The process domain "{0}" is unable to delete the handled invocation data from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04064: The process domain is unable to select the invocation data for the message {0} from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04065: The process domain is unable to select the invocation data for the process "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04066: The process domain is unable to insert the invocation data for the message {0} and the operation {1} in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04067: The process domain is unable to update the state of the invocation the message {0}. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04069: The process domain is unable to fetch a list of the stale instances belonging to the process "{0}" (revision "{1}"). The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04076: The process domain is unable to look up the TX data source "{0}".

Cause: The J2EE container was not configured properly; a data source with the expected name has not been created or has been removed.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04077: The process domain is unable to establish a connection with the data source with the connection URL "{0}". The exception reported is: {1}

Cause: The J2EE container was not configured properly; the connection parameters for the data source might not have been correct.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04078: The process domain is unable to release its data source connection. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the transaction has become corrupt.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04079: cannot read BLOB stream from the data source with key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. In addition, verify that the connection pool properties, as defined in the application server startup properties, are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04080: The data stream for the instance or activity object "{0}" is not found in the data source.

Cause: The data stream with the instance or activity object key named in the error message was not found.

Action: Verify that the instance or activity key named in the error message refers to a valid instance or activity that has been started and not removed from the process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04082: The process domain is unable to delete the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04083: The process domain is unable to insert or update the exception entry for the activity "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04084: The process domain is unable to delete the exception entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04085: The process domain is unable to find the activity in the domain "{0}" with the custom key "{1}". The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04087: failure to find schedulable activities for domain "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04090: The process domain is unable to read the serialized scope for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04091: The process domain is unable to read the indexes for the instance "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04092: The process domain is unable to update or insert the indexes for the instance "{0}" into the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04099: The process domain is unable to find instances with root ID "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04100: The process domain is unable to find any invoke messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04101: The process domain is unable to find any callback messages with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04102: The process domain is unable to insert the process event for process "{0}" (revision "{1}") in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04103: The process domain is unable to find any process events with the specified where condition in the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04108: The process domain is unable to select the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04109: The process domain is unable to delete the attachment by the key "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04110: The process domain is unable to insert the attachment into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04111: The process domain is unable to select the attachment reference "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04112: The process domain is unable to insert the attachment reference into the data source. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04113: The process domain is unable to remove the attachment reference of the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04121: An attempt to fetch the test details using the where condition "{0}" from the data source fails. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04122: The process domain is unable to insert or update test details for the instance "{0}" in the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04123: The process domain is unable to update the state of the following delivery messages "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04124: The process domain is unable to update the state of the following delivery subscriptions "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04125: The process domain is unable to select the number of detail instances for the master instance specified by the conversation ID "{0}".

Cause: There was a problem accessing the SOA data source, or the SQL statement has been constructed incorrectly.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04126: The process domain is unable to select document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04127: The process domain is unable to insert document references for the instance ID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04128: The process domain is unable to select document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04129: The process domain is unable to insert document references for delivery message GUID "{0}". The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04132: cannot read CLOB stream from the data source with the key "{0}"; the exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the current transaction settings prohibited this action.

Action: Verify that the machine hosting the data source is physically connected to the network. Additionally verify that the connection pool properties as defined in the application server startup properties are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04138: The process domain is unable to store the test definition for process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04139: The process domain is unable to delete the test definition for the process "{0}", revision "{1}", test suite "{2}", location "{3}" in the data source. The exception reported is: {4}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04140: The process domain is unable to delete test definitions for the process "{0}", revision "{1}" in the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04141: The process domain is unable to delete the events logged for the process "{0}", revision "{1}" from the data source. The exception reported is: {2}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04142: The process domain is unable to delete the events logged for the domain. The exception reported is: {0}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04143: The process domain is unable to insert the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04144: The process domain is unable to update the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source, or the data segment was full.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04145: The process domain is unable to find the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04146: The process domain is unable to delete the fault entry for the activity "{0}" from the data source. The exception reported is: {1}

Cause: There was a problem accessing the SOA data source.

Action: Verify that the machine hosting the data source is physically connected to the network. Otherwise, verify that the data source connection parameters (user/password) are currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04147: The process domain was unable to fetch the activity guide instance with key "{0}" from the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04148: The process domain was unable to update the activity guide instance with key "{0}" in the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04149: The process domain was unable to insert the activity guide instance with key "{0}" to the datastore. The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource, or the data segment may be full.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04150: The process domain was unable to insert the audit counter for instance "{0}". The exception reported is: {1}

Cause: There is a problem accessing the SOA datasource.

Action: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04151: The process domain was unable to update the audit counter for the instance "{0}". The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource, or the data segment may be full.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04152: The process domain was unable to select the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04153: The process domain was unable to select for update on the audit counter for the instance "{0}" from the datastore. The exception reported is: {1}

Cause: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

Action: There is a problem accessing the SOA datasource.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04160: Cannot locak invoke message for processing.

Cause: Either Db row is locked by another thread or not enough ITLs required by concurrency is not available

Action: DB tuning may help.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-04161: Cannot locak subscription for processing.

Cause: Either Db row is locked by another thread or not enough ITLs required by concurrency is not available

Action: DB tuning may help.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05000: failure to fetch the dispatcher trace for the engine "{0}"; the exception reported is: {1}

Cause: The dispatcher trace XML file was written to an output buffer that was not sized correctly.

Action: Contact Oracle Support Services. Provide the error message and the process that appeared to cause the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05001: The message handler for the class {0} is not registered.

Cause: This was an internal error. It occurred because the dispatcher message handler was not registered in the MessageRegistry class.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05002: error while attempting to process the message "{0}"; the reported exception is: {1}

Cause: This error contained an exception thrown by the message handler.

Action: Contact Oracle Support Services. Please provide the SOA server logs to support. You could also enable debug logs for logger oracle.soa.bpel.engine and reproduce the problem and provide soa server diagnostics logs to Oracle Support. Please be advised that setting logger to debug level may degrade SOA server performance. Please consult Oracle Support before enabling it
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05003: No message local handler is implemented for the message "{0}".

Cause: This was an internal error. It occurred when a remote message was handled locally.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05004: error while sending a batch message to the dispatch queue; the exception reported is: {0}

Cause: There was a problem with enqueuing the message to the JMS queue or the dispatcher EJB could not be found in the JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05005: The process domain is unable to send a message to the JMS queue "{0}". The exception reported is: {1}

Cause: There was a problem with enqueuing the message to the JMS queue; the queue configuration might be incorrect.

Action: Verify that the JMS service for the application server has been configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05006: error while scheduling a batch message with the dispatcher; the exception reported is: {0}

Cause: There was a problem finding the dispatcher EJB in the current JNDI context.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05007: there is no active transaction while scheduling a message with the dispatcher

Cause: this usually happens if the underlying subsystem rollback back the transaction without bubbling up the system or transaction exception to the bpel layer

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05213: The process identifier "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process identifier for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid process ID. Process identifiers might start with a letter, a dollar sign ($) or an underscore (_); process characters (other than the first character) include a letter, a number, a dollar sign ($), an underscore (_) or a hyphen (-).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05214: The process revision tag "{0}" for the BPEL process archive "{1}" is not valid.

Cause: The process revision tag for the BPEL process archive named in the message was not valid.

Action: Ensure that the deployment descriptor contained in the BPEL process archive named in the error message has a valid revision tag. Valid revision tags may contain the following characters: a letter, a number, a dollar sign ($), an underscore (_), a hyphen (-), or a period (.).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05215: The process domain is encountering the following errors while loading the process "{0}" (composite "{1}"): {2}.

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05216: The class {0} for the process "{1}" (revision "{2}") does not implement the ICubeProcess interface.

Cause: The current BPEL component named in the error message was probably compiled with an older version of SCAC. All process classes contained within the process domain must implement this interface.

Action: Recompile the SOA composite again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05217: error while attempting to instantiate the class {0} for the process "{1}" (revision "{2}"); the exception reported was: {3}

Cause: This error contained an exception thrown by the underlying process loader module.

Action: Verify the exception trace in the log (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05222: cannot find class for type {0}

Cause: This was an internal error. The persistence manager for the type named in the error message could not be found in the class path. All required persistence managers should be registered by default.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05225: The persistence manager class {0} for the type {1} does not implement the IPersistenceManager interface.

Cause: This was an internal error. All persistence managers registered with the system must conform to the IPersistenceManager interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-05226: error while attempting to instantiate the persistence manager class {0} for type {1}; the exception reported was: {2}

Cause: The persistence manager class named in the error message was not in the system class path or there was an incompatibility with the JDK used to compile the class and the current JVM version.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05243: failure to obtain load lock for process "{0}"; the exception reported is: {1}

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05244: failure to obtain load lock for process "{0}"; timed out after {1} seconds.

Cause: The lock timeout was too small for the current load or there was a large number of process modification requests.

Action: The default timeout is 120 seconds. If this is not sufficient, customize the value using the JVM system property orabpel.process.lock.timeout, which is added to the JVM start line.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05250: error while attempting to deploy the BPEL component file "{0}"; the exception reported is: {1}

Cause: This error contained an exception thrown by the underlying deployment module.

Action: Please enable debug level for logger oracle.soa.bpel.engine.deployment and retry to deploy and provide soa server diagnostics logs to Oracle Support.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05252: The bpel container could not find persistence manager {0} for type {1} in the classpath

Cause: During dehydration the bpel container would serialize all the objects in the scope, each object in the scope should have a persistence manager registered or available in the classpath, otherwise bpel container would not know how to serialize the object for the dehydration store.

Action: Please make sure the persistence manager {0} for type {1} is available in classpath. please refer the documentation on how to write a persistence manager.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05253: Cannot re-deploy a durable process "{0}" with keepInstancesOnRedeploy=true.

Cause: A durable BPEL process cannot be deployed when the flag keepInstancesOnRedeploy is set to "true".

Action: Remove the keepInstancesOnRedeploy flag and try again.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-05254: Cannot re-deploy process "{0}", error during checksum calculation due to "{1}"

Cause: Error during checksum calculation

Action: Please Contact Oracle Support Services. Provide the error message and the exception trace in the log files
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-08015: cannot find operation {0} of portType {1} in the WSDLs of composite "{2}

Cause: In the composite named in the error message, either the WSDL that defined portType named in the error message was changed, or there were multiple definitions of the same portType.

Action: Ensure that there is only one definition of portType named in the error message and redeploy the composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09004: cannot convert the object of the class {0} to XML text

Cause: The object of the class named in the error message was not converted to XML text because of the exception: {1}

Action: Ensure that a valid marshaller is registered for the class named in the error message and refer to the BPEL developer guide about how to create a marshaller for a JAVA type.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09006: A mismatch of a schema-generated object version cannot be used in the system.

Cause: Either the XML schema class {0} has been compiled with an older version of SCHEMAC, or the BPEL process domain to which the class is deployed could not use the helper classes that were generated for this class.

Action: Recompile XML schema using the SCHEMAC tool that is bundled with the current process domain.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09007: error while attempting to instantiate the XML marshaller class {0}

Cause: The exception reported was: {1}

Action: Ensure that marshaller is defined, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09008: error while marshalling the object to XML

Cause: The class {0} did not implement the com.collaxa.cube.engine.xml.IMarshaller interface.

Action: Ensure that the marshaller class {0} implements the correct interface. All XML marshallers used in the BPEL must implement this interface.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09009: The BPEL service engine is not able to instantiate the schema registry.

Cause: The class {0} (for the run-time schema registry) did not implement the ISchemaRegistry interface.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09010: error attempting to create the schema registry class {0}

Cause: This is an internal error. The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09200: When performing the assign operation, the to node {0} is invalid.

Cause: The node named in the error message was either null or an empty node set, and it was not an instance of org.w3c.Element.

Action: Verify the node value at line number {1} is not null and is an instance of org.w3c.Element.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09204: The result of from-spec is null.

Cause: Either the from node value or the xpath query in the from node value was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, the from node value should not be empty. Verify the from node value at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09205: The assign activity of the to node query is returning zero node.

Cause: Either the to node data or the xpath query in the to node was invalid.

Action: According to BPEL4WS spec 1.1 section 14.3, verify the to node value at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09207: There is an error while parsing the xml data.

Cause: The XML data was not valid; the reason was {0}.

Action: Ensure the XML data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09219: failure to save the element {0} during dehydration

Cause: This element was not a root element and the scope had reference to this element. The scope should have references only to root element.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode).
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09221: failure to serialize the element {0} to the binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09222: failure to deserialize the document {0} from binary format during dehydration

Cause: The exception reported was: {1}

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09223: The assign activity part and query {0} are returning multiple nodes.

Cause: The assign activity part and query named in the error message returned multiple nodes. It should return single node.

Action: According to BPEL4WS specification 1.1 section 14.3, the assign activity part and query named in the error message should not return multiple nodes. Verify the part and xpath query named in the error message at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09224: cannot set a nonelement value to an element-based variable

Cause: An attempt to assign a nonelement value to an element-based variable failed.

Action: Verify the BPEL source for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09225: cannot set a nonmessage value to a message-based variable

Cause: An attempt to assign a nonmessage value to a message-based variable failed.

Action: Verify the BPEL source for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09226: cannot use a simple type variable in the setVariableData method

Cause: It was not allowed to use simple type variable in setVariableData method.

Action: Verify the BPEL JAVA exec source code for invalid assign activities.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09227: The from-spec for {2} operation must return either an attribute list or an element list.

Cause: The from-spec did not return an attribute list or an element list.

Action: Verify the assign activity for the operation named in the error message at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09228: The message part {2} of the WSDL variable {3} is not an XML element; {4} operation cannot be performed.

Cause: The operation named in the error message was not performed because the named message part of the WSDL variable named in the error message was not an XML element.

Action: Verify the message part named in the error message is a valid XML element at line number {1} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09229: The to-spec does not yield any data; the {1} operation cannot be performed.

Cause: The operation named in the error message was not performed because to-spec did not yield any data.

Action: Verify the to-spec of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09230: The parent of the selection result {1} does not exist or is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the parent of the selection result named in the error message did not exist or was not an XML element.

Action: Verify the element of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09231: The selection result at list entry {1} does not have a parent node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message did not have a parent node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09232: The selection result at list entry {1} is not an XML node; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML node.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09233: The selection result at list entry {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result at the list entry named in the error message was not an XML element.

Action: Verify the list entry of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09234: The selection result of {1} is not an XML element; the {2} operation cannot be performed.

Cause: The operation named in the error message was not performed because the selection result named in the error message was not an XML element.

Action: Verify the assign activity at line number {0} in the BPEL source and ensure the run-time data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09240: failure of the copyList assign operation

Cause: The element list specified by the to-spec used in the copyList operation was not contiguous.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09241: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of copyList was element-based, while the to-list was not element-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09242: The copyList assign operation fails due to a type mismatch.

Cause: The from-list of the copyList operation was attribute-based, but the to-list was not attribute-based.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09243: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have an element parent.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure that the run-time to-list data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09244: The copyList assign operation fails.

Cause: The element returned from the to-list spec of the copyList operation did not have a parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09245: The copyList assign operation fails.

Cause: The members of the to-list spec of the copyList operation did not share the same parent node.

Action: Verify the copyList operation of the assign activity at line number {0} in the BPEL source and ensure the run-time to-list data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09248: cannot instantiate document builder {0}

Cause: The reason was: {1}

Action: Ensure that document builder class named in the error message exists in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09249: error while parsing the XML text {0}

Cause: The XML text was invalid because {1}.

Action: Verify that the XML text is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09250: error while creating the XML document

Cause: The reason was {0}.

Action: Contact Oracle Support Services. Provide the error message and the exception trace in the log files (with logging level set to debug mode)
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

ORABPEL-09251: cannot perform copy XMLNS for prefix:{0}

Cause: Namespaces conflicted: {1} and {2}

Action: Verify the from element data of the assign operation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09252: cannot perform copy

Cause: The bpelx:copyQName attribute on copy assign element is set to "yes", but the result of the from-spec is not a QName.

Action: Verify the from-spec of the assign operation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09500: An error occurs while processing the XPath expression; the expression is {0}.

Cause: The XPath expression failed to execute; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath query is correct.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09501: An error occurs while registering the XPath function {0}.

Cause: Registering the XPath function failed; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath function named in the error message is defined in the domain property file.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09502: The syntax error occurs while parsing XPath expression {0}, at position {1}.

Cause: The XPath query syntax was wrong; the exception was: {2}

Action: Check the detailed root cause described in the exception message text and verify that the XPath expression named in the error message is correct. The XPath expression is defined in the BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09503: an error occurs while parsing XPath expression {0}

Cause: The XPath expression was invalid; the reason was: {1}.

Action: Check the detailed root cause described in the exception message text and verify that the XPath expression named in the error message is correct. The XPath expression is defined in the BPEL process.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09504: The XPath variable or expression {0} is empty at line {1}.

Cause: An attempt to read or copy data referenced or computed by the XPath expression either had invalid data, according to the XML schema, or did not contain certain optional data.

Action: Ensure that the variable or expression result named in the error message is not empty. Enable XML schema validation of related variables to ensure the run-time data is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09505: The XPath variable or expression {0} is empty at line {1}.

Cause: An attempt to create the missing to data by the XPath expression failed. Attribute ignoreMissingToData does not apply to this expression.

Action: Make sure the expression uses only: PathExpr ::= "/"RelativePathExpr RelativePathExpr ::= ForwardStep (("/") ForwardStep)* ForwardStep ::= (ForwardAxis QName) | AbbrevForwardStep AbbrevForwardStep ::= "@"? QName ForwardAxis ::= ("child" "::") | ("attribute" "::").
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09705: An error occurs while initializing BPEL variable {0}; the schema processor cannot find the element {1} in the following schemas: {2}.

Cause: The XSD element on which the variable was based was not properly defined in XSD or the WSDL.

Action: Ensure that the element named in the error message is valid in the XSD or the WSDL.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09706: An error occurs while initializing BPEL variable {0} at line {1}; the schema processor cannot find type {2} for part {3} in the following schemas: {4}.

Cause: The XSD type on which the variable was based was not properly defined in XSD or the WSDL.

Action: Ensure that the type named in the error message is valid in the WSDL.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09707: cannot initialize variable {0} at line {2}

Cause: The reason was: {1}.

Action: Ensure that the variable named in the error message is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-09717: validation of variable {0} failed

Cause: The reason was: {1}.

Action: Pleasehandle the exception in bpel.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20300: A problem occurs while processing reports data {0}.

Cause: The DataCaptureAgency class reported an exception.

Action: Examine the log file to determine the problem.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20301: The Reporting Data Publisher {0} fails.

Cause: The data publisher reported an exception.

Action: Examine the log file for more details.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20302: A problem occurs while setting up a connection to the JMS destination {0} using the connection factory {1}.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS configuration is valid.
Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20303: An error occurs while publishing report data to the JMS destination {0}.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS destination is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20304: The JMS destination lookup fails. The related report data will not be published.

Cause: The JMS configuration was incorrect.

Action: Verify that the JMS destination or JNDI name {0} is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20305: The JMS connection factory lookup fails. The related report data will not be published.

Cause: The JMS configuration was incorrect.

Action: Verify that JNDI name {0} is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20306: A problem occurs while releasing the JNDI resources used to publish to the destination {0}.

Cause: The JMS configuration was incorrect.

Action: Verify that JNDI name is correct.
Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20307: The custom data publisher class {0} cannot be loaded.

Cause: The custom data publisher class named in the error message was not found.

Action: Verify that the class file and all dependencies can be loaded from the suitcase or from the application class path.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20308: The custom data publisher class {0} cannot be initialized properly.

Cause: An attempt to create the custom data publisher class named in the error message failed.

Action: Examine the log file for a class creation exception.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20309: The sensor cannot be registered because it has no name.

Cause: The sensor name was missing.

Action: Specify the sensor name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20310: The sensor {0} cannot be registered because a sensor with the same name is already registered.

Cause: The sensor name was a duplicated name.

Action: Specify a unique sensor name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20311: The sensor-sensor action association for sensor {0}, action {1} cannot be created because no sensor named {2} exists in the registry.

Cause: The sensor name was missing.

Action: Specify a valid sensor name in the association.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20312: The sensor-sensor action association for sensor {0}, action {1} cannot be created because no sensor action named {2} exists in the registry.

Cause: The sensor name was missing.

Action: Register the sensor action before specifying an assocation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20313: The sensor action cannot be registered because it has no name.

Cause: The sensor name was missing.

Action: Specify the sensor action name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20314: The sensor action {0} cannot be registered because a sensor action with the same name is already registered.

Cause: The sensor action name was a duplicated name.

Action: Specify a unique sensor action name.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20315: An error occurs while loading sensors and sensor actions for the process {1}, revision {2} in the domain {0}.

Cause: The loading of sensors failed.

Action: Examine the log file for the exception of loading sensors.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20316: No target is specified for sensor {0}.

Cause: The target information was missing.

Action: Specify a target.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20317: The target {1} for sensor {0} is invalid.

Cause: The target information was wrong.

Action: Specify a dollar sign ($) before the variable name and ensure that the variable exists.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20318: The configuration for sensor {0} is missing.

Cause: The sensor configuration was missing.

Action: The variableConfig element must be specified for variable sensors. Complete the variable sensor definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20319: The sensor {0} is a variable sensor but has activity or fault configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20320: The sensor {0} is a fault sensor but has activity or variable configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20321: The configuration for sensor {0} is missing.

Cause: The sensor configuration was missing.

Action: The activityConfig element must be specified for activity sensors. Complete the activity sensor definition.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20322: The sensor {0} is an activity sensor but has variable or fault configurations defined.

Cause: The sensor configuration was wrong.

Action: Remove the unnecessary configuration elements.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20323: The sensor {0} is invalid because {1} is an unrecognized sensor kind.

Cause: The sensor kind was wrong.

Action: Specify a valid sensor kind.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20324: The sensor action {0} is invalid because it publishes to a JMS destination but no destination is specified.

Cause: The JMS destination was missing in the sensor action.

Action: Specify the JMS destination property in the sensor action.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20325: The sensor action {0} is invalid because it publishes to a JMS destination but no connection factory is specified.

Cause: The JMS connection factory information was wrong.

Action: Specify the JMS connection factory.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20326: The sensor action {0} is invalid because it publishes to a custom publisher but no publisher class is specified.

Cause: The custom publisher class name was wrong.

Action: Specify the fully qualified class name of the custom data publisher.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20327: The sensor action {0} is invalid because {1} is an unrecognized publish type.

Cause: The publish type was wrong.

Action: Specify a valid publish type.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20328: The sensor action {0} is invalid because the associated sensor {1} cannot be found.

Cause: The associated sensor named in the error message was missing.

Action: Ensure that sensor names used in the sensor action file match those defined in the sensor file.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20329: The sensor action {0} is invalid because the connection name is not specified.

Cause: The connection name in the sensor action named in the error message was missing.

Action: Specify the connection name property in the sensor action.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20330: The Sensor.xsd schema cannot be loaded from the class path.

Cause: The installation of Sensor.xsd was missing

Action: Ensure that the Sensor.xsd file has not been modified in any way.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20331: The JMS Adapter cannot be loaded from the class path.

Cause: The loading of the JMS adapter failed.

Action: Ensure that the JMS adapter has been properly deployed in the application server.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20501: An error occurs while loading monitor model for the process {1}, revision {2} in the domain {0}.

Cause: The loading of monitor model failed.

Action: Examine the log file for the exception of loading monitor model.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20502: An error occurs while monitor database executing command {1}, for database {0}.

Cause: The monitor database command execution failed.

Action: Examine the log file for the exception of executing a monitor database command.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20503: An error occurs while monitor buisiness indicator evaluates the xpath {0}.

Cause: The monitor business indicator xpath evaluation execution failed.

Action: Examine the log file for the exception of executing a monitor business indicator xpath evaluation.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20504: An error occurs while monitor process activity execution for activity {0} and event {1}.

Cause: The monitor process activity execution failed.

Action: Examine the log file for the exception of executing a monitor process activity.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20505: An error occurs while monitor creates the registry. This error does not interfere in the BPEL process.

Cause: The monitor files are not found or an error occurs while loading the monitor files.

Action: Examine the log file for the exception of creating a monitor registry.
Level: 1

Type: WARNING

Impact: Programmatic

ORABPEL-20506: An error occurs while monitor loads the configuration.

Cause: The monitor config load failed.

Action: Examine the log file for the exception of loading a monitor config.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20507: An error occurs while monitor pubishes data to BAM.

Cause: The monitor BAM publish failed.

Action: Examine the log file for the exception of publishing monitor data to BAM publisher.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20508: An error occurs while monitor get the activity path information.

Cause: The monitor get activity path failed.

Action: Examine the log file for the exception of getting activity path information.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20509: Composite: {0}, Process: {1}, Process Revision: {2}, Business Indicator: {3}, Metric: {4}, Activity: {5}, Evaluation Event: {6}.Skipping evaluation for all metrics in this Business Indicator/Activity/Evaluation Event. No rows will be inserted.

Cause: The XPATH Evaluation of Business Indicator failed.

Action: Check XPath expression in conjunction with process variable state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20510: Composite: {0}, Process: {1}, Process Revision: {2}, Business Indicator: {3}, Metric: {4}, Activity: {5}, Evaluation Event: {6}.A null value will be inserted for this metric.

Cause: The Metric XPATH Evaluation of Business Indicator failed.

Action: Check Metric XPath expression in conjunction with process variable state.
Level: 1

Type: ERROR

Impact: Programmatic

ORABPEL-20511: An attempt to connect BAM failed. Error Message: {0}

Cause: Either BAM adapter credentials are incorrect or SOA/BAM trusted domain configuration is missing.

Action: See "Configuring the Oracle BAM Adapter" in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more information.
Level: 1

Type: ERROR

Impact: Programmatic

42 ORAMED-01001 to ORAMED-09001

ORAMED-01001: Error occurred while assigning to target "{0}" using expression "{1}".

Cause: Error occurred while assigning to target "{0}" using expression "{1}".

Action: Check if source message has right values or source expression is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01002: Metadata error occurred while assigning. Check if source and target expression are valid. ["{0}"].

Cause: Metadata error occurred while assigning. Check if source and target expression are valid. ["{0}"].

Action: Modify source or target for valid expression. Empty string, null and invalid expressions are not allowed
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01003: Invalid source used while assigning. Check if source expression is valid. ["{0}"].

Cause: Invalid source used while assigning. Check if source expression is valid. ["{0}"].

Action: Modify source for valid expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01004: Source evaluated from expression "{0}" is invalid.

Cause: Source evaluated from expression "{0}" is invalid.

Action: Check the expression for correctness. Modify the source expression based on the requirement, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01005: Target creation for target expression "{0}" failed.

Cause: Target creation for target expression "{0}" failed.

Action: Check if the target expression is valid, otherwise, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01006: Encountered variable which is not supported or implemented "{0}".

Cause: Encountered variable which is not supported or implemented "{0}".

Action: Check if source and target expression for valid variable like $in, $out, $initial and so forth, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01007: Header variable "{0}" not recognized.

Cause: Header variable "{0}" not recognized.

Action: Header variable should be of the format $in.header.<prefix>_<root-elem>. Fix the header variable.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01008: Property "{0}" not found in "{1}" message.

Cause: Property "{0}" not found in "{1}" message.

Action: Check source and target expression for valid property name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01009: Failed to assign element "{0}" to element "{1}". Parent node not found.

Cause: Failed to assign element "{0}" to element "{1}". Parent node not found.

Action: Check target expression for valid element associated with proper owner document, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01010: Failed to assign source "{0}" to target part "{1}". Assigning Text data to part is not supported unless target part is available.

Cause: Failed to assign source "{0}" to target part "{1}". Assigning Text data to part is not supported unless target part is available.

Action: Check source and target expression for valid expression, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01011: Failed to assign attachment "{0}" from source to target. Attachment not available in source message.

Cause: Failed to assign attachment "{0}" from source to target. Attachment not available in source message.

Action: Check source expression is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01012: Part "{0}" not found in source message.

Cause: Part "{0}" not found in source message.

Action: Check source and target expression for valid part name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01013: Encountered dynamic assign which is not supported "{0}".

Cause: Encountered dynamic assign which is not supported "{0}".

Action: Check if source has valid dynamic assign. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01014: Encountered assign fragment with type "{0}". Supported are xml and xquery.

Cause: Encountered assign fragment with type "{0}". Supported are xml and xquery.

Action: Check if source has valid assign. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01015: Error occurred while evaluating xpath expression "{0}".

Cause: Error occurred while evaluating xpath expression "{0}".

Action: Check if xpath expression is valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01101: Error evaluating filter expression.

Cause: Error evaluating filter expression.

Action: Ensure that the filter expression is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01102: Error evaluating filter expression, "{0}".

Cause: Error evaluating filter expression, "{0}".

Action: Ensure that the filter expression metadata is valid, otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01104: Encountered variable which is not supported "{0}".

Cause: Encountered variable which is not supported "{0}".

Action: Check if source has valid variable $in, filter expression is supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01105: Encountered dynamic filter which is not supported "{0}".

Cause: Encountered dynamic filter which is not supported "{0}".

Action: Check if source has valid dynamic filter expression. Supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01201: Error occurred while transforming payload using "{0}" for target part "{1}".

Cause: Error occurred while transforming payload using "{0}" for target part "{1}".

Action: Review the XSL/XQuery or source payload. Either the XSL/XQuery defined does not match with the payload or payload is invalid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01202: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}".

Cause: Fatal error occurred while transforming payload using XSL "{0}" for target part "{1}".

Action: Review the XSL for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01203: No part exists with name "{0}" in source message.

Cause: No part exists with name "{0}" in source message.

Action: Review the transformation definition in mplan. Contact Oracle Support Services if the error cannot be fixed.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01204: Initial source message is not available in the context. Failed evaluating "{0}".

Cause: Initial source message is not available in the context. Failed evaluating "{0}".

Action: Review the transformation/assign definition in mplan. Accessing initial source message is not supported during callback.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01205: Failed to persist streaming attachment for message "{0}".

Cause: Failed to persist streaming attachment for message "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01206: Encountered dynamic transformation which is not supported "{0}".

Cause: Encountered dynamic transformation which is not supported "{0}".

Action: Check if source has valid dynamic transformation. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01301: Schematron validation fails with error "{0}".

Cause: Schematron validation fails with error "{0}".

Action: Fix the payload.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01302: Response payload for operation "{0}" is invalid.

Cause: Response payload for operation "{0}" is invalid.

Action: Response received by Mediator was either invalid or null. Examine why the service being invoked by Mediator is returning a null/invalid response. You can also try invoking the service directly and see if it sends back proper response.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01303: XSD schema validation fails with error "{0}".

Cause: XSD schema validation fails with error "{0}".

Action: Fix payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01304: Schematron validation failure.

Cause: Schematron validation failure.

Action: Fix payload or schematron definition and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01305: Group ID validation failure.

Cause: Group ID validation failure.

Action: XPATH Expression returned null Group Id. Check the XPATH expression, fix the payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01306: Sequence ID validation failure."{0}".

Cause: Sequence ID validation failure."{0}".

Action: SequenceID value is incorrect. Either XPATh Expression returned null or sequenceID value does not fall within the sequence range. Check the XPATH expression, fix the payload and resubmit.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01351: Unable to execute "{0}" method on callout instance of "{1}".

Cause: Unable to execute "{0}" method on callout instance of "{1}".

Action: Check server log for any exceptions. Check if there is an issue in implementation of Java callout class.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01360: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Cause: Wrong source message type. Neither a NormalizedMessage nor a BusinessEvent, message type class :{1}

Action: Contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01361: Mediator does not support the Resequencing strategy."{0}"

Cause: Mediator does not support the Resequencing strategy."{0}"

Action: Mediator does not support the Resequencing strategy. Refer to the documentation of resequencer for more details.You can also contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01362: Unexpected runtime error occurred while processing the message.

Cause: Unexpected runtime error occurred while processing the message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-01363: Mediator does not have content to respond to the request-response type operation operation "{0}".

Cause: Mediator does not have content to respond to the request-response type operation operation "{0}".

Action: Examine your design to rectify, or reset the property oracle.soa.mediator.twoway.allowNullReply to true.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02001: This error occurs because of invalid filter expression "{0}".

Cause: This error occurs because of invalid filter expression "{0}".

Action: Review the filter expression and check for possible syntax errors in the filter expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02002: Invalid filter metadata "{0}". Either no filter expression specified or expression may be invalid.

Cause: Invalid filter metadata "{0}". Either no filter expression specified or expression may be invalid.

Action: Fix the filter condition metadata.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02051: Invalid callout implementation "{0}".

Cause: Invalid callout implementation "{0}".

Action: Fix the callout implementation.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02101: Cannot load XSL transform into the cache for XSL or XSLT "{0}".

Cause: Cannot load XSL transform into the cache for XSL or XSLT "{0}".

Action: Check XSL file for any syntax error and fix the same.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02102: Invalid part type "{0}".

Cause: Invalid part type "{0}".

Action: Ensure that the parts provided in transformation/xpath are valid.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02103: Invalid assign expression "{0}".

Cause: Invalid assign expression "{0}".

Action: Check assign xpath expression for any syntax error. If there are any syntax errors, correct the xpath expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02201: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Cause: Could not load schema document into the cache for XSD "{0}". Reason : {1}

Action: Check the XSD schema for any syntax error and fix the same.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02202: Invalid part name in metadata for schematron validator "{0}".

Cause: Invalid part name in metadata for schematron validator "{0}".

Action: Fix the schematron metadata.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02203: Could not load schematron file {0}.

Cause: Could not load schematron file {0}.

Action: Provide the correct schematron document.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02204: Could not load wsdl interface for message with component dn "{0}".

Cause: Could not load wsdl interface for message with component dn "{0}".

Action: Fix the component to point to valid wsdl.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02205: Schematron document for schematron file {0} is invalid.

Cause: Schematron document for schematron file {0} is invalid.

Action: Fix the schematron document.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02206: Could not create XSD validator for schema with target namespace "{0}" for message "{1}".

Cause: Could not create XSD validator for schema with target namespace "{0}" for message "{1}".

Action: Check XML schema for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02207: Failed to validate redeployment of mediator.

Cause: Failed to validate redeployment of mediator.

Action: Configure composite properly, otherwise contact Oracle for support.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02208: Component is not valid. Either component/componentDN is null or there is a mismatch between "{0}" and "{1}"

Cause: Component is not valid. Either component/componentDN is null or there is a mismatch between "{0}" and "{1}"

Action: Configure composite properly, otherwise contact Oracle for support.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02209: Failed to fetch mediator from source URI "{0}".

Cause: Failed to fetch mediator from source URI "{0}".

Action: Configure composite properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02210: Encountered dynamic schematron which is not valid "{0}".

Cause: Encountered dynamic schematron which is not valid "{0}".

Action: Check if source has valid dynamic schematron validator. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02301: Could not load mediator mplan information. Reason : {0}

Cause: Could not load mediator mplan information. Reason : {0}

Action: Check your mediator mplan for any syntax error.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02302: Could not load metadata manager. Reason : {0}.

Cause: Could not load metadata manager. Reason : {0}.

Action: Check your composite configuration.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02303: Composite reference {0} not found for operation {1}.

Cause: Composite reference {0} not found for operation {1}.

Action: Check your composite.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02304: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Cause: Could not load mediator mplan for componentDN "{0}" . It may be undeployed.

Action: Using SOA Enterprise Manager, check if composite is deployed. If the composite is not deployed, you can try deploying the composite again.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02305: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names.

Cause: Could not find mediator case for case name "{0}" . Mediator component may be redeployed with different case names.

Action: This message will be put in error state. Fix the mplan by adding the right case and then recover it through EM.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02401: Got invalid response from decision service : {0}

Cause: Got invalid response from decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02402: Could not invoke decision service : {0}

Cause: Could not invoke decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-02403: Dynamic mplan returned by decision service is invalid. Mplan returned by decision service : {0}

Cause: Dynamic mplan returned by decision service is invalid. Mplan returned by decision service : {0}

Action: Ensure that the decision service used by the mediator is configured properly.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03001: Unable to lock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Cause: Unable to lock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Action: Unable to lock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03002: Unable to retrieve locked Resequencer Groups for containerId "{0}" and timestamp "{1}".

Cause: Unable to retrieve locked Resequencer Groups for containerId "{0}" and timestamp "{1}".

Action: Unable to retrieve lock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03003: Unable to store Resequencer Group."{0}".

Cause: Unable to store Resequencer Group."{0}".

Action: Unable to store Resequencer Group. Check your database connection or check data.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03004: Unable to store Resequencer Message."{0}"

Cause: Unable to store Resequencer Message."{0}"

Action: Unable to store Resequencer Message. Check your database connection or check data.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03005: Unable to unlock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Cause: Unable to unlock Resequencer Groups for container ID "{0}" and timestamp "{1}".

Action: Unable to unlock Resequencer Groups. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03006: Unable to retrieve Resequencer message. "{0}"

Cause: Unable to retrieve Resequencer message. "{0}"

Action: Unable to retrieve Resequencer message. Check your database connection.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03101: Unable to get subscriptions for message "{0}"

Cause: Unable to get subscriptions for message "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03102: Error creating cache for cache policy "{0}". Reason : {1}

Cause: Error creating cache for cache policy "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03103: Cannot load Cache entry with NULL or EMPTY key.

Cause: Cannot load Cache entry with NULL or EMPTY key.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03104: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Cause: Do not cache RuntimeESBSystem object for NULL or EMPTY system GUID.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03105: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Cause: Could not read WSDL Definition for WSDL with NULL or EMPTY file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03106: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Cause: Do not cache WSDL Definition for NULL or EMPTY WSDL file name.

Action: The WSDL file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03107: Could not read Schema Document for XSD with NULL or EMPTY file name.

Cause: Could not read Schema Document for XSD with NULL or EMPTY file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03108: Do not cache Schema Document for NULL or EMPTY XSD file name.

Cause: Do not cache Schema Document for NULL or EMPTY XSD file name.

Action: The XSD schema file being read is not available or reachable. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03109: Could not read parsed filter expression for NULL or EMPTY expression.

Cause: Could not read parsed filter expression for NULL or EMPTY expression.

Action: The filter expression is null or empty. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03110: Information to process an incoming callback message is not available.

Cause: Information to process an incoming callback message is not available.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03201: Retry of deferred message failed.

Cause: Retry of deferred message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03202: Retry of callback message failed.

Cause: Retry of callback message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03203: Retry of timeout message failed.

Cause: Retry of timeout message failed.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03301: Unexpected exception in case execution "{0}".

Cause: Unexpected exception in case execution "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03302: Unexpected exception in one-way operation "{0}" on reference "{1}".

Cause: Unexpected exception in one-way operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03303: Unexpected exception in request response operation "{0}" on reference "{1}".

Cause: Unexpected exception in request response operation "{0}" on reference "{1}".

Action: Check whether the reference service is properly configured and running or look at exception for analyzing the reason or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03304: Unexpected exception in asynchronized request execution "{0}".

Cause: Unexpected exception in asynchronized request execution "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03401: Context lookup failed "{0}".

Cause: Context lookup failed "{0}".

Action: Ensure that the topic is mapped to a JNDI tree.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03402: Error creating "{0}".

Cause: Error creating "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03403: Subscriber does not exist for system "{0}".

Cause: Subscriber does not exist for system "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03405: Error converting field "{0}".

Cause: Error converting field "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03406: Publisher does not exist for system "{0}".

Cause: Publisher does not exist for system "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03408: Unable to store deferred message "{0}".

Cause: Unable to store deferred message "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03409: Invalid, premature, or already-handled callback message. No correlation found for message with conversation ID "{0}".

Cause: Invalid, premature, or already-handled callback message. No correlation found for message with conversation ID "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03501: Unable to start transaction; transaction status is "{0}".

Cause: Unable to start transaction; transaction status is "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03502: Unable to resume transaction.

Cause: Unable to resume transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03503: Unable to commit transaction. Transaction has been rolled back.

Cause: Unable to commit transaction. Transaction has been rolled back.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03504: Unable to rollback transaction.

Cause: Unable to rollback transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03505: "{0}" object not found in JNDI tree.

Cause: "{0}" object not found in JNDI tree.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03506: Unable to get transaction status.

Cause: Unable to get transaction status.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03507: Unable to set rollback only for transaction; transaction status is "{0}".

Cause: Unable to set rollback only for transaction; transaction status is "{0}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03508: One of the routing rule execution resulted in a transaction rollback.

Cause: One of the routing rule execution resulted in a transaction rollback.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03509: Unable to suspend transaction.

Cause: Unable to suspend transaction.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03510: Error obtaining Transaction Manager.

Cause: Error obtaining Transaction Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03511: "{0}" object not found in jndi tree

Cause: "{0}" object not found in jndi tree

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03601: Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "{0}"

Cause: Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03602: Unable to create document.

Cause: Unable to create document.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03603: Unable to register base function "{0}" for "{1}".

Cause: Unable to register base function "{0}" for "{1}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03604: Unable to stream xslt results into temp file "{0}"

Cause: Unable to stream xslt results into temp file "{0}"

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03651: Unable to create callout instance for "{0}".

Cause: Unable to create callout instance for "{0}".

Action: Ensure that your callout configuration is correct. Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03652: Unable to execute "{0}" method on callout instance of "{1}".

Cause: Unable to execute "{0}" method on callout instance of "{1}".

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03701: Unable to configure xpath transformer.

Cause: Unable to configure xpath transformer.

Action: Check log file for any exceptions to fix the configuration otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03702: Unable to resolve source expression "{0}".

Cause: Unable to resolve source expression "{0}".

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03801: Unable to initialize filter/validator. "{0}" is not supported.

Cause: Unable to initialize filter/validator. "{0}" is not supported.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03802: Unable to create initial context.

Cause: Unable to create initial context.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-03803: Unable to initialize Container ID Manager.

Cause: Unable to initialize Container ID Manager.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04001: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04002: Error executing service due to server down "{0}". Reason : {1}

Cause: Error executing service due to server down "{0}". Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04004: Error persisting resequencer message,"{0}" , due to internal Error.. Reason : {1}

Cause: Error persisting resequencer message,"{0}" , due to internal Error.. Reason : {1}

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04101: Error receiving DB message.

Cause: Error receiving DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04102: Error publishing DB message.

Cause: Error publishing DB message.

Action: Check log file for any exceptions and contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04201: Metadata error occurred while using DVM. Check if DVM location, source domain, source value expression and dynamic parameters are valid. ["{0}"].

Cause: Metadata error occurred while using DVM. Check if DVM location, source domain, source value expression and dynamic parameters are valid. ["{0}"].

Action: Modify required parameters. Empty string, null and invalid expressions are not allowed otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04202: Invalid source value expression used while configuring DVM. Check if source value expression is valid. ["{0}"].

Cause: Invalid source value expression used while configuring DVM. Check if source value expression is valid. ["{0}"].

Action: Modify source value for valid expression.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04203: Error occured while overriding information via DVM lookup Check if DVM location "{0}", source domain "{1}" and source expression "{2}" is valid.

Cause: Error occured while overriding information via DVM lookup Check if DVM location "{0}", source domain "{1}" and source expression "{2}" is valid.

Action: Modify required parameters. Empty string, null and invalid expressions are not allowed otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04204: Part "{0}" not found in source message.

Cause: Part "{0}" not found in source message.

Action: Check source expression for valid part name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04205: Property "{0}" not found in "{1}" message.

Cause: Property "{0}" not found in "{1}" message.

Action: Check source expression for valid property name otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04206: Encountered variable which is not supported "{0}".

Cause: Encountered variable which is not supported "{0}".

Action: Check if source has valid variable $in, lookup is supported only for inbound expression. Otherwise Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04207: Metadata error occurred while using Business Rule. Check if decision service reference and operation are valid. ["{0}"].

Cause: Metadata error occurred while using Business Rule. Check if decision service reference and operation are valid. ["{0}"].

Action: Modify required parameters. Empty string, null and invalid expressions are not allowed otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04208: Encountered multiple dynamic values to be applied on one static routing rule ["{0}"]. Multiple dynamic values are not supported in static routing rule.

Cause: Encountered multiple dynamic values to be applied on one static routing rule ["{0}"]. Multiple dynamic values are not supported in static routing rule.

Action: Modify Business Rules or DVM to generate only one dynamic value, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04209: Encountered 11g version dynamic routing metadata. 11g dynamic routing metadata is not supported. ["{0}"] 11g dynamic routing rule has to be upgraded.

Cause: Encountered 11g version dynamic routing metadata. 11g dynamic routing metadata is not supported. ["{0}"] 11g dynamic routing rule has to be upgraded.

Action: Refer to the documentation of dynamic routing upgrade for more details, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04301: XQuery execution evaluated in null result.

Cause: XQuery execution evaluated in null result.

Action: Please make sure the XQuery content will result in non null value, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04302: Failed to obtain XQuery connection. ["{0}"]

Cause: Failed to obtain XQuery connection. ["{0}"]

Action: Please check the logs for more details, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04303: Failed to initialize XQuery. Cause ["{0}"].

Cause: Failed to initialize XQuery. Cause ["{0}"].

Action: Please check the logs for more details, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04304: Parameter configured for XQuery transformation is incorrect. ["{0}"].

Cause: Parameter configured for XQuery transformation is incorrect. ["{0}"].

Action: Ensure that the XQuery parameters provided in transformation are valid, otherwise contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04305: Failed to resolve XQuery external variable "{0}"

Cause: Failed to resolve XQuery external variable "{0}"

Action: External variable which is declared in transformation param must be mediator implicit variables.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04306: Evaluating the implicit mediator XQuery variables resulted in {0}

Cause: Evaluating the implicit mediator XQuery variables resulted in {0}

Action: External variable which is declared in transformation param must be mediator implicit variables. Otherwise please check the logs for more details.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04307: Unable to execute XQuery expression for "{0}".

Cause: Unable to execute XQuery expression for "{0}".

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04308: Unable to bind XQuery external variables. Cause = {0}

Cause: Unable to bind XQuery external variables. Cause = {0}

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04309: Failed to transform XQuery {0}. XQuery execution must result in XML element or document to assign it to the target.

Cause: Failed to transform XQuery {0}. XQuery execution must result in XML element or document to assign it to the target.

Action: Check log file for any exceptions to fix the expression otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-04310: Invalid XQuery implicit variable {0} declared of type {1} Mediator implicit variables which are declared as XQuery external variables must conform to their equivalent type. For ex: $in.<part-name> can be document or element.

Cause: Invalid XQuery implicit variable {0} declared of type {1} Mediator implicit variables which are declared as XQuery external variables must conform to their equivalent type. For ex: $in.<part-name> can be document or element.

Action: Check log file for any exceptions to fix the external variables otherwise contact Oracle Support Services for further help.
Level: 1

Type: ERROR

Impact: Programmatic

ORAMED-09001: Parameter name contains "{0}" qname "{1}".

Cause: Parameter name contains "{0}" qname "{1}".

Action: Verify Name-Value parameters to be of the form 'name1=value1 name2=value2' with value not having any spaces.
Level: 1

Type: ERROR

Impact: Programmatic

43 OSB-75050 to OSB-2032402

OSB-75050: Missing parameter: parentClassLoader

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75051: Missing parameter: mwHome

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75052: Missing parameter: mbeanServerType

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75053: Missing parameter: username

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75054: Missing parameter: password

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75055: Missing parameter: inputName

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75056: Missing parameter: address

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75057: Missing parameter: protocol

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75058: Missing parameter: port

Cause: The OSB OVAB Plugin has not been configured correctly.

Action: Ensure that all required parameters are configured.
Level: 1

Type: ERROR

Impact: Other

OSB-75059: No channel supporting a JMX protocol found in appliance

Cause: Unable to find a suitable channel supporting a JMX protocol.

Action: Ensure that the appliance is configured with a suitable channel.
Level: 1

Type: ERROR

Impact: Other

OSB-75060: MBeanServerConnection already closed

Cause: Something has already closed the MBeanServerConnection. This should not happen.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-75061: Importing of some (or all) OSB resources failed

Cause: Importing of some (or all) OSB resources failed. The log file should contain more detail.

Action: Check the log file for more details and correct the errors.
Level: 1

Type: ERROR

Impact: Other

OSB-75062: Importing the configuration plan failed: {0}

Cause: Importing the configuration plan failed. The error message will provide more details.

Action: Correct the error described.
Level: 1

Type: ERROR

Impact: Other

OSB-380000: General runtime error: {0}

Cause: A generic runtime error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem. This error typically occurs when an exception is thrown during the outbound call, but it can also be explicitly raised by the outbound transport implementation, in which case, it may have a customized the message associated with it.

Action: If this is an unexpected error happening on a customized transport, check for unchecked exceptions in outbound call implementation. For other transports, check the documentation corresponding to this error code. Contact Oracle Support Services when this is an OSB runtime internal error.
Level: 1

Type: ERROR

Impact: Other

OSB-380001: Application error: {0}

Cause: An application error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem. Only transports that explicitly declare support for application errors can return such errors. This error is explicitly raised by the transport implementation and usually has a customized message associated with it. It is used by OSB to prevent unnecessary retries.

Action: Check in the transport documentation describing application errors.
Level: 1

Type: ERROR

Impact: Other

OSB-380002: Connection error: {0}

Cause: A connection error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem. This error is raised by the transport implementation and usually has a customized message associated with it. It is used by OSB to put a URI offline.

Action: Check in the transport documentation describing connection errors.
Level: 1

Type: ERROR

Impact: Other

OSB-380003: Exception on {0}, {1}

Cause: An unexpected runtime error has occured in OSB transport subsystem while processing the message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-380004: Version mismatch for service {0}

Cause: The processing of the response message has failed in OSB transport subsystem due to the fact that the configuration for the business service is in flux. This service is unable to send an outbound message until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.
Level: 1

Type: ERROR

Impact: Configuration

OSB-380006: No transport provider registered with ID: {0}

Cause: There is no transport provider deployed on the OSB server for the specified ID

Action: Verify that the transport provider application for that specified ID was correctly deployed on the OSB server. If this happens during server start up, it is also possible that the transport is registered too late. If so, try lowering its deployment order.
Level: 1

Type: ERROR

Impact: Deployment

OSB-380008: Provider with ID {0} does not support proxy service endpoints

Cause: The transport provider configuration does not support inbound endpoints, but somehow the configuration framework tried to create or update an inbound endpoint for that provider

Action: If this is a custom provider, verify that transport provider XML configuration is consistent with the generated endpoint configuration. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-380009: Provider with ID {0} does not support business service endpoints

Cause: The transport provider configuration does not support outbound endpoints, but somehow the configuration framework tried to create or update an outbound endpoint for that provider

Action: If this is a custom provider, verify that the transport provider XML configuration is consistent with the generated endpoint configuration. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-380010: Invalid endpoint configuration: provider specific configuration is missing

Cause: The provider for that endpoint declares a provider specific XML Schema Type but the endpoint configuration contains no provider specific configuration

Action: If this is a custom provider, verify that the provider specific definition is correctly set in the implementation. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-380011: Invalid endpoint configuration: provider specific configuration is not valid

Cause: The endpoint configuration contains a provider specific configuration but the provider for that endpoint does not declare any provider specific XML Schema Type

Action: If this is a custom provider, check that its implementation returns the appropriate schema type corresponding to the provider specific configuration. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-380012: Proxy Service configuration requires exactly one URI

Cause: Proxy Service configuration requires exactly one URI

Action: If this is a custom provider, verify the proxy service configuration is correctly initialized. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-380013: Business Service configuration requires at least one URI

Cause: Business Service configuration requires at least one URI

Action: If this is a custom provider, verify the business service configuration is correctly initialized. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-380014: Invalid endpoint configuration: Provider with ID {0} does not declare application errors

Cause: The endpoint supports application errors but the provider for that endpoint does not

Action: If this is a custom provider, verify that transport provider XML configuration is consistent with the generated endpoint configuration. Otherwise, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-380015: Business Service do not support duplicate URIs. Service {0} found with duplicate URI {1}.

Cause: This error happens during configuration update: the URI of one of the updated Business Service is already used

Action: Delete Business Service or use a different URI
Level: 1

Type: ERROR

Impact: Configuration

OSB-380016: None of the URIs are online for Business service {0}

Cause: The Business service is configured to put URIs offline upon connection errors and there is no online URIs left to route messages sent to this service

Action: Check the service configuration and the server connections
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-380017: Transport configuration xml file is invalid: {0} : {1}

Cause: The transport provider configuration xml file is either syntactically or semantically incorrect. The message body should include the error description and the invalid XML snippet

Action: Correct the configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-380018: Configured service type is not supported by the transport ({0}).

Cause: The configured service type is not supported by the transport ({0}).

Action: If you are trying to import a config jar, your service definition is corrupted, or the current OSB version no longer support the binding defined in the config jar, re-create the service with the new supported binding. For any other reasons, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

OSB-380019: Service transport configuration is in flux: ({0}).

Cause: The service transport configuration is in flux: ({0}).

Action: If you modified your service transport configuration, messages received after the change is committed will be processed normally. For any other reasons, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

OSB-380020: Service ({0}) has been disabled.

Cause: The service ({0}) has been disabled.

Action: Enable the service, messages received after the change is committed will be processed normally. For any other reasons, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

OSB-380103: An unexpected throttling error occurred while processing message sent to business service {0}: {1}

Cause: An internal error occurred in the throttling sub-system. The message body should include the throttled service on which the error occurred and the message describing the problem: this error can be due to a transactional error, interrupted thread exception, timeout or an invalid runtime state

Action: If this is due to an invalid runtime state, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-380500: Exception in {0}, {1}

Cause: An unexpected exception has occurred in OSB Transport subsystem. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-380501: Target not found: {0}

Cause: An unexpected error has occured while deploying or un-deploying a WLS artifact for the specified service. The deployment target {0} is not in the known list of available targets for OSB domain.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-381001: Error encountered while creating the endpoint {0}: {1}

Cause: An unexpected exception occurred in OSB Email transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381002: Unable to find file path {0} for the service endpoint {1}. Current Process may not have access to this file or the file doesn't exist: {2}

Cause: Unable to find the intermediary file path while processing the message. This error may not be fatal and can appear even if the message is successfully processed once. This typically happens if the server is restarted while processing Email transport messages.

Action: Make sure that current user has read, write permission for the given file path location.
Level: 1

Type: ERROR

Impact: Files

OSB-381003: Initialization Error.

Cause: An unexpected exception occured while initializing the Email Transport Provider.

Action: Contact technical support.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381004: Error while parsing or reading the service configuration.

Cause: Service configuration may have been corrupted.

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381005: Could not create or find the file with the path {0} while saving email attachments at location {1}

Cause: File could not be created at this location. current user may not have read, write permission at the given file path location.

Action: Make sure that current user has read, write permission for the given file path location. Please check that file location is valid.
Level: 1

Type: ERROR

Impact: Files

OSB-381006: Error encountered while saving the Email attachments for the email Part with file name {0} at location {1}: {2}

Cause: Email attachments could not be saved due to an unexpected error. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Files

OSB-381007: In address {0}, the port is not a number.

Cause: Port is not a positive integer.

Action: Make sure that port is an integer greater than 0.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381008: Error encountered while creating Internet email address from address, personal name and header encoding as {0}, {1} and {2} respectively: {3}

Cause: An unexpected exception has occurred in Email service endpoint while creating the address. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381009: Error encountered while creating Internet email address from address and header encoding as {0} and {1} respectively: {2}

Cause: An unexpected exception has occurred in Email service endpoint while creating the address. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381010: Could not connect to remote Email server {0} for the service endpoint {1}

Cause: Email proxy service could not connect to the remote email server. Server address may be incorrect or server may be down currently.

Action: Make sure that the service endpoint URI points to the correct Email server address.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381011: Error occured for the service endpoint {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB Email transport. There should be an error message that points to cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381012: Could not delete temporary file {0} for Email Proxy Service: {1}

Cause: File could not be deleted from this location. Current user may not have read, write permission at the given file path location.

Action: Make sure that current user has read, write permission for the given file path location. Please check that file location is valid.
Level: 1

Type: ERROR

Impact: Files

OSB-381013: Error encountered while processing the Inbox messages for Email Proxy Service {0}: {1}

Cause: Error encountered while processing the message after the pipeline is invoked. Post processing may involve moving the message to a different folder or archiving the file.

Action: There should be an error message that points to the cause of the problem.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381014: URI {0} for this proxy service is already used by another proxy service: {1} with same service account.

Cause: An error had occured while registering a new Email proxy service: The URI configured for this proxy service is already used by another Email proxy service. Each Email proxy service has to have a unique URI if the service account is same.

Action: Check the transport configuration for Email proxy service and make sure that combination of URI and the service account is unique.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381015: Error while parsing or reading the Email Endpoint configuration.

Cause: Endpoint configuration may have been corrupted..

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381016: Exception cause {0}: {1}

Cause: An unexpected exception occured.

Action: Contact Oracle Support Services. There should be an error message that points to the cause of the problem.
Level: 1

Type: ERROR

Impact: Other

OSB-381017: Invalid pass by reference is set, it can only be true when the message type is of type XML.

Cause: Pass by reference is configured with non-xml message type Email proxy service.

Action: If Pass by reference is true, Email proxy service should be configured with xml message types.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381018: Given service account {0} is not of static type. Only static service accounts are supported with Email proxy and business services.

Cause: Service account is not of static type.

Action: Make sure that the service account configured in Email proxy or business service is a static service account.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381019: Service account does not exist.

Cause: Service account does not exist.

Action: Make sure that service account with the configured name exists in the OSB project.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381020: Exception encountered while upgrade. There should be an error message that points to the cause of the problem.

Cause: There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-381021: Invalid read limit {0}, it should be greater than or equal to zero.

Cause: Read limit is the number of email messages polled by the Email proxy service in a polling cycle. It should always be greater than or equal to zero.

Action: Make sure that read limit is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381022: Invalid polling interval {0}, it should be greater than zero.

Cause: Email Server is polled for new email messages by the Email proxy service after every poll interval. It should be greater than zero.

Action: Make sure that the polling interval is greater than zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381023: Invalid mail protocol {0}

Cause: Mail protocols supported by Email proxy service are POP3 and IMAP.

Action: Make sure that mail protocol is either POP3 or IMAP.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381024: Folder name is missing for the service configured with IMAP and post read action as Move.

Cause: Folder name is missing for the service configured with IMAP and post read action as Move.

Action: Make sure that folder name is specified in case Email proxy service is configured with IMAP transfer protocol and the post read action as Move.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381025: Download directory is missing.

Cause: Download directory is a required configuration parameter. Email messages are first staged in the download directory before invoking the pipeline.

Action: Make sure that download directory is specified.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381026: Error directory is missing.

Cause: Error directory is a required configuration parameter. Email messages are moved to this directory in case of processing errors.

Action: Make sure that error directory is specified.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381027: Archive directory is missing.

Cause: Archive directory is required in case pass by reference or pass attachments by reference is true.

Action: Make sure that archive directory is specified.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381028: Invalid PostRead option: {0}

Cause: Invalid post read option.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381029: Given encoding is invalid: {0}

Cause: Encoding name is incorrect or the particular encoding is not supported by the Java virtual machine.

Action: Make sure that the Email proxy service is configured with supported encoding.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381030: Neither SMTP resource nor mail session configured.

Cause: Either SMTP resource or mail session should be configured for the Email business service. It must be provided either in transport configuration or as the uri parameter.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381031: Connection timeout can not be negative: {0}.

Cause: Connection timeout is negative.

Action: Make sure that connection timeout is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381032: Reply to address can not be empty if reply to name is specified.

Cause: Reply to address is empty though reply to name is specified.

Action: Make sure that both Reply To Name and Reply to Address fields are defined.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381033: From address can not be empty if from name is specified.

Cause: From address is empty though from name is specified.

Action: Make sure that both From Address and From Name fields are defined.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381034: URI {0} is not valid.

Cause: URI is not formed properly.

Action: Make sure that the URI follows the correct syntax.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381035: Mail session with the jndi name {0} does not exist in the weblogic server instance.

Cause: Service should be configured with the mail session which exists in the weblogic server instance.

Action: Make sure that the mail session exists in the weblogic server instance.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381036: SMTP Ref {0} does not exist.

Cause: SMTP Ref mentioned in URI does exist in OSB

Action: Create the mentioned SMTP ref in OSB
Level: 1

Type: ERROR

Impact: Configuration

OSB-381037: Both Mail session and SMTP server cannot be configured

Cause: Either mail session or smtp server may be configured.

Action: Remove either or mail session or smtp server from the configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381038: Invalid parameter in uri : {0}

Cause: Invalid parameter in the URI. Only mail session and SMTP are valid parameters.

Action: Provide the correct parameter in the uri.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381039: Error while initializing the SSL : {0}

Cause: Error while initializing the SSL

Action: There should be an error message that points to the cause of the problem.
Level: 1

Type: ERROR

Impact: Security

OSB-381040: Destination URI does not exist in resource {0}

Cause: Destination URI does not exist.

Action: Destination URI does not exist in the target resource.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381041: Socket I/O timeout can not be negative: {0}.

Cause: Socket I/O timeout is negative.

Action: Make sure that Socket I/O timeout is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381042: Email Server connection failed with SSL enabled : {0} Trying to connect using TLS

Cause: Either Email Server doesn't support SSL or it may down

Action: Make sure that Email Server Support SSL and it is running
Level: 1

Type: ERROR

Impact: Security

OSB-381043: Failed to establish a TLS Connection : {0} This may be because of trust certificate was not found. Please refer to the documentation for a list of valid locations to store the trust certification

Cause: Either Email Server doesn't support TLS or it may down

Action: Make sure that Email Server Support TLS and it is running
Level: 1

Type: ERROR

Impact: Security

OSB-381101: Error encountered while creating the endpoint {0}: {1}

Cause: An unexpected exception has occurred in OSB FTP transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381102: Service Account Reference is missing in the FTP service configuration.

Cause: Service Account Reference is missing in the FTP service configuration.

Action: Make sure that service account is specified in the FTP service configuration.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381103: Invalid polling interval {0}, it should be greater than zero.

Cause: FTP Server is polled for new files by the Ftp proxy service after every poll interval. It should be greater than zero.

Action: Make sure that the polling interval is greater than zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381104: Error while parsing or reading the Ftp Endpoint configuration.

Cause: Error while parsing or reading the Ftp Endpoint configuration.

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381105: Error occured for the service endpoint: {0}

Cause: An unexpected general purpose exception has occurred in OSB Ftp transport. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-381106: Unable to get file {0} on attempt number {1}: {2}

Cause: Could not retrieve the file.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Files

OSB-381107: Credential not found for alias {0}: {1}

Cause: Credentials could not be retrieved.

Action: Make sure that the credentials with the given name exists in the OSB domain.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381109: File: {0} was read from the remote FTP server: {1} but could not be deleted after processing.

Cause: File read through FTP proxy service could not be deleted. Current user may not have read, write permission.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.
Level: 1

Type: ERROR

Impact: Files

OSB-381111: URI Syntax error for the path {0}: {1}

Cause: URI is not formed properly.

Action: Make sure that the URI follows the correct syntax.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381112: Unable to rename file {1} on the remote host {0} for the service endpoint {2}

Cause: Remote FTP file could not be renamed. Current user may not have read, write permission.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.
Level: 1

Type: ERROR

Impact: Files

OSB-381114: File {1} could not be renamed to {2} on the remote host {0} for the service endpoint {3}: {4}

Cause: Exception encountered while executing renaming the file on the remote FTP server.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.
Level: 1

Type: ERROR

Impact: Files

OSB-381115: File {1} could not be deleted on the remote host {0} for the Ftp proxy service {2}

Cause: Exception encountered while deleting the file on the remote FTP server.

Action: Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.
Level: 1

Type: ERROR

Impact: Files

OSB-381116: URI {0} for this proxy service is already used by another proxy service: {1} with same file mask.

Cause: An error had occured while registering a new Ftp proxy service: The URI configured for this proxy service is already used by another Ftp proxy service. Each Ftp proxy service has to have a unique URI if the file mask is same.

Action: Check the transport configuration for Ftp proxy service and make sure that the combination of URI and the file mask is unique.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381117: Exception in {0}: {1}

Cause: Exception encountered while executing this method. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Other

OSB-381118: Invalid pass by reference is set, it can only be true when the message type is of type XML.

Cause: Pass by reference is configured with non-xml message type Ftp proxy service.

Action: If Pass by reference is true, Ftp proxy service should be configured with xml message types.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381119: Given service account {0} is not of static type. Only static service accounts are supported with FTP proxy and business services.

Cause: Configured service account is not of static type.

Action: Make sure that the service account configured in FTP proxy or business service is a static service account.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381120: Service account {0} does not exist.

Cause: Configured service account does not exist.

Action: Make sure that service account with the configured name exists in the OSB project.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381121: Given encoding {0} is invalid

Cause: Encoding name is incorrect or the particular encoding is not supported by the Java virtual machine.

Action: Make sure that the Ftp proxy service is configured with supported encoding.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381122: Retry count {0} should be greater than zero.

Cause: At the time of polling the FTP server for new files, FTP connection failures are tried for the number of times as specified by retry Count. It should be greater than zero.

Action: Make sure that retry count is greater than zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381123: Invalid socket timeout {0}, it should be greater than or equal to zero.

Cause: Configured socket timeout is invalid.

Action: Make sure that socket timeout is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381124: Invalid read limit {0}, it should be greater than or equal to zero.

Cause: Read limit is the number of message polled by the Ftp proxy service in a polling cycle. It should always be greater than or equal to zero.

Action: Make sure that read limit is greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381125: Archive directory should be specified in case Ftp proxy service is configured with Pass by Reference as true.

Cause: Archive directory is not configured for pass by reference as true.

Action: Make sure that archive directory points to valid file path.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381126: Invalid transfer mode, it should be either binary or ascii.

Cause: Invalid transfer mode.

Action: Make sure that transfer encoding is either binary or ascii.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381150: Directory: {0} creation failed for the endpoint: {1}

Cause: Directory required to generate the ejb endpoints files could not be created.

Action: Check that the OSB process has the permission to create the directory.
Level: 1

Type: ERROR

Impact: Files

OSB-381151: Endpoint {0} could not be initialized: {1}

Cause: Endpoint could not be initialized.

Action: Exception message may point to the cause of the issue.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381152: WSDL generation failed for the Endpoint {0} with exception: {1}

Cause: WSDL generation failed.

Action: Exception message may point to the cause of the issue.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381153: JWS generation failed for the Endpoint {0} with error message(s): {1}

Cause: JWS generation failed.

Action: Error message(s) may point to the cause of the error.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381201: Error encountered while creating the endpoint {0}: {1}

Cause: An unexpected exception has occurred in OSB File transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381202: Could not create the directory: {0}

Cause: Directory with the given path could not be created. Directory path may be incorrect or the current user may not have the permission to create the files at this location.

Action: Make sure that the directory path is correct and the user has permissions to create the files at this location.
Level: 1

Type: ERROR

Impact: Files

OSB-381203: Invalid pass by reference is set, it can only be true when the message type is of XML.

Cause: Pass by reference is configured with non-xml message type File proxy service.

Action: If Pass by reference is true, File proxy service should be configured with xml message types.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381204: Exception in {0}: {1}

Cause: Exception encountered while executing this method. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Other

OSB-381205: Error occured for endpoint {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB File transport. There should be an error message that points to cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381206: URI {0} is not valid.

Cause: URI is not formed properly.

Action: Make sure that the URI follows the correct syntax.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381207: Error occured while performing file operations: {0}

Cause: Message could not be written to the File Business service outbound directory. Current user may not have read, write permission for this location.

Action: Make sure that current user has read, write permission for the given directory path location.
Level: 1

Type: ERROR

Impact: Files

OSB-381208: Error occured while processing inbound file for File Proxy Service {0}: {1}

Cause: File could not be processed due to an unexpected error. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-381209: Poller target server should be specified in case of cluster domain.

Cause: Poller target server should be specified in case of cluster domain.

Action: Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381210: File cannot be moved from location {0} to the stage directory. Current Process may not have permission to do this operation.

Cause: Current user may not have read, write permission for the given file path location.

Action: Make sure that current user has read, write permission for the given file path location.
Level: 1

Type: ERROR

Impact: Files

OSB-381211: Unable to find file path: {0}. Current Process may not have access to this file or the file doesn't exist.

Cause: Unable to find the intermediary file path while processing the message. This error may not be fatal and can appear even if the message is successfully processed once. This typically happens if the server is restarted at the time it is processing some File transport messages.

Action: Make sure that current user has read, write permission for the given file path location.
Level: 1

Type: ERROR

Impact: Files

OSB-381212: URI {0} for this proxy service is already used by another proxy service: {1} with same file mask.

Cause: An error had occured while registering a new File proxy service: The URI configured for this proxy service is already used by another File proxy service. Each File proxy service has to have a unique URI.

Action: Check the transport configuration for File proxy service and make sure that unique value for the URI is used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381213: Could not parse this endpoint configuration.

Cause: Could not parse the endpoint configuration.

Action: Check that the endpoint configuration is formed properly.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-381214: Endpoint-uri and archive directory path can not be the same.

Cause: Endpoint-uri and archive directory path can not be the same.

Action: Make sure that endpoint-uri and archive directory point to the different locations.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381215: Error occured while moving the file to the location {0}: {1}

Cause: File proxy service could not move the file to this location. Current user may not have read, write permission for this location.

Action: Make sure that current user has read, write permission for the given file path location.
Level: 1

Type: ERROR

Impact: Files

OSB-381216: Directory {0} could not be created.

Cause: Directory could not be created with this file path. Current user may not have read, write permission for this location.

Action: Make sure that current user has read, write permission for the given directory path location.
Level: 1

Type: ERROR

Impact: Files

OSB-381217: Error encountered while setting the max read limit size through system property: {0}

Cause: Error encountered while setting the max read limit size through system property. Max read limit size in an integer.

Action: Make sure that the max read limit is an integer.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381218: Directory Couldn't created for the Service Reference: {0}

Cause: Error encountered while creating directory.

Action: Make sure that that permission enabled for directory creation.
Level: 1

Type: ERROR

Impact: Files

OSB-381250: Unexpected error happened in the Transport at {0} due to {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381251: URI "{0}" is not valid for this endpoint.

Cause: The SOA-DIRECT business service is called with URI "{0}". The URI is either empty, or does not conform to the URI format for the SOA-DIRECT transport.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381252: The callback marker URI is not a valid URI.

Cause: The SOA-DIRECT business service is invoked with the callback marker URI, which is not a valid URI at runtime.

Action: there are different ways the URI was set as the callback marker URI: - dynamically overridden in the pipeline - the business service is configured with the marker URI and the pipeline logic did not override it Check the pipeline and/or SOAP headers and make sure the correct URI is configured.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381253: An unexpected error occurred while reading either the MessageID and/or RelatesTo headers: {0}

Cause: An unexpected error occurred while reading either the MessageID and/or RelatesTo headers. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381254: An unexpected error occurred while setting/updating the ReplyTo address: {0}

Cause: An unexpected error occurred while setting/updating the ReplyTo address. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381255: An error occurred while un-marshalling the request message: {0}

Cause: An error occurred while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381256: An error occurred while transforming the payload: {0}

Cause: The Oracle SOA suite is based on the DOM object model. An error occurred while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381257: An unexpected error occurred initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381258: Operation "{0}" is not valid for this endpoint.

Cause: The SOA-DIRECT business service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the configuration of the pipeline to make sure the operation is set and configured with a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381259: Could not invoke proxy service {0} due to {1}

Cause: An Remote Exception happened while trying to invoke the SOA-DIRECT Transport proxy service via RMI

Action: Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists
Level: 1

Type: ERROR

Impact: Other

OSB-381260: An error occurred while marshalling the response message: {0}

Cause: An error occurred while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381261: An error occurred while marshalling the Business fault: {0}

Cause: An error occurred while marshalling the Business fault. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381262: An unexpected error occurred while setting/updating the FaultTo address: {0}

Cause: An unexpected error occurred while setting/updating the FaultTo address. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381263: An unexpected error occurred while checking whether a transaction is running: {0}

Cause: An unexpected error occurred while checking whether a transaction is running. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381264: No callback address for WSA ReplyTo or FaultTo header

Cause: There is no callback address for the WSA callback header: neither the endpoint defines a physical address nor the header defines a callback address.

Action: Set a physical callback address in the transport configuration for this header, or manually add it in the pipeline
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381304: Exception in {0}: {1}

Cause: An unexpected exception has occurred in OSB HTTP transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381316: X.509 token identity assertion is not enabled in the security realm

Cause: An identity asserter with X.509 token support enabled is required because HTTPS inbound endpoint {0} specifies CLIENT-CERT authentication

Action: Enable X.509 identity assertion in your Identity Assertion provider in the security realm pages of the WebLogic Server console
Level: 1

Type: ERROR

Impact: Security

OSB-381317: The X.509 username-mapper sub-plugin of the default identity asserter in not configured

Cause: HTTPS inbound endpoint {0} specifies CLIENT-CERT authentication, therefore the username mapper properties of the default identity asserter must be configured (this is required to support 2-way SSL)

Action: Configure the username-mapper fields of the Default Identity Assertion provider in the security realm pages of the WebLogic Server console
Level: 1

Type: ERROR

Impact: Security

OSB-381318: URI {0} for this proxy service is already used by another proxy service: {1}

Cause: An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service is already used by another HTTP proxy service or WS proxy service. Each HTTP proxy service has to have a unique URI.

Action: Check the transport configuration for HTTP proxy service and make sure that unique value for the URI is used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381319: HTTP business service URLs must start with either http:// or https:// and have a hostname

Cause: An error had occured while registering a new HTTP business service: One of the URLs configured for the business service is invalid. According to RFC 2616, HTTP urls must start with http:// and have a hostname

Action: Check the transport configuration for HTTP business service and make sure that a valid URL is being entered
Level: 1

Type: ERROR

Impact: Configuration

OSB-381320: Cannot create an inbound HTTP endpoint with absolute URI {0}

Cause: An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service is an absolute URI. Only relative URIs are supported for HTTP proxy services.

Action: Check the transport configuration for HTTP proxy service and make sure that only a relative URI (e.g. "/someName") is used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381321: URI {0} for this proxy service is already used by OSB Kernel application

Cause: An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service "/" is already used internal OSB Kernel application.

Action: Check the transport configuration for HTTP proxy service and make sure that a different unique value is used for the URI of this proxy
Level: 1

Type: ERROR

Impact: Configuration

OSB-381322: Failed to add a header named {0}: HTTP headers need to be string, instead {1} was found

Cause: There was a problem while setting specified header name/value pair in outbound HTTP request or inbound response. HTTP transport only allows String header values while another data type was given. One way it could happen is when using transport header action to pass all transport headers through from one transport that supports non-String headers, such as JMS, to HTTP transport

Action: Check the pipeline configuration to make sure only Strings are used to set transport header values of HTTP outbound request or inbound response
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381323: SSL client authentication is not allowed over plain-text HTTP

Cause: The proxy service is configured for client-certificate authentication but it is not an https endpoint. Client-certificate authentication is only allowed over https endpoints

Action: Set the https-required flag to true in the transport configuration page
Level: 1

Type: ERROR

Impact: Security

OSB-381324: Invalid http transport-level authentication configuration: custom token authentication is not supported on business services

Cause: The HTTP transport configuration of this outbound endpoint specifies custom-token authentication. This is not supported in this Oracle Service Bus release

Action: Change the authentication method in the endpoint configuration page
Level: 1

Type: ERROR

Impact: Security

OSB-381326: Invalid http transport-level custom token authentication configuration: header name has not been specified

Cause: Transport-level custom token authentication requires you to specify the name of the HTTP header that will carry the token

Action: Edit the http endpoint configuration details and specify the name of the custom token http header
Level: 1

Type: ERROR

Impact: Security

OSB-381327: Transport-level custom token identity assertion failed

Cause: Transport-level custom token identity assertion failed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381328: Inbound http BASIC authentication failed

Cause: Inbound http BASIC authentication failed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-381329: Inbound SSL client certificate authentication failed

Cause: Inbound SSL client certificate authentication failed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-381330: Outbound HTTP request resulted in failure due to {0} : {1}. Request will be retried

Cause: HTTP request is failed with an application error.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381331: A token-type must be configured when using custom token authentication

Cause: The endpoint is configured for custom token authentication. A token-type must be specified

Action: In the HTTP transport-specific configuration page, choose a token-type from the drop-down list or select a different authentication method
Level: 1

Type: ERROR

Impact: Security

OSB-381332: The name of the HTTP header which carries the custom token must be specified

Cause: The endpoint is configured for custom token authentication. The name of the HTTP header which carries the custom token must be specified

Action: In the HTTP transport-specific configuration page, enter the name of the HTTP header or select a different authentication method
Level: 1

Type: ERROR

Impact: Security

OSB-381333: HTTP method "GET" is only allowed for Service Type any xml or messaging type with none as the request type.

Cause: "GET" method can not be configured for this service. It is allowed only for Service Type of any xml or messaging type with none as the request type.

Action: Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381334: HTTP methods "PUT" and "DELETE" are only allowed for Service Type any xml or messaging type.

Cause: "PUT" and "DELETE" methods can not be configured for this service. It is allowed only for Service Type of any xml or messaging type

Action: Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381335: HTTP method "HEAD" is only allowed for Service Type any xml or messaging type with none as the response type.

Cause: "HEAD" method can not be configured for this service. It is allowed only for Service Type of any xml or messaging type with none as the response type.

Action: Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381336: HTTP business service has no URIs configured.

Cause: Business service is not configured with any URIs.

Action: Check the transport configuration for HTTP business service and make sure that URI set should not be empty.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381337: HTTP business service cannot have both ''chunked streaming mode'' and ''follow HTTP redirects'' options enabled.

Cause: HTTP business service cannot have both ''chunked streaming mode'' and ''follow HTTP redirects'' options enabled.

Action: Check the transport configuration for HTTP business service and make sure that both ''chunked streaming mode'' and ''follow HTTP redirects'' options are not enabled.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381338: Invalid http transport-level authentication configuration: custom authentication is not supported on proxy services

Cause: The HTTP transport configuration of this inbound endpoint specifies custom authentication. This is not supported in this Oracle Service Bus release

Action: Change the authentication method in the endpoint configuration page
Level: 1

Type: ERROR

Impact: Security

OSB-381339: Invalid http transport-level custom authentication configuration: custom authentication class name has not been specified

Cause: Transport-level custom authentication requires you to specify the name of the class that implements the custom authentication.

Action: Edit the http endpoint configuration details and specify the name of the custom authentication class.
Level: 1

Type: ERROR

Impact: Security

OSB-381341: Custom authentication class: "{0}" is not an implementation of "OutboundAuthentication" interface.

Cause: Transport-level custom authentication requires you to specify the name of the class that implements the com.bea.wli.sb.transports.http.OutboundAuthentication interface.

Action: Edit the http endpoint configuration details and specify the name of the class that implements the com.bea.wli.sb.transports.http.OutboundAuthentication interface.
Level: 1

Type: ERROR

Impact: Security

OSB-381342: Custom authentication class: "{0}" is not available in the system classpath.

Cause: Could not find custom authentication class in system classpath.

Action: Please make sure that the Custom authentication class: "{0}" is available as part of the system classpath.
Level: 1

Type: ERROR

Impact: Security

OSB-381343: Rejecting a non HTTP POST request due to WS-I compliance rules for service with context path {0} .

Cause: Non HTTP POST request is rejected due to WS-I compliance rules.

Action: Rejecting a non HTTP POST request due to WS-I compliance rules. User should send a POST request the service.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381401: Exception in {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB WS transport. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-381404: One or more endpoint URLs in this WS transport business service are plain HTTP URLs but policy requires the HTTPS protocol

Cause: This endpoint's policy requires HTTPS access. All URLs in this endpoint must use the HTTPS protocol

Action: Edit the endpoint URLs to make sure all URLs use the HTTPS protocol
Level: 1

Type: ERROR

Impact: Configuration

OSB-381405: URI {0} for this proxy service is already used by OSB Kernel application

Cause: An error had occured while registering a new WS proxy service: The URI configured for this proxy service "/" is already used by internal OSB Kernel application.

Action: Check the transport configuration for WS proxy service and make sure that a different unique value is used for the URI of this proxy.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381406: Cannot create an inbound WS endpoint with absolute URI {0}

Cause: An error had occured while registering a new WS proxy service: The URI configured for this proxy service is an absolute URI. Only relative URIs are supported for WS proxy services.

Action: Check the transport configuration for WS proxy service and make sure that only a relative URI (e.g. "/foo") is used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381407: URI {0} for this proxy service is already used by another proxy service: {1}

Cause: An error had occured while registering a new WS proxy service: The URI configured for this proxy service is already used by another WS proxy service or HTTP proxy service. Each WS proxy service has to have a unique URI.

Action: Check the transport configuration for WS proxy service and make sure that unique value for the URI is used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381408: WS business service should always have absolute URI. Given URI is not absolute: {0}

Cause: WS business service should have absolute URIs.

Action: Change the WS business service configuration and make sure that all the URIs should be absolute.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381409: WS outbound services can only have http and https schemes. Given URI has invalid scheme:{0}

Cause: An error occurred while registering new WS business service: WS business services can only have http and https schemes.

Action: Change the scheme of the WS business service to http or https.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381410: The ws-policy of the WS business service requires HTTPS BASIC authentication but no service account has been configured

Cause: An HTTPS BASIC authentication policy requires the endpoint to send a username/password when connecting to the back-end service. A service account specifies how to get the username/password and allows the endpoint to get the username/password. This endpoint is configured for outbound HTTPS BASIC authentication but the service account reference is null.

Action: Configure a service account reference in the endpoint configuration page.
Level: 1

Type: ERROR

Impact: Security

OSB-381411: An entry with key:{0} is timed out in WsCorrelationTable.

Cause: While invoking a WS business service, a response to a WS request did not arrive in before the specified response timeout occurred.

Action: Check that WS business service or the target webservice is functioning properly and increase the response timeout value if necessary.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381412: An error occured while sending the message reliably to the target reliable webservice.

Cause: Reliable delivery failure has occurred while sending the message to the target reliable webservice. This failure might be because of Sequence timeout, inactivity timeout, authentication/authorization failures or bad certificate errors etc.

Action: Check that WS business service or the target webservice is functioning properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381413: URI:{0} of WS proxy service has '/' at the end.

Cause: WS proxy services should not have an ending '/' in URI.

Action: Remove the ending '/' in the URI of the WS proxy service.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381414: Attempting an indirect send to a WS transport proxy which requires BASIC authentication ({0}). Proxy-to-proxy routing and test console access are not allowed with this pattern

Cause: WS transport proxy services which require username/password (i.e. BASIC) authentication cannot be invoked from another proxy or from the test console.

Action: Check the message flow configuration and make sure there are no proxy-to-proxy routes where the target proxy service is a WS transport endpoint with BASIC authentication. Also, whenever using the test console to test such a WS transport proxy, make sure you set the "direct call" check-box to true.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381415: X.509 token identity assertion is not enabled in the security realm. An identity asserter with X.509 token support enabled is required because ws proxy service "{0}" has a ws-policy which requires CLIENT-CERT authentication

Cause: An identity asserter with X.509 token support enabled is required whenever the ws-policy requires CLIENT-CERT authentication

Action: Enable X.509 identity assertion in your Identity Assertion provider in the security realm pages of the WebLogic Server console
Level: 1

Type: ERROR

Impact: Security

OSB-381416: The X.509 username-mapper sub-plugin of the default identity asserter in not configured. The username-mapper is required because ws proxy service "{0}" has a ws-policy which requires CLIENT-CERT authentication

Cause: An identity asserter with X.509 token support enabled and username-mapper plugin enabled is required whenever the ws-policy requires CLIENT-CERT authentication (this is required to support 2-way SSL)

Action: Configure the username-mapper fields of the Default Identity Assertion provider in the security realm pages of the WebLogic Server console
Level: 1

Type: ERROR

Impact: Security

OSB-381417: WS transport proxy "{0}" is configured with client-certificate-required policy and is deployed in a cluster. There is typically a load-balancer between the client and the cluster. The load balancer forwards client-certificates to the server, but the server will only honor this certificate if it is configured with "Client Cert Proxy Enabled", otherwise the certificate will be ignored and the request will fail.

Cause: Typically, when a WS transport proxy is configured with client-certificate-required policy and is deployed in a cluster, the managed servers must be configured with "Client Cert Proxy Enabled". This is so that the managed servers will honor the certificate in the "WL-Proxy-Client-Cert" HTTP header. Make sure to read the section on SSL configuration in WebLogic Server documentation when using this feature.

Action: Set "Client Cert Proxy Enabled" to true in the WLS console. This can be done at the cluster level or individually for each managed server in the cluster. Make sure to read the section on SSL configuration in WebLogic Server documentation when using this feature. Use a weblogic.security.net.ConnectionFilter to ensure that this WebLogic Server instance accepts connections only from the machine on which the proxy-server plugin is running, otherwise you will create a security vulnerability because the WL-Proxy-Client-Cert header can be spoofed.
Level: 1

Type: ERROR

Impact: Security

OSB-381418: Unexpected failure while processing an incoming message for endpoint {0}

Cause: There was an unexpected error while processing an inbound message by specified WS proxy service.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-381419: WS business service URLs must start with either http:// or https:// and have a hostname

Cause: An error had occured while registering a new WS business service: One of the URLs configured for the business service is invalid. According to RFC 2616, HTTP urls must start with http:// and have a hostname.

Action: Check the transport configuration for WS business service and make sure that a valid URL is being entered.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381422: Sending the failed request message to error queue is failed for service: {0} with error : {1}

Cause: Error queue configured for the service may not be available or it may not be accepting the messages from OSB as the security credentials do not match.

Action: Make sure configured error queue is available and provide right credentials to the service.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381450: An unexpected error occured initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-381451: An error occured while accessing the credentials for the JNDI connection: {0}

Cause: An error occured while accessing the credentials for the JNDI connection. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-381452: The Oracle BPEL delivery service could not be accessed: {0}

Cause: An error occured while doing the lookup of the delivery service to the Oracle BPEL Process Manager.

Action: Make sure the target Oracle BPEL Process Manager is running, that the host and port are correctly configured and that the business service has the correct credentials.
Level: 1

Type: ERROR

Impact: Process

OSB-381453: Operation "{0}" is not valid for this endpoint.

Cause: The BPEL business service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the configuration of the pipeline to make sure the operation is set and configured with a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381454: URI "{0}" is not valid for this endpoint.

Cause: The BPEL business service is called with URI "{0}". The URI is either empty, or does not conform to the URI format for the BPEL transport.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381455: The callback marker URI is not a valid URI.

Cause: The BPEL business service is invoked with the callback marker URI, which is not a valid URI at runtime.

Action: There are different ways the URI was set as the callback marker URI: - dynamically overridden in the pipeline - the business service is configured with the marker URI and the pipeline logic did not override it Check the pipeline and/or SOAP headers, and make sure the correct URI is configured.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381456: An error occured while transforming the payload: {0}

Cause: The Oracle BPEL PM is based on the DOM object model. An error occured while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381457: An error occured while un-marshalling the request message: {0}

Cause: An error occured while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381458: An error occured while marshalling the response message: {0}

Cause: An error occured while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381459: An error occured while marshalling the BPEL fault: {0}

Cause: An error occured while marshalling the BPEL fault. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381460: An unexpected error occured while setting/updating the ReplyTo address: {0}

Cause: An unexpected error occured while setting/updating the ReplyTo address. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381461: An unexpected error occured while reading either the MessageID and/or RelatesTo headers: {0}

Cause: An unexpected error occured while reading either the MessageID and/or RelatesTo headers. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381462: The protocol "{0}" does not support transaction propagation.

Cause: The protocol "{0}" does not support transaction propagation.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381463: An unexpected error occured while checking whether a transaction is running: {0}

Cause: An unexpected error occured while checking whether a transaction is running. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381464: An unexpected error occured trying to suspend the transaction: {0}

Cause: An unexpected error occured trying to suspend the transaction. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381465: An unexpected error occured trying to resume the transaction: {0}

Cause: An unexpected error occured trying to resume the transaction. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381502: Exception in {0}: {1}

Cause: An unexpected general purpose exception has occurred in OSB JMS transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381506: Unexpected type of message received: {0}

Cause: A non Text or Bytes or Object message was received by JMS proxy service or as a response to JMS business service. OSB JMS transport only supports Text, Bytes and Object messages.

Action: Make sure only JMS Text or Bytes messages are being sent to OSB JMS proxy or business services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381510: Error writing jar file: {0}

Cause: There was an unexpected error while generating JMS service-related artifacts. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381511: Unexpected failure while processing an incoming message for endpoint {0}

Cause: There was an unexpected error while processing an inbound message by specified JMS proxy service. This may have happened due mis-configuration of the service

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381512: JMS Endpoint with name {0} already registered

Cause: There was an unexpected error at session activation time while registering a new JMS service. Two or more JMS services share the same name.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381513: The URIs for request and response may not be equal

Cause: In the configuration for the JMS proxy service the request and response URIs are the same. Such configuration is not legal as it will most likely result in an infinite loop and request/response processing.

Action: Make sure that request and response URIs have different values in JMS proxy service configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381514: Service binding(SOAP/XML/WSDL) has request/response operations but JMS transport configuration does not have any response information.

Cause: Service binding(SOAP/XML/WSDL) has request/response operations but JMS transport configuration does not have any response information.

Action: Make sure that the JMS transport configuration of the service is consistent with declared service binding type.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381515: Invalid target for JMS proxy: {0}

Cause: The target configured for JMS proxy service is not valid in the current cluster configuration. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381517: URI {0} for this proxy service is already used by another proxy service: {1} with no message selector

Cause: Two or more JMS proxy services are using the same URI. The operation cannot be completed because only a single JMS proxy is allowed to receive messages from a given JMS destination.

Action: Make sure that the given JMS proxy is the only one that is configured with the URI in question.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381518: The generated MDB EAR file name {0} for service {1} is already used by another service. Please change the name this service to avoid a collision.

Cause: There was an unexpected error while OSB was generating JMS service-related artifacts.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381519: Failure while processing an incoming message for endpoint {0} due to service configuration in flux

Cause: The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy service is in flux. This proxy is unable to process messages until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381520: Connection factory {0} does not exist!

Cause: OSB JMS transport failed to look up the configured JMS connection factory for the service with JMSMessageID response pattern in specified JNDI provider at service activation time

Action: Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381521: The response destination is null or is not a queue

Cause: The JMS destination configured for response is not a queue. Only JMS queues are supported destinations for responses to JMS proxy services.

Action: Check that the JMS response URI configured in JMS proxy service refers to a JMS queue.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381522: The JMS URI {0} is not valid

Cause: One or more of the URIs configured for JMS service is not in the format expected by OSB. The expected format is jms://host:port[,host:port]*/MyFactory/MyQueue where - host is the name of the server that is the JNDI provider - port is the port of the server that is the JNDI provider - MyFactory is the JNDI name of the connection factory - MyQueue is the JNDI name of the JMS destination

Action: Make sure that the URI string conforms to the expected format
Level: 1

Type: ERROR

Impact: Configuration

OSB-381523: The server name {0} is not configured in the table of response JNDI destinations

Cause: There was one or more missing target that corresponds to a managed server that is part of OSB cluster domain in the map of destinations JMS service that uses JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381524: response destination for {0} not found in table of response JNDI destinations

Cause: There was one or more missing destination that corresponds to a managed server that is part of OSB cluster domain in the map of destinations JMS service that uses JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381525: Cannot re-use the same destination {0} for {1}; use unique response destination for each managed server

Cause: There were two or more identical destination names configured for two different managed servers for JMS service with JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another.

Action: Make sure that each managed server name corresponds to a unique JMS destination name in JMS transport configuration for the service
Level: 1

Type: ERROR

Impact: Configuration

OSB-381526: Response JNDI Names map not found for JMSMessageID response pattern

Cause: There was a problem with the configuration of JMS service with JMSMessageID correlation pattern. The configuration is missing a required element that specifies the map of destinations for a set of managed servers.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381527: Service Account {0} is not static. Only static service accounts are supported with JMS proxies and business services.

Cause: The service account used in the configuration of JMS service is not a static account (i.e. either pass-through or mapped). Only static service accounts are supported with JMS proxies and business services

Action: Check that the type of the service account used in the configuration of the service and make sure only static accounts are used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381528: Attempting an indirect send to a proxy using the JMSMessageID response pattern. Proxy-to-proxy routing not allowed with this pattern.

Cause: Sending an outbound message from a proxy that routs to a JMS proxy with JMSMessageID response pattern is not supported

Action: Check the message flow configuration for the proxy and make sure it does not route to a JMS proxy that uses JMSMessageID response pattern
Level: 1

Type: ERROR

Impact: Configuration

OSB-381529: Transaction associated with message id {0} has failed due to status: {1}

Cause: A transaction has failed while waiting for response for JMS request/response service. As a result, any related response message will be ignored.

Action: Examine the log files to determine that cause of the transaction failure and/or retry sending the request. If the problem persists, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381530: Failed to lookup connection factory {0}

Cause: OSB JMS transport failed to look up the configured JMS connection factory in specified JNDI provider at service activation time

Action: Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381531: Inbound response will not be sent due to inbound request transaction status: {0}

Cause: A response to JMS proxy service will not be sent due to the fact that the transaction associated with the inbound request has failed due to stated reason.

Action: Examine the log files to determine that cause of the transaction failure and/or retry sending the request. If the problem persists, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381533: {0} already exists and is not a Queue

Cause: The destination specified in JMS Transport configuration already exists and is not a JMS Queue.

Action: Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a queue in JMS transport page and an object with the specified JNDI name exists, it is expected to be a Queue
Level: 1

Type: ERROR

Impact: Configuration

OSB-381534: {0} already exists and is not a Topic

Cause: The destination specified in JMS Transport configuration already exists and is not a JMS Topic.

Action: Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a topic in JMS transport page and an object with the specified JNDI name exists, it is expected to be a Topic
Level: 1

Type: ERROR

Impact: Configuration

OSB-381535: {0} already exists and is not a TopicConnectionFactory

Cause: The connection factory specified in JMS Transport configuration already exists and is not an instance of JMS TopicConnectionfactory. Since the configured destination type is a topic, one needs to provide an instance of valid TopicConnectionFactory in the configuration

Action: Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a topic in JMS transport page and an object with the specified JNDI name exists, it is expected to be a TopicConnectionFactory
Level: 1

Type: ERROR

Impact: Configuration

OSB-381536: {0} is not a proxy service"

Cause: An unexpected error has occured during UDDI export of JMS services. The JMS service being exported was expected to be a proxy and was not.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381537: JMS provider-specific configuration was not specified

Cause: There was an unexpected error processing the message while parsing the JMS transport-specific configuration of the service endpoint

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381538: Request metadata XML must be an instance of {0}

Cause: There was an unexpected error processing the message while processing request metadata for the inbound or outbound request.

Action: Check the pipeline actions in your message flow and make sure that you are setting the request metadata in way that is consistent with the transport specified for the service. One can use Log actions to examine the contents of any message context variable.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381539: Response metadata XML must be an instance of {0}

Cause: There was an unexpected error processing the message while processing response metadata for the inbound or outbound request.

Action: Check the pipeline actions in your message flow and make sure that you are setting the response metadata in way that is consistent with the transport specified for the service. One can use Log actions to examine the contents of any message context variable.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381546: Unexpected JMS Object type of message received for service other than messaging service with sub-type 'Java'

Cause: A JMS Object type of message was received by JMS proxy service or as a response to JMS business service for service other than messaging service with sub-type 'Java'. Messages should be of type Text or Bytes.

Action: Make sure only JMS Text or Bytes messages are being sent to OSB JMS proxy or business services for service other than messaging service with sub-type 'Java'.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381547: Unexpected type of message: {0} received for service configured as messaging service with sub-type 'Java'

Cause: A Text or Bytes message was received by JMS proxy service or as a response to JMS business service for service configured as messaging service with sub-type 'Java'. Messages should be of type Object.

Action: Make sure only JMS Object messages are being sent to OSB JMS proxy or business services for service configured as messaging service with sub-type 'Java'.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381548: Service binding with response type 'Java' configured with incompatible response message type in the JMS transport configuration

Cause: The configuration of the JMS service was not compatible with the declared service binding type. A messaging service with 'Java' response type should not have a response message type configured in the JMS transport configuration. In this case, Object type of messages are sent as the response.

Action: Make sure that the JMS transport configuration should not have a response message type configured in the JMS transport configuration.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381549: Service binding with request type 'Java' configured with incompatible message type in the JMS transport configuration

Cause: The configuration of the JMS service was not compatible with the declared service binding type. A messaging service with 'Java' request type should not have a message type configured in the JMS transport configuration. In this case, Object type of messages are sent by the business service.

Action: Make sure that the JMS transport configuration should not have a message type configured in the JMS transport configuration.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381550: Payload from the pipeline not received with one java object

Cause: A message with java object should contain one java object.

Action: Make sure that the message contains only one java object.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381551: Response message type is not configured in service binding but JMS transport has response configuration.

Cause: The configuration of the JMS service is not compatible with the declared service binding type. JMS transport should not have response configuration as the service messaging type does not have any response.

Action: Make sure that the JMS transport configuration of the service is consistent with declared service binding type.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381552: Response message type is configured in service binding but JMS transport does not have any response configuration.

Cause: The configuration of the JMS service is not compatible with the declared service binding type. JMS transport should have response configuration as the service messaging type has response.

Action: Make sure that the JMS transport configuration of the service is consistent with declared service binding type.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381553: An update to proxy service {0} failed while modifying its deployment ear file, {1}.

Cause: An update to the JMS proxy service failed while updating its deployment ear file. Either the old version of the ear file could not be deleted or renaming the new ear file failed.

Action: Make sure that the named ear file exists in the sbgen subdirectory of the domain. If not, the service should be deleted and re-added to force the generation of a new ear file.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381558: Proxy-to-proxy routing not allowed with this configuration: JMSCorrelationID response pattern and JMS_NO_MDB_FOR_RESPONSE=true.

Cause: When JMS_NO_MDB_FOR_RESPONSE property is set to true for a JMS proxy service, a default MDB will not be generated on inbound response queue, therefore, no response message will be received.

Action: Check the message flow configuration for the proxy and make sure it does not route to a JMS proxy that uses JMSCorrelationID response pattern combined with JMS_NO_MDB_FOR_RESPONSE property set to true.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381601: Error encountered while putting the message in the queue for the service endpoint {0}: {1}

Cause: Message may not be processed as there was an unexpected error while putting the message in the task queue. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381602: Error encountered while polling the resource for the service endpoint {0}: {1}

Cause: Unexpected exception happened at the time of polling the external resource. There should be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381603: Error occured while polling the resource for the service endpoint {0}. Polling will be stopped: {1}

Cause: An unexpected exception occured at the time of polling the external resource. There should be an error message that points to the cause of the problem. This is a fatal error and may stop the polling of external resource.

Action: Reactivate the service or restart the server.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381604: Error while initializing the Transport Provider {0}: {1}

Cause: An unexpected exception occured while initializing the Transport Provider. There may be an error message that points to the cause of the problem.

Action: There may be an error message that points to the cause of the problem.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381606: Error encountered while executing the task from PolledMessageListener MDB.

Cause: An unexpected exception occured while passing the message to the pipeline. There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381607: Error encountered while parsing the transport provider configuration file {0}: {1}

Cause: Error encountered while parsing the transport provider configuration file

Action: Contact technical support.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381611: Poller target server should be specified in case of cluster domain.

Cause: Poller target server should be specified in case of cluster domain.

Action: Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381612: Poller target server should belong to one of the managed servers in the OSB cluster domain.

Cause: Poller target server should belong to one of the managed servers in the OSB cluster domain.

Action: Make sure that the File proxy configuration has one of the managed servers as poller target server if it is running in the cluster.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381613: Service endpoint {0} activation failed: {1}

Cause: Service endpoint could not be activated due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381614: Service endpoint {0} could not be resumed: {1}

Cause: Service endpoint could not be resumed due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Deployment

OSB-381651: Exception in {0}, {1}

Cause: An unexpected general purpose exception has occurred in OSB local transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381652: Local Proxy Services cannot have URIs

Cause: An invalid configuration has been found for a local proxy service during new service registration due to the presence of URIs. Local proxy services cannot be associated with any URIs.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381653: Only local proxy services are supported

Cause: An invalid configuration has been found for a local service during new service registration. Only proxy services are supported for local transport.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381700: Exception in {0}, {1}

Cause: An incoming Tuxedo request encountered a problem. See the error accompanying this message for more details

Action: Consult the Weblogic Server log for more details on the problem and contact Customer Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381701: Request failed. {0}

Cause: The Tuxedo call failed. The Tuxedo invocation encountered an error. Please refer to the accompanying message for more details.

Action: Verify the WTC configuration, remote Tuxedo configuration or see the local and remote logs for possible system or application errors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381750: Unexpected error happened in the SB Transport at {0} due to {1}

Cause: An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing

Action: If this error happened during a configuration update, check that your SB transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-381751: Could not create connection with proxy service {0} due to {1}

Cause: An error happened while trying to lookup the SB Transport proxy service RMI stubs

Action: Verify that your JNDI context host, port and credentials are correct. Also check that protocol used by the JNDI context is supported and enabled. For instance, IIOP/IIOPS protocols are not supported between WebLogic Server, and HTTP/HTTPS protocols requires HTTP tunneling.
Level: 1

Type: ERROR

Impact: Other

OSB-381752: Could not invoke proxy service {0} due to {1}

Cause: An Remote Exception happened while trying to invoke the SB Transport proxy service via RMI

Action: Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists
Level: 1

Type: ERROR

Impact: Other

OSB-381753: Could not generate plan {0} due to {1}

Cause: An internal error occurred while creating a proxy services with a custom dispatch policy. The deployment plan for this proxy artifact could not be created

Action: The message body should give you more details about the error. This could be caused by a I/O Exception or because the location of the deployment plan write-protected.
Level: 1

Type: ERROR

Impact: Other

OSB-381754: Unsupported payload type {0}

Cause: An internal error occurred during the message processing: the payload associated with the message is not supported by the SB Transport

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381755: Operation "{0}" is not valid for this endpoint.

Cause: The SB Proxy service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the client configuration to make sure the operation is set and configured with a valid value.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381756: An unexpected error occured initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-381757: An error occured while marshalling the response message: {0}

Cause: An error occured while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381758: An error occured while transforming the payload: {0}

Cause: The Oracle SOA suite is based on the DOM object model. An error occured while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381759: An error occured while un-marshalling the request message: {0}

Cause: An error occured while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381801: Error occured for endpoint {0}

Cause: Error occured for endpoint. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381802: Could not read file : {0} for Endpoint {1}:

Cause: The given file is not available or does not have read permissions

Action: Please verify the location of the file and check the read permissions
Level: 1

Type: ERROR

Impact: Other

OSB-381803: Unable to get file : {0} on attempt number : {1} :

Cause: Either the remote file does not exist or does not have read permissions

Action: Please check that the remote file exist and have read permissions
Level: 1

Type: ERROR

Impact: Other

OSB-381804: Credential not found for alias :{0} :

Cause: In case of ServiceAccount this may happen if the ServiceAccount does exist or it does not have any username password. In case of ServiceKeyProvider this may happen if the service key provider does not exist or does not have a key-pair for SSL client authentication

Action: In case of ServiceAccount, please verify if the username-password exists. In case of ServiceKeyProvider, please verify if the Key-Pair exists.
Level: 1

Type: ERROR

Impact: Other

OSB-381805: File: {0} moved to error directory path: {1}

Cause: Due to the error file could not be transferred to the destination. File is finally moved to the error directory after the retries mentioned in the business service. This could happen if the destination is not reachable or if the destination directory does not have permission to write the file.

Action: Please verify if the destination is reachable and it has the permissions to write the file.
Level: 1

Type: ERROR

Impact: Other

OSB-381807: URI Syntax error for the path : {0}

Cause: URI Syntax error occured due to Invalid URI provided.

Action: Please verify the syntax of the URI
Level: 1

Type: ERROR

Impact: Other

OSB-381808: Unable to rename file : {1} on remote host : {0} for endpoint :{2}

Cause: Error occured during file rename. This may happen if the file is not accessible, destination does not exist or does not have permissions to the destination directory.

Action: Please verify if the file exists and is accessible. For the destination directory, verify if the destination directory exists and has write permission to the destination directory.
Level: 1

Type: ERROR

Impact: Other

OSB-381810: File : {1} could not be renamed to {2} on remote host : {0} for endpoint :{3}

Cause: Error occured while renaming the file on the remote Host. It may happen if the remote destination is not accessible or if it does not have permissions to write the file.

Action: Please verify if the remote directory exists and is accessible. Ensure that it has necessary write permissions to put a file.
Level: 1

Type: ERROR

Impact: Other

OSB-381811: File : {1} could not be deleted on remote host : {0} for endpoint :{2}

Cause: File could not be delete on the remote Host. It may happen if the user does not have necessary permissions to delete the file or if the file is not accessible.

Action: Please ensure that the file is accessible and user has necessary permissions to delete the file.
Level: 1

Type: ERROR

Impact: Other

OSB-381812: File : {0} was read from remote server :{1} but unable to delete

Cause: File was read but it could not be deleted. It may happen when the client does not have permissions to delete the file.

Action: Please verify if the client has permissions to delete the file.
Level: 1

Type: ERROR

Impact: Other

OSB-381813: Could not parse this endpoint configuration.

Cause: Endpoint configuration could not be parsed.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

OSB-381814: Pass by reference can be true only when the message is of type XML.

Cause: Pass by reference can be true only when the message is of type XML.

Action: Do not use pass by reference when the message is not XML type
Level: 1

Type: ERROR

Impact: Other

OSB-381815: URI {0} for this proxy service is already used by another proxy service: {1} with same file mask.

Cause: The same URI and file mask is already in use by some other service.

Action: Change the URI or the file mask of one of the service to avoid this conflict.
Level: 1

Type: ERROR

Impact: Other

OSB-381816: Invalid polling interval, it should be greater than zero:{0}.

Cause: Invalid polling interval, it should be greater than zero.

Action: Please provide a valid polling interval, greater than zero.
Level: 1

Type: ERROR

Impact: Other

OSB-381817: Retry count should be greater than zero:{0}

Cause: Invalid Retry count provided.

Action: Please provide a valid Retry count greater than zero.
Level: 1

Type: ERROR

Impact: Other

OSB-381818: Timeout should be greater than zero.:{0}

Cause: Invalid timeout provided.

Action: Please provide a valid timeout greater than zero.
Level: 1

Type: ERROR

Impact: Other

OSB-381819: Invalid read limit, it should be greater than or equal to zero:{0}

Cause: Invalid read limit provided

Action: Please provide a valid read limit greater than or equal to zero.
Level: 1

Type: ERROR

Impact: Other

OSB-381820: Archive dir is invalid:{0}

Cause: Invalid Archive directory location

Action: Please verify the archive directory location provided.
Level: 1

Type: ERROR

Impact: Other

OSB-381821: Given encoding is invalid:{0}

Cause: Invalid encoding is provided

Action: Please verify the encoding provided.
Level: 1

Type: ERROR

Impact: Other

OSB-381822: ServiceAccountRef does not exist.

Cause: ServiceAccountRef does not exist.

Action: Please verify the ServiceAccount provided.
Level: 1

Type: ERROR

Impact: Other

OSB-381823: Given Service-Account:{0} is not of static type. Only static service accounts are supported with SFTP proxy and business services.

Cause: The given Service Account is not valid, SFTP service only works with static Service Accounts.

Action: Please use a Static Service Account for SFTP service.
Level: 1

Type: ERROR

Impact: Other

OSB-381824: Service account "{0}" does not exist.

Cause: Service Account does not exist

Action: Please verify the Service Account used for the service
Level: 1

Type: ERROR

Impact: Other

OSB-381825: Exception {1}

Cause: Exception occured in transport

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Other

OSB-381826: Key Not Found for host {0}

Cause: Public key of the remote SFTP server is not found in known_hosts file.

Action: Please verify the Public key of SFTP server exists in known_hosts file in the desired format.
Level: 1

Type: ERROR

Impact: Other

OSB-381827: Key Mismatch for host {0}

Cause: Public key for the SFTP server present in the known_hosts file does not match with the key exchanged with the server. The mismatch may happen if the Public Key of the SFTP server is updated on the server but the known_hosts file contains the old key. It may also happen if the Public key is not present for the algorithm used.

Action: Please verify the Public Key of the SFTP server in the known_hosts file. Update the known_hosts with the latest Public Key of the server.
Level: 1

Type: ERROR

Impact: Other

OSB-381828: SFTPClientException occured, message is :: {0}

Cause: SFTPClientException occured. The exception message should provide more detail.

Action: No action required
Level: 1

Type: ERROR

Impact: Other

OSB-381831: Archive file {0} does not exist.

Cause: Archive file does not exist or is not accessible

Action: Please verify that the archive location exists and has read-write permissions.
Level: 1

Type: ERROR

Impact: Other

OSB-381832: Local file {0} does not exist.

Cause: Local file does not exist in the download directory or does not have read permissions

Action: Please verify the download directory location and check for read permissions
Level: 1

Type: ERROR

Impact: Other

OSB-381833: Error in renaming file {0} to {1}

Cause: Error is renaming file to destination directory

Action: Please verify that the destination directory is accessible
Level: 1

Type: ERROR

Impact: Other

OSB-381834: End point does not exists for service {0}

Cause: EndPoint does not exist for the given service.

Action: Contact Oracle support
Level: 1

Type: ERROR

Impact: Other

OSB-381835: Service Key Provider Ref does not exist

Cause: Service Key Provider Ref does not exist

Action: Contact Oracle support
Level: 1

Type: ERROR

Impact: Other

OSB-381836: Key Pair not found for ref : {0}

Cause: Key Pair not found for ref.

Action: Contact Oracle support
Level: 1

Type: ERROR

Impact: Other

OSB-381837: Hostname in known_hosts file is null or blank

Cause: Bad known_hosts file format

Action: Fix the hostname in known_hosts and check for any extra spaces
Level: 1

Type: ERROR

Impact: Other

OSB-381838: Algorithm specified in known_hosts is null or blank. It should be ssh-rsa or ssh-dss

Cause: Bad known_hosts file format

Action: Fix the algorithm name in known_hosts
Level: 1

Type: ERROR

Impact: Other

OSB-381839: Bad Algorithm name "{0}", it should be ssh-rsa or ssh-dss.

Cause: Bad known_hosts file format

Action: Specify the correct algorithm name in known_hosts
Level: 1

Type: ERROR

Impact: Other

OSB-381840: Public key specified in known_hosts is null or blank.

Cause: Bad known_hosts file format

Action: Specify the correct public key in known_hosts and check for any extra spaces
Level: 1

Type: ERROR

Impact: Other

OSB-381841: known_hosts file does not exist or it does not have read permissions.

Cause: Known_hosts file not accessible

Action: Create the known_hosts file and provide read permissions
Level: 1

Type: ERROR

Impact: Other

OSB-381842: Invalid key specified for Host "{0}", it is not a {1} key

Cause: Wrong algorithm name specified for the key in known_hosts

Action: Specify the correct algorithm name for the key in known_hosts
Level: 1

Type: ERROR

Impact: Other

OSB-381843: Bad known_hosts file, there should be no space in "HOST,IP"

Cause: Found space in "HOST,IP" in known_hosts file

Action: Remove any space in "HOST,IP" in known_hosts file
Level: 1

Type: ERROR

Impact: Other

OSB-381901: Exception in {0}, {1}

Cause: An unexpected general purpose exception has occurred in OSB MQ transport. There should be an error message that points to cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-381904: Unexpected type of message received: {0}

Cause: An unexpected message type received.

Action: Make sure only MQ Text or Bytes messages are being sent to OSB JMS proxy or business services.
Level: 1

Type: ERROR

Impact: Data

OSB-381905: The URIs for request and response may not be equal

Cause: In the configuration for the MQ proxy service the request and response URIs are the same. Such configuration is not legal as it will most likely result in an infinite loop and request/response processing.

Action: Make sure that request and response URIs have different values in MQ proxy service configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381906: URI {0} for this proxy service is already used by another proxy service: {1}

Cause: Two or more MQ proxy services are using the same URI. The operation cannot be completed because only a single MQ proxy is allowed to receive messages from a given MQ destination.

Action: Make sure that the given MQ proxy is the only one that is configured with the URI in question.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381907: The URI {0} is not valid

Cause: One or more of the URIs configured for MQ service is not in the format expected by OSB. The expected format is mq://host:port?conn=MyOSBProject/MyMQConnectionResource

Action: Make sure that the URI string conforms to the expected format
Level: 1

Type: ERROR

Impact: Configuration

OSB-381908: Failed to lookup MQ Connection Resource {0}

Cause: Failure when trying to lookup MQ Connection Resource specified in the URI of the service. The MQ connection resource specified in the URI may not exist.

Action: Please ensure that the MQ connection resource specified in the URI exists.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381909: Service binding is incompatible with transport configuration (response message type)

Cause: The configuration of the MQ service was not compatible with the declared service binding type. For example, a messaging service with non-'None' response type has to have a response destination configured in MQ transport configuration.

Action: Make sure that the MQ transport configuration of the service is consistent with declared service binding type.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381911: Endpoint: {0} activation failed.

Cause: Service endpoint could not be activated due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381912: Endpoint: {0} could not be resumed.

Cause: Service endpoint could not be resumed due to an unexpected exception. There may be an error message that points to the cause of the problem.

Action: Error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381913: Error occured while polling the resource for Endpoint: {0}. Polling will be stopped.

Cause: A fatal error has occured when trying to poll the MQ queue specified in the URI of the service.

Action: The error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381915: Error occured while polling the resource for response; Endpoint: {0}. Polling will be stopped.

Cause: A fatal error has occured when trying to poll the MQ queue specified in the response URI of the service.

Action: The error message may point to the cause of the problem.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381916: Error occured when connecting to MQ: {0}

Cause: An error has occured when trying to connect to the MQ server; please check the MQ reason code associated with the error for more details

Action: Please check the MQ reason code associated with the error for more details
Level: 1

Type: ERROR

Impact: Configuration

OSB-381919: The MQ Connection Resource {0} in URI {1} does not exist

Cause: The MQ Connection Resource does not exist.

Action: Make sure that the MQ connection resource referenced in the URI exists.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381920: The Unrecognized Response URI should not be the same as Response URI for the service

Cause: In the configuration for the MQ business service the Unrecognized Response URI and Response URI are the same. Such configuration is not legal as it will most likely result in an infinite loop and request/response processing.

Action: Make sure that Unrecognized Response URI and Response URI have different values in MQ business service configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-381921: Error trying to access queue {0}

Cause: OSB could not connect to the configured queue on MQ Server.

Action: Please check if the queue exists on the configured MQ Server.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381922: Error trying to send message to {0}; queue {1} not available.

Cause: OSB could not send message because queue in not available.

Action: Please check if the queue exists on the configured MQ Server.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381940: Error occured when connecting to MQ: {0}

Cause: An error has occured when trying to connect to the MQ server; please check the MQ reason code associated with the error for more details

Action: Please check the MQ reason code associated with the error for more details
Level: 1

Type: ERROR

Impact: Configuration

OSB-381941: Error occured when connecting to MQ. Unable to obtain pooled connection, Resource {0}. Pool size may need to be increased

Cause: An error has occured when trying to connect to the MQ server. Pool size for mq connection pool may need to be increased.

Action: Pool size for mq connection pool may need to be increased.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381942: Error occured when connecting to MQ. Unable to obtain pooled connection, Resource {0}. {1}

Cause: An error has occured when trying to connect to the MQ server. Please check the MQ reason code associated with the error for more details

Action: Please check the MQ reason code associated with the error for more details
Level: 1

Type: ERROR

Impact: Configuration

OSB-381950: Unexpected error happened in the JCA Transport at {0} due to {1}

Cause: An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing

Action: If this error happened during a configuration update, check that your JCA transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-381951: JCA inbound request only invocation failed, exception: {0}

Cause: An exception was thrown during JCA inbound request only invocation

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381952: JCA inbound request response invocation failed, exception: {0}

Cause: An exception was thrown during JCA inbound request only invocation

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381953: Failed to create JCABindingReference for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when creating JCA outbound JCABindingReference

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Deployment

OSB-381954: Failed to close JCABindingReference for wsdl: {0}, operation: {2}, exception: {3}

Cause: An exception was thrown when closing JCA outbound JCABindingReference

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381955: JCA outbound one way invocation failed for wsdl: {0}, operation: {1}, request msg: {2}, exception: {3}

Cause: An exception was thrown when invoking JCA outbound request only endpoint

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381956: JCA outbound request response invocation failed for wsdl: {0}, operation: {1}, request msg: {2}, exception: {3}

Cause: An exception was thrown when invoking JCA outbound request response endpoint

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381957: Failed to create JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when creating JCABindingService

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381958: Failed to close JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when closing JCABindingService

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381959: Failed to activate JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when activating JCABindingService

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381960: Failed to deactivate JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when deactivating JCABindingService

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381961: Failed to create JCABindingService for wsdl: {0}, exception: {1}

Cause: An exception was thrown when creating JCABindingInterface

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381962: Failed to transform message to DOM, message source: {0}, exception: {1}

Cause: An exception was thrown when transforming message source to DOM object

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381963: JCA transport failed to resume existing transaction after received response to inbound request for endpoint: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when resuming existing transaction after received response to inbound request

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381964: JCA transport outbound message was sent without specifying an operation

Cause: JCA transport outbound received a send message request without operation name.

Action: Message should be routed to JCA transport outbound service operation or the inbound service operation should be passed through to outbound.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381965: JCA transport outbound message was sent with invalid URI for the endpoint

Cause: JCA transport outbound received a send message request with an endpoint URI that is not for the endpoint.

Action: If this error happened during a configuration update, check that your JCA transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381966: Failed to get subject from credential call-back when invoking JCA outbound service, exception: {0}

Cause: Failed to get subject from credential call-back when invoking outbound JCA business service.

Action: See exception for more detail.
Level: 1

Type: ERROR

Impact: Security

OSB-381967: Invoke JCA outbound service failed with application error, exception: {0}

Cause: Exception occurred during JCA outbound service invocation. See server log for more detail.

Action: See server log for more detail.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381968: An unexpected error occurred initialization DOM support for the transport: {0}

Cause: There may be a server configuration problem preventing correct initialization of the DOM factory. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381969: JCA transport outbound message was sent with no URI for the endpoint

Cause: JCA transport outbound received a send message request with no endpoint URI set for the endpoint.

Action: Endpoint URI has to be set in TransportOptions when invoking JCA transport business service endpoint.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381970: No service information is registered for: {0}

Cause: JCA transport failed to find the service information using the service ref.

Action: If this error happened during a configuration update, check that your JCA transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381971: Invoke JCA outbound service failed with connection error, exception: {0}

Cause: Exception occurred during JCA outbound service invocation. See server log for more detail.

Action: See server log for more detail.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381972: Failed to create inbound JCABindingService for wsdl: {0}, operation: {1}, exception: {2}

Cause: An exception was thrown when creating inbound JCABindingService

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381973: Failed to restore the original endpoint while trying to compensate for endpoint update failure. Endpoint: {0}, exception: {1}

Cause: Failed to compensate for endpoint update failure, create and activate JCA endpoint failed while trying to restore the original endpoint

Action: See exception for more detail
Level: 1

Type: ERROR

Impact: Session

OSB-381974: Operation "{0}" is not valid for this endpoint.

Cause: The JCA service is called with operation "{0}". The operation is either empty, or not defined for the configured WSDL binding.

Action: Check the configuration of the pipeline to make sure the operation is set and configured with a valid value.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381975: An error occurred while transforming the payload: {0}

Cause: The Oracle JCA adapter is based on the DOM object model. An error occurred while transforming the payload message into a DOM object. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381976: An error occurred while un-marshalling the request message: {0}

Cause: An error occurred while un-marshalling the request message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381977: An error occurred while marshalling the response message: {0}

Cause: An error occurred while marshalling the response message. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381978: An error occurred while marshalling the JCA exception: {0}

Cause: An error occurred while marshalling the JCA exception. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381979: An error occurred while validating JCA transport endpoint, exception: {0}

Cause: An error occurred while validating the JCA transport endpoint. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Session

OSB-381980: Invoke JCA outbound service failed with application error

Cause: Exception occurred during JCA outbound service invocation. See server log for more detail.

Action: See server log for more detail.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-381981: Upgrade JCA WSDL: {0} failed with exception: {1}

Cause: Exception occurred during JCA WSDL upgrade. See server log for more detail.

Action: See server log for more detail.
Level: 1

Type: ERROR

Impact: Upgrade

OSB-381982: Upgrade JCA service: {0} failed with exception: {1}

Cause: Exception occurred during JCA service upgrade. See server log for more detail.

Action: See server log for more detail.
Level: 1

Type: ERROR

Impact: Upgrade

OSB-381983: Resolve toplink mapping file: {0} to InputStream failed with exception: {1}

Cause: Exception occurred while trying to resolve toplink mapping file to input stream. See server log for more detail.

Action: See server log for more detail.
Level: 1

Type: ERROR

Impact: Files

OSB-381984: OSB JCA transport does not support adapter type: {0}

Cause: OSB JCA transport does not support the adapter. Please see OSB JCA transport documentation for more detail.

Action: OSB JCA transport does not support the adapter. Please see OSB JCA transport documentation for more detail.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381985: Failed to load OSBSupportedAdapter.xml, exception: {0}

Cause: OSB JCATransport failed loading OSBSupportedAdapter.xml.

Action: Please make sure OSBSupportedAdapter.xml contains valid adapter types.
Level: 1

Type: ERROR

Impact: Configuration

OSB-381986: An error occurred while validating JCA transport endpoint. JNDI lookup with URL: {0} failed due to lack of permission. Add a static service account to JCA service to specify the credentials for authentication.

Cause: Lookup adapter connection factory JNDI: {0} failed due to lack of permission. The JNDI is protected.

Action: Add a static service account to JCA service to specify the credentials for authentication
Level: 1

Type: ERROR

Impact: Security

OSB-381987: An error occurred while validating JCA transport endpoint. JNDI lookup with URL: {0} failed. Missing JNDI configuration such as undeployed or incorrectly configured JCA Adapter RAR or connection factory.

Cause: Lookup adapter connection factory JNDI: {0} failed. Missing JNDI configuration such as undeployed or incorrectly configured JCA Adapter RAR or connection factory.

Action: Configure an adapter connection factory with JNDI: {0}
Level: 1

Type: ERROR

Impact: Configuration

OSB-381988: An error occurred while validating JCA transport endpoint properties, exception: {0}

Cause: An error occurred while validating the JCA transport endpoint properties. More information should be provided by the following nested exception: {0}

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382000: General runtime error: {0}

Cause: A general runtime error has occurred in OSB pipeline runtime while processing the message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-382001: Context variable names must be non-null and have non-zero length

Cause: A runtime error has occurred in OSB pipeline runtime while processing the message. Message context variable names must be non-null and have non-zero length

Action: Check your pipeline configuration to make sure all variable names are properly configured and have non-zero length
Level: 1

Type: ERROR

Impact: Configuration

OSB-382002: Router runtime cache has not been initialized on this node!

Cause: An unexpected error has occurred in during the initialization of OSB pipeline runtime while processing the request message for specified proxy service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382003: Unknown error while processing message for service {0}

Cause: An error has occurred in OSB pipeline runtime while processing the request message for specified proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382004: Failed to process request message for service {0}: {1}

Cause: An error has occurred in OSB pipeline runtime while processing the request message for specified proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382005: Failed to process response message for service {0}: {1}

Cause: An error has occurred in OSB pipeline runtime while processing the response message for specified proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382006: No object is registered for ref ''{0}''

Cause: An error has occurred in OSB pipeline runtime while processing the response message for specified proxy service due to an attempt to look up an object in Java object repository with the specified reference. This may have occurred to due a previously executed pipeline action that deleted the object with the corresponding reference.

Action: Check the pipeline message flow configuration to make sure there is no pipeline action that deletes the object with the specified reference that executes prior to this error
Level: 1

Type: ERROR

Impact: Data

OSB-382007: Failed to start timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382008: Failed to lookup counter {0}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382009: Failed to increment counter {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382010: Failed to stop timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382012: Expected object of type java.lang.Throwable, instead found: {0}

Cause: An unexpected error has occurred in OSB pipeline runtime while processing the response message from a business service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382013: The configurations for the proxy service is in flux.

Cause: The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy service is in flux. This proxy is unable to send an outbound message to service "{0}" until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.
Level: 1

Type: ERROR

Impact: Process

OSB-382014: The configurations for the proxy and target services are in flux. This proxy is unable to route to service "{0}" until the configuration stabilizes.

Cause: The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy and target services are in flux. This proxy is unable to send an outbound message to service "{0}" until the configuration stabilizes.

Action: Wait until the configuration of OSB server stabilizes and retry sending the request.
Level: 1

Type: ERROR

Impact: Process

OSB-382015: Cannot create RouterContext for non-proxy services: {0}

Cause: There was an internal error while initializing the OSB pipeline runtime state for given service. Only proxy service can process inbound messages

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382016: Failed to instantiate router for service {0}: {1}

Cause: There was an error while initializing the OSB pipeline runtime state for given proxy service. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382017: Failed to find runtime object for this service: {0}

Cause: There was an unexpected error while initializing the OSB pipeline runtime state for given service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382018: Unable to generate runtime for router configuration: {0}

Cause: This is a diagnostic error message that is logged with error severity in the event OSB pipeline runtime fails to initialize its state. The message will contain various bits of information that will help in the analysis of the underlying cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382020: Failed to register the stage action {0}: {1}

Cause: There was an error during the initialization and/or registration of single pipeline action {0}. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382021: Failed to register the stage-action application {0}: {1}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions contained in an application file {0}. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382022: Failed to load factory class: {0}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382023: Failed to instantiate instance of action factory: {0}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382024: Failed to instantiate instance of action factory (constructor may not be public): {0}

Cause: There was an error during the initialization and/or registration of a set of pipeline actions. This may happen due to incorrectly configured installation of OSB product

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382025: Transformation from {0} to {1} is not supported

Cause: An error has occured while transforming the message payload from one type (e.g. MFL) to another (e.g. XML). This may happen some transport requires the payload in certain form in order to send an outbound request and OSB runtime has no way to convert payload in its current form to desired form

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382028: Failed to load WSDL binding information for service

Cause: There was an unexpected error during the processing of the message by OSB pipeline runtime. The error happened while trying to load WSDL binding information for proxy service.

Action: Check configuration of proxy service and contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382029: Failed to create WS-I compliance checker

Cause: There was an unexpected error during the processing of the message by OSB pipeline runtime. The error happened during initialization of component that checks for WS-I compliance.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382030: Failure while un-marshalling message: {0}

Cause: There was an error parsing request or response payload. E.g. the request payload may have improperly formatted multipart/related data which will lead to an error trying to un-marshall message attachments. There will be an error message that will point to specific cause of the error

Action: Look at the specific error message and examine the payload to see why OSB fails to un-marshall its contents properly.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382032: The message must be an instance of: {0}

Cause: There was an error parsing the contents of request or response message due to the fact that the payload was expected to contain a valid SOAP envelope but did not. This can happen for when a SOAP (Any SOAP or WDSL-based OSB proxy receives a request message that does not contain a valid SOAP envelope

Action: Examine the payload to make sure it contains valid SOAP envelope
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382033: A soap:Envelope must contain a soap:Body

Cause: There was an error parsing the contents of request or response message due to the fact that the payload was expected to contain a valid SOAP Body within SOAP Envelope but did not. This can happen for when a SOAP (Any SOAP or WDSL-based OSB proxy receives a request message that does not contain a valid SOAP Body element in its envelope

Action: Examine the payload to make sure it contains valid SOAP Body element
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382034: Expected SOAP 1.1 Envelope

Cause: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Envelope element was missing.

Action: Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382035: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Header element was missing.

Cause: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Header element was missing.

Action: Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382036: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Body element was missing.

Cause: There was an error during the conversion of SOAP 1.1 payload to SOAP 1.2 payload. The expected SOAP 1.1 Body element was missing.

Action: Make sure the payload is valid SOAP 1.1 payload. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382037: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Envelope element was missing.

Cause: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Envelope element was missing.

Action: Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382038: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Header element was missing.

Cause: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Header element was missing.

Action: Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382039: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Body element was missing.

Cause: There was an error during the conversion of SOAP 1.2 payload to SOAP 1.1 payload. The expected SOAP 1.2 Body element was missing.

Action: Make sure the payload is valid SOAP 1.2 payload. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382040: Failed to set the value of context variable "{0}". Value must be an instance of {1}.

Cause: There was an error assigning a value to specified message context variable. There are certain message context variables, e.g. $outbound, $attachments, $fault that have a pre-defined structure (see online OSB documentation for details) and any value assigned to them is expected to be in certain format

Action: Use OSB Log action to verify that the value being assigned to the variable is in fact in expected format
Level: 1

Type: ERROR

Impact: Data

OSB-382041: Failed to set the value of context variable "{0}". Variable is read-only.

Cause: There was an error assigning a value to specified message context variable. There are certain message context variables, e.g $operation that one cannot assign values to and thus they are considered read-only.

Action: Check OSB on-line documentation to make sure that the variable whose value is being changed is not considered a read-only variable.
Level: 1

Type: ERROR

Impact: Data

OSB-382042: Failed to set the value of context variable "{0}". {1}

Cause: There was an error assigning a value to specified message context variable. This may happen when trying to assign non-XML values to message context variables that expect XML content (e.g. $fault).

Action: Use OSB Log action to verify that the value being assigned to the variable is in fact in expected format
Level: 1

Type: ERROR

Impact: Data

OSB-382043: Failed to update the value of context variable "{0}": {1}

Cause: There was an error assigning or updating a value of a specified message context variable. This may happen when the value being assigned does not conform to specified format for a system variable (e.g. setting $outbound to null) or updating a read-only portion of a variable (e.g. changing 'service' element of $inbound) message context variable

Action: Use OSB Log action to verify that the value being assigned to the variable is in fact in expected format. Also check OSB on-line documentation to make sure that the part of the variable that you are changing is not considered read-only.
Level: 1

Type: ERROR

Impact: Data

OSB-382045: Failed to initialize the value of context variable "{0}": {1}

Cause: There was an unexpected error while initializing one of the system variables. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382046: Failed to marshall the value of context variable "{0}" to XML: {1}

Cause: There was an error retrieving the XML representation of the value of a system context variable, e.g. request or response meta-data for $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382047: Processor must be in INACTIVE state

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382048: Processor must be in RESPONSE or ERROR state

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382049: OSB failed to start a transaction

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382050: Expected active transaction, actual transaction status: {0}

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382051: No transaction found on the current thread

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382052: Cannot commit a different transaction

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382053: Cannot rollback a different transaction

Cause: There was an internal error in OSB pipeline runtime while processing the inbound request by a proxy service. The state of OSB pipeline was not expected

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382054: Expected [[http://www.bea.com/wli/sb/context]java-content] element under $body is missing or invalid

Cause: Services of Messaging Type : Java are expected to contain a valid [[http://www.bea.com/wli/sb/context]java-content] child element under $body.

Action: Make sure the contents of $body conforms to expected format. One can use Log action to log and examine the contents of any message context variable, including $body
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382100: Failure in binding-layer while processing inbound request for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the inbound request by a proxy service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382101: Failure in binding-layer while preparing inbound response for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while preparing the inbound response for a proxy service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382102: Failure in binding-layer while preparing outbound request for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while preparing the outbound request for a business service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382103: Failure in binding-layer while processing outbound response for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the outbound response from a business service. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382104: Failed to prepare request metadata for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the request metadata for either $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382105: Failed to prepare response metadata for service {0}: {1}

Cause: There was an error in OSB pipeline runtime while processing the response metadata for either $inbound or $outbound message context variable. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382110: There was an error while encoding base64 content

Cause: An unexpected error has occurred in OSB pipeline runtime while performing XOP/MTOM-related processing of inbound message. There should be an error message that describes specific error cause

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382111: Missing ref attribute from binary-content element

Cause: A binary-content element is not properly constructed - it is missing a required ref attribute

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382112: No object is registered for ref ''{0}'' in source repository

Cause: An error has occurred in OSB pipeline runtime while processing the response message for specified proxy service due to an attempt to look up an object in source repository with the specified reference.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382113: Missing or illegal value for Content-ID MIME header in MimeSource

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for outbound request message

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382114: Could not decode URI ''{0}''. {1}

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message There should be precise error message that points to the cause of the error

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382115: Encountered XOP:Include SOAP Element without an href. Without the href, we cannot lookup its MIME attachment !

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382116: There should be exactly one MIME attachment with Content-ID = ''{0}''.

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382117: Received more than one ''Content-Transfer-Encoding'' MIME header in attachment with CID ''{0}'', received {1}

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382118: Decoding of MIME attachments from MIME Content-Transfer-Encoding=''{0}'' not supported

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382119: A service not enabled for XOP/MTOM has received an XOP/MTOM message

Cause: A service not enabled for XOP/MTOM has received an XOP/MTOM message

Action: Make sure that the proxy service has XOP/MTOM feature enabled to allow it to properly process incoming payload
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382120: Mixing of XOP/MTOM and attachments is not allowed!

Cause: An outbound request to a service enabled for XOP/MTOM cannot be prepared due to the fact that the business service is enabled for XOP/MTOM support and the value of $attachments variable is not null. Mixing of XOP/MTOM and attachments is not supported

Action: Please make sure that $attachments variable does not contain any information when routing to XOP/MTOM-enabled services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382121: Each MIME part that is referred to by xop:Include MUST have a Content-Transfer-Encoding header field

Cause: An error has occurred in OSB pipeline runtime while performing XOP/MTOM processing for inbound request message

Action: Make sure that the inbound XOP/MTOM payload is valid according to XOP/MTOM standard
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382150: Failure while dispatching request to service {0}: {1}

Cause: There was an unexpected error in OSB pipeline runtime while performing an outbound request for either routing, publish or service callout action. There should be a specific error message that will point to the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382151: Nothing is known about service {0}

Cause: There was an unexpected error retrieving configuration details for specified service {0}.

Action: Use OSB console to check that the service in question is properly configured
Level: 1

Type: ERROR

Impact: Configuration

OSB-382153: Cannot delete system variable "{0}" from context

Cause: An attempt to delete a system variable from the message context failed because there are a number of system variables that cannot be deleted, such as $inbound and $outbound.

Action: Check OSB online documentation on whether a given system variable can be deleted from the message context.
Level: 1

Type: ERROR

Impact: Data

OSB-382187: Could not roll back the action for delete resequencer configuration {0}: {1}

Cause: Could not roll back the action for delete resequencer configuration. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.
Level: 1

Type: ERROR

Impact: Process

OSB-382188: Could not roll back the action for create resequencer configuration {0}: {1}

Cause: Could not roll back the action for create resequencer configuration. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.
Level: 1

Type: ERROR

Impact: Process

OSB-382189: Could not load the resequencer configuration for pipeline {0}: {1}

Cause: Could not load the resequencer configuration. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.
Level: 1

Type: ERROR

Impact: Configuration

OSB-382190: Component {0} may not be invoked because it exists in a different project

Cause: Invoked components (pipeline and split join resources) must be in the same project as the proxy service invoking them

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-382191: {0}: Unhandled error caught by system-level error handler: {1}

Cause: A error has occurred during message processing and was not handled via the user-configured error handler

Action: Check the exception message. It will indicate the source of error.
Level: 1

Type: ERROR

Impact: Process

OSB-382500: OSB Service Callout action received SOAP Fault response

Cause: OSB Service Callout action has received a SOAP Fault response from the web service that was invoked. The contents of the received SOAP Fault can be seen in the details element of $fault message context variable.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382501: OSB Service Callout action received an unrecognized response

Cause: The service invoked by OSB Service Callout action has returned payload that was not consistent with the declared service binding type and as a result could not be properly parsed by OSB. For example, this can happen if a service that was registered with XML binding type, returned non well-formed XML payload. The contents of the received response can be seen in the details element of $fault message context variable.

Action: Check the contents of response payload in $fault variable to see why it is inconsistent with the declared service binding type
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382502: OSB Service Callout action received an error response

Cause: The service invoked by OSB Service Callout action has indicated that an error condition other than a SOAP fault has occured. For example, this may happen when an HTTP 404 (Page Not Found) error code is received from an external HTTP service. The contents of the received response (if any) can be seen in the details element of $fault message context variable.

Action: Check the contents of response payload in $fault variable to see what the problem with service invocation is
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382505: OSB Validate action failed validation

Cause: The input expression has failed validation according to provided schema resource. The details of the validation error, such as specific error message, location of the invalid XML, etc. can be seen in the details element of $fault message context variable

Action: Check the contents of $fault variable to see the source of the validation failure
Level: 1

Type: ERROR

Impact: Data

OSB-382510: OSB Assign action failed updating variable "{0}": {1}

Cause: There was an error during the evaluation of XQuery/XSLT expression during the execution of Assign action. This could happen if an XQuery expression the result of which is being assigned to a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382511: OSB Delete action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Delete action. This could happen if the specified XPath expression is not a valid expression or results in a runtime error from XPath evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XPath expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382512: OSB Insert action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Insert action. This could happen if an XQuery expression the result of which is being inserted into a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382513: OSB Replace action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Replace action. This could happen if an XQuery expression the result of which is being replaced in a variable, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382514: OSB Rename action failed updating variable "{0}": {1}

Cause: There was an error during the execution of Rename action. This could happen if the specified XPath expression is not a valid expression or results in a runtime error from XPath evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XPath expression for potential syntax or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382515: Callout to java method "{0}" resulted in exception: {1}

Cause: Java method specified in Java Callout action was invoked and resulted in an exception. The exception details should be part of the error message.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382516: Failed to evaluate expression for callout to java method "{0}". Argument index: {1}, exception: {2}

Cause: There was an error evaluating one or more arguments to a Java callout method. This could happen if an XQuery expression the result of which is being used as an argument to java method, results in a runtime error from the XQuery evaluation engine. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382517: Failed to assign the result of java callout to variable. Method: {0}, variable: {1}, exception: {2}

Cause: There was an error while assigning the result of invoked Java method to specified message context variable. This could happen if the variable being assigned to is a read-only system variable (e.g. $operation), or a system variable whose type does not match that returned by the invoked Java method. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382518: Security exception while calling to java method "{0}". Service account: {1}. {2}

Cause: There was an error while setting up the security context for java callout method. This could happen if there is a problem retrieving the credentials of specified service account. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382519: The XmlObject returned by a java callout must be a simple type, an attribute or an element.

Cause: Java method invoked returned an unsupported type of XML Bean. The only supported types are simple types, attributes or element.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382520: Unexpected error executing if-then-else expression

Cause: An unexpected runtime exception has occured during the execution of the if-then-else action.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382521: Variable targeted for rename is not XML or MFL

Cause: The variable that is targeted for rename operation does not hold XML data.

Action: Check the value of the variable that is targeted for rename operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382522: Variable targeted for replace is not XML or MFL

Cause: The variable that is targeted for replace operation does not hold XML data.

Action: Check the value of the variable that is targeted for rename operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382523: The outbound variable has not been initialized

Cause: This is an unexpected error that occured due to incorrect state of the pipeline at runtime

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382524: Failed to perform validation

Cause: An unexpected runtime error has occured during the execution of validate action. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382525: Variable targeted for validate is not XML or MFL

Cause: The variable that is targeted for validate operation does not hold XML data.

Action: Check the value of the variable that is targeted for validate operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382526: Variable targeted for insert is not XML or MFL

Cause: The variable that is targeted for insert operation does not hold XML data.

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382527: Inserting the result of this expression will create an invalid (multi-rooted) document

Cause: Inserting the result of this expression will create an invalid (multi-rooted) document. One way this could happen is if ones tries to insert (some) element node before . in $body message context variable

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382528: Failed to insert after

Cause: Inserting the result of this expression after specified XPath resulted in an error.

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382529: Cannot insert as a child of an attribute

Cause: It is illegal to insert as a child of an attribute

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382530: Unable to insert after first child

Cause: Unable to insert after first child as there was no child elements of specified XPath expression

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382531: Unable to insert after last child

Cause: Unable to insert after child element

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382532: Only attributes may be inserted next to another attribute

Cause: Only attributes may be inserted next to another attribute

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382533: Only elements and simple values may be inserted next to or inside of another element

Cause: Only elements and simple values may be inserted next to or inside of another element

Action: Check the value of the variable that is targeted for insert operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382534: Content targeted for replace is not an element or an attribute

Cause: Content targeted for replace is not an element or an attribute

Action: Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382535: An attribute may only be replaced with an attribute

Cause: An attribute may only be replaced with an attribute

Action: Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382536: An element or its contents may only be replaced with elements and simple values

Cause: An element or its contents may only be replaced with elements and simple values

Action: Check the value of the variable that is targeted for replace operation. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382537: Invalid SOAP RPC document - part "{0}" is not defined in the WSDL definitions.

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.
Level: 1

Type: ERROR

Impact: Data

OSB-382538: Invalid SOAP RPC document - part {0} occurs more than once.

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.
Level: 1

Type: ERROR

Impact: Data

OSB-382539: Invalid SOAP RPC document - part {0} contains more than one XML element

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.
Level: 1

Type: ERROR

Impact: Data

OSB-382540: Unexpected error - invalid internal state occured during the execution of service callout action

Cause: An unexpected error had occured during the execution of service callout action

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382541: Invalid SOAP RPC document - part "{0}" is required but not present.

Cause: The response to service callout contained invalid data according to WSDL definition of the service being invoked.

Action: Check the response payload of service invocation and make sure it conforms to the WSDL definitions for the service. The contents of the received response can be seen in the details element of $fault message context variable.
Level: 1

Type: ERROR

Impact: Data

OSB-382542: The Transport Mode is set to "request-only". A Service Callout only supports "request-response" communications.

Cause: The Transport Mode is set to "request-only". Service Callout action only supports "request-response" communications.

Action: Check the contents of $outbound message context variable to make sure the transport mode element is set properly. One can use Log action to see the contents of any message context variable at runtime
Level: 1

Type: ERROR

Impact: Configuration

OSB-382543: Invalid message: the SOAP Header value is not an XML instance

Cause: The value of the message context variable used to set SOAP headers for service callout action does not contain valid XML

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime
Level: 1

Type: ERROR

Impact: Data

OSB-382544: Invalid message: the message is not an XML instance

Cause: The value of the message context variable used to set SOAP body for service callout action does not contain valid XML

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime
Level: 1

Type: ERROR

Impact: Data

OSB-382545: Unexpected error - the part schema type cannot be found

Cause: An unexpected error had occured during the execution of service callout action during the parsing phase of the service callout response

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382546: Unexpected error - mismatch between configuration and WSDL definition

Cause: An unexpected error had occured during the execution of service callout action during the parsing phase of the service callout response

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-382547: The value for part "{0}" is not valid. An XML Element is expected.

Cause: An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to the fact that the configured message context variable does not contain valid XML element.

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime
Level: 1

Type: ERROR

Impact: Data

OSB-382548: Unable to find the type definition of the part {0}

Cause: An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to missing or invalid type information in WSDL definitions

Action: Check the registered WSDL definition for proper semantic type information for the part in question
Level: 1

Type: ERROR

Impact: Data

OSB-382549: Error accessing information from the target WSDL service

Cause: An error had occured during the execution of service callout action during the phase when an outbound request payload gets constructed due to not being able to access service WSDL definition. There should be a specific message that will point to the cause of the error.

Action: Check that the corresponding WSDL definition is properly registered
Level: 1

Type: ERROR

Impact: Configuration

OSB-382550: Setting quality of service to 'Exactly Once' in service callout action is not supported for service {0}

Cause: Setting quality of service to 'Exactly Once' in service callout action is not supported for selected service. Quality of service can be set to 'Exactly Once' only if the service transport endpoint is Transactional and the message pattern is 'one-way' or 'synchronous'.

Action: Check the pipeline configuration to make sure that the quality of service is not set to 'Exactly Once' via Routing Options or some other action that changes the contents of $outbound message context variable. You can use Log action to see the value of any message context variable at runtime.
Level: 1

Type: ERROR

Impact: Configuration

OSB-382551: XQuery expression did not return the non-empty source to apply the MFL translation.

Cause: XQuery expression did not return the non-empty source to apply the MFL translation.

Action: Check the XQuery expression to make sure that it returns a non-empty input to apply the MFL translation. You can use Log action to see the value of XQuery expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382552: Binary content reference {0} is not valid.

Cause: Binary content reference is not valid. It should be inserted by the pipeline as a result of passing binary content to the pipeline.

Action: Check the binary-content ref attribute on which the MFL translation is applied. binary-content element should be inserted as a result of passing binary content to the pipeline. You can use Log action to see the value of this ref attribute at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382553: Input to non-xml to xml MFL translation is invalid.

Cause: Input to the transformation should be non-empty text or the binary data represented by binary-content element in the pipeline. XML input is not allowed.

Action: Make sure that input expression returns the text or the binary-content ref attribute inserted by the pipeline as a result of passing binary content to the OSB. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382554: XQuery expression evaluates to an invalid MFL resource name {0}.

Cause: XQuery expression did not return the valid MFL resource name. It should evaluate to an existing mfl resource in the OSB at runtime.

Action: Make sure that XQuery expression should evaluate to a existing mfl resource in the OSB at runtime. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382555: XML to Binary MFL translation failed for the MFL Resource {0} : {1}

Cause: XML to Binary MFL translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured mfl resource and the input data for potential syntactic or semantic problems.
Level: 1

Type: ERROR

Impact: Data

OSB-382556: Binary to XML MFL translation failed for the MFL Resource {0} : {1}

Cause: Binary to XML MFL translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured mfl resource and the input data for potential syntactic or semantic problems.
Level: 1

Type: ERROR

Impact: Data

OSB-382557: No source was found in source repository with ref ''{0}''.

Cause: No source was found in source repository with ref ''{0}'', which was the result of configured XQuery expression

Action: Check the XQuery expression to make sure that it returns proper result. You can use Log action to see the value of an XQuery expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382558: Dynamic validate query must return a single instance of {0}

Cause: The configured XQuery expression did not evaluate to a single instance of expected XML snippet in format "ctx:validate...".

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382559: XQuery expression did not return the non-empty source to apply the nXSD translation.

Cause: XQuery expression did not return the non-empty source to apply the nXSD translation.

Action: Check the XQuery expression to make sure that it returns a non-empty input to apply the nXSD translation. You can use Log action to see the value of XQuery expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382560: Binary content reference {0} is not valid.

Cause: Binary content reference is not valid. It should be inserted by the pipeline as a result of passing binary content to the pipeline.

Action: Check the binary-content ref attribute on which the nXSD translation is applied. binary-content element should be inserted as a result of passing binary content to the pipeline. You can use Log action to see the value of this ref attribute at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382561: Input to native to XML nXSD translation is invalid.

Cause: Input to the translation should be non-empty text or the binary data represented by binary-content element in the pipeline. XML input is not allowed.

Action: Make sure that input expression returns the text or the binary-content ref attribute inserted by the pipeline as a result of passing binary content to the OSB. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Other

OSB-382562: XQuery expression evaluates to an invalid nXSD {0}.

Cause: XQuery expression did not return the valid nXSD. It should evaluate to an existing nXSD schema in the OSB at runtime.

Action: Make sure that XQuery expression should evaluate to a existing nXSD schema in the OSB at runtime. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-382563: XML to Native nXSD translation failed for the nXSD {0} : {1}

Cause: XML to Native nXSD translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured nXSD resource and the input data for potential syntactic or semantic problems.
Level: 1

Type: ERROR

Impact: Data

OSB-382564: Native to XML nXSD translation failed for the nXSD {0} : {1}

Cause: Native to XML nXSD translation failed. There should be a specific error message that will pinpoint the source of the problem.

Action: Check the configured nXSD resource and the input data for potential syntactic or semantic problems.
Level: 1

Type: ERROR

Impact: Data

OSB-382565: nXSD ref {0} does not exist.

Cause: nXSD ref does not exist.

Action: Make sure that the nXSD ref exists in OSB configuration.
Level: 1

Type: ERROR

Impact: Data

OSB-382566: Error in applying translation to the input for nXSD {0} : {1}

Cause: Error in applying nXSD translation to the input.

Action: Make sure that input nXSD is well formed. Please refer to error message for more debug details.
Level: 1

Type: ERROR

Impact: Data

OSB-382567: Invalid message: the Attachments value is not an XML instance

Cause: The value of the message context variable used to set attachments for service callout action does not contain valid XML

Action: Check the contents of specified message context variable to make sure it is set properly. One can use Log action to see the contents of any message context variable at runtime
Level: 1

Type: ERROR

Impact: Data

OSB-382600: Dynamic publish query must return a single instance of {0}

Cause: The configured XQuery expression did not evaluate to a single instance of expected XML snippet in format \"ctx:route...\".

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382601: Error during dynamic publish action: {0}

Cause: A runtime error has occured during the execution of dynamic publish action. This might occur for a variety of reasons, for example, the XQuery/XSLT evaluation of service reference has produced a runtime error or returned an XML element in an unexpected format.

Action: Check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382602: Service not specified

Cause: The result of the configured XQuery expression did not contain the expected 'service' element.

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Configuration

OSB-382603: Error during publish

Cause: A runtime exception has occured during the execution of the publish action. This may have occured due to an error from the underlying transport. There should be a specific error message that will point the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-382604: Unexpected error executing the publish table expression

Cause: An unexpected runtime exception has occured during the execution of the publish table action.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382605: Publishing to service {0} is not supported because it has result caching enabled

Cause: If a business service is caching it's results, it cannot be published to.

Action: Either remove the result caching configuration from the business service or publish to a different service.
Level: 1

Type: ERROR

Impact: Configuration

OSB-382610: Dynamic route query must return a single instance of {0}

Cause: The configured XQuery expression did not evaluate to a single instance of expected XML snippet in format \"ctx:route...\".

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Data

OSB-382611: Service not specified

Cause: The result of the configured XQuery expression did not contain the expected 'service' element.

Action: Please see online documentation for details of the expected format and check the configured XQuery expression for potential syntactic or semantic problems
Level: 1

Type: ERROR

Impact: Configuration

OSB-382612: Error preparing message for dispatch: {0}

Cause: A runtime exception has occured during the preparation of the outbound message for routing node. This may have occured due to an error while executing request actions of the routing node. There should be a specific error message that will point the cause of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382613: Cannot perform routing unless router is in REQUEST state

Cause: This is an unexpected error that occured due to erroneous state of the pipeline

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-382614: Unexpected error executing the routing table expression

Cause: An unexpected runtime exception has occured during the execution of the routing table action.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-382620: XPath expression for key does not yield a text value

Cause: XPath expression does not yield a text value.

Action: Please check the XPath expression.
Level: 1

Type: ERROR

Impact: Other

OSB-382621: Failed to issue report: {0}

Cause: Reporting data manager is not able to process and/or store reporting data in appropriate data store.

Action: Check if the reporting provider is installed properly.
Level: 1

Type: ERROR

Impact: Other

OSB-382630: Failed to generate the alert: {0}

Cause: Failed to generate the alert. There might be a problem with the configured Alert Destination.

Action: Please check the configuration of Alert Destination.
Level: 1

Type: ERROR

Impact: Other

OSB-383500: Failed to deploy pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to deploy. Exception details will point to the actual cause.

Action: Please check the resequencer configuration. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383501: Failed to deploy pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to deploy. Exception details will point to the actual cause.

Action: Please check the resequencer configuration. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383502: Failed to undeploy pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to undeploy. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383503: Failed to deploy pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to undeploy. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383504: Failed to load pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to load. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383505: Failed to load pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to load. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383506: Failed to unload pipeline resequencer component for service {0}: {1}

Cause: Resequencer component failed to unload. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383507: Failed to unload pipeline resequencer component for service {0} with operation name {1}: {2}

Cause: Resequencer component failed to unload. Exception details will point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383508: Failed to initialize resequencer: {0}

Cause: Resequencer failed to initialize. Exception details will point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383509: Pipeline ref {0} not found. Message dispatch from resequencer to pipeline will fail: {1}

Cause: Pipeline ref does not exists. Pipeline component may have been deleted.

Action: Please make sure that the pipeline component exists in the OSB configuration.
Level: 1

Type: ERROR

Impact: Other

OSB-383510: Message with id {0} for resequencer component {1} could not be persisted: {2}

Cause: Message could not be persisted. DataBase may be down. Exception details may point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383511: Message with id {0} for resequencer component {1} dispatch failed to Resequencer: {2}.

Cause: Message could not be dispatched to Resequencer. Exception details may point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the exact source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383512: Message with id {0} could not be retrieved: {1}

Cause: Message could not be retrieved. DataBase may be down. Exception details may point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383513: Message with id {0} for resequencer component {1} could not be dispatched to pipeline after resequencing: {2}

Cause: Message could not be dispatched to pipeline after resequencing. Exception details may point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383514: Message with id {0} for resequencer component {1} could not be persisted: {2}

Cause: Message could not be persisted. Exception details may point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383515: Message payload with id {0} for resequencer component {1} could not be read: {2}

Cause: Message could not be read. Exception details may point to the actual cause.

Action: Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383516: Resequencer is not configured for this pipeline.

Cause: Resequencer is not configured for this pipeline. Pipeline component may have been updated to remove resequencer configuration.

Action: Please update the Pipeline configuration.
Level: 1

Type: ERROR

Impact: Other

OSB-383517: Resequencer configuration parsing failed.

Cause: Resequencer configuration parsing failed. Pipeline component may be corrupt.

Action: Please update the Pipeline configuration.
Level: 1

Type: ERROR

Impact: Other

OSB-383518: Pipeline ref {0} not found.

Cause: Pipeline ref does not exists. Pipeline component may have been deleted.

Action: Please make sure that the pipeline component exists in the OSB configuration.
Level: 1

Type: ERROR

Impact: Other

OSB-383519: Invalid variable name {0} in XQuery expression for pipeline component {1}

Cause: Invalid variable name in the XQuery expression for pipeline component.

Action: Please modify the XQuery expression. Valid variables are 'body', 'headers' and 'transportMetaData'
Level: 1

Type: ERROR

Impact: Other

OSB-383520: XQuery expression execution failed for pipeline {0}: {1}

Cause: XQuery expression execution failed. Please check the exception message.

Action: Please check the exception message. It may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383521: XQuery expression {0} evaluated to a null value.

Cause: XQuery expression evaluated to a null value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. An empty result may be due to missing XML elements/attributes in the data, improper use of namespaces...
Level: 1

Type: ERROR

Impact: Other

OSB-383522: XQuery expression {0} evaluated to an array value.

Cause: XQuery expression evaluated to an array value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1).
Level: 1

Type: ERROR

Impact: Other

OSB-383523: Resequencer validation failed: {0}

Cause: Resequencer validation failed.

Action: Please check the exception message. It may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383524: XQuery variable {0} could not be retrieved for message id {1}: {2}

Cause: XQuery variable could not be retrieved.

Action: Please check the XQuery expression. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-383525: XQuery {0} evaluated to unknown type {1}

Cause: XQuery evaluated to unknown type.

Action: Please check the XQuery expression.
Level: 1

Type: ERROR

Impact: Other

OSB-383526: Resequencer could not be stopped successfully: {0}

Cause: Resequencer could not be stopped successfully.

Action: Please check the error message.
Level: 1

Type: ERROR

Impact: Other

OSB-383527: Resequencer message {0} deletion failed after successful execution: {0}

Cause: Resequencer message could not be deleted after successful execution.

Action: Please check the error message.
Level: 1

Type: ERROR

Impact: Other

OSB-383528: Resequencer message {0} targeted to resequencer component {1} doesn't contain the operation name in the dispatch context. Possible cause is, operation name may not be part of the wsdl definition.

Cause: Operation name may not be part of the wsdl definition. It should be one way operation as defined in the wsdl.

Action: Please check the SOAP message. It should have one way operation as defined in the wsdl.
Level: 1

Type: ERROR

Impact: Other

OSB-383529: Resequencer message {0} targeted to resequencer component {1} doesn't contain the valid operation name: {2}. Possible cause is, operation name may not be part of the wsdl definition.

Cause: Operation name may not be part of the wsdl definition. It should be one way operation as defined in the wsdl.

Action: Please check the SOAP message. It should have one way operation as defined in the wsdl.
Level: 1

Type: ERROR

Impact: Other

OSB-383530: Failed to update the resequencer global configuration parameters: {0}

Cause: Resequencer failed to update the global configuration parameters. Exception details will point to the actual cause.

Action: Please make sure that the DB is running. Exception message may indicate the source of error.
Level: 1

Type: ERROR

Impact: Other

OSB-386000: General security error

Cause: General security error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386003: Mapped service account "{0}" is invalid: user mapping entry for local user "{1}" maps to non-existing remote user "{2}"

Cause: Map the local user to a valid remote user.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386004: Message-level access control denied access to proxy service {0}, operation {1}, subject: {2}

Cause: Message-level access denied.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386005: Mapped service account "{0}" is invalid: its anonymous mapping maps to a non-existing remote user

Cause: Update the service account to map to a valid remote user.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386006: An error occurred while initializing {0}

Cause: Failed to initialize the component.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-386007: ResourceIdManager.registerResourceType() failed

Cause: Failed to register the resource.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-386008: Message level username/password authentication failed: {0}

Cause: Message level username/password authentication failed.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386009: Message level custom token authentication failed: {0}

Cause: Message level custom token authentication failed.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386010: Internal error: the proxy service is configured for message-level custom token or custom username/password authentication but WS-Security authentication has already taken place.

Cause: WS-Security authentication and message-level custom authentication are mutually exclusive.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386011: An error occurred while evaluating the custom authentication token XPath selector: {0}

Cause: Error evaluating the custom authentication token XPath selector.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386012: An error occurred while evaluating the message-level username XPath selector: {0}

Cause: Error evaluating the message-level username XPath selector.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386013: An error occurred while evaluating the message-level password XPath selector: {0}

Cause: Error evaluating the message-level password XPath selector.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386014: the result of the XPath selector is empty

Cause: the result of the XPath selector is empty

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386015: the XPath selector returned multiple nodes

Cause: the XPath selector returned multiple nodes

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386016: the result of the XPath cannot be converted to java.lang.String (it is not a single text-node or attribute value)

Cause: the result of the XPath cannot be converted to java.lang.String (it is not a single text-node or attribute value)

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386017: the XPath cannot be evaluated because the request message does not have the required message part ({0})

Cause: the XPath cannot be evaluated because the request message does not have the required message part.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386018: an error occurred while evaluating the XPath expression: {0}

Cause: an error occurred while evaluating the XPath expression.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386019: The proxy service operation selection algorithm returned an invalid operation name: {0}

Cause: The proxy service operation selection algorithm returned an invalid operation name.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386020: the xpath result is not within the scope of the root node ({0}), this can happen if the xpath uses the '//' construct.

Cause: You must update your xpath to make sure it only selects elements within the root node (i.e. header or body).

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386021: No resource data

Cause: The resource data parameter was not supplied or is empty.

Action: Specify valid resource data.
Level: 1

Type: ERROR

Impact: Security

OSB-386022: No resource type

Cause: The resource type information was not supplied.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

OSB-386023: No resource identifier

Cause: The resource identifier parameter was not supplied or is empty.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

OSB-386024: No resource keys found

Cause: No resource key information was supplied in the resource identifier.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

OSB-386025: Invalid data type for {0} resource key value

Cause: The data type of a resource key value is not valid.

Action: Specify a valid resource key data type value.
Level: 1

Type: ERROR

Impact: Security

OSB-386026: Invalid resource type: "{0}"

Cause: An invalid or unknown resource type was supplied.

Action: Specify a valid resource type.
Level: 1

Type: ERROR

Impact: Security

OSB-386027: Expected resource type: {0}

Cause: The resource type supplied did not match the expected type.

Action: Verify a valid resource type was supplied and contact Oracle support.
Level: 1

Type: ERROR

Impact: Security

OSB-386028: Expected resource key: {0}

Cause: The resource identifier supplied does not contain the expected key.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

OSB-386029: Unknown resource key: {0}

Cause: The resource key supplied in the resource data is unknown.

Action: Specify only resource keys valid for a specific resource type.
Level: 1

Type: ERROR

Impact: Security

OSB-386030: Invalid application name

Cause: The application name parameter was empty or contains invalid values.

Action: Specify a valid application name.
Level: 1

Type: ERROR

Impact: Security

OSB-386031: Invalid component name

Cause: The component name parameter was empty or contains invalid values.

Action: Specify a valid component name.
Level: 1

Type: ERROR

Impact: Security

OSB-386032: Illegal application search name

Cause: The application name was not a legal search string.

Action: Specify a valid application name search string.
Level: 1

Type: ERROR

Impact: Security

OSB-386033: Illegal component search name

Cause: The component name was not a legal search string.

Action: Specify a valid component name search string.
Level: 1

Type: ERROR

Impact: Security

OSB-386034: No component type

Cause: The component type parameter is empty.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

OSB-386035: Invalid component type: "{0}"

Cause: The component type parameter specified is not valid.

Action: Specify a valid component type of EJB, WebApp, Connector or WebService.
Level: 1

Type: ERROR

Impact: Security

OSB-386036: Empty array value found

Cause: An empty string was supplied for an array element of the resource key.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

OSB-386037: Unexpected resource identifier data: "{0}"

Cause: The resource identifier supplied contains unexpected data.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

OSB-386038: Unexpected resource key array value: "{0}"

Cause: An unexpected value was supplied for a resource key array.

Action: Specify a valid resource identifier.
Level: 1

Type: ERROR

Impact: Security

OSB-386039: Empty {0} resource {1} string

Cause: An empty string was supplied for an element of the resource.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

OSB-386040: Empty {0} resource {1} array string

Cause: An empty string was supplied for an array element of the resource.

Action: Specify a valid string.
Level: 1

Type: ERROR

Impact: Security

OSB-386041: key-pair binding with alias "{1}" and purpose "{2}", but there is no such key-pair binding in the PKI Credential Mapper Provider in your security realm

Cause: In older release of ALSB (2.0 and 2.1), ALSB did not include the password to service key provider key-pair credentials in exported configuration jar files. When such a service key provider is later imported into subsequent releases, OSB expects the key-pair binding to already be present in the PKI Credential Mapper Provider. To do that, you would export the PKI Credential Mapper Provider data from your previous domain and import it into your new domain. NOTE: It is recommended that you instead re-configure this service key provider credentials, that way OSB will keep an encrypted copy of the key-pair's password and this error will not happen again

Action: Either import the PKI Credential Mapper provider data or reconfigure the service key provider's credentials in the OSB console
Level: 1

Type: ERROR

Impact: Security

OSB-386042: Mapped service account "{0}" is invalid: the remote-user table is invalid, there are multiple entries with username "{1}"

Cause: The remote user table in a mapped service account cannot have multiple entries with the same username

Action: Edit the mapped service account and remove the duplicate entry
Level: 1

Type: ERROR

Impact: Security

OSB-386043: Service Key Provider "{0}" has a WSS X.509 Token credential and a Digital Signature credential, and they refer to different keys. WSS X.509 credentials have been deprecated. You must remove the WSS X.509 credential.

Cause: WSS X.509 credentials have been deprecated. You must remove the WSS X.509 credential.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386100: Authentication failed

Cause: Authentication failed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386101: Missing authentication token

Cause: Missing authentication token

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386102: Message-level authorization denied

Cause: Message-level authorization denied

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386200: General web service security error

Cause: General web service security error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386201: A web service security fault occurred

Cause: A web service security fault occurred

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386400: General outbound web service security error

Cause: General outbound web service security error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386401: Failed to convert outbound message to SOAP

Cause: Failed to convert outbound message to SOAP

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386402: Cannot determine the outbound operation

Cause: Cannot determine the outbound operation

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386415: Could not enforce access control policy: {0}

Cause: Failed to enforce access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386417: Could not get the Authorization Manager

Cause: Failed to get the Authorization Manager

Action: Contact Oracle Support Services
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-386420: A web service security error ocurred while producing security header

Cause: A web service security error ocurred while producing security header

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386440: A web service security error occurred while processing the security header

Cause: A web service security error occurred while processing the security header

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386460: Web service security policy validation error

Cause: Web service security policy validation error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386800: Could not find Authorization Provider ${0}

Cause: Failed to get the Authorization Provider.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386801: An error occurred while activating access control changes for proxy "{0}".

Cause: Error while activating the access control changes.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386802: An error occurred while removing access control policy from provider "{0}" with resource id "{1}".

Cause: Error removing access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386803: An error occurred while removing access control policy from provider "{1}" for service "{0}" at scope "{2}".

Cause: Error removing access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386804: An error occurred while finding access control policy from provider "{0}" with resource id "{1}".

Cause: Error finding access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386805: An error occurred while finding access control policy from provider {1} for service {0} at scope {2}.

Cause: Error finding access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386806: An error occurred while adding access control policy to provider "{0}" with resource id "{1}".

Cause: Error adding access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386807: An error occurred while adding access control policy to provider "{1}" for service "{0}" at scope "{2}".

Cause: Error adding access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386808: An error occurred while setting access control policy expression on provider "{0}" with resource id "{1}".

Cause: Error setting access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386809: An error occurred while setting access control policy expression on provider "{1}" for service "{0}" at scope "{2}".

Cause: Error setting access control policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386810: Policy for resource id "{1}" already exists in provider "{0}".

Cause: Duplicate policy found.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386820: Argument "{0}" has an invalid value "{1}".

Cause: Invalid argument specified.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386830: Invalid access control policy expression "{3}" for service "{0}" at "{1}" level for provider "{2}".

Cause: Invalid access control policy expression specified.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386831: Multiple policies found for provider "{2}" for service "{0}" at scope "{1}".

Cause: Update the service to have only one policy from a provider at the given scope.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386832: Access control policy found for invalid operation "{1}" for service "{0}".

Cause: Access control policy applied on an invalid operation.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386833: Multiple policy entry found for same operation "{1}" for service "{0}".

Cause: Multiple policy entry found for same operation for a service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386834: Access control policy found for non-existing provider "{1}" in service "{0}".

Cause: Access control policy found for non-existing provider.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386835: Access control policy found for non-existing operation "{1}" in service "{0}".

Cause: Access control policy found for non-existing operation.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386836: Unnecessary proxy wide message access control policy found for service "{0}".

Cause: Hint: The service is neither an active security intermediary nor has custom authentication enabled.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386837: Unnecessary operation specific message access control policy found for operation "{1}" on service "{0}".

Cause: Hint: The service is not WSDL based.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386838: Unnecessary operation specific message access control policy found for service "{0}".

Cause: Hint: The service is neither an active security intermediary nor has custom authentication enabled.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386839: Message level access control policy found for non-existing operation "{1}" on service "{0}".

Cause: Message level access control policy found for non-existing operation.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386840: Invalid authorization provider "{2}" found in service "{0}" at "{1}".

Cause: Invalid authorization provider specified.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-386841: Authorization provider "{0}" does not exist.

Cause: Authorization provider does not exist. Please check the provider.

Action: Authorization provider does not exist. Please check the provider.
Level: 1

Type: ERROR

Impact: Security

OSB-387000: Failed to initialize Authorization Helper

Cause: Failed to initialize Authorization Helper

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387001: No Policy Editor available

Cause: No Policy Editor available

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387004: Policy deployment for resource {0} failed: {1}

Cause: Error occured during policy deployment.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387008: Failed to get WssPolicyCtx from service {0}

Cause: Failed to get WssPolicyCtx.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387009: Failed to convert message context to SOAPMessage

Cause: Failed to convert message context to SOAPMessage.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387010: Failed to store new SOAPMessage in router's message context

Cause: Failed to store new SOAPMessage in router's message context.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387011: Failed to get the effective request policy for operation {1} for service {0}

Cause: Check the policies attached.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387012: Failed to get the effective response policy for operation {1} for service {0}

Cause: Check the policies attached.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387013: Failed to get the endpoint URL for service {0}

Cause: Failed to get the endpoint URL for service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387014: The request could not be mapped to one of the operations exposed by the service

Cause: Failed to map request to operation on the service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387015: Failed to get the outbound operation name from the router's message context

Cause: Failed to get the outbound operation name from the router's message context

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387016: There is no target operation set on the outbound endpoint, the operation must be set in order to fetch the appropriate policy, set the operation in the message context

Cause: There is no target operation set on the outbound endpoint, the operation must be set in order to fetch the appropriate policy, set the operation in the message context

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387018: Unexpected ProviderNotFoundException while deleting user/password credentials for service account {0}

Cause: Unexpected Error while deleting credentials in service account

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387019: Unexpected ProviderNotFoundException while deleting PKI credentials for service key provider {0}

Cause: Exception while deleting PKI credentials for service key provider.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387022: An error occurred during web service security inbound request processing [error-code: {0}, message-id: {1}, proxy: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387023: An error occurred during web service security inbound response processing [error-code: {0}, message-id: {1}, proxy: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387024: An error occurred during web service security outbound request processing [error-code: {0}, message-id: {1}, service: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387025: An error occurred during web service security outbound response processing [error-code: {0}, message-id: {1}, service: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387026: An internal web service security error occurred [error-code: {0}, message-id: {1}, service: {2}, operation: {3}]--- Error message:{4}

Cause: Check the stacktrace for the error.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387028: Message-level access control policy denies access to proxy "{0}", operation "{1}", message-id: {2}, subject: {3}.

Cause: Message-level access control policy denied.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387029: An error happened while incrementing monitoring counter "{0}" [message-id: {1}, service: {2}, operation: {3}]

Cause: Check the stacktrace to find the cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387030: Cannot read SerializedMS.dat: an IOException was thrown while reading data from {0}.

Cause: Cannot read SerializedMS.dat: an IOException thrown while reading the data.

Action: Contact Oracle Support Services
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387031: SerializedMS.dat error: version mismatch, path: {0}. The version of the SerializedMS.dat file is not the supported version. Got version {1}, expected version {2}.

Cause: Verify that the SerializedMS.dat file has not been corrupted.

Action: Contact Oracle Support Services
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387032: Error opening SerializedMS.dat: {0}. A FileNotFoundException was thrown while opening the input stream.

Cause: Verify that the SerializedMS.dat file exists and is accessible. Read the exception text for more information on diagnosing the problem.

Action: Contact Oracle Support Services
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387033: Error closing SerializedMS.dat: {0}. An IOException was thrown on the close of the input stream while reading the SerializedMS.dat file. Verify that the SerializedMS.dat file is valid. Read the exception text for more information on diagnosing the problem.

Cause: An IOException was thrown on the close of the input stream while reading the SerializedMS.dat file. Verify that the SerializedMS.dat file is valid. Read the exception text for more information on diagnosing the problem.

Action: Contact Oracle Support Services
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387034: Could not create temporary file for {0} , .new, {1}

Cause: When creating a temporary file, an IOException was thrown by the File.createTempFile method.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

OSB-387035: Could not create temporary file for {0}, .old, {1}

Cause: When creating a temporary file, an IOException was thrown by the File.createTempFile method and the temp file could not be created.

Action: Verify the filename and directory. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

OSB-387036: Could not clear temporary file {0}

Cause: The temporary file could not be deleted.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

OSB-387037: Could not rename {0} to {1}

Cause: The temporary file could not be renamed.

Action: Verify that the file can be renamed and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

OSB-387038: Could not delete {0}

Cause: The temporary file could not be deleted.

Action: Verify that the file can be deleted and is not locked by some other process.
Level: 1

Type: ERROR

Impact: Security

OSB-387039: Error creating {0}

Cause: When writing a file using a FileOutputStream, a FileNotFound exception was thrown. Either the file does not exist, the file is a directory rather than a regular file, or the file cannot be opened for reading.

Action: Verify the filename. Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

OSB-387040: Error writing to file {0}

Cause: When writing a file using a FileOutputStream, an IOException was thrown.

Action: Read the exception text for more information on diagnosing the problem.
Level: 1

Type: ERROR

Impact: Security

OSB-387041: There are more than one user password credential mapper providers configured in your security realm. Oracle Service Bus supports at most one user password credential mapper. OSB service account management will be disabled. Review your realm configuration and make sure there is at most one provider.

Cause: There are more than one user password credential mapper providers configured in your security realm. Oracle Service Bus supports at most one user password credential mapper. OSB service account management will be disabled. Review your realm configuration and make sure there is at most one provider.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387042: There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.

Cause: There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387043: The user password credential mapper provider configured in your security realm does not implement UserPasswordCredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider that supports writes if you need OSB service account support.

Cause: The user password credential mapper provider configured in your security realm does not implement UserPasswordCredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider that supports writes if you need OSB service account support.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387044: Invalid service account {0}: the service account does not have a name

Cause: Specify a valid name to the Service Account.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387045: Invalid service account {0}: the service account does not have a type

Cause: Create a service account of valid type

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387046: Invalid service account type: {0}

Cause: Create a service account of valid type

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387047: Invalid static service account {0}: the service account does not have a username/password

Cause: Static service account should have a username/password

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387048: Invalid static service account {0}: the username is null

Cause: Static service account should have a valid username.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387049: Invalid static service account {0}: the username is invalid

Cause: Static service account should have a valid username.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387050: Invalid static service account {0}: the password is null

Cause: Static service account should have a valid password.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387051: Invalid static service account {0}: the password is invalid

Cause: Static service account should have a valid password.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387052: Invalid mapper service account {0}: the service account does not have any user mapping entries or an anonymous mapping

Cause: Mapper service account should have valid user mapping entries or an anonymous mapping

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387053: Invalid mapper service account {0}: local username in user mapping is null

Cause: Mapper service account should have a valid local username in user mapping

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387054: Invalid mapper service account {0}: local username is invalid

Cause: Mapper service account should have a valid local username in user mapping

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387055: Invalid mapper service account {0}: the map has an entry with a null remote username/password

Cause: Mapper service account should have a valid remote username/password

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387056: Invalid mapper service account {0}: the map has an entry with a null remote username

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387057: Invalid mapper service account {0}: the map has an entry with an invalid remote username

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387058: Invalid mapper service account {0}: the map has an entry with a null remote password

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387059: Invalid mapper service account {0}: the map has an entry with an invalid remote password

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387060: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote username on the anonymous mapping is null

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387061: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote username on the anonymous mapping is invalid

Cause: Mapper service account should have a valid remote username

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387062: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote password on the anonymous mapping is null

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387063: Invalid mapper service account {0}: the service account has an anonymous mapping but the remote password on the anonymous mapping is invalid

Cause: Mapper service account should have a valid remote password

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387066: An error occurred while activating changes for service account {0}.

Cause: This is an unexpected error. Check the logs for more details.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387067: There are more than one PKI credential mapper providers configured in your security realm. Oracle Service Bus supports at most one PKI credential mapper. OSB service key provider management will be disabled. Review your realm configuration and make sure there is at most one PKI credential mapper provider.

Cause: There are more than one PKI credential mapper providers configured in your security realm. Oracle Service Bus supports at most one PKI credential mapper. OSB service key provider management will be disabled. Review your realm configuration and make sure there is at most one PKI credential mapper provider.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387069: The PKI credential mapper provider configured in your security realm does not implement PKICredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service key provider management will be disabled. Configure a PKI credential mapper provider that supports writes if you need OSB service provider support. This is typically the case if you have OSB proxies with web service security enabled or outbound 2-way SSL connections.

Cause: The PKI credential mapper provider configured in your security realm does not implement PKICredentialMapEditorMBean. This is a read-only provider. Oracle Service Bus service key provider management will be disabled. Configure a PKI credential mapper provider that supports writes if you need OSB service provider support. This is typically the case if you have OSB proxies with web service security enabled or outbound 2-way SSL connections.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387072: An error occurred while persisting the changes for service key provider {0} to credential mapping provider {1}. The PKI credentials associated with service providers are now in an inconsistent state. This requires immediate attention. Error: {3}

Cause: See the stacktrace for additional information.

Action: Contact your Oracle representative.
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387073: Invalid service key provider {0}: missing key-alias for {1} key

Cause: Service key provider should have valid key-alias for all keys.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387074: Invalid service key provider {0}: invalid key-alias for {1} key

Cause: Service key provider should have valid key-alias for all keys.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387075: Invalid service key provider {0}: missing key-password for {1} key

Cause: Service key provider should have valid key-password for all keys.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387076: Invalid service key provider {0}: invalid key-password for {1} key

Cause: Service key provider should have valid key-password for all keys.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387077: Invalid 21 compatibility resource id in service key provider {0} for {1} key: {2}

Cause: Invalid 21 compatibility resource id in service key provider

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387078: Failed to bind key-pair credential for service key provider {0} and purpose {1}: {2}

Cause: Check the logs to diagnose the error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387079: Failed to bind key-pair credential for service key provider {0} for digital signature purposes: the certificate does not support digital signatures. Key-alias: {1}

Cause: Specify valid certificate which supports the digital signature.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387080: Failed to bind key-pair credential for service key provider {0} for encryption purposes: the certificate does not support encryption. Key-alias: {1}

Cause: Specify valid certificate which supports the digital encryption.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387081: Error in service key provider "{0}": could not read a certificate under keystore alias "{1}" for purpose "{2}"

Cause: Check the stacktrace to diagnose the error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387082: Proxy service access denied (proxy: {0}, subject: {1})

Cause: Check the accenss control policy for the proxy service

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387095: [Policy Migration] [proxy service: {0}] [authorization provider: {1}] The 2.1 policy cannot be migrated because it makes use of policy predicates which are specific to URLResource. A deny-all policy will be bound to the proxy. You must re-configure this policy in the console.

Cause: The 2.1 policy cannot be migrated because it makes use of policy predicates which are specific to URLResource. A deny-all policy will be bound to the proxy. You must re-configure this policy in the console.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387096: Oracle Service Bus could not determine if the default ALSBProxyServiceResource policy is present or not because some authorization providers do not implement PolicyReaderMBean. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. If the policy is indeed missing, the administrator must create it.

Cause: Oracle Service Bus could not determine if the default ALSBProxyServiceResource policy is present or not because some authorization providers do not implement PolicyReaderMBean. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. If the policy is indeed missing, the administrator must create it.

Action: Contact Oracle Support Services
Level: 14

Type: INCIDENT_ERROR

Impact: Security

OSB-387097: Oracle Service Bus has determined the default ALSBProxyServiceResource policy is missing. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. Access to all OSB proxy services will be denied. The administrator must create the policy using the provider tools.

Cause: Oracle Service Bus has determined the default ALSBProxyServiceResource policy is missing. OSB could not deploy the policy because neither EntitleNet provider nor XACML provider is present. Access to all OSB proxy services will be denied. The administrator must create the policy using the provider tools.

Action: Contact Oracle Support Services
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-387099: Service Key Provider "{0}" has a WSS X.509 Token credential. WSS X.509 credentials have been deprecated. You must configure a Digital Signature credential instead.

Cause: WSS X.509 credentials have been deprecated. You must configure a Digital Signature credential instead.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387100: Service "{0}" is configured as No Policies, but policies have been found in the service definition.

Cause: Service is configured as No Policies, but policies have been found in the service definition.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387102: Exception in {0}, {1}

Cause: A general runtime error has occured during OSB's OWSM support initialization

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387105: Exception in {0}, continuing, {1}

Cause: This is an informational message that is logged during the OSB's OWSM support initialization process when a non-fatal exception occurs

Action: No action is necessary
Level: 1

Type: ERROR

Impact: Security

OSB-387176: OWSM Policies can't be bounded at the Operation level

Cause: Attaching OWSM Policies at the Operation Level is not supported by OWSM. Policies can be attached only at the service level currently.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387177: OWSM Policy {0} is not supported.

Cause: This Policy is not supported. Refer OSB documentation on list of supported policies.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387178: An error occurred while computing the web service policy for service {0}: {1}

Cause: An error occurred while computing the web service policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387179: OWSM Policies are not supported on WSRM Transport

Cause: OWSM Policies are not supported on WSRM Transport

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387180: OSB does not support attaching OWSM MTOM/no-MTOM Policy on Proxy/Business Service. Please delete these OWSM Policies. For MTOM support in OSB enable MTOM configuration on the Pipeline/Business Service.

Cause: OSB does not support attaching OWSM MTOM/no-MTOM Policy on Proxy/Business Service. Please delete these OWSM Policies. For MTOM support in OSB enable MTOM configuration on the Pipeline/Business Service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387181: This service can not have both WebLogic Server 9.X-style security policies and owsm policies

Cause: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy along with the OWSM policies.

Action: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy along with the OWSM policies.
Level: 1

Type: ERROR

Impact: Security

OSB-387182: This service can not have both OWSM security policies and a service account

Cause: Service account can not be configured on a service attached with OWSM policies.

Action: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy along with the OWSM policies.
Level: 1

Type: ERROR

Impact: Security

OSB-387187: OWSM Policy Support is not available in this environment. Upgrade your domain if you need OWSM Policy support. Please see documentation on how to upgrade your domain.

Cause: OWSM Policy Support is not available in this environment. Upgrade your domain if you need OWSM Policy support. Please see documentation on how to upgrade your domain.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387189: OWSM Policy ''{0}'' is not allowed on ''{1}'' transport.

Cause: Refer OSB documentation for supported policies on the transport.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387190: OWSM Policy ''{0}'' is not allowed since transport authentication is set to ''None''. If you are trying to attach an HTTP Token Policy make sure the transport authentication is set to Basic Authentication.

Cause: OWSM transport policies attached have to match with the transport configuration for the service. If you are trying to attach an HTTP Token Policy make sure the transport authentication is set to Basic Authentication.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387191: OWSM Policy ''{0}'' is not allowed since transport authentication is set to ''{1}''. Authentication method on the policy conflicts with the configuration on the transport.

Cause: Update the policies to match the transport configuration of the service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387194: OWSM Policy ''{1}'' is not allowed since transport authentication is set to ''{0}''. If you are trying to attach an HTTP Token Policy make sure that the authentication on transport configuration is set to ''None''. You can either set the authentication mechanism directly on the transport configuration page or attach OWSM HTTP Token Policy.

Cause: If you are trying to attach an HTTP Token Policy make sure that the authentication on transport configuration is set to ''None''. You can either set the authentication mechanism directly on the transport configuration page or attach OWSM HTTP Token Policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387195: OWSM Policy ''{0}'' contains unsupported authentication method ''{1}''. Only ''Basic'' , ''SPNEGO'' and ''HTTP SAML 2.0 Bearer Token'' authentications are supported with OWSM policy.

Cause: Edit OWSM policy in Enterprise Manager and change the authentication mechanism to ''Basic'' , ''SPNEGO'' or ''HTTP SAML 2.0 Bearer Token''. For any other authentication method, directly configure on the transport and do not attach any OWSM HTTP Token policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387196: The service has both OWSM Transport Policy ''{0}'' and transport level access controls. This combination is not supported. If OWSM Transport Policy is used, OWSM authorization policy should be used.

Cause: Solution: Either remove OWSM Transport Policy and replace that intent by configuring authentication directly on the transport OR remove transport ACLs from the Security page and replace them with OWSM Authorization Policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387197: The service has OWSM Transport Policy ''{0}'' with transport security enabled but HTTPS is not enabled on this service.

Cause: This combination is not supported. Please enable ''HTTPS Required'' on transport configuration page OR disable transport security on the OWSM policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387198: The service has OWSM Transport Policy ''{0}'' with mutual authentication (TWO WAY SSL) enabled.

Cause: This configuration is not supported. Please disable the mutual authentication on the OWSM policy.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387201: The service has OWSM Transport Policy ''{0}'' with Include Timestamp enabled. This configuration is not supported. Please disable the Include Timestamp attribute on the OWSM policy.

Cause: The service has OWSM Transport Policy with Include Timestamp enabled. This configuration is not supported.

Action: Disable the Include Timestamp attribute for the policy from EM
Level: 1

Type: ERROR

Impact: Security

OSB-387203: The business service does not have a STS configuration policy attached

Cause: (any soap) business service with STS issue token policy does not have STS configuration policy

Action: Attach a STS Configuration policy to the business service
Level: 1

Type: ERROR

Impact: Security

OSB-387204: STS information is missing from the attached WSDL and the business service does not have a STS configuration policy attached

Cause: (soap) business service with STS issue token policy does not have STS information available

Action: Attach a STS Configuration policy to the business service, or attach a WSDL with STS information present
Level: 1

Type: ERROR

Impact: Security

OSB-387207: HTTP proxy/business service can not have both AT(atomic_transaction) and RM(reliable_messaging) policies together.

Cause: HTTP service can not be configured with both AT and RM policies.

Action: Either AT(atomic_transaction) or RM(reliable_messaging) policy but not both can be applied to a HTTP poxy/business services.
Level: 1

Type: ERROR

Impact: Security

OSB-387211: HTTP proxy/business service can not have RM(reliable_messaging_policy) policy.

Cause: HTTP service can not be configured with RM policy.

Action: To enable RM, system property with name com.oracle.osb.disi.rm.enabled must be set with its value as true.
Level: 1

Type: ERROR

Impact: Security

OSB-387212: HTTP proxy/business service with RM(reliable_messaging_policy) policy should also have (reliable_messaging_internal_api_policy) policy.

Cause: HTTP service with incomplete RM policy.

Action: Add (oracle/reliable_messaging_internal_api_policy) policy along with (reliable_messaging_policy) policy.
Level: 1

Type: ERROR

Impact: Security

OSB-387251: Policy ID {0} is not supported.

Cause: This policy is not supported by OSB. Refer to the documentation for list of supported policies.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387252: Multiple policies found for given policy ID {0}.

Cause: Remove the duplicate policies.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387253: Failed to validate OWSM credentials due to the following error: {0}

Cause: This is an informational message that is logged during the OSB's OWSM support' config overrides validation process when a non-fatal exception occurs. Skipping config overrides validation as OSB failed to access the configured Keystore and Credential Store. Refer to OWSM documentation for details on Keystore and Credential Store configuration.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387254: Failed to validate the Override Value "{0}" due to the following error: {1}

Cause: This is an informational message that is logged during the OSB's OWSM support config overrides validation process when a non-fatal exception occurs.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387256: Invalid CSF Key ''{1}'' set for override ''{0}''. This CSF Key does not exist in the Credential Store.

Cause: This is an informational message that is logged during the OSB's OWSM support config overrides validation process when a non-fatal exception occurs.

Action: Update the Credential Store with the required CSF Key.
Level: 1

Type: ERROR

Impact: Security

OSB-387257: Invalid Recepient Alias "{0}" specified.

Cause: This is an informational message that is logged during the OSB's OWSM support config overrides validation process when a non-fatal exception occurs.

Action: Update the keystore with the required certificate.
Level: 1

Type: ERROR

Impact: Security

OSB-387258: Invalid Value {1} specified for {0}. Valid values are {2}.

Cause: Invalid version specified.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387259: Invalid wssp value "{1}" specified for wsp: "{0}". Valid wssp values are: "{2}".

Cause: Invalid combination of wssp and wsp versions specified.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387260: Query parameters "wsp" and "wssp" are not supported for ORAWSDL.

Cause: ORAWSDL does not support "wsp" and "wssp" parameters.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Security

OSB-387301: Unexpected error happened in the JEJB Transport at {0} due to {1}

Cause: An internal error occurred. It is due to either an unrecoverable failure during a configuration update or a runtime error during message processing

Action: If this error happened during a configuration update, check that your JEJB transport services are not corrupted. In case of corrupted configuration, manually clean up the failed services or restart your server. For other errors, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-387302: Could not create connection with proxy service {0} due to {1}

Cause: An error happened while trying to lookup the JEJB Transport proxy service RMI stubs

Action: Verify that your JNDI context host, port and credentials are correct. Also check that protocol used by the JNDI context is supported and enabled. For instance, IIOP/IIOPS protocols are not supported between WebLogic Server, and HTTP/HTTPS protocols requires HTTP tunneling
Level: 1

Type: ERROR

Impact: Other

OSB-387303: Could not invoke proxy service {0} due to {1}

Cause: An Remote Exception happened while trying to invoke the JEJB Transport proxy service via RMI

Action: Check your that network connection, destination server and port are up. Also, check that the remote proxy service still exists
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387304: Could not generate plan {0} due to {1}

Cause: An internal error occurred while creating a proxy services with a custom dispatch policy. The deployment plan for this proxy artifact could not be created

Action: The message body should give you more details about the error. This could be caused by a I/O Exception or because the location of the deployment plan write-protected.
Level: 1

Type: ERROR

Impact: Deployment

OSB-387305: Unsupported payload type {0}

Cause: An internal error occurred during the message processing: the payload associated with the message is not supported by the JEJB Transport

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387306: Method: {0} is not exposed through JEJB inbound service for invocation.

Cause: This method is not exposed by the JEJB proxy service for invocation.

Action: Please check the proxy service configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387307: Method: {0} is not exposed through JEJB business service for invocation.

Cause: This method is not exposed by the JEJB business service for invocation.

Action: Please check the business service configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387308: Corresponding OSB service is in disabled state.

Cause: Corresponding OSB service is in disabled state.

Action: Please enable the corresponding proxy service.
Level: 1

Type: ERROR

Impact: Configuration

OSB-387309: Following Response payload to the inbound JEJB service is not properly formed: {0}

Cause: Response payload to the inbound JEJB service is not properly formed.

Action: Response message should be modeled as the SOAP message with operation name as the sub-elements. Please refer to the generated wsdl for the message structure.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387310: Following Request payload to the outbound JEJB service is not properly formed: {0}

Cause: Request payload to the outbound JEJB service is not properly formed.

Action: Request message should be modeled as the SOAP message with operation name as the sub-elements. Please refer to the generated wsdl for the message structure.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387311: Parameter: {0} with class name: {1} could not be loaded

Cause: Parameter received from the payload could not be loaded.

Action: Please look at the exception message for the reason. Refer to the generated wsdl for the message structure.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387312: No object is registered for ref ''{0}''

Cause: An attempt to look up an object in Java object repository with the specified reference failed. This may have occurred to due a previously executed pipeline action that deleted the object with the corresponding reference.

Action: Check the pipeline message flow configuration to make sure there is no pipeline action that deletes the object with the specified reference that executes prior to this error.
Level: 1

Type: ERROR

Impact: Other

OSB-387313: Colocated call is not supported by JEJB transport provider.

Cause: Colocated call is not supported by JEJB transport provider.

Action: Colocated calls are not supported by JEJB transport provider. Please route the pipeline message to JEJB business service.
Level: 1

Type: ERROR

Impact: Configuration

OSB-387314: JNDI Provider: {0} could not be retrieved due to {1}

Cause: JNDI Provider could not be retrieved due to an unexpected error.

Action: Please look at error message for the reason. If problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

OSB-387315: JNDI Provider: {0} not found

Cause: JNDI Provider does not exists in OSB

Action: Please make sure that a valid JNDI Provider is configured with the given name.
Level: 1

Type: ERROR

Impact: Configuration

OSB-387316: Unexpected error while creating or updating the JEJB Service due to {0}

Cause: Unexpected error while creating or updating the JEJB Service due to {0}

Action: Please look at the error for the actual reason.
Level: 1

Type: ERROR

Impact: Deployment

OSB-387317: Could not find an existing JNDI provider with one of the following URIs: {0}

Cause: Could not find an existing JNDI provider with one of the following URIs: {0}

Action: While importing the JEJB service from UDDI, JEJB Transport Provider looks for existing JNDI provider with the same host and port as mentioned in the access point of the imported service. Make sure that a JNDI provider is already created at the time of importing the service. Please refer to the documentation for more details.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-387318: Java object received from the pipeline message with type: {0} cannot be converted to the expected type: {1}

Cause: Java object received from the pipeline message cannot be converted to the expected type.

Action: Please check the pipeline logic. Java object received from the pipeline message cannot be converted to the expected type as defined in the ejb interface.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-390003: Child resource {0} is not associated with a parent resource

Cause: Child resource is not associated with a parent resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-390004: Child resource {0} is associated with more than one parent resource

Cause: More than one resource instance contains a reference to a child instance. Instances of resources that are defined as Child types can only be references by instances of resources that are defined as Parent types, through parent-child references. Update references in the parent instances or delete one of the parent instances so that only one has a child reference to the child resource.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-390005: Dangling child reference from {0} to {1}

Cause: Dangling child reference from parent.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-390006: Parent resource {0} has multiple containments of child resource {1}. Containment names: {2}

Cause: A parent resource can reference a child resource only once.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-390013: Execution record for the given task was not found

Cause: An attempt is made to undo a previous change, but the information about the change, is not found. No execution record was found with the task id supplied by the user. The task id may be invalid, or the execution record may have been purged by the admin

Action: Make sure you are using the correct task id.
Level: 1

Type: ERROR

Impact: Data

OSB-390014: Change has already been undone

Cause: An attempt is made to undo a previous change twice.

Action: No action is necessary
Level: 1

Type: ERROR

Impact: Other

OSB-390015: No undo record found for task

Cause: An attempt is made to undo a previous change, but the change cannot be undone. Certain internal changes initiated by the server cannot be undone.

Action: No action is necessary
Level: 1

Type: ERROR

Impact: Data

OSB-390018: Undo cannot be completed because the changes have errors. See log file for details

Cause: Undo cannot be completed because the changes have errors. See log file for details

Action: Inspect the error log, and if there are validation errors in resources, attempt to fix them.
Level: 1

Type: ERROR

Impact: Other

OSB-390019: No exec records for session {0}

Cause: Unexpected error due to a failed session activation

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Session

OSB-390101: Activation of session {0} failed: {1}

Cause: Activation of session failed. The exception should provide more detail.

Action: Inspect the error message and try to fix any validation errors or add systems resources that are missing.
Level: 1

Type: ERROR

Impact: Session

OSB-390103: Failed to discard session {0} after successful activation: {1}

Cause: Failed to discard session after successful activation. The exception should provide more detail.

Action: Retry the discard operation.
Level: 1

Type: ERROR

Impact: Session

OSB-390104: Failed to create WLS change list for activation of session {0}: {1}

Cause: Session activation requires a lock on WLS configuration to perform any deployments that are required by the resources. However the lock could not be obtained Another session activation may be in progress, or another user may have already started a WLS change list and holding the lock.

Action: If another session activation is already in progress, wait until the activation finishes. If another user is holding the lock, contact the user.
Level: 1

Type: ERROR

Impact: Session

OSB-390105: Unable to create WLS change list due to a short term automatic lock obtained by user {0}. The user has no pending changes and the lock will expire in {1} seconds. Please try again after the lock has expired.

Cause: Session activation requires a lock on WLS configuration to perform any deployments that are required by the resources. In this case the lock is obtained automatically by WLS console on behalf of the user. The lock is obtained regardless of any changes, and will expire in a short time.

Action: Wait until the lock expires or the other user explicitly releases the lock, and try again.
Level: 1

Type: ERROR

Impact: Session

OSB-390106: Failed to cancel WLS change list: {0}

Cause: An unexpected error occurred when cancelling WLS changes after a failed session activation

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Session

OSB-390108: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred: {0}

Cause: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred. The message should provide more detail.

Action: Retry the activation.
Level: 1

Type: ERROR

Impact: Session

OSB-390109: Failed to notify session listener {1} for operation {2} on session {0}

Cause: An unexpected error occured when activating changes.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Session

OSB-390111: Another session operation is in progress. Please retry later.

Cause: Another session operation is in progress. Please retry later.

Action: Retry the session activation after the other activation finishes
Level: 1

Type: ERROR

Impact: Session

OSB-390112: No session was specified.

Cause: Certain configuration APIs work only in a session, but no session name is passed in the arguments.

Action: Make sure you provide the session name.
Level: 1

Type: ERROR

Impact: Session

OSB-390113: Resource {0} was not modified in session {1}, therefore cannot sync to the core data.

Cause: An attempt is made to sync to the core changes for a resource that has not been modified in a session. If a resource is modified both in a session, and in the core (via the activation of another session), two versions of the resource conflict. The user can either choose to overwrite core changes simply by activating the session, or sync to the core changes, effectively discarding his own changes.

Action: Make sure you invoke sync operation on a resource that is modified in the session.
Level: 1

Type: ERROR

Impact: Session

OSB-390114: Deployed configuration state has changed while creating a session. Please try creating the session again.

Cause: Deployed configuration state has changed while creating a session. Please try creating the session again.

Action: Retry session creation.
Level: 1

Type: ERROR

Impact: Deployment

OSB-390115: Failed to save WLS changes for session {0}

Cause: WLS changes that are made in response to a session activation has failed

Action: Inspect the error messages from WLS and consult WLS documentation
Level: 1

Type: ERROR

Impact: Deployment

OSB-390116: Failed to release WLS Edit session lock: {0}

Cause: Failed to release WLS Edit session lock. The exception should provide more detail.

Action: No action is necessary
Level: 1

Type: ERROR

Impact: Session

OSB-390117: Failed to instantiate core: {0}

Cause: Unexpected error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-390118: Failed to instantiate session: {0}

Cause: Failed to instantiate session. The exception should provide more detail.

Action: Retry session creation
Level: 1

Type: ERROR

Impact: Session

OSB-390119: Failed to set session description: {0}

Cause: Failed to set session description. The exception should provide more detail.

Action: Make sure you provided the correct session name
Level: 1

Type: ERROR

Impact: Session

OSB-390120: Failed to notify session {0} of core changes: {1}

Cause: When a session is activated, the changes are propagated to other sessions, causing them to absorb the changes and revalidate their own content if necessary. An unexpected error occured while the changes are propagated.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Session

OSB-390121: Session {0} already exists

Cause: You are attempting to create a session that already exists.

Action: When creating a session programmatically, first check if a session with the same name exist. If so you can choose to use it or discard it. When using the console, make sure you are now using a stale view of the configuration by refreshing the page.
Level: 1

Type: ERROR

Impact: Session

OSB-390122: Cannot create session on a non-admin server

Cause: A programmatic attempt is made to create a session on a server other than the admin.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Session

OSB-390123: {0} is an invalid session name

Cause: Session names can contain java identifier characters, '-' or '.'.

Action: Use a session name that contains only the legal character, namely, java identifier characters, '-' or '.'
Level: 1

Type: ERROR

Impact: Session

OSB-390124: Session {0} cannot be discarded because it is being activated

Cause: An attempt is made to discard a session that is in the process of being activated

Action: If the activation is initiated accidentally, wait for the activation to finish successfully and undo the session activation.
Level: 1

Type: ERROR

Impact: Session

OSB-390125: Session {0} was not found

Cause: The session was not found.

Action: Make sure the correct session name is used.
Level: 1

Type: ERROR

Impact: Session

OSB-390206: Rollback failed due to errors

Cause: Rollback failed due to errors.

Action: Make sure you have the correct file permissions, or that you have enough space in file system
Level: 1

Type: ERROR

Impact: Other

OSB-390208: Commit failed due to errors

Cause: Commit failed due to errors

Action: Make sure you have the correct file permissions, or that you have enough space in file system
Level: 1

Type: ERROR

Impact: Other

OSB-390209: Failed to write to transaction file {0}

Cause: Failed to write to transaction file. The exception should provide more detail.

Action: Make sure you have the correct file permissions, or that you have enough space in file system
Level: 24

Type: INCIDENT_ERROR

Impact: Files

OSB-390210: Undo failed

Cause: Undo failed. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-390212: Cannot enlist transactional resource {0} when transaction is in {1} state

Cause: Cannot enlist transactional resource when transaction is in the given state.

Action: Retry the operation that caused this error
Level: 1

Type: ERROR

Impact: Other

OSB-390213: Cannot write transactional resource {0} when transaction is in {1} state

Cause: Cannot write transactional resource when transaction is in the given state.

Action: Retry the operation that caused this error
Level: 1

Type: ERROR

Impact: Other

OSB-390214: No transaction exists

Cause: No transaction exists.

Action: Retry the operation that caused this error
Level: 1

Type: ERROR

Impact: Other

OSB-390215: No file was found

Cause: Internal error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Files

OSB-390216: Attempting to read from a file that is marked for deletion, file: {0}

Cause: Internal error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Files

OSB-390300: Startup recoveryFailed

Cause: An attempt from a managed server to synchronize configuration with the admin server has failed.

Action: Inspect the errors and consult WLS documentation.
Level: 1

Type: ERROR

Impact: Disaster Recovery

OSB-390301: Failed to commit deployment

Cause: Failed to commit deployment. The exception should give more detail.

Action: Retry the deployment
Level: 1

Type: ERROR

Impact: Deployment

OSB-390302: Failed to cancel deployment

Cause: Internal error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-390303: Failed to prepare deployment

Cause: Session activation has failed in its prepare phase

Action: Inspect the errors and consult the documentation
Level: 1

Type: ERROR

Impact: Deployment

OSB-390501: No configuration has been uploaded or previously uploaded jar file has already been imported

Cause: An attempt is made to import an uploaded jar twice. An uploaded jar file is deleted from the internal staging area immediately after an import

Action: When importing the same jar twice, make sure you upload it for each time you want to import it
Level: 1

Type: ERROR

Impact: Data

OSB-390504: Invalid jar file

Cause: The jar file that is being imported is not a jar file that was previously exported.

Action: Make sure you are using a jar file that was previously exported. Check if the jar file is meant to be using for bulk import, and if so, use bulk import feature
Level: 1

Type: ERROR

Impact: Data

OSB-390505: The jar that is being imported is an unsupported version of the product. The version was {0}. Supported versions are: {1}

Cause: The jar that is being imported was created using a version of the product that is no longer supported.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-390506: Invalid actions defined for the following environment values: {0}

Cause: Invalid actions have been specified for some environment values.

Action: Only specify valid action for environment values.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394000: Exception on {0}, {1}

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394003: Failed to send alert to Alert Destination {2}. Resource: {0}. Alert Rule Name: {1}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394004: Failed to invoke action {3} that is part of alert destination {2}. Resource: {0}. Alert Rule Name: {1}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394005: Failed to send alert to reporting data set. Resource: {0}. Alert Rule Name: {1}. Alert Id: {2}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394006: Failed to generate SNMP trap. Resource: {0}. Alert Rule Name: {1}. Alert Id: {2}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394007: Failed to store alert in the alert log. Resource: {0}. Alert Rule Name: {1}. Alert Id: {2}.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394009: Failed to evaluate rules

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394030: Failed to shutdown SLA Alert Manager.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394031: Failed to shutdown Pipeline Alert Manager.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394032: Failed to shutdown Alert Log Manager.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394033: Failed to unbind AlertLogger.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394034: Failed while invoking command.

Cause: The exception should detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-394500: Error encountered while importing resource: {0}.

Cause: Error occured while importing resource from UDDI. Registry may be down or not accessible.

Action: Please check if the registry is running and try again.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394501: Error encountered while querying for businesses: {0}.

Cause: Error while querying the business entities in registry.

Action: Check if the registry is running and if you have permission to query the business entity.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394503: Error getting UDDI inquiry port : {0}.

Cause: Error while getting the inquiry port. Please check the Inquiry URL entered.

Action: Please check the Inquiry URL entered.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394505: Failed to connect to the UDDI registry.

Cause: Registry may be down or bad inquiry URL provided.

Action: Please verify if the registry is running and accessible. Ensure that the correct inquiry URI is provided.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394506: Error encountered while querying for business services: {0}.

Cause: Some error occured on UDDI registry while querying for the Business Service.

Action: Please check the error logs at UDDI registry.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394507: The registry name contains characters that are not allowed.

Cause: The registry name contains characters that are not allowed.

Action: Please remove the special characters from the registry name.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394510: {0} could not be imported. Please verify if the URI is available

Cause: Registry may be down or not accessible.

Action: Please verify the registry is accessible.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394511: Validation Exception occured on service creation

Cause: Valid failed.

Action: Check the conflicts in Change Center.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394512: User exception while importing repository

Cause: Internal error.

Action: Contact Oracle support.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394513: Repository ID {0} not present : {1}

Cause: Internal Error

Action: Contact Oracle support.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394517: Error getting xml value from InstanceParms : {0}

Cause: Instance Params as received from UDDI gave error while converting to XML.

Action: Verify the Instance params as present in UDDI registry.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394520: Error in AutoImport: {0}

Cause: An error occurred during AutoImport. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-394521: The Publish URL must be specified in order to publish tModels

Cause: Publish URL is not specified for the registry.

Action: Specify the Publish URL.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394522: The Security URL must be specified in order to publish tModels

Cause: Security URL not specified for the registry.

Action: Specify the Security URL.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394525: Error in AutoPublish: {0}

Cause: An error occurred during AutoPublish. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-394528: Rest Service Wsdl could not be imported. Please verify if the URI is available

Cause: Registry may be down or not accessible.

Action: Please verify the registry is accessible.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394550: UDDI Error- Message is : {0}

Cause: UDDI Error occurred. The exception message should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-394551: UDDI Error- Message is : {0}. Exception is : {1}

Cause: UDDI Error occurred. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-394552: An error was encountered while publishing this service : {0}.

Cause: Error while publishing the services or tModels.

Action: Please check if the registry running and if services and tModels follow the UDDI specification.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394553: Failed to connect to the specified publish URL.

Cause: Registry not accessible or bad publish URL specified.

Action: Please ensure that the registry is running and accessible. Verify the publish URL specified for the registry.
Level: 1

Type: ERROR

Impact: Configuration

OSB-394554: Please ensure that the URLs specified for the registry are correct.

Cause: Wrong Publish or Security URL specified.

Action: Please verify whether the Publish and Security URLs are correct and accessible.
Level: 1

Type: ERROR

Impact: Configuration

OSB-395000: Exception in {0}, {1}

Cause: A general runtime error has occured during OSB initialization

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-395005: Exception in {0}, continuing, {1}

Cause: This is an informational message that is logged during the OSB initialization process when a non-fatal exception occurs

Action: No action is necessary
Level: 1

Type: ERROR

Impact: Process

OSB-395007: The OSB debugger failed during initialization: {0}

Cause: A general runtime error has occured during initialization of OSB debugger.

Action: Verify the port defined for the OSB debugger is not already in use by another application or component. Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-395100: The TokenIterator does not correspond to a XmlObject value

Cause: One of the actions has attempted to treat the result of XQuery expression as XML, whereas the actual return value was not XML

Action: Please check the configuration to make sure that the context in which the XQuery expression is used is consistent with the actual return value
Level: 1

Type: ERROR

Impact: Data

OSB-395101: prolog declarations are not allowed for xquery snippets

Cause: The inline XQuery expression has prolog declarations, such as ''declare namespace'' statements. This is not allowed in inline XQuery expressions

Action: Please check the text of inline expression for prolog declarations. If those are really necessary, then register a XQuery resource and use it instead of an inline expression in your action.
Level: 1

Type: ERROR

Impact: Configuration

OSB-395102: The given value is not of a supported type: {0}

Cause: One of the actions has passed an expression to XQuery evaluation engine that is not of recognized type

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and has semantic meaning. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

OSB-395103: Unsupported XQuery Type: {0}

Cause: While evaluating the result of XQuery expression, an unexpected XML token has been found.

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and has semantic meaning. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

OSB-395104: The TokenIterator does not correspond to a single String value

Cause: The result of XQuery expression was expected to be a single String value and was something else.

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and will result in a single String value
Level: 1

Type: ERROR

Impact: Data

OSB-395105: The TokenIterator does not correspond to a single XmlObject value

Cause: The result of XQuery expression was expected to be a single XML object value and was something else.

Action: Please check the configuration of the action to make sure the text of the expression is properly configured and will result in a single XML object value
Level: 1

Type: ERROR

Impact: Data

OSB-395106: Unexpected Error: the TokenSource does not contain an BEGIN ATTRIBUTE

Cause: There was an unexpected error while parsing the result of XQuery expression. A BEGIN ATTRIBUTE token was expected but not found

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-395107: Unexpected Error: the TokenSource does not contain an END ATTRIBUTE

Cause: There was an unexpected error while parsing the result of XQuery expression. A END ATTRIBUTE token was expected but not found

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-395108: Error parsing XML: {0}

Cause: There was an unexpected error while parsing the result of XQuery expression. There should be a message that points to the cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-395109: There was an error trying to migrate the contents of the xquery {0} to 1.0 engine: {1}

Cause: There was an unexpected error while migrating the contents of an xquery to 10 engine standard. There should be a message that points to the cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-395130: Exception in {0}, {1}

Cause: An unexpected exception occurred. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-395132: Selected WSDL binding is missing an operation ''{0}'' defined by corresponding port type

Cause: There was a problem while registering a WSDL-based service: The set of operations defined in the WSDL binding does not match exactly that of the corresponding port type

Action: Make sure the selected WSDL binding set of operations is exactly the same as that of the corresponding port type
Level: 1

Type: ERROR

Impact: Configuration

OSB-395133: Mismatch between the WSDL binding and the service definition type: {0}

Cause: There was an unexpected problem while registering a WSDL-based service: (1) the type of WSDL binding in WSDL resource is SOAP whereas the service is not of SOAP type or (2) there was a mismatch between the SOAP versions of the service and the corresponding WSDL binding or (3) the binding from the WSDL is not supported

Action: Edit and save the service. If this does not help, contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395134: You can only use a HTTP binding with verb="POST"

Cause: There was an problem while registering a WSDL-based service: corresponding WSDL binding was HTTP with non-POST verb, which is not allowed

Action: Correct the WSDL resource or choose another WSDL binding for the service
Level: 1

Type: ERROR

Impact: Configuration

OSB-395135: Selected WSDL binding contains mixed-style operations and is not supported

Cause: There was a problem while registering a WSDL-based service: Some of the operations in the WSDL binding are of style ''document'' while others are of ''rpc''. OSB only supports all rpc or all document, but not mixed.

Action: Make sure the selected WSDL binding does not contain mixed-style operations
Level: 1

Type: ERROR

Impact: Configuration

OSB-395136: The wsdl binding has more than one operation you must specify how to select the operations

Cause: There was an problem while registering a WSDL-based service: The WSDL binding has more than one operation, so you must specify how to select the operation in service registration wizard

Action: Check the service configuration and make sure that the operation selection algorithm is properly configured
Level: 1

Type: ERROR

Impact: Configuration

OSB-395137: No corresponding mapping was found in the service definition for the WSDL operation: {0}

Cause: No corresponding mapping was found in the service definition for the WSDL operation: {0}

Action: Check the service configuration and make sure that the operation selection algorithm is properly configured
Level: 1

Type: ERROR

Impact: Configuration

OSB-395138: The operation referenced in the service definition cannot be found in the WSDL: {0}

Cause: There was an problem while registering a WSDL-based service: The operation referenced in the service definition cannot be found in the WSDL: {0}

Action: Check the service configuration and make sure that the operation selection algorithm is properly configured
Level: 1

Type: ERROR

Impact: Configuration

OSB-395139: Two or more operations expect the same incoming message, you must use a selector different than message body

Cause: There was a problem registering a WSDL-based service: the specified operation selection algorithm was SOAP Body while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body of the incoming SOAP message.

Action: Choose a different operation selection algorithm for the service or use a different WSDL binding
Level: 1

Type: ERROR

Impact: Configuration

OSB-395140: At least one operation could not be mapped for this selector algorithm, you should use a selector different than message body. Attempt to evaluate the operation, for example during WS-Security, Operational Branch processing etc. - may result in unexpected results.

Cause: There was a problem registering a WSDL-based service: the specified operation selection algorithm was SOAP Body or XML Payload while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body/payload of the incoming message.

Action: Choose a different operation selection algorithm for the service. Another option is to update the WSDL in a way that it is compatible with the selection algorithm. For example, make sure that the WSDL messages have a single part defined by element.
Level: 1

Type: ERROR

Impact: Configuration

OSB-395141: Either there are duplicate values for the soapAction attribute for different operations in the selected WSDL binding or soapAction is not defined for at least one operation in the WSDL. Therefore SOAPAction header operation selection algorithm cannot be used

Cause: There was a problem registering a WSDL-based service: Either there are duplicate values for the soapAction attribute for different operations in the selected WSDL binding or soapAction is not defined for at least one operation in the WSDL. Therefore SOAPAction header operation selection algorithm cannot be used

Action: Choose a different operation selection algorithm for the service or use a different WSDL binding
Level: 1

Type: ERROR

Impact: Configuration

OSB-395142: You cannot select operations for business services

Cause: There registered business service is not properly configured: it is not allowed to have operation selection algorithm for business services

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395143: At least one message type must be specified for the request or response. Both message types cannot be ''None''

Cause: There was a problem registering messaging type service: At least one message type must be specified for the request or response. Both message types cannot be ''None''

Action: Choose a message type other than ''None'' for either request or response message type
Level: 1

Type: ERROR

Impact: Configuration

OSB-395144: The schema defined for mixed type, cannot be found in the repository

Cause: There was a problem registering Messaging Type service: the corresponding XML schema resource was not found

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395145: The schema defined for mixed type, cannot be parsed

Cause: There was a problem registering Messaging Type service: the corresponding XML schema resource could not be parsed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395146: The element defined for mixed type, cannot be found in the schema

Cause: There was a problem registering Messaging Type service: the specified element was not found in the XML schema resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395147: The type defined for mixed type, cannot be found in the schema

Cause: There was a problem registering Messaging Type service: the specified type was not found in the XML schema resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395148: The XPath expression for operation selection is not valid: {0}

Cause: The XPath expression for operation selection is not valid

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395149: Two or more operations expect the same incoming message, you must use a selector different than payload type

Cause: There was a problem registering a WSDL-based service: the specified operation selection algorithm was Payload Type while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body of the incoming SOAP message.

Action: Choose a different operation selection algorithm for the service or use a different WSDL binding
Level: 1

Type: ERROR

Impact: Configuration

OSB-395150: The Transport Header name is required for the current selection algorithm

Cause: The Transport Header name is required for the current selection algorithm.

Action: Provide a Transport Header name.
Level: 1

Type: ERROR

Impact: Configuration

OSB-395330: Invalid number of arguments

Cause: The number of arguments to custom XQuery function did not match that which was expected

Action: Please check the pipeline action configuration that uses the custom XQuery function to make sure it is configured properly
Level: 1

Type: ERROR

Impact: Configuration

OSB-395331: An unexpected error occurred, the runtime executor is in an illegal state.

Cause: An unexpected error has occured during the execution of XQuery or XSLT resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-395332: The XQuery expression used to specify the name of the XQuery resource did not result in a string value

Cause: The result of the XQuery expression is expected to be a single string value which is the full path to XQuery resource to execute

Action: Please check the XQuery expression to make sure it produces expected results. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-395333: XQuery expression evaluates to an invalid XQuery resource name: ''{0}''.

Cause: XQuery expression did not return the valid XQuery resource name. It should evaluate to an existing XQuery resource at runtime.

Action: Make sure that XQuery expression should evaluate to a existing XQuery resource in OSB at runtime. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-395334: The number of parameters for registered XQuery resource {0} does not match that given to it at runtime

Cause: The number of input parameters given to XQuery resource at runtime does not match the number that he resource requires

Action: Double-check that the number of input arguments supplied in dynamic XQuery configuration matches that of the XQuery resource to be used at runtime
Level: 1

Type: ERROR

Impact: Configuration

OSB-395335: XQuery resource {0} expected an XQuery expression for XQuery parameter {1} but none was found

Cause: Each parameter to an XQuery resource needs to have an XQuery expression configured to be bound as its value at runtime. One or more of the parameters to the given XQuery is missing an expression for its value

Action: Double-check that all of the parameters to the XQuery resource have been properly supplied in dynamic XQuery configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-395336: The value of input argument {0} cannot be null or an empty string

Cause: The input argument value to the XQuery function is {1}; the argument value should not be null or empty string

Action: Please check the input argument {0} value to make sure it does not result in a null or empty string..
Level: 1

Type: ERROR

Impact: Data

OSB-395337: CustomXPathFunctionManager: Error during initialization! File: {0}. Error: {1}

Cause: There was an error parsing the contents of file {0} containing custom XPath function definitions

Action: Please check the contents of the file and make sure it conforms to specified XML schema and all restrictions on supported Java methods/types, etc. are followed
Level: 1

Type: ERROR

Impact: Process

OSB-395339: No custom function with QName ''{0}'' exists

Cause: An unexpected error has occured during the execution of XQuery resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-395340: Custom function name needs to be a non-empty string

Cause: The name of the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395341: Custom function namespace needs to be a non-empty string

Cause: The namespace of the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395342: Custom function class name needs to be a non-empty string

Cause: The name of the Java class for the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395343: Custom function class method signature needs to be a non-empty string

Cause: The name of the Java class method for the custom XPath function needs to be a non-empty string

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395344: Custom function class {0} needs to be public

Cause: The Java class for the custom XPath function needs to have public scope

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395345: Custom Function class {0} has no methods

Cause: The Java class for the custom XPath function has no methods

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395346: No method with signature ''{0}'' was found in class {1}

Cause: The Java class for the custom XPath function has no method with the specified signature

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395347: Method ''{0}'' needs to be public static

Cause: The Java method for the custom XPath function has to be declared as public static

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395348: Unsupported Java class {0} used by custom XPath function

Cause: One or more of the input arguments and/or return values from a custom XPath function has a Java type not currently supported by this feature

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395349: Expected {0} arguments. Got: {1}

Cause: The number of input arguments passed into custom XQuery function at runtime does not match the number of expected arguments specified by its corresponding Java method signature

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395350: Error invoking custom xquery java function: {0}

Cause: An runtime error has occured during the invocation of a custom XQuery function

Action: Check the server log and the corresponding exception stack trace to see additional information that might point to the cause of the error
Level: 1

Type: ERROR

Impact: Data

OSB-395351: CustomXPathFunctionManager: Error during initialization! File: {0} Error: {1}

Cause: There was an error during initialization reading the contents of one or more Jar files in ALSB_HOME config xpath-functions directory

Action: Please check the contents of the directory
Level: 1

Type: ERROR

Impact: Process

OSB-395353: CustomXPathFunctionManager: Custom function name ''{0}'' is not valid

Cause: Custom function name needs to be a valid NCName. See http://www.w3.org/TR/REC-xml-names/#NT-NCName for more information

Action: Check the custom XPath function configuration file in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified rule
Level: 1

Type: ERROR

Impact: Configuration

OSB-395355: CustomXPathFunctionManager: Error during initialization! File: {0} Error(s): {1}

Cause: There was an error during initialization reading the contents of specified XML configuration file

Action: Check the custom XPath function configuration file(s) in ALSB_HOME\\config\\xpath-functions directory and make sure all entries conform to specified XML schema
Level: 1

Type: ERROR

Impact: Configuration

OSB-395357: XPath can only be executed against XML or MFL content

Cause: The configured XPath expression refers to a message contents variable or other expression whose content is not XML. XPath can only be executed against XML or MFL content

Action: Please check the value the configured expression to make sure that it refers to valid XML content. One can use Log action to log the result of any expression including message context variables.
Level: 1

Type: ERROR

Impact: Data

OSB-395358: XQuery expression for input parameter resulted in null

Cause: The configured XQuery expression the result of which is used for input parameter to XSLT transformation resulted in null.

Action: Please check the configured expression to make sure it results in non-null value. One can use Log action to log the result of any XQuery expression.
Level: 1

Type: ERROR

Impact: Data

OSB-395359: No value could be bound to variable: {0}

Cause: The configured XQuery expression the result of which is used for named input variable to XSLT transformation resulted in null.

Action: Please check the configured expression to make sure it results in non-null value. One can use Log action to log the result of any XQuery expression.
Level: 1

Type: ERROR

Impact: Data

OSB-395360: Failed to parse configuration into typed XmlObject: {0}

Cause: There was an error while initializing OSB pipeline runtime state for a given service. The error occurred while parsing the saved configuration for service message flow

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-395361: The XQuery expression used to specify the name of the XSLT resource did not result in a string value

Cause: The result of the XQuery expression is expected to be a single string value which is the full path to XSLT resource to execute

Action: Please check the XQuery expression to make sure it produces expected results. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-395362: XQuery expression evaluates to an invalid XSLT resource name: ''{0}''.

Cause: XQuery expression did not return the valid XSLT resource name. It should evaluate to an existing XSLT resource at runtime.

Action: Make sure that XQuery expression should evaluate to a existing XSLT resource in OSB at runtime. You can use Log action to see the value of this expression at runtime.
Level: 1

Type: ERROR

Impact: Data

OSB-395363: The number of parameters for registered XSLT resource {0} does not match that given to it at runtime

Cause: The number of input parameters given to XSLT resource at runtime does not match the number that he resource requires

Action: Double-check that the number of input arguments supplied in dynamic XSLT configuration matches that of the XSLT resource to be used at runtime
Level: 1

Type: ERROR

Impact: Configuration

OSB-395364: XSLT resource {0} expected an XQuery expression for XSLT parameter {1} but none was found

Cause: Each parameter to an XSLT resource needs to have an XQuery expression configured to be bound as its value at runtime. One or more of the parameters to the given XSLT is missing an expression for its value

Action: Double-check that all of the parameters to the XSLT resource have been properly supplied in dynamic XSLT configuration
Level: 1

Type: ERROR

Impact: Configuration

OSB-395365: CustomXPathFunctionManager: Error during XQuery 1.0 engine-specific initialization!

Cause: There was an error during initialization

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-395366: XPath expression invalid, not a selection: {0}

Cause: Only selection-type XPath expressions are supported

Action: Use a selection-type XPath expression
Level: 1

Type: ERROR

Impact: Data

OSB-397000: Exception in {0}, {1}

Cause: A general runtime error has occured in OSB resource management component There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-397007: The environment value "{1}" used in the configuration plan for "{0}" does not support the {2} action.

Cause: An attempt was made to perform an action against an environment value that doesn't support that action.

Action: Modify the configuration plan to correct the error.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397008: An SLA alert rule name is required in the location for the {1} environment value action in the configuration plan for "{0}".

Cause: No SLA alert rule name was specified in the location for the environment value action.

Action: Modify the configuration plan to correct the error.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397009: The SLA alert rule "{2}" specified in the location for the {1} environment value action was not found in "{0}".

Cause: The SLA alert rule name was not found.

Action: Modify the configuration plan to correct the error.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397010: The customizations contain the following illegal environment variable types: {0}

Cause: The customizations should only use public env value types. Public env value types have a category of either environmental or operational.

Action: Update the customization to only use public env value types.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397011: Location of the env value of type "{1}" used in the configuration plan for "{0}" is {4} which is out of bounds [{2},{3}] in resource.

Cause: Environment value's location is out of bounds from the accepted range.

Action: Check the passed env value's location. It should be in the valid range.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397012: There are no valid locations in "{0}" for env value of type "{1}".

Cause: There are no valid locations for the env value.

Action: Check that env value is specified correctly.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397013: The location "{2}" for env value of type "{1}" in the configuration plan for "{0}" must be a non-negative integer.

Cause: The location should be a non-negative integer.

Action: Ensure that the specified location is a non-negative integer.
Level: 1

Type: ERROR

Impact: Configuration

OSB-397014: No location specified for env value of type "{1}" in the configuration plan for "{0}".

Cause: No location specified.

Action: Specify a location.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398000: Exception in {0}, {1}

Cause: An unexpected error has occured in OSB runtime while processing a message. There should be a specific error message that points to the cause of the error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-398014: Invalid Proxy URI: {0}

Cause: There was an error while processing the configuration for given proxy service: The URI specified was not valid. There should be an error message that points out a specific problem

Action: Check the URI for the proxy service to make sure it is valid
Level: 1

Type: ERROR

Impact: Configuration

OSB-398015: The service definition does not contain a reference to a wsdl

Cause: The WSDL-based service being registered is incorrectly configured: there was a problem retrieving its corresponding WSDL information

Action: Contact technical support
Level: 1

Type: ERROR

Impact: Configuration

OSB-398016: Error loading the WSDL from the repository: {0}

Cause: The WSDL-based service being registered is incorrectly configured: there was a problem retrieving its corresponding WSDL information. There should be an error message that points to the cause of the problem

Action: Contact technical support
Level: 1

Type: ERROR

Impact: Configuration

OSB-398017: The service definition contains a reference to a port not present in the wsdl: {0}

Cause: There was a problem while registering a WSDL-based service: specified WSDL port is not present in associated WSDL resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398018: The service definition contains a reference to a binding not present in the wsdl: {0}

Cause: There was a problem while registering a WSDL-based service: specified WSDL binding is not present in associated WSDL resource

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398023: You can only setup inbound web service security on proxy services

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398024: This WSDL does not support web service security, you must attach a policy first

Cause: A service defined by the WSDL requires web service security policy but the WSDL does not have any

Action: Attach ws-policy to the WSDL or configure custom ws-policy for the service
Level: 1

Type: ERROR

Impact: Configuration

OSB-398025: You can only setup a service account on business services

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398026: You can only use web service security with a SOAP binding

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398038: Proxy service "{0}" does not have a credential for web service security encryption (no service key provider has been specified). The ws-policy of operation "{1}" requires an encryption credential.

Cause: The ws-policy of the proxy service contains a confidentiality assertion, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have an encryption credential)
Level: 1

Type: ERROR

Impact: Configuration

OSB-398040: Proxy service "{0}" does not have a credential for web service security digital signatures (no service key provider has been specified). The ws-policy of operation "{1}" requires a digital signature credential.

Cause: The ws-policy of the proxy service contains an integrity assertion, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have a digital signature credential)
Level: 1

Type: ERROR

Impact: Configuration

OSB-398042: Proxy service "{0}" does not have a credential for outbound two-way SSL authentication (no service key provider has been specified)

Cause: At least one route out of the proxy service requires 2-way SSL, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have an SSL client authentication credential)
Level: 1

Type: ERROR

Impact: Configuration

OSB-398043: The ws-policy of operation "{2}" for proxy service "{0}" contains a confidentiality assertion but service key provider "{1}" does not have an encryption credential

Cause: The ws-policy of the proxy service requires encryption, the service key provider linked to the proxy service must have an encryption credential

Action: Edit the service key provider and assign it an encryption credential, or edit the proxy service and choose a different service key provider (in the security tab)
Level: 1

Type: ERROR

Impact: Configuration

OSB-398044: The ws-policy of operation "{2}" for proxy service "{0}" contains an integrity assertion but service key provider "{1}" does not have a digital signature credential

Cause: The ws-policy of the proxy service requires digital signatures, the service key provider linked to the proxy service must have a digital signature credential

Action: Edit the service key provider and assign it a digital signature credential, or edit the proxy service and choose a different service key provider (in the security tab)
Level: 1

Type: ERROR

Impact: Configuration

OSB-398046: Proxy service "{0}" has one or more routes to a service which requires 2-way SSL authentication, but the proxy service does not have a credential for outbound SSL (service key provider "{1}" does not have an SSL credential).

Cause: At least one route out of the proxy service requires 2-way SSL, the proxy must have a reference to a service key provider

Action: In the security tab, assign a service key provider to the proxy service (the service key provider must have an SSL client authentication credential)
Level: 1

Type: ERROR

Impact: Configuration

OSB-398052: Could not retrieve an X.509 certificate from PKI Credential provider [service key provider: "{0}", key alias: "{1}"]

Cause: An error occurred while calling the PKI Credential Mapper Provider lookup method

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398055: Business service "{0}" cannot be associated with a router

Cause: There was an unexpected error validating the configuration of business service {0}: business services cannot be associated with a message flow

Action: Checking service configuration and/or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398056: WS-I Compliance failure ({0}): {1}

Cause: The body of request or response message does not conform to WS-I basic profile due to stated reason. This could happen when receiving request messages by OSB proxy services or response messages from business services enabled for WS-I compliance.

Action: Look at the specific error message and examine the payload to see why the body of the message fails WS-I compliance check
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-398059: Proxy service "{0}" has web service security configuration but either: 1) its WSDL does not have web service security policies, or 2) the <UsingPolicy> tag is missing from the WSDL. You must edit/save the proxy (that will remove the web service security configuration), or add web service security policies to the WSDL.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398060: The ws-policy of operation "{1}" in proxy service "{0}" contains a concrete confidentiality assertion. Confidentiality assertions assigned to proxy services must be abstract, the encryption certificate must not be embedded in the policy.

Cause: The proxy service is a WS-Security (web services security) active intermediary. Its ws-policy includes a "confidentiality" assertion (this is a Oracle-proprietary policy assertion which specifies that the client must encrypt the request message). This confidentiality assertion is concrete. That means the policy includes a base-64 encoded certificate (in the /wssp:Confidentiality/wssp:KeyInfo/wssp:SecurityTokenReference/wssp:Embedded/wsse:BinarySecurityToken element). Proxy services should not have concrete confidentiality assertions on its policy because the proxy's encryption certificate is assigned through a service key provider.

Action: Make the policy abstract. To do this edit the policy and delete the SecurityToken and SecurityTokenReference child elements inside the /wssp:Confidentiality/wssp:KeyInfo element.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398061: The ws-policy of operation "{1}" in business service "{0}" contains an abstract confidentiality assertion. Confidentiality assertions assigned to business services must not be abstract, the encryption certificate must be embedded in the policy

Cause: The ws-policy of the business service includes a "confidentiality" assertion (this is a Oracle-proprietary policy assertion which specifies that request messages to this service must be encrypted). This confidentiality assertion is abstract. That means the policy does not include an embedded base-64 encoded server certificate. The confidentiality assertion must be concrete.

Action: Make the policy concrete. To do this edit the policy and make sure there are SecurityToken and SecurityTokenReference child elements inside the /wssp:Confidentiality/wssp:KeyInfo element. The value of the SecurityTokenReference element is an embedded base-64 encoded server certificate (it must be the server's encryption certificate). Consult Oracle Service Bus security documentation to find examples of what this policy should look like.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398062: An error occurred during web service security validation: {0}

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398063: There is an outbound call to operation "{1}" on service "{0}", this operation requires encrypted response messages; the proxy must be assigned to a service key provider

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy specify that response messages to the proxy must be encrypted with the proxy's encryption key. The proxy service should have a reference to a service key provider from which OSB will get the proxy's encryption credential (OSB will send this certificate on the request message), but no service key provider reference has been assigned to the proxy.

Action: Edit the proxy service. In the security tab choose a service key provider (the service key provider must have an encryption credential).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398064: There is an outbound call to operation "{1}" on service "{0}", this operation requires signed request messages; the proxy must be assigned to a service key provider

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy require OSB to sign the request messages. The proxy service should have a reference to a service key provider from which OSB will get the proxy's digital signature credential, but no service key provider reference has been assigned to the proxy.

Action: Edit the proxy service. In the security tab choose a service key provider (the service key provider must have a digital signature credential).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398065: There is an outbound call to operation "{1}" on service "{0}", this operation requires encrypted response messages but the service key provider does not have an encryption credential

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy specify that response messages to the proxy must be encrypted with the proxy's encryption key. The service key provider assigned to this proxy does not have an encryption credential.

Action: Edit the service key provider and choose an encryption credential; or alternatively, edit the proxy service and -in the security tab- choose a different service key provider (one which has an encryption credential).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398066: There is an outbound call to operation "{1}" on service "{0}", this operation requires signed request messages but the service key provider does not have a digital signature credential

Cause: One or more nodes in the pipeline route messages to a service whose ws-policy require OSB to sign the request messages. The service key provider assigned to this proxy does not have an encryption credential.

Action: Edit the service key provider and choose a digital signature credential; or alternatively, edit the proxy service and -in the security tab- choose a different service key provider (one which has a digital signature credential).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398067: An error occurred during WSS policy attachment validation for the service {0} : {1}

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398068: Proxy service attribute cannot be set to true for a business service resource

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398069: Failed to start timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB service runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-398070: Failed to increment counter {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-398071: Failed to stop timer {0}: {1}

Cause: There was an unexpected error while collecting statistics in OSB pipeline runtime during the processing of a message. There should be a specific message that describes specific cause of the problem

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Process

OSB-398072: Proxy must invoke either a Pipeline, a Split-Join, a Business Service or another Proxy

Cause: A Proxy Service Resource must be wired to one of four resources: a Pipeline, a Split-Join, a Business Service or another Proxy

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398073: Proxy may not invoke {0}. It must invoke either a Pipeline, a Split-Join, a Business Service or another Proxy

Cause: A Proxy Service Resource must be wired to one of four resources: a Pipeline, a Split-Join, a Business Service or another Proxy

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398074: A Proxy service may not invoke itself directly or indirectly

Cause: A Proxy Service Resource must be wired to one of four resources: a Pipeline, a Split-Join, a Business Service or another Proxy

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398075: A Proxy service of type {0} may not invoke service {1} of type {2}

Cause: A Proxy Service Resource can only invoke a service of compatible type. Also, when a proxy services that invokes another proxy or business service directly, service binding types have to match exactly

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398076: The operation selection of a WSDL-typed pipeline {0} invoked by a WSDL-typed proxy service must either be none or match that of the invoking proxy service

Cause: The operation selection of a WSDL-typed pipeline invoked by a WSDL-typed proxy service must either be none or match that of the invoking proxy service

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398077: Operation selection must be specified by the invoked pipeline {0}

Cause: When an Any SOAP proxy invokes WSDL SOAP pipeline or Any XML proxy invokes WSDL XML pipeline, the pipeline resource must specify operation selection

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398078: Component {0} may not be invoked because it exists in a different project

Cause: Invoked components (pipeline and split join resources) must be in the same project as the proxy service invoking them

Action: Check the proxy service configuration and wire it as needed
Level: 1

Type: ERROR

Impact: Configuration

OSB-398106: The ws-policy of operation "{1}" in service "{0}" contains an identity assertion. The business service should have a web service security service account, but none has been configured.

Cause: The ws-policy of operation "{1}" in service "{0}" contains an identity assertion. Only web service security username tokens are supported for identity purposes. This business service must have a web service security service account.

Action: Edit the business service. In the security tab, choose a web service security service account.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398107: The ws-policy for service "{0}" and operation "{1}" contains a policy assertion with qname "{2}". This assertion is not recognized. Make sure the namespace declaration and local-name are correct.

Cause: The ws-policy contains a policy assertion which is not recognized.

Action: Edit the ws-policy and make sure all policy assertions are supported by Oracle Service Bus.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398108: Business service "{0}" has web service security configuration but either: 1) its WSDL does not have web service security policies, or 2) the <UsingPolicy> tag is missing from the WSDL. You must edit/save the service (that will remove the web service security configuration), or add web service security policies to the WSDL.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398110: Business service "{0}" has configuration for message-level custom token authentication. Message-level custom token authentication only applies to proxy services.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398111: Proxy service "{0}" has configuration for message-level custom authentication. Message-level custom authentication is not valid on services with binary or text binding.

Cause: An unexpected error occurred. The service definition is invalid.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398112: Operation "{1}" in proxy service "{0}" is configured for WS-Security authentication, but the proxy service is also configured for message-level custom token authentication. WS-Security authentication and message-level custom authentication are mutually exclusive.

Cause: WS-Security authentication and message-level custom authentication are mutually exclusive.

Action: Make sure your proxy service is not configured for both types of authentication. You may have to edit the proxy service or the ws-policy to make sure that at most one of these two techniques is used.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398113: Invalid custom authentication token selector: {0}

Cause: The XPath expression in the custom-token selector is invalid

Action: Enter a valid XPath expression in the custom-token selector field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398114: Invalid username selector: {0}

Cause: The XPath expression in the username selector is invalid

Action: Enter a valid XPath expression in the username selector field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398115: Invalid password selector: {0}

Cause: The XPath expression in the password selector is invalid

Action: Enter a valid XPath expression in the password selector field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398116: Invalid user-defined authentication context property selector: {0}

Cause: The XPath expression in the user-defined property selector is invalid

Action: Enter a valid XPath expression in the user-defined property selector field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398117: Invalid variable name in selector: "{0}"

Cause: The variable name in a custom-token must be either "header" or "body"

Action: Edit the proxy service. In the security tab, choose a valid message part for your custom-token.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398118: The ws-policy of operation "{1}" in proxy service "{0}" contains an Identity assertion for UsernameToken without password. Such UsernameTokens can only be used when the token is signed, however, this ws-policy does not have an Integrity assertion. Either add an Integrity assertion policy or change your Identity policy so that the UsernameToken includes a password.

Cause: A web service security username token without a password can only be trusted if the token itself is signed by the message producer.

Action: Edit the ws-policy and make sure it either forbids username tokens without password, or otherwise have the policy require a digital signature which covers the username token.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398120: The WSDL for the typed transport endpoint could not be accessed.

Cause: There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398121: Error loading the WSDL for the typed transport endpoint: {0}

Cause: There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration. There should be an error message that points to the specific cause of the error

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398123: Missing sla-alerting element in the service entry element.

Cause: There was an unexpected error while validating service configuration: a required element "sla-alerting" was missing from the configuration

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398125: Logging element should not exist in the service entry element.

Cause: There was an unexpected error while validating service configuration: business service configuration cannot have "logging" element

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398126: sla-alerting element should not exist in the service entry element.

Cause: There was an unexpected error while validating service configuration: business service configuration cannot have "sla-alerting" element

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398127: pipeline-alerting element should not exist in the service entry element.

Cause: There was an unexpected error while validating service configuration: business service configuration cannot have "pipeline-alerting" element

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398128: One of the Web service policy attached is not allowed on service {0} because the service binding does not support it

Cause: The service definition is invalid; it should not contain any ws-policy configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398129: An error occurred while computing the web service policy for service {0}: {1}

Cause: An error occurred while computing the web service policy for service. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398130: Service "{0}" must have RM (reliable messaging) policy assertions in its web service policy

Cause: WS transport services must have RM (reliable messaging) policy.

Action: Configure the service's ws-policy. Make sure it has RM policy assertions.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398131: This service should not have WebLogic Server 9.X-style security policy assertions

Cause: WS transport services cannot have WebLogic Server 9.X-style security policy assertions

Action: Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy assertions.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398132: RM (reliable messaging) policy assertions are not allowed on this service.

Cause: RM (reliable messaging) policy assertions are only allowed on ws-transport services.

Action: Either remove the RM policy assertions from the service's ws-policy or switch the service to the ws transport.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398133: The service is based on WSDL with Web Services Security Policies that are not natively supported by Oracle Service Bus. Please select 'OWSM Policies - From OWSM Policy Store' option and attach equivalent OWSM security policy. For the Business Service, either you can add the necessary client policies manually by clicking 'Add' button or you can let Oracle Service Bus automatically pick and add compatible client policies by clicking 'Add Compatible' button.

Cause: WS-SP 1.x assertions are not allowed in this version of Oracle Service Bus (except in some cases in WS Transport endpoints)

Action: The service is based on WSDL with Web Services Security Policies that are not natively supported by Oracle Service Bus. Please select 'OWSM Policies - From OWSM Policy Store' option and attach equivalent OWSM security policy. For the Business Service, either you can add the necessary client policies manually by clicking 'Add' button or you can let Oracle Service Bus automatically pick and add compatible client policies by clicking 'Add Compatible' button.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398134: Proxy service {0} is marked as a web service security intermediary but does not have web service security policies

Cause: A web service security intermediary proxy service must have security policy (in it ws-policy).

Action: If you want this proxy service to be a web service security intermediary, edit the service's ws-policy and make sure it includes security policy. If on the other hand you do not want this proxy service to be a web service security intermediary, go to the security tab and click "update" (without making any other changes).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398135: Business service {0} has a service account reference for web service security authentication but does not have web service security policies

Cause: A web service security service account is only meaningful if the business service has web service security policy (in its ws-policy). This business service has a reference to a web service security service account (although you may not be able to see it in the console).

Action: Either add security policy to this service's ws-policy or go to the security tab and click "update"(without making any other changes).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398136: Proxy service {0} is enabled for content streaming and cannot be marked as a web service security intermediary

Cause: Content streaming feature is not allowed if your service is configured as a web service security active intermediary.

Action: Edit the service and turn off content streaming feature
Level: 1

Type: ERROR

Impact: Configuration

OSB-398137: Proxy service {0} is enabled for content streaming and perform custom authentication

Cause: Content streaming feature is not allowed if your service is configured for custom authentication.

Action: Edit the service and turn off content streaming feature
Level: 1

Type: ERROR

Impact: Configuration

OSB-398138: WSI-Compliance cannot be checked in proxies enabled for content streaming

Cause: WSI-Compliance cannot be checked in proxies enabled for content streaming.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398139: {0} is a soap/abstract soap type service, the service should have ws-policy configuration

Cause: soap/abstract soap type service should have ws-policy configuration

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398140: Proxy service "{0}" is a passive wss intermediary. The ws-policy of operation "{1}" contains an abstract confidentiality assertion but the proxy service does not have a service key provider reference or the referenced service key provider does not have an encryption credential. You will be able to invoke this proxy service but its effective WSDL will not have an encryption certificate. Clients must get this certificate out-of-band.

Cause: A passive WSS intermediary is a proxy service which has a WS-Security policy in its public WSDL (i.e., its "effective" WSDL), but which does not perform any WS-Security processing. It simply relays the security header to a back-end service. Whenever a passive WSS intermediary has an "abstract confidentiality" policy, the proxy should have a service key provider which, in turn, must have an encryption credential. This encryption credential will be then inlined in the effective WSDL.

Action: Edit the proxy service. In the security tab, choose a service key provider (the service key provider must have an encryption credential).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398141: One or more ws-policies have been bound to operation "{0}" but there is no such operation

Cause: The service has custom ws-policy. One of the custom ws-policies is assigned to an operation which does not exist in the WSDL. This may be the result of a change in the WSDL.

Action: Either edit the WSDL and add the missing operation, or if no such operation exists, edit the service, go to the policy tab and click "update" (without making any other changes).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398142: One or more ws-policies have been bound to the response of operation "{0}" but the operation is one-way

Cause: The service has custom ws-policy. One of the custom ws-policies is assigned to the response message of an operation which is declared in the WSDL to be a one-way operation. Such operations do not have response messages. This may be the result of a change in the WSDL.

Action: Edit the service, go to the policy tab and click "update" (without making any other changes).
Level: 1

Type: ERROR

Impact: Configuration

OSB-398143: A reliable messaging policy is bound to operation "{0}"; reliable messaging policies can only be bound to the service as a whole

Cause: RM (reliable messaging) policies cannot be bound to specific operations, they can only be bound to the entire service.

Action: Edit the service's ws-policy. Make sure RM policies are bound to the service as a whole.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398147: Service {0} is enabled for XOP/MTOM and cannot be marked as a web service security intermediary

Cause: XOP/MTOM feature is not allowed if your service is configured for as active message-level security intermediary

Action: Edit the service and turn off XOP/MTOM feature
Level: 1

Type: ERROR

Impact: Configuration

OSB-398148: Service {0} is enabled for XOP/MTOM and perform custom authentication

Cause: XOP/MTOM feature is not allowed if your service is configured for custom authentication.

Action: Edit the service and turn off XOP/MTOM feature
Level: 1

Type: ERROR

Impact: Configuration

OSB-398149: Only SOAP Document-style WSDL bindings are supported for REST services

Cause: Only SOAP Document-style WSDL bindings are supported for REST services

Action: Edit the service WSDL to select another binding
Level: 1

Type: ERROR

Impact: Configuration

OSB-398150: The service definition does not contain a reference to a WADL

Cause: The REST service being registered is incorrectly configured: there was a problem retrieving its corresponding WADL information

Action: Contact technical support
Level: 1

Type: ERROR

Impact: Configuration

OSB-398151: User-defined property name is empty or not valid.

Cause: user-defined property name is either not provided or invalid

Action: Enter a valid name in the user-defined property name field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398204: [OSB Tracing] Internal Error while tracing message {0}

Cause: This is an informational message from OSB tracing subsystem that is logged whenever it fails to trace a particular message (inbound/outbound request/response)

Action: No action is required
Level: 1

Type: ERROR

Impact: Other

OSB-398307: Result Caching is not supported on Proxy Services.

Cause: Result Caching is only valid on business services.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-398308: Result Caching is not supported on business service because it has no request-response operations.

Cause: Result Caching is only allowed on business services that use at least one request-response operation.

Action: Edit the service configuration and either use a wsdl that defines a request/response operation or do not enable the result caching feature.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398310: Invalid Cache Token expression: {0}

Cause: The Cache Token XQuery expression is invalid

Action: Enter a valid XQuery expression in the Cache Token Expression field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398312: Invalid Expiration Time expression: {0}

Cause: The Expiration Time XQuery expression is invalid

Action: Enter a valid XQuery expression in the Expiration Time Expression field
Level: 1

Type: ERROR

Impact: Configuration

OSB-398313: Cache expression is using invalid variable {0}.

Cause: The Cache XQuery expression is using an invalid variable. It should only be using $body, $header, $operation or $metadata.

Action: Ensure that the Cache XQuery expression only uses valid variables.
Level: 1

Type: ERROR

Impact: Configuration

OSB-398314: There was an error getting the result: {0}.

Cause: An exception was thrown when getting the result to be cached. The detail message should provide more information about the actual cause.

Action: Correct the error described in the exception message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-398325: An error has occurred while parsing the payload. Payload details:{0}Exception:{1}

Cause: An exception occurred while parsing the inbound request or outbound response payload as XML. The exception message should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-398350: Error marking the following URIs offline as they are not part of {0}: {1}

Cause: An attempt was made to mark a URI offline that is not one of the URLs configured in the business service endpoint configuration.

Action: Check that the URI is part of the Business Service endpoint configuration before trying again.
Level: 1

Type: ERROR

Impact: Other

OSB-398351: WSI-Compliance option can only be enabled for SOAP 1.1 services

Cause: WSI-Compliance option can only be enabled for SOAP 1.1 services

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-473000: Failed to receive statistics from server {0} at tick {1}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473001: Error while aggregating statistics data for nexttick={0} and lastprocessedtick={1}.

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473003: Aggregation Server Not Available. {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473004: Cannot recover from persistent Store.

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473006: Failed to initialize statistics data structure after checkpoint {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473008: Aggregator rejected statistics reported by server {0} with tick {1}. The last processed tick by Aggregator is {2}.

Cause: This is caused when the statistics for a server are received by the Aggregator too late.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473010: Aggregator rejected statistics reported by server {0} with tick {1} because the server snapshot version {2} is not compatible with current snapshot versions {3}.

Cause: This happens when the snapshot sent to the Aggregator has a different snapshot version that the current snapshot version.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473013: Failed to send statistics to aggregation server: {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473014: Writing to Persistence Store Failed: {0}

Cause: The exception will detail the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473050: Monitoring has been disabled for the domain

Cause: Monitoring for this domain has been disabled. When the monitoring is disabled statistics are not collected. Hence you cannot retrieve statistics while monitoring is disabled.

Action: Enable monitoring for this domain. Go to Global Settings under System Administration and enable monitoring. You need to open a session using change center to do this.
Level: 1

Type: ERROR

Impact: Other

OSB-473051: Aggregator did not receive statistics from {0} for the current view

Cause: There is a communication failure between Aggregator server and other managed servers. One of the managed servers failed to send statistics to the managed server on which Aggregator is running.

Action: Wait for some time and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473052: Reset statistic Task Failed {0}

Cause: There is an error while trying to reset the statistics. There may be a problem while creating a session and committing it in the background.

Action: Wait for some time and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473053: Reset Unsuccessful: Weblogic Session lock held by user

Cause: A lock already exists on WLS Configuration. Some one opened a session on Weblogic for editing WLS configuration.

Action: Release the existing lock on weblogic server and try again. Go to weblogic console and Activate or Undo all changes.
Level: 1

Type: ERROR

Impact: Other

OSB-473055: Failed to get {0} from {1} due to {2}

Cause: Information about a service could not be retrieved. This may be because the service is not found in the domain. Service could have been deleted, renamed, moved or never existed.

Action: Check if the service exists and try with correct service ref again.
Level: 1

Type: ERROR

Impact: Other

OSB-473056: Failed to reset statistics for {0} services due to {1}

Cause: There is an error while trying to reset the statistics. There may be a problem while creating a session and committing it in the background.

Action: Wait for some time and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473057: Failed to get statistics for services due to {0}

Cause: There is a problem while trying to retrieve statistics for a service. This may be because the arguments passed to the API are not proper.

Action: Check the arguments passed to API and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473058: Failed to get statistics for services as operation {0} returned null.

Cause: Monitoring runtime did not return any statistics for a service.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473059: INTERNAL_PROCESSING_ERROR: {0}

Cause: Used to represent an internal error in the monitoring runtime. This may be because an unrecognized statistic type is returned by the monitoring runtime.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473060: INTERNAL_PROCESSING_ERROR: {0} due to {1}

Cause: Used to represent an internal error in the monitoring runtime.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473062: {1} is incorrect value for parameter {0} as it specifies a bitmap which does not represent valid combinations of resource types.

Cause: You should send a valid combination of bits while retrieving statistics. The values from 1 to 15 are allowed.

Action: Correct the resourceTypes argument and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473063: {1} is incorrect value for parameter {0} as it specifies a bitmap that has bits set for one or more resource types, which are not applicable to the service.

Cause: This is because you have requested statistics for a resource type which is not applicable for the service.

Action: Correct the bit combination and try again
Level: 1

Type: ERROR

Impact: Other

OSB-473064: Parameter {0} is invalid as it contains one or more {1} services.

Cause: You would have requested for business service statistics but you have sent a proxy ref as an argument to API. Or you would have requested for proxy service statistics but you have sent a business service ref as an argument to API.

Action: Correct the ref array argument and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473065: Could not find service - {0}. It is either renamed or moved or deleted or never existed...

Cause: The service for which you are trying to retrieve statistics does not exist. It may have been deleted, moved, renamed or never existed.

Action: Check if the service exists and try with the correct service ref.
Level: 1

Type: ERROR

Impact: Other

OSB-473066: Monitoring has been disabled for the service - {0}

Cause: Monitoring has been disabled for the service for which you are trying to retrieve or reset statistics.

Action: Enable the monitoring for this service. Go to View Proxy/Business Service page and click on Operational Settings Tab. You can enable monitoring here. To do this you need to open a session using change center.
Level: 1

Type: ERROR

Impact: Other

OSB-473067: The value of parameter {0} is invalid as {1}.

Cause: One of the argument passed to public API contains an invalid value.

Action: Correct the arguments to API and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-473068: The value of aggregation interval {0} is invalid.

Cause: The service cannot be monitored at the specified Aggregation Interval.

Action: Change the Aggregation Interval to one of the valid aggregation Intervals.
Level: 1

Type: ERROR

Impact: Other

OSB-473069: Failed to read reset record for {0}

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473070: Failed to reset statistics

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473071: Failed to shutdown collector

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473072: Failed to shutdown aggregator

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473075: Could not compute information for {0}

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473076: Snapshot version incompatible

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473077: Exception in ClusterTimerPersistenceStore

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473078: Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with the time skew 0

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473079: Cannot contact the admin server. Therefore constructing the Cluster Authority Urzeit from the persisted value

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473080: Error while closing the JNDI context

Cause: See the exception for the exact cause.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-473500: JMS Reporting Data Manager failed to deploy during server start up {0}

Cause: The JMS Reporting Data Manager failed to deploy during server start up. This could be caused by insufficient Security privileges, missing Reporting Tables, or a lost Database Connection.

Action: Please verify the user's Security privileges and the existence of Reporting Tables and/or a Database Connection If there are no Reporting Tables, please run the JMS Reporting Provider Database Script.
Level: 1

Type: ERROR

Impact: Deployment

OSB-473501: The JMS Reporting Data Manager failed to undeploy {0}

Cause: There was a problem with un-deployment: all of the messages were already processed.

Action: Please contact Oracle Support with your log details.
Level: 1

Type: ERROR

Impact: Deployment

OSB-473502: Message reports are not persisted in the Reporting Table for MSG_GUID = {0} {1}

Cause: An unexpected error occurred when creating insert statement for message reports. There should be an error message that points to cause of the problem.

Action: Please contact Oracle Support with your log details.
Level: 1

Type: ERROR

Impact: Data

OSB-473503: A SQL Exception occurred during Message Reporting. Persistence with the SQL State is {0} and the Error Code is {1} {2}

Cause: A SQL Exception occurred while Message Reports were being inserted into the Message table.

Action: Please refer to the log for the source of the failure or contact Oracle Support.
Level: 1

Type: ERROR

Impact: Data

OSB-473504: The JMS Report Data Handler failed to send the message to the JMS Queue : {0} {1}

Cause: The JMS Report Data Handler failed to send a message to the JMS Queue. There may be no JMS Connection Factory or the data may be invalid.

Action: Please refer to the log for the source of the failure or contact Oracle Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-473505: JMS Reporting does not support this type of Database : {0}

Cause: JMS Reporting does not support this type of Database.

Action: Please use a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.
Level: 1

Type: ERROR

Impact: Installation

OSB-473506: An Error occurred while determining the Database type {0}

Cause: The type of Database may not be supported or the Database may be disconnected.

Action: Please check your Database connection and that you are using a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.
Level: 1

Type: ERROR

Impact: Network

OSB-473507: JMS Reporting does not support this type of Database.

Cause: JMS Reporting does not support this type of Database.

Action: Please use a supported Database type. These types include: ORACLE, SQL Server, DB2, SYBASE.
Level: 1

Type: ERROR

Impact: Installation

OSB-473508: The Database connection is disconnected {0}

Cause: Database connection has been lost.

Action: Please check the Database connection.
Level: 1

Type: ERROR

Impact: Network

OSB-473509: The ReportingMDB received an invalid Object {0} and the message will not be processed {1}

Cause: The ReportingMDB received an invalid Object for processing. It requires a ReportMessage type object.

Action: Please contact Oracle Support.
Level: 1

Type: ERROR

Impact: Data

OSB-473510: An unexpected error occurred while processing the message in ReportingMDB {0}

Cause: An unexpected error occurred while processing the message in ReportingMDB.

Action: Please refer to the log for the source of the error or contact Oracle Support
Level: 1

Type: ERROR

Impact: Data

OSB-473511: Failed to lookup the JNDI Provider for the JMS Reporting datasource {0}

Cause: Failed to look up the configured JNDI Provider for the JMS Reporting datasource

Action: Please verify that the JNDI Provider referred to by JMS Reporting is up and running.
Level: 1

Type: ERROR

Impact: Network

OSB-473512: An error occured while retrieving the report data from the Reporting table.

Cause: An error occured while retrieving the report data from the Reporting table.

Action: Please contact Oracle Support.
Level: 1

Type: ERROR

Impact: Network

OSB-473513: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Cause: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Action: Please verify the Payload or contact Oracle support.
Level: 1

Type: ERROR

Impact: Data

OSB-473514: An unexpected error occurred while receiving the message in ReportingMDB {0}

Cause: An unexpected error occurred while receiving the message in ReportingMDB. The message will not be processed.

Action: Please refer to the log for the source of the failure or contact Oracle Support.
Level: 1

Type: ERROR

Impact: Data

OSB-473516: An invalid message format was received in ReportMDB {0}. The message will not be processed. {1}

Cause: An Invalid message format was received. The message will not be processed.

Action: Please verify the Payload or the Report action configuration.
Level: 1

Type: ERROR

Impact: Data

OSB-473517: The JMS Reporting Provider Database tables weren't created and the JMS Reporting Data Manager didn't deploy.

Cause: The JMS Reporting Provider Database tables weren't created and the JMS Reporting Data Manager didn't deploy.

Action: Please run the JMS Reporting Provider Database Script and restart the server.
Level: 1

Type: ERROR

Impact: Deployment

OSB-473518: An error occurred while inserting data into the Reporting Table with a batch update {0}

Cause: The Batch update failed.

Action: Please make sure batch update supports your database JDBC driver.
Level: 1

Type: ERROR

Impact: Data

OSB-473519: An error occurred when initializing the PurgingMDB {0}

Cause: Report messages will not be deleted due to an error in resource initialization.

Action: Please verify that the PurgingMDB is deployed and your database connection.
Level: 1

Type: ERROR

Impact: Deployment

OSB-473520: An error occurred while initializing the ReportingMDB and Database details.

Cause: The ReportingMDB and Database details were not initialized.

Action: Please verify your Database connection.
Level: 1

Type: ERROR

Impact: Deployment

OSB-473521: No transaction is available to process the Report Message.

Cause: No transaction is available to process the Report Message.

Action: Please refer to the log to determine why the transaction is unavailable and/or retry sending the request. If the problem persists, please contact Oracle support
Level: 1

Type: ERROR

Impact: Other

OSB-473522: An error occurred while inserting data into the Reporting Table with Batch Update {0}

Cause: The Batch Update failed.

Action: Please make sure the Batch Update supports the database JDBC Driver.
Level: 1

Type: ERROR

Impact: Data

OSB-473523: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Cause: The document type is not allowed: the Message Body Data must be a String, XmlObject, or Binary.

Action: Please verify the Payload.
Level: 1

Type: ERROR

Impact: Data

OSB-473524: Could not initialize PurgingMDB and Database details.

Cause: Could not initialize PurgingMDB and Database details.

Action: Please verify the Database Connection.
Level: 1

Type: ERROR

Impact: Deployment

OSB-473525: Failed to lookup the JNDI Provider for the JMS Reporting datasource {0}

Cause: Failed to look up the configured JNDI Provider for the JMS Reporting datasource

Action: Make sure that the JNDI provider referred to by JMS Reporting is up and running.
Level: 1

Type: ERROR

Impact: Network

OSB-473526: There is no Database connection.

Cause: There is no Database connection.

Action: Please verify the Network connection.
Level: 1

Type: ERROR

Impact: Network

OSB-473527: There is No Report Index.

Cause: There is a Missing Key-Value pair in the Report Action.

Action: Please add a Key-Value pair to the Report Action.
Level: 1

Type: ERROR

Impact: Data

OSB-482200: The operation {0} is not supported by the provider {1} for user/group {2}.

Cause: Certain management operations WebLogic Server authentication providers are optional. Not all authentication providers support these optional operations. For example, an authentication provider may not support user account creation.

Action: Choose a different authentication provider. If you still need help contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-482201: The user {2} in provider {1} does not have sufficient privileges to execute the operation {0}.

Cause: An attempt was made to perform an operation by a user which does not have sufficient privileges

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-482202: An exception {1} was generated when executing operation {0} for user/group {3} in provider {2}.

Cause: An unexpected error occurred

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-482203: The user {0} already exists in provider {1}.

Cause: An attempt to create a user account failed because a user account with the same username already exists

Action: Make sure the user account does not already exist (possibly on a different authentication provider). You may have to choose a different username for the new user account.
Level: 1

Type: ERROR

Impact: Other

OSB-482204: Invalid user/group {0} supplied.

Cause: An invalid user name or group name was entered.

Action: Make sure you enter a valid user name or group name.
Level: 1

Type: ERROR

Impact: Other

OSB-482205: Invalid password supplied for user {0}: {1}

Cause: The password you entered is invalid

Action: Enter a valid password
Level: 1

Type: ERROR

Impact: Other

OSB-482206: The group {0} already exists in provider {1}.

Cause: An attempt to create a group failed because the group already exists

Action: Make sure the group does not already exist (possibly on a different authentication provider). You may have to choose a different group name.
Level: 1

Type: ERROR

Impact: Other

OSB-494001: Internal error generating navigation menu. No CommandId initialized for action "{0}".

Cause: Internal error generating navigation menu. No CommandId initialized for action.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-494002: Internal error occurred in OSBConsole : {0}

Cause: An unexpected general purpose exception has occurred in OSB Console There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-494003: A request to redirect to an invalid target has been detected. Request={0} address={1} user={2}

Cause: An invalid request has been detected. They may be an open redirect attack. The console has output a critical message to the server log.

Action: Take action based upon provided exception details.
Level: 24

Type: INCIDENT_ERROR

Impact: Other

OSB-494004: A Cross-site request forgery (CSRF) has been detected. Task={0} address={1} user={2}

Cause: CSRF : The console has output a critical message to the server log.

Action: Take action based upon provided exception details.
Level: 24

Type: INCIDENT_ERROR

Impact: Security

OSB-495001: Internal error generating navigation menu. No CommandId initialized for action "{0}".

Cause: Internal error generating navigation menu. No CommandId initialized for action.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-495002: Internal error occured in OSBConsole : {0}

Cause: An unexpected general purpose exception has occurred in OSB Console There should be an error message that points to the cause of the problem.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-495003: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred: {0}

Cause: Cannot Create or Edit or Activate or Exit session because there are unexpected errors occurred. The exception should provide more detail.

Action: Retry the activation.
Level: 1

Type: ERROR

Impact: Other

OSB-800007: Invalid message.

Cause: Invalid message.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800009: Invalid URI.

Cause: Invalid URI.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800010: URI does not start with t3://

Cause: URI does not start with t3://

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800016: Unable to suspend because ref: {0} could not be found.

Cause: Unable to suspend because the ref could not be found.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800017: No end-point is registered with ref: {0}

Cause: No end-point is registerd with the given ref.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800019: Unable to accept the connections and stopped listening on the server Dsp.

Cause: Unable to accept the connections and stopped listening on the server Dsp. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Network

OSB-800020: Unable to resume because ref: {0} could not be found.

Cause: Unable to resume because the ref could not be found.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800021: Unable to start because ref: {0} could not be found.

Cause: Unable to start because the ref could not be found.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800022: Unable to delete because ref: {0} could not be found.

Cause: Unable to delete because the ref could not be found.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800024: Unable to get dispatch policies.

Cause: Unable to get dispatch policies. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800028: DSP transport registration failed.

Cause: DSP transport registration failed. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-800029: Illegal TransportSender type.

Cause: Illegal TransportSender type.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800030: Writing of response to the client is failed.

Cause: Writing of response to the client failed. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800031: Unable to start the service: {0}

Cause: Unable to start the service. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800032: Unable to activate the service: {0}

Cause: Unable to activate the service. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800033: Scheduling it to workmanager is failed.

Cause: Scheduling to the workmanager failed. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800034: DspTransport receiver is failed.

Cause: DSP Transport receiver failed. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800037: No JMX Connector available.

Cause: No JMX Connector available.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800039: DspConfig.xml not found

Cause: DspConfig.xml not found.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Data

OSB-800040: DSP Transport : incoming message is empty

Cause: The incoming message is empty.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800041: Soap Fault Received: {0}

Cause: Soap Fault received.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800042: Error sending message

Cause: Error sending message. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-800043: Error binding socket

Cause: Error binding socket. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Ports

OSB-800044: Error closing socket

Cause: Error closing socket. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Ports

OSB-800045: Error closing socket input stream

Cause: Error closing socket input stream. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Ports

OSB-800046: Error executing query

Cause: Error executing query. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800047: Error processing query result

Cause: Error processing query result. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800048: Invalid uri: {0}

Cause: The uri is invalid. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-800049: Error getting provider configuration

Cause: Error getting provider configuration. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800050: Error searching for URI conflicts

Cause: Error searching for URI conflicts. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800051: Error checking binding type

Cause: Error checking binding type. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-800201: No dvm element found

Cause: DVM document must have a dvm element.

Action: Add 'dvm' element to the document.
Level: 1

Type: ERROR

Impact: Process

OSB-800202: Columns missing in DVM

Cause: Domain names are must in a DVM document

Action: Add domain names to the DVM document
Level: 1

Type: ERROR

Impact: Process

OSB-800203: Rows are missing in DVM document.

Cause: DVM document must have rows.

Action: Add rows to the DVM document.
Level: 1

Type: ERROR

Impact: Process

OSB-800204: Empty or Null DVM.

Cause: String empty or null.

Action: Provide a valid a dvm string.
Level: 1

Type: ERROR

Impact: Process

OSB-800205: Xml is invalid

Cause: Xml is invalid

Action: Provide a valid dvm xml.
Level: 1

Type: ERROR

Impact: Process

OSB-800206: Exception in Dvm Exception {1}

Cause: Exception occured in Dvm function call

Action: Please refer to exception log and rectify the issue.
Level: 1

Type: ERROR

Impact: Process

OSB-800207: Dvm resource parsing failed. Error is {0}

Cause: Dvm resource parsing failed. The exception message should provide more detail.

Action: Check the server log for details.
Level: 1

Type: ERROR

Impact: Process

OSB-800253: Xref resource parsing failed. Error is {0}

Cause: Xref resource parsing failed. The exception message should provide more detail.

Action: Check the server log for details.
Level: 1

Type: ERROR

Impact: Process

OSB-800254: Empty or Null Xref.

Cause: String empty or null.

Action: Provide a valid a xref string.
Level: 1

Type: ERROR

Impact: Process

OSB-800255: Xml is invalid

Cause: Xml is invalid

Action: Provide a valid xref xml.
Level: 1

Type: ERROR

Impact: Process

OSB-800256: Exception in Xref Exception {1}

Cause: Exception occured in Xref function call

Action: Please refer to exception log and rectify the issue.
Level: 1

Type: ERROR

Impact: Process

OSB-2030750: Failed to register MBean

Cause: Failed to register MBean

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-2030751: Failed to register MBeans

Cause: Failed to register MBeans

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-2030800: Failed to refresh OSB-EM Discovery MBeans

Cause: Failed to refresh OSB-EM Discovery MBeans

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-2030801: Failed to register FMW EM Plugin OSBConfigurationMBean

Cause: Failed to register FMW EM Plugin OSBConfigurationMBean

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-2030852: Failed to import: {0}

Cause: Failed to import. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2030853: Invalid plugin file: {0}

Cause: Invalid plugin file. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-2030854: Could not create plugin classloader: {0}

Cause: Could not create plugin classloader. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-2030855: Could not register plugin classloader: {0}

Cause: Could not register plugin classloader. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-2030856: Could not register transport: {0}

Cause: Could not register transport. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-2030857: Could not register resource: {0}

Cause: Could not register resource. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Configuration

OSB-2030900: Failed to initialize deployment handler.

Cause: Failed to initialize deployment handler. The exception should provide more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-2031000: Split-Join deployment error during activation:{0}

Cause: An unexpected error occured while deploying a new/updated Split-Join or un-deploying an existing Split-Join.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Deployment

OSB-2031001: The Activation of Split-Join resources could not be committed because the deployment session has already been closed.

Cause: The Activation of Split-Join resources could not be committed because the deployment session has already been closed. This is an invalid state that could be the result of other session (WLS, OSB) related issues.

Action: The deployment session has not been committed and the server may be in an inconsistent state. If the OSB session has been activated, try to undo and retry the activation. If the problem persists, restarting the server should unlock the sessions. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

OSB-2031002: Load notifications for Split-Join resources cannot be started because a deployment session is already active.

Cause: A deployment session is already active at server startup and a session for the server load notifications cannot be created.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

OSB-2031003: Split-Join deployment error during load notification: {0}{1}

Cause: An unexpected error occured while deploying a Split-Join during server startup.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

OSB-2031004: Load notifications for Split-Join resources could not be committed because the session has already been closed.

Cause: Something has already closed the session. This should not happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Deployment

OSB-2031100: Error converting the response message (Split-Join: ''{0}'' LINK: ''{1}'' Service: ''{2}''): {3}{4}

Cause: An error occured trying to un-marshall the response of a service invocation. A generic fault will be raise in the Split-Join.

Action: Turn on transport level debug log to get more information regarding the response message. If the service being invoked is a proxy service, turning on tracing for that service may also provide more information on the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031101: Error converting the response fault (Split-Join: ''{0}'' LINK: ''{1}'' Service: ''{2}''): {3}{4}

Cause: An error occured trying to un-marshall the fault response of a service invocation. A generic fault will be raise in the Split-Join.

Action: Turn on transport level debug log to get more information regarding the response message. If the service being invoked is a proxy service, turning on tracing for that service may also provide more information on the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031102: Error creating the SOAP Fault from the response fault while calling Split-Join ''{0}'': {3}{4}

Cause: An error occured trying to marshall the fault response into a SOAP Fault. The fault response was processed as if this error did not occur. If an error handler was configured in the calling Split-Join for this fault, and a SOAP Fault variable was defined, then its content will be empty.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031200: Schema validation for {0} failed: {1}

Cause: The schema has been modified other than by the Split-Join editor

Action: Please edit Split-Join using the Split-Join editor
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031201: Failed to parse schema: {0}

Cause: The schema has been modified other than by the Split-Join editor

Action: Please edit Split-Join using the Split-Join editor
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031202: Failed to create validation meta data: {0}

Cause: An unexpected error occurred trying to create meta data from wsdl definitions referenced by Split-Join.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031203: Failed to validate Split-Join: {0}

Cause: An unexpected error occurred during validation of Split-Join

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031300: Variable {0} is assigned a null value.

Cause: The transformation (most probably an assign or replace in that case) did not return any value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. An empty result may be due to missing XML elements/attributes in the data, improper use of namespaces...
Level: 1

Type: ERROR

Impact: Other

OSB-2031301: Variable {0} is assigned an array of values.

Cause: The transformation (most probably an assign or replace in that case) returned more than one value.

Action: Turn on tracing to check the data. Check the data expression for the given transformation. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1).
Level: 1

Type: ERROR

Impact: Other

OSB-2031310: Variable {0} targeted for replace is not XML.

Cause: The variable targeted for replace operation does not hold XML data.

Action: Check that in the Split-Join resource the variable {0} is defined by an XML element or complex type.
Level: 1

Type: ERROR

Impact: Other

OSB-2031311: Content targeted for replace is not an element or an attribute

Cause: Content targeted for replace is not an element or an attribute

Action: Check the value of the variable that is targeted for replace operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031312: An attribute may only be replaced with an attribute

Cause: An attribute may only be replaced with an attribute

Action: Check the value of the variable that is targeted for replace operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031313: An element or its contents may only be replaced with elements and simple values

Cause: An element or its contents may only be replaced with elements and simple values

Action: Check the value of the variable that is targeted for replace operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031320: A Delete action cannot delete a variable.

Cause: This is caused by an invalid XPath expression that is trying to delete the variable.

Action: Check the XPath expression of the Delete action. The XPath expression should not result in the selection of the variable itself (e.g. ".[0]").
Level: 1

Type: ERROR

Impact: Other

OSB-2031330: Variable {0} targeted for insert is not XML.

Cause: The variable targeted for insert operation does not hold XML data.

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031331: Content cannot be inserted before/after the variable itself.

Cause: The Insert is configured to insert before/after the result of the selection, but the result of the selection is the variable itself.

Action: Check the XPath expression of the Insert action. The XPath expression should not result in the selection of the variable itself (e.g. ".[0]").
Level: 1

Type: ERROR

Impact: Other

OSB-2031332: Failed to insert after.

Cause: Inserting the result of this expression after specified XPath resulted in an error.

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031333: Cannot insert as a child of an attribute

Cause: It is illegal to insert as a child of an attribute

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031334: Unable to insert after first child

Cause: Unable to insert after first child as there was no child elements of specified XPath expression

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031335: Unable to insert after last child

Cause: Unable to insert after child element

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031336: Only attributes may be inserted next to another attribute

Cause: Only attributes may be inserted next to another attribute

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031337: Only elements and simple values may be inserted next to or inside of another element

Cause: Only elements and simple values may be inserted next to or inside of another element

Action: Check the value of the variable that is targeted for insert operation.
Level: 1

Type: ERROR

Impact: Other

OSB-2031350: Parameter at index {1} in method "{0}" is assigned an array of values.

Cause: The parameter expression returned more than one value for the parameter at index {1} in method "{0}".

Action: Check the data expression for the given parameter. Such result may happen for example if the selected XML elements/attributes correspond to repeating nodes (XML Schema maxOccurs > 1).
Level: 1

Type: ERROR

Impact: Other

OSB-2031351: Parameter at index {1} in method "{0}" is of type XmlObject but the expression resulted in a simple type.

Cause: The parameter expression returned a simple type value instead of an XML fragment.

Action: Check the data expression for the given parameter. An XML fragment is expected but a simple type is returned.
Level: 1

Type: ERROR

Impact: Other

OSB-2031352: A NumberFormatException was raised for parameter at index {1} in method "{0}": {2}

Cause: A NumberFormatException was raised for parameter at index {1} in method "{0}" during the conversion from the simple type result to the expected java type.

Action: Check the data expression for the given parameter and the schema type of the result. The value returned does not match the expected java type.
Level: 1

Type: ERROR

Impact: Other

OSB-2031353: Callout to java method "{0}" resulted in exception: {1}

Cause: The java method specified in the Java Callout operation was invoked and resulted in an exception. The exception details should be part of the error message.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031354: Security exception while calling to java method "{0}". Service account: "{1}". {2}

Cause: There was an error while setting up the security context for java callout method. This could happen if there is a problem retrieving the credentials of specified service account. There should be a specific error message that will pinpoint the source of the problem.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031400: No Flow Reference specified.

Cause: While trying to create, retrieve or update a Flow Configuration, no reference was specified.

Action: Ensure a Flow Reference is specified
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031401: No configuration details specified.

Cause: While trying to create or update a Flow Configuration, no configuration details were specified.

Action: Ensure Flow configuration is specified
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031402: No operational values specified.

Cause: While trying to update the operational settings for a Flow, no operational settings were specified.

Action: Ensure that operational settings are specified
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031403: No operational settings query specified.

Cause: While trying to return a list of flow refs with a given set of operational values, no operational values were specified.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031404: Expecting ref of type '{0}' but received ref of type '{1}'.

Cause: A flow ref is expected but received incorrect ref.

Action: Please check that the passed is ref is correct and is of type flow ref.
Level: 1

Type: ERROR

Impact: Other

OSB-2031405: An exception occurred trying to suspend the transaction: {0}.

Cause: An unexpected exception occurred while suspending the transaction after invoking an external service.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031410: Error during conversion of fault response to source for Split-Join "{0}". Root cause: {1}

Cause: Message converter could not transform the fault message. The fault message is potentially invalid. The exception should provide more details about the actual error. An attempt will be made to return a fault response with a server error of type http://www.bea.com/alsb/flow/faults:responseProcessingFault.

Action: Make sure the fault message format is correct and conforms to the style/use specified in the wsdl associated with flow. Please correct the fault message and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-2031411: Error during conversion of response to source for Split-Join "{0}". Root cause: {1}

Cause: Message converter could not transform the response message. The response message is potentially invalid. The exception should provide more details about the actual error. An attempt will be made to return a fault response with a server error of type http://www.bea.com/alsb/flow/faults:responseProcessingFault.

Action: Make sure the response message format is correct and conforms to the style/use specified in the wsdl associated with Split-Join. Please correct the response message and try again.
Level: 1

Type: ERROR

Impact: Other

OSB-2031412: Unable to dispatch fault response for "{0}" due to error creating response metadata. Root cause: {1}

Cause: This is an unexpected error. This should not normally happen.

Action: Please make sure product installation is complete. Restart the server. Make sure there are no errors during server startup. Make sure Split-Join is deployed correctly. If error persists, contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031413: Error during conversion of default server fault response to source for Split-Join "{0}". Root cause: {1}

Cause: Message converter could not transform the fault message. The fault message is potentially invalid. The exception should provide more details about the actual error.

Action: Make sure the fault message format is correct and conforms to the style/use specified in the wsdl associated with Split-Join. Please correct the fault message and try again.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031414: Unable to dispatch response for "{0}" due to error creating response metadata. Root cause: {1}

Cause: This is an unexpected error. This should not normally happen.

Action: Please make sure product installation is complete. Restart the server. Make sure there are no errors during server startup. Make sure Split-Join is deployed correctly. If error persists, contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031415: Error during scheduling response for "{0}". Root cause: {1}

Cause: The exception should provide the root cause for the error

Action: Please correct the error before trying again.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031416: No statistics were returned for Split-Join {0} and server {1}.

Cause: The exception should provide the root cause for the error

Action: Please correct the error before trying again.
Level: 1

Type: ERROR

Impact: Other

OSB-2031417: No statistics were returned for Split-Join {0}.

Cause: The exception should provide the root cause for the error

Action: Please correct the error before trying again.
Level: 1

Type: ERROR

Impact: Other

OSB-2031418: An exception occurred trying to resume the transaction: {0}.

Cause: An unexpected exception occurred while resuming the transaction on the response thread.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031500: Unable to determine which inbound messaging activity to deliver message to. The message matches multiple inbound messaging activities with the same operation ''{1}'' but different correlation sets.

Cause: The inbound message has been rejected because it matches more than 1 enabled inbound messaging activity with the same partner link and operation but different correlation sets. It cannot be determined which inbound messaging activity the message should be delivered to. This is potentially due to a timing issue. See WS-BPEL 2.0, section 10.4 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031501: The completion condition for counter ''{0}'' can never be true.

Cause: The counter will never complete. See WS-BPEL 2.0, section 11.7 for more detail.

Action: Revise the counter so that it can complete.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031502: An inbound messaging activity is already enabled for operation ''{1}''.

Cause: A receive activity was processed that, if successfully enabled, would have resulted in more than 1 receive waiting for the same message. If more than 1 receive is enabled for the same partner link, operation and correlation set it would result in multiple targets for inbound messages. This is potentially due to a timing issue. See WS-BPEL 2.0, section 10.4 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031503: An inbound messaging activity is already enabled for operation ''{1}''.

Cause: It is illegal to have more than 1 inbound messaging activity enabled with the same partner link, operation and message exchange token. See WS-BPEL 2.0, section 10.4.1 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031504: The counter ''{0}'' defines ''{1}'' iterations but the completion condition requires ''{2}'', so it will never complete.

Cause: The counter has processed to the point where it will never complete (For example, the counter may require 8 more iterations but there will only be 6). See WS-BPEL 2.0, section 11.7 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031506: The expression evaluated to a type of ''{1}'' but a type of ''{0}'' was expected.

Cause: An expression evaluated to an incompatible type for assignment. See WS-BPEL 2.0, sections 8.4.2 and 8.4.3 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031507: The message for operation ''{1}'' has not been replied to.

Cause: The partner link for an outstanding message exchange has just gone out of scope so the exchange will never be replied to. See WS-BPEL 2.0, section 10.4.1 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031508: Unknown message exchange for operation ''{1}''.

Cause: An attempt was made to reply to a non-existent message exchange. See WS-BPEL 2.0, section 10.4.1 for more detail.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031509: Executing an expression caused an unhandled fault: {0}.

Cause: An unexpected error occurred while executing an expression. The exception message should provide details of the cause.

Action: Correct the error specified in the exception message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031510: The partner role ''{0}'' is uninitialized.

Cause: An attempt was made to access a partner link before it was initialized. This should never happen (it should be caught by validation during deployment).

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031511: The source for doXslTransform has {0} items, when exactly 1 is required.

Cause: The source for the doXslTransform function contains an XML document with other than 1 root node.

Action: Ensure that the source contains only 1 root node.
Level: 1

Type: ERROR

Impact: Other

OSB-2031512: The source for doXslTransform is of unsupported type ''{0}''. Supported types are {1}.

Cause: The source for doXslTransform is an unsupported type. This should never happen.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031513: The XSL stylesheet ''{0}'' was not found.

Cause: The XSL stylesheet could not be found on the class loader hierarchy.

Action: Ensure that the stylesheet can be found on the class loader hierarchy.
Level: 1

Type: ERROR

Impact: Other

OSB-2031514: The message for process ''{0}'' and operation ''{2}'' is rejected because a previous message for the same is waiting to be processed (possible out of order).

Cause: A message was received by the process for a partner link, operation and correlation sets when one is already waiting to be processed. One possible reason for this is that the messages were received out of order.

Action: Resend the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031515: The <from> element ''{0}''is not substitutable for the <to> element ''{1}''.

Cause: The EII selected by the from-spec is not substitutable for the EII selected by the to-spec. If the from-spec and the to-spec select EIIs with different element names, then the from-spec element must belong to the substitutionGroup of the to-spec element (as determined by the schema definitions for the elements).

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031518: Variable ''{0}'' is being referenced before it has been initialized with a value.

Cause: The variable is being referenced before it has been initialized. This is generally a problem with the process definition but it could be a timing issue.

Action: Modify the process to ensure that the variable is always initialized before it is referenced.
Level: 1

Type: ERROR

Impact: Other

OSB-2031519: Inbound message ''{0}'' cannot initialize variable because it is incomplete.

Cause: The inbound message is missing at least one part.

Action: Ensure that the message contains all the parts defined on the message type for the input message of the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031520: Outbound message ''{0}'' cannot be sent because it is incomplete.

Cause: The outbound message is missing at least one part.

Action: Ensure that the message contains all the parts defined on the message type for the output message of the operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031521: Expression ''{0}'' returned {1} items when exactly 1 is required.

Cause: Expressions (particularly those used in Copy) should return a single item. If the expression evaluates to 0 or more than 1 item it is an exception.

Action: Ensure that the expression selects a single item.
Level: 1

Type: ERROR

Impact: Other

OSB-2031522: Nested transactions are not supported.

Cause: An attempt was made to start a new transaction when one was already active. This is not supported. This should never happen (because transactions cannot be explicitly started currently).

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

OSB-2031600: Correlation set ''{0}'' has an invalid initiate value of ''{1}''.

Cause: The correlation set has an invalid value. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031601: Unable to deliver the message for process ''{0}'' and operation ''{2}''. It does not match any start activity.

Cause: The inbound message does not match a start activity and it contains no correlation properties. As such, it will never be able to be delivered to a process instance.

Action: Either modify the message so it will correlate (different process, partner link, operation or correlation properties) or modify the process.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031602: Unable to deliver the message for process ''{0}'' and operation ''{2}''. It does not match any inbound messaging activities.

Cause: There are no inbound message activities for the partner link and operation of the message. The message cannot be delivered to any instance of the given process.

Action: Either modify the message so it does match an inbound messaging activity (different process, partner link or operation) or modify the process to match the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031603: The message for process ''{0}'' and operation ''{2}'' correlated to some inbound messaging activities but they were removed when the best matches were selected.

Cause: While correlating the incoming message, some messaging activities were found but after ranking them, there was no "best" match selected. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031604: The message for process ''{0}'' and operation ''{2}'' correlated to some inbound messaging activities on process instance ''{3}'' but the activities were removed when the best matches were selected.

Cause: While correlating the incoming message, a specific process instance was selected but there were no messaging activities for the partner link and operation. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031605: Unable to determine which process instance to deliver the message to. The message for process ''{0}'' and operation ''{2}'' matches multiple process instances.

Cause: The incoming message correlates to multiple process instances. This means that there was more than 1 process instance to which the message could be delivered.

Action: Either modify the message so it only matches one process instance (different process, partner link, operation or correlation properties) or modify the process.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031606: Unable to determine which start activity to deliver the message to. The message for process ''{0}'' and operation ''{2}'' matches multiple start activities.

Cause: The incoming message correlates to multiple start activities in the process instance. This means the message cannot be delivered. This is a problem with the process definition.

Action: Modify the process definition to define only a single start activity for the same partner link and operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031607: Unable to determine correlation properties. Correlation set ''{0}'' has not been initiated on process instance ''{1}''.

Cause: A correlation set that has an initiate value of "NO" has not been initiated. An initiate value of "NO" means that the correlation set should already be initiated before being used to correlate an inbound message.

Action: Modify the process to ensure that all correlation sets are initiated before they are used.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031608: Unable to determine correlation properties. Correlation set ''{0}'' has already been initiated.

Cause: A correlation set that has an initiate value of "YES" has already been initiated. An initiate value of "YES" means that the correlation set should NOT be initiated as it will be initiated using the values of the inbound message.

Action: Modify the process to ensure that correlation sets are NOT initiated before they should be.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031609: Unable to determine correlation properties. Correlation set ''{0}'' has different property values.

Cause: A message that has already been matched to a messaging activity has different correlation properties than the correlation set values associated to the messaging activity. This generally occurs for outbound messages (since the inbound messages wouldn't have matched this instance if they didn't match).

Action: Ensure that the outbound message has the same correlation properties as the messaging activity.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031610: Unable to deliver the message for process ''{0}'' and operation ''{2}''. It does not match any existing process instance.

Cause: While correlating the incoming message, message properties were calculated but did not match any existing process instance. It is possible that this message will match a process instance in the future.

Action: Resend the message.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031650: No value found for variable ''{0}'' and property ''{1}''.

Cause: The variable value does not contain the specified property.

Action: Ensure that the variable does contain the specified property.
Level: 1

Type: ERROR

Impact: Other

OSB-2031651: A selection operation returned a 'nil' XML.

Cause: The expression evaluated to an XML object specified as a 'nil' value.

Action: Ensure that the expression evaluates to a non-'nil' value.
Level: 1

Type: ERROR

Impact: Other

OSB-2031652: Scripting language ''{0}'' is not supported.

Cause: The scripting language is not supported. This should be caught by validation during deployment.

Action: Modify the process to use a supported scripting language.
Level: 1

Type: ERROR

Impact: Other

OSB-2031653: The context node is of unsupported type ''{0}'' when it is required to be of type ''{1}''.

Cause: The context node for the expression is not of the expected type. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031654: Variable ''{0}'' is a message. It must be either a variable defined by a schema type or a schema variable or a message part.

Cause: The variable used in the expression is defined as a message type. Message type variables cannot be referenced directly - only their parts can be referenced. This should be caught by validation during deployment.

Action: Modify the expression to use the $(variable).(part) syntax.
Level: 1

Type: ERROR

Impact: Other

OSB-2031655: Variable ''{0}'' is not a message but is being referenced as though it has a part ''{1}''.

Cause: The variable is being used via the $(variable).(part) but it is not a message type variable. This should be caught by validation during deployment.

Action: Modify the expression to use only $(variable) syntax.
Level: 1

Type: ERROR

Impact: Other

OSB-2031656: Variable ''{0}'', defined as message type ''{1}'', does not contain part ''{2}''.

Cause: The variable is defined by a message type that does not have the given part. This should be caught by validation during deployment.

Action: Modify the expression to use a part that the message type does have.
Level: 1

Type: ERROR

Impact: Other

OSB-2031657: The xml fragment for the literal has more than 1 root element.

Cause: An XML literal must have a single root element. This should be caught by validation during deployment.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031700: Trying to add a null input message to exchange for operation ''{1}''.

Cause: A null input message cannot be added to a message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031701: Trying to add a second input message to exchange for operation ''{1}''.

Cause: An input message can only be set once on a message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031702: Exchange for operation ''{1}'' does not support input messages.

Cause: An input message can only be added to a message exchange that is expecting an input message. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031703: Input message ''{0}'' is not for exchange with operation ''{2}''.

Cause: An input message can only be added to a message exchange if it is of the same message type as the input message in the WSDL operation for the message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031704: Trying to add a null output message to exchange for operation ''{1}''.

Cause: A null output message cannot be added to a message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031705: Trying to add a second output message to exchange for operation ''{1}''.

Cause: An output message can only be set once on a message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031706: Exchange for operation ''{1}'' does not support output messages.

Cause: An output message can only be added to a message exchange that is expecting an output message. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031707: Output message ''{0}'' is not for exchange with operation ''{2}''.

Cause: An output message can only be added to a message exchange if it is of the same message type as the output message in the WSDL operation for the message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031708: Trying to add a null fault message to exchange for operation ''{1}''.

Cause: A null fault message cannot be added to a message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031709: Trying to add a second fault message to exchange for operation ''{1}''.

Cause: A fault message can only be set once on a message exchange. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031710: Part ''{0}'' is not part of message ''{1}''.

Cause: The part is not defined in the message type. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031711: Message ''{0}'' is unknown.

Cause: The message type is unknown. This should never happen.

Action: Contact Oracle Support Servicesl Support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031750: The <to> evaluates to null.

Cause: The ''to'' node of a copy evaluates to null. It should evaluate to a a non-null value.

Action: Ensure that the ''to'' node evaluates to a non-null value.
Level: 1

Type: ERROR

Impact: Other

OSB-2031751: The <from> evaluates to null.

Cause: The ''from'' node of a copy evaluates to null. It should evaluate to a a non-null value.

Action: Ensure that the ''from'' node evaluates to a non-null value.
Level: 1

Type: ERROR

Impact: Other

OSB-2031753: The value returned is a ''{0}'' when a boolean was required.

Cause: Conditions should evaluate to a boolean value but this condition did not.

Action: Ensure that the condition always evaluates to a boolean value.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031754: Received an unexpected response for invoke (operation is ''{0}'').

Cause: The Invoke received a response from the invocation but it was not expected because the exchange pattern was not IN_OUT.

Action: Ensure that the partner link being invoked has the expected exchange pattern.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031755: Expected a fault or output response for invoke but got neither.

Cause: The Invoke expected a response from the invocation but none was received.

Action: Ensure that the partner link being invoked has the expected exchange pattern of IN_OUT.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2031757: The alarm definition ''{0}'' defines no deadline, duration or repeat interval.

Cause: An alarm must contain a deadline, duration or a repeat interval. This should be caught by validation during deployment.

Action: Modify the alarm to define a deadline, duration or a repeat interval.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031758: The value returned ''{0}'' must be positive.

Cause: A repeat interval must be a positive integer.

Action: Ensure that the repeat every interval expression evaluates to a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031759: The expression ''{0}'' is an invalid deadline.

Cause: The deadline expression must evaluate to an XML Schema date or datetime.

Action: Ensure that the deadline expression evaluates to an XML Schema date or datetime.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031760: The expression ''{0}'' is an invalid duration. It should be in the form PnYnMnDTnHnMnS.

Cause: The duration expression must evaluate to an XML Schema duration. eg. For 1 day and 10 seconds use P1DT10S See http://www.w3.org/TR/xmlschema-2/#duration for details.

Action: Ensure that the duration expression evaluates to an XML Schema duration.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031762: WSDL operation for operation ''{1}'' not found.

Cause: The WSDL operation was not found in the process metadata. This should be caught by validation during deployment.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031763: The completion condition must be a number, but the expression evaluated to ''{0}''.

Cause: The completion condition must evaluate to an XML Schema unsigned integer.

Action: Ensure that the completion condition evaluates to an XML Schema unsigned integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031764: The completion condition value of ''{0}'' is invalid.

Cause: The completion condition must evaluate to a positive integer.

Action: Ensure that the completion condition evaluates to a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031765: Timer expression ''{0}'' is invalid: {1}

Cause: The timer expression is not valid according to the XML Schema for deadlines or durations (depending on which expression it is). The exception message should indicate where the error is.

Action: Correct the expression according to the exception message.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031766: The date value ''{0}'' is invalid.

Cause: The date value is not a valid XML Schema date or datetime.

Action: Ensure that the date is a valid XML Schema date or datetime.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031768: The start counter value must be a number, but the expression evaluated to ''{0}''.

Cause: The start counter value must evaluate to an XML Schema unsigned integer.

Action: Ensure that the start counter value evaluates to an XML Schema unsigned integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031769: The start counter value of ''{0}'' is invalid.

Cause: The start counter value must evaluate to a positive integer.

Action: Ensure that the start counter value evaluates to a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031770: A final counter value must be a number, but the counter evaluated to ''{0}''.

Cause: The final counter value must evaluate to an XML Schema unsigned integer.

Action: Ensure that the final counter value evaluates to an XML Schema unsigned integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031771: The final counter value ''{0}'' is invalid.

Cause: The final counter value must evaluate to a positive integer.

Action: Ensure that the final counter value evaluates to a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

OSB-2031800: Resource ''{0}'' not found.

Cause: The specified resource cannot be found via the class loader.

Action: Ensure that the resource is on the class loader hierarchy.
Level: 1

Type: ERROR

Impact: Files

OSB-2031801: Resource ''{0}'' is invalid.

Cause: The resource does not conform to the http://www.bea.com/bpel/operation XML schema.

Action: Ensure that the resource conforms to the schema.
Level: 1

Type: ERROR

Impact: Other

OSB-2031802: XPath ''{0}'' is invalid for loading operations: {1}.

Cause: The XPath used in loading operations is a subset of XPath 1.0. The exception message should detail the reason it is invalid.

Action: Correct the errors detailed in the exception message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031803: XPath defines no components.

Cause: The XPath used for loading operations contains no XPath steps.

Action: Ensure that the XPath contains at least one XPath step.
Level: 1

Type: ERROR

Impact: Other

OSB-2031804: Property ''{1}'' on class {0} is read only.

Cause: Unable to inject a value into the class for the property as there is no setter method.

Action: Either update preprocess.xml to not inject the property or add a public setter method.
Level: 1

Type: ERROR

Impact: Other

OSB-2031805: Property ''{1}'' on class {0} has an unsupported type.

Cause: Unable to inject a value into the class for the property as it is an unsupported type. Only simple JavaBean types are supported.

Action: Either remove the injection from preprocess.xml or change the property type.
Level: 1

Type: ERROR

Impact: Other

OSB-2031806: Property ''{1}'' on class {0} is not found.

Cause: Property does not exist on the class.

Action: Either remove the injection from preprocess.xml or add the property.
Level: 1

Type: ERROR

Impact: Other

OSB-2031807: An XmlObject that matches the xpath ''{0}'' has no line numbers.

Cause: The XmlObject was created without line numbers. Line numbers are required to use XPath expressions. This should not happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031808: The class {0} is not found.

Cause: The class {0} is not found.

Action: Ensure the class is on the classpath.
Level: 1

Type: ERROR

Impact: Other

OSB-2031809: An error occurred introspecting class {0}: {1}.

Cause: Unable to introspect on the class.

Action: Correct the errors detailed in the exception message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031810: An error occurred create a new instance of class {0}: {1}.

Cause: Unable to create a new instance of the class.

Action: Correct the errors detailed in the exception message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031856: Partner link {0} not found.

Cause: A partner link was not found.

Action: Ensure that the partner link is in scope.
Level: 1

Type: ERROR

Impact: Other

OSB-2031857: Correlation set {0} not found.

Cause: A correlation set was not found.

Action: Ensure that the correlation set is in scope.
Level: 1

Type: ERROR

Impact: Other

OSB-2031858: Thread {0} has a job in the job queue.

Cause: An attempt was made to create a new job for the thread but there is already a job in the job queue for it. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031859: The job queue capacity has been reached. No more jobs can be added.

Cause: The job queue capacity has been reached. No more jobs can be added. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031860: Thread {0} has an invalid status.

Cause: An attempt was made to start processing the given thread but it's status is invalid for processing. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031900: Variable type ''{0}'' is unsupported.

Cause: The variable type is unsupported. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031901: <to> must evaluate to a message.

Cause: The ''to'' value should be a message. This should be caught by validation during deployment.

Action: Ensure that the ''to'' value evaluates to a message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031902: <from> must evaluate to a message.

Cause: The ''from'' value should be a message. This should be caught by validation during deployment.

Action: Ensure that the ''from'' value evaluates to a message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031903: <to> is a ''{0}'' message but <from> is a ''{1}'' message.

Cause: The ''to'' and ''from'' need to be the same message type. This should be caught by validation during deployment.

Action: Ensure that the ''from'' and ''to'' evaluates to messages of the same message type.
Level: 1

Type: ERROR

Impact: Other

OSB-2031904: Creating partner links is not supported.

Cause: Creating partner links is not supported. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031905: Cloning partner links is not supported.

Cause: Cloning partner links is not supported. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031906: <to> must be a partner link.

Cause: An attempt was made to set a non-partner link value to a service reference. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031907: Creating text nodes is not supported.

Cause: Creating text nodes is not supported. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031908: Cloning text nodes is not supported.

Cause: Cloning text nodes is not supported. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031909: <to> must be a text node.

Cause: An attempt was made to set a non-text node value to a text value. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031910: <to> must be an xml object.

Cause: An attempt was made to set a non-XML object value to an XML object. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2031911: Variable ''{0}'' is invalid: {1}.

Cause: A variable has an invalid value. The reason should be specified in the exception message.

Action: Correct the error as detailed in the exception message.
Level: 1

Type: ERROR

Impact: Other

OSB-2031912: The keepSrcElementName attribute has been set but the from-spec and to-spec are not both EIIs.

Cause: The keepSrcElementName on the Copy element is only allowed to be used when both the from-spec and to-spec are EIIs. If either the from-spec or to-spec is NOT an EII, the keepSrcElementName MUST NOT be explicitly set.

Action: Ensure that the expressions for the from-spec and to-spec select EIIs.
Level: 1

Type: ERROR

Impact: Other

OSB-2032000: Error during invocation of "{0}" for event "{1}" of type "{2}".

Cause: There are several reasons for the invocation to fail. The exception must provide details to help identify the reason for the failure.

Action: Fix the artifact based on the exception. If the exception is not clear contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032001: Fatal error: Unable to invoke "{0}" for event "{1}" of type "{2}" as "{0}" does not exist.

Cause: The artifact invoked does not exist. This is probably due to the fact that there were errors during deployment or the session used to deploy is not activated yet.

Action: Make sure the invoked artifact is correct, deployed correctly and the session used to deploy the artifact is activated without errors.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032002: Received unknown message exchange "{0}" on reply. Reply will be ignored.

Cause: Reply expects message exchange of type "RequestResponseMessageExchange". However, received an unknown message exchange. Hence, reply will be ignored

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032003: Neither output nor fault is set on response for message exchange "{0}" for blocking request with key "{1}". Reply will be ignored.

Cause: Either output or fault must be set on a response. However, neither is set for the message exchange.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032004: Callback listener is missing for message exchange "{0}" for non-blocking request with key "{1}". Reply will be ignored.

Cause: Callback listener that is used to dispatch the reply for non-blocking requests is missing. Hence, the reply can not be dispatched.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032005: Neither output nor fault is set on response for message exchange "{0}" for non-blocking request with key "{1}". Reply will be ignored.

Cause: Either output or fault must be set on a response. However, neither is set for the message exchange.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032006: Unknown data type "{2}" found for data in dispatcher cache for request with message exchange "{0}", with key "{1}". Reply will be ignored.

Cause: Type of data found in dispatcher cache is unknown. Hence, reply can not be dispatched.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032007: Timeout for event "{0}" can not be dispatched as the key (used to look up request entry in the dispatcher cache)is null. Timeout will be ignored.

Cause: This error could be due to a system defect in garbage collection or unique id generation. This could also be due to data corruption.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032008: Unknown data type "{0}" found for data, with key "{1}", in the dispatcher cache when trying to dispatch timeout event for a non-blocking request. Timeout will be ignored.

Cause: System defect or data corruption is the cause of this failure.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032009: Error Dispatching the Event: unexpected error. - {0}.

Cause: The exception message should describe the cause.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032010: Error Dispatching the Event: the service-ref is unsupported. - {0}.

Cause: The exception message should describe the cause.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032100: Scheduler can not dispatch request to engine as the process "{0}" is not found. Request will be ignored.

Cause: The process is no longer deployed and active. Either the process is undeployed or session activation failed during process deployed as the session had errors.

Action: Make sure the process is deployed correctly. If error persists, please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032101: Scheduler can not dispatch request to engine for process "{0}" as the message exchange is null. Request will be ignored.

Cause: Message exchange is null.

Action: This is an unexpected error. Please contact support.
Level: 1

Type: ERROR

Impact: Requests/Responses

OSB-2032400: Failed to acquire lock on {0}.

Cause: An attempt to acquire a lock failed because the object is already locked by another transaction. This generally happens when different threads on the same process instance try to lock the same object. The transaction will be added as blocked to the object and will be locked when the current lock is released.

Action: Nothing. The lock will be acquired when current lock is released.
Level: 1

Type: ERROR

Impact: Other

OSB-2032401: {0} does not own lock on {1}.

Cause: An attempt to unlock an object was made by a transaction that does not own the lock. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

OSB-2032402: There is no current transaction.

Cause: An attempt was made to suspend the current transaction, but there is no current transaction. This should never happen.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

44 SOA-10000 to SOA-65070

SOA-10000: Import type {0} is not currently defined. The only valid import types are "wsdl" and "edl". If you are attempting to import an xsd file, please do so through a WSDL document.

Cause: The import type specified for the composite import is unrecognized

Action: Make sure the import type is one of the currently recognized types (.edl, .wsdl)
Level: 1

Type: ERROR

Impact: Configuration

SOA-10001: No binding node (e.g. <binding.ws>) found for {0}. Please make sure that the composite specifies a binding of a given type.

Cause: No bindings are configured for the given service or reference

Action: Check that the composite's services and references specify at least one binding.
Level: 1

Type: ERROR

Impact: Configuration

SOA-10002: Unable to add a code source to the composite classloader due to an exception. Please ensure that the proper resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.

Cause: Unable to add a code source to the composite's classloader due to an exception

Action: Ensure that resources are available in the SCA-INF/classes, SCA-INF/gen-classes, and SCA-INF/lib composite archive sub-directories.
Level: 1

Type: ERROR

Impact: Deployment

SOA-10003: Failed to retrieve the application topology node from the TopologyService using {0}.

Cause: Unable to retrieve a toplogy node from the Toplogy Service

Action: Please check whether the toplogy node path is valid
Level: 1

Type: ERROR

Impact: Deployment

SOA-10004: Failed to create MAS-enabled componentType lookup; {0}.

Cause: Unable to create a strategy that enables the lookup of .componentType files in a MAS environment

Action: Make sure the toplogy node path, composite home directory, and strategy class name are correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-10005: Failed to retrieve {0} document from topology node {1}.

Cause: Unable to retrieve a document from the topolgy node

Action: Make sure the toplogy node path, composite home directory, and the document name are correct
Level: 1

Type: WARNING

Impact: Other

SOA-10006: Error occurred while retrieving {0} document from topology node {1}. The underlying cause was a {2}.

Cause: An error occurred during the retrieval of a document from a topology node

Action: Make sure the resource path is valid and that the deployment succeeded
Level: 1

Type: ERROR

Impact: Configuration

SOA-10007: Error occurred while attempting to retrieve message part {0} from a normalized message payload with elements {1}.

Cause: An attemp to retrieve a message part of a given name from a Normalized Message failed

Action: Make sure that there is no mismatch between the WSDL defined part name and a configured part name
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-10008: Error occurred during deployment of component: {0} to service engine: {1}, for composite: {2}

Cause: An error occurred during component deployment

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Deployment

SOA-10009: Error occurred during creation of domain/instance noun: {0}

Cause: An error occurred during creating noun for domain/instance

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Configuration

SOA-10010: Error occurred while getting portable mbean factory: {0}

Cause: An error occurred while getting portable mbean factory

Action: Please check the root cause of the failure
Level: 1

Type: ERROR

Impact: Configuration

SOA-20000: Message Router for {0} is null. Please validate that the composite deployment completed successfully by checking the server logs.

Cause: There is no message router found for the composite

Action: Check that the composite deployment completed successfully
Level: 1

Type: ERROR

Impact: Deployment

SOA-20001: Message Router for {0} is not able to process messages. The composite state is set to "off". The composite can be turned "on" by using the administrative consoles.

Cause: The composite state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the composite to enable processing
Level: 1

Type: ERROR

Impact: Configuration

SOA-20002: No path info set for provider invocation. Unable to determine composite and service for processing.

Cause: There is no path information in the inovcation URI that facilitates routing of the message to the composite service

Action: Make sure that the invoking URL is of the form http://host:port/soa-infra/services/applicationName/compositeName/serviceName
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20003: Unable to register service.

Cause: There was an issue during the attempt to create the endpoint for the composite service

Action: Make sure that the WSDL either has a service and port that correspond to the values specified in the composite file or that there is no empty service node in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20004: Unable to deregister service.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20006: Unable to register reference {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20007: Cannot find binding component for service "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given service binding type

Action: Make sure that the binding type specified for the composite's service is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20008: Cannot find binding component for reference "{0}".

Cause: There is no binding component configured in the SOA Platform that can handle the given reference binding type

Action: Make sure that the binding type specified for the composite's reference is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20009: Cannot find service engine for component "{0}" in composite "{1}".

Cause: There is no service engine configured in the SOA Platform that can handle the given component implmentation type

Action: Make sure that the implementation type specifed for the composite's component is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20010: Unable to find Binding Component for type "{0}".

Cause: No binding component found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured binding component
Level: 1

Type: ERROR

Impact: Configuration

SOA-20011: Unable to find Service Engine for type "{0}".

Cause: No service engine found for the given type

Action: Make sure the configured type has a corresponding SOA Platform configured service engine
Level: 1

Type: ERROR

Impact: Configuration

SOA-20012: Unable to find component or reference identified by "{0}".

Cause: Unable to find a component or reference of the given name in the composite

Action: Make sure the composite wires are properly formed and reference existing components and/or references
Level: 1

Type: ERROR

Impact: Configuration

SOA-20013: MDS Root mis-configuration.

Cause: The MDS root directory is misconfigured

Action: Make sure the composite directories specified in the deployed-composites.xml file are correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-20018: Cannot read WSDL "{0}" from Metadata Manager.

Cause: There was a problem reading a WSDL document from the MDS repository

Action: Make sure the composite imports point to the valid WSDL paths
Level: 1

Type: ERROR

Impact: Deployment

SOA-20019: Object "{0}" does not exist in metadata repository.

Cause: The requested file or resource does not exist in the MDS repository

Action: Make sure the resource path is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20020: Deployment of composite "{0}" failed: {1}.

Cause: Unable to deploy the composite

Action: Check the associated exception for more information
Level: 1

Type: ERROR

Impact: Deployment

SOA-20021: Undeployment of composite "{0}" failed: {1}.

Cause: There was an error generated during the undeployment of a composite

Action: Check the associated exception for more information concerning the undeployment issue
Level: 1

Type: ERROR

Impact: Deployment

SOA-20025: Failed to find a WSDL Definition for service: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20026: Failed to find composites to deploy based on path: "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20027: Unable to create interceptors, InterceptorChainFactory may not be defined for "{0}".

Cause: There was a problem creating an interceptor chain associated with the composite

Action: Make sure that the interceptor chain factories are configured in the SOA platform's configuation file located in the fabric war's WEB-INF directory
Level: 1

Type: ERROR

Impact: Deployment

SOA-20028: Unable to create mbeans for the composite "{0}" because of error "{1}".

Cause: There was an error generated during the creation of the composite MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20029: Unable to unregister mbean for the composite "{0}" because of error "{1}".

Cause: There was an error while attempting to unregister the composite MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20030: Unable to unregister deployed composites runtime mbean because of error "{0}".

Cause: There was an error while attempting to unregister the deployed composites MBean

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20031: An active composite for "{0}" has already been registered. Only one active composite is allowed.

Cause: An attempt was made to deploy an active composite for an application that already has an active composite

Action: Make sure that only one active composite is associated with a given application. You can deactive/activate composites via the management consoles
Level: 1

Type: ERROR

Impact: Deployment

SOA-20032: The composite "{0}" is retired. New instances cannot be initiated.

Cause: An attempt was made to initiate a composite instance using a retired composite

Action: Make sure to create a new instance with an active composite. The composite mode can be configured via the management consoles
Level: 1

Type: ERROR

Impact: Deployment

SOA-20034: No composite found for application "{0}", composite name "{1}" and revision "{2}".

Cause: An attempt was made to reload a composite application for which resources can not be found in the metadata repository

Action: Make sure that the application name, composite name, revision, and label specify a valid metadata store
Level: 1

Type: ERROR

Impact: Configuration

SOA-20035: Composite "{0}" has already been loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20036: Composite "{0}" has been loaded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20037: Composite home directory "{0}" does not exist.

Cause: The composite home directory specified is not valid

Action: Make sure the composite home directory specified in deployed-composites.xml is valid
Level: 1

Type: ERROR

Impact: Deployment

SOA-20038: Composite "{0}" does not exist.

Cause: No composite message router was found for the specified composite

Action: Make sure the composite distinguished name specified is valid and that the composite application deployed successfully
Level: 1

Type: ERROR

Impact: Deployment

SOA-20039: Operation not supported.

Cause: An attempt was made to undeploy using the deployment update mechanism

Action: N/A
Level: 1

Type: ERROR

Impact: Deployment

SOA-20040: Message exchange pattern not currently supported.

Cause: The attempted message exchange pattern is not supported

Action: Make sure that the composite wiring is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20041: Deployment failure on rollback: {0}

Cause: An error was raised during an attempt to rollback a composite deployment

Action: Make sure that all composite resources have been removed
Level: 1

Type: ERROR

Impact: Deployment

SOA-20042: Not enough information to ascertain composite name from pathInfo "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20043: No deployed composite found for path "{0}".

Cause: The path information in the URI was not sufficient enough to identify a composite

Action: Make sure that the URL used to invoke the composite service has the proper application name, composite name, revision, and label
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20044: Unable to retrieve resource "{0}" associated with composite "{1}".

Cause: An attempt to retrive a composite application associated resource (e.g. a WSDL file) failed

Action: Make sure the URL specified is correct
Level: 1

Type: ERROR

Impact: Deployment

SOA-20045: No WSDL URL provided

Cause: No WSDL URI was specified for the composite associated WSDL

Action: Make sure the WSDL import in the composite file is valid and specifies a URI for the file
Level: 1

Type: ERROR

Impact: Deployment

SOA-20046: Deployment of MBEANS for composite "{0}" failed: {1}.

Cause: There was a problem deploying the composite MBeans

Action: Check the associated exception for more information. There may have been a problem deregistering the MBean during a previous undeployment.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20047: Unable to initialize composite parser: {0}.

Cause: Unable to initialize the composite parser

Action: Make sure that any parser providers registered in the fabric war web.xml file are valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20048: Unable to discover local host name: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20049: Unable to register composite loader due to exception: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20050: Binding components failed to create holder type for {0}.

Cause: The required holder class is not available on the classpath

Action: Make sure the holder class is available in the classpath
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20051: Return value from the Java Service method {0} is invalid.

Cause: The service returned a value of a different type than was expected

Action: Verify that the service and the WSDL correspond
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20052: Binding Component failed to access holder value for {0}.

Cause: Unable to call a setter/getter on the holder class instance

Action: Make sure the access method is public
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20053: Binding Component is unable to locate operation {0} for java service {1}.

Cause: The requested method does not exist on the target service class

Action: Verify that the target service implements all methods defined in the WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20054: Binding Component failed to invoke method {0}.

Cause: The requested method of the target service is not public

Action: Verify that the targets service's methods are public
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20055: Missing WebResult method annoation for java service {0}.

Cause: The @WebResult annotation is not defined for the service interface

Action: Make sure the @WebResult annotation is specified in the service interface
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20056: Could not locate service for {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20057: Could not find invocation context containing sdo metadata for component {0}.

Cause: The requested service is not registered

Action: Make sure the service is registered and named correctly
Level: 1

Type: ERROR

Impact: Deployment

SOA-20058: Could not find registry for {0}.

Cause: The requested service registry does not exist

Action: Make sure that the registry is available and named correctly
Level: 1

Type: ERROR

Impact: Deployment

SOA-20059: Unable to copy the WSDL definition due to exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20060: Partname metadata for the parameter {0} is missing.

Cause: A parameter of a method of the service interface is missing the @PartName annotation

Action: Make sure the @PartName annotation is specified for the parameters of the method
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20061: Input argument {0} has a wrong parameter java type.

Cause: Unable to create an instance of a parameter value

Action: Make sure the parameter classes are available and have default constructors
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20097: Binding component is unable to load schema from this location: {0}

Cause: Could not load an imported schema

Action: Make sure the schema is available in the location specfied in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20098: Binding component failed to initialize.

Cause: There was an internal error during initialization

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20099: WSDL port metadata in composite {0} not found

Cause: There was an internal error during load

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20100: Binding component failed to register Metadata types with SDO provider.

Cause: There was an internal error during load

Action: Please contact support
Level: 1

Type: ERROR

Impact: Deployment

SOA-20101: Metadata for operation {0}, service {1} can not be found.

Cause: The operation was not defined in the service WSDL

Action: Make sure the operation is defined in the service WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20102: An error occurred while scheduling deployment. Exception reported is "{0}"

Cause: There was an error while attempting to schedule a deployment

Action: Check the associated exception for the cause of the error
Level: 1

Type: ERROR

Impact: Deployment

SOA-20104: The composite for model "{0}" is not found!

Cause: There was an error during retrieval of the service associated composite

Action: Make sure the composite is valid
Level: 1

Type: ERROR

Impact: Configuration

SOA-20106: Binding Component is unable to load schema at "{0}" due to missing system id in the referencing source schema.

Cause: Unable to load schema due to missing system id in the referencing WSDL or schema

Action: Ensure the system id is defined in the WSDL
Level: 1

Type: ERROR

Impact: Deployment

SOA-20107: Configuration Error in Java Binding. Unable to find portType or interface.

Cause: Service or port names were not specified in the binding configuration

Action: Make sure the service and port name are available in the binding configuration
Level: 1

Type: ERROR

Impact: Configuration

SOA-20108: The resource "{0}" not found in the composite "{1}"

Cause: Unable to retrieve a resource from the composite's MDS repository

Action: Make sure the resource path specified, relative to composite URI, is correct
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20109: Invocation Exception: {0}:

Cause: The service generated an error during invocation

Action: Ensure that the service is operating correctly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20110: This {0} method is not implemented!

Cause: One way operations are not supported for SDO dynamic stubs

Action: Consider using an alternate message exchange pattern
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20111: Binding Component failed to create user defined faults.

Cause: A SOAP fault was generated by the service invocation

Action: Ensure that the service is operating properly. The fault may be expected.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20112: The called service raised a fault.

Cause: The service generated an exception

Action: Ensure that the service is operating properly
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20113: Unable to access the following endpoint(s): {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20114: Unable to update reference instance with response payload due to exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20115: Illegal modification to existing composite {0}. Changes are not allowed to elements of the composite distinguished name (application name, composite name, revision, and label). If you are attempting a re-deployment of a failed deployment, please undeploy and then deploy the composite.

Cause: The attempted change of the deployed composite file was not valid

Action: Make sure the change you are making is allowed
Level: 1

Type: ERROR

Impact: Deployment

SOA-20116: Only changes to policy references of {1} of composite {0} are supported by the Web Service Binding Components. All other changes (e.g. changes to the port attribute of a binding) will be ignored.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20117: The wire target URI {1}/{2} for composite {0} is not valid. No service {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid service names.

Cause: The composite wire appears to be malformed since no such component/service pair exists

Action: Please check the componentType file for the component for valid service names.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20118: The wire source URI {1}/{2} for composite {0} is not valid. No reference {2} is defined for component {1} in its componentType file. Please check the componentType file for component {1} for valid reference names.

Cause: The composite wire appears to be malformed since no such component/reference pair exists

Action: Please check the componentType file for the component for valid reference names.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20119: Unable to find a WSDL that has a definition for service {0} and port {1}. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.

Cause: Unable to find a WSDL that has a definition corresponding to the provided service and port names

Action: Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20120: Unable to find a composite definition in {0}. Please make sure there is a composite.xml definition file that defines a composite with the same name as the composite name in the composite JAR name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20121: An attempt was made to deploy a composite ''{0}'' that has already been deployed. This is an internal error, and does not require any action. The original composite definition remains in effect.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20122: Unable to find a file named ''adf-config.xml'' in the search path starting at {0}. The ''adf-config.xml'' file is required to configure the MDS instance used for composite deployment. Repackage the composite application, providing an MDS store a and namespace named after the composite name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20124: Unable to process the MDS configuration at {0}. Please verify the formatting and contents of the ''adf-config.xml'' file. Also, check the rest of the log for MDS failures, which could help point out the root cause of the processing failure.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20125: Cannot create an XSLT transformer. Please ensure that your JAXP environmentis properly configured with an XSLT 1.0 transformer.

Cause: Unable to create the adf-config xml transformer

Action: Make sure the adf-config file is property formatted
Level: 1

Type: ERROR

Impact: Deployment

SOA-20126: Updating MDS configuration at {0} with file-based MDS root {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20127: Exception when processing MDS configuration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20128: The context header qname is invalid or malformed. Please check that the correct context header qname is specified for the contextHeadersQNames property in the fabric-config.xml file

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20129: Could not create a context header due to exception

Cause: Unable to create the context header

Action: Ensure that the context provider implementation is valid and working
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20130: Entry Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20131: External Binding Component: invocation of service {0}, operation {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20132: Binding Component found port type: {1}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20133: Binding Component registered the following schema with SDO implementation within context of classloader {1} ==> {0}

Cause:

Action:
Level: 32

Type: TRACE

Impact: Other

SOA-20134: No annotation found on service interface.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20135: Exception creating JAXWS servant. Exception: {0}, Message: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20136: WS Binding: exception during SOAP invocation: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20138: No oracle-archive.xml found; will use file scanning for application ''{0}''

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20139: Unable to find a registered server for pathInfo {0}. Please ensure that the given composite is deployed. If this is occurring during the processing of a callback, please make sure that the "#" delimiter in the callback URL is properly encoded.

Cause: The path provided in the invocation URI does not map to a deployed composite

Action: Make sure the URI is correct and references a deployed composite application
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20141: Schema validation failed for message part {0}. Please ensure at the message sender level that the data sent is schema compliant.

Cause: Validation of the message part against its schema failed.

Action: Please take actions at the message sender to ensure that the data is schema compliant.
Level: 1

Type: ERROR

Impact: Data

SOA-20143: Unable to register a service endpoint for a defined reference callback. Please ensure the WSDL and reference configuration are correct.

Cause: Unable to register a callback endpoint for the defined reference callback

Action: Make sure that the application configuration is correct. For example, ensure that the associated WSDL does not have any mis-spelled message names.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20144: Unable to find a target component or reference based on invocation context {0}. Please check the composite file and make sure a wire exists for the specified reference or source URI.

Cause: Unable to find a wire for the reference

Action: Make sure that the service or component reference is actually wired to a target
Level: 1

Type: ERROR

Impact: Deployment

SOA-20145: The serviceName/serviceID attribute is missing.

Cause: Unable to find serviceName attribute for the binding

Action: Make sure that the serviceName is specified in the composite
Level: 1

Type: ERROR

Impact: Deployment

SOA-20146: Unable to deploy service {0} with multiple WS bindings. Please make sure there is only one WS binding for the given service in the composite file.

Cause: Unable to deploy a service with multiple WS bindings

Action: Make sure that the service has only one WS binding
Level: 1

Type: ERROR

Impact: Deployment

SOA-20147: javaInterface name for the binding is missing or the interface class is not available.

Cause: Unable to find javaInterface attribute for the binding

Action: Make sure that javaInterface attribute is specified on the composite
Level: 1

Type: ERROR

Impact: Deployment

SOA-20148: null

Cause: Failure in looking up EJB

Action: Make sure JNDI properties, jndi name specified are correct.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20149: Caller is not in allowed role!

Cause: Failure in authenticating ejb invocation

Action: Make sure invocation client has the right role mapped.
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-20150: SOA EJB Invoker could not load bean interface class defined for service {0}.

Cause: Failure in loading ejb interface class

Action: Make sure interface class is included in the deployment package.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20151: SOA EJB Invoker could not locate composite for service {0}.

Cause: Failure in locating composite

Action: Make sure the composite configuration is correct
Level: 1

Type: ERROR

Impact: Configuration

SOA-20152: SOA EJB Invoker could not locate method named {0} with {1} of arguments on interface class {2} for service.

Cause: Failure in locating method

Action: Make sure the composite configuration is correct
Level: 1

Type: ERROR

Impact: Configuration

SOA-20153: Failure in processing jps credential store properties, exception stack: {0} .

Cause: Failure in processing credential store properties

Action: Make sure the properties are specified correctly or permission to access the the store has been setup.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20154: The path "{0}" has already been used by another direct binding. Please select a different path override.

Cause: Illegal pathOverride used in composite configuration. The alias name has already been used for other another direct binding.

Action: Select a different path alias for the direct binding component.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20155: Expected protocol ''soadirect'', got ''{0}'' instead.

Cause: Illegal protocol used in direct binding composite configuration.

Action: Correct path should start with "soadirect"
Level: 1

Type: ERROR

Impact: Configuration

SOA-20156: Invalid service path "{0}".

Cause: Service Path used in the invocation is invalid.

Action: Correc the service path.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20157: Service not found for path "{0}".

Cause: Service not found for the path name used in the invocation.

Action: Check composite configuration to see if the path name used matches.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20158: Direct binding component failed to initialize.

Cause: Exception occured during the direct binding component initialization.

Action: Check the exception for detailed failure cause.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20159: Direct binding component not initialized.

Cause: Direct binding component has not been initialized.

Action: Check server startup log to see any detailed exception log.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20160: Could not obtain keystore location or password

Cause: Could not obtain the keystore location or password for setting up 2 Way SSL

Action: Make sure that the keystore is available in the default location or is specified in the SOA configuration. In addition, make sure the keystore password is configured in the credential store.
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-20161: Unable to create SSL Socket Factory

Cause: Could not create the SSLSocketFactory for supporting 2 Way SSL

Action: Check the associated exception for the cause of the failure.
Level: 1

Type: ERROR

Impact: Network

SOA-20168: Could not find a port for the dynamic reference given service name {0} and port type {1}

Cause: Could not find a port that matched the supplied service name and port type for the dynamic reference

Action: Check the dynamic reference configuration and the supplied WSDL to ensure proper configuration.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20169: Folder {0} is not able to process messages. The folder state is set to "off". The folder can be turned "on" by using the administrative consoles.

Cause: The folder state or mode do not allow processing of messages

Action: Use the management consoles to set the mode and state of the folder to enable processing
Level: 1

Type: ERROR

Impact: Configuration

SOA-20170: Partition {0} does not exist. Make sure the partition was created and exists.

Cause: The folder can not be found

Action: Check the folder name and make sure such a folder was created and exists
Level: 1

Type: ERROR

Impact: Configuration

SOA-20171: Cannot find port type {0} in the WSDL. Make sure the port type is defined in the WSDL

Cause: The port type cannot be found

Action: Check the WSDL and make sure the port type is defined in the WSDL
Level: 1

Type: ERROR

Impact: Configuration

SOA-20172: No source URI specified for the given invocation or callback. Please make sure there is a wire specified for the context {0}.

Cause: No source URI for the wire

Action: Check the composite and make sure a wire is defined for the interaction.This is most likely an indication of an error in the wiring.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20173: @WebService or @PortableWebService annotation is required, but not found on {0}.

Cause: Interface class does not contain @WebService annoation.

Action: Add @WebService annotation that describes the service in the interface class.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20174: Failed to get application helper context using service id ''{0}''.

Cause: Unable to create application helper context.

Action: Check the underlying cause from the SDO implementation.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-20175: Binding property {0} overridden by a message property of the same name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20176: Both csf-key and username/password have been set. The csf-key will be used for authentication processing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20177: Could not lookup the service endpoint from UDDI either due to a UDDI connection error or the provided ServiceKey {0} was invalid.

Cause: Could not lookup service endpoint from UDDI. Either by error on UDDI connection or invalid ServiceKey

Action: Check the OSR-UDDI inquiryUrl configuration and the supplied ServiceKey to ensure proper configuration.
Level: 1

Type: ERROR

Impact: Configuration

SOA-20178: Unsupported interface type: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20179: Ejb Binding is not found.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20180: Unable to load interface class {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20181: Unknown service: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20182: JNDI name {0} already exists.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20183: Could not find method {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20184: Ejb Reference binding failed to invoke ejb.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20185: Ejb Reference binding failed to create jndi initial context.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20186: No ejb registered with the jndi name: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20187: Invalid EJB2 beans. Create method returned null for : {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20188: Failed to invoke create method on the bean.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20189: Invalid bean. EJB2 reference does not implement Home interface.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20190: Unable to register JNDI binding.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20191: Unable to unregister JNDI binding.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20192: No response for invocation.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20193: Conversion of BizFault failed.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20194: Java based Ejb service binding started a transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20195: Java based Ejb service binding committed the transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20196: Java based Ejb service binding rollback the transaction.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20197: Failed to initialize ADR home directories.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20206: Failed to register SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20207: Failed to deregister SOA diagnostic dumps, DFW (diagnostic framework) not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20208: Failed to deregister SOA diagnostic dumps, local soa dumps registry not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20209: No MBean server found, can not register SOA dump: soa.env.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20210: Can not find facade locator, the following SOA diagnostic dumps not registered: {0}, {1}, {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20211: Failed to look up SOA data source: jndi = [{0}], soa.db dump can not be registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20212: SOA data source not available (NULL), soa.db dump not registered.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20213: JNDI context not available, can not look up SOA data source, no DB dump (soa.db) registration.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20214: Not registering SOA incident rules file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20215: Not unregistering SOA incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20216: Not registering custom incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20217: Not unregistering custom incident rules file {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20265: No binding found for reference [{1}] of composite [{0}]. A callback endpoint can not be created. Please make sure the composite is deployed to this server.

Cause: There is no reference binding available or deployed

Action: Check that the composite deployment completed successfully and is targeted for this server.
Level: 1

Type: ERROR

Impact: Deployment

SOA-20266: The composites {0} failed during server startup. Please check the logs for more information.

Cause: Composites failed in deployment during server restart

Action: Check the associated exception for more information
Level: 1

Type: ERROR

Impact: Deployment

SOA-20273: Failed to activate weblogic config changes. FailureException: {0}, Failure Message: {1}. {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20274: Failed to cancel pending weblogic onfig changes. Failure Message: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20275: Failed to initialize FolderAppRoleManager. Partition specific soa roles will not be created. Failure: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20277: An error occurred while creating the application role named [{0}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20278: An error occurred while looking up local jndi edit config mbean. {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-20279: An error occurred looking up workmanager named [{0}], use workmanager named [{1}] instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20280: Created workmanager named [{0}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20281: Error occurred while destroying a partition.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20282: Approle [{0}] for the folder already exists. It will be deleted and recreated.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20283: Failed to lookup soainfra application name, using [soa-infra] instead.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20284: Failed to set AppSecurityContext id to soa application.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20285: JAXBConfigPersistenceHandler is null. WorkManagerGroup configuration changes will not be persisted.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-20286: FolderAppRoleManager was not initialized properly. Partition roles will not be created.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20287: Failed to readjust workmanager MaxThreadsConstraint based on soa datasource max capacity size.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20289: Cannot find the capacity constraint named [{0}] in the domain.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20290: Default SOA WorkManager is used for {0} work execution since the partition workmanager is not available. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20291: SOA Executor WorkManager work with id [{0}] has been rejected. {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20298: Error caught when registering SOA dump: [{0}], error message: [{1}], stacktrace: [{2}]

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20304: Failed to look up SOA data source: jndi = [{0}], soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20305: JNDI context not available, can not look up SOA data source, soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20306: SOA data source not available (NULL), soa.edn registered but not able to capture diagnostic in DB.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20307: Invalid format used for the cluster operation message.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-20309: Failed to process workmanager group cluster notification message for [{0} {1} operation].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20311: Failed to activate max thread configuration update. A restart will be necessary.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-20315: Failed to save rejected message for service [{0}] of binding type [{1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21500: Error occurred when creating target MDS instance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21501: Error occurred when rolling back MDS label.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21502: Error occurred when creating MDS label.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21503: MDS store of namespace {0} does not have versioning support. Cannot be used in MAS based deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21504: Only single composite is supported in a SAR archive.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21505: Invalid composite name in undeploy: {0}, both composite name and revision need to be specified.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21506: Cannot find revision in undeploy : {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21507: Error reading deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21508: Cannot find composite deployment coordinator.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21509: Error in reading data from deployer client.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21510: There was an error deploying the composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21511: Cannot find archive: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21512: Data transfer error in MDS.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21513: Command {0} not supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21514: MDS Transfer directory {0} already exists for composite {1}. Removing and replacing to deploy new version of composite.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21515: Cannot find composite {0} in sar file : {1}. Abort deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21516: Cannot find base composite for: {0}. Abort redeployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21517: Composite with same revision ID already exists: {0}. Please set the overwrite flag or use different revision ID. Abort deployment.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21518: Protocol {0} is not supported. Only http is supported.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21519: Error parsing composite {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21520: Cannot find shared data archive: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21521: Error removing archive data from MDS for composite: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21522: Error occurs in applying deployment plan {1} to sar file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21523: Composite {0} cannot be automatically set as default due to state: {1} or mode: {2}. The state needs to be on and the mode needs to be active.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21524: Error occurred in processing sar file {0} before transferring into MDS store. Please make sure the sar file is a valid jar file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21525: Cannot find JPS context: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21526: Error occurs in checking JPS role.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21527: User {0} doesn''t have the privilege of deploying/undeploying composites. Only users of SOAAdmin/SOAOperator role are authorized to deploy/undeploy composites.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21528: There was an error undeploying composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21529: There was an error deploying/undeploying composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21530: CompositeDeploymentServlet-----> received request from user: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21531: CompositeDeploymentServlet-----> completed deployment/undeployment successfully. Time spent: {0} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21532: CompositeDeploymentServlet initialized.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21533: User [{0}] has been successfully authorized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21534: Start unzipping data to base directory: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21535: Complete unzipping data.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21536: Calling DeployManager to attach deployplan: {0} to SAR file: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21537: Sending back error message: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21538: Removing temporary directory: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21539: Perform deployment operation with redeploy flag: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21540: Perform undeployment operation: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21541: Calling coordinator to undeploy {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21542: Undeploying revision: {0}.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21543: Deploying SAR file: {0} to domain: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21544: Deploying shared data file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21545: Calling coordinator to deploy {0}, with isForceDefault flag: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21546: Calling coordinator to update composite. base composite: {0}, new composite: {1}, isForceDefault flag: {2}, keepInstancesOnRedeploy flag: {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21547: AutoDeployer-> starting deploying shared data file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21548: AutoDeployer-> shared data file {0} was successfully deployed. Time spent: {1} sec. This file will be removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21549: AutoDeployer-> starting deploying SAR file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21550: AutoDeployer-> SAR file {0} was successfully deployed. Time spent: {1} sec. SAR file will be removed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21551: AutoDeployer-> removing temporary MDS data directory {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21552: Preparing transferring data into MDS for package: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21553: Transferred data into MDS successfully for package: {0}. Transferred size: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21554: Removed extra data from MDS successful for package: {0}. Removed size: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21555: Preparing removing data from MDS for package: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21556: Removed data from MDS successfully for package: {0}. Removed size: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21557: CompositeDeploymentServlet-----> completed deploying {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21558: CompositeDeploymentServlet-----> completed undeploying {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21559: CompositeDeploymentServlet-----> completed redeploying {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21560: Cannot remove temporary directory: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-21561: Removing label {0} in namespace {1} of MDS storage

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21562: Composite from sar file: {0} already exists in the target server. Will NOT attempt redeployment and this sar file will be removed from the autodeploy directory.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21563: The composite ({0}) imported a shared library: {1}/{2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21564: The classloader for the shared library ({1}/{2}) referenced by the composite ({0}) cannot be found.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-21566: There was an error exporting composite on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21567: Sending back jar file: {0} of length: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21568: CompositeDeploymentServlet-----> completed exporting composite {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21569: CompositeDeploymentServlet-----> completed exporting post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21570: CompositeDeploymentServlet-----> completed importing post deployment updates {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21571: There was an error exporting post deployment changes on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21572: There was an error importing post deployment changes on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21573: CompositeDeploymentServlet-----> completed exporting shared data of pattern {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21574: There was an error exporting shared data on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21575: adf-config.xml file cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21576: Cannot find adf-config file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21577: Cannot get adf-config file URL: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21578: Cannot create SOA MDS instance.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21579: Cannot find composite: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21580: Cannot find deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21581: The composite name in composite.xml of the jar file: {0} does not match the composite name to be updated: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21582: The composite revision in composite.xml of the jar file: {0} does not match the composite revision to be updated: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21583: Composite does not exist, cannot import updates: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21584: Composite label cannot be null: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21585: Error read deployed-composites.xml: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21586: Cannot find deployed-composites.xml to save.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21587: Cannot update deployed-composites.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21588: There was an error removing shared data on {1}: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21589: CompositeDeploymentServlet-----> completed removing shared data of folder {0} successfully. Time spent: {1} sec.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21590: Error occurred when modifying the revision in composite.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21591: Cannot find Fabric lifecycle: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21592: SOA platform is not fully started. Please retry later.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21593: Calling coordinator to deploy resource files.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21598: Calling coordinator to patch composite {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21800: Merge tools failed: {0}. Please check log file for more information.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21801: Cannot find merge tool registration file: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21802: Cannot parse mergetool-registry.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21803: Please use JDeveloper to customize the composite of new revision before merge, since the composite of previous revision had been customized.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21804: Invalid target found when creating BindingContainerProxy, target::{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21805: Invalid target type when calling {0}, instance::{1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21806: Error building composite model from: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21807: ReferenceConfigModel not available for key={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21808: Invalid inputs, difference in reference entries found original composite.xml {0} DT@RT composite.xml {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21809: Exception [{0}] when creating composite model serializer, exception message: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21810: Error [{0}] when creating composite model serializer, error message: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21811: Error [{0}] when marshaling composite model into XML, error message: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21812: Can not create the merged composite.xml file at path={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21813: Exception when write to merged composite.xml at path={0}, exception=[{1}]

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21814: Invalid target found when creating PolicyReferenceContainerProxy, target::{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21815: Invalid target found when creating PropertyContainerProxy, target::{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21816: Invalid location for composite application, it must be a directory where artifacts of the composite reside, the parameter is [{0}]

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21817: Missing directory where the resulted composite.xml will be written...

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21818: Exception when parsing composite.xml: e={0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21819: Inconsistency found between v2 and the result composite.xml regarding callbacks in {0} with key = {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21820: Inconsistency found between v1 and DT@RT composite.xml regarding callbacks setting, parent type=[{0}], key={1} in v1 composite.xml has callback : {2}, in DT@RT composite.xml has callback {3}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21821: Inconsistent binding configuration detected between v1 composite.xml and DT@RT composite.xml, binding in v1:[{0}], binding in DT@RT:[{1}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21822: Inconsistency found between v1 and DT@RT composite.xml regarding services setting, service[key={0}] in v1 composite.xml {1}, in DT@RT composite.xml {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21823: Inconsistency found between v1 and DT@RT composite.xml regarding components setting, component[key={0}] in v1 composite.xml {1}, in DT@RT composite.xml {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21824: Missing composite.xml for [{0}]

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-21825: No merge operation, the composite.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21826: Cannot find composite sar file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21827: File: {0} is not a composite sar file because composite.xml is not found in this file.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21828: No merge operation, the sensor.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-21829: No merge operation, the sensorAction.xml containing DT@RT customization does not present at [{0}].

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22000: The shared library "{0}" is not deployed; Thus, it cannot be redeployed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22001: The shared library "{0}" is already deployed

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22002: Deploying new shared library: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22003: Redeploying shared library: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22004: Found shared library "{0}" in the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22005: Found version {1} of shared library "{0}" in the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22006: {0} was removed from the MDS repository

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22007: {0} was not removed from the MDS repository

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22008: {0} was not removed from the MDS repository (It may not be empty)

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22009: Failed to remove shared library {0}/{1} from the MDS repository

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22010: SharedLibraryDeploymentCoordinator not found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22011: {0} is not a directory

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22012: Failed to delete {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22013: {0} does not exist, so nothing to delete.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-22014: Shared library {0}/{1} has subscribers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-22015: The shared library {0}/{1} cannot be undeployed because it is referenced by one or more composites: {2}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-22016: A shared library classloader named {0} was created for {1}/{2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22017: The classloader {0} for shared library {1}/{2} has been committed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22018: The following codesources were added to the shared library ({0}/{1}) classloader: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-22019: The classloader {0} for shared library {1}/{2} has been closed.

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-25000: set user and password...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25001: set config plan...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25002: sarLocation cannot be found: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25003: ---->Deploying composite success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25004: ---->Response code={0}, error:{1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25005: Exception:{0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25006: ---->Undeploying composite ({0}) success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25007: Config plan was successfully attached.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25008: Must provide a sar file or composite.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25009: Config plan file already exists, please provide overwrite as true to overwrite the file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25010: Config plan was successfully generated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25011: Config plan was successfully extracted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25012: Config plan was successfully validated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25013: Report file already exists, please provide overwrite as true to overwrite the file.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25014: Ant script does not exist: {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25015: oracle.home is not available. Please provide this property.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25016: Cannot find ANT script $oracle.home/bin/ant-sca-compile.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25017: Invoking ANT script: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25018: Cannot find ANT script $oracle.home/bin/ant-sca-package.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25019: Cannot find ANT script $oracle.home/bin/ant-sca-test.xml.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25020: Cannot find composite lifecycle mbean.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25021: Composite ({0}) is successfully started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25022: Composite ({0}) is successfully stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25023: Composite ({0}) is successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25024: Composite ({0}) is successfully retired.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25025: Composite ({0}) is successfully set as default composite.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25026: Invalid update type: {0}, please choose among: none/all/property/runtime.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25027: Removing existing sar file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25028: ---->Export composite success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25029: Invalid update type: {0}, please choose among: all/property/runtime.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25030: Removing existing jar file: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25031: ---->Export updates success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25032: ---->Cannot find post deployment property updates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25033: ---->Cannot find post deployment runtime/metadata updates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25034: ---->Cannot find any post deployment updates.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25035: ---->Import updates success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25036: ---->Export shared data success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25037: ---->Cannot find shared data of given pattern: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25038: Calling composite store mbean to export composite...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25039: Composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25040: Calling composite store mbean to export composite with all post deployment updates ...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25041: Composite with all post deployment updates was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25042: Calling composite store mbean to export composite with property post deployment updates ...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25043: Composite with property post deployment updates was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25044: Calling composite store mbean to export composite with runtime post deployment updates ...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25045: Composite with runtime post deployment updates was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25046: No connection to a server exists. This operation can be executed only in the online mode.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25047: INFO: SOA server down, use domain runtime mbean...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25048: Cannot find composite store mbean on this server.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25049: Calling composite store mbean to export all post deployment updates, if any...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25050: All post deployment updates of the composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25051: Calling composite store mbean to export property post deployment updates, if any...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25052: Property post deployment updates of the composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25053: Calling composite store mbean to export runtime post deployment updates, if any...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25054: Runtime post deployment updates of the composite was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25055: Calling composite store mbean to import post deployment updates...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25056: Post deployment updates was successfully imported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25057: Calling composite store mbean to export shared data...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25058: Shared data was successfully exported.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25059: ---->Remove shared data success.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25060: Partition was successfully created.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25061: Cannot find folder lifecycle mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25062: Partition was successfully deleted.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25063: All composites in the partition were successfully started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25064: All composites in the partition were successfully stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25065: All composites in the partition were successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25066: All composites in the partition were successfully retired.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25067: Cannot find jar file: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25068: Merge completed successfully, created merged updates in jar file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25069: Merge completed but no jar file created, check log file for details: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-25070: Found multiple composite store mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25071: Found multiple domain runtime composite store mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25072: Cannot find composite store mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25073: start composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25074: Found multiple composite lifecycle mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25075: Cannot find composite lifecycle mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25076: stop composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25077: activate composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25078: retire composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25079: assign default composite operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25080: get default composite revision operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25081: list deployed composites operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25082: list composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25083: create partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25084: Found multiple folder mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25085: delete partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25086: start composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25087: stop composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25088: activate composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25089: retire composites in partition operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25090: list all partitions operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25091: Found multiple EDNConfig mbeans.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25092: Cannot find EDNConfig mbean on this server.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25093: EDN event delivery is successfully enabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25094: enable EDN events operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25095: EDN event delivery is successfully disabled.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25096: disable EDN events operation failed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25097: SOA Platform is running and accepting requests.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25098: SOA Platform is not ready: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-25103: Composite ({0}) endpoint ({1}) is successfully activated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25104: Composite ({0}) endpoint ({1}) is successfully deactivated.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25105: Requested updates cannot be found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-25106: Requested shared data cannot be found.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-30000: Received event: Subject: {2} Sender: {1} Event: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30001: Error closing queue connection

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30002: Error shutting down

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30003: Error enqueueing event

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-30004: Error closing queue session

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30005: Invalid consistency level {2} for event {0} to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-30006: No processor registered for target {0}

Cause: No business event processor is registered for the target

Action: Make sure the service engine or event target supports business events
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-30007: Processor threw exception "{2}" during onEvent for event {0} sent to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-30008: Sent event {1} to {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-30009: Ignored event named {1} from {0} to supress potential infinite recurison

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31000: Received event: Subject: {2} Sender: {1} Event: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31001: Error closing queue connection

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31002: Error shutting down

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31003: Error enqueueing event

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31004: Error closing queue session

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31005: Invalid consistency level {2} for event {0} to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31006: No processor registered for target {0}

Cause: No business event processor is registered for the target

Action: Make sure the service engine or event target supports business events
Level: 1

Type: ERROR

Impact: Requests/Responses

SOA-31007: Processor threw exception "{2}" during onEvent for event {0} sent to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31008: Sent event {1} to {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-31009: Ignored event named {1} from {0} to suppress potential infinite recurison

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-31033: Sent OAOO event [QName: "{1}" to target: "{0}"]: {2}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-50000: Failed to locate partition {0}: {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50001: Failed to create a DirectConnectionFactory instance ({0}): {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50002: The composite {0} could not be found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50003: Skipped recovery attempt for fault {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50004: Recovery attempt for fault {0} failed : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50005: Exception encountered during recovery attempt: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50006: The {0} service engine does not support automated fault recovery

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50007: The composite {0} is not in a state for which recovery can be performed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50008: Fault is unrecoverable

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50009: Incorrect job type: {0} ; Expected {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50010: Updated status for asynchronous job {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50011: Recorded results for asynchronous job {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50012: The results for job {0} are not available because the processing has not yet completed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50013: Processing asynchronous {0} job {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50014: The processing of asynchronous job {0} failed: {1} : {2}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50015: This method is only valid for references with a single binding whose interface is defined by a WSDL definition.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50016: The binding interface is not defined by a WSDL definition.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50017: The specified migration plan document is invalid.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50018: The root element of the specified migration plan document is invalid; expected {0}, but was {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50019: Invalid filterExpression: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50020: Missing required FlowInstanceFilter Criteria: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50021: Missing required SensorFilter Criteria: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50022: A complete composite DN must be specified on the instance filter.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50023: A complete composite DN is required: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50024: The target revision is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50025: A valid migration report is required.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50026: Invalid migration job identifier: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50027: Invalid flow migration report.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50028: There is no migration result for job {0} because processing failed: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-50029: Internal error. {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50030: Unable to migrate instances during upgrade.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-50031: Unable to generate migration report during upgrade.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-55000: This profile contains the standard SOA platform and the BPM technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55001: This profile contains the SOA Foundation technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55002: This profile contains the BPEL SOA components.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55003: This profile contains the BPEL and Workflow technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55004: This profile contains the standard SOA platform and the BPM technologies, plus the FULL adapter set.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55005: This profile contains the SOA Foundation technologies, plus the FULL adapter Set.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55006: This profile contains the SOA Foundation technologies as well as the B2B technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55007: This profile contains the standalone B2B/Healthcare technologies.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55008: This profile contains the SOA platform and BPM technologies enabled in version 11g. This profile is meant for upgrade use cases.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55009: This profile contains the SOA platform technologies enabled in version 11g. This profile is meant for upgrade use cases.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Deployment

SOA-55010: Error occurred while trying to get the current SOA Profile name.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

SOA-55011: Error occurred while trying to obtain profile description for profile {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

SOA-55012: Error occurred while trying to query the status of the SOA Technology {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Deployment

SOA-55013: Error occurred while trying to change the current profile to {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55014: Error occurred while trying to get the domain directory from JRF.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55015: Error occurred while trying to get the domain install templates from CIE.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55016: Errors occurred while trying to obtain the list of supported profiles for this SOA domain. This likely means that there is a configuration error with the domain.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55017: No Profile found with this name {0}. Please select from one of the supported profiles.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55018: Exception occurred while trying to change profiles to {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55019: Error while attempting to get admin server connection info.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55020: Error occurred while creating WebLogic deployment Manager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55021: No profile commands registered with this manager. This is likely a problem with the initialization of the profile manager.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55022: Attempt to change the current SOA Profile has failed. Please check the server log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55023: Error occurred while trying to update the current SOA Profile to {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55024: Attempt to deploy internal modules failed during a targeting change for application {0}. Please check the server log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55025: Attempt to undeploy internal modules failed during a targeting change for application {0}. Please check the server log for details.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55026: Error during edit session operation. The operation that failed is {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55027: Error occurred while trying to obtain the AppDeploymentMBean for application {0}. The MBean is not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55028: Error occurred while trying to obtain the source path for application {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55029: Error occurred while waiting for a deployment operation to complete. Deployment command is null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55030: Error while trying to setup internal modules. Application {0} not available.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55031: Error in internal module setup for application {0}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55032: Error in internal module operation {0}. Deployment result is {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55033: No Targets were found that support soa-infra. This is a deployment error or an installation problem.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55034: Start module attempt for module name {0} failed. Deployment status = {1}.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55035: Set of {0} modules for the new profile cannot be null.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55036: Set of {0} modules for the new profile cannot be empty.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55037: Exception encountered during {0} module targeting for SOA profile transition.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55038: Module name {0} to be targeted is not found. This could be an installation problem, or could mean that a profile was chosen that does not match with the components installed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55039: Module name {0} to be un-targeted is not found. This could be an installation problem, or could mean that a profile was chosen that does not match with the components installed.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55040: Error occurred during targeting operations for a SOA Profile transition.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-55041: The Modularity operation for the following modules: ({0}) has timed out waiting for a server deployment operation to complete. Please increase the value of the {1} system property and restart the server before attempting this command again.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Deployment

SOA-60000: No processor registered for asynchronous job type: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-60001: Skipped recovery attempt for fault {0} : {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60002: Recovery attempt for fault {0} failed : {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-60003: Recovery attempt for fault {0} succeeded

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60004: Exception encountered during recovery attempt: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60005: The {0} service engine does not support automated fault recovery

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60006: The composite {0} is not in a state for which recovery can be performed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60007: Fault is unrecoverable

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60008: Incorrect job type: {0} ; Expected {1}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-60009: Scheduled asynchronous job: {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-60010: Updated status for asynchronous job {0} : {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-60011: Recorded results for asynchronous job {0}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-60012: The results for job {0} are not available because the processing has not yet completed.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60013: Processing asynchronous {0} job {1}

Cause:

Action:
Level: 1

Type: TRACE

Impact: Other

SOA-60014: The processing of asynchronous job {0} failed: {1} : {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

SOA-60015: {1} faults matched the filter criteria associated with the bulk fault recovery job {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

SOA-60016: The composite {0} could not be found

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-60017: The Fabric mesh could not be accessed: {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-60018: Fault state unknown for faultId {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-60019: operation to retrieve sca entity associated data failed {0}

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

SOA-65001: No global transaction is currently associated with the executing thread "{0}".

Cause: No global transaction is currently associated with the calling thread.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65002: Failure to unwrap the wrapped DMS ExecutionContext "{0}" and associate it with the thread "{1}".

Cause: An error occured while unwrapping a DMS ExecutionContext.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65003: An error occurred while executing SOA's Instance Tracking Audit interceptor. See nested exception for root cause.

Cause: An error occured while executing the SOA Instance Tracking Audit Interceptor.

Action: Correct issue associated with the error's route cause.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65004: No FlowId is associated with request.

Cause: A request was not associated with a FlowId

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65005: No Component Instance ID is associated with the Executing Thread's DMS Execution Context

Cause: The Component Instance ID was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65006: No Component Instance ID creation time is associated with the Executing Thread's DMS Execution Context

Cause: The Component Instance ID creation time was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65007: The CommonFault associated with FaultId "{0}" could not be retrieved from the database.

Cause: The CommonFault associated with a given FaultId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65008: The fault Id was not associated with the Executing Thread DMS Execution Context.

Cause: The fault Id was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65009: The fault context was not associated with the Executing Thread DMS Execution Context.

Cause: The fault context was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65010: The Composite Sca Entity ID was not associated with the Executing Thread DMS Execution Context.

Cause: The composite Sca Entity Id was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65011: No Object found with JNDI Name "{0}"

Cause: No Object found with this JNDI Name

Action: Check values provided
Level: 1

Type: ERROR

Impact: Configuration

SOA-65012: Cannot cast object with jndi name "{0}" to class "{1}"

Cause: Invalid Class assignment for object with this JNDI Name

Action: Contact oracle support
Level: 1

Type: ERROR

Impact: Configuration

SOA-65013: Invalid async component state process count with original value "{0}" to new value "{1}"

Cause: Invalid async parallel process count with conflict of original and new value

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65014: Invalid async parallel process call sequence, the setPartialExecutions should be executed first with flow id "{0}" to component instance id "{1}"

Cause: Invalid async parallel process call sequence, the setPartialExecutions should be executed first.

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65015: Invalid async component completed process count with new value "{0}" to available partial parallel process count value "{1}"

Cause: Invalid async completed process count with conflict of new value and available partial parallel process count value

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65016: The FlowId "{0}" is not a valid FlowId. Valid values are numeric values.

Cause: Invalid FlowId format

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65017: The original Flow Event associated with the business flow "{0}" is missing.

Cause: Flow Trace issue.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65018: Invalid SCAEntityId "{0}".

Cause: The SCAEntityId value is not valid.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65019: The CommonFault associated with the Component Fault Key "{0}" could not be retrieved from the database.

Cause: No Fault is associated with the provided component fault key

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65020: The Composite Sca Entity ID Entry Time was not associated with the Executing Thread DMS Execution Context for the following FlowId "{0}".

Cause: The composite Sca Entity Id Entry Time was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65021: An error occurred while collecting sensor data.

Cause: An error occured while collecting sensor data

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65022: An invalid Flow id value was provided "{0}".

Cause: An invalid FlowId value was provided.

Action: FlowId values must be positive numeric values.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65023: Composite instance associated with FlowId "{0}" and Composite Instance Id "{1}" could not be found.

Cause: Internal instance tracking properties are missing.

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65024: The JPA persistence layer is not in health state.

Cause: The JPA persistence layer is not in health state.

Action: Contact oracle support.
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65025: Unknown instance tracking policy name "{0}"

Cause: The supplied or configured instance tracking persistence policy name is unrecognized

Action: Configure the policy with a valid policy name choice
Level: 1

Type: WARNING

Impact: Configuration

SOA-65026: Setting instance tracking persistence policy to "{0}"

Cause: The instance tracking policy has been initialized on server start or reconfigured

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65027: Unknown audit store policy name "{0}"

Cause: The supplied or configured audit store policy name is unrecognized

Action: Configure the policy with a valid policy name choice
Level: 1

Type: WARNING

Impact: Configuration

SOA-65028: Setting audit store policy to "{0}"

Cause: The audit store policy has been initialized on first use after server start

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65029: Changing the audit store policy from "{1}" to "{0}"

Cause: The audit store policy has been reconfigured by the administrative user

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65030: ''undeploy'' event was received for composite "{0}" and ScaEntityId "{1}". Marking associated active composite instances as stale.

Cause: Marking composite instance as stale suring undeployment

Action:
Level: 1

Type: NOTIFICATION

Impact: Configuration

SOA-65031: The following error occurred while marking composite instances as stale during undeployment for composite "{0}" and ScaEntityId "{1}". {2}

Cause: An error occured while marking composite instances as stale during undeployment

Action:
Level: 1

Type: ERROR

Impact: Configuration

SOA-65032: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be retrieved.

Cause: Callback properties could not be retrieved. See error message and associated Exception for details.

Action:
Level: 1

Type: WARNING

Impact: Configuration

SOA-65033: Invalid component instance id "{0}" associated with Flow Entry for Flow Id "{1}" and component type "{2}".

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65034: Error while retrieving Composite Instance associated with Flow Id "{0}", Composite SCA Entity Id "{1}" and creation time "{2}".

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65035: Error while retrieving Flow events for correlated flow "{0}", from Flow "{1}".

Cause: Internal error.

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65036: The flow instance for Flow Id "{0}" could not be retrieved from the database

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65037: Error while retrieving Flow events for correlated flow "{0}" associated with Correlation Flow ID "{1}".

Cause: Internal error.

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65038: null

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65039: null

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65040: Error while retrieving Composite Instance associated Composite Id "{0}".

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65041: AuditService is not available

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65042: An error occurred while creating DAO "{0}".

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65043: The Composite Instance ID was not associated with the Executing Thread DMS Execution Context for the following FlowId "{0}".

Cause: The composite instance ID was not associated with the Executing Thread DMS Execution Context

Action: Contact oracle support
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65044: Error while retrieving Async Component State associated with Flow Id "{0}" and Component Instance Id "{1}".

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65045: The SCASensorValue associated with ComponentInstanceId "{0}" and SensorName "{1}" could not be retrieved from the database.

Cause: The SCASensorValue associated with the given ComponentInstanceId and SensorName could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65046: The SCAAsyncComponentState associated with FlowId "{0}" and ComponentInstanceId "{1}" could not be retrieved from the database.

Cause: The SCAAsyncComponentState associated with the given FlowId and ComponentInstanceId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65047: The FlowInstance associated with FlowId "{0}" could not be retrieved from the database.

Cause: The FlowInstance associated with the given FlowId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65048: The FlowInstance associated with CorrelationFlowId "{0}" could not be retrieved from the database.

Cause: The FlowInstance associated with the given CorrelationFlowId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65049: An error occurred while retrieving DAO "{0}".

Cause: Internal error.

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65050: The FlowAssociation associated with FlowId "{0}" and CorrelationFlowId "{1}" could not be retrieved from the database.

Cause: The FlowAssociation associated with the given FlowId and CorrelationFlowId could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65051: The SCAMetaData associated with FlowId "{0}", CIKey "{1}", InternalID "{2}" and MetaDataCategory "{3}" could not be retrieved from the database.

Cause: The SCAMetaData associated with the given FlowId, CIKey, InternalId and MetaDataCategory could not be retrieved

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65052: An error occurred while processing Flow Events associated with flow ID "{0}" in the context of migration.

Cause: Error while processing Flow Events associated with migration

Action: Contact oracle support.
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65053: Cannot create audit store policy of type "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65054: Cannot update null DAO.

Cause: The data access object was null

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65055: Failed to publish AuditEvent.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65056: Unknown audit store policy "{0}". Defaulting to policy "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65057: Failed to retrieve SOA configuration while retrieving audit store policy. Defaulting to policy "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65058: Policy "{0}" does not implement instance access policy.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65059: Failed to publish AuditDetails.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65060: Cannot flush buffered instances because there is no MGIContext currently set.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65061: Cannot participate in global transaction when MGIContext is using a local transaction.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65062: Cannot call onCommit before preCommit.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65063: Error performing operation "{0}".

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65064: Unsupported DAO type "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65065: Failed to look up Spring bean "{0}"

Cause:

Action:
Level: 1

Type: ERROR

Impact: Programmatic

SOA-65066: The callback properties associated with Flow Id "{0}", Component Instance Id "{1}" and Internal Id "{2}" could not be persisted.

Cause: Callback properties could not be persisted. See error message and associated Exception for details.

Action:
Level: 1

Type: WARNING

Impact: Configuration

SOA-65067: MGIContext is not set on current thread

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65068: Current thread is already associated with an MGIContext belonging to another FlowId. Existing MGIContext FlowId = {0}. Current FlowId = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65069: Exception while persisting Instance Tracking data as part of transaction rollback. Pending operations: "{0}". Transaction status: "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

SOA-65070: Exception while executing transaction synchronizer afterCompletion on TransactionSynchronizer "{0}"

Cause:

Action:
Level: 1

Type: WARNING

Impact: Programmatic

45 SDP-25001 to SDP-26457

SDP-25001: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25002: Unable to create JNDI Context.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25003: Unable to create an instance of Driver Locator.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25004: Message could not be delivered to client due to rollback at the client application. Message ID {0}.

Cause: The client did rollback on the transaction, hence the message could not be re-delivered to the client.

Action: Check why the client did rollback
Level: 1

Type: WARNING

Impact: Process

SDP-25005: Failed to create Sending Core instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25006: Failed to remove an EJB instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25007: An error occurred while processing an outbound message.

Cause: The outbound JMS message does not contain a valid message or request information.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25008: An error occurred while processing an outbound message.

Cause: An exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25009: An error occurred while storing a message.

Cause: An exception has occurred while processing the message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25010: An error occurred while sending an outbound message.

Cause: An exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25011: An error occurred while transforming an outbound message.

Cause: An exception has occurred while processing the outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25012: An error occurred while processing error statuses.

Cause: An exception has occurred while processing error statuses.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25013: An error occurred while resending an outbound message.

Cause: An exception has occurred while processing the resent outbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25014: A JMS exception occurred, trying to recover

Cause: A JMS exception occurred

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.

Cause: An error has occurred while transforming an outbound message.

Action: Use the messageId to trace the message handling.
Level: 1

Type: WARNING

Impact: Process

SDP-25016: Could not get TimerService or Timers.

Cause: Could not get TimerService or Timers.

Action: Check application server status.
Level: 1

Type: ERROR

Impact: Process

SDP-25017: Could not cancel timer.

Cause: Could not cancel timer

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25020: Unable to schedule a timed failover event.

Cause: An exception has occurred while scheduling a timed failover event.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25021: An error occurred while processing a timed failover event.

Cause: An exception has occurred while processing a timed failover event.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25022: Unable to schedule a timed resend event.

Cause: An exception has occurred while scheduling a timed resend event.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.

Cause: An exception has occurred while scheduling a timer to refresh the driver cache.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25032: An error occurred while registering driver information {0}.

Cause: An exception has occurred while registering the driver information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25033: An error occurred while unregistering driver information {0}.

Cause: An exception has occurred while unregistering the driver information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}.

Cause: A Messaging Driver registered with the Messaging Server

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25035: Messaging store not found.

Cause: An exception has occurred while attempting to find the messaging store.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25036: An error occurred while registering driver information at User preference subsystem {0}.

Cause: An exception has occurred while registering the driver information at User preference subsystem.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25037: An error occurred while unregistering driver information at User preference subsystem {0}.

Cause: An exception has occurred while unregistering the driver information at User preference subsystem.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25040: Unable to create an instance of CommandReceiverBean.

Cause: An exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25042: An error occurred while processing a command message.

Cause: An exception has occurred while attempting to process a command.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25043: An unknown command message was received, ignoring: {0}.

Cause: The engine received an unknown command message and was unable to process the command.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25055: Failed to create Receiving Core instance.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25057: An error occurred while processing an inbound JMS message.

Cause: The inbound JMS message does not contain a valid message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25058: An error occurred while processing an inbound message.

Cause: An exception has occurred while processing the inbound message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25059: An unknown JMS message is received, ignoring: {0}.

Cause: The engine received an unknown JMS message and was unable to process it.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25060: There is no application that has registered this address as an access point. The message will be delivered when the access point is registered. Address={0}

Cause: There is no application that has registered this recipient address as an access point.

Action: Register the access point. The message is kept in a pending queue until an application registers a corresponding access point.
Level: 1

Type: WARNING

Impact: Process

SDP-25061: An error occurred while processing inbound message statuses.

Cause: An exception has occurred while attempting to process inbound message statuses.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25062: Cannot correlate status with any message; storing for possible later processing.

Cause: An inbound status arrived in an unexpected order.

Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25063: Status not delivered to client since no client information found for application {0}.

Cause: There is no application client information stored.

Action: Check the log file for additional information.
Level: 1

Type: WARNING

Impact: Process

SDP-25064: An error occurred while recording a status processing update.

Cause: An exception has occurred while attempting to record a status processing update.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25065: An error occurred while sending a message to failover address {0}.

Cause: An exception has occurred while sending out a failover message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25066: An error occurred while processing an outbound message status.

Cause: An exception has occurred while attempting to process an outbound message status.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.

Cause: A severe configuration error has occurred and the system is not functional.

Action: Check the messaging engine configuration and the stack trace, if available, for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25081: An error occurred while adding a message converter rule: {0}.

Cause: An invalid message converter rule was provided.

Action: Check the log file for additional details.
Level: 1

Type: WARNING

Impact: Process

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).

Cause: An invalid message converter rule was provided.

Action: Check the log file for additional details.
Level: 1

Type: WARNING

Impact: Process

SDP-25083: Message content is not an instance of MimeMultipart.

Cause: An invalid message content was provided to this converter.

Action: Check the current log file for additional details. Check User Messaging Service Javadoc on OTN for more information on sending MimeMultipart messages.
Level: 1

Type: WARNING

Impact: Process

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.

Cause: A message was sent or received that appears to be a duplicate of an already processed message; re-enqueuing message with delay specified.

Action: Ensure that messages are assigned unique Message IDs.
Level: 1

Type: WARNING

Impact: Process

SDP-25087: No matching driver found for {0} = {1}.

Cause: No matching driver found for the given property.

Action: Check that there is a correctly deployed and configured driver matching the given property.
Level: 1

Type: WARNING

Impact: Process

SDP-25088: Unable to refresh the driver locator cache, due to exception.

Cause: An error has occurred while refreshing the driver locator cache.

Action: Check the reported error message and correct any configuration problems.
Level: 1

Type: ERROR

Impact: Process

SDP-25101: Caught a database exception.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25106: Conflicting recipient IDs for Message {0}.

Cause: A conflict between recipient identifiers has been detected.

Action: Ensure that applications are using unique Message IDs.
Level: 1

Type: WARNING

Impact: Process

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.

Cause: A status object returned from a driver contained a different Message ID than expected.

Action: Ensure that drivers are mapping Gateway IDs to Message IDs correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-25109: Could not initialize persistence context.

Cause: An exception has occurred while initializing the persistence context.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25202: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.

Cause: The client application sent a message without required attribute.

Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.
Level: 1

Type: WARNING

Impact: Process

SDP-25250: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25251: Messaging Exception while processing Parlay X request.

Cause: A Messaging Exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25252: Exception while initializing Parlay X Messaging servlet.

Cause: An exception occurred while initializing the Parlay X Messaging servlet.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25253: Exception while initializing Parlay X Messaging content servlet.

Cause: An exception occurred while initializing the Parlay X Messaging content servlet.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25254: Exception while processing SOAP attachment content.

Cause: An exception occurred while processing message content in a SOAP attachment.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.

Cause: The client application sent a message with multiple attachment parts.

Action: Client applications should send one attachment part per message. Complex content should be sent as a MIME Multipart object.
Level: 1

Type: WARNING

Impact: Process

SDP-25256: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.

Cause: The client application sent a message without required attribute.

Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.
Level: 1

Type: WARNING

Impact: Process

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.

Cause: Could not acquire instance of class javax.xml.datatype.DatatypeFactory. Marshalling/unmarshalling of some XML elements may not happen correctly.

Action: Ensure that the server's JAXP framework is configured correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-25300: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25301: JNDI context is null.

Cause: JNDI context was null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.
Level: 1

Type: ERROR

Impact: Process

SDP-25302: EJB home for UserPrefsService is null.

Cause: EJB home for UserPrefsService is null.

Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to specify an EJB home.
Level: 1

Type: ERROR

Impact: Process

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.

Cause: EJB Naming Exception was caught when creating a UserPrefsServices object.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25304: EJB Remote Exception was caught at server {0}.

Cause: EJB Remote Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25305: EJB Create Exception was caught at server {0}.

Cause: EJB Create Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25306: XML Document object is null.

Cause: XML Document object is null.

Action: Specify a valid XML document object.
Level: 1

Type: ERROR

Impact: Process

SDP-25307: No file to upload. File name is not set.

Cause: The file name to be uploaded was not set.

Action: Invoke setFileName() to set the file name.
Level: 1

Type: ERROR

Impact: Process

SDP-25308: The file, {0}, cannot be read.

Cause: The file cannot be read.

Action: Check the file.
Level: 1

Type: ERROR

Impact: Process

SDP-25309: File not found: {0}.

Cause: The file with the given file name does not exist.

Action: Check to see if the path and file name are correct. File name must be in /path/filename or file://path/filename format.
Level: 1

Type: ERROR

Impact: Process

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}.

Cause: The document cannot be uploaded because parser and stack were out of sync.

Action: Fix mismatched tags.
Level: 1

Type: ERROR

Impact: Process

SDP-25312: Provisioning Exception was caught.

Cause: Provisioning Exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25314: Rule {0} is already defined.

Cause: Rule with the same name was already defined.

Action: Choose a different rule name to avoid conflict.
Level: 1

Type: ERROR

Impact: Process

SDP-25316: Input parameter, UserPrefsServices, is null.

Cause: The UserPrefsServices object was null.

Action: Pass a valid UserPrefsServices object as a parameter. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25317: Required input parameter, UserID, is null.

Cause: Failed to invoke method, because required input parameter, UserID, is null.

Action: Pass a valid UserID. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25318: Invalid input parameter. DeviceAddress object is null.

Cause: Input parameter, DeviceAddress object, is null.

Action: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25319: UserRuleSet is not set. Call initProcessor() first.

Cause: UserRuleSet object is null.

Action: Call initProcessor() first to complete initialization.
Level: 1

Type: ERROR

Impact: Process

SDP-25320: Rule Set is null.

Cause: The Rule Set was not available or could not be created.

Action: Use a valid Rule Set.
Level: 1

Type: ERROR

Impact: Process

SDP-25321: XML String representing the Rule Set is null.

Cause: The XML document element representing the Rule Set was null or empty.

Action: Use a valid Rule Set XML element.
Level: 1

Type: ERROR

Impact: Process

SDP-25322: User Rule Set is null.

Cause: The User Rule Set was not available or could not be created.

Action: Use a valid User Rule Set object.
Level: 1

Type: ERROR

Impact: Process

SDP-25323: User Rule Set is inconsistent. See exception for more details.

Cause: User Rule Set is inconsistent.

Action: Check User Rule Set for consistency.
Level: 1

Type: ERROR

Impact: Process

SDP-25324: XML document is invalid. See exception for details.

Cause: XML document is invalid. See stacktrace for more details.

Action: Validate the XML document.
Level: 1

Type: ERROR

Impact: Process

SDP-25325: Cannot serialize Rule Session.

Cause: Cannot serialize Rule Session, which is not critical.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Process

SDP-25326: Filter XML is null.

Cause: The Preference Rules were missing or inconsistent.

Action: Use a well-formed User Preference XML document.
Level: 1

Type: ERROR

Impact: Process

SDP-25327: Cannot create Rule Session.

Cause: Cannot create Rule Session.

Action: No action needed.
Level: 1

Type: WARNING

Impact: Process

SDP-25328: UserPrefsException was caught.

Cause: UserPrefsException was caught.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25329: Rule {0} does not exist.

Cause: The expected rule was not found.

Action: Check the rule by name on the User Preference page.
Level: 1

Type: ERROR

Impact: Process

SDP-25330: Business Term Type has changed. Term = {0}.

Cause: Business Term Type has changed.

Action: Recheck the Preference Rules.
Level: 1

Type: WARNING

Impact: Process

SDP-25331: Cannot instantiate User Preferences Services.

Cause: Cannot instantiate User Preferences Services due to an initialization error.

Action: Check User Prefs Services configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-25334: Device name is null.

Cause: Device name is null.

Action: Provide a valid Device name.
Level: 1

Type: ERROR

Impact: Process

SDP-25336: Input parameter, UserPrefsObject, is null.

Cause: Required parameter, UserPrefsObject, is null.

Action: Provide a valid UserPrefsObject.
Level: 1

Type: ERROR

Impact: Process

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.

Cause: Origin rule number is not valid.

Action: Specify a valid rule number.
Level: 1

Type: ERROR

Impact: Process

SDP-25341: The order of calling methods is wrong.

Cause: The order of calling methods is wrong.

Action: Check the order of the methods being called.
Level: 1

Type: ERROR

Impact: Process

SDP-25343: No devices are defined.

Cause: Tried to call delivery preferences without defining devices.

Action: Define devices for use with delivery preferences.
Level: 1

Type: ERROR

Impact: Process

SDP-25344: Invalid action {0} is found and ignored.

Cause: An invalid action was detected.

Action: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.
Level: 1

Type: WARNING

Impact: Process

SDP-25345: Runtime exception was caught.

Cause: Runtime exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25346: No configured Business Terms are available, only system terms will be used.

Cause: Business Term configuration could not be read.

Action: Ensure that business term configuration is correct
Level: 1

Type: WARNING

Impact: Process

SDP-25347: Device {0} cannot be added because it is present in the list.

Cause: A device was present in the list already.

Action: Ensure that the device to be added is not in the device list.
Level: 1

Type: WARNING

Impact: Process

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.

Cause: Device ID index number is not valid.

Action: Specify a valid device ID index number.
Level: 1

Type: ERROR

Impact: Process

SDP-25349: Name of rule is not set.

Cause: Rule name was not set.

Action: Set the name of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25350: FilterOperation of a rule is not set.

Cause: FilterOperation of a rule was not set.

Action: Set the FilterOperation of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25351: ActionOperation of a rule is not set.

Cause: ActionOperation of a rule was not set.

Action: Set the ActionOperation of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25352: Condition of a rule is not set.

Cause: Condition of a rule was not set.

Action: Set the condition of the rule.
Level: 1

Type: ERROR

Impact: Process

SDP-25353: unable to send a BROADCAST message because no address is set.

Cause: An address has not been set for the BROADCAST action.

Action: Set at least one address for the BROADCAST action.
Level: 1

Type: ERROR

Impact: Process

SDP-25354: A failover address is not set for the FAIL_OVER action.

Cause: An address has not been set for the FAIL_OVER action.

Action: Set at least one address for the FAIL_OVER action.
Level: 1

Type: ERROR

Impact: Process

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.

Cause: An identical device address already exists.

Action: Remove the conflicting device address, overwrite it, or specify a different address.
Level: 1

Type: WARNING

Impact: Process

SDP-25361: The Java VM does not support the encoding {0}.

Cause: The Java VM does not support the encoding used for XML string representing the RuleSet.

Action: Check your server Java VM and make sure it supports the encoding.
Level: 1

Type: ERROR

Impact: Process

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.

Cause: The fact from user or application had an incorrect data type.

Action: Provide the fact with the correct data type as indicated.
Level: 1

Type: WARNING

Impact: Process

SDP-25388: Device named {0} of user {1} not found.

Cause: The user does not have a device with that name.

Action: Check username and device name.
Level: 1

Type: WARNING

Impact: Process

SDP-25390: Failed to set default address of MESSAGING of user {0}.

Cause: Failed to set default address

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25400: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25403: Error in registering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-25404: Error in unregistering messaging Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans.

Cause: Naming exception thrown while looking up the Management Store EJB.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.

Cause: Create exception thrown while creating Management Store EJB.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25407: Exception initializing Runtime MBean.

Cause: An exception was thrown during runtime MBean initialization.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}.

Cause: Invalid combination of query parameters or invalid query value.

Action: Check stack trace.
Level: 1

Type: WARNING

Impact: Process

SDP-25409: Unable to initialize the composite type for the MBean.

Cause: OpenDataException was caught.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}.

Cause: OpenDataException was caught.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}.

Cause: An exception was thrown while attempting to get the parent server MBean.

Action: Check stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-25500: Failed to schedule Work.

Cause: Work could not be scheduled in the WorkManager

Action: Check stacktrace and WorkManager configuration
Level: 1

Type: ERROR

Impact: Process

SDP-25501: Exception when delivering pending messages.

Cause: Exception when delivering pending messages

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25502: Unable to create JNDI Context.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25503: Unable to connect to the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25504: Unable to register application information with the messaging server.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-25505: Unable to enqueue outbound message.

Cause: Engine Sending Queue may not be available.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25506: Unable to get receiving queues from application information.

Cause: An exception has occurred.

Action: Check the stack trace for more details. Check the Application information properties.
Level: 1

Type: ERROR

Impact: Process

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.

Cause: The client is not aware of any engine queues to enqueue the status.

Action: Check that the application is registered successfully with the messaging server.
Level: 1

Type: ERROR

Impact: Process

SDP-25508: Unable to enqueue inbound message status.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25509: An error occurred while notifying the MessageDispatcherBean about engine queues.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}.

Cause: An invalid JMS message was dequeued by the Dispatcher MDB.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25513: JNDI lookup of application callback listener failed.

Cause: An invalid callback listener was previously registered and could not be invoked.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25514: An error occurred while dispatching an inbound message to the application {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25515: An error occurred while dispatching an inbound status to the application {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.

Cause: Message/Status listener was not configured by the application.

Action: If the application requires asynchronous message/status callbacks, configure the listener information. Otherwise, ignore this warning.
Level: 1

Type: WARNING

Impact: Process

SDP-25517: Messaging client MDB suspend failed: {0}.

Cause: 1) The Messaging client was unable to access the MDB MBean because the container may not be in RUNNING state. 2) The server administrator username 'weblogic' does not exist.

Action: 1) Check the state of the container. Check the stack trace for more details. 2) Specify a valid server administrator username using the system property -Doracle.ums.admin.user and restart the server.
Level: 1

Type: WARNING

Impact: Process

SDP-25519: QueueWorker rejected.

Cause: QueueWorker rejected

Action: Check WorkManager configuration.
Level: 1

Type: ERROR

Impact: Process

SDP-25524: Client called the deprecated method acknowledge().

Cause: The method acknowledge is deprecated.

Action: Use global transactions instead to achieve reliable message reception.
Level: 1

Type: WARNING

Impact: Process

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25541: An error occurred while generating received message statuses.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25542: Security principal in client EJB Context "{0}" does not match security principal in ApplicationInfo "{1}". This may cause permission errors during future Messaging Client operations.

Cause: The security principal in the current EJBContext is different from the ApplicationInfo security principal field specified when creating the Messaging Client instance (or the default value, if no principal was provided).

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another.
Level: 1

Type: WARNING

Impact: Process

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".

Cause: The security principal in effect for the current thread is different from the security principal field specified when creating the Messaging Client instance.

Action: Ensure that the security principals used by this application for all Messaging Client operations match one another, or avoid configuring a specific security principal.
Level: 1

Type: WARNING

Impact: Process

SDP-25700: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25701: Unable to instantiate class {0}.

Cause: Unable to instantiate a class.

Action: Check to see if that class is in classpath or not.
Level: 1

Type: ERROR

Impact: Process

SDP-25702: Unable to set content of Message object.

Cause: Unable to set content of a message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25703: Exception when getting cluster name for server {0}.

Cause: Could not get cluster name from RuntimeServiceMBean

Action: Check the stack trace for more details
Level: 1

Type: ERROR

Impact: Process

SDP-25704: Error in setMultiplePayload.

Cause: An error occurred in setMultiplePayLoad().

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25705: Exception printing message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25706: Failed to clone message content.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25707: Failed to clone headers. Message = {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25709: Unable to perform JNDI lookup.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25710: Exception caught when calling onMessage(), will rollback transaction.

Cause: Exception caught when calling onMessage(), will rollback transaction.

Action: Check log to get more information.
Level: 1

Type: WARNING

Impact: Process

SDP-25711: Received unknown object: {0} on queue {1}.

Cause: Received unknown object in JMS queue

Action: Check log to get more information.
Level: 1

Type: WARNING

Impact: Process

SDP-25712: Message received with invalid format: {0} on queue {1}.

Cause: Invalid message received on JMS queue

Action: Check log to get more information.
Level: 1

Type: ERROR

Impact: Process

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25715: Invalid format, skipping: {0}.

Cause: Invalid queue information.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}

Cause: Error occurred in looking up QueueConnectionFactory in JNDI.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.

Cause: Error occurred in looking up queue in JNDI.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25718: Error occurred in getQueueInfoList.

Cause: Error occurred in getQueueInfoList().

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-25725: Message serialization failed.

Cause: Failed to serialize message due to I/O Error.

Action: Ensure that content is being created according to recommendations for Message class.
Level: 1

Type: ERROR

Impact: Process

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.

Cause: The Java EE server platform could not be determined. Either this application is executing in a Java SE environment, or the Java EE server is configured incorrectly.

Action: If executing in a Java SE environment, no action is necessary. Otherwise ensure that Java Required Files module is deployed to this environment.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}.

Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.

Action: Ensure that any WS-Security policies are specified in the correct format.
Level: 1

Type: WARNING

Impact: Process

SDP-25730: QueueWorker got exception.

Cause: QueueWorker got exception.

Action: Check the log for related information.
Level: 1

Type: WARNING

Impact: Process

SDP-25731: Failed to find database entry to update. Id: {0}

Cause: Failed to find database entry to update.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-25800: Oracle User Messaging Service configuration is successfully upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25801: Shall upgrade driver {0} using configuration file at {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25802: Driver {0} upgraded using {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25803: Driver {0} already upgraded. Ignoring configuration in {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25804: Shall upgrade server {0} using configuration file at {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25805: Server {0} upgraded using {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25806: Server {0} already upgraded. Ignoring configuration in {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25807: Shall upgrade user preference configuration for {0} using file at {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25808: User preference configuration for {0} upgraded using {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25809: Invalid managed server entered. Continue upgrade to see if we still can do a remote copy of the 11g configuration files.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25810: Custom deployed UMS application {0} will be deleted from the domain.

Cause: Custom deployed UMS applications are not supported any longer.

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25811: Failed to read configuration for driver {0}, {1}. Probably due to targeted driver without configuration.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25812: Ignoring configuration for application {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25820: Error in upgrading Oracle User Messaging Service configuration. Reason: {0}

Cause: An unexpected error occurred during Oracle User Messaging Service configuration upgrade.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25821: Failed to read the configuration file {0}.

Cause: The configuration file is missing or in wrong format.

Action: Check if the configuration file exists with correct format. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25822: Failed to save the configuration at {0}.

Cause: Error occured while saving the configuration to the configuration file.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25823: Failed to delete the old configuration file at {0}.

Cause: Error occurred while deleting the old configuration file.

Action: Check the file system. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25824: Failed to parse the configuration file at {0}.

Cause: Error occured while parsing the configuration file.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25825: Error during copy of configuration files from remote managed server {0}.

Cause: Old 11g configuration files where due to some problem not copied correct to the AdminServer. It could be that the plugin is missing information needed to connect to and copy the configuration from one of the managed servers. Or it could be that the sshd is not running on all the managed servers.

Action: Check the error messages in the log file to see what the problem is. Correct the problem before running the Upgrade Assistant again or perform a manual copy of the old configuration from the remote managed servers to the AdminServer.
Level: 1

Type: ERROR

Impact: Process

SDP-25826: Error connecting to remote managed server {0}.

Cause: It could be that the plugin is missing information needed to connect to one of the managed servers. Or it could be that the sshd is not running on all the managed servers.

Action: Check the error messages in the log file to see what the problem is. Correct the problem before running the Upgrade Assistant again or perform a manual copy of the old configuration from the remote managed servers to the AdminServer.
Level: 1

Type: ERROR

Impact: Process

SDP-25827: Neither the configuration nor the data entered by the user provides all information needed to copy the UMS 11g configuration files.

Cause: Upgrade Assistant does not have all information about the remote managed servers to be able to connect and copy the UMS 11g configuration files.

Action: Make sure to fill in name and address for all remote managed Servers that does not have this information configured.
Level: 1

Type: ERROR

Impact: Process

SDP-25850: Oracle User Messaging Service schema upgraded.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25851: Oracle User Messaging Service schema upgrade is valid.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25852: Oracle User Messaging Service schema version {0} is the latest one. Upgrade is not required.

Cause: Specified Oracle User Messaging Service database schema version is the latest one. Upgrade is not required.

Action: No user action is required.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25853: Oracle User Messaging Service schema upgrade is invalid.

Cause: Specified User Messaging Service schema was updated but is invalid.

Action: Restore the User Messaging Service schema from a backup and retry. Check the error messages in Oracle User Messaging Service component log files. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Process

SDP-25854: The upgrade is not supported from Oracle User Messaging Service schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Oracle User Messaging Service Upgrade Guide for supported versions to upgrade.
Level: 1

Type: ERROR

Impact: Process

SDP-25855: Error in upgrading Oracle User Messaging Service schema. {0}

Cause: An unexpected error occurred during Oracle User Messaging Service schema upgrade.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25856: Oracle User Messaging Service schema status is invalid.

Cause: Specified Oracle User Messaging Service database schema was invalid.

Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-26000: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26001: Cannot create JNDI Context.

Cause: Cannot create JNDI Context.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26002: The driver {0} is operational

Cause: The driver is operational

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26003: Driver {0} is not configured with required properties. Driver disabled until configured.

Cause: Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26004: No Messaging Engine Queue information to enqueue status.

Cause: No Engine Queue information to enqueue status.

Action: Check that the Engine is deployed. Check Engine Queue information.
Level: 1

Type: ERROR

Impact: Process

SDP-26005: Dispatcher failed to find a driver.

Cause: Dispatcher failed to find a driver.

Action: Compare delivery type and content type between message and available drivers.
Level: 1

Type: WARNING

Impact: Process

SDP-26006: Exception while dispatching message to driver resource adapter.

Cause: Exception while dispatching message to driver resource adapter.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26007: No configuration was found for this Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Driver deployment.

Action: Create a configuration this SMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26008: Invalid configuration for driver {0}. Driver disabled until configured.

Cause: Invalid configuration for driver

Action: Correct the driver configuration.
Level: 1

Type: WARNING

Impact: Process

SDP-26009: Could not get JNDI InitialContext.

Cause: None

Action: None
Level: 1

Type: ERROR

Impact: Process

SDP-26010: Unable to start driver: {0}.

Cause: Unable to start driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26011: Failed to invoke registerDriverInfo() for driver: {0}

Cause: Exception thrown while invoking registerDriverInfo().

Action: Check stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26012: Unable to remove scheduled workers

Cause: An exception has occurred while removing a driver thread.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26013: Unable to stop driver: {0}.

Cause: Unable to stop driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26014: Unable to process inbound message/status.

Cause: Exception occurred while processing inbound message/status.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26015: Unable to process command message.

Cause: Exception occurred while processing command message.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26016: Error occurred while attempting to get the parent server MBean for {0}

Cause: Error occurred while attempting to get the parent server MBean

Action: Check stack trace for more details
Level: 1

Type: ERROR

Impact: Process

SDP-26017: Failed to invoke registerDriverInfo() for driver: {0}

Cause: Exception thrown while invoking registerDriverInfo().

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26018: Invalid {0} value: {1}

Cause: The driver has been configured with an invalid property value.

Action: Review the driver configuration and ensure that the property is valid.
Level: 1

Type: WARNING

Impact: Process

SDP-26019: Error occurred while registering driver {0}

Cause: Error occurred while registering driver.

Action: Check stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26020: Registration of driver {0} succeeded.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26021: Timed out while waiting for reply from Messaging engine.

Cause: The registration command timed out in the JMS queue because the Messaging engine is down or the system is under heavy load.

Action: Check if the Messaging engine is up and ensure the system is not under extremely heavy load.
Level: 1

Type: WARNING

Impact: Process

SDP-26022: Illegal DeliveryType specified, ignoring type {0}.

Cause: Illegal DeliveryType specified.

Action: Check message delivery type.
Level: 1

Type: ERROR

Impact: Process

SDP-26023: Benchmark logging is enabled for all inbound messages, which may slow down system performance. To disable it, unset environment variable sdpm_inbound_benchmark_logging and restart.

Cause: Benchmark logging is enabled when environment variable sdpm_inbound_benchmark_logging=true.

Action: To disable benchmark logging, unset environment variable sdpm_inbound_benchmark_logging and restart.
Level: 1

Type: WARNING

Impact: Process

SDP-26024: Registration of driver {0} did not complete. Current state is {1}. Will retry periodically until messaging server responds.

Cause: None

Action: None
Level: 1

Type: WARNING

Impact: Process

SDP-26025: Error when registering messaging driver Runtime MBeans for {0}.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-26026: Error in unregistering messaging driver Runtime MBeans.

Cause: Exception was thrown.

Action: Check stack trace
Level: 1

Type: ERROR

Impact: Process

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.

Cause: A property with an unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character
Level: 1

Type: WARNING

Impact: Process

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.

Cause: A property with an invalid value and/or unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character
Level: 1

Type: WARNING

Impact: Process

SDP-26029: Exception occurred during driver configuration initialization for {0}.

Cause: An exception occurred during driver configuration initialization.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26030: Unable to schedule worker {0} for {1}.

Cause: An exception occurred while scheduling a worker.

Action: Check the stack trace.
Level: 1

Type: ERROR

Impact: Process

SDP-26031: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.

Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.
Level: 1

Type: WARNING

Impact: Process

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.

Cause: Driver connection factory could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the driver connection factory JNDI name is configured correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-26033: Started messaging driver: {0}

Cause: Driver was started.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26034: Stopped messaging driver: {0}

Cause: Driver was stopped.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26035: JNDI lookup of server command endpoint {0} failed. Will retry until successful.

Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.

Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.
Level: 1

Type: WARNING

Impact: Process

SDP-26036: Unable to perform JNDI lookup.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26037: Unable to create JMSMessageReceiver

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26039: Driver {0} does not have inbound configuration. No messages (including information about bounced emails) are received.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26040: Driver {0} does not have outbound configuration. Messages cannot be sent through this driver.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26041: An attempt to configure inbound for driver {0} was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Cause: An attempt to configure inbound for the driver was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Action: Remove inbound configuration or configure all required properties for this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26042: An attempt to configure outbound for driver {0} was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Cause: An attempt to configure outbound for the driver was detected. All required properties was not configured so the whole configuration (inbound and outbound) will be invalidated. Driver disabled until configured.

Action: Remove outbound configuration or configure all required properties for this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26100: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26101: Content type parsing error {0}.

Cause: Error occurred while trying to parse the content type.

Action: Check and see if the content type is specified correctly.
Level: 1

Type: WARNING

Impact: Process

SDP-26102: Error while writing e-mail message content.

Cause: An exception has occurred while writing e-mail content and headers to an e-mail message.

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26103: Error while writing e-mail subject.

Cause: Cannot write the subject.

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26104: Recipient address error.

Cause: Recipient e-mail address has an error.

Action: Check and see if the recipient e-mail address is correct.
Level: 1

Type: WARNING

Impact: Process

SDP-26105: Unable to deliver to following address(es): {0} Reason: {1}

Cause: One or more recipient e-mail addresses had an error.

Action: Ensure that the e-mail address is correct.
Level: 1

Type: WARNING

Impact: Process

SDP-26106: Failed to send the e-mail message

Cause: Unable to login to SMTP server.

Action: Check SMTP server host name, port, user name, and password.
Level: 1

Type: WARNING

Impact: Process

SDP-26107: Failed to add header - name: {0} value: {1}

Cause: Unable to add an e-mail header to a multipart message

Action: Check the stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26109: Caught exception while closing connection to e-mail server.

Cause: An exception was caught while closing connection.

Action: Check stack trace or error log.
Level: 1

Type: ERROR

Impact: Process

SDP-26110: Starting Email Driver failed.

Cause: Could not start Email Driver.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: ERROR

Impact: Process

SDP-26117: Connection information of the inbound e-mail server is missing. Check the server host name, user name, and password.

Cause: Connect information was missing or incomplete.

Action: Provide the required connection information.
Level: 1

Type: ERROR

Impact: Process

SDP-26118: Failed to open folder: {0}

Cause: Folder name is not correct or does not exist.

Action: Check folder name spelling.
Level: 1

Type: ERROR

Impact: Process

SDP-26119: Max retry limit reached for trying to connect to user {0}

Cause: Email driver has reached Max retry limit to connect to user.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: WARNING

Impact: Process

SDP-26120: IMAP server failed to expunge e-mail messages. mail box: {0}

Cause: An exception was caught when doing expunge.

Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: ERROR

Impact: Process

SDP-26121: Attempt to reconnect {0}. Error Count: {1} Retry Count: {2}.

Cause: Attempt to reconnect to the incoming e-mail server

Action: Check e-mail driver parameters and make sure all servers are up.
Level: 1

Type: WARNING

Impact: Process

SDP-26122: An exception has been thrown when connecting to user {0}

Cause: Email driver could not connect to user.

Action: Check username and password. Make sure the user exists and is accessible.
Level: 1

Type: ERROR

Impact: Process

SDP-26123: Could not initialize Email Store for: user {0}, server {1}, folder {2}, sslEnabled {3}

Cause: Could not initialize Email Store for the specified user, server, folder, and sslEnabled parameters.

Action: Check stack trace or error log. Check username, password, server, folder and sslEnabled parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26124: Invalid folder: {0}

Cause: An invalid folder name was specified.

Action: Check and see if the specified folder is valid and accessable.
Level: 1

Type: ERROR

Impact: Process

SDP-26126: Unrecoverable message - {0}

Cause: failed to recover an e-mail message

Action: Check stack trace or error log.
Level: 1

Type: WARNING

Impact: Process

SDP-26130: Ignoring property {0} with invalid value {1} during driver initialization.

Cause: A property with an invalid value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Ensure the value configured value is valid.
Level: 1

Type: WARNING

Impact: Process

SDP-26131: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization.

Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.
Level: 1

Type: WARNING

Impact: Process

SDP-26134: Email Driver {0} is not configured with incoming mail properties. No emails (including information about bounced emails) are received.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26135: Email Driver {0} is not configured with outgoing mail properties. Emails cannot be sent through this driver.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26136: Driver property OutgoingDefaultFromAddr is deprecated. Use DefaultSenderAddress instead.

Cause: Driver property OutgoingDefaultFromAddr in 'usermessagingconfig.xml' is deprecated.

Action: Use DefaultSenderAddress instead.
Level: 1

Type: WARNING

Impact: Process

SDP-26137: Both DefaultSenderAddress and the deprecated OutgoingDefaultFromAddr is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.

Cause: Both OutgoingDefaultFromAddr and DefaultSenderAddress is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.

Action: Remove configuration for OutgoingDefaultFromAddr.
Level: 1

Type: WARNING

Impact: Process

SDP-26138: Message was not delivered. No valid sender(From) address available.

Cause: No sender address set in message and DefaultSenderAddress is not configured in 'usermessagingconfig.xml'.

Action: Set sender(From) address in message or set DefaultSenderAddress in 'usermessagingconfig.xml'.
Level: 1

Type: WARNING

Impact: Process

SDP-26150: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null

Cause: Driver context is null

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26152: WorkManager object is null in SMPP driver.

Cause: The caller of setWorkManager() passed in a null WorkManager object as an argument

Action: Make sure WorkManager object is not null.
Level: 1

Type: ERROR

Impact: Process

SDP-26153: Failed to connect to server, host: {0}, port: {1} (local address: {2}, local port: {3})

Cause: Failed to connect to server with the specified parameters.

Action: Check the stack trace and the specified parameters. Ensure that the network is operational.
Level: 1

Type: ERROR

Impact: Process

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.

Cause: The account ID was not set.

Action: Set the correct account information.
Level: 1

Type: ERROR

Impact: Process

SDP-26156: Failed to initialize SMPP Driver because driver attributes sms.server.host, sms.server.transmitter.port or sms.server.receiver.port is not set.

Cause: SMSC server or account information is not correct or missing.

Action: Check those parameters.
Level: 1

Type: ERROR

Impact: Process

SDP-26158: Caught exception while closing connection

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26159: Illegal data length value from SMSC received and ignored: {0}

Cause: SMPP Driver has detected a corrupted data field from SMSC and it is trying to recover.

Action: This error suggests communication errors between SMPP driver and SMSC. Check to see if this driver supports that SMSC.
Level: 1

Type: WARNING

Impact: Process

SDP-26160: No configuration was found for this SMPP Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this SMPP Driver deployment.

Action: Create a configuration this SMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26161: Starting SMPP Driver: {0}

Cause: SMPP Driver resource adapter initialization.

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC

Cause: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.

Action: None.
Level: 1

Type: WARNING

Impact: Process

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.

Cause: Could not bind to the SMSC as a receiver. Bind operation will be retried periodically until it is successful.

Action: None required. Change value of configuration parameter "BindRetryDelay" to adjust retry interval.
Level: 1

Type: WARNING

Impact: Process

SDP-26165: Lookup of encoded credential value for account {0} in the credential failed during driver initialization.

Cause: Lookup of encoded credential value in the credential failed during driver initialization.

Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.
Level: 1

Type: WARNING

Impact: Process

SDP-26166: SMPP Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: SMPP Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26200: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26203: XMPP Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: XMPP Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26204: Error occurred while initializing XMPPDriver.

Cause: Error occurred while initializing driver instance.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26205: Exception while getting content from message with id={0}

Cause: Exception while getting content from message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26206: Lookup of encoded credential value for username {0} in the credential failed during driver initialization.

Cause: Lookup of encoded credential value in the credential failed during driver initialization.

Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.
Level: 1

Type: ERROR

Impact: Process

SDP-26209: Unable to initialize accounts

Cause: Unable to initialize accounts.

Action: Check username, password and IM server.
Level: 1

Type: ERROR

Impact: Process

SDP-26210: Unable to connect to XMPP server: {0}

Cause: Check the associated stack trace for the cause of the connection failure.

Action: Check the XMPP server hostname and port parameters and make sure the server is up.
Level: 1

Type: ERROR

Impact: Process

SDP-26213: Exception while sending message - from: {0} to: {1}.

Cause: Exception while sending message.

Action: Check stack trace and recipient address
Level: 1

Type: WARNING

Impact: Process

SDP-26214: Caught an exception in XMPP driver while sending out a message.

Cause: An exception was caught.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26216: No accounts defined in XMPP driver.

Cause: No XMPP accounts defined.

Action: Define a valid XMPP (IM) account.
Level: 1

Type: WARNING

Impact: Process

SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.

Cause: Could not locate an account to deliver this message.

Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26219: Server DNS problem with account: {0}

Cause: The hostname could not be resolved by DNS.

Action: Check the stack trace, account parameters, and DNS server.
Level: 1

Type: ERROR

Impact: Process

SDP-26220: Server I/O problem with account: {0}

Cause: The connection with the XMPP server was broken.

Action: Check the account parameters and the network connection.
Level: 1

Type: ERROR

Impact: Process

SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.

Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.

Action: None
Level: 1

Type: WARNING

Impact: Process

SDP-26223: Failed to set presence.

Cause: Failed to set presence.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26224: Exception occurred when processing incoming presence.

Cause: Exception occurred when processing incoming presence.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26225: Received Error Message. Code: {0} Text: {1}.

Cause: Received Error Message.

Action: Check error code and error message.
Level: 1

Type: WARNING

Impact: Process

SDP-26226: Unauthorized login to Jabber/XMPP server: {0}

Cause: Invalid username and/or password was supplied.

Action: Check username and password.
Level: 1

Type: WARNING

Impact: Process

SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}

Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.

Action: Contact the server administrator for a new account.
Level: 1

Type: WARNING

Impact: Process

SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}

Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.

Action: Check that the specified account does not exist. Check that your password is valid
Level: 1

Type: WARNING

Impact: Process

SDP-26230: Digest authentication failed. Attempting plain-text authentication: {0}

Cause: Digest authentication failed.

Action: Digest authentication failed. Check with the Jabber/XMPP server administrator.
Level: 1

Type: WARNING

Impact: Process

SDP-26234: Disconnecting from Jabber/XMPP server: {0}.

Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.

Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26235: Account disconnected: {0}.

Cause: The account was disconnected from the server either due to I/O or authentication error.

Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Level: 1

Type: ERROR

Impact: Process

SDP-26236: Got an exception when receiving a message.

Cause: Got an exception when receiving a message.

Action: Check to see if the message is well-formed.
Level: 1

Type: WARNING

Impact: Process

SDP-26237: The call for conversion does not supply account information. The first account is being used for conversion.

Cause: The call for conversion did not supply the necessary account information.

Action: Provide the correct account information.
Level: 1

Type: WARNING

Impact: Process

SDP-26238: Cannot deliver to this {0} user, because {1} transport is not enabled in the driver. Set the value for driver parameter: {2}.

Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.

Action: Enable the transport in the driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26239: Invalid network name in address: {0}

Cause: Invalid network name in address

Action: Specify a valid network name in address.
Level: 1

Type: WARNING

Impact: Process

SDP-26243: Config Parameters:XMPP Server : {0}XMPP Port : {1}XMPP Users : {2}SecurityMode : {3}SASLAuthentication : {4}

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26245: Could not initialize XMPPDriver.

Cause: XMPPDriver was misconfigured.

Action: Check driver parameters, account information and Jabber/XMPP server.
Level: 1

Type: ERROR

Impact: Process

SDP-26247: Failed to get roster from XMPP server

Cause: Failed to get roster from XMPP server

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Cause: The account was disconnected from the server due to an unknown error.

Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Level: 1

Type: WARNING

Impact: Process

SDP-26249: No configuration was found for this XMPP Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this XMPP Driver deployment.

Action: Create a configuration this XMPP Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26250: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26251: Could not initialize Proxy Driver

Cause: Could not initialize Proxy Driver.

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Process

SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.

Cause: DriverConnection returned by DriverConnectionFactory was null

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Process

SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.

Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.

Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.
Level: 1

Type: ERROR

Impact: Process

SDP-26255: Exception occurred while initializing Proxy Driver

Cause: Exception occurred while initializing Proxy Driver

Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.
Level: 1

Type: ERROR

Impact: Process

SDP-26256: Proxy Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: Proxy Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26257: Exception occurred while invoking Proxy Driver remote request

Cause: Exception occurred while invoking Proxy Driver remote request

Action: Check stack trace or error log. Check Proxy Driver configuration and remote gateway.
Level: 1

Type: ERROR

Impact: Process

SDP-26258: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.

Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.

Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.
Level: 1

Type: WARNING

Impact: Process

SDP-26259: No configuration was found for this Proxy Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Proxy Driver deployment.

Action: Create a configuration this Proxy Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26300: A Twitter exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26301: Got an exception when receiving tweets.

Cause: An exception has occurred when receiving tweets.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26302: Got an exception when receiving direct messages.

Cause: An exception has occurred when receiving direct message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26303: Exception caught during attributes transferring of an inbound direct message.

Cause: An exception has occurred when transferring attributes of a direct message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26304: Exception caught during attributes transferring of an inbound tweet.

Cause: An exception has occurred when transferring attributes of a tweet.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26305: Got an exception when building an inbound UMS message from a received tweet or direct message.

Cause: An exception has occurred when rebuilding an inbound UMS message.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26306: Required OAuth login information is missing or incomplete. Consumer key, consumer secret, access token, and/or access token secret is not set.

Cause: At least one of Twitter consumer key, consumer secret, access token, and access token secret is missing or not set.

Action: Check the log file for the missing field(s).
Level: 1

Type: ERROR

Impact: Process

SDP-26307: Required xAuth login information for user {0} is missing or incomplete. Both username and password are required.

Cause: Username or password is missing or not set.

Action: Check the log file for the missing field(s).
Level: 1

Type: ERROR

Impact: Process

SDP-26308: No configuration was found for this Twitter Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Twitter Driver deployment.

Action: Create a configuration this Twitter Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26309: Twitter Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: Twitter Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26310: Twitter Driver not properly configured. AuthenticationMode {0} is unknown and not supported.

Cause: Twitter Driver not properly configured. AuthenticationMode given is unknown and not supported.

Action: Configure and restart this driver.
Level: 1

Type: ERROR

Impact: Process

SDP-26311: Retweet id string {0} in meta data could not be converted to long. No tweet for messageId {1}

Cause: Retweet id string in meta data could not be converted to long.

Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26312: Ignoring reply id string {0} in meta data that could not be converted to long.

Cause: Ignoring reply id string in meta data that could not be converted to long.

Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26313: Ignoring geo location string ({0}) in meta data that could not be converted to (double,double).

Cause: Ignoring geo location string in meta data that could not be converted to (double,double).

Action: Check how the application generates the meta data.
Level: 1

Type: WARNING

Impact: Process

SDP-26350: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26351: Driver property VoiceXMLReceiveURL is empty.

Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.

Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.
Level: 1

Type: ERROR

Impact: Process

SDP-26352: VoiceXMLOutboundServletURI cannot be null

Cause: VoiceXMLOutboundServletURI is null

Action: Assign proper value for Outbound Servlet URL.
Level: 1

Type: ERROR

Impact: Process

SDP-26356: Socket error from VoiceXML Gateway.

Cause: Socket Error from the Gateway

Action: Check VoiceXML server URL and the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26357: VoiceXMLDriver could not initialize.

Cause: Initialization failed.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26358: VoiceXMLDriver: Exception while processing the HTTP request.

Cause: Exception while processing the HTTP request

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26359: VoiceXMLDriver: Caught exception while closing connection

Cause: Caught exception while closing connection

Action: Check the stack trace for more details.
Level: 1

Type: WARNING

Impact: Process

SDP-26360: VoiceXML Driver {0} is not configured with all required properties. Driver disabled until configured.

Cause: VoiceXML Driver was not configured with all required properties.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26361: Lookup of encoded credential value for username {0} in the credential failed during driver initialization.

Cause: Lookup of encoded credential value in the credential failed during driver initialization.

Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.
Level: 1

Type: ERROR

Impact: Process

SDP-26362: No configuration was found for this VoiceXML Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this VoiceXML Driver deployment.

Action: Create a configuration this VoiceXML Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26450: An exception was caught.

Cause: An exception has occurred.

Action: Check the stack trace for more details.
Level: 1

Type: ERROR

Impact: Process

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.

Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.

Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.
Level: 1

Type: WARNING

Impact: Process

SDP-26452: No extension endpoint could be found for the specified recipient address.

Cause: None of the configured extension endpoints matched the protocol and domain of the message recipient.

Action: Ensure that an endpoint is configured for the desired protocol and domain, or configure a default (empty) domain.
Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26453: No configuration was found for this Extension Driver deployment: {0}. Driver disabled until a configuration is created.

Cause: No configuration was found for this Email Driver deployment.

Action: Create a configuration this Email Driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26454: Extension Driver {0} is not configured with at least one extension point with a valid endpoint URL and protocol. Driver disabled until configured.

Cause: Extension Driver is not configured with at least one extension point with a valid endpoint URL and protocol.

Action: Configure this driver.
Level: 1

Type: WARNING

Impact: Process

SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.

Cause: An error occurred while processing the Extension Driver configuration.

Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
Level: 1

Type: ERROR

Impact: Process

SDP-26456: An exception occurred while enabling the WS-Security configuration: {0}

Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.

Action: Ensure that any WS-Security policies are specified in the correct format.
Level: 1

Type: ERROR

Impact: Process

SDP-26457: An exception occurred while constructing the SOAP message: {0}

Cause: An exception occurred while constructing the SOAP message

Action: Check the configuration of the server.
Level: 1

Type: ERROR

Impact: Process

46 TPC-00001 to TPC-60113

TPC-00001: The document root cannot be deleted.

Cause: The user tried to delete the document root.

Action: Do not try to delete the document root.
Level: 1

Type: ERROR

Impact: Logging

TPC-00002: Failed to create folder "{0}".

Cause: The user does not have permission to create a folder.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00003: Failed to create local directory "{0}".

Cause: The user does not have permission to create the local directory.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00004: Failed to create team document directory item.

Cause: The user does not have permission to create documents.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00005: Failed to delete team document.

Cause: The document has already been deleted or the user does not have permission.

Action: Verify document existence and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00006: Failed to download document "{0}".

Cause: The download failed because of connection failures or the user does not have permission.

Action: Verify connectivity and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00007: Failed to get document connector.

Cause: Failed to get an instance of the document connector.

Action: Verify connector installation and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00008: Failed to rename document item to "{0}".

Cause: The user does not have permission to rename documents.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00009: Failed to show team document content.

Cause: The user does not have permissions to view the document.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00010: Failed to upload team document.

Cause: The user does not have permissions to upload team documents.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00011: Connector for "{0}" might not be properly installed. Use Help->Check for Updates... to fix the problem.

Cause: The connector is not properly installed or the user does not have permission.

Action: Verify the connector installation and the user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00012: Work Item Connector Login Error.

Cause: The user could not log in to the connector.

Action: Ensure the user credentials are correct.
Level: 1

Type: ERROR

Impact: Logging

TPC-00013: Creating User Repository Error.

Cause: The user does not have permission to create a repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00014: Failed to construct the connector.

Cause: The connector parameters are incorrect.

Action: Verify the connector parameters in the administration screen.
Level: 1

Type: ERROR

Impact: Logging

TPC-00015: Failed to log in to "{0}" repository.

Cause: Failed to access repository.

Action: Check connection and access permission.
Level: 1

Type: ERROR

Impact: Logging

TPC-00016: Missing the required user repository.

Cause: Miss the required user repository.

Action: Add needed user repository.
Level: 1

Type: ERROR

Impact: Logging

TPC-00017: No item has been found with the specified ID or you do not have access to it.

Cause: No item with the specified ID exists or user does not have access to view it.

Action: Enter another valid ID value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00018: Specify your login.

Cause: The login cannot be empty.

Action: Provide data for the login.
Level: 1

Type: ERROR

Impact: Logging

TPC-00019: Specify your password.

Cause: The password cannot be empty.

Action: Provide data for the password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00020: Cannot save your account information to server. Contact your administrator.

Cause: There is an issue with server connectivity or user credentials.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00021: Update failed. Check field values and try again.

Cause: Invalid values for some fields.

Action: Verify field values and try again.
Level: 1

Type: ERROR

Impact: Logging

TPC-00022: Cannot delete repository "{0}". Make sure that no team is using the repository.

Cause: The repository is being used by one or more teams.

Action: Remove the repository from all teams.
Level: 1

Type: ERROR

Impact: Logging

TPC-00023: Cannot save the new repository "{0}". Make sure its name is unique.

Cause: The repository name is not unique.

Action: Specify a unique repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00024: Cannot update repository "{0}". Check your log file for details.

Cause: TPC server has encountered problem during updating the repository. Check the server's log to find out what has caused the problem.

Action: Check your log file for details.
Level: 1

Type: ERROR

Impact: Logging

TPC-00025: Create new repository error.

Cause: The repository parameters are incorrect.

Action: Verify the repository parameters.
Level: 1

Type: ERROR

Impact: Logging

TPC-00026: Delete repository error.

Cause: The user does not have permission to delete the repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00027: Repository Access Error.

Cause: The user credentials may not be correct or there may be connectivity issues.

Action: Verify the user credentials and the connectivity of the repository.
Level: 1

Type: ERROR

Impact: Logging

TPC-00028: Repository field cannot be empty.

Cause: The repository name cannot be empty.

Action: Provide a name for the repository.
Level: 1

Type: ERROR

Impact: Logging

TPC-00029: Test failed.

Cause: The username and password are not correct.

Action: Provide a valid username and password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00030: Update User Repository Account Failure.

Cause: Failed to update user repository account.

Action: Check account parameters.
Level: 1

Type: ERROR

Impact: Logging

TPC-00031: Repository field cannot be empty.

Cause: The repository field cannot be empty.

Action: Provide repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00032: Update repository error.

Cause: The repository data is invalid.

Action: Verify the repository data.
Level: 1

Type: ERROR

Impact: Logging

TPC-00033: Repository server name cannot be changed once it is committed.

Cause: The repository server name cannot be changed once it is created.

Action: Do not change repository server name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00034: Create repository server error.

Cause: The repository server parameter values are incorrect.

Action: Verify the parameter values.
Level: 1

Type: ERROR

Impact: Logging

TPC-00036: Repository server "{0}" is already used. Choose a different name.

Cause: The specified repository server name is already in use.

Action: Choose a different name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00037: Create new role error.

Cause: The role name is invalid.

Action: Verify that the name of the role is valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00038: Name field cannot be empty.

Cause: The name field cannot be empty.

Action: Enter data in name field.
Level: 1

Type: ERROR

Impact: Logging

TPC-00039: Failed to delete role.

Cause: The user does not have permission to delete the role.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00040: Failed to delete role "{0}". Make sure no team member uses this role.

Cause: The role is already associated to some users.

Action: Remove the role from all users.
Level: 1

Type: ERROR

Impact: Logging

TPC-00041: You can only delete a team that does not have any member. Make sure there is no user associated with this team.

Cause: The team has members associated with it.

Action: Remove all members from the team in order to delete it.
Level: 1

Type: ERROR

Impact: Logging

TPC-00042: You can only delete a team that does not have any subteam. Make sure there is no descendent team under this team.

Cause: The team has teams beneath it in the hierarchy.

Action: Remove all teams below the specified team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00043: Cannot save the new team "{0}". Make sure its name is unique.

Cause: The team name is not unique.

Action: Enter a unique name for the team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00044: Failed to Create Team.

Cause: Some data fields are invalid.

Action: Verify the team fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00045: Failed to Delete Team.

Cause: The user may not have permission to delete teams.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00046: Team name cannot be empty.

Cause: The team name is empty.

Action: Provide a value for the team name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00047: Create new team error.

Cause: Some data fields are invalid.

Action: Verify the team fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00048: Update team error.

Cause: Some data fields are invalid.

Action: Verify the team fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00049: Create new user error.

Cause: Some data fields are invalid.

Action: Verify the user fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00050: You can only delete a user that does not belong to any team. Make sure the current user is not associated with any team.

Cause: The specified user was associated with a team, so deletion was not allowed.

Action: Remove the user from all teams.
Level: 1

Type: ERROR

Impact: Logging

TPC-00051: Failed to Delete User.

Cause: The user did not have the permissions required to delete other users.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00052: Login, password, and email field cannot be empty.

Cause: Empty login, password or email field.

Action: Enter data for all fields.
Level: 1

Type: ERROR

Impact: Logging

TPC-00053: Login exists. Use different login.

Cause: The login ID already exists.

Action: Provide a unique login ID.
Level: 1

Type: ERROR

Impact: Logging

TPC-00054: Failed to open file "{0}".

Cause: The connection failed or the user does not have permission.

Action: Verify connectivity and check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00055: Failed to change Team Server password.

Cause: Server connectivity issue.

Action: Verify server connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00056: The new password does not match the retyped password.

Cause: The new password does not match the retyped password.

Action: Verify the passwords entered.
Level: 1

Type: ERROR

Impact: Logging

TPC-00057: The old password entered is incorrect.

Cause: The old password entered is incorrect.

Action: Provide the correct password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00058: Failed to create buddy "{0}".

Cause: Server connectivity issue.

Action: Verify server connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00059: Buddy "{0}" already exists.

Cause: The specified buddy already exists.

Action: Refresh your buddy list.
Level: 1

Type: ERROR

Impact: Logging

TPC-00060: Fail to create group "{0}" on the server.

Cause: Server connectivity issue or the group name is invalid.

Action: Verify server connectivity and verify that the group name is valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00061: Make sure you enter a valid account name before clicking the Add button.

Cause: The account name is invalid.

Action: Verify the account name which should be in email format, abc@xyz.net.
Level: 1

Type: ERROR

Impact: Logging

TPC-00062: Failed to connect to chat server "{0}".

Cause: The connection information is incorrect.

Action: Verify the connection information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00063: Failed to log in to chat server "{0}".

Cause: The login credentials are incorrect.

Action: Verify the login credentials and connection information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00064: Failed to save the work item.

Cause: Some of the workitem field values are invalid.

Action: Verify the input data.
Level: 1

Type: ERROR

Impact: Logging

TPC-00065: Failed to update password.

Cause: The password is invalid.

Action: Ensure the password is 12 characters or less.
Level: 1

Type: ERROR

Impact: Session

TPC-00066: Failed to log in to team server.

Cause: The login credentials are incorrect.

Action: Verify the login credentials.
Level: 1

Type: ERROR

Impact: Session

TPC-00067: Invalid username or password.

Cause: Invalid username or password.

Action: Verify the login name and password.
Level: 1

Type: ERROR

Impact: Session

TPC-00068: Invalid server name or port.

Cause: Invalid server name or port.

Action: Verify the server name or server port.
Level: 1

Type: ERROR

Impact: Logging

TPC-00069: Failed to update query "{0}".

Cause: The query specification is incorrect.

Action: Verify the query fields are valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00070: Failed to create new query "{0}".

Cause: The query specification is incorrect.

Action: Verify the query fields are valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00071: Cannot save the query. Make sure the query is valid.

Cause: The query specification is incorrect.

Action: Verify the query fields are valid.
Level: 1

Type: ERROR

Impact: Logging

TPC-00072: Query "{0}" already exists. Provide another name.

Cause: The specified query already exists.

Action: Provide a unique name for the query.
Level: 1

Type: ERROR

Impact: Logging

TPC-00073: Duplicate Tag Name Error.

Cause: The tag name already exists.

Action: Provide a unique name for the tag.
Level: 1

Type: ERROR

Impact: Logging

TPC-00074: Failed to add tag to the current work item.

Cause: Connectivity issue.

Action: Verify connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00075: Failed to create new tag.

Cause: The user does not have permission to create new tags.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00076: Missing Required Information.

Cause: Missing Required Information.

Action: Provide tag name and description.
Level: 1

Type: ERROR

Impact: Logging

TPC-00077: Tag "{0}" already exists.

Cause: The tag name already exists.

Action: Provide a unique tag name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00078: No result found. Either the tag used has been changed or there is no item associated with the tag. Close this window and try again.

Cause: The tag used has been changed or there is no item associated with the tag.

Action: Select a different tag.
Level: 1

Type: ERROR

Impact: Logging

TPC-00079: Failed to delete the context.

Cause: Connectivity issue.

Action: Verify server connectivity or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00080: There is no context being saved.

Cause: There are no open files to be saved to the context.

Action: Open files in the editor and then save the context.
Level: 1

Type: ERROR

Impact: Logging

TPC-00081: Failed to update the context.

Cause: The context files may not be present in the local file system.

Action: Restore the file system or delete the context.
Level: 1

Type: ERROR

Impact: Logging

TPC-00082: Restore context exception: "{0}".

Cause: An error was encountered during restoring the context. Detailed exception should have been provided in the message dialog.

Action: Check the log files.
Level: 1

Type: ERROR

Impact: Logging

TPC-00083: Cannot retrieve context.

Cause: The context was not properly stored.

Action: Delete the context and reopen the files manually.
Level: 1

Type: ERROR

Impact: Logging

TPC-00084: Cannot save context.

Cause: An error was encountered during saving the context. Detailed exception should have been provided in the message dialog.

Action: Check the log files.
Level: 1

Type: ERROR

Impact: Logging

TPC-00085: Cannot find document "{0}" to add.

Cause: The document may have been removed from the content store.

Action: Verify the document exists in the content store and contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00086: Failed to download attachment "{0}".

Cause: Connectivity issue.

Action: Verify the connectivity and retry or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00087: Failed to update attachment "{0}".

Cause: Connectivity issue.

Action: Verify the connectivity and retry or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00088: Failed to update attributes on attachment "{0}". Error: {1}.

Cause: Connectivity issue.

Action: Verify the connectivity and retry or contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00089: Failed to upload attachment "{0}". Error: {1}.

Cause: Connectivity issues or the upload directory is not properly set.

Action: Verify the connectivity and the upload directory.
Level: 1

Type: ERROR

Impact: Logging

TPC-00090: Cannot create the work item relationship.

Cause: Connectivity issues or the specified work item does not exist.

Action: Verify the connectivity and ensure the work item specified was not deleted.
Level: 1

Type: ERROR

Impact: Logging

TPC-00091: Connector "{0}" is installed but its version "{1}" is not supported. Supported version is "{2}" or lower. Contact your TPC Administrator to upgrade the connector on the server.

Cause: Connector versions mismatched.

Action: Use only supported version of the client connector.
Level: 1

Type: ERROR

Impact: Logging

TPC-00092: Cannot update team query "{0}".

Cause: User may not have permission to update team query.

Action: Check permission to update team query.
Level: 1

Type: ERROR

Impact: Logging

TPC-00093: You can only delete a team that does not have any repository. Make sure there is no repository associated with this team.

Cause: The team has repositories associated with it.

Action: Remove all repositories from the team in order to delete it.
Level: 1

Type: ERROR

Impact: Logging

TPC-00094: Failed to Update User.

Cause: The user does not have permissions to update this user.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00095: Failed to delete team member "{0}".

Cause: The team member may be in use.

Action: Remove all associations to the team member.
Level: 1

Type: ERROR

Impact: Logging

TPC-00096: Failed to delete team repository for team "{0}" using repository "{1}".

Cause: The user does not have permissions to update the team repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00097: Failed to create team repository for team "{0}" using repository "{1}".

Cause: The user does not have permissions to create the team repository.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00098: Failed to delete team parameter for team "{0}" using repository "{1}".

Cause: The user does not have permissions to delete the parameter.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00099: Failed to update team parameter for team "{0}" using repository "{1}".

Cause: The user does not have permissions to update the parameter.

Action: Check user permissions.
Level: 1

Type: ERROR

Impact: Logging

TPC-00100: Failed to create team member "{0}".

Cause: Some required property of the team member may be missing.

Action: Make sure the user associated with the team member is specified correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-00101: Cannot grant privilege "{0}" to role "{1}".

Cause: The privilege did not exist or the association was not unique.

Action: Specify an existing privilege or a unique association for the role.
Level: 1

Type: ERROR

Impact: Logging

TPC-00102: Cannot revoke privilege "{0}" from role "{1}".

Cause: The association did not exist.

Action: Specify correct association to delete. This may be an error in the application.
Level: 1

Type: ERROR

Impact: Logging

TPC-00103: Cannot update privilege "{0}" for role "{1}".

Cause: The association might not exist.

Action: Specify correct association to update. This may be an error in the application.
Level: 1

Type: ERROR

Impact: Logging

TPC-00104: Cannot create role "{0}".

Cause: The role may exist.

Action: Specify unique role to create.
Level: 1

Type: ERROR

Impact: Logging

TPC-00105: Cannot update role "{0}".

Cause: The role may not exist.

Action: Specify correct role to update. This may be an error in the application.
Level: 1

Type: ERROR

Impact: Logging

TPC-00106: Cannot grant privilege "{0}" for login "{1}".

Cause: The association is not unique.

Action: Specify a unique association for the login.
Level: 1

Type: ERROR

Impact: Logging

TPC-00107: Cannot revoke privilege "{0}" from login "{1}".

Cause: The association may not exist or the login may not exist.

Action: Specify correct login.
Level: 1

Type: ERROR

Impact: Logging

TPC-00108: Cannot update team "{0}".

Cause: The team information may not be specified properly.

Action: Specify correct team information.
Level: 1

Type: ERROR

Impact: Logging

TPC-00109: Cannot delete team "{0}".

Cause: The team may not exist.

Action: Specify correct team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00110: Invalid email address. Specify valid email address.

Cause: Email address specified is invalid.

Action: Specify valid email address in this format, abc@xyz.net.
Level: 1

Type: ERROR

Impact: Logging

TPC-00111: You have lost connection to TPC server. {0}

Cause: TPC server might be down or there is network connectivity issue.

Action: If the reason for the problem was provided, fix the problem then log-in to TPC again.
Level: 1

Type: ERROR

Impact: Network

TPC-00112: Server did not send a valid certificate.

Cause: Invalid certificate from server caused by the specified reason.

Action: Verify that you have specified correct server name and port.
Level: 1

Type: ERROR

Impact: Logging

TPC-00113: TPC server requires a certificate to connect, but you rejected it.

Cause: User rejected a certificate sent by TPC server. The certificate is needed in SSL connection mode.

Action: Verify and accept the certificate before you connect.
Level: 1

Type: ERROR

Impact: Logging

TPC-00114: Failed to accept the server certificate for an unknown problem. Try again.

Cause: The certificate is either empty or there was a problem in accepting the certificate.

Action: Verify and accept the certificate again.
Level: 1

Type: ERROR

Impact: Logging

TPC-00115: Failed to delete attachment "{0}". Error: {1}.

Cause: The specified attachment cannot be found in the content store.

Action: Verify the document exists in the content store and contact your administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-00116: Password cannot be reused.

Cause: The old password cannot be reused.

Action: Specify password different than the old one.
Level: 1

Type: ERROR

Impact: Logging

TPC-00117: Password cannot be empty.

Cause: The password is empty.

Action: Please specify a non blank password.
Level: 1

Type: ERROR

Impact: Logging

TPC-00118: User canceled.

Cause: User has canceled login.

Action: None.
Level: 1

Type: ERROR

Impact: Logging

TPC-00119: Unable to establish connection with server using this url: {0}.

Cause: Failed to log in to specified server URL.

Action: Specify correct server URL.
Level: 1

Type: ERROR

Impact: Session

TPC-00120: Value is required for "{0}".

Cause: Value for the specific input field is required but it has not been provided

Action: Specify value for the field
Level: 1

Type: ERROR

Impact: Logging

TPC-00121: Invalid value for "{0}". Value should be a type of "{1}".

Cause: An incorrect type of value was specified.

Action: Specify correct value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00122: Password for "{0}" is not valid after the login was renamed. Make sure you reset the password.

Cause: The user's login was renamed. Its password is no longer valid

Action: Reset the password for the login.
Level: 1

Type: WARNING

Impact: Logging

TPC-00123: Repository name cannot contain any of these characters: #/\?

Cause: The repository name contains invalid character(s)

Action: Provide valid repository name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00124: Please provide value for first name, last name, or email.

Cause: Value for first name,last name, or email is not specified.

Action: Provide valid value.
Level: 1

Type: ERROR

Impact: Logging

TPC-00125: Cannot save the user profile.

Cause: The user information specified cannot be saved.

Action: Provide valid user profile values and try it again.
Level: 1

Type: ERROR

Impact: Logging

TPC-00126: Query name cannot be empty. Please provide a valid name.

Cause: The query name is blank.

Action: Provide valid query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00127: The new query name cannot be the same as the original name.

Cause: The new query name is the same as the original name.

Action: Provide a new query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00128: The provided name cannot contain any of these characters: #/\? or all whitespaces

Cause: The query name contains invalid character(s)

Action: Provide valid query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00129: The specified query name already exists. Please provide a different name.

Cause: An existing query with the name specified already exists.

Action: Provide a different query name.
Level: 1

Type: ERROR

Impact: Logging

TPC-00130: This value will be used in a URL and cannot be empty or contain #, ?, / or \.

Cause: Input text is either empty or econtains invalid character like #, ?, /, or \.

Action: Remove #, ?, / or \.
Level: 1

Type: ERROR

Impact: Logging

TPC-00131: Cannot save to JDeveloper system.

Cause: TPC unabled to save to JDeveloper Preferences.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Logging

TPC-00132: Cannot activate a team whose parent team "{0}" is inactive. Activate the parent team then this team.

Cause: Activating a team whose parent is inactive is not allowed.

Action: Activate the parent team before activating the team.
Level: 1

Type: ERROR

Impact: Logging

TPC-00133: Default email client is not configured. Configure a default email client.

Cause: Default email client is not configured.

Action: Configure a default email client.
Level: 1

Type: ERROR

Impact: Logging

TPC-00134: Chat server does not support offline messages. Please try IM later or sending an Email.

Cause: Chat server does not support offline messages.

Action: Try IM later or sending an Email.
Level: 1

Type: ERROR

Impact: Logging

TPC-00135: Your client version "{0}" is currently not compatible with TPC server version "{1}". Download a patch to fix this problem.

Cause: You need to install a TPC patch to fix this issue.

Action: Contact Oracle Support if the patch is not available.
Level: 1

Type: ERROR

Impact: Logging

TPC-00136: Cannot process your request for build and test data. See accompanying message for the reason.

Cause: TPC server cannot process the request related to build and test information.

Action: Contact your Team Productivity Center administrator to get root of the problem resolved.
Level: 1

Type: ERROR

Impact: Requests/Responses

TPC-00137: Update for configuration change failed.

Cause: TPC server failed to update configuration changes for subscription and displaying branch.

Action: Check server log file for failure details.
Level: 1

Type: ERROR

Impact: Logging

TPC-00138: Cannot find an opened editor associated with your current workitem during procesing the relationship operation.

Cause: The editor for the workitem was not registered in JDeveloper as opened.

Action: Reopen the workitem editor
Level: 1

Type: ERROR

Impact: Logging

TPC-00139: Value for "{0}" is missing.

Cause: Value for the field was not specified

Action: Enter valid value for the field
Level: 1

Type: ERROR

Impact: Logging

TPC-00140: Cannot read CSV file "{0}".

Cause: The file was either not found or not readable

Action: Specify correct CSV file
Level: 1

Type: ERROR

Impact: Logging

TPC-00141: "{0}" from file "{1}" is not a valid CSV format.

Cause: The file was not using a valid CSV format

Action: Download and use the CSV template
Level: 1

Type: ERROR

Impact: Logging

TPC-00142: TPC has encountered an internal error: {0}

Cause: This is the generic internal error for TPC program exceptions. This indicated that a process encountered an exceptional condition

Action: If the reason for the problem was provided, report as a bug.
Level: 1

Type: ERROR

Impact: Other

TPC-00143: Can't find "{0}" in repository "{1}".

Cause: The item specified by the URL cannot be found the the targeted repository.

Action: Check with the repository admin to make sure item exists in the back end repository.
Level: 1

Type: ERROR

Impact: Other

TPC-00144: Can't find {0}.

Cause: The item specified by the URL cannot be found.

Action: Check and make sure the document exists in the back end.
Level: 1

Type: ERROR

Impact: Other

TPC-00145: You are neither the owner nor TPC administrator . You cannot delete this review.

Cause: Not the TPC admistrator or the owner to be permitted to do delete.

Action: Ask the owner or TPC administrator to delete the review.
Level: 1

Type: ERROR

Impact: Other

TPC-00146: Cannot process LDAP synchronization request.

Cause: LDAP synchronization process encountered the problem.

Action: Contact TPC Administrator to fix the problem.
Level: 1

Type: ERROR

Impact: Other

TPC-00147: Cannot find search filter "{0}" within the user search base "{1}".

Cause: Either the search filter was not valid, or the user search base was incorrect.

Action: Specify correct the search filter or the user seach base.
Level: 1

Type: ERROR

Impact: Other

TPC-00148: Cannot save the workitem due to missing value for required fields. Fix the problem and try again.

Cause: Required fields in the workitem were not specified.

Action: Specify all required field for the workitem.
Level: 1

Type: ERROR

Impact: Other

TPC-00149: The selected repository server cannot be deleted. It could be used by some team as its team repository. Please go to the team tab and then team repository tab to make sure no team uses it.

Cause: Delete operation will trigger database integrity violation.

Action: Do not perform delete operation.
Level: 1

Type: ERROR

Impact: Logging

TPC-00150: Cannot load Team Navigator

Cause: TPC has encountered unexpected error during loading the Team Navigator. Additional information should have been provided.

Action:
Level: 1

Type: ERROR

Impact: Logging

TPC-00151: Failed to decode url: {0}

Cause: Failed to decode url.

Action:
Level: 1

Type: ERROR

Impact: Logging

TPC-00152: Failed to encode url: {0}

Cause: Failed to decode url.

Action:
Level: 1

Type: ERROR

Impact: Logging

TPC-00153: Could not find Bug Reporter extension. Use Help->Check for Updates... to install Bug Reporter extension.

Cause: Could not find bugfiler.

Action: Check and install bugfiler extension.
Level: 1

Type: ERROR

Impact: Logging

TPC-60000: Team Productivity Center services initialized.

Cause: Service started normally.

Action: No action needed.
Level: 1

Type: NOTIFICATION

Impact: Threads

TPC-60001: Cannot insert record with blank Id.

Cause: The record has a blank Id.

Action: Enter a value for the Id.
Level: 1

Type: WARNING

Impact: Threads

TPC-60002: The record you want to update does not exist.

Cause: The record does not exist.

Action: Refresh your data.
Level: 1

Type: WARNING

Impact: Threads

TPC-60003: Cannot retrieve a record with a null Id.

Cause: The Id is null.

Action: Make sure the record has a valid Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60004: Cannot retrieve a record with a null name.

Cause: The item name is null.

Action: Make sure the record has a valid name.
Level: 1

Type: ERROR

Impact: Threads

TPC-60005: Cannot create a record with a null or empty password.

Cause: Password for this record is either null or empty.

Action: Make sure the record has a valid password.
Level: 1

Type: ERROR

Impact: Threads

TPC-60006: Username or password is invalid.

Cause: Invalid username and/or password.

Action: Verify the login name and password.
Level: 1

Type: ERROR

Impact: Threads

TPC-60007: Team Productivity Center services failed to start.

Cause: Cannot find required startup credentials.

Action: Verify the server was installed correctly.
Level: 1

Type: ERROR

Impact: Threads

TPC-60008: Cannot delete record

Cause: The server received an error during deletion of the record.

Action: Verify the record is not being used by others.
Level: 1

Type: ERROR

Impact: Threads

TPC-60009: Cannot connect to an inactive account.

Cause: You are trying to connect using account that has been deactivated.

Action: Contact TPC Administrator to activate it.
Level: 1

Type: ERROR

Impact: Data

TPC-60010: TPC Server requires authentication for this request. Authenticate with the server, or upgrade your client to fix the problem.

Cause: You either did not authenticate with the server, or your client version is no longer supported by the server.

Action: Authenticate with the server, or upgrade your client to correct the problem.
Level: 1

Type: ERROR

Impact: Threads

TPC-60011: Cannot initialize session in the webservice context.

Cause: Internal error on the server.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Threads

TPC-60012: This request is not supported by the server. Contact your TPC Administrator to upgrade the server.

Cause: You have requested a service that is not supported by the server.

Action: Contact TPC Administrator to upgrade the server.
Level: 1

Type: ERROR

Impact: Threads

TPC-60013: TPC client version "{0}" is not supported. Supported version is "{1}" or higher. Use Help > "Check for Updates..." to upgrade your client.

Cause: Client and Server versions mismatched.

Action: Use Help > "Check for Updates..." to upgrade the client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60014: This client is no longer supported. Use Help > "Check for Updates..." to install or upgrade TPC client to "{0}" or higher to fix the problem.

Cause: Your client is not recognized by the server either because it is invalid or no longer supported.

Action: Use Help > "Check for Updates..." to install or upgrade the TPC client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60015: Server version does not exist.

Cause: This is an internal error caused by missing a server version from the database.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-60016: Your session has either expired or terminated. Please reconnect and try again.

Cause: TPC server has terminated client session either unexpectedly or for scheduled maintenance.

Action: Relogin to the server once it becomes available again. Contact TPC Administrator for the availability of the server.
Level: 1

Type: ERROR

Impact: Threads

TPC-60017: Service is about to shut down...

Cause: One of the TPC service is about to shut down.

Action: Save all works and log off.
Level: 1

Type: ERROR

Impact: Threads

TPC-60018: Cannot create a null record.

Cause: You try to create a null record.

Action: Make sure the record has valid contents.
Level: 1

Type: ERROR

Impact: Threads

TPC-60019: The branch or label series "{0}" has already existed.

Cause: You try to create a branch or label series that has already existed.

Action: Check the name of your branch or label series. It must be unique per SCM connector.
Level: 1

Type: ERROR

Impact: Threads

TPC-60020: The branch "{0}" does not exist.

Cause: The branch you want to update does not exist.

Action: Specify a valid branch.
Level: 1

Type: ERROR

Impact: Threads

TPC-60021: The branch "{0}" you want to create or update is for a non-existing SCM connector "{1}".

Cause: The branch references the non-existing connector.

Action: Specify a valid SCM connector.
Level: 1

Type: ERROR

Impact: Threads

TPC-60022: The branch "{0}" you want to create or update is for a non-existing team "{1}".

Cause: The branch references the non-existing team.

Action: Specify a valid team.
Level: 1

Type: ERROR

Impact: Threads

TPC-60023: You must specify an SCM connector name for querying the branch "{0}".

Cause: The branch query requires an SCM connector name.

Action: Specify an SCM connector.
Level: 1

Type: ERROR

Impact: Threads

TPC-60024: You must specify a branch name for querying the build dashboard "{0}".

Cause: You did not specify a branch name used to query the specified build dashboard.

Action: Provide branch name.
Level: 1

Type: ERROR

Impact: Threads

TPC-60025: Build dashboard "{0}" for branch "{1}" does not exist.

Cause: There is no record for specified build and branch.

Action: Verify that you sepcified correct information.
Level: 1

Type: ERROR

Impact: Threads

TPC-60026: Dashboard for build "{0}" has already existed.

Cause: You try to create a build dashboard that has already existed.

Action: Check the name of your build.
Level: 1

Type: ERROR

Impact: Threads

TPC-60027: Missing branch or connector for creating the build dashboard "{0}".

Cause: You need to specify the branch and SCM connector when creating a build dashboard.

Action: Check the name of your build.
Level: 1

Type: ERROR

Impact: Threads

TPC-60028: The build dashboard "{0}" does not exist.

Cause: The build dashboard you want to update does not exist.

Action: Specify a valid build dashboard.
Level: 1

Type: ERROR

Impact: Threads

TPC-60029: This operation is not supported.

Cause: The requested operation is not supported.

Action: Try some other time.
Level: 1

Type: ERROR

Impact: Threads

TPC-60030: "{0}" with parent ID "{1}" will not be created as it is missing required Dashboard ID.

Cause: You need to specify the build dashboard id when creating a build summary for it.

Action: Specify the build id.
Level: 1

Type: WARNING

Impact: Threads

TPC-60031: {0} "{1}" for build "{2}" has already existed.

Cause: You try to create a build summary that has already existed.

Action: Check the name of the build summary.
Level: 1

Type: ERROR

Impact: Threads

TPC-60032: Changeset "{0}" for "{0}" has already existed.

Cause: You try to create a build changeset that has already existed.

Action: Check the name of the build changeset.
Level: 1

Type: ERROR

Impact: Threads

TPC-60033: You must specify an SCM connector name and a product/release name for this query.

Cause: This branch query requires both an SCM connector name and a product/release name.

Action: Specify both information
Level: 1

Type: ERROR

Impact: Threads

TPC-60034: Repository "{0}" has already existed.

Cause: You try to create a repository that has already existed.

Action: Check the name of your repository.
Level: 1

Type: ERROR

Impact: Threads

TPC-60035: The repository "{0}" does not exist.

Cause: The repository you want to update does not exist.

Action: Specify a valid repository.
Level: 1

Type: ERROR

Impact: Threads

TPC-60036: Missing test result Id for creating workitem "{0}" using repository "{0}".

Cause: You need to specify the test result Id when creating a workitem for it.

Action: Specify the test result Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60037: The workitem key and repository for test result Id "{0}" are missing.

Cause: You asked to create a workitem for a test result but you did not specify a key and repository for the workitem.

Action: Specify the key and repository.
Level: 1

Type: ERROR

Impact: Threads

TPC-60038: The test result "{0}" does not exist.

Cause: The test result you want to update does not exist.

Action: Specify a valid test result.
Level: 1

Type: ERROR

Impact: Threads

TPC-60039: Workitem "{0}" specified for test result Id "{0}" has already existed.

Cause: You try to create a workitem for a test result but the workitem has already existed.

Action: Specify a valid workitem.
Level: 1

Type: ERROR

Impact: Threads

TPC-60040: Workitem "{0}" has already existed in the repository "{0}".

Cause: You try to create a workitem that has already existed.

Action: Check the key and repository used for the workitem are correct.
Level: 1

Type: ERROR

Impact: Threads

TPC-60041: TPC server version "{0}" is not valid. Expected at least in this format: #.#.#.#

Cause: This is an internal error caused by invalid server version recorded on the database.

Action: Contact TPC Administrator.
Level: 1

Type: ERROR

Impact: Logging

TPC-60042: TPC client version "{0}" is not valid. Expected at least in this format: #.#.#.#

Cause: This is an internal error caused by invalid client version.

Action: Correct your TPC client installation. You can do this by removing the old one then reinstall, or install correct TPC client to another JDeveloper client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60043: Your client version "{0}" is newer than your TPC server version "{1}". This server supports clients beginning with version "{2}" or lower only. Use either a supported client or upgrade the server to fix the problem.

Cause: Your client has a newer version which is not supported by your server.

Action: Use either a supported client or upgrade the server to fix the problem.
Level: 1

Type: ERROR

Impact: Logging

TPC-60044: Your client version "{0}" is currently not compatible with your TPC server version "{1}". Download a patch to fix this problem.

Cause: You need to install a TPC patch to fix this issue.

Action: Contact Oracle Support if the patch is not available.
Level: 1

Type: ERROR

Impact: Logging

TPC-60045: Cannot find owner "{0}" to remove from build summary "{1}".

Cause: You ask to remove owner which does not exist for the specified build summary.

Action: Specify correct build summary.
Level: 1

Type: ERROR

Impact: Logging

TPC-60046: Cannot establish connection to TPC repositories.

Cause: TPC server cannot connect to the database.

Action: Check if you specified username and password to connect to the database correctly.
Level: 1

Type: ERROR

Impact: Logging

TPC-60047: Created By is required to create the task but is missing. It should be set to current logged-in user.

Cause: This is an internal error caused by missing Created By in the input specified by the caller.

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Logging

TPC-60048: The task "{0}" with Id "{1}" does not exist.

Cause: The task you want to update does not exist.

Action: Specify a valid task.
Level: 1

Type: ERROR

Impact: Threads

TPC-60049: The task "{0}" for team "{1}" does not exist.

Cause: The task you want to delete or retrieve does not exist.

Action: Specify a valid task.
Level: 1

Type: ERROR

Impact: Threads

TPC-60050: The task Id to retrieve, delete, or update is null.

Cause: Missing task Id.

Action: Specify a valid task Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60051: Team Id cannot be null.

Cause: Missing team Id.

Action: Specify a valid team Id for the task you want to retrieve.
Level: 1

Type: ERROR

Impact: Threads

TPC-60052: Task name you want to retrieve is null.

Cause: Missing task name.

Action: Specify a valid task name.
Level: 1

Type: ERROR

Impact: Threads

TPC-60053: Task you want to delete is missing from input.

Cause: Task to delete is missing from input.

Action: Specify a valid task.
Level: 1

Type: ERROR

Impact: Threads

TPC-60054: Multiple tasks were found with the name "{0}".

Cause: The API expects to return one task only but multiple tasks were found.

Action: Use other APIs.
Level: 1

Type: ERROR

Impact: Threads

TPC-60055: Assigned To Id "{0}" does not exist.

Cause: Assigned To Id cannot be found

Action: Specify correct Assigned To Id
Level: 1

Type: ERROR

Impact: Threads

TPC-60056: Cannot find user associated with login "{0}".

Cause: Cannot find user associated with the specified login

Action: Specify correct login
Level: 1

Type: ERROR

Impact: Threads

TPC-60057: Assigned To Id cannot be null.

Cause: Assigned To Id is null

Action: Specify correct Assigned To Id
Level: 1

Type: ERROR

Impact: Threads

TPC-60058: JPA Query string to execute is empty.

Cause: Internal error

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Threads

TPC-60059: Cannot retrieve values for null lookup type.

Cause: Internal error

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Threads

TPC-60060: Query name "{0}" already exists. Use another name.

Cause: Query name already exists

Action: Use another name
Level: 1

Type: ERROR

Impact: Threads

TPC-60061: Cannot find user credential to access TPC database.

Cause: User credential to connect to TPC database cannot be found.

Action: Reinstall TPC Server.
Level: 1

Type: ERROR

Impact: Process

TPC-60062: Cannot find persistence.xml.

Cause: Cannot find persistence.xml for acessing database.

Action: Reinstall TPC Server.
Level: 1

Type: ERROR

Impact: Process

TPC-60063: Cannot update user record for "{0}" without valid status id.

Cause: User to update did not valid status ID.

Action: Specify valid status ID.
Level: 1

Type: ERROR

Impact: Data

TPC-60064: Cannot find Lookup value(s) for type "{0}" and locale "{1}". Value for default locale is returned.

Cause: Lookup Value(s) for specified type and locale did not exist.

Action: None
Level: 1

Type: WARNING

Impact: Data

TPC-60065: Cannot find Lookup value(s) for type "{0}".

Cause: Lookup Value(s) for specified type did not exist.

Action: Check your TPC Installation log and see if these values have been inserted correctly.
Level: 1

Type: ERROR

Impact: Data

TPC-60066: Cannot find privilege assigned to user ID "{0}".

Cause: User did not have any privilege.

Action: Specify correct user ID
Level: 1

Type: ERROR

Impact: Data

TPC-60067: Invalid operator "{0}" used with "{1}".

Cause: Operator used in the specified field's criterion was not valid.

Action: Specify valid operator.
Level: 1

Type: ERROR

Impact: Data

TPC-60068: Cannot find translated strings associated with seeded data.

Cause: Translated strings associated with seeded constants were missing from backend table.

Action: Check your TPC Installation log and see if these values have been inserted correctly.
Level: 1

Type: ERROR

Impact: Data

TPC-60069: No parameter definition for connector "{0}" found.

Cause: Parameter definition for the connector was not found.

Action: Check your TPC Installation log and see if the parameter definition has been inserted correctly.
Level: 1

Type: ERROR

Impact: Data

TPC-60070: Connector "{0}" not found.

Cause: The specified connector was not found.

Action: Install the connector using OTPC Installer.
Level: 1

Type: ERROR

Impact: Data

TPC-60071: No connector found.

Cause: No connector was not found.

Action: Install connectors using OTPC Installer.
Level: 1

Type: ERROR

Impact: Data

TPC-60072: Existing accounts: "{0}".

Cause: The specified accounts had already been created.

Action: No action required
Level: 1

Type: NOTIFICATION

Impact: Logging

TPC-60073: Work Item Change Id is null.

Cause: Work Item change id was not found.

Action: Make sure the id for Work Item Change was specified as create review.
Level: 1

Type: ERROR

Impact: Data

TPC-60074: Work Item Change id "{0}" has been associated with other review.

Cause: Work Item change id has been associated with other review.

Action: Make sure this Work Item Change was not associate with other review.
Level: 1

Type: ERROR

Impact: Data

TPC-60075: User "{0}" does not have valid permissions for performing any operation associated with an LDAP server.

Cause: The LDAP-related operation was not submitted by a TPC administrator.

Action: Contact your TPC administrator to perform the operation for you.
Level: 1

Type: ERROR

Impact: Data

TPC-60076: The {0} "{1}" does not exist.

Cause: The record you want to update or delete does not exist.

Action: Specify a valid record.
Level: 1

Type: ERROR

Impact: Data

TPC-60077: The {0} "{1}" already exists.

Cause: The record you want to create already exists.

Action: Specify new record.
Level: 1

Type: ERROR

Impact: Data

TPC-60078: The record with {0} id "{1}" used to create review topic does not exist.

Cause: The record with id field, such as review/changeset/user id, specified does not exist as create review topic.

Action: Make sure associated records with review/changeset/user have been created before create review topic.
Level: 1

Type: ERROR

Impact: Data

TPC-60079: The topic name used to create review topic is invalid.

Cause: The topic name is not specified as create review topic.

Action: Make sure topic name is specified as create review topic.
Level: 1

Type: ERROR

Impact: Data

TPC-60080: Cannot find user ID required for performing the LDAP-related operation.

Cause: User ID was required to process LDAP-related operation but was not provided.

Action: Specify the user ID and try again.
Level: 1

Type: ERROR

Impact: Data

TPC-60081: "{0}" failed authentication using {1}.

Cause: LDAP authentication failed for the specified reason.

Action: Contact TPC Administrator to fix the problem.
Level: 1

Type: ERROR

Impact: Data

TPC-60082: Cannot perform user synchronization because LDAP is not enabled.

Cause: LDAP is either disabled or its connection parameters have not been specified.

Action: Contact TPC Administrator to fix the problem.
Level: 1

Type: ERROR

Impact: Data

TPC-60083: Failed to update user review preference.

Cause: The review preference may not be in the valid format.

Action: Contact TPC Administrator to fix the problem.
Level: 1

Type: ERROR

Impact: Data

TPC-60084: Cannot authenticate with a non-existing LDAP account.

Cause: You are trying to authenticate using a non existing LDAP account.

Action: Contact TPC Administrator to synchronize your account from LDAP server.
Level: 1

Type: ERROR

Impact: Data

TPC-60085: Failed to update user latest viewed reviews.

Cause: The latest viewed reviews may not be in the valid format.

Action: Contact TPC Administrator to fix the problem.
Level: 1

Type: ERROR

Impact: Data

TPC-60086: Cannot update user offline notification flag.

Cause: The server may not be installed correctly.

Action: Verify the server was installed correctly.
Level: 1

Type: ERROR

Impact: Threads

TPC-60090: Cannot save the team resource as its name is missing.

Cause: You did not specify a name which is required in order to save the team resource.

Action: Specify a name or key for the team resource.
Level: 1

Type: ERROR

Impact: Data

TPC-60091: Cannot save team resource "{0}" for team Id "{1}" and class "{2}" as its detailed parameters are missing.

Cause: You did not specify connection's parameters which are required in order to save the team resource.

Action: Specify connection's parameters for the team resource.
Level: 1

Type: ERROR

Impact: Data

TPC-60092: Team resource "{0}" is missing a required team Id.

Cause: Specified team resource is missing team Id which is required in order to perform the database operation

Action: Specify a valid team Id for the team resource you want to perform an operation on.
Level: 1

Type: ERROR

Impact: Threads

TPC-60093: Cannot find team with team Id "{0}".

Cause: Specified team Id is not found in the database.

Action: Specify a valid team Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60094: Team resource "{0}" for team Id "{1}" and class "{2}" has already existed.

Cause: The team resource you want to create has already existed.

Action: Specify a new team resource to create.
Level: 1

Type: ERROR

Impact: Data

TPC-60095: User Id {0} for a private connection "{1}" with team Id "{2}" and class "{3}" cannot be found.

Cause: The private team resource you want to create has already existed.

Action: Specify a new team resource to create.
Level: 1

Type: ERROR

Impact: Data

TPC-60096: Cannot update or delete empty record.

Cause: The record you try to update or delete is empty or null.

Action: Specify a valid record to update or delete.
Level: 1

Type: ERROR

Impact: Data

TPC-60097: Cannot modify or delete team connection "{0}" as it no longer exists. Please refresh its Connection Type node.

Cause: The team resource you want to update or delete does not exist in the database.

Action: Specify an existing team resource.
Level: 1

Type: ERROR

Impact: Data

TPC-60098: Review Id is null.

Cause: Review id was not found.

Action: Make sure review id was specified in the request.
Level: 1

Type: ERROR

Impact: Data

TPC-60099: Review Work Item List is null.

Cause: Review Work Item List is null.

Action: Make sure review work item list was specified in the request.
Level: 1

Type: ERROR

Impact: Data

TPC-60100: Failed to create connection "{0}". The logged-in user "{1}" does not have ID "{2}" as specified in the connection.

Cause: The team connection does not have the same user ID as the logged-in user.

Action: Specify correct user ID.
Level: 1

Type: ERROR

Impact: Data

TPC-60101: Cannot find user with user ID "{0}".

Cause: Specified user ID is not found in the database.

Action: Specify a valid user Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60102: The user ID "{1}" you specified in your request does not match yours.

Cause: The user requests data belong to someone else, which is disallowed for the operation.

Action: Specify your own user ID.
Level: 1

Type: ERROR

Impact: Data

TPC-60103: User "{0}" does not have permission to create connection "{1}" for team "{2}".

Cause: The user does not have sufficient permission to create a connection in the specified team.

Action: Specify correct user and team.
Level: 1

Type: ERROR

Impact: Data

TPC-60104: Repository "{0}" cannot be deleted since it is used by various {1}. Deleting it will cause severe impact to the system's integrity.

Cause: The repository is used by the specified records.

Action: Remove the dependent or child records and try again.
Level: 1

Type: ERROR

Impact: Data

TPC-60105: Team Repository "{0}" cannot be deleted since it is used by changesets.

Cause: The specified team repository is used by changesets.

Action: Remove the dependent changesets and try again.
Level: 1

Type: ERROR

Impact: Data

TPC-60106: TPC client review preference version "{0}" is outdated. Supported version is "{1}" or higher. Use Help > "Check for Updates..." to upgrade your client.

Cause: Client review preference versions is not supported.

Action: Use Help > "Check for Updates..." to upgrade the client.
Level: 1

Type: ERROR

Impact: Logging

TPC-60107: Cannot find team connection with ID "{0}".

Cause: Specified team connection ID is not found in the database.

Action: Specify a valid team connection Id.
Level: 1

Type: ERROR

Impact: Threads

TPC-60108: TPC server has encountered an error during processing your request "{0}": {1}

Cause: An unexcepted error was raised by the system.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Logging

TPC-60109: Cannot find review with review ID "{0}".

Cause: Specified review ID is not found in the database.

Action: Specify a valid review Id.
Level: 1

Type: ERROR

Impact: Data

TPC-60110: User "{0}" does not have privilege to delete review "{1}" of id "{2}".

Cause: User does not have privilege to delete review.

Action: Specify a valid user Id.
Level: 1

Type: ERROR

Impact: Data

TPC-60111: Review "{0}" of id "{1}" can not be deleted because at least one reviewer has started reviewing.

Cause: Review can not be deleted because at least reviewer has started reviewing.

Action: Abort deleting review
Level: 1

Type: ERROR

Impact: Data

TPC-60112: Team Repository "{0}" cannot be deleted since it is used by queries belong to "{1}".

Cause: The specified team repository is used by saved queries.

Action: Remove the dependent queries and try again.
Level: 1

Type: ERROR

Impact: Data

TPC-60113: Team Repository "{0}" cannot be deleted since it is used by active work items belong to "{1}".

Cause: The specified team repository is used by active work items.

Action: Remove the dependent active work items and try again.
Level: 1

Type: ERROR

Impact: Data

47 UCM-ADF-10000 to UCM-ADF-45200

UCM-ADF-10000: An internal error occurred

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

UCM-ADF-10001: Create operation not supported by Entity Object {0}

Cause: The create operation was performed on an Entity Object that does not support it.

Action: Do not attempt the create operation on this Entity Object.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-10002: Updates not supported by Entity Object {0}

Cause: An update was performed on an Entity Object that does not support updates.

Action: Do not attempt to update this Entity Object.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-10003: Delete operation not supported by Entity Object {0}

Cause: The delete operation was performed on an Entity Object that does not support it.

Action: Do not attempt the delete operation on this Entity Object.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-10004: File not found: {0}

Cause: There was no file at the specified path.

Action: Create the missing file or correct the path.
Level: 1

Type: ERROR

Impact: Files

UCM-ADF-10005: toString method failed: {0}

Cause: The method toString threw an exception.

Action: Review the error reported in the chained exception.
Level: 1

Type: WARNING

Impact: Other

UCM-ADF-10006: Class {0} does not implement interface {1}

Cause: The class instance did not implement a required interface.

Action: Modify the class to implement the required interface.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-10007: Item not found: {0}

Cause: There was no item with the specified primary key.

Action: Specify a primary key of an item that exists.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-10008: Cannot convert {0} to {1}

Cause: The conversion between two types failed.

Action: Ensure the type conversion is valid.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-10200: Localization key {0} not found in {1}

Cause: An internal warning occurred.

Action: Report the warning to Oracle Support Services
Level: 1

Type: WARNING

Impact: Logging

UCM-ADF-10201: Message key not found. Parameters: {0} {1} {2} {3} {4} {5}

Cause: An internal warning occurred.

Action: Report the warning to Oracle Support Services
Level: 1

Type: WARNING

Impact: Logging

UCM-ADF-10202: Log message requires localization due to log level: {0}

Cause: An internal warning occurred.

Action: Report the warning to Oracle Support Services
Level: 1

Type: WARNING

Impact: Logging

UCM-ADF-10204: Error initializing localization preferences for mode: {0}

Cause: Localization preferences for the given mode cannot be initialized.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Other

UCM-ADF-10400: Exception logged automatically

Cause:

Action:
Level: 1

Type: ERROR

Impact: Logging

UCM-ADF-10401: Cannot set the cause of the exception

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

UCM-ADF-10600: Unable to parse XML document

Cause: The XML document was not well formed.

Action: Review and correct the XML document.
Level: 1

Type: ERROR

Impact: Files

Cause: The XML document was not schema valid.

Action: Review and correct the XML document.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.

UCM-ADF-10601: Node {0} has more than one child element named {1}

Cause: The XML document was not valid.

Action: Review and correct the XML document.
Level: 1

Type: ERROR

Impact: Files

UCM-ADF-10602: Node {0} has more than one text child

Cause: The XML document was not valid.

Action: Review and correct the XML document.
Level: 1

Type: ERROR

Impact: Files

UCM-ADF-10800: UCM configuration name not unique: {0}

Cause: More than one UCM configuration had the same name.

Action: Review and correct ucm-configurations.xml.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-10801: Invalid UCM configuration name: {0}

Cause: There was no UCM configuration with the specified name.

Action: Review and correct the Application Module configuration.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-10802: No manager named {0}

Cause: There was no manager with the specified name.

Action: Review and correct the Entity Definition or View Object manager property.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-10803: Invalid class name {0} for manager {1}

Cause: The specified class name could not be loaded.

Action: Review and correct ucm-configurations.xml.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-11000: Unable to create IDC client

Cause: An error occurred creating the IDC client.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

UCM-ADF-11001: Application Module configuration does not define property {0}

Cause: The Application Module configuration did not define a value for the property.

Action: Set the value for the property.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-11200: Unable to create entity manager {0}

Cause: An error occurred creating the entity manager.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-11201: Unable to create view manager {0}

Cause: An error occurred creating the view manager.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-11400: Error executing UCM service {0}

Cause: An error occurred in executing a UCM service.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

UCM-ADF-11401: Error executing UCM service {0}: {1} (status code {2})

Cause: An error occurred in executing a UCM service.

Action: Review the error message.
Level: 1

Type: ERROR

Impact: Requests/Responses

UCM-ADF-11402: Unable to convert {0} to RIDC string

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

UCM-ADF-11403: Unable to convert RIDC string {0} to type {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

UCM-ADF-11404: Unsupported data type: {0}

Cause: An attribute definition specified an unsupported data type.

Action: Review and correct the attribute definition.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-11600: View Definition is {0} but query request View Definition is {1}

Cause: The View Definition was different than the query request's View Definition.

Action: Supply the correct View Definition.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-11601: Invalid option list name: {0}

Cause: The response binder did not have an option list with the specified name.

Action: Supply the correct option list name.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-11800: Entity Definition {0} does not define property {1}

Cause: The Entity Definition did not define a value for the property.

Action: Set the value for the property.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-11801: No value for attribute {0} of Entity Object {1}

Cause: The Manager did not set a value for the attribute.

Action: Review and correct the Manager class.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-11802: DML operation {0} failed for Entity Object {1} with primary key {2}

Cause: The DML operation failed.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Other

UCM-ADF-12000: View Object {0} does not define property {1}

Cause: The View Object did not define a value for the property.

Action: Set the value for the property.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-12001: Unsupported View Object access mode (must be SCROLLABLE): {0}

Cause: The View Object specified an unsupported access mode.

Action: Review and correct the View Object.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-12002: Unable to close RowSetIterator

Cause: The method RowSetIterator#close threw an exception.

Action: Review the error reported in the chained exception.
Level: 1

Type: WARNING

Impact: Other

UCM-ADF-12003: Unable to parse ORDER BY clause: {0}

Cause: The ORDER BY clause cannot be parsed.

Action: Review and correct the ORDER BY clause.
Level: 1

Type: ERROR

Impact: Other

UCM-ADF-12004: Invalid column name or attribute index in ORDER BY clause: {0}

Cause: The column name or attribute index in the ORDER BY column is invalid.

Action: Review and correct the ORDER BY clause.
Level: 1

Type: ERROR

Impact: Other

UCM-ADF-12200: Invalid value of bind parameter {0}: {1}

Cause: The value of the bind parameter was invalid.

Action: Set the bind parameter to a valid value.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-12416: Item not found

Cause: The specified item did not exist.

Action: Specify an item that exists.
Level: 1

Type: ERROR

Impact: Requests/Responses

UCM-ADF-12418: Insufficient privileges

Cause: The user had insufficient privileges to perform the operation.

Action: Perform the operation as a user with sufficient privileges.
Level: 1

Type: ERROR

Impact: Requests/Responses

UCM-ADF-20000: Invalid value of user property {0}: {1}

Cause: A user property contained an invalid value and was ignored.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Data

UCM-ADF-20200: Unsupported search specification type: {0}

Cause: A query specified an unsupported type of search specification.

Action: Review and correct the query.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-20201: Bind parameters SearchSpecification and QuickSearch are mutually exclusive

Cause: A query specified a non-null value for both the SearchSpecification and QuickSearch bind parameters.

Action: Review and correct the query.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-20400: Invalid revision field name: {0}

Cause: The specified revision field name is not found.

Action: Review and correct the revision field name.
Level: 1

Type: ERROR

Impact: Programmatic

UCM-ADF-30000: The Faces Servlet filter ''{0}'' is not configured correctly

Cause: The Faces Servlet filter is not configured correctly.

Action: Check the documentation for the proper filter configuration.
Level: 1

Type: ERROR

Impact: Configuration

UCM-ADF-45000: Unexpected error during login

Cause: An error occurred during logging in.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

UCM-ADF-45200: Unable to logout: {0}

Cause: An error occurred during logging out.

Action: Review the error reported in the chained exception.
Level: 1

Type: ERROR

Impact: Requests/Responses

48 UCS-10106 to UCS-31204

UCS-10106: RemoteAccessFactory is not bound!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10107: Could not find a property editor for class ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10108: Error initializing the editor. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10109: Failed to export command {1}. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10110: Could not create progress writer. Progress information will be lost.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10111: Exception when converting to string. Reason: {0}

Cause: Internal error

Action: No action required.
Level: 1

Type: ERROR

Impact: Process

UCS-10112: Could not connect to remote resource. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10113: Property class {0} was not found.

Cause: Malformed command-service.xml.

Action: Correct command-service.xml.
Level: 1

Type: WARNING

Impact: Process

UCS-10114: Command ''{0}'' has no help!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10115: Missing name element for command.

Cause: Malformed command-service.xml.

Action: Correct command-service.xml.
Level: 1

Type: ERROR

Impact: Process

UCS-10116: Object evicted from cache "{0}". Increase the size of the cache or change the expiry delay. Key = "{1}", value = "{2}".

Cause: An object has been evicted form the cache since the cache is to small.

Action: Increase the size of the cache or change the expiry delay.
Level: 1

Type: WARNING

Impact: Process

UCS-10195: Failed to read commands from file ''{1}''. Reason: {0}.

Cause: Reading and/or parsing of commands failed.

Action: Correct the command description.
Level: 1

Type: ERROR

Impact: Process

UCS-10196: Creating Command Service

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10197: Starting Command Service.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10198: Command Service already started.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10199: Stopping Command Service.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10200: Command Service already stopped.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10201: Destroying Command Service.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10202: Loading command: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10203: Could not instantiate the class ''{1}''. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10204: The class or its nullary constructor is not accessible. Reason: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10205: Could not find the class ''{0}''. Make sure that it is available to the system and verify that you wrote the class name correctly.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10206: Loaded {0} (out of {1}) commands into the system.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10207: Could not find the attribute. The only valid attribute names are \"class", \"resource\" and "\"description\". Please verify that you spelled them correctly.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10249: Failed to send error message to client: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10250: MemoryMonitor starting

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10251: MemoryMonitor stopping

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10252: Expected an Integer but found: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10253: Cannot create a tree of type {0}, returning null

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10254: Unknown exception caught. Message - {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10255: Could not find MessageDigest for algorithm {1}, reason: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10256: Failed to create the XML reader: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10257: Exception {0} with ExceptionUniqueID: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10258: SQL error: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10300: Failed to set default attributes.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10301: Could not find a property editor for attribute type ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10302: Failed to set attribute.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10303: Failed to set list of attributes.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10306: Loading persisted data for {0} [{1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10307: Metadata deserialized.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10308: Error loading MBean state.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10309: Persisting metadata for MBean.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10310: store

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10312: Error persisting MBean

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10313: Loading attribute name: {0}, value: {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10316: Created store file: {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10317: Storing data for {0} [{1}]

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10318: Caught null attribute for {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10319: Constructor threw exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10320: Failed to undeploy Mbeans

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10321: Trying to load Mbean {0}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10322: Registering MBean {0} with object name {1}

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10323: Failed to load Mbean.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10324: Failed to deregister Mbean.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10325: Failed to persist MBean.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10326: Failed to load metadata for Mbean from {1}. Reason: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10327: Failed to call MBean lifecycle {1} for bean {2}. Reason: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-10328: Failed to load the jmxframework.

Cause: Internal Error, possibly misconfiguration or missing jars.

Action: Confirm JMX framework is configured / set up properly.
Level: 1

Type: ERROR

Impact: Process

UCS-11051: Error when looking up userservice.

Cause: The J2EE application SubscriberDataServices may not be deployed or started.

Action: Ensure that the J2EE application SubscriberDataServices is running.
Level: 1

Type: ERROR

Impact: Process

UCS-11052: Error when creating userservice.

Cause: The J2EE application SubscriberDataServices may not be deployed or started.

Action: Ensure that the J2EE application SubscriberDataServices is running.
Level: 1

Type: ERROR

Impact: Process

UCS-11179: Command Line Interface connection problems.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11180: No value for ''{0}'' was provided.

Cause: A configuration value for the indicated property was not specified in the ejb-jar.xml file for the subscriberdataservice application.

Action: Specify the corresponding property.
Level: 1

Type: ERROR

Impact: Process

UCS-11181: Failed to find the user ''{0}''. Reason: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11182: Failed to close connection to LDAP store. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11183: Unable to find a user with attribute ''{0}'' = ''{1}''. Reason: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11184: Failed to find user attributes for privateId = ''{0}''. Reason: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11185: Error performing SQL operation.

Cause: A SQL operation against the database failed.

Action: Verify that the database is accessible and correctly configured.
Level: 1

Type: ERROR

Impact: Process

UCS-11186: Format error in public identity stored in the database.

Cause: A public identity stored in the database is not a valid SIP URI.

Action: Correct the public identity.
Level: 1

Type: ERROR

Impact: Process

UCS-11187: More than one privateId found for publicId ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11188: Failed to get account status for user ''{0}''. Reason: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11189: {0} is not supported in DAO implementation {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11191: Failed to obtain the ha1 digest hash for user ''{0}'' for realm ''{1}''. Reason: {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11192: Failed to obtain the group membership for user ''{0}'' for realm ''{1}''. Reason: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11193: Failed to obtain all the defined roles. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11194: Failed to get ejb environment property ''{0}''. Reason: {1}.

Cause: The value of the given JNDI name is not in a proper format.

Action: Ensure that the value of the JNDI name is a boolean (that is, true or false).
Level: 1

Type: ERROR

Impact: Process

UCS-11208: Invalidating DirContextPool

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11209: Failed to get an instance of {0}. Reason: {1}.

Cause: Installation is not properly configured.

Action: Verify installation.
Level: 1

Type: ERROR

Impact: Process

UCS-11210: Unable to fetch verifier for ''{0}''. Crypto Scheme not supported.

Cause: User in OID not configured properly.

Action: Correct the configuration of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11211: Unable to fetch verifier for ''{0}''. User without reversible password.

Cause: User in OID not configured properly.

Action: Correct the configuration of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11212: Unable to fetch verifier; user name missing.

Cause: User in OID not configured properly.

Action: Correct the configuration of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11213: Failed to obtain an error code for dynamic verifier. Reason: {0}.

Cause: Problems accessing OID

Action: Verify the availability of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11214: Invalid response control for ''{0}''

Cause: User in OID not configured in a proper way.

Action: Correct the configuration of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11215: Empty verifier found for ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11216: No {0} attribute found for verifier.

Cause: User in OID not configured properly.

Action: Correct the configuration of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11217: Empty password attribute found for verifier.

Cause: User in OID not configured properly.

Action: Correct the configuration of OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11218: More than one password verifier found.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11219: Failed to close NamingEnumeration in dynamic verifier.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11220: Failed to parse expiration time ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11221: Failed to parse lockout time ''{0}''.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11222: No user attributes were retrieved!

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11223: Invalid password format for LDAP credentials

Cause: The format of the LDAP password is not recognized.

Action: Verify the configuration of the OID.
Level: 1

Type: ERROR

Impact: Process

UCS-11224: The registered componenent under the JNDI name {0} was not of type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11225: The function with ObjectName ''{0}'' is not a valid math function.

Cause: Configuration of LockoutService uses a math function that is not recognized.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Process

UCS-11226: Could not find the MBean. Have you configured it correctly?. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11227: The math function threw an exception. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11228: A user tried to login with the username ''{0}'', which is not a known username.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11231: Could not create ObjectName for LoginFailure pattern ''{0}''. Reason: {1}.

Cause: Misconfigured installation.

Action: Correct the configuration.
Level: 1

Type: ERROR

Impact: Process

UCS-11232: User ''{0}'' failed to log in. Will call all the configured LoginFailure-handlers in the system.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11233: User ''{0}'' exceeded the maximum number of login attempts.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11234: Did not find account for ''{0}''.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11235: Problems getting account for ''{0}''. Reason: {1}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11236: Could not create SecurityService => Could not unlock account. Reason: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-11237: Failed to setup radius client pool. Reason: {0}.

Cause: Configuration of Radius Client pool is probably faulty.

Action: Verify and correct configuration of Radius Client pool.
Level: 1

Type: ERROR

Impact: Process

UCS-11238: RadiusException when authenticating: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30001: Charging is not allowed

Cause: Attempted to use charging when charging is not allowed (according to the configuration).

Action: Verify ChargingAllowed configuration
Level: 1

Type: WARNING

Impact: Process

UCS-30002: Ignore the 2xx response at state: {0}.

Cause: Received a 2xx response in an illegal state.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30003: Failed to ACK the 2xx repsonse.

Cause: IOException received when trying to send ACK.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30004: Could not ACK a dialog in the state: {0}.

Cause: Illegal state when trying to ACK dialog

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30005: Failed to send SIP request.

Cause: IOException when trying to send SIP request.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30006: Could not cancel a call in the state: {0}.

Cause: Illegal state when trying to cancel call

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30007: Failed to send out response to BYE.

Cause: IOException when trying to send out response to BYE.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30008: Failed to end the call leg.

Cause: Failed to send Bye.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30009: Could not cancel call in connected state.

Cause: Illegal state to cancel call.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30010: Failed to parse the SIP address.

Cause: Illegal SIP address

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30011: Failed to create the call.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30012: Could not find call with id: {0}.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30013: Failed to execute the action.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30014: Failed to terminate the call: {0}.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30015: Could not find the application session for call id: {0}.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30016: Failed to create SIP Invite Message.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30017: Failed to send INVITE to ''{0}'' from ''{1}''.

Cause: Check the exception.

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30018: Failed to handle response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30019: Failed to handle BYE.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30020: Ignore an error response at call state: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30021: Should not receive a BYE message in state: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30022: Failed to retrieve MaxiumCallDuration from configuration store.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30023: The session should not be NULL here; bad internal state.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30024: Could not terminate a call that is not in connected state.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30025: Failed to cancel the call: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30026: Failed to connect the call due to invalid state: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30027: Failed to connect the call due to resource unavailable: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30028: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.

Cause: The cache was not defined in the web.xml.

Action: Define the cache in a resource-ref element in the web.xml
Level: 1

Type: WARNING

Impact: Process

UCS-30029: The call length supervisor failed to end call: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-30030: Could not find the TimerManager "{0}" in JNDI. Call-length supervisor is disabled.

Cause: The TimerManager was not defined in the web.xml.

Action: Define the TimerManager in a resource-ref element in the web.xml
Level: 1

Type: WARNING

Impact: Process

UCS-30031: The cache "{0}" could not be retrieved from the CacheFactory. Make sure that the cache is defined in /config/ucs-thirdpartycall-coherence-cache-config.xml.

Cause: Coherence configuration for the cache is missing in the /config/ucs-thirdpartycall-coherence-cache-config.xml file in the thirdpartycallservice.jar

Action: Define the cache.
Level: 1

Type: ERROR

Impact: Process

UCS-30032: Could not find the WorkManager "{0}" in JNDI.

Cause: The WorkManager was not defined in the web.xml.

Action: Define the WorkManager in a resource-ref element in the web.xml
Level: 1

Type: ERROR

Impact: Process

UCS-30033: Could not call ThirdPartyCallListener at address "{1}" due to: {0}.

Cause: The registered ThirdPartyCallListener at specified address could not be invoked.

Action: Make sure that the ThirdPartyCallListener web services is available.
Level: 1

Type: WARNING

Impact: Process

UCS-30034: Could not schedule ThirdPartyCallListener work with callIdentifier "{1}" due to: {0}.

Cause: A work item for the work manager could not be scheduled

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31000: UCS-31000: PLACE-HOLDER MESSAGE

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31001: UCS-31001: Call Control is starting...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31002: UCS-31002: Call Control has been started

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31003: UCS-31003: Call Control is shutting down...

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31004: UCS-31004: Call Control has been shut down

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31100: UCS-31100: Failed to handle BYE.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31101: UCS-31101: Failed to handle response.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31102: UCS-31102: Exception when handling expired SipApplicationSession. Exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31103: UCS-31103: Could not send ACK. Exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31104: UCS-31104: Configured P-Asserted-Identity header is not an accepted address. Exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31105: UCS-31105: Could not send BYE. Exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31106: UCS-31106: Could not send CANCEL. Exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31107: UCS-31107: Could not send response to BYE. Exception {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31108: UCS-31108: Could not deliver event ''{1}'' to application due to exception in application. Exception {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Process

UCS-31201: JEE application name is not available: {0}.

Cause: JEE application name is not available

Action: Verify that the domain is correctly installed.
Level: 1

Type: WARNING

Impact: Process

UCS-31202: Server name is not available: {0}.

Cause: Server name is not available

Action: Verify that the domain is correctly installed.
Level: 1

Type: WARNING

Impact: Process

UCS-31203: The call detail record (CDR) could not be stored since the CDR is invalid: {0}.

Cause: The call detail record (CDR) could not be stored to the database since the CDR is invalid.

Action: Inspect the logged call detail record (CDR). Correct it and insert manually into the database.
Level: 1

Type: WARNING

Impact: Process

UCS-31204: The call detail record (CDR) could not extracted from the JMS message: {0}.

Cause: The call detail record (CDR) could not be extracted from the JMS message.

Action:
Level: 1

Type: WARNING

Impact: Process

49 UPGAST-00001 to UPGAST-00300

UPGAST-00001: unable to continue due to an unexpected error

Cause: An unexpected error occurred.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00002: Invalid argument {0}; an argument must begin with a hyphen.

Cause: A command-line argument did not start with a hyphen.

Action: Run the command again, using a hyphen to identify any arguments. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00003: invalid argument {0}

Cause: The specified argument was not recognized.

Action: Run the command again, specifying a valid argument. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00004: Value for argument {0} not supplied.

Cause: The value for a command-line argument was not specified.

Action: Run the command again, specifying the required value for the command-line argument. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00009: Invalid log level: {0}.

Cause: The log level specified was not recognized.

Action: Run the command again, specifying a valid log level. Enter the command ua -help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00010: Port number {0} is not valid.

Cause: The port number specified was not a positive numeric value or was out of range.

Action: Specify a valid port number.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00011: Host name {0} is not valid or unknown.

Cause: Lookup of the specified host name failed.

Action: Specify a valid host name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00012: Required port is missing.

Cause: A required port was not entered.

Action: Enter the required port.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00013: Required user name is missing.

Cause: A required user name was not entered.

Action: Enter the required user name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00014: unable to connect to WebLogic Server at {0}:{1}

Cause: Failed connecting to the WebLogic Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00015: Required listen address is missing.

Cause: A required listen address was not entered.

Action: Enter the required listen address.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00016: Required password is missing.

Cause: A required password was not entered.

Action: Enter the required password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00017: Required confirm password is missing.

Cause: A required confirm password was not entered.

Action: Enter the required confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00018: Password and confirm password do not match.

Cause: The password and confirm password do not have the same value.

Action: Enter the same value for the password and confirm password.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00019: User name may not contain commas, tabs, or any of the following characters: {0}

Cause: An invalid user name was specified.

Action: Enter the user name using only valid characters.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00020: Listen address {0} is not valid or unknown.

Cause: Lookup of the specified listen address failed.

Action: Specify a valid listen address.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00021: WLST script failure, see {0} for details

Cause: The execution of a WLST script has failed

Action: Check the specified WLST output file for the details of the failure.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00022: Instance config directory {0} does not exist

Cause: The instance directory specified does not contain the expected config directory.

Action: Specify a valid instance directory and then rerun the Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00023: Standalone template {0} does not exist for component {1} of type {2}.

Cause: A template was not found for the listed component.

Action: Install the components standalone environment and then rerun the upgrade in that standalone environment.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00024: failed reading {0}

Cause: Unable to read or parse the specified file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00025: The password must be at least 8 alphanumeric characters with at least one number or special character.

Cause: An invalid password was specified.

Action: Enter a password using 8 alphanumeric characters with at least one number or special character.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00026: failed reading {0}

Cause: Unable to read or parse the specified OPMN file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00027: OPMN file {0} does not exist in the instance directory.

Cause: The specified OPMN file did not exist.

Action: Specify a valid instance directory where the specified OPMN file exists
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00028: Template {0} does not exist for component {1} of type {2}.

Cause: A template was not found for the listed component.

Action: Install the listed component and then rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00029: Directory is not a valid domain for upgrade. {0}

Cause: The specified directory was not a valid Oracle WebLogic domain for standalone upgrades. The domain was not created during a previous standalone upgrade.

Action: Specify an Oracle WebLogic domain that is created during a previous standalone upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00030: The specified domain name {0} is invalid. It must include only alphanumeric characters, hyphens ("-") or underscore characters ("_") and contain at least one letter but must not start with a number.

Cause: An invalid domain name was specified.

Action: Enter a valid domain name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00031: unable to get the active DomainMBean for the WebLogic Server domain

Cause: Failed getting the active DomainMBean for the WebLogic Server domain.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00032: unable to communicate with the WebLogic Server

Cause: Communication with the WebLogic Administrative Server was either lost or never established.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00033: Required domain directory is missing.

Cause: A required domain directory was not entered.

Action: Enter the required domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00034: unable to establish an EDIT connection

Cause: The connection to the Edit service in the WebLogic Administration Server failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00035: unable to save configuration changes

Cause: Verification in the WebLogic Administration Server failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00036: unable to start an edit operation

Cause: The Edit service in the WebLogic Administration Server failed to start an edit operation.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00037: unable to fetch or store attribute "{0}" in the WebLogic Server

Cause: This is an internal logic error. The most common cause is an incorrect attribute name.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00038: unable to locate an MBean named "{0}"

Cause: The specified MBean was not found. This could be an error, depending on the context.

Action: See the secondary error message for additional details.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00039: failed deleting {0}

Cause: Unable to delete the specified file.

Action: Manually delete the specified file.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00040: unable to get the DomainRuntimeMBean for the WebLogic Server domain

Cause: Failed getting the DomainRuntimeMBean for the current WebLogic Server domain.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00047: failed to read the installer inventory

Cause: The install inventory could not be accessed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00048: unable to open the log file

Cause: Failed to open the log file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00049: unable to read the log file

Cause: Failed to read the log file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00050: unable to create logging directory: {0}

Cause: The directory for log files could not be created.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00051: unable to create the log file

Cause: Failed to create the log file.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00052: unable to initialize logging

Cause: Initialization of logging failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00053: No upgrade components were found in the config file {0}.

Cause: No upgrade components in the specified configuration file.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00054: An error occured loading the domain configuration file {0}

Cause: Either the specified directory does not contain the expected file, or the file does not conform to the expected syntax.

Action: Specify a valid WebLogic domain root directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00056: error initializing upgrade plug-in for {0}

Cause: An unexpected error occurred initializing an upgrade plug-in.

Action: Contact Oracle Support Services. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00058: {0} file does not exist or cannot be accessed.

Cause: The specified file did not exist or could not be accessed.

Action: Make sure the path to the file is correct.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00059: Invalid database type: {0}.

Cause: The database type specified was not recognized.

Action: Specify a valid database type.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00079: failed to create temporary directory: {0}

Cause: An error was encountered creating a temporary directory.

Action: Ensure that the directory location exists and is not protected.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00080: failed to start WebLogic Server {0}

Cause: An error was encountered starting a WebLogic Server.

Action: Examine the log file to determine the reason why the WebLogic server failed to start.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00081: failed to stop WebLogic Server {0}

Cause: An error was encountered stopping a WebLogic Server.

Action: Examine the log file to determine the reason why the WebLogic server failed to stop.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00093: {0} directory does not exist or is not a directory.

Cause: The specified directory did not exist or was not a directory.

Action: Specify a valid directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00094: {0} directory already exists.

Cause: The specified directory already existed.

Action: Specify a valid directory that does not exist.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00095: {0} directory is not writable.

Cause: The specified directory must have write permissions.

Action: Specify a directory that is writable or correct the permissions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00096: error initializing the help system

Cause: An internal error occurred while setting up the help system.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00097: The IP address of the host {0} cannot be determined.

Cause: The network address of the specified host could not be determined.

Action: Check the validity of the specified host.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00098: error setting the Oracle look-and-feel for the graphical user interface

Cause: An internal error occurred while setting the appearance for the graphical user interface.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00107: The DISPLAY environment variable is not set. The graphical user interface (GUI) requires that this environment variable be set on UNIX.

Cause: The required DISPLAY environment variable was not defined.

Action: Set the required DISPLAY environment variable and then rerun the Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00173: The plugin for {0} has requested an input value named {1} but that name is not in the upgrade descriptor.

Cause: There was an inconsistency between the plugin descriptor definition and the input values requested by the plugin.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00174: failed to create or write to response file

Cause: The file specified for saving responses could not be created or written to.

Action: Specify a file in a location that is writable.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00175: Can not read response file {0}.

Cause: The file specified for reading responses does not exist, or can not be read.

Action: Specify a readable response file.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00176: Response file specifies an unknown upgrade step {0}.

Cause: The response file specifies an upgrade that is unknown in this Fusion Middleware installation. Either the response file is for some other environment, or the Upgrade Descriptor files have not been properly installed.

Action: Specify a response file generated for this installation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00177: Response file line is not understood: {0}

Cause: The response file contains syntax errors.

Action: Correct the syntax errors in the response file and run the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00178: Response file specifies a bad input name, {0}.

Cause: The response file contains syntax errors, or is not of the correct version.

Action: Correct the syntax errors in the response file and run the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00180: error loading upgrade plug-in for {0}

Cause: An unexpected error occurred loading an upgrade plug-in.

Action: Contact Oracle Support Services. See the secondary error message for additional details.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00181: error during execution of upgrade plug-in for {0}

Cause: An unexpected error occurred during execution of an upgrade plug-in.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00182: The examination phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevented the examination phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00183: The upgrade phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevented the upgrade phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00185: failed to load JDBC driver

Cause: There was a failure loading a JDBC driver.

Action: See the log file for details. This is an internal error. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00186: unable to connect to database as the DBA user name {0}

Cause: Required fields to connect to a database were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00187: Unable to connect to WebLogic Admin Server. Some fields are empty.

Cause: Required fields to connect to a WebLogic Admin Server were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00188: SQL script {0} does not exist.

Cause: SQL script could not be located. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00189: Exception raised while running an external command.

Cause: An exception was raised while running an external command (such as sqlplus) in a subprocess. Check the stack trace for detailed information.

Action: Attempt to correct the environment problem if any, then retry the upgrade. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00190: {0} component version is {1}, status is {2}, upgraded flag is {3}

Cause: During upgrade a component reported a successful upgrade but the SCHEMA_VERSION_REGISTRY was not updated correctly. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00191: unable to validate the SCHEMA_VERSION_REGISTRY for component {0}

Cause: An unexpected error occurred validating the SCHEMA_VERSION_REGISTRY. This is an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00192: A dependency by component {0} on component {1} is unresolved.

Cause: A required component was not found while discovering upgrade components and their dependencies.

Action: Make sure the required component has been installed and that it's upgrade descriptor XML file is in the plugins/upgrade directory of their product home.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00196: The validate method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the validate method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00197: No upgrade descriptor files were found in the Oracle home.

Cause: Either this Oracle home contains no upgradable components, or the installation was incomplete.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00198: Descriptor tag {0} is only allowed in components of type={1}

Cause: An upgrade plugin descriptor is improperly formed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00200: Message reference {0} is not defined in resource bundle {1}.

Cause: An upgrade plugin descriptor is referencing an undefined message.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00202: Unable to validate credentials. Some fields are empty.

Cause: Required fields to validate credentials were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00203: Internal Error, validate method is not implemented by plug-in for input named {0}.

Cause: Required validate method was not implemented by plug-in or the signature of the validate method is incorrect.

Action: Implement the required validate method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00204: Response file specifies an unknown field "{0}".

Cause: The response file specifies an input value with a qualified field name that is unknown for inputs of this type.

Action: Specify a response file generated for this installation or correct your editing error.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00205: Response file specifies an incorrect or no format version. Version must be {0}.

Cause: The fileFormatVersion specified in the [GENERAL] section of the file is either missing or incorrect for this program.

Action: Generate new response files using the same version of the program that is going to read them.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00206: No upgrade descriptor files were found in the Oracle home, yet a response file was specified.

Cause: Either this Oracle home contains no upgradable components and you are using a response file generated for a different installation, or the installation is incomplete or damaged.

Action: Make sure that this installation is the one you intended to upgrade, and that the Upgrade Descriptor files are in the plugins/upgrade/ directories
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00207: The Upgrade Descriptor in file {0} specifies a bad value "{1}" for the attribute named "{2}".

Cause: An attribute in a tag in an Upgrade Descriptor, which provides information to the Upgrade Assistant about individual upgrade plugins, contains an improper value.

Action: Contact Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00208: An unrecognized database type "{0}" was specified in a descriptor or response file.

Cause: Database type names in descriptor and response files must come from a fixed list of names. A name was encountered which is not on the list.

Action: Correct the spelling of your database type and run the program again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00209: directory path is not specified

Cause: A required directory path was not entered.

Action: Enter the required directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00210: file path is not specified

Cause: A required file path was not entered.

Action: Enter the required file path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00211: The response file specified a dependency on a plugin numbered {0} but either no plugin in the file has that as an INSTANCE value, or the descriptor file does not indicate that such a dependency is possible.

Cause: All dependsOnPluginInstance properties must refer to numbers defined earlier in the response file with a pluginInstance property, and must refer to a plugin to which such a dependency is allowed by the upgrade descriptor file.

Action: If you created or edited the response file, correct the error and try again. If this is a response file generated by the Upgrade Assistant, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00212: unable to connect to database as the schema user {0}

Cause: Required fields to connect to a database were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00213: Unable to connect to database as the dba user "{0}". {1}.

Cause: The database connection failed for the specified reason.

Action: Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is "Login has timed out" verify that the host and port are correct and make sure the database is up and is configured for network access.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00214: Unable to connect to database as the schema user "{0}". {1}.

Cause: The database connection failed for the specified reason.

Action: Correct the problem using information provided in the log file; then retry the operation. In particular if the indicated reason is "Login has timed out" verify that the host and port are correct and make sure the database is up and is configured for network access.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00215: Upgrade is not being done due to examine failures.

Cause: When using a response file, actual upgrades are not done if any plugin can not complete it's EXAMINE phase.

Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00216: A library file "{0}" referred to in an Upgrade Descriptor file does not exist.

Cause: Upgrade Plugins can refer to other JAR files. A file in such a reference can not be found. This can be caused by an incorrect installation.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00217: directory path is not specified {0}

Cause: A required directory path was not entered.

Action: Enter the required directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00218: file path is not specified {0}

Cause: A required file path was not entered.

Action: Enter the required file path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00219: No schemas were found for component {0} in the Schema Version Registry.

Cause: A database query to get a list of schemas from the Schema Version Registry returned an empty list.

Action: Verify that you have schemas for the specified component.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00220: failed to get a list of schemas from the Schema Version Registry

Cause: A database query to get a list of schemas from the Schema Version failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00221: unexpected error upgrading schema

Cause: An unexpected error occurred during schema upgrade.

Action: Check the error messages in the Upgrade Assistant log files. Correct the problem before running the Upgrade Assistant again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00222: invalid database type specified

Cause: An invalid database type was specified.

Action: The database type specified is not supported by the RCU JDBCEngine. Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00223: The upgrade of "{0}" is being skipped because the upgrade for "{1}" has either failed or been skipped.

Cause: One component upgrade which is a pre-requisite for a second component's upgrade has not finished successfully. Therefore the second component's upgrade has not been executed.

Action: Fix the original problem and run Upgrade again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00224: The specified database does not contain any schemas for {0} or the database user lacks privilege to view the schemas.

Cause: The database you have specified does not contain any schemas registered as belonging to the component you are upgrading, or else the current database user lacks privilege to query the contents of the schema version registry.

Action: Verify that the database contains schema entries in schema version registry. If it does not, specify a different database. Verify that the user has DBA privilege. Connect to the database as DBA.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00225: The response file contains a non-numeric value "{0}" where a number is required.

Cause: Plugin ID numbers must be decimal integers.

Action: Correct the response file and run the program again.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00226: The database connect string format is incorrect. The correct format is: {0}

Cause: The database connect string format was specified incorrectly.

Action: Enter the database connect string using the correct format.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00227: Oracle instance directory path is not specified

Cause: A required Oracle instance directory path was not entered.

Action: Enter the required Oracle instance directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00228: Oracle instance directory path is not specified {0}

Cause: A required Oracle instance directory path was not entered.

Action: Enter the required Oracle instance directory path.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00229: The directory {0} is not an 11g Oracle instance directory.

Cause: The directory specified was not a valid 11g Oracle instance directory.

Action: Enter a valid 11g Oracle instance directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00230: No editions were found

Cause: A database query to get a list of editions returned an empty list.

Action: Verify that you have editions enabled and have created on or more editions.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00231: failed to get a list of editions

Cause: A database query to get a list of editions failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00232: database query for compatibility failed: {0}

Cause: A database query to check that database compatibility is 11.2.0 or greater failed

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00233: database compatibility must be 11.2.0 or greater not {0}

Cause: An EBR-enabled Oracle database requires that compatibility parameter be set to "11.2.0" or greater. However the actual compatibility was less than version 11.2.0

Action: Issue the SQL command ALTER SYSTEM SET COMPATIBLE = '11.2.0' SCOPE=SPFILE.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00234: Unable to enable editions for schema: {0}

Cause: An attempt to enable editions for the database user failed.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00235: Schema version registry table does not exist for component {0}

Cause: An attempt to list the contents of schema version registry table for the component failed because the schema version registry does not exist. This is expected only in the case of ODI 11.1.1.3.0 schemas that were created by ODI Studio.

Action: If this error occurs when upgrading a non-ODI 11.1.1.3.0 schema there is an internal error. Contact Oracle Corporation
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00236: There is no schema version registry entry for component {0}

Cause: An attempt to list the contents of schema version registry table for the component failed because no registry entry exists for the component. This is expected only in the case of ODI 11.1.1.3.0 schemas that were created by ODI Studio.

Action: If this error occurs when upgrading a non-ODI 11.1.1.3.0 schema there is an error. Contact Oracle Corporation
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00237: A duplicate component definition for component {0} has been detected in product home {1}.

Cause: Component names must be unique within an Oracle home. Either the component descriptor files are incorrect, or multiple copies of the same component have been installed in the same Oracle home.

Action: Remove the duplicate installations, or contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00238: A dependency by component {0} on component {1} is unresolved. Upgrades of component {0} will be disabled.

Cause: A dependent component was not found while discovering upgrade components and their dependencies.

Action: Make sure the required component has been installed.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00239: messageclass attribute must be specified for message reference {0}

Cause: A resource bundle was not specified in the component's upgrade descriptor.

Action: Specify the component's resource bundle using the messageclass attribute.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00240: An unexpected error was encountered while monitoring the progress of a plugin.

Cause: During the upgrade phase of a plugin, the upgrade monitor thread encountered an error while shutting down

Action: The Fusion Middleware schema upgrade was not impacted and the error can be ignored.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00241: An unexpected error has occured while executing WLST commands: {0}

Cause: The WLST interpreter exited abnormally. This could be due to an environmental problem or to an error in the script.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00242: Unable to connect to the LDAP Server. {0}.

Cause: Failed connecting to the LDAP Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00243: Unable to connect to the LDAP Server. {0}. {1}.

Cause: Failed connecting to the LDAP Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00244: unable to connect to {0} Server {1}

Cause: Required fields to connect to the specified Server were not supplied.

Action: Enter the missing required fields and rerun.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00245: An unexpected error has occurred while initializing internal data structures.

Cause: A problem was encountered while setting up the internal WLS descriptor.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00246: The selected domain has a version of {0} which is less than the minimum of {1}.

Cause: Upgrade requires the domain to be at a certain minimum version, which this domain does not meet.

Action: Select a different domain, or run the Reconfiguration tool before trying to upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00247: unable to connect to WebLogic Server at {0}:{1} {2}

Cause: Failed connecting to the WebLogic Server at the specified host and port.

Action: See the secondary error message for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00248: Descriptor item {0} missing required "text" attribute.

Cause: The named input tag in an upgrade descriptor does not have a required "text" attribute.

Action: Contact Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00249: Internal Error, isOptionalInputRequired method is not implemented by plug-in for input named {0}.

Cause: Required isOptionalInputRequired method was not implemented by plug-in or the signature of the isOptionalInputRequired is incorrect.

Action: Implement the required isOptionalInputRequired method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00250: Required input {0} is missing from section {1} in the response file.

Cause: The response file does not supply any values for a required input.

Action: Correct the response file and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00251: An error occured reading Upgrade Descriptor file {0}

Cause: The file does not conform to the expected syntax.

Action: See the secondary message for additional information. Contact Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00252: Required input {0} is missing from section {1} in response file.

Cause: The response file does not supply any values for an optional input that the plugin indicates it needs in this case.

Action: Correct the response file and retry the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-000253: An error occured loading the domain configuration from {0}.

Cause: WLST encountered a problem loading the domain configuration files. See the console stackdump for further information.

Action: Choose a different domain root.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00254: invalid response file contents

Cause: The response file is not a valid response file.

Action: Specify a response file generated for this installation or correct your editing error. See secondary message for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00255: Response file invokes plugin for {0} more than once.

Cause:

Action: If you need to upgrade multiple instances of the same component, use multiple runs of the Upgrade Assistant.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00256: Upgrade is being skipped because the -examine flag is set

Cause: When using a response file, actual upgrades are not done when the -examine command line option is set.

Action: If you want to perform an actual upgrade in response file mode remove the -examine flag from the command line. If you intended to perform just the examine phase, no action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00257: The -examine flag is only allowed with the -response flag

Cause: You cannot specify -examine command line option without the -response option.

Action: You cannot specify the -examine flag when running the upgrade tool in GUI mode. If you want to perform an examine without an actual upgrade you must also specify -response on the command line.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00258: Component {0} named in response file is not in domain {1}.

Cause: The response file references a component which is not configured in the specified domain.

Action: Specify a response file generated for this domain.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00259: The getInitialValue method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the getInitialValue method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00260: Internal Error, getInitialValue method is not implemented by plug-in for input named {0}.

Cause: Required getInitialValue method was not implemented by plug-in or the signature of the getInitialValue method is incorrect.

Action: Implement the required getInitialValue method with the correct signature.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00261: The isOptionalInputRequired method for plug-in {0} will not be called due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the isOptionalInputRequired method from executing.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00262: The log directory did not exist or cannot be accessed: {0}.

Cause: The log directory specified was not recognized as an existing, writable directory.

Action: Run the command again, specifying a valid log directory. If necessary create the log directory and make sure it is a writable directory. See the command line help for details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00263: The response file contained both configuration type and schema type upgrades.

Cause: The response file contains a mix of configuration type and schema type upgrades.

Action: Change the response file to specify only configuration type or schema type upgrades then rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00264: Bad "name" attribute value in Upgrade Descriptor.

Cause: Names in Upgrade Descriptor files must be alphanumeric.

Action: Correct the name.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00265: Directory is not a valid domain for upgrade. {0}

Cause: The specified directory was not a valid Oracle WebLogic domain.

Action: Specify an existing WebLogic domain directory.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00266: Oracle instance directory {0} is not a unique directory path.

Cause: A duplicate Oracle instance directory path was specified.

Action: Specify Oracle instance directoies that are not duplicated.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00268: The response file specified is not for a standalone upgrade.

Cause: The response file contained WebLogic credentials that are not valid during a standalone upgrade.

Action: Regenerate the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00269: The response file specified is not for an upgrade requiring WebLogic credentials.

Cause: The response file does not contain WebLogic credentials that are required during an online upgrade.

Action: Regenerate the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00280: The -examine flag is not allowed with the -readiness flag

Cause: You cannot specify -examine command line option with the -readiness option.

Action: You cannot specify the -examine flag when running the upgrade tool in readiness check mode. If you want to perform an examine without an actual upgrade you must remove the -response option from the command line.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00281: Upgrade is being skipped because the -readiness flag is set

Cause: Actual upgrades are not done when the -readiness command line option is set.

Action: If you want to perform an actual upgrade remove the -readiness flag from the command line. If you intended to perform just the readiness phase, no action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00282: Upgrade Assistant is finished due to readiness check failures.

Cause: Examine the readiness check report file and the log file to understand which checks failed.

Action: Correct the problem using information provided in the log file; then retry the operation.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00283: The readiness check phase for plug-in {0} will not be run due to a previous error.

Cause: An error occurred when loading or initializing the plug-in which prevents the readiness check phase from running.

Action: Review the log file for additional details.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00285: The selected domain has a version of {0} which is less than the current release {1}.

Cause: Upgrade readiness requires the domain to be of a version older than the current release. This prerequisite has been met.

Action: No action is necessary.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00286: The selected domain has a version of {0} which is equal to or newer than the minimum of {1}.

Cause: Upgrade readiness requires the domain to be at an older version than the current release, which this domain does not meet.

Action: Select a different domain before running the readiness check.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00290: getNewVersion returns null for plugin {0} because newversion attribute is missing from upgrade descriptor file

Cause: The upgrade plugin called the getNewVersion API without having declared newversion= attribute in the upgrade descriptor file.

Action: Correct the upgrade descriptor file. Starting in release 12.1.3 the <schema> tags must include a newversion= attribute that shows what the schema version number will become after sucecssful upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00291: The schema examination phase failed because newversion attribute is missing from upgrade descriptor file for {0}. See bug 16358145 for details.

Cause: The upgrade framework detect that the plugin has not declared the required newversion= attribute in the upgrade descriptor file. Refer to bug 16358145 for further description.

Action: Correct the upgrade descriptor file. Starting in release 12.1.3 the <schema> tags must include a newversion= attribute that shows what the schema version number will become after sucecssful upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00292: Null value found in UAWLSINTERNAL field "{0}" of the response file.

Cause: A value necessary for identifying the WLS domain is missing.

Action: Correct the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00293: Unexpected error occurred when retrieving information for the datasource "{0}".

Cause: The upgrade framework encountered an internal error when it attempted to retrieve information for a datasource.

Action: This is an internal error. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00294: Unable to establish a connection to a WLS server.

Cause: Attempt was made to connect to a WLS server during an offline upgrade.

Action: Correct the response file and rerun the upgrade.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00295: The selected domain has a version of {0} which must be less than the current release {1}.

Cause: Schema upgrade requires the domain to be of a version older than the current release. This prerequisite has not been met.

Action: Choose a different domain that is for a previous release of Oracle Fusion Middleware.
Level: 1

Type: ERROR

Impact: Upgrade

UPGAST-00296: The Upgrade Descriptor in file {0} specifies an illegal combination of attributes "{1}" and "{2}".

Cause: A tag in an Upgrade Descriptor, which provides information to the Upgrade Assistant about individual upgrade plugins, contains two attributes whose values are incompatible with each other.

Action: Contact Oracle Support.
Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGAST-00297: no text found for offset {0}, read amount {1}, document length {2}

Cause: Unknown; possibly the result of previous errors.

Action: Refresh the log file viewer window.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00298: find position {0}, offset, {1}, search string {2}

Cause: Unknown; possibly the result of previous errors.

Action: Refresh the log file viewer window.
Level: 1

Type: WARNING

Impact: Upgrade

UPGAST-00300: The preselected check box for {0} has been deselected by the user

Cause: The user has manually unchecked an upgrade item that was preselected by Upgrade Assistant.

Action: Make sure that Oracle's recommendation to always upgrade this item really does not apply to your situation. If you are unsure then this box should be checked in most cases
Level: 1

Type: WARNING

Impact: Upgrade

50 WC-05319 to WC-05370

WC-05319: Failed to retrieve security parent portal for the child portal {0}

Cause: Failure in retrieveing security parent

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05320: Failed to copy security data for portal {0}

Cause: Copy of security data from the security parent failed

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05321: Failed to delete portal {0} and all its children

Cause: Deletion of portal along with children failed

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05322: Failed to retrieve parent portal for the child portal {0}

Cause: Failure in retrieving parent portal

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05323: Failed to retrieve child portals for portal {0}

Cause: Failure in retrieving child portals

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05324: Failed to set inheritance from parent for portal {0}

Cause: Failure in setting the inheritance flag for child portals

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WC-05370: Failed to retrieve root portal for portal {0}

Cause: Failure in retrieving root portal

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

51 WCS-03051 to WCS-90200

WCS-03051: No event is selected.

Cause: There was invalid or missing information in the connection.xml or adf-config.xml file.

Action: Verify that the connections.xml and adf-config.xml file contains a valid entry with the correct connection information.
Level: 1

Type: WARNING

Impact: Other

WCS-03052: event date validation error

Cause: An invalid date or time was selected for the event.

Action: Verify the date and time.
Level: 1

Type: ERROR

Impact: Other

WCS-03053: No upcoming events were found.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection for the Portal Events service, and the Portal Events server is running
Level: 1

Type: WARNING

Impact: Other

WCS-03101: The Events service is not able to acquire an adapter from the server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the adapter was not defined.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the specified adapter is defined.
Level: 1

Type: ERROR

Impact: Other

WCS-03102: The Events service is unavailable.

Cause: The connections.xml file either did not contain a valid connection entry for the Personal Events service, or it was missing the entry for Personal Events with the state attribute set to default.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03103: Data query in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03104: Create event in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03105: Update event in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03106: Delete event in Personal Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03107: failure to send event mail in Personal Events service

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and that the Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03108: failure to retrieve online meeting

Cause: Either the connections.xml file did not contain a valid connection entry for the Conference service, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection for the Conference service, and the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03109: failure to retrieve personal event list

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03110: failure to retrieve personal event detail

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03111: The Personal Events service credential is not configured properly.

Cause: The Personal Events service credential was not configured properly.

Action: Verify that the Personal Events service credential is correct, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-03112: The Personal Events service is not properly configured.

Cause: The Personal Events service was not properly configured in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Personal Events service.
Level: 1

Type: ERROR

Impact: Other

WCS-03113: The Personal Events server is not available.

Cause: The Personal Events server was not available.

Action: Verify that the connections.xml file contains a valid entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03114: failure to send personal event

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and the Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03115: failure to log in to the Exchange server

Cause: The credential for the Personal Events service was not configured properly or the Exchange server was not running.

Action: Verify that the credential for the Personal Events service is correct, and the Exchange server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03116: failure to log in to the Exchange server

Cause: The credential for the Personal Events service credential was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03117: Failed to login to the exchange server.

Cause: The credential for the Personal Events service is not configured properly or the exchange server is not running.

Action: Verify that the credential for the Personal Events service is correct, and the exchange server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03118: Failed to login to the exchange server.

Cause: The credential for the Personal Events service credential is not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03201: The Events service is not able to acquire an adapter for an Events server.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service.
Level: 1

Type: ERROR

Impact: Other

WCS-03202: The Events service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03203: Data query in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03204: Create event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03205: Update event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03206: Delete event in Events service failed

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03207: Send event mail in Events service failed

Cause: Either the connections.xml file did not contain a valid connection for the Mail service, or the Mail server was down.

Action: Verify that the connections.xml file contains a valid connection for the Mail service, and Mail server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03208: The changes to the event cannot be saved.

Cause: The event was modified or deleted by another user after the event was retrieved.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-03209: Cannot create the category

Cause: The category could not be created because a category of the same name already exists.

Action: Select the existing category.
Level: 1

Type: ERROR

Impact: Other

WCS-03210: cannot add the portal event to the personal calendar

Cause: Either the connections.xml file did not contain a valid connection entry for the Personal Events service, or the Personal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03211: cannot add the portal event to the personal calendar

Cause: The Personal Events service was not configured properly in connections.xml or the Personal Events service is down.

Action: Verify that the connections.xml file contains a valid connection entry for the Personal Events service, and the Personal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03212: cannot add the portal event to the personal calendar

Cause: The credential for the Personal Events service was not configured properly.

Action: Verify that the credential for the Personal Events service is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-03213: Failure to create category

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03214: failure to retrieve categories

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03215: failure to retrieve portal event list

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03216: failure to retrieve portal event detail

Cause: Either the connections.xml file did not contain a valid connection entry for the Portal Events service, or the Portal Events server was down.

Action: Verify that the connections.xml file contains a valid connection entry for the Portal Events service, and the Portal Events server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03217: failure to check the relationship for the event

Cause: Either the connections.xml file did not contain a valid connection entry for the Relationship service,or the Relationship service was down.

Action: Verify that the connections.xml file contains a valid entry for the Relationship service, the Relationship service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03218: failure to save the display mode preference

Cause: Either the connections.xml file did not contain a valid connection entry for the Preferences service, or the Preferences service was down.

Action: Verify that the connections.xml file contains a valid entry for the Preferences service, and the Preferences service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03219: failure to change the repeat attributes

Cause: Either the connections.xml file did not contain a valid connection entry for the Events service, or the Events service was down.

Action: Verify that the connections.xml file contains a valid entry for the Events service, and the Events service is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03220: The event was deleted by another user after you retrieved it. Refresh the Events task flow to see the changes if necessary.

Cause: The event was deleted by another user after you retrieved it.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03221: The event was updated by another user after you retrieved it. Refresh the Events task flow to see the changes if necessary.

Cause: The event was updated by another user after you retrieved it.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03222: You do not have permission to update this event or your permission to update this event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to update this event or your permission to update this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03223: You do not have permission to view this event or your permission to view this event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to view this event or your permission to view this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03224: You do not have permission to create the event or your permission to create the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to create this event or your permission to create this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03225: You do not have permission to delete the event or your permission to delete the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to delete this event or your permission to delete this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03226: You do not have permission to manage the event or your permission to manage the event is revoked. Refresh the Events task flow to see the changes if necessary.

Cause: You do not have permission to manage this event or your permission to manage this event is revoked.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03227: Event not found.

Cause: The event doesn't exist or was deleted.

Action: Refresh the Events task flow to view changes, and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-03228: The Events service is currently disabled, preventing you from performing this operation. Contact your administrator.

Cause: The Events service is currently disabled.

Action: Contact your administrator. Enable the Events service.
Level: 1

Type: WARNING

Impact: Other

WCS-03301: The Web Conference service is unavailable.

Cause: Either the connections.xml file did not contain a valid connection entry, or the adapter was not defined in the adf-config.xml file.

Action: Verify that the connections.xml file contains a valid connection entry, and the specified adapter is defined in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-03302: The Web Conference service is unavailable.

Cause: The connections.xml file either did not contain a valid connection entry or the entry for conference service with the state attribute set to default was missing.

Action: Verify that the connections.xml file contains a valid connection entry and that the conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03303: failure to query data in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03304: failure to create conference in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03305: failure to update conference in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03306: failure to delete conference in WebCenter Conference service

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03307: failure to retrieve personal meetings

Cause: There was an issue with the connections.xml file, or the Conference server was down.

Action: Verify that the connections.xml file contains a valid connection entry and that the Conference server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03308: The Conference service is not properly configured.

Cause: The Conference service was not properly configured in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: ERROR

Impact: Other

WCS-03309: The Conference service is properly not configured.

Cause: The Conference service was not configured in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: WARNING

Impact: Other

WCS-03310: The Conference service is not properly configured.

Cause: The ambiguous connections of Conference service were found in connections.xml.

Action: Verify that the connections.xml file contains a valid entry for the Conference service.
Level: 1

Type: ERROR

Impact: Other

WCS-03701: WebCenter Tasks service unable to acquire a data connection.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03702: Tasks query failed in WebCenter Task service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03703: Create task failed in WebCenter Task service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03704: Task update failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03705: Task purge failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03706: Task delete failed in WebCenter Tasks service.

Cause: There was an issue with the connections.xml file, or the BPEL server was down.

Action: Verify that the connections.xml file contains a valid entry with the bpel.state set to default, and that the BPEL server is running.
Level: 1

Type: ERROR

Impact: Other

WCS-03707: The adf-config.xml element associated with the BPEL connection to be used by the To-Dos and Group Tasks service was not present.

Cause: "The application\'s adf-config.xml file was missing the adf-task-config element containing a BPELConnection name.

Action: Add the adf-config.xml entry associated with the To-Dos and Group Tasks service\'s BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: ERROR

Impact: Other

WCS-04001: unable to resolve the name {0}

Cause: The object with the given name could not be found.

Action: Check the JNDI configuration or the context passed.
Level: 1

Type: ERROR

Impact: Other

WCS-04002: ADFConfig does not contain adf-collaboration-config details with namespace: {0}.

Cause: The collaboration configuration tag 'adf-collaboration-config' might have been missing in ADFConfig.

Action: Ensure that the adf-config.xml file contains the adf-collaboration-config tag.
Level: 1

Type: ERROR

Impact: Other

WCS-04003: No adapter found for service {0}

Cause: No adapter configuration found or the implementation class could not be loaded.

Action: Ensure adapter is configured properly or change the SessionFactory to override the default behavior.
Level: 1

Type: ERROR

Impact: Other

WCS-04004: unable to load the class {0}

Cause: The class named in the error message was not available in the class path.

Action: Check the class path and ensure this class is available.
Level: 1

Type: ERROR

Impact: Other

WCS-04005: unable to load the class {0}, due to: {1}

Cause: Either the class named in the error message was not available in the class path or it could not be instantiated.

Action: Check the logs for more details. Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-04006: ADFConfig {0} {1} does not contain the required attribute {1}.

Cause: The required attribute was missing from the configuration.

Action: Ensure that the required attribute is added to the configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-04007: The attachment size is too large to be consumed.

Cause: The storage quota was exceeded.

Action: Select a different attachment with a smaller size.
Level: 1

Type: WARNING

Impact: Other

WCS-04008: The attachment type is not supported.

Cause: The attachment type was not supported.

Action: Try with a different MIME type.
Level: 1

Type: WARNING

Impact: Other

WCS-04009: The attachment cannot be found.

Cause: The attachment was not readable.

Action: Try a different attachment.
Level: 1

Type: WARNING

Impact: Other

WCS-04010: failure to create, update, or fetch the service configuration file {0}, due to: {1}

Cause: One of the following was the cause: There was a concurrent modification by another user; there was an MDS I/O exception; the metadata was not found; a validation error occurred; or the update was not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-04011: unable to find the service configuration file {0}, due to: {1}

Cause: The service was not provisioned for this portal.

Action: Provision this service or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04012: unable to find the credentials for user {0}

Cause: The credentials were either not supplied, or were invalid.

Action: Supply credentials using the External Application configured for the service.
Level: 1

Type: WARNING

Impact: Other

WCS-04013: failure to authenticate the user {0}, due to: {1}

Cause: There was a failure while connecting to server, or the credentials were invalid.

Action: Ensure the credentials are supplied and are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-04014: no connections available for: {0}

Cause: There are no connections defined for this connection type.

Action: At least one connection must be defined for this connection type.
Level: 1

Type: WARNING

Impact: Other

WCS-04015: There are multiple connections defined for the connection type {0}, but no default connection is specified.

Cause: Multiple connections of this type were defined, but the default connection was not specified.

Action: Select the appropriate connection for this type and mark it as the default.
Level: 1

Type: ERROR

Impact: Other

WCS-04016: unable to look up connection with name {0}

Cause: Either the connection name was wrong or the connection was deleted.

Action: Verify the name of the connection supplied and also ensure that the connection with this name is available.
Level: 1

Type: ERROR

Impact: Other

WCS-04017: failure to create session instance for: {0}

Cause: An instantiation exception occurred for the session class. Either this class was not a valid class or it could not be loaded from the class path.

Action: Verify that the session class supplied is a valid class, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Other

WCS-04018: failure to create session for {0}, due to: {1}

Cause: Either the required configuration was missing or class was not found.

Action: Verify that the session class supplied is a valid class, and that it is available in the class path.
Level: 1

Type: ERROR

Impact: Other

WCS-04019: There are multiple adapters for the session {0}, but the default adapter is not specified.

Cause: Multiple adapters were defined for this session type, but the default adapter was not specified in the connection.

Action: Update the connection and ensure that the adapter name is specified (ensure that the "adapter.name" property exists).
Level: 1

Type: ERROR

Impact: Other

WCS-04020: No adapter found with name {0}.

Cause: Adapter not found with the given name.

Action: Ensure the adapter with this name configured in the adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-04021: Not an instance of {1} : {0}

Cause: Supplied class is not an instance of SessionManager class.

Action: Check the service configuration property "session.manager.class".
Level: 1

Type: ERROR

Impact: Other

WCS-04022: The service is unavailable.

Cause: Cannot establish connection to the server, either the server is down or the connect details are wrong.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04023: Cache not available.

Cause: Cache is not initialized.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04024: unable to find object {0} in the cache

Cause: The object was either not cached or it had expired.

Action: Ensure that the object is cached.
Level: 1

Type: WARNING

Impact: Other

WCS-04025: Session not initialized {0}.

Cause: Either initialize method on the session is not invoked or initialization has failed.

Action: Check logs for more details or Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04026: session instance acquired is null from SessionFactory: {0}

Cause: SessionFactory returned null session instance. Wrong factory implementation.

Action: Check the SessionFactory implementation for more details or contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04027: Session Factory class not defined.

Cause: Either the service-config for the session is missing or "session.factory.class" property is missing.

Action: Check the service-config.xml for the given session type exists and "session.factory.class" property is defined with a qualified class name that is available in the classpath. Contact system administrator for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-04030: System user session is requested from session {0}, but administrator user name is not defined in the connection nor in adf-config.

Cause: Missing "admin.user" property from connection and/or adf-config.xml.

Action: Ensure that either the connection or ADF service-config contains a property called "admin.user" with a valid administrator user.
Level: 1

Type: WARNING

Impact: Other

WCS-04031: Unexpected error occurred, due to : {0}

Cause: An unexpected server exception occurred.

Action: Contact the system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04032: Could not get access to cache object.

Cause: API should be invoked only for getting access to the root cache.

Action: Try using correct API.
Level: 1

Type: WARNING

Impact: Other

WCS-04033: Invalid cache name: {0}.

Cause: Cache name supplied is either empty or null.

Action: Supply valid name for the cache.
Level: 1

Type: WARNING

Impact: Other

WCS-04034: Not able to fetch data due to {0}.

Cause: Might be because the backend system is not reachable.

Action: Try after sometime.
Level: 1

Type: WARNING

Impact: Other

WCS-04035: Session Type for Session instance {0} is null.

Cause: Session Factory does not set the SessionType on the Session instance created.

Action: Check the session factory implementation.
Level: 1

Type: WARNING

Impact: Other

WCS-04036: User not found: {0}.

Cause: Unable to find the user with the supplied name in the user repository.

Action: Check user with the given identity exists in the user repository.
Level: 1

Type: WARNING

Impact: Other

WCS-04037: Supplied class {0} is not an instance of {1}.

Cause: Supplied class is not an instance of SessionFactory class.

Action: Check the adf-config.xml or service-config.xml configuration property "session.factory.class".
Level: 1

Type: ERROR

Impact: Other

WCS-04039: Session Manager instance creation failed for {0}

Cause: Either the required configuration is missing or class is not found..

Action: Check the class supplied is a valid class and its available in the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-04040: CacheFactory not specified.

Cause: CacheFactory instance is not found.

Action: Set appropriate CacheFactory instance on the Cache class.
Level: 1

Type: ERROR

Impact: Other

WCS-04041: No default or active connection available for: {0}

Cause: There is no default or active connection defined for this connection type.

Action: At least one connection must be defined default or active for this connection type.
Level: 1

Type: WARNING

Impact: Other

WCS-04042: Enterprise role not found: {0}.

Cause: Unable to find the enterprise role with the supplied name in the backend server.

Action: Check group with the given identity exists in the backend server.
Level: 1

Type: WARNING

Impact: Other

WCS-04043: Service is disabled for the current Portal: {0}.

Cause: Service is disabled for the current Portal.

Action: Enable this service or contact the Portal Moderator.
Level: 1

Type: WARNING

Impact: Other

WCS-04201: Error loading relationship service implementation

Cause: The relationship service encountered a problem while loading a relationship service implementation.

Action: Check the stack trace for more information
Level: 1

Type: ERROR

Impact: Other

WCS-04206: Error checking create permission

Cause: There was an error loading the relationship security provider.

Action: Check to make sure that the relationship security provider is properly configured.
Level: 1

Type: ERROR

Impact: Other

WCS-04207: Could not instantiate relationship repository

Cause: The relationship service encountered a problem while instantiating the repository.

Action: Check the stack trace for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-04208: jdbc/WebCenterDS data source not found: {0}

Cause: The jdbc/WebCenterDS data source could not be found.

Action: Ensure that the jdbc/WebCenterDS data source is created.
Level: 1

Type: WARNING

Impact: Other

WCS-04301: Relationship repository is not available.

Cause: An error was encountered while checking if the relationship repository was available.

Action: Check the log for errors that may have caused this.
Level: 1

Type: ERROR

Impact: Other

WCS-04302: Relationship already exists between [sourceApplicationId={0} sourceResourceId={1}] and [targetApplicationId={2} targetResourceId{3}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04303: Resource does not exist [applicationId={0} resourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04304: Target resource was not found [targetApplicationId={0} targetResourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04305: Relationship was marked as a bi-directional relationship, however no target to source back relationship was found for target [targetApplicationId={0} targetResourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04306: Source object was not found [sourceApplicationId={0} sourceResourceId={1}].

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04401: Exception during event or action

Cause: The relationship service encountered a problem while performing an event or action

Action: Check the application log for more information on the cause
Level: 1

Type: ERROR

Impact: Other

WCS-04403: Could not find relationship service {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04404: Service {0} threw exception for getViewObject() on RelatedObject {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04405: linksDetailedPanelWindow is null: cannot add partial target to RequestContext.

Cause: The relationship popup task flow is not included in the page.

Action: Check to make sure the relationship popup task flow is included in the page.
Level: 1

Type: WARNING

Impact: Other

WCS-04406: Cannot get current RichLinksDetailButtonRow. FacesContext.getCurrentInstance().getRenderKit() returned null for component: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04407: Exception while checking for existing links

Cause: An error was encountered while checking for existing links.

Action: Check the application log for more information on the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-04408: Error instantiating RichLinksDetailButtonRow

Cause: The relationship service encountered a problem while instantiating a custom component.

Action: Check the relationship links button component for valid attributes.
Level: 1

Type: ERROR

Impact: Other

WCS-04409: Error instantiating RichLinskDetailMenuItem

Cause: The relationship service encountered a problem while instantiating a custom component.

Action: Check the relationship links menu component for valid attributes.
Level: 1

Type: ERROR

Impact: Other

WCS-04410: Could not find Links Detail Popup in the LinksDetailBean bean

Cause: The relationship service encountered a problem while encoding the popup.

Action: Make sure the links popup task flow is included in the page.
Level: 1

Type: ERROR

Impact: Other

WCS-04412: Attribute value is null for component: {0}

Cause: A required attribute value is bound to a null value.

Action: Make sure the required attributes of this component are bound to non-null values.
Level: 1

Type: WARNING

Impact: Other

WCS-04413: An exception occurred while parsing parameter

Cause: A number format exception was encountered while parsing a parameter.

Action: Make sure the window width/height parameters for launching relationship views are valid numbers.
Level: 1

Type: WARNING

Impact: Other

WCS-04414: Got null from registry for service ID {0}, including all target services: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04415: Service {0} returned null for target view object with objectId: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-04417: Could not find {0} parameter for the Links Detail taskflow.

Cause: The parameter is required for processing links-detail task flow.

Action: Make sure the parameter is bound to a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-04418: User principal is null.

Cause: The user principal returned by the security context was null.

Action: Make sure security is property configured for the application.
Level: 1

Type: WARNING

Impact: Other

WCS-04419: Links components cannot render

Cause: The links-detail-popup task flow panelWindow was not found.

Action: Make sure the view includes the links-detail-popup task flow.
Level: 1

Type: WARNING

Impact: Other

WCS-04420: The image file {0} you tried to select was invalid. Provide a valid image file.

Cause: Unable to embed the image as the file is null or invalid.

Action: Select a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-04421: The taskflow id {0} was invalid. Provide a valid taskflow id.

Cause: Unable to retrieve the taskflow as the id is null or invalid.

Action: Specify a valid taskflow Id.
Level: 1

Type: ERROR

Impact: Other

WCS-04422: The NewRelatedObject returned from the service {0} was invalid.

Cause: Unable to process the returned object.

Action: Return a valid object for linking.
Level: 1

Type: ERROR

Impact: Other

WCS-04601: unexpected error

Cause: An unexpected error occurred for the RTC service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-04602: Unable to load RTC configuration

Cause: Connections context could not be acquired.

Action: Ensure that the connections.xml file is available and valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04603: Unable to load RTC configuration

Cause: No RTC (Real-Time Communication) connection was specified.

Action: Ensure that the property 'selected.connection' for the RTC service's 'service-config' element within the application's adf-config.xml file is available with a valid RTC connection name value.
Level: 1

Type: WARNING

Impact: Other

WCS-04604: Unable to lookup RTC connection {0}

Cause: The specified connection name either did not exist or did not resolve to a valid RTC connection.

Action: Ensure that the property 'selected.connection' for the RTC service's 'service-config' element within the application's adf-config.xml file contains a valid RTC connection name (as defined in the application's connections.xml file).
Level: 1

Type: WARNING

Impact: Other

WCS-04605: Unable to load RTC adapter {0}

Cause: The specified RTC adapter name was invalid.

Action: Ensure that the property 'adapter.name' of the RTC connection is valid and the corresponding adapter definition is available within the RTC 'service-config' element in the application's adf-config.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-04606: Unable to load RTC adapter {0}

Cause: The specified RTC adapter class does not extend from IMPConnection class.

Action: Ensure that the RTC adapter class extends IMPConnection class and follows its contract.
Level: 1

Type: WARNING

Impact: Other

WCS-04607: Unable to load RTC adapter {0}

Cause: The specified RTC adapter class could not be instantiated.

Action: Ensure that the RTC adapter class extends IMPConnection class and follows its contract.
Level: 1

Type: WARNING

Impact: Other

WCS-04608: Unable to load RTC adapter {0}

Cause: The RTC configuration object was null or invalid.

Action: Ensure that the RTC configuration is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04610: Unable to create instance of the UserManager implementation class {0}.

Cause: The specified user manager class could not be instantiated.

Action: Ensure that the class exists and can be instantiated with a default constructor.
Level: 1

Type: WARNING

Impact: Other

WCS-04611: Unable to find a valid RTC connection.

Cause: No RTC connections were found within the application's connections.xml file.

Action: Ensure that there is a valid RTC connection defined in the application's connections.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-04612: Invalid RTC address resolver specified: {0}

Cause: Specified address resolver was invalid.

Action: Ensure that the resolver type is one of DEFAULT, PROFILE_ATTRIBUTE, or CUSTOM.
Level: 1

Type: WARNING

Impact: Other

WCS-04614: Invalid attribute specified for PROFILE address resolver: {0}

Cause: The specified profile attribute for the address resolver was invalid.

Action: Ensure that the 'rtc.address.resolver.mapping' attribute is not null and contains a valid profile attribute.
Level: 1

Type: WARNING

Impact: Other

WCS-04615: Unable to load custom RTC address resolver: {0}

Cause: The custom class could not be initialized.

Action: Ensure that the custom class extends RtcAddressResolver and follows the contract specified by it.
Level: 1

Type: WARNING

Impact: Other

WCS-04616: Unable to load custom RTC address resolver: {0}

Cause: No custom class was specified for the CUSTOM type RTC address resolver.

Action: Ensure that the 'rtc.address.resolver.mapping' attribute is not null and contains a fully qualified and valid class name that extends from the RtcAddressResolver class.
Level: 1

Type: WARNING

Impact: Other

WCS-04619: The RTC address resolver supplied is invalid or null.

Cause: The RTC address resolver supplied was invalid or null.

Action: Ensure that 'rtc.address.resolver.mapping' attribute is not null.
Level: 1

Type: WARNING

Impact: Other

WCS-04620: The domain supplied is invalid or null.

Cause: The domain supplied was invalid or null.

Action: Ensure that the 'domain' attribute is not null or invalid.
Level: 1

Type: WARNING

Impact: Other

WCS-04621: Invalid timeout value specified: {0} Defaulting to {1}

Cause: The presence cache timeout value was either null or not a valid number.

Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.
Level: 1

Type: WARNING

Impact: Other

WCS-04625: Failed to instantiate IMPSession for the logged-in user.

Cause: The adapter class could not be instantiated.

Action: Ensure that the property 'adapter-class' has been defined for the adapter in the adf-config.xml and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-04701: Unable to load LCS adapter: base connection URL is missing.

Cause: The property 'base.connection.url' was missing.

Action: Ensure that the LCS connection entry contains the 'base.connection.url' property and points to a valid URL.
Level: 1

Type: ERROR

Impact: Other

WCS-04702: Unable to load LCS adapter: LCS PoolName is missing.

Cause: The property 'LCSPoolName' was missing.

Action: Ensure that the LCS connection entry in connections.xml contains the 'LCSPoolName' property and contains a valid LCS pool name.
Level: 1

Type: WARNING

Impact: Other

WCS-04703: Unable to perform operation {0}

Cause: Failed to perform the operation on remote Web service.

Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.
Level: 1

Type: ERROR

Impact: Other

WCS-04704: Failed to log on user {0}.

Cause: User login failed.

Action: Check user credentials and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-04705: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid LCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04706: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid LCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04707: Failed to add user {0} to the logged in user''s buddy list (logged in user:{1})

Cause: Failed to update buddy list of the user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04708: Failed to remove user {0} from the logged in user''s buddy list (logged in user:{1})

Cause: Failed to update buddy list of the user.

Action: Ensure that the server is up and responding.
Level: 1

Type: WARNING

Impact: Other

WCS-04709: Account field missing from user credentials

Cause: Can't login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04710: Connection not defined

Cause: Connection is not defined.

Action: Ensure that the connection is defined.
Level: 1

Type: WARNING

Impact: Other

WCS-04711: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04801: Invalid timeout value specified: {0} Defaulting to {1}

Cause: The presence cache timeout value was either null or not a valid number.

Action: Ensure that the 'rtc.cache.time' attribute is not null and contains a valid number.
Level: 1

Type: WARNING

Impact: Other

WCS-04804: Unable to acquire RTC connection for user {0}. RTCService running in dummy mode.

Cause: Exception caught while initializing IMPConnection.

Action: Check the log file for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-04805: Unable to acquire associated external application details.

Cause: The external application ID could not be loaded from the RTC connection configuration.

Action: Ensure that the 'ext.app.id' attribute is not null and refers to a valid external application ID.
Level: 1

Type: ERROR

Impact: Other

WCS-04806: Unable to acquire associated external application details.

Cause: The external application was not found for the external application ID.

Action: Ensure that external application ID refers to a valid external application.
Level: 1

Type: ERROR

Impact: Other

WCS-04851: Failed to generate endpoint to talk to OCS WebService.

Cause: The webservice is unreachable.

Action: Ensure that the OCS connection entry contains the 'base.connection.url' property and points to a valid URL.
Level: 1

Type: ERROR

Impact: Other

WCS-04852: Unable to perform operation {0}

Cause: Failed to perform the operation on remote Web service.

Action: Ensure that the RTC configuration is correct, the remote system is available, and the errors generated in the remote system's logs have been fixed.
Level: 1

Type: ERROR

Impact: Other

WCS-04853: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04854: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04855: Account field missing from user credentials

Cause: Cannot login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04856: Connection not defined

Cause: Connection is not defined.

Action: Ensure that the connection is defined.
Level: 1

Type: WARNING

Impact: Other

WCS-04857: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-04876: Exception caught while fetching buddy list for user {0}

Cause: Failed to retrieve buddy list from the Remote Service.

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04877: Exception caught while fetching presence information using user account {0}

Cause: Failed to fetch presence information from the remote service .

Action: Ensure that valid OCS connection entries have been supplied and the server is up.
Level: 1

Type: WARNING

Impact: Other

WCS-04878: Account field missing from user credentials

Cause: Can't login to server without the account information.

Action: Ensure that a valid sip address value is supplied as the Account in credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-04879: Failed to add users as buddies

Cause: Can't add users as buddies on beehive server.

Action: Ensure that valid admin details have been supplied in the connection.
Level: 1

Type: WARNING

Impact: Other

WCS-04901: Not initializing RtcAction {0} as it does not extend from RtcAction

Cause: Specified class does not extend from RtcAction.

Action: Ensure that the specified class is a proper subclass of RtcAction.
Level: 1

Type: WARNING

Impact: Other

WCS-04902: Failed to initialize RtcAction {0}

Cause: Unable to instantiate the supplied RtcAction subclass.

Action: Ensure that the specified class is a proper subclass of RtcAction, and provides a default constructor.
Level: 1

Type: WARNING

Impact: Other

WCS-04903: ADFConfig does not contain rtc-config details with namespace : {0}.

Cause: The RTC actions tag 'rtcC:actions' might be missing in ADFConfig.

Action: Ensure adf-config.xml file contains rtcC:actions tag.
Level: 1

Type: WARNING

Impact: Other

WCS-04904: Cannot process call request : User Profile for user {0} not found

Cause: User has selected PSTN call method but its profile cannot be found for the user to read the contact number.

Action: Ensure that the user profile exists in the system.
Level: 1

Type: WARNING

Impact: Other

WCS-04905: Cannot process call request : Contact information for user {0} not found

Cause: User has selected PSTN call method but has not supplied the correct ldap attribute to read the contact information.

Action: Ensure that correct ldap attribute has been supplied in connection/adf-config and its value has been set in the profile.
Level: 1

Type: WARNING

Impact: Other

WCS-04906: Cannot process call request : Incorrect call method supplied

Cause: User has supplied an incorrect call method.

Action: Ensure that correct call method is supplied. Refer to the documentation to find the supported call methods.
Level: 1

Type: WARNING

Impact: Other

WCS-04907: Cannot process call request : Call domain not specified in connection.

Cause: User has selected PSTN call method but has not supplied the call.domain property.

Action: Ensure that correct call.domain has been supplied in connection/adf-config.
Level: 1

Type: WARNING

Impact: Other

WCS-04908: Cannot process call request : User name is missing or not provided.

Cause: User name is missing or it has not been provided.

Action: Ensure that correct user name is provided, contact administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05001: Cannot retrieve the metadata for a portal

Cause: Unable to fetch the portal metadata due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05002: An error occurred while trying to get the ScopeAPI implementation for the service {0}.

Cause: Service {0} does not support provisioning.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05003: The service object passed to the wrapper is null.

Cause: A null service object was retrieved from the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05004: A portal template named {0} already exists.

Cause: Name specified for the portal template was not unique. A template with the same name already exists.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05005: Cannot create portal template

Cause: No name was provided for the portal template.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05006: Unable to retrieve information about {0}.

Cause: No portal template was found with the name specified.

Action: Provide the name of an existing portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05007: The reference to the portal template metadata {0} is invalid.

Cause: No portal template was found with the name specified.

Action: Provide the name of an existing portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05008: Unable to get mutable metadata for the portal template {0}

Cause: Some portion of the portal template metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05009: Metadata for the portal template {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05010: An error occurred reading or writing metadata of portal template {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05011: The commit operation failed due to a concurrent metadata change for portal template {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05012: Couldn''t retrieve the portal members email ids for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05013: Unable to execute portal related operation on {0}

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05014: Unable to get metadata for portal {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05015: Cannot create metadata for portal {0}

Cause: Metadata for the specified portal already exists.

Action: Provide a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-05018: The reference to the metadata of portal {0} is invalid.

Cause: The metadata reference was invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05019: Unable to get mutable metadata for portal {0}

Cause: Some portion of the portal metadata has already been modified.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05020: Metadata of portal {0} is invalid.

Cause: MDS reported a metadata validation error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05021: An error occurred reading or writing metadata of portal {0}.

Cause: MDS reported an IO error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05022: The commit operation failed due to a concurrent metadata change for portal {0}.

Cause: MDS reported a concurrent metadata change error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05023: Cannot retrieve a list of members for the current portal.

Cause: An error occurred trying to access the specified portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05025: Could not create portal {0} from portal template {1}.

Cause: An internal error occurred.

Action: Contact Administrator.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05026: Could not create portal template {1} from portal {0}.

Cause: Either the specified portal template already exists or the name was invalid.

Action: Provide a valid,unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05027: Unable to get preference metadata for portal {0}

Cause: Either the metadata does not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05035: Unexpected error in renaming portal from {0} to {1}. Contact administrator or try again after some time.

Cause: An invalid character was found in the name.

Action: Remove the invalid character(s) from the name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05036: A portal with the URL {0} already exists.

Cause: A portal with the specified URL exists.

Action: Specify a unique name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05037: The portal template name contains an invalid character {0}.

Cause: An invalid character was found in the portal template name.

Action: Remove the invalid character(s) from the portal template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05038: A portal template named {0} already exists.

Cause: A portal template with the specified name already exists.

Action: Specify a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05039: An error occurred attempting to save this portal as a portal template.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05040: The portal name contains one or more blank space characters.

Cause: A blank was found in the portal name. Blank spaces are not allowed.

Action: Remove all blank spaces from the portal name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05041: The portal template name contains one or more blank space characters.

Cause: A blank space was found in the name of the portal template. Blank spaces are not allowed.

Action: Remove all blank spaces from the portal template name and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05042: Unable to get metadata {1} for portal {0}.

Cause: Either the metadata did not exist, an invalid metadata reference was used or an attempt was made to get mutable metadata that has already been changed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05043: A portal with display name {0} already exists. It may be used as a hidden portal by other users.

Cause: A portal with the specified display name exists.

Action: Specify a unique display name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05047: Sending invitation to user(s) failed. The reason is : {0}.

Cause: Connection details for the BPEL server providing portal invitation services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal invitation services.
Level: 1

Type: ERROR

Impact: Other

WCS-05048: Unexpected error occurred while trying to invite user(s) to portal {0}

Cause: The BPEL server that provides the portal invitation service might have been down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05058: Cannot create policy store metadata for portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05059: Cannot save the changes

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05063: Cannot delete portal {0} due to unknown errors.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05065: Cannot not get the list of available services

Cause: No services were available in the service registry.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05066: An error occurred while attempting to unsubscribe a user from portal {0}.

Cause: The BPEL server supporting portal unsubscription may be down

Action: Ask your administrator to restart the BPEL server and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05067: Unable to send unsubscription request to moderator(s). The reason is : {0}.

Cause: Connection details for the BPEL server providing portal unsubscription services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05068: An error occurred attempting to unsubscribe user from portal {0}: {1}.

Cause: Connection details for the BPEL server providing portal unsubscription services were not available.

Action: Ask your administrator to configure a connection to the BPEL server providing portal unsubscription services.
Level: 1

Type: ERROR

Impact: Other

WCS-05069: Unable to send subscription notification to moderator(s). The reason is : {0}.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05070: An error occurred attempting to subscribe a user to portal{0}.

Cause: The BPEL server providing the portal subscription service may be down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05071: An error occurred attempting to subscribe user to portal {0}: {1}.

Cause: The BPEL server providing the portal subscription service may be down.

Action: Ask your administrator to restart the BPEL server, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05072: Error occurred while navigating to portal {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05073: Could not create portal with name {0}

Cause: The portal name provided could not be created.

Action: Please contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05074: An error occurred attempting to access a page of the renamed portal.

Cause: The portal rename operation was not successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05075: An error occurred attempting to rename a portal.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05077: Could not retrieve portal workflow configuration. Please contact administrator.

Cause: An error occurred attempting to retrieve the BPEL Several URL configured in connections.xml

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05078: Cannot delete workflow approval metadata from the portal

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05079: Cannot get the security handler for portal template {0}

Cause: The policy store metadata was not available for portal template security initialization.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05080: Cannot create the portal template {0}

Cause: The portal template was not created due to an error reported by the metadata store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05081: Unable to retrieve metadata object for portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05082: Adding workflow approval metadata to the portal failed

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05083: An error occurred attempting to rename portal {0} to {1}.

Cause: The portal rename operation was successful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05084: An unexpected error occurred attempting to delete portal {0}.

Cause: The portal delete operation was unsuccessful.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05085: Portal name cannot be null

Cause: Portal name was blank.

Action: Enter a valid alphanumeric name for the portal
Level: 1

Type: ERROR

Impact: Other

WCS-05086: Portal name is a reserved keyword.

Cause: The portal name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last, system.
Level: 1

Type: ERROR

Impact: Other

WCS-05087: The portal name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Portal name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the portal that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05088: Cannot delete the seeded portal template {0}

Cause: An attempt was made to delete a seeded portal template.

Action: Do not try to delete a seeded portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05089: Connection details for the BPEL server providing portal notification services are not available. Unable to send add or delete notifications to members of portal{0}

Cause: Connection details for the BPEL server providing portal invitation services were not available or configured incorrectly.

Action: Ask your administrator to configure a connection to the BPEL server providing portal notification services.
Level: 1

Type: ERROR

Impact: Other

WCS-05090: An error occurred attempting to send a notification to a member added to or deleted from portal {0}

Cause: An error occurred attempting to send a portal notification.

Action: Contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WCS-05091: Connection details for the BPEL server providing notification services in WebCenter Portal not found.

Cause: Connection details for the BPEL server providing notification services in WebCenter Portal were not available.

Action: Ask the administrator to configure a connection to the BPEL server providing notification services in WebCenter Portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05092: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05093: Portal template name cannot be null

Cause: No name was specified for the portal template.

Action: Specify a valid alphanumeric name for portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05094: Portal template name is a reserved keyword.

Cause: The template name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the template which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last
Level: 1

Type: ERROR

Impact: Other

WCS-05095: Template name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template name contains non-alphanumeric or space characters

Action: Specify a valid alphanumeric name for the template that only contains:a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05096: A portal template with name {0} already exists.

Cause: A portal template with the specified name exists.

Action: Specify a unique name.
Level: 1

Type: ERROR

Impact: Other

WCS-05097: Cannot upload portal icon

Cause: An error occurred while attempting to upload the file to WebCenter Portal

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05098: Cannot upload a portal logo

Cause: An error occurred attempting to upload the file to WebCenter Portal

Action: Try again or contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05099: Unable to set lock on portal {0}

Cause: A lock could not be acquired for this portal.

Action: Try again later.
Level: 1

Type: ERROR

Impact: Other

WCS-05100: Unable to execute operation on portal {0}

Cause: Portal {0} was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05101: Unable to execute portal operation

Cause: The portal was locked by some other operation.

Action: Wait for the first operation to complete and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-05102: Error creating portal {0} from portal template {1}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05103: Errors while renaming portal {0}

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05104: Unexpected error while trying to request change membership to portal {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the portal moderator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05105: Unexpected error while trying to send notification to user {0}

Cause: The BPEL server might have been down.

Action: Ensure BPEL server is up and retry. Contact the portal moderator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05106: Unexpected error creating region in cache

Cause: An attempt to create a region in the JOC (Java Object Cache) failed.

Action: Ensure that the JOC configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05107: Unexpected error getting object {0} from region {1} in cache

Cause: An attempt to retrieve an object from the cache failed.

Action: Ensure that the JOC configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05108: Search {0} for portal returned more than {2} results.

Cause: Search matched {1} results for portal template. The maximum number of result records allowed for this report is {1}.

Action: Restrict your query further, or use a different query.
Level: 1

Type: ERROR

Impact: Other

WCS-05109: Portal operation resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05111: Creating template resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05112: Fetching portal member count resulted in unexpected exception.

Cause: An internal error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05113: An error occurred while trying to provision the service {0}. The service did not get provisioned.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05114: An error occurred while trying to unprovision the service {0}. The service did not get unprovisioned.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05115: An error occurred while trying to determine the selected service.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05116: An error occurred while trying to process the service that was selected.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05117: An error occurred while trying to load the configuration screen for the selected service.

Cause: An unexpected error occurred.

Action: Reload the browser page, and if problem persists, contact the administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05118: Failed to delete portal {0} security metadata

Cause: Deletion of portal security metadata failed

Action: An unexpected error occurred while trying to deleting portal {0}. Please contact administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05119: An unexpected error occurred while trying to provision/unprovision services.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05120: An unexpected error occurred while trying to save the configuration for the service {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05121: An unexpected error occurred while trying to upload an image for portal {0}.

Cause: An unexpected error occurred during image upload.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05122: There was an error while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05123: Metadata Not Found Exception occurred while fetching the service config metadata for a portal {0}.

Cause: An unexpected error occurred while fetching the service config metadata for portal {0}

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05124: An exception occurred while fetching the Portal Manager for portal {0}.

Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05125: An exception occurred while fetching the Portal Manager for portal {0}.

Cause: An unexpected error occurred while fetching the Portal Manager for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05126: An exception occurred while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05127: An exception occurred while fetching the contacts list for portal {0}.

Cause: An unexpected error occurred fetching the contacts list for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05128: An exception occurred while fetching the GUID for portal {0}.

Cause: An unexpected error occurred while fetching the GUID for portal {0}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05129: Error occurred while launching the delete role confirmation.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05130: Error occurred while launching add/invite members table.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05131: Error occurred while getting the message for inviting non-members.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05132: Error occurred while performing operations on roles.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05133: Error occurred while adding custom attributes name={0} and value={1}.

Cause: An unexpected error occurred while adding the custom attributes.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05134: Error occurred while deleting the name={0} custom attribute

Cause: An unexpected error occurred while deleting the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05135: Error occurred while editing the custom attribute name={0} and value={1}.

Cause: An unexpected error occurred while editing the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05136: Error occurred while fetching the custom attributes for portal {0}.

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05137: No Such Attribute exists.

Cause: Unable to find the custom attributes

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05138: Unexpected error in getting the list of portals. You can try again later or contact Administrator.

Cause: Unexpected error in getting portals.

Action: Please contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05139: Unexpected error in retrieving portal {0}.

Cause: Unexpected error in retrieving the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05140: Unexpected error while rolling back the service {0}

Cause: Error in rolling back the service.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05141: Unknown errors creating portal. Please contact Administrator.

Cause: Post creating the portal, there were errors.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05142: Portal was created successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: List refresh failed after creating portal.

Action: Manually refresh the portal list.
Level: 1

Type: ERROR

Impact: Other

WCS-05143: Errors were encountered in creating portal. The main error is - {0}. You may want to delete the current portal if it is visible in your lists. Contact the administrator if the problem persists.

Cause: Errors were seen in post-processing the create portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05144: Errors were encountered while creating the portal. The main error is - {0}. Rollback of the creation also failed. You may want to clean the current portal if it is visible in your lists. You may want to try to create the portal again later or contact the administrator.

Cause: Error in post-processing the portal.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05145: Portal created with the following warning(s) : {0}

Cause: Portal was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05146: Unexpected errors in deleting the portal. Contact Administrator.

Cause: Unexpected error in deleting the portal.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05147: Deletion of the portal resulted in errors. The main error is - {0}. You may want to try deleting the portal again later. If the error persists, contact the administrator.

Cause: Delete of the portal resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05148: Deletion of portal resulted in errors. The main error is - {0}. Rollback of the deletion failed as well. You may want to try deleting the portal again later. If the error persists, contact the administrator.

Cause: Delete of the portal resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05149: Portal was deleted successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: List refresh failed after deleting portal.

Action: You can refresh the portal list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05150: Unexpected errors in renaming the portal. Contact Administrator.

Cause: Unknown errors in renaming the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05151: Rename of the portal resulted in errors. The main error is - {0}. You may want to try to rename the portal again later. If the error persists, contact the administrator.

Cause: Rename of the portal resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05152: Rename of the portal resulted in errors. The main error is - {0}. Rollback of renaming also failed. You may want to try to rename the portal again later or contact the administrator.

Cause: Portal was renamed but there were errors in processing.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05153: Portal was renamed successfully but refreshing the portal list failed. You may try to refresh the portal list manually.

Cause: Refreshing the list after renaming the portal failed.

Action: Manually refresh the list of portals.
Level: 1

Type: ERROR

Impact: Other

WCS-05154: Portal was renamed with warnings. These are some of the warnings - {0}.

Cause: Portal was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05155: Unexpected error in retrieving the portal list.

Cause: Unexpected error in retrieving the portal list.

Action: Try again after some time. If problem persist, contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05156: Unexpected error while provisioning some optional services in the portal. You may want to provision them again by going to portal Administration.

Cause: Unexpected error while provisioning some optional services in the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05157: Provisioning some optional services {0} in the portal did not go through successfully. You may want to provision them again by going to portal Administration.

Cause: Provisioning some optional services in the portal did not go through successfully.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05158: Unexpected error while unprovisioning the services.

Cause: Unexpected error in unprovisioning the services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05159: Portal was deleted with warnings. These are some of the warnings - {0}.

Cause: Portal was renamed with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05160: Unexpected errors while granting user access on new portal {0}. Please contact Administrator.

Cause: Unexpected errors while granting access on new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05161: Unexpected errors while removing access on new portal {0}. Please contact Administrator.

Cause: Unexpected errors while removing access on new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05162: Unknown error while removing access for portal {0}

Cause: Unexpected errors while removing access on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05163: Unknown error while mapping access for the new portal {0}

Cause: Unexpected errors while mapping access on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05164: Unexpected errors in provisioning services for new portal {0}

Cause: Unexpected errors in provisioning services for new portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05165: Unknown error while reprovisioning services since delete failed for portal {0}

Cause: Unexpected errors while reprovisioning services on portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05166: Unknown error while creating metadata for new template {0}

Cause: Unexpected errors while copying metadata from portal {0} to template {1}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05167: Unknown error in creating metadata for the new portal {0}

Cause: Unexpected errors while creating metadata for portal {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05168: Unknown error in renaming the portal.

Cause: Unexpected errors in renaming the portal.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05169: Unknown error in renaming services from portal {0} to portal {1}.

Cause: Unexpected errors in renaming the services.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05170: Updates or deletes are being performed on portal {0} by another moderator. Please try again after some time.

Cause: Portal {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05171: Error occurred while trying to determine if service {0} is provisioned in the current portal.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05172: The role {0} does not exist and hence could not be assigned to the user {1}.

Cause: Role {0} may have already been deleted .

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05173: Error occurred while trying to modify the role for user {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05174: Error occurred while accessing footer information.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05175: Portal {0} already exists.

Cause: Name specified for the portal was not unique. A portal with the same name already exists.

Action: Provide a unique name for the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05176: Portal name must contain at least one alphanumeric character

Cause: Portal name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-05177: Unable to perform the operation on the selected portal(s) due to unknown errors

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05178: Failed to refresh the portal list due to unknown errors

Cause: Unknown error occurred while trying to refresh the portal list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05179: Unable to perform the operation on the selected portal template(s) due to unavoidable errors

Cause: Selection of portal template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05180: An error occurred while trying to delete the portal template(s).

Cause: Selection of portal template(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05181: Error while creating portal

Cause: Error occurred during portal creation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05182: Error in closing the Create Portal dialog.

Cause: Error occurred while closing the Create Portal dialog

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05183: Another user is modifying the settings. Please try after some time.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05184: Unable to delete selected portal(s).

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05185: Unable to export selected portal(s) due to unknown errors

Cause: Selection of portal(s) failed

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05186: Error occurred while checking existing status of portal {0}.

Cause: An unexpected error occurred while checking existing status of the portal.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05187: Error occurred while retrieving portal {0} creation date

Cause: An unexpected error occurred while retrieving the portal creation date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05188: Error occurred while retrieving portal {0} status changed date.

Cause: An unexpected error occurred while retrieving the portal status changed date.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05189: Failed to validate the name/display name

Cause: Failed to validate the name/display name

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05190: An error occurred in post-processing the invite for {0} in portal {1}. Please contact Administrator.

Cause: Unable to cleanup invited status metadata

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05191: Unexpected error occurred while saving the portal changes.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05192: Unexpected error occurred while making portal public.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05193: Unexpected error retrieving data for the Portal Switcher.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05194: Portal template {0} based on portal {1} created successfully with the errors.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05195: Portal template {0} deletion failed due to concurrent operation performed on the same resource by some other user.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05197: Portal mail ID is not available because the Mail service is not configured.

Cause: Portal mail ID is not available because the Mail service is not configured.

Action: Contact the administrator to configure the Mail service.
Level: 1

Type: ERROR

Impact: Other

WCS-05198: Failed to initialize cache for portal template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05200: Failed to update cache for portal template {0}.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05201: Unknown error occurred while processing the templates.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05202: User was added but could not be notified due to some errors.

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05203: Template name must contain at least one alphanumeric character

Cause: Template name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for template name.
Level: 1

Type: ERROR

Impact: Other

WCS-05204: Portal display name cannot be null.

Cause: Portal display name was blank.

Action: Enter a valid alphanumeric name for the portal display name
Level: 1

Type: ERROR

Impact: Other

WCS-05205: Portal display name is a reserved keyword. One of: {0}

Cause: The portal display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: webcenter, pages, page, spaces, space, group, groups, space, spaces, webcenter space, webcenter spaces, webcenter Portal, WebCenter Portal, WebCenter Portal spaces, portal, webcenter administration, my spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05206: The portal name contains invalid characters.

Cause: Portal display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the portal display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05207: The portal name must contain at least one letter or number.

Cause: Portal display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05208: Select at least one portal to change state/status of portal.

Cause: No portal has been selected or changing the state.

Action: Select at least one portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05209: There are no templates available for creating the portal(s). You should refresh the list of templates by going to the Portal Templates page or create new templates or publish available templates if any to continue creating portal(s). If the problem persists, contact system administrator

Cause: No templates available for creating portal.

Action: Create new templates or publish existing templates if any.
Level: 1

Type: ERROR

Impact: Other

WCS-05210: Unknown error occurred while initiating creation of a portal.

Cause: Unable to launch the Create Portal dialog.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05211: Unknown error occurred while retrieving the list of templates.

Cause: Unknown error occurred while retrieving the list of templates.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05212: User {0} not authorized to perform the operation {1}:{2}

Cause: User {0} not authorized to perform the operation {1}:{2}

Action: User {0} not authorized to perform the operation {1}:{2}
Level: 1

Type: ERROR

Impact: Other

WCS-05213: Unexpected Error occurred while performing the method {0}. Contact system administrator.

Cause: Unexpected Error occurred while performing the method {0}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05214: Unable to retrieve information about {0} as another user is modifying the {0}. Please try again after some time.

Cause: Cannot retrieve metadata for portal {0} as another user is modifying the settings. Please try after some time.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05215: User(s) added successfully, but sending notification to the user(s) failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05216: User was removed successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05217: User role was modified successfully, but sending notification to the user failed

Cause: The BPEL server may be down.

Action: Ensure BPEL server is up and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-05218: Unknown error occurred while navigating to portal {0}.

Cause: Unable to navigate to the portal.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05219: Try accessing the portal from the Portal Switcher menu or the Portal page if the portal creation resulted in warnings. If the portal is not listed, refresh the list. If the portal is still not visible, report the error to your administrator. If the portal creation resulted in error, try deleting the portal if it is visible or else request the administrator to delete the portal

Cause: You can try accessing the portal from the Portal Switcher menu or the Portal page. If the portal is not listed, try refreshing the listing on the Portal page.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05220: Deletion or Rename is being performed on portal {0} by another Moderator. Refresh the list of portals and try again after some time.

Cause: Portal {0} is already being deleted or renamed.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05221: An unexpected error occurred while trying to delete portal template. Try again after some time. If the problem persists, contact administrator.

Cause: An unexpected error occurred while trying to delete portal template.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05222: Some optional services in the portal could not be provisioned as they were disabled. You may want to provision them again by going to portal Administration.

Cause: Unexpected error while provisioning some optional services in the portal.

Action: Contact Administrator and look in the logs for information about the specific service that has been disabled.
Level: 1

Type: ERROR

Impact: Other

WCS-05223: Admin Role does not exist in the policy store for portal {0}, so creating it

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05224: Unexpected error occurred while revoking portal public status.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05225: Cannot retrieve the portal distribution list for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05226: Cannot retrieve the portal moderators list for {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05227: Cannot retrieve the Webcenter Portal administrators list due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-05228: Unable to send change membership notification. The reason is : {0}.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05229: Cannot retrieve portal workflow configuration. Please contact your administrator.

Cause: The BPEL URL has not been configured yet.

Action: Notify your administrator that the BPEL service supporting portal subscription is not configured
Level: 1

Type: ERROR

Impact: Other

WCS-05230: An error occurred while searching invited user {0} in portal {1}. Contact your administrator.

Cause: Unable to search invited status metadata

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05231: Cannot retrieve user {0} email ID in portal {1} due to {2}

Cause: Failed to retrieve email id due to {2}

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05232: Template publishing role does not exist in the policy store for portal {0}, so creating it

Cause: Copy of the role failed, now trying to sanitize the portal security data

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05233: Sanitizing template {0} failed unable to copy the publish data

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05234: WebCenter Portal is not configured with BPEL server information.

Cause: BPEL server is not configured.

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05235: WebCenter Portal is not properly configured with the required BPEL server information.

Cause: BPEL server information is not correct.

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05236: BPEL server is either down or not properly configured.

Cause: Either the BPEL server is down or the portal workflows are not configured properly

Action: Contact your administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05237: Unexpected error occurred rebuilding the user portals list.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05238: Unexpected error occurred rebuilding the public portals list.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05239: Unable to retrieve portal tags.

Cause: An error occurred while trying to retrieve the tags for portal.

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05240: Unable to create portal tags.

Cause: An error occurred while trying to create the tags for portal.

Action: Please contact Administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-05241: Error occurred while getting portal activity streaming preferences.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05242: Error occurred while fetching the portal members information.

Cause: Error occurred while fetching the portal members information.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05243: Unexpected error deriving {0} list.

Cause: An unexpected error occurred.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05244: The member's current role is selected. If you want to change this member's role, choose another role from the list.

Cause: The new role is same as the old role.

Action: Select new role.
Level: 1

Type: ERROR

Impact: Other

WCS-05246: Unexpected error persisting portal information to tables

Cause: Error saving portal information to the database

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05247: Unable to retrieve mail ID for the portal.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05248: Unable to find security policy store metadata while creating portal template {0}

Cause: An error was detected in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05249: Unexpected error occurred fetching ratings table from repository.

Cause: An unexpected error occurred fetching the bulk ratings table from the repository.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05250: Unable to delete portal {0} as either it is being exported or imported. Please refresh the list portals list and try again later.

Cause: Attempt to delete portal {0} when the portal is being exported/imported.

Action: Try delete after sometime. Contact the administrator if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05251: Unable to delete the portal template {0} as either it is being exported or imported. Please refresh the portal templates list and try again later.

Cause: Attempt to delete portal template {0} when the portal is being exported/imported.

Action: Try delete after sometime. Contact the administrator if the problem persists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-05252: Unexpected error in getting information from users table

Cause: Error in getting information from the database

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05253: Role {1} of a user {0} is changed successfully to Role {2}, with failures in some of the services {3}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05254: Unexpected error occurred while refreshing the portal cache

Cause: Unexpected error occurred while refreshing the portal cache

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05255: Unexpected error occurred while cleaning up some of the permissions

Cause: Failed to clean up the policies post portal creation due to unexpected error

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-05256: Error while deleting security metadata for portal {0}.

Cause: An unexpected error occurred while deleting security metadata for portal. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-05267: Error while deleting security metadata for portal template {0}.

Cause: An unexpected error occurred while deleting security metadata for portal template. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-05268: Error occurred while fetching the portal data.

Cause: Error occurred while fetching the portal data.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05269: Error occurred while fetching the portal template data.

Cause: Error occurred while fetching the portal template data.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05270: You can add only a total of {0} items including subportals to the selected set. Remove items from selected set and try to add again.

Cause: Limit of selected set exceeded.

Action: Remove items from selected set and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05271: Please select one or more row to add.

Cause: No rows selected to add.

Action: Select one or more rows and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05272: Unexpected errors while granting user access on new portal template {0}. Please contact Administrator.

Cause: Unexpected errors while granting access on new group template : {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05273: Unknown error in removing access for the portal template {0}

Cause: Unexpected errors while removing access on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05274: Unable to find the security management lock for template {0}

Cause: Unable to find the security management lock for template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05275: Unexpected errors in provisioning services for new portal template {0}

Cause: Unexpected errors in provisioning services for new portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05276: Unknown error in reprovisioning services since delete failed for portal template {0}

Cause: Unexpected errors while reprovisioning services on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05277: Unknown error in mapping access for the new portal template {0}

Cause: Unexpected errors while mapping access on portal template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05278: Portal template {0} already exists.

Cause: Name specified for the portal template was not unique. A portal template with the same name already exists.

Action: Provide a unique name for the portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05279: Unexpected error while rolling back the template during {0}

Cause: Error in rolling back the plugin.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05280: Creation of portal template resulted in error. Rollback of the create template failed as well. The main error is - {0}. You may delete the template if it is available in the list as this template is in unusable state.

Cause: Error in rolling back the plugin.

Action: Try deleting this template if it is available on the Portale Templates page.
Level: 1

Type: ERROR

Impact: Other

WCS-05281: Rollback of portal template metadata also resulted in error. The main error is - {0}. Try deleting the template from the Portal Templates page if it is available as this template is in unusable state.

Cause: Error in deleting the template metadata.

Action: Try deleting this template if it is available on the Portal Templates page.
Level: 1

Type: ERROR

Impact: Other

WCS-05282: Unexpected errors in deleting the portal template. Contact Administrator.

Cause: Unexpected error in deleting the portal template.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05283: Deletion of the portal template resulted in errors. The main error is - {0}. You may want to try again later. If the error persists, contact the administrator.

Cause: Delete of the portal template resulted in error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05284: Deletion of portal template resulted in errors. Rollback of the deletion failed as well. The main error is -{0}. You may want to try again later. If the error persists, contact the administrator.

Cause: Delete of the portal template resulted in error.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05285: Portal template was deleted successfully but refreshing the portal template list failed. You may try to refresh the portal template list manually.

Cause: List refresh failed after deleting portal template.

Action: You can refresh the portal template list manually.
Level: 1

Type: ERROR

Impact: Other

WCS-05286: Updates or deletes are being performed on portal template {0} by another Moderator. Please try again after some time.

Cause: Portal template {0} is already being deleted.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05287: Unexpected errors occurred while creating template {0}.

Cause: Unexpected errors occurred while creating template.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05288: Creation of template resulted in errors. The main error is - {0}. Try again after some time or contact administrator

Cause: Template creation resulted in errors.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05289: Unexpected error occurred while executing pre portal template creation due to {0}.

Cause: Unexpected error occurred while executing pre portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05290: Base portal name cannot be null

Cause: Base portal name cannot be null

Action: Enter a value for base portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05291: Error occurred while executing custom pre portal creation code due to {0}.

Cause: Error occurred while executing custom pre portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05292: Error occurred while executing custom post portal creation code due to {0}.

Cause: Error occurred while executing custom post portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05293: Error occurred while executing custom pre portal deletion code due to {0}.

Cause: Error occurred while executing custom pre portal deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05294: Error occurred while executing custom post portal deletion code due to {0}.

Cause: Error occurred while executing custom post portal deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05295: Error occurred while executing custom pre portal rename code due to {0}.

Cause: Error occurred while executing custom pre portal rename due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05296: Error occurred while executing custom post portal rename code due to {0}.

Cause: Error occurred while executing custom post portal rename due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05297: Error occurred while executing custom pre portal template creation code due to {0}.

Cause: Error occurred while executing custom pre portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05298: Error occurred while executing custom post portal template creation code due to {0}.

Cause: Error occurred while executing custom post portal template creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05299: Portal template created with the following warning(s) : {0}

Cause: Portal was created with warnings.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05300: Error occurred while executing custom pre portal template deletion code due to {0}.

Cause: Error occurred while executing custom pre portal template deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05301: Error occurred while executing custom post portal template deletion code due to {0}.

Cause: Error occurred while executing custom post portal template deletion due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05302: Unexpected error occurred while executing pre portal creation due to {0}.

Cause: Unexpected error occurred while executing pre portal creation due to {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05303: Unable to add {0} as it conflicts with another portal on target application.

Cause: Conflict cannot be imported.

Action: Unselect the conflict row and add again.
Level: 1

Type: ERROR

Impact: Other

WCS-05309: Unexpected error occurred during updating template {0}

Cause: Unexpected error occurred during updating template {0}

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05310: Template Display Name is null

Cause: Template Display Name is null.

Action: Enter valid values.
Level: 1

Type: ERROR

Impact: Other

WCS-05311: Template display name is a reserved keyword. One of: {0}

Cause: The template display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the template display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05312: The template display name contains invalid characters. Only alphanumeric and space characters are allowed.

Cause: Template display name contained non-alphanumeric/space characters.

Action: Specify a valid alphanumeric name for the template display name that only contains a-z, A-Z, 0-9, _, or a space character
Level: 1

Type: ERROR

Impact: Other

WCS-05313: Portal display name must contain at least one alphanumeric character

Cause: Portal display name did not contain any alphanumeric characters

Action: Provide at least one alphanumeric character for portal display name.
Level: 1

Type: ERROR

Impact: Other

WCS-05314: Portal template with display name {0} already exists.

Cause: Portal template with display name {0} already exists.

Action: Enter another display Name.
Level: 1

Type: ERROR

Impact: Other

WCS-05315: Unexpected error occurred while fetching template displayName {0}.

Cause: Template with display name {0} already exists.

Action: Enter another display Name.
Level: 1

Type: ERROR

Impact: Other

WCS-05316: Unexpected error occurred while creating role {0} for template {1}

Cause: Unexpected error occurred while creating role {0} for template {1}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05317: Unexpected error occurred while saving members data from portal {0} to template {1}

Cause: Unexpected error occurred while saving members data from portal {0} to template {1}.

Action: Try again after some time or contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05318: Unexpected error occurred while copying member from template {0} to portal {1}

Cause: Unexpected error occurred while copying member {0} whose role {1} due to {3}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05325: Parent portal cannot be null

Cause: Parent portal was null.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05326: Failed to set parent portal

Cause: Error in setting parent portal

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05327: Unexpected error occurred while making the template {0} public.

Cause: Unexpected error occurred while making the template {0} public.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05328: Unexpected error occurred while fetching the templates.

Cause: UUnexpected error occurred while fetching the templates.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05329: Unexpected error occurred while deleting the template during overriding the template {0}.

Cause: Unexpected error occurred while deleting the template while overriding the template.

Action: Contact Administrator or Try again after some time
Level: 1

Type: ERROR

Impact: Other

WCS-05330: Unexpected error occurred while overriding the template {0}.

Cause: Unexpected error occurred while overriding the template.

Action: Contact Administrator or Try again after some time
Level: 1

Type: ERROR

Impact: Other

WCS-05331: Unexpected error occurred while saving the template permissions.

Cause: Unexpected error occurred while saving the template permissions.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05332: Unexpected error occurred while fetching the supported languages for this portal.

Cause: Unexpected error occurred while fetching the supported languages.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05333: Unexpected error occurred while launching the portal in edit mode.

Cause: Unexpected error occurred while launching the portal in edit mode.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05334: This operation is not possible on multiple portals. Select one portal to proceed with the operation.

Cause: Unable to perform the operation on multiple portals.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05335: Unexpected error occurred while launching the About Portal dialog.

Cause: Unexpected error occurred while launching the About Portal dialog.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05336: Portal not specified

Cause: The supplied portal name was null or blank.

Action: Specify a valid portal name that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-05337: Membership not changed for user {0}. You cannot manage your own membership.

Cause: Changing one's own membership in a portal is not allowed.

Action: Select users other than the current user to change their membership.
Level: 1

Type: WARNING

Impact: Other

WCS-05338: Unexpected error occurred while publishing portal template(s)

Cause: Unexpected error occurred while publishing portal template(s)

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05339: Unable to create portal as the template name is not specified.

Cause: Template is not selected.

Action: Select at least one template to create portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05340: Unknown errors occurred while saving the cache for portal {0}, try setting the values again in the portal administration settings.

Cause: Error while saving cache.

Action: Retry again from Settings screen.
Level: 1

Type: ERROR

Impact: Other

WCS-05341: Portal display name must be less than 200 characters.

Cause: Portal display name exceeded 200 characters.

Action: Specify portal display name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05342: Portal name must be less than 200 characters.

Cause: Portal name exceeded 200 characters.

Action: Specify portal name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05343: Portal template display name must be less than 200 characters.

Cause: Portal template display name exceeded 200 characters.

Action: Specify portal template display name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05344: Portal template name must be less than 200 characters.

Cause: Portal template name exceeded 200 characters.

Action: Specify portal template name less than 200 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05345: Keywords must be less than 4000 characters.

Cause: Keywords exceeded 4000 characters.

Action: Specify keywords less than 4000 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05346: Description must be less than 4000 characters.

Cause: Description exceeded 4000 characters.

Action: Specify description less than 4000 characters.
Level: 1

Type: ERROR

Impact: Other

WCS-05347: Select at least one portal to continue the operation.

Cause: Select at least one portal to continue.

Action: Select at least one portal to continue.
Level: 1

Type: ERROR

Impact: Other

WCS-05348: Unexpected error occurred while publishing following portal template(s) {0}

Cause: Unexpected error occurred while publishing following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05349: Unexpected error occurred while launching Rename dialog

Cause: Unexpected error occurred while launching Rename dialog

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05350: Unexpected error occurred while launching Set Access dialog

Cause: Unexpected error occurred while launching Set Access dialog

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05351: Unexpected error occurred while unpublishing portal template(s)

Cause: Unexpected error occurred while unpublishing portal template(s)

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05352: Unexpected error occurred while unpublishing following portal template(s) {0}

Cause: Unexpected error occurred while unpublishing following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05353: Select at least one portal to copy data to template.

Cause: Select at least one portal to copy data to template.

Action: Select at least one portal to copy data to template.
Level: 1

Type: ERROR

Impact: Other

WCS-05354: Portal template metadata {0} not found.

Cause: Portal template metadata not found.

Action: Portal template metadata not found.
Level: 1

Type: ERROR

Impact: Other

WCS-05355: Unable to set parent for one or more selected portal(s).

Cause: Failed to set parent for selected portal(s)

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05356: The new parent {0} specified cannot be a child portal in the hierarchy of {1}.

Cause: The new parent {0} is a child portal in the hierarchy of {1}.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05357: The new parent is one of the selected portals for reparenting. Choose a different parent

Cause: The new parent {0} is one of the selected portal for reparenting.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05358: The new parent and child portal cannot be same

Cause: The new parent and child portal specified are same.

Action: Choose a different parent portal
Level: 1

Type: ERROR

Impact: Other

WCS-05359: The URL contains invalid characters

Cause: Value entered in the url is not proper

Action: Only the following characters are allowed: A-Z, a-z, 0-9, _
Level: 1

Type: ERROR

Impact: Other

WCS-05360: The URL contains non-English characters

Cause: Non-ascii, multibyte characters entered in the pretty URL

Action: Only English names and ascii characters are supported
Level: 1

Type: ERROR

Impact: Other

WCS-05361: Error occurred while fetching the custom attributes

Cause: An unexpected error occurred while fetching the custom attribute.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05362: The archive that you are trying to import is not a valid {0} archive. Refer to the Spaces diagnostic log file for more information or contact your system administrator.

Cause: The supplied file to import was not a valid archive.

Action: Retry the import operation with a valid archive.
Level: 1

Type: ERROR

Impact: Other

WCS-05363: The URL contains invalid characters. Permitted characters: A-Z, a-z, 0-9, _

Cause: Value entered in the url is not proper

Action: Only the following characters are allowed: A-Z, a-z, 0-9, _
Level: 1

Type: ERROR

Impact: Other

WCS-05364: The portal template name contains non-English characters

Cause: Non-ascii, multibyte characters entered in the pretty URL

Action: Only English names and ascii characters are supported
Level: 1

Type: ERROR

Impact: Other

WCS-05365: Membership not changed for group {0}. You cannot manage the membership of this group because your own membership is granted through this group. Only direct members who have manage permission can manage the membership of groups.

Cause: Changing one's own membership in a portal is not allowed.

Action: Select users other than the current user to change their membership.
Level: 1

Type: WARNING

Impact: Other

WCS-05366: Unexpected error occurred while fetching list of all portals

Cause: Unexpected error occurred while fetching list of all portals

Action: Unexpected error occurred while fetching list of all portals
Level: 1

Type: ERROR

Impact: Other

WCS-05367: Unable to display the list of portals you have access on due to unexpected errors. Try again after some time or contact administrator if the problem persists.

Cause: Unexpected error occurred while fetching list of all portals

Action: Unexpected error occurred while fetching list of all portals
Level: 1

Type: ERROR

Impact: Other

WCS-05368: Portal GUID not specified

Cause: The supplied portal GUID was null or blank.

Action: Specify a valid portal GUID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-05369: Portal not found

Cause: The system could not find the specified portal.

Action: Specify a valid portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05370: Internal handler error

Cause: The internal handler for portal {0} failed.

Action: Refer to logs for more information and contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05371: The list of portal name passed was null

Cause: The list of portal names passed to fetch the metadata was empty.

Action: Pass a valid list of values.
Level: 1

Type: ERROR

Impact: Other

WCS-05372: The customizations available in portal template {1} were not copied to portal {0} since that process was interrupted.

Cause: Thread executing the customization document copy has been cancelled.

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05373: The customizations available in portal template {1} were not copied to portal {0} since that process has timed-out.

Cause: Thread executing the customization document copy has been timed out

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05374: The customizations available in portal template {1} were not copied to portal {0} due to unexpected errors.

Cause: Thread executing the customization document copy has failed to unexpected errors

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05375: The customizations available in portal {1} were not copied to portal template {0} since that process was interrupted.

Cause: Thread executing the customization document copy has been cancelled.

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05376: The customizations available in portal {1} were not copied to portal template {0} since that process has timed-out.

Cause: Thread executing the customization document copy has been timed out

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05377: The customizations available in portal {1} were not copied to portal template {0} due to unexpected.

Cause: Thread executing the customization document copy has failed to unexpected errors

Action: Retry this option using mds export/import wlst commands.
Level: 1

Type: ERROR

Impact: Other

WCS-05378: Unable to launch About Portal Template dialog.

Cause: Unable to launch About Portal Template dialog.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-05379: Unable to perform the operation on multiple portal templates.

Cause: Unable to perform the operation on multiple portal templates.

Action: Select a single portal template only and retry the operation
Level: 1

Type: ERROR

Impact: Other

WCS-05380: Select at least one portal template to continue the operation.

Cause: Select at least one portal template to continue.

Action: Select at least one portal template to continue.
Level: 1

Type: ERROR

Impact: Other

WCS-05381: User {0} does not have permission to view portal {1}.

Cause: User {0} does not have permission to view portal {1}.

Action: User {0} does not have permission to view portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05382: User {0} does not have permission to manage portal {1}.

Cause: User {0} does not have permission to manage portal {1}.

Action: User {0} does not have permission to manage portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05383: User {0} does not have the permission to create portal {1}.

Cause: User {0} does not have the permission to create the portal.

Action: User {0} does not have the permission to create the portal.
Level: 1

Type: ERROR

Impact: Other

WCS-05384: User {0} does not have the permission to view the portal template {1}.

Cause: User {0} does not have the permission to view the portal template {1}.

Action: User {0} does not have the permission to view the portal template {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05385: User {0} does not have permission to create portal template.

Cause: User {0} does not have permission to create portal template.

Action: User {0} does not have permission to create portal template.
Level: 1

Type: ERROR

Impact: Other

WCS-05386: User {0} does not have permission to manage portal template {1}.

Cause: User {0} does not have permission to manage portal template {1}.

Action: User {0} does not have permission to manage portal template {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05387: User {0} does not have permission to edit portal {1}.

Cause: User {0} does not have permission to edit portal {1}.

Action: User {0} does not have permission to edit portal {1}.
Level: 1

Type: ERROR

Impact: Other

WCS-05388: Unexpected error occurred while creating portal {0} from portal template {1}. Try again after some time. If the problem persists, contact Administrator

Cause: Unexpected error occurred while creating portal {0} from portal template {1}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05389: User {0} does not have permission to manage security of portal {1}.

Cause: User {0} does not have permission to manage security of portal {1}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05390: Unexpected error occurred while deleting portal {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: Unexpected error occurred while deleting portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05391: Unexpected error occurred while creating portal template {1} from portal {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: Unexpected error occurred while creating portal template {1} from portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05392: Unexpected error occurred while deleting portal template {0}. Try again after some time. If the problem persists, contact Administrator.

Cause: An unexpected error occurred while deleting portal template {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05393: User {0} is not authorized to refresh Portal cache.

Cause: User {0} is not authorized to refresh Portal cache.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05394: An unexpected error occurred while creating portal preference metadata.

Cause: An unexpected while creating portal preference metadata.

Action: Contact the administrator or try again later.
Level: 1

Type: ERROR

Impact: Other

WCS-05395: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.

Cause: User {0} does not have permission to view portal {0}, the portal is not discoverable, and self-subscription is not enabled.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05396: An unexpected error occurred while trying to drop the role {0} in portal {1}.

Cause: An unexpected error occurred while trying to drop the role {0} in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05397: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.

Cause: An unexpected error occurred while trying to set welcome message {0} for invited non-member in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05398: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.

Cause: An unexpected error occurred while trying to set welcome message {0} for invited member in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05399: An unexpected error occurred while trying to set add member message {0} in portal {1}.

Cause: An unexpected error occurred while trying to set add member message {0} in portal {1}.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05400: An unexpected error occurred while trying to get portal members.

Cause: An unexpected error occurred while trying to get portal members.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05401: Changing role for invited members, is not supported.

Cause: Changing role for invited members, is not supported.

Action: For changing the role of Invited Members, delete the existing invite for the member and invite the member again with the new role.
Level: 1

Type: WARNING

Impact: Other

WCS-05402: Unexpected error occurred while deleting the customization documents for portal {0}.

Cause: Unexpected error occurred while deleting the customization documents for portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05403: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.

Cause: Unexpected error occurred while getting Parent Display Name for portal {0} due to {1}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05404: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.

Cause: Unexpected error occurred while getting URL of parent portal for portal {0} due to {1}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05405: Unexpected error occurred while deleting the package containing assets for portal {0}.

Cause: Unexpected error occurred while deleting the package containing generic-site-resources documents for portal {0}.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05406: Unable to create portal as a portal with the URL or display name {0} already exists.

Cause: A portal with the specified URL or display name already exists.

Action: Specify a unique UURL or display name for the portal.
Level: 1

Type: WARNING

Impact: Other

WCS-05407: Unable to create portal as portal name is a reserved keyword. One of: {0}

Cause: The portal name specified was a reserved keyword.

Action: Specify a valid alphanumeric name for the portal which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05408: Unable to create portal as portal display name is a reserved keyword. One of: {0}

Cause: The portal display name specified was a reserved keyword

Action: Specify a valid alphanumeric name for the portal display name which excludes the following reserved keywords: webcenter, pages, page, Spaces, Space, group, groups, Space, Spaces, webcenter Space, webcenter Spaces, webcenter Portal, WebCenter Portal, WebCenter Portal Spaces, portal, webcenter administration, my Spaces, admin, last.
Level: 1

Type: ERROR

Impact: Other

WCS-05409: Simulated error condition during creation of portal {0} for internal test purposes.

Cause: Simulated error condition during creation of portal {0} for internal test purposes.

Action: This is just for negative tests.
Level: 1

Type: ERROR

Impact: Other

WCS-05410: Unexpected error occurred while deleting the portal template(s) {0}

Cause: Unexpected error occurred while deleting following portal template(s) {0}

Action: Contact Administrator or try again after some time.
Level: 1

Type: ERROR

Impact: Other

WCS-05411: Couldn''t get the first accessible page for portal {0} due to {1}.

Cause: Error in getting the first accessible page for the portal.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-05412: Unexpected error occurred in setting {0} as parent of portal {1} due to {2}.

Cause: Error in setting the parent portal.

Action: Contact the application administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05413: Unexpected error while setting the parent to {0} due to {1}.

Cause: Error in setting the parent and security parent for the scope

Action: Contact the application administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05414: User {0} is not authorized to generate Sitemaps for this site.

Cause: User {0} is not authorized to generate Sitemaps for this site.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05415: Unexpected error while getting the sitemap index.

Cause: Error in getting the sitemap index.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05416: Unexpected error while getting the sitemap for portal {0}.

Cause: Error in getting the portal sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05417: Unexpected error while generating the sitemap.

Cause: Error while generating the sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05418: Unexpected error while generating the sitemap for portal {0}.

Cause: Error while generating the portal sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05419: Unexpected error while updating the sitemap for portal {0}.

Cause: Error while updating the sitemap.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05420: Unexpected error occured while deleting the portal entry from default portal metadata due to {0}.

Cause: Error while deleting the portal from default portal metadta.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05421: Unexpected error occured while renaming the portal entry from default portal metadata due to {0}.

Cause: Error while renaming the portal from default portal metadta.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05422: Error fetching parent space for space {0} due to {1}

Cause: Error occured while fetching parent space.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05423: Unexpected error occured while fetching the moderator list for space{0} due to {1}

Cause: Error occured while fetching the list of moderators.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-05701: Deleting portal {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05702: Creating portal {0} failed

Cause: WebService API failed to execute create web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05703: An error occurred while revoking the roles {1} for users in portal {0}

Cause: WebService API failed to execute revoke role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05704: An error occurred while granting roles for {1} users in portal {0}

Cause: WebService API failed to execute grant role web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05705: Getting portal template {0} metadata failed

Cause: WebService API failed to execute get portal template metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05706: Getting portal metadata {0} failed

Cause: WebService API failed to execute get portal metadata web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05707: Getting portals for search string {0} failed

Cause: WebService API failed to execute get spaces web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05708: Getting portal templates for search string {0} failed

Cause: WebService API failed to execute get template web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05709: Setting the Custom Attributes for scope {0} failed

Cause: WebService API failed to execute Custom Attributes.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05710: An error occurred while attempting to retrieve spaces web service endpoint configured in connections.xml of caller application

Cause: Unable to retrieve spaces web service endpoint configured in caller applications connections.xml

Action: Please check spaces web service endpoint configured in connections.xml
Level: 1

Type: ERROR

Impact: Other

WCS-05711: One of the arguments passed to API call {0} is null

Cause: A null argument was passed to an API call

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05712: No portal name is provided

Cause: Portal name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05713: No portal template name is provided

Cause: Portal template name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05714: No portal user name is provided

Cause: Portal user name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05715: No portal role name is provided

Cause: Portal role name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05716: No portal custom attribute name is provided

Cause: Portal custom attribute name is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05717: No portal custom attribute value is provided

Cause: Portal custom attribute value is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05718: Error while setting the new end point for the space web services

Cause: Portal web services client already has an endpoint {0}

Action: It cannot be overridden at the run-time. Try setting it in connections.xml and restarting the application
Level: 1

Type: ERROR

Impact: Other

WCS-05719: Portal web service client is null

Cause: Portal web service client is null

Action: You need to set the context for the client and then initialize it
Level: 1

Type: ERROR

Impact: Other

WCS-05720: An unexpected error occurred while instantiating space web services client

Cause: Unable to create an instance of GroupSpaceWSClient

Action: Please verify the context parameters or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05721: An error occurred when user {0} tried to accept invite for portal {2} with role {1}

Cause: Failed to execute acceptance of portal invite

Action: Check the parameters being passed to the acceptInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05722: An error occurred when user {0} tried to reject the invite for portal {1}

Cause: Failed to execute rejection of portal invite

Action: Check the parameters being passed to the rejectInvite API or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05723: An error occurred while fetching the roles for portal {0}

Cause: An error occurred while fetching the roles for portal {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05724: An error occurred while inviting {0} members to portal {1}

Cause: An error occurred while inviting the members to portal {1}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05725: An error occurred while creating the portal template {0} based on portal {1}

Cause: An error occurred while creating the portal template {0}

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05726: An error occurred while fetching the roles for portal template {0}

Cause: An error occurred while fetching the roles for portal template {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05727: The Service ID {0}, is invalid.

Cause: An error occurred while fetching the RSS Feed URL for the Service ID, {0}.

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05728: An error occurred while checking if a login user {0} is a member of portal {1}

Cause: An error occurred while checking if a login user {1} is a member of portal {0}

Action: Contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-05729: Deleting portal template {0} failed

Cause: WebService API failed to execute deleting web service call.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05730: Search on portals for search string {0} failed

Cause: WebService API failed to execute search for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05731: Creation of role {0} failed in portal {1}

Cause: WebService API failed to execute create role for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05732: Dropping of role {0} failed in portal {1}

Cause: WebService API failed to execute drop role for portals.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05733: Failed to get role information for identity {0} in portal {1}

Cause: WebService API failed to get role information.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05734: Failed to get member information for portal {0}

Cause: WebService API failed to get member information.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05735: Search on portal templates for search string {0} failed

Cause: WebService API failed to execute search for portal template.

Action: Check the web service parameters, make sure the configuration is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05736: No image URL is provided

Cause: Image URL is not provided

Action: Ensure to invoke the API with non-null arguments
Level: 1

Type: ERROR

Impact: Other

WCS-05737: Unexpected error occurred in preparing image URL {0}

Cause: An error occurred in preparing image URL

Action: Make sure that the URL passed is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-05900: Unexpected error occurred while performing operation.

Cause: Error occurred due to unknown cause

Action: Try the operation again or contact oracle support
Level: 1

Type: ERROR

Impact: Other

WCS-06001: JCR session leak: leaked {0} sessions during {1} request to URI {2}.

Cause: JCR sessions have not been returned to the pool after the request ended.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-06002: Connection "{0}" is not a content repository connection.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06004: Error getting default IdcContext for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06005: Error getting admin IdcContext for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06006: Error getting IdcClient for connection "{0}": {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06007: Invalid maximum binary cache entry size: {0}. The value must be a number.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06008: The connection "{0}" is not an Oracle Content Server connection.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06009: There was an error looking up connection {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-06902: Incomplete repository connection, cannot login.

Cause: The repository configuration details are not valid and a classpath issue prevented the loading of the underlying JCR repository.

Action: Verify that all the configuration parameters are correct and check the message from the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-06905: Credentials for connection {0} not found using External Application Identifier {1}.

Cause: An attempt to fetch user credentials failed. User credentials may not have been provisioned or the external application configuration may be incorrect.

Action: Verify the external application configuration. If necessary, provision credentials for the user.
Level: 1

Type: WARNING

Impact: Other

WCS-06906: invalid credentials for connection {0} using External Application Identifier {1}

Cause: An attempt to log in using the provisioned credentials failed. The user's credentials for this connection might have been changed or the external application configuration might have been incorrect.

Action: If the provisioned credentials for the given user are not valid, then those credentials must be provisioned again. It might also be necessary to verify the external application configuration.
Level: 1

Type: WARNING

Impact: Other

WCS-06908: JCR Repository creation failure.{0}

Cause: A JCR repository instance could not be created from the parameters provided.

Action: Check the configuration parameters, and retry.
Level: 1

Type: WARNING

Impact: Other

WCS-06910: External Application Definition not found using External Application Identifier {0}

Cause: An attempt to fetch user credentials failed. The External Application ID is incorrect.

Action: Verify that the External Application definition has been created for this connection.
Level: 1

Type: WARNING

Impact: Other

WCS-06911: There is no authenticated user and PUBLIC credentials are not supported for External Application ID {0}.

Cause: An attempt to fetch credentials failed because there is not currently an authenticated user and the External Application ID does not support PUBLIC credentials.

Action: Use an External Application ID that supports PUBLIC credentials or authenticate so that no attempt to use PUBLIC credentials will occur.
Level: 1

Type: WARNING

Impact: Other

WCS-06912: There is no authenticated user and the PUBLIC credentials provisioned for External Application ID {0} are not valid.

Cause: An attempt to login using PUBLIC credentials failed because the provisioned PUBLIC credentials are not valid.

Action: Contact your system administrator and inform them that the PUBLIC credentials need to be updated or authenticate so that no attempt to utilize the PUBLIC credentials will occur.
Level: 1

Type: WARNING

Impact: Other

WCS-06913: The SHARED credentials provisioned for External Application ID {0} are not valid.

Cause: An attempt to login using SHARED credentials failed because the provisioned SHARED credentials are not valid.

Action: Contact your system administrator and inform them that the SHARED credentials need to be updated.
Level: 1

Type: WARNING

Impact: Other

WCS-07001: severe internal error

Cause: An irrecoverable internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07002: error obtaining Documents service ADF configuration

Cause: An error occurred while obtaining or interpreting the DocLib section of ADF configuration.

Action: Verify that the Documents service section of the ADF configuration is present, complete, and contains valid data.
Level: 1

Type: WARNING

Impact: Other

WCS-07003: error obtaining content repository connection

Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid entry for the content repository connection.
Level: 1

Type: WARNING

Impact: Other

WCS-07004: content repository login failure

Cause: The attempt to log on to the content repository failed.

Action: Make sure the credentials used are valid.
Level: 1

Type: WARNING

Impact: Other

WCS-07005: JCR error connecting to content repository

Cause: A JCR repository exception (other than login) occurred.

Action: Use the associated JCR exception text to diagnose the problem.
Level: 1

Type: WARNING

Impact: Other

WCS-07006: run-time error obtaining content repository

Cause: An unexpected run-time exception occurred.

Action: Use the associated run-time exception text to diagnose the problem.
Level: 1

Type: WARNING

Impact: Other

WCS-07007: cannot list items in directory {0}

Cause: An error occurred while trying to list the items in the specified folder.

Action: Make sure that the content repository connection is accessible and that the specified folder exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07008: cannot get breadcrumbs for directory {0}

Cause: An error occurred while trying to list the breadcrumbs items for the specified folder.

Action: Make sure that the content repository connection is accessible and that the specified folder exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07010: error listing folder {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07011: The Rich Text Editor could not load the target document, it may have been deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07012: The Rich Text Editor could not load the destination folder, it may have been deleted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07013: No content repository connection with the name "{0}" can be found.

Cause: A JNDI Name Not Found Exception occurred while attempting to obtain the content repository connection.

Action: Verify connections.xml contains an entry for the specified content repository connection name.
Level: 1

Type: WARNING

Impact: Other

WCS-07014: An attempt to log on to the content repository did not complete within the allotted time.

Cause: The content repository may have been slowed by heavy loads or network congestion.

Action: Wait a while, and then retry. Optionally, ask the system administrator to allocate more resources for the content repository or to lengthen the timeout period.
Level: 1

Type: WARNING

Impact: Other

WCS-07015: An attempt to log on to the content repository did not succeed because the Documents service is disabled.

Cause: Login failed because the Documents service was disabled. Another login was still executing, exceeding its allotted timeout period.

Action: Wait a while, and then retry. Optionally, ask the system administrator to allocate more resources for the content repository or to lengthen the timeout period.
Level: 1

Type: WARNING

Impact: Other

WCS-07016: Cannot get the user name for the selected user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07017: The target Content Server does not support the following query used to retrieve recent documents: {0}.

Cause: Required components may not have been installed or properly configured.

Action: Check the Content Server installation guide for WebCenter for details on required components and their configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-07018: An error occurred while trying to convert the following object from {0} to {1}: {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07019: Cannot create folder "{0}" in "{1}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07020: Error refreshing the JCR session.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07021: The transferable object contains no usable data.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07022: After fail-over, failed to get the item {0} from the repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07023: Please refresh to see the latest content (View > Refresh Content).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07024: Please refresh to see the latest content (View > Refresh Content). You may need to navigate up the folder hierarchy before refreshing.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07025: Unable to rename the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07026: Unable to perform the operation. The document or folder may have been deleted or you do not have permission.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07027: An error occurred performing post operation refreshing. The current document or folder may have been deleted or you do not have permission.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07028: The folder being renamed no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07029: Unable to checkout {0}. This document is already checked out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07030: Unable to perform the current operation.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07031: Unable to delete selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07032: Unable to rename the selected folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07033: Unable to create folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07034: Unable to display folder properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07035: Unable to create new HTML document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07036: Unable to upload the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07037: Unable to edit the HTML document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07038: Unable to display document properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07039: Unable to display folder properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07040: Unable to save folder properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07041: Unable to check in the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07042: Unable to check out the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07043: Unable to cancel the document check-out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07044: Unable to view version history for the document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07045: Unable to copy selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07046: Unable to paste selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07047: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07048: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07049: You do not have permission.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07050: The folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07051: The selected documents or folders no longer exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07052: The document no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07053: The parent folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07054: The document or folder being copied/moved no longer exists or the target folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07055: The parent folder is currently unavailable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07056: One or more of the selected documents or folders no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07057: The document being renamed no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07058: The document or folder no longer exists.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07059: The maximum number of folders stored within a folder has been reached. Contact your systems administrator.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07060: The maximum number of documents stored within a folder has been reached. Contact your systems administrator.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07061: The document is checked out by another user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07062: The document is checked out by user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07063: The document is not checked out.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07064: An unknown error occurred in the Oracle Content Server.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07065: The selected document or folder or its parent folder may have been deleted or your permissions may have been revoked.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07066: Unable to move selected documents or folders.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07067: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07068: A document or folder with the same name exists in this folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07069: The folder name contains an invalid character.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07070: The folder name is too long.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07071: Unable to save document properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07072: The destination cannot be a child folder of the source folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07073: Unable to display item properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07074: Unable to save item properties.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07075: No transfer data found for data flavor {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07076: No value found for task flow parameter {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07077: An error occurred while adding the content presenter task flow to the page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07078: The class method ''{0}.{1}'' cannot be called with a null or empty argument ''{2}''.

Cause: The specified method call cannot be called with the specified argument with value of null.

Action: Ensure the specified argument has a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-07079: Datasource type ''{0}'' was expected but found ''{1}''.

Cause: The configured datasource type did not match the expected datasource type.

Action: Correct the presenter configuration to the expected datasource type.
Level: 1

Type: ERROR

Impact: Other

WCS-07080: Error retrieving node(s).

Cause: An error was encountered retrieving node(s).

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07081: Error saving Content Presenter Configuration.

Cause: An error was encountered saving the specified configuration document.

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07082: Query expression must be a valid, non-empty expression.

Cause: The specified query expression was invalid.

Action: Review the specified query expression and correct it.
Level: 1

Type: ERROR

Impact: Other

WCS-07083: The datasource type ''{0}'' requires ''{1}'' to be set.

Cause: The specified datasource type is not consistent with the datasource state.

Action: Specific datasource types require different parameters to be set. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07084: Invalid datasource type ''{0}''. Valid datasource types:{1}.

Cause: The specified datasource type was invalid.

Action: Correct the specified datasource type to one of the examples provided in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-07085: The configuration {0} is required.

Cause: You have not specified the mentioned configuration item.

Action: Make sure the mentioned configuration item is provided for this presenter instance.
Level: 1

Type: ERROR

Impact: Other

WCS-07086: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).

Cause: You have not specified the page size and maximum results.

Action: Correct the page size and maximum results.
Level: 1

Type: ERROR

Impact: Other

WCS-07087: Error loading task-flow instance configuration

Cause: An error occurred while loading the task-flow instance configuration.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07088: Error saving task-flow instance configuration

Cause: An error occurred while saving the task-flow instance configuration.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07089: Unable to save presenter configuration data.

Cause: An error occurred while saving the presenter configuration data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07090: Unable to retrieve presenter configuration data.

Cause: An error occurred while retrieving the presenter configuration data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07091: Unable to retrieve presenter template data.

Cause: An error occurred while retrieving the presenter template data.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07092: An error occurred while running the query.

Cause: An error occurred while previewing the query.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07093: An error occurred while retrieving the node.

Cause: An error occurred while retrieving the node.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07094: Maximum results (current:{0}) must be an integer between {1} and {2}.

Cause: The value you have specified for maximum results must inclusively be between the range specified.

Action: Correct the maximum results to be inclusively be between the specified range.
Level: 1

Type: ERROR

Impact: Other

WCS-07095: An error occurred while running the query.

Cause: A general repository exception has occurred.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07096: Unable to retrieve properties for the specified item.

Cause: An error occurred while retrieving properties for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07097: Unable to retrieve markup for the specified item: {0}

Cause: An error occurred while retrieving markup for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07098: Unable to delete the selected version.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07099: Unable to retrieve workflow approvers for the specified item: {0}

Cause: An error occurred while retrieving workstate approvers for the specified item.

Action: Check the base exception for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07100: Oracle Content Server error: {0}

Cause: An unexpected error occurred in the Oracle Content Server.

Action: Check the Oracle Content Server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07101: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07102: Repository error

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07103: Unsupported repository operation

Cause: The Documents service tried to invoke an operation that is not supported by the underlying document repository.

Action: Avoid this operation with this repository.
Level: 1

Type: WARNING

Impact: Other

WCS-07104: Access Denied

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07105: Versioning is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07106: Locking is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07107: The recent documents query is not supported on this repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07108: Repository error: {0}

Cause: An unexpected error occurred in the content repository.

Action: Check the base exception and repository's log for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-07201: Unable to approve the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07202: Unable to reject the selected document.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07203: Error initializing the user security cache.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07204: Unable to create new wiki page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07205: Unable to find parent folder.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07206: parent folder is not set.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07207: Could not retrieve links count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07208: Could not retrieve tags count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07209: Could not retrieve comments count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07210: Could not retrieve likes count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07211: Could not retrieve likes/comments count for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07212: Error trying to retrieve spaces page for resource {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07213: Could not set the security on the folder or document.

Cause: An error occurred while trying to update the item's security.

Action: Review the associated error messages.
Level: 1

Type: WARNING

Impact: Other

WCS-07214: The Scenario datasource was not constructed correctly

Cause: Either the conductor or the scenario have not be set correctly.

Action: Review the specified conductor service and scenario configurations to make sure they are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-07215: Failed to get UCM configuration settings.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07216: The workflow settings could not be saved as there are too many approvers. Please reduce the number of approvers.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07217: Unable to add the following approvers to the workflow, the approvers username limit has been reached.{0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07218: Unknown error while retrieving recent documents

Cause: An unknown error occurred while querying for recent documents.

Action: Check the underlying exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07219: Invalid parameter combination: the connection name specified by resourceId = {0} is not the same as specified in parameter connectionName = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07220: Invalid parameter combination: the item identified by resourceId = {0} is not a child of startFolderPath = {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07221: {0} is not a valid resource identifier.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07222: The item with resourceId = {0} does not exist or is not accessible.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07223: Invalid content id ''{0}'' for datasource type ''{1}''.

Cause: The specified content id was invalid.

Action: Correct the specified content id to a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-07225: The object is not a Document Library resource.

Cause: An unexpected condition has occurred.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07226: Failed to set ACL on content item as item ACL has been changed concurrently.

Cause: The attempt to change the security settings has failed because the settings have already been changed by another user.

Action: Re-try the operation against the refreshed view of the item's security policy.
Level: 1

Type: ERROR

Impact: Other

WCS-07227: Modifications to an item's security policy are not supported.

Cause: An attempt has been made to modify an item's security policy.

Action: An item's security policy must be updated entirely and not partially.
Level: 1

Type: ERROR

Impact: Other

WCS-07228: Failed to set ACL on content item {0}.

Cause: The attempt to set ACL security on an Oracle Content Server repository item has failed.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07229: Failed to restore content item {0} for security settings.

Cause: The attempt to restore a content item from its identifier has failed.

Action: Retry the security settings operation.
Level: 1

Type: ERROR

Impact: Other

WCS-07230: Determining if Content Server is configured to support item level security failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07231: Determining if Content Server is configured to support Slide Previewer failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07232: Error discovering if user has admin access to file or folder.

Cause: An error occurred when trying to discover if the current user has admin capabilities for the file or folder.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07233: Cannot perform action, item is in a workflow.

Cause: An action is being attempted on a document which is in a workflow.

Action: Retry the action, when the workflow is complete.
Level: 1

Type: WARNING

Impact: Other

WCS-07234: Fetching Workflow data from Content Server failed.

Cause: An error occurred while getting workflow information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07235: No connection specified for Documents to use.

Cause: An attempt was made to use Documents without explicitly specifying a connection or configuring a primary connection.

Action: Either explicitly supply Documents with a connection or specify a primary connection in the ADF configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-07237: Determining if Content Server is configured with AutoVue failed.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07238: Unexpected exception: {0}

Cause: An unexpected exception occurred.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07239: Unexpected error

Cause: An unexpected error occurred.

Action: Check the server logs for details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-07240: Unsupported resource type

Cause: The Documents service tried to perform an operation on a resource but failed to do so because the resource type was not recognized.

Action: Avoid this operation with this particular type of resource.
Level: 1

Type: WARNING

Impact: Other

WCS-07241: Renaming the root folder is not allowed.

Cause: An attempt was made to rename the root folder.

Action: Avoid the rename operation with the root folder.
Level: 1

Type: WARNING

Impact: Other

WCS-07242: Error reading the document's content.

Cause: The document's content could not be accessed.

Action: Verify that the document is available.
Level: 1

Type: WARNING

Impact: Other

WCS-07243: Error performing paste.

Cause: An error prevented the items from being pasted at the destination folder.

Action: Verify that the destination folder still exists, is writable, and no items with the same names exist there.
Level: 1

Type: ERROR

Impact: Other

WCS-07244: When searching between dates, if the dates are not specified in ascending order, the search may not return any results.

Cause: The begin and end dates have been specified in the wrong order.

Action: Specify the dates in ascending order.
Level: 1

Type: WARNING

Impact: Other

WCS-07245: Operation not allowed on Public folders.

Cause: An attempt has been made to perform an illegal operation on a Public folder.

Action: Do not select a Public folder when performing operations such as delete and rename. If performing a copy or move operation then select item(s) inside the Public folder, not the Public folder itself.
Level: 1

Type: ERROR

Impact: Other

WCS-07246: Approver list is too large for current workflow.

Cause: Unable to save the set of approvers for the workflow as the usernames exceed the 255 character limit.

Action: Reduce the approvers for the workflow.
Level: 1

Type: ERROR

Impact: Other

WCS-07247: Could not list the items in a folder;

Cause: An error occurred while trying to list the items in a folder.

Action: Make sure that the content repository connection is accessible and that the folder exists. Navigate to another folder in the hierarchy.
Level: 1

Type: WARNING

Impact: Other

WCS-07248: Unable to open the editor.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07249: Could not connect to the content repository.

Cause: A error occurred while trying to connect to the content repository.

Action: Make sure that the content repository is running and accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-07250: Provisioning of the Documents service failed.

Cause: An error occurred while trying to provision the Documents service.

Action: Make sure that the content repository connection is accessible. Check the Oracle Content Server logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07251: The item may have been deleted or has already been approved or rejected.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07252: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07253: Unexpected error evaluating property ''{0}'' of base {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-07254: Click the blog name in the banner to refresh with the latest content.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07501: There is no role matching the given ID: {0}.

Cause: The application attempted to look up a service role with an invalid role ID.

Action: Ensure that your application uses a valid service role ID.
Level: 1

Type: ERROR

Impact: Other

WCS-07502: Cannot grant super administrator role for scope {1}.

Cause: Could not grant the super administrator role to the scope. The super administrator role can only be granted to the default scope; other roles must be granted on a portal scope.

Action: Verify that the role mapping is correctly defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07503: Cannot log on to the content repository.

Cause: The username and password used for the current login were not correct.

Action: Check the username and password.
Level: 1

Type: WARNING

Impact: Other

WCS-07504: There was an unknown content repository exception.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07505: The repository login was interrupted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07601: Unable to read document metadata (''{0}'',''{1}'').

Cause: Generally caused by a malformed xml document.

Action: Check the specified xml document for errors.
Level: 1

Type: ERROR

Impact: Other

WCS-07602: Document metadata (''{0}'',''{1}'') is expected to be of type ''{2}'', but found ''{3}''.

Cause: Generally caused by a malformed xml document with an incorrect namespace.

Action: Check the specified xml document and make sure the xmlns attribute is set to 'http://xmlns.oracle.com/webcenter/content/templates/registry'.
Level: 1

Type: ERROR

Impact: Other

WCS-07603: No content list template or content template found in registry(''{0}'',''{1}'').

Cause: Generally caused by an empty display template descriptor.

Action: Check the specified xml document and make sure that either content-templates or content-list-templates are defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07604: Default template view named ''{0}'' not found for content type ''{1}''.

Cause: A content type has been configured in the template registry with a default template that has not been found.

Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the content type.
Level: 1

Type: ERROR

Impact: Other

WCS-07605: There are duplicate template categories with id ''{0}''.

Cause: There are duplicate template categories that are defined with the specified id.

Action: Check the template registry document and make sure and change the name of the specified template category.
Level: 1

Type: ERROR

Impact: Other

WCS-07606: There are duplicate content types by name ''{0}''.

Cause: There are duplicate content types that are defined with the specified name.

Action: Check the template registry document and make sure and change the name of the specified content type.
Level: 1

Type: ERROR

Impact: Other

WCS-07607: There are duplicate content repositories by name ''{0}'' and type ''{1}''.

Cause: There are duplicate content repositories that are defined with the specified name.

Action: Check the template registry document and make sure and change the name of the specified content repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07608: There are duplicate template views by id ''{0}''.

Cause: There are duplicate template views that are defined with the specified id.

Action: Check the template registry document and make sure and change the id of the specified template view.
Level: 1

Type: ERROR

Impact: Other

WCS-07609: The class method ''{0}.{1}'' cannot be called with a null argument ''{2}''.

Cause: The specified method call cannot be called with the specified argument with value of null.

Action: Ensure the specified argument has a non-null value.
Level: 1

Type: ERROR

Impact: Other

WCS-07610: Unable to locate resource key ''{0}'' in bundle ''{1}''.

Cause: The display template registry is configured with a resource bundle and key that is unable to be found.

Action: Check the specified resource bundle and ensure that the specified key exists.
Level: 1

Type: WARNING

Impact: Other

WCS-07611: No template category defined by id ''{0}''.

Cause: The display template registry does not contain a category configuration by the specified id.

Action: Add the specified category id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07612: No template view defined by id ''{0}''.

Cause: The display template registry does not contain a template configuration by the specified id.

Action: Add the specified template id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07613: No template registry found in application.

Cause: The display template registry does not exist or cannot be found.

Action: Check application configuration and ensure registry is properly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-07614: Default template view named ''{0}'' not found in template category ''{1}''.

Cause: A category has been configured in the template registry with a default template view that has not been found.

Action: Check the specified xml document and make sure a template view exists with the id of the defaultView specified on the category.
Level: 1

Type: ERROR

Impact: Other

WCS-07615: Default category named ''{0}'' not found in the registry.

Cause: A default category has been configured in the template registry that has not been found.

Action: Check the specified xml document and make sure a the default category has been defined.
Level: 1

Type: ERROR

Impact: Other

WCS-07616: No template view defined by id ''{0}'' and category ''{1}''.

Cause: The display template registry does not contain a template configuration by the specified category and view.

Action: Add the specified template id to the template registry.
Level: 1

Type: WARNING

Impact: Other

WCS-07617: A general display template error has occurred.

Cause: An unexpected exception has occurred processing the display template registry.

Action: Review the original stacktrace cause for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07618: No default template view specified for category id ''{0}''. Returning the default view for the default category.

Cause: The specified category in the template registry is not configured with a default view, but has been referenced using the default behavior.

Action: Update the specified category in the template registry to configure a default view.
Level: 1

Type: WARNING

Impact: Other

WCS-07619: Invalid configuration for category id ''{0}''. Could not find view defined for view id ''{1}''.

Cause: The specified category in the template registry is configured with no default templates.

Action: Update the registry to only include a single default template for the category.
Level: 1

Type: WARNING

Impact: Other

WCS-07620: Invalid configuration for category id ''{0}''. Multiple templates found for view id ''{1}''.

Cause: The specified category in the template registry is configured with multiple templates.

Action: Update the registry to only include a single template for the category and view id combination.
Level: 1

Type: WARNING

Impact: Other

WCS-07621: Invalid configuration for content type name ''{0}'' in repository name ''{1}'' configuration.

Cause: The specified category in the template registry is configured with no default templates.

Action: Update the registry to only include a single default template for the category.
Level: 1

Type: WARNING

Impact: Other

WCS-07622: Invalid configuration for content type name ''{0}'' in repository ''{1}''. Multiple default templates found.

Cause: The specified category in the template registry is configured with multiple templates.

Action: Update the registry to only include a single template for the category and view id combination.
Level: 1

Type: WARNING

Impact: Other

WCS-07701: severe internal error while getting the template view ID

Cause: An irrecoverable internal error has occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-07702: Error while getting the template view ID

Cause: An error occurred while determining the template for a node.

Action: Check the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07703: No request dispatcher for template viewID {0} located at {1}

Cause: An error occurred while trying to dispatch the request to the template. The target template may not exist.

Action: Check that the target template exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07704: Error processing the display template include for template viewID {0} located at {1}

Cause: An error occurred while processing the template include. This may result from a syntax or logic error in the template code.

Action: Check the underlying exception for the details of the error.
Level: 1

Type: ERROR

Impact: Other

WCS-07710: Error while getting the template view ID because of null node or view, node: {0}, view: {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07712: Error setting up context for template. {0}

Cause: An error occurred while trying to setup the context for the template.

Action: Check the underlying error.
Level: 1

Type: ERROR

Impact: Other

WCS-07713: Internal error: illegal reentrant use of template context.

Cause: An internal error was detected, attempted reentrant use of template context.

Action: Contact your Oracle Support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07714: Error tearing down context for template. {0}

Cause: An error occurred while trying to teardown the context for the template.

Action: Check the underlying error.
Level: 1

Type: WARNING

Impact: Other

WCS-07715: Error popping context, found another template context. {0}. {1}.

Cause: An error occurred while trying to pop the context, found another template context.

Action: Contact your Orale support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07716: Error popping context, found another context. {0}.

Cause: An error occurred while trying to pop the context, found another context.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07717: Error while invoking component.

Cause: An error occurred while invoking the template component.

Action: Check the underlying exception.
Level: 1

Type: WARNING

Impact: Other

WCS-07718: Error when resuming context: no queued context to resume.

Cause: Template context cannot be resumed, as context queue is empty.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07719: Error when resuming context: no context to resume.

Cause: Template context cannot be resumed, as there is no context to resume.

Action: Contact your Oracle support representative.
Level: 1

Type: ERROR

Impact: Other

WCS-07801: Cannot seed the WebCenter data into the content repository.

Cause: An error occurred while seeding data for the Documents service in the content repository.

Action: Check the underlying exception and content repository log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07802: Cannot find the adf-config.xml file.

Cause: Could not find an adf-config.xml document in the classpath.

Action: To enable the Documents service in WebCenter, ensure adf-config.xml and connections.xml containing Documents service information are on the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-07803: Cannot open a connection to the Oracle Content Server.

Cause: The application failed to open a connection to the Oracle Content Server.

Action: Check that the Oracle Content Server connection is properly configured and that the server is available.
Level: 1

Type: ERROR

Impact: Other

WCS-07804: Cannot create the Security Group, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07805: Cannot create the seeded role, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07806: Cannot create the folder, {0}, in the folder, {1}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07807: Cannot rename the folder, {0}, to {1}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07808: Cannot delete the folder, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07809: Cannot get folder with the path, {0}, from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07810: Error obtaining the content repository connection "{0}".

Cause: A JNDI Naming Exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid content repository connection.
Level: 1

Type: ERROR

Impact: Other

WCS-07811: Unsupported repository connection "{0}" for the Documents service.

Cause: The specified content repository is not currently supported for Documents service WebCenter Portal integration. The supported content repository types is Oracle Content Server.

Action: Verify that adf-config.xml and connections.xml contain a valid entry for the Documents service repository.
Level: 1

Type: ERROR

Impact: Other

WCS-07812: Cannot remove permissions, {0}, for user/group, {1}, to the account for the folder, {2}.

Cause: The application failed to remove permissions for the user/group on the folder.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07813: Cannot grant permissions, {0}, for user, {1}, to the account for the folder, {2}.

Cause: The application failed to grant permissions for the user on the folder.

Action: Check that the permissions and user are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07814: Error while removing an account from all users credentials.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07816: Unable to seed the WebCenter data in the Oracle Content Server repository.

Cause: A Content Server error occurred while seeding the WebCenter data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07817: Unable to seed the Personal Folder data in the Oracle Content Server repository.

Cause: A Content Server error occurred while seeding the Personal Folder data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07818: Cannot find the WebCenter administrators to seed in the Document Library repository.

Cause: The application failed to determine the list of WebCenter administrators.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07819: Cannot release the session pool.

Cause: Failed to release the session pool for the content repository administrative connection.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07820: Cannot create a search result row from the JCR node.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07821: Error while calling the EC_SET_PROPERTY service with dECPropType = {0}, dECPropKey = {1}, dECPropSubKey = {2}, dECPropValue = {3}.

Cause: A call to the Oracle Content Server EC_SET_PROPERTY service during repository setup failed to complete.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07822: Cannot get the WebCenter URL.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07823: Cannot grant the account, {0}, to all users.

Cause: An error occurred while trying to grant the account to all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07824: Unable to get the admin session to the Oracle Content Server repository.

Cause: An error occurred while trying to obtain an admin session to the Oracle Content Server repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07825: Cannot remove role, {0}, for user/group, {1}.

Cause: The application failed to remove the specified role from the user/group.

Action: Check the role and user/group are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07826: Cannot remove role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.

Cause: The application failed to remove the role and permissions on the folder for the user/group.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07827: Cannot add role, {0}, for user/group, {1}.

Cause: The application failed to add the specified role to the user/group.

Action: Check the role and user/group are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-07828: Cannot add role {0} and permissions, {1}, to the account for the folder, {2} for the user/group {3}.

Cause: The application failed to add the role and permissions on the folder for the user/group.

Action: Check that the permissions and user/group are valid and that the folder exists.
Level: 1

Type: ERROR

Impact: Other

WCS-07829: Cannot update the account for the portal {0}, with permission, {1}, for all users.

Cause: An error occurred while trying to update the portal account for all users.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07830: Cannot set default attributes, {0}, for the key, {1}

Cause: An error occurred while trying to set default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07831: Cannot delete default attributes for the key, {0}.

Cause: An error occurred while trying to delete default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07832: Cannot determine account and permission from the default attributes for the portal, {0}.

Cause: An error occurred while trying to determine the account and permission from the default attributes for the portal. The default attributes are not in the correct format.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07833: The Java Object Cache is not available.

Cause: An error occurred while trying to retrieve the cache.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07834: A Java Object Cache operation timed out. Distributed caches may be inconsistent.

Cause: A cache operation timed out.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07835: Java Object Cache, Put operation failed.

Cause: A cache put operation failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07836: Java Object Cache, Destroy operation failed.

Cause: A cache destroy operation failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07837: Java Object Cache, Get operation failed.

Cause: A cache get operation failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07838: Java Object Cache, release ownership failed.

Cause: A cache unlock operation on a cached object failed.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07839: Invalid document service ADF configuration.

Cause: The documents services configuration in adf-config.xml is invalid.

Action: Verify that the documents services configuration in adf-config.xml conforms to the documents service configuration data schema.
Level: 1

Type: ERROR

Impact: Other

WCS-07840: Cannot get folder with the GUID, {0}, from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07850: Failed to destroy Java Object Cache region, {0}.

Cause: An error occurred while trying to destroy the Doclib Java Object Cache region.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07857: Cannot get the version for the {0} component from the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07863: Cannot determine if Document Library supports Enterprise Roles.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07864: Cannot enable the workflow {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07865: Cannot create the workflow with the name {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07866: Cannot create the workflow step {0} for the workflow {1}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07867: Cannot get the portal account from the GUID {0}.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07868: Cannot propagate account for the portal folder {0} to its contents.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07870: Security settings are only supported for Oracle Content Server.

Cause: An attempt has been made to set security for a non Oracle Content Server repository.

Action: To enable security, use Oracle Content Server.
Level: 1

Type: ERROR

Impact: Other

WCS-07871: Cannot set default attributes, for the key, {1}

Cause: An error occurred while trying to get default attributes for the specified key.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07872: Unable to upgrade the WebCenter data in the Oracle Content Server repository.

Cause: A Content Server error occurred while upgrading the WebCenter data in the repository.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07873: Cannot get the workflow {0}.

Cause: A Content Server error occurred while getting the workflow.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07874: The documents services configuration in adf-config.xml is invalid, one of the settings is being used in another Webcenter's configuration.

Cause: Either the portal root or application name in the Document Properties is the same as another WebCenter instance using the same Content Server.

Action: Ensure the portal root and application are both unique and not being used in another WebCenter's configuration using the same Content Server.
Level: 1

Type: ERROR

Impact: Other

WCS-07875: Can not get the folder metadata for the scope, {0}.

Cause: A Content Server error occurred while getting the scope's folder metadata.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07877: Error invalidating the VCR cache entry for {0}.

Cause: An error happened while trying to remove an item from the VCR cache.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07878: Error determining if a scope in the export set has document library provisioned.

Cause: An error happened while trying to determine if the scope is provisioned.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07879: Error while writing doclib provisioned scope to export file.

Cause: An error happened while trying to output the scopes which have document library provisioned.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07880: Error while writing the doclib export document to MDS for portal(s) {0}.

Cause: An error happened while trying to write the document containing the document library export data to MDS.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07884: Error while reading the set of doclib provisioned scopes from the export file.

Cause: An error happened while trying to read the scopes which have document library provisioned from the export file.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07885: Error while reading the doclib export document from MDS for portals{0} .

Cause: An error happened while trying to read the document containing the document library export data from MDS.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07886: Error provisioning document library for a scope in the import set.

Cause: An error happened while trying to provisioning document library during import.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07887: No document library export data found for import in MDS under path {0} for portal(s) {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-07888: Invalid datasource type ''{0}''. Valid datasource types:{1}.

Cause: The specified datasource type was invalid.

Action: Correct the specified datasource type to one of the examples provided in the error message.
Level: 1

Type: ERROR

Impact: Other

WCS-07889: Query expression must be a valid, non-empty expression.

Cause: The specified query expression was invalid.

Action: Review the specified query expression and correct it.
Level: 1

Type: ERROR

Impact: Other

WCS-07890: The Scenario datasource was not constructed correctly

Cause: Either the conductor or the scenario have not be set correctly.

Action: Review the specified conductor service and scenario configurations to make sure they are correct.
Level: 1

Type: ERROR

Impact: Other

WCS-07891: Failed to get UCM configuration settings.

Cause: An error occurred while getting configuration information from the Content Server.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07892: Invalid content id ''{0}'' for datasource type ''{1}''.

Cause: The specified content id was invalid.

Action: Correct the specified content id to a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-07893: The datasource type ''{0}'' requires ''{1}'' to be set.

Cause: The specified datasource type is not consistent with the datasource state.

Action: Specific datasource types require different parameters to be set. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07894: Both page size and maximum results are required and must be a positive integer (pageSize:{0}, maxResults:{1}).

Cause: You have not specified the page size and maximum results.

Action: Correct the page size and maximum results.
Level: 1

Type: ERROR

Impact: Other

WCS-07895: Maximum results (current:{0}) must be an integer between {1} and {2}.

Cause: The value you have specified for maximum results must inclusively be between the range specified.

Action: Correct the maximum results to be inclusively be between the specified range.
Level: 1

Type: ERROR

Impact: Other

WCS-07896: An error occurred while retrieving the node.

Cause: An error occurred while retrieving the node.

Action: Check the base exception for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-07897: Error retrieving node(s).

Cause: An error was encountered retrieving node(s).

Action: Please contact a system administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-07898: The datasource type ''{0}'' is currently not supported for custom folder.

Cause: The specified datasource type is not supported for ContentListFactory custom folder.

Action: Only specific datasource types are supported. Please resolve this situation.
Level: 1

Type: ERROR

Impact: Other

WCS-07899: Cannot update the seeded role, {0}, in the Oracle Content Server.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07900: Can not perform document library role mapping, role mapper is not initialized.

Cause: A Content Server error occurred while executing the operation.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07901: Can not perform document library role mapping, role mapper was initialized with a different scope to that being processed. Initialized with scope {0} and processing with scope {1}.

Cause: The document library role mapper can only process actions for the scope with which it was initialized. A request has been made to process role mapping for a different scope which is not permitted.

Action: Check the underlying exception and Oracle Content Server log for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07902: Can not perform document library role mapping, the scope does not have Document Library provisioned.

Cause: The document library role mapper can only map roles for a scope which has document library provisioned.

Action: Check the scope has document library provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-07903: Invalid repository name {0}.

Cause: An invalid repository was specified.

Action: Verify that a valid repository is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-07904: Error while exporting the documents content.

Cause: An error happened while trying to export the documents content of the scopes being exported.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07905: Error while getting the documents contents of the source scope.

Cause: An error happened while trying to get the documents of the source scope from the Content Server.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07906: No scopes have been specified for export.

Cause: No portals have been specified to be exported.

Action: Specify scopes to be exported.
Level: 1

Type: WARNING

Impact: Other

WCS-07907: Error while importing the documents content.

Cause: An error happened while trying to import the documents content of the scopes being imported.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07908: Group Space folder does not exist in target instance can not proceed with import.

Cause: The scope has not been provisioned in the target instance, can not proceed to import data into the target instance.

Action: Ensure WebCenter Export Import has completed successfully and the Scope is provisioned in the target instance.
Level: 1

Type: ERROR

Impact: Other

WCS-07909: The import archive {0} was not found, no document data will be imported.

Cause: The archive containing the documents data was not found. Import of documents content will not occur.

Action: Ensure WebCenter Export included the exporting of documents content..
Level: 1

Type: WARNING

Impact: Other

WCS-07910: Unable to delete data in the target scope prior to import.

Cause: An error happened while trying to delete existing data in the target scope before import commences.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07911: Unable to create document in target scope.

Cause: An error happened while trying to create a document in the target scope.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07916: The following documents were not imported {0}.

Cause: The documents in the list could not be imported into the target UCM.

Action: Check the logs for more information.
Level: 1

Type: WARNING

Impact: Other

WCS-07917: Error creating content URL.

Cause: An error occurred creating a content URL.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07918: The content item {0} was not imported. An item with the filename {1} already exists in the folder.

Cause: Oracle Content Server does not permit multiple content items with the same filename to be checked into the same folder. The content item being imported has the same filename as an existing content item in the same folder. The duplicate document has not been imported.

Action: Check the source UCM instance and either remove the duplicate content items, or ensure the import has imported the correct version of the content item.
Level: 1

Type: WARNING

Impact: Other

WCS-07919: The content item {0} was not imported. The filename {1} contains an invalid characters.

Cause: The filename of the file being imported contains invalid characters, the document can not be checked in.

Action: Check the logs for more information.
Level: 1

Type: WARNING

Impact: Other

WCS-07920: An error occurred loading the names of additional content attributes.

Cause: An error occurred loading the names of additional content attributes.

Action: Check the underlying exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-07923: No primary content repository connection.

Cause: There is no content repository connection name set as the primary connection.

Action: Set a content repository connection as the primary connection.
Level: 1

Type: ERROR

Impact: Other

WCS-08001: Supplied class {0} is not an instance of {1}.

Cause: Forum service adapter details were not configured properly in the adf-config.xml file or the adapter implementation class was not correct.

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-08002: Not able to invoke constructor of class {0} through Constructor.newInstance() call.

Cause: Application tried to instantiate a class through Constructor.newInstance().

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-08003: Not able to find the method "{0}" in the class "{1}".

Cause: Matching constructor was not found in the adapter implementation class.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-08004: Not able to resolve the name {0}

Cause: Not able to acquire Context to look up.

Action: Check for JNDI configuration.
Level: 1

Type: ERROR

Impact: Other

WCS-08005: User "{0}" is not authorized.

Cause: Contact your administrator for access to discussions forum.

Action: Provide valid user credentials, or check if user exists or has appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-08006: User "{0}" not logged on.

Cause: User might not have logged on to the system.

Action: Try logging on using correct user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-08007: User "{0}" not found

Cause: User might not have been created, or user might have been deleted from the back-end application.

Action: Contact your administrator or try different user credentials.
Level: 1

Type: ERROR

Impact: Other

WCS-08008: Service "{0}" is not a valid service or it is not supported by the "{1}" adapter implementation.

Cause: Adapter implementation does not recognize this service type.

Action: Read the documentation for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-08009: Discussion forum Category with name "{0}" already exists.

Cause: Category with the given name already exists.

Action: Try with a different category name.
Level: 1

Type: WARNING

Impact: Other

WCS-08010: Category not found.

Cause: Category does not exists or user is not authorized to access it.

Action: Provide a valid category ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08011: Discussion forum object Forum with name "{0}" already exists.

Cause: Discussion forum object Forum with the given name already exists.

Action: Try with a different forum name.
Level: 1

Type: WARNING

Impact: Other

WCS-08012: No forums were found.

Cause: Forum does not exists or user is not authorized to access it.

Action: Provide a valid forum ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08013: Topic not found.

Cause: Topic does not exists or user is not authorized to access it.

Action: Provide a valid topic ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08014: Message not found.

Cause: Message does not exists or user is not authorized to access it.

Action: Provide a valid message ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08015: There is a problem with the supplied attachments.

Cause: Possible causes: attachment was larger than expected, it was not readable or available, or it was not a supported mime type.

Action: Try with a different attachment or contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08016: Unable to look up the forum connection with name "{0}".

Cause: Either the forum connection name is not valid or corresponding connection details are deleted from the connection store.

Action: Check the default connection name in adf-config and connection details in connection store for discussion forum service or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08017: Ambiguous forum connection definitions found in the connection store.

Cause: More than 1 connection type found for discussion forum service. Unable to decide which one to use.

Action: Configure the appropriate connection name as the default connection to use from the management console or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08018: Discussion forum object Message with subject "{0}" is prevented from being posted.

Cause: Discussion forum object Message is rejected because of any one of the following reasons: 1) blocking a set of users from posting, 2) preventing a user from posting more than once every X seconds, 3) rejecting any messages that contain profanity from the back-end application.

Action: If you are authorized to post messages and your text has valid language, then try again after some time.
Level: 1

Type: WARNING

Impact: Other

WCS-08019: Host address "{0}" configured in connection store is not correct.

Cause: IP address of the host configured in connection store could not be determined.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08020: Unable to connect to discussion server.

Cause: Possible reasons: The IP address of the host configured in the connection store could not be determined, or the connection was refused by the host.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08021: Forum connection details are not available in the connection store.

Cause: Forum connection details were not available in the connection store.

Action: Configure discussion forum service connection details in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-08022: Unable to create discussion forum object Forum with name "{0}".

Cause: Unable to create discussion forum object Forum with the supplied name and description.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08023: Not able to reach service endpoint port type due to {0}.

Cause: Service end point is not reachable.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08024: Input parameter value "{0}" supplied is invalid.

Cause: Invalid input parameter value is supplied.

Action: Provide valid values for the input parameters.
Level: 1

Type: ERROR

Impact: Other

WCS-08025: You do not have permission to see forums for this portal.

Cause: User is not authorized to access the forum.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08026: You do not have permission to see recent topics for this portal.

Cause: User is not authorized to access the recent topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08027: You do not have permission to see popular topics for this portal.

Cause: User is not authorized to access the popular topics.

Action: Contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08028: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-08029: Could not connect to the configured discussions server.

Cause: Configured discussion server is not reachable.

Action: Check if server details are correct or contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-08201: Not able to create forum configuration file for community "{0}" due to : {1}.

Cause: Possible failure creating the category or forum, or an issue with the MDS write operation.

Action: Contact your system administrator or read the discussion forum service configuration documentation for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-08202: Failed to flush changes into preference store due to {0}.

Cause: Possible failure in the backing store, or a failure to contact the backing store.

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-08601: Supplied class {0} is not an instance of {1}.

Cause: Service db adapter details were not configured properly in the adf-config.xml file or the adapter implementation class was not correct.

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-08602: Not able to instantiate the class {0}, no default empty constructor found.

Cause: Application tried to instantiate a class through Constructor.newInstance().

Action: Check that the adapter class name in the adf-config file is correct and ensure to have a default empty constructor.
Level: 1

Type: ERROR

Impact: Other

WCS-08603: User "{0}" not logged on.

Cause: User might not have logged on to the system.

Action: Try logging on using correct user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-08604: Category with name "{0}" already exists.

Cause: Category with the given name already exists.

Action: Try with a different category name.
Level: 1

Type: WARNING

Impact: Other

WCS-08605: Unable to find the Category: {0}.

Cause: Category does not exists or user is not authorized to access it.

Action: Provide a valid category ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08606: Unable to find the Survey {0}.

Cause: Survey does not exists or user is not authorized to access it.

Action: Provide a valid survey ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08607: Survey already exists: {0}.

Cause: Survey with the given name already exists.

Action: Try with a different survey name.
Level: 1

Type: WARNING

Impact: Other

WCS-08608: Survey already closed: {0}

Cause: Survey is closed, some operations on closed surveys are not allowed.

Action: Some operations on closed surveys are not allowed.
Level: 1

Type: WARNING

Impact: Other

WCS-08609: Survey already published: {0}

Cause: Survey is published, some operations on published surveys are not allowed.

Action: Some operations on published surveys are not allowed.
Level: 1

Type: WARNING

Impact: Other

WCS-08610: Unable to find the Survey Item {0}.

Cause: Survey item does not exists.

Action: Provide a valid survey item ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08611: Unable to find the Survey Template {0}.

Cause: Survey template does not exists or user is not authorized to access it.

Action: Provide a valid survey template ID.
Level: 1

Type: WARNING

Impact: Other

WCS-08612: Failed to perform {0} operation. Check logs for more details.

Cause: Unknown exception occured.

Action: Contact your administrator to check logs for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-08613: Failed to perform {0} operation. Check logs for more details.

Cause: Unknown exception occured.

Action: Contact your administrator to check logs for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-08614: Survey not published: {0}

Cause: Survey is not published, certain operations are not allowed without publishing.

Action: Publish the survey to allow this operation.
Level: 1

Type: WARNING

Impact: Other

WCS-09001: The IMAP host cannot be null or an empty string.

Cause: The IMAP server host address was not specified.

Action: Configure Mail Service connection.
Level: 1

Type: ERROR

Impact: Other

WCS-09002: The SMTP host cannot be null or an empty string.

Cause: The SMTP server host address was not specified.

Action: Configure Mail Service connection.
Level: 1

Type: WARNING

Impact: Other

WCS-09003: Anonymous user access is not permitted on the mail service. Users must log on to the application.

Cause: User was not logged on to the application. ADF security context was not set to authenticated user.

Action: Log on to the application using the ADF authentication mechanism.
Level: 1

Type: WARNING

Impact: Other

WCS-09004: User credentials not found in the credential store for user "{0}" with external application ID: {1}.

Cause: Mapped user credentials for the current logged on user were not found in the credential store.

Action: Supply valid credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-09005: Multiple connection definitions found for mail service.

Cause: Multiple connection definitions were defined in the registry; could not identify the default connection to use.

Action: Specify the default connection to be used in adf-config.xml. For more details, refer to the Mail Service documentation for creating connections.
Level: 1

Type: WARNING

Impact: Other

WCS-09006: Lookup for connection "{0}" failed.

Cause: Failed to get the JNDI context, or the mail connection with the given name was not available.

Action: Supply proper connection name, and ensure that the entry exists in the connection repository.
Level: 1

Type: ERROR

Impact: Other

WCS-09007: ADF connections context could not be acquired. Failed to find mail connection.

Cause: Failed to get the JNDI context for the connection repository.

Action: ADF connection context details were missing from the adf-config.xml file. For more information, refer to the ADF Developer's Guide.
Level: 1

Type: ERROR

Impact: Other

WCS-09008: Failed to create mail session due to: {0}

Cause: Unexpected failure: either the IMAP/SMTP server did not respond, it failed to understand the request, or it was not configured properly.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09009: Failed to connect to the mail server. Connection timed out.

Cause: Could not connect to the mail server in the given time.

Action: Confirm that the IMAP/SMTP servers are running or increase the timeout value.
Level: 1

Type: WARNING

Impact: Other

WCS-09010: Failed to read messages from the folder "{0}". Further information: {1}

Cause: Either the IMAP folder had issues or the search term was not supported by the server.

Action: Contact your system administrator to check the issues in the log file.
Level: 1

Type: WARNING

Impact: Other

WCS-09011: Failed to get message with ID "{0}" from the folder "{1}". Further information: {2}.

Cause: Either the IMAP folder had issues or the search term was not supported by the server.

Action: Contact your system administrator to check the issues in the log file.
Level: 1

Type: WARNING

Impact: Other

WCS-09012: Failed to send the message with subject "{0}". Further information: {1}

Cause: Either the SMTP server did not respond or the message was corrupted.

Action: Contact your system administrator to check the issues in the log file.
Level: 1

Type: ERROR

Impact: Other

WCS-09013: Message with ID "{0}" has been permanently removed from the "{1}" folder.

Cause: Either this message did not exist on the IMAP folder or it was been deleted via expunge on the folder.

Action: The IMAP folder has been expunged to permanently delete all messages. The message cannot be recovered.
Level: 1

Type: WARNING

Impact: Other

WCS-09014: Unable to find the "{0}" folder.

Cause: Either the folder with this name did not exist on the IMAP server or the mail server did not support folders.

Action: Ensure that the folder with the given name exists and that the IMAP server is properly configured.
Level: 1

Type: WARNING

Impact: Other

WCS-09015: Failed to perform the {0} operation due to: {1}.

Cause: Either the mail server was down or it did not support this operation.

Action: Ensure that the IMAP and SMTP servers are properly configured and available.
Level: 1

Type: ERROR

Impact: Other

WCS-09016: Logon failed: unknown user name or incorrect password

Cause: The user credentials acquired from the credential store were incorrect.

Action: Ensure that the user credentials supplied for logon are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-09017: Could not make an attachment: not a valid body part for creating an attachment.

Cause: Either the body part was not recognized, it could not be attached to the message, or the body part could not be processed.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09018: No recipients for the mail specified.

Cause: No recipients for the mail specified.

Action: At least one recipient must be specified for the mail to be delivered.
Level: 1

Type: ERROR

Impact: Other

WCS-09019: No mail connection found.

Cause: No mail connection was specified.

Action: The mail connection is not available in the connection repository. Ensure that a connection to the mail server is defined.
Level: 1

Type: ERROR

Impact: Other

WCS-09020: Connection to the server failed.

Cause: Connection to the server failed: either the host or port information was wrong or the server was down.

Action: Check the mail server connection details and ensure that the mail server is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-09021: User name to connect to the mail server for Email Gateway is not supplied.

Cause: Connection to the server failed: mail user account was not complete.

Action: User account details are required to connect to the mail server.
Level: 1

Type: ERROR

Impact: Other

WCS-09022: User password to connect to the mail server for Email Gateway is not supplied.

Cause: Connection to the server failed: mail user account is not complete.

Action: User account details are required to connect to the mail server.
Level: 1

Type: ERROR

Impact: Other

WCS-09023: Cannot attach file. Either the file exceeds the maximum allowed file size or it is empty(zero bytes). Attached files must be less than 2 MB.

Cause: Either the attachment size is 0(zero) or greater than 2 MB.

Action: Attach a file within in the expected size limit.
Level: 1

Type: ERROR

Impact: Other

WCS-09025: Message delivery failure: The message could not be sent because connecting to the SMTP mail server failed. The server may be unavailable. If the problem persists, report the error to your administrator.

Cause: Connection to the server failed: either the host or port information was wrong or the server was down.

Action: Check the mail server connection details and ensure that the mail server is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-09026: Error processing the message.

Cause: The message might have been sent with improper encoding.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09027: The number of recipients for the mail:{0} has exceeded the maximum limit:{1} set by the space administrator.

Cause: The number of recipients for the mail has exceeded the maximum limit set by the space administrator.

Action: Reduce the number of recipients or contact the space administrator to change the maximum limit
Level: 1

Type: ERROR

Impact: Other

WCS-09201: Distribution list "{0}" already exists.

Cause: A distribution list with the supplied name already exists.

Action: Create the distribution list with a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-09202: Distribution list "{0}" is not available.

Cause: A distribution list with the supplied name does not exist.

Action: Verify the supplied name and ensure that the list exists on the mail server.
Level: 1

Type: ERROR

Impact: Other

WCS-09203: Mandatory connection property "{0}" missing from the directory connection.

Cause: The mandatory connection property required to establish directory connection was not supplied.

Action: Verify the supplied directory connection details, and ensure that the required details are supplied.
Level: 1

Type: ERROR

Impact: Other

WCS-09204: Filter criteria not defined for the directory search: {0}.

Cause: Filter criteria was not defined for the directory search.

Action: Search criteria should contain filter details.
Level: 1

Type: ERROR

Impact: Other

WCS-09205: Incorrect format for the schema attribute. Value retrieved is: {0}.

Cause: The schema was not specified properly.

Action: Check the base DN for the schema details and supply the complete base DN.
Level: 1

Type: ERROR

Impact: Other

WCS-09214: Failed to acquire the initial directory context for name: {0}, due to : {1}

Cause: Failed to acquire the connection either the connection details are wrong or server is not reachable.

Action: Ensure proper configuration is provided or Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09215: Unable to create the distribution list: {0}, Mandatory attributes missing. Further information: {1}

Cause: Mandatory attributes to create a group are missing.

Action: Contact System Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-09216: Unexpected error occurred. Further info: {0}

Cause: Unexpected error occurred contact system administrator.

Action: Contact Oracle Support
Level: 1

Type: ERROR

Impact: Other

WCS-09217: Unable to lookup the context name: {0}, due to : {1}

Cause: Unable to find the context.

Action: Contact System Administrator
Level: 1

Type: WARNING

Impact: Other

WCS-09218: Unable to destroy the context name: {0}, due to : {1}

Cause: Either context does not exists or its not a proper context name.

Action: Contact System Administrator
Level: 1

Type: WARNING

Impact: Other

WCS-09219: Unable to modify attributes for the context name: {0}, due to : {1}

Cause: Either context does not exists or its not a proper context name.

Action: Contact System Administrator
Level: 1

Type: WARNING

Impact: Other

WCS-09220: Unable to find the attribute: {0} under context {1}, due to {2}

Cause: Required attribute not found in the context object.

Action: Ensure the required attribute is available in the context object.
Level: 1

Type: WARNING

Impact: Other

WCS-09251: Failed to make attachment, due to: {0}.

Cause: Either the file size was too large or the selected file was not readable. Check the server settings.

Action: Ensure that the file is available and readable. Also ensure that the file is not too large. If the problem persists, then contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09252: Failed to remove attachment due to: {0}.

Cause: Either this attachment did not exist or it failed to read the message. See the error log for more details.

Action: Contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09253: Failed to send message, due to: {0}.

Cause: Either the mail session was expired or the user was not logged in.

Action: Contact your system Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09254: Failed to read attachments, due to: {0}.

Cause: Either the mail session is expired or the user is not logged-in.

Action: Contact your system Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09255: External application ID not defined.

Cause: The required configuration parameter External Application ID was not found.

Action: Contact your system Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09256: This message has been deleted.

Cause: This message had been deleted.

Action: Only non-deleted mails can be viewed.
Level: 1

Type: WARNING

Impact: Other

WCS-09257: No compose message object found.

Cause: User may not be in the compose mode or the state is lost.

Action: Ensure the user is in compose message view.
Level: 1

Type: WARNING

Impact: Other

WCS-09258: Unable to find the attachment table component.

Cause: Unable to find the table component in the current view.

Action: Ensure the table component id name is not changed.
Level: 1

Type: WARNING

Impact: Other

WCS-09259: Unable to find the backing bean by name {0}.

Cause: Either the backing bean is removed or the name is changed.

Action: Ensure the backing bean names are intact.
Level: 1

Type: WARNING

Impact: Other

WCS-09501: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09502: Supplied class {0} is not an instance of {1}.

Cause: Announcement service adapter details might not have been configured properly in the adf-config.xml file or adapter implementation class was not proper.

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-09503: Not able to invoke constructor of class {0} through Constructor.newInstance() call.

Cause: Application is trying to instantiate a class through Constructor.newInstance().

Action: Check that the adapter class name in the adf-config file is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-09504: Not able to find the method "{0}" in the class "{1}".

Cause: Matching constructor might not be found the adapter implementation class.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-09505: User "{0}" is not authorized.

Cause: Contact your administrator for access to announcements.

Action: Provide valid user credentials, or check if user exists or has appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-09506: User "{0}" not logged on.

Cause: User might not have logged on to the system.

Action: Try logging on using correct user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-09507: User "{0}" is not found.

Cause: User might not have been created, or user might have been deleted from the back-end application.

Action: Contact your administrator or try different user credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-09508: Announcement configuration file for community "{0}" not found or details such as category ID and announcement ID are not available.

Cause: There was a failure in creating the announcement configuration or an issue with the MDS read or write operation.

Action: Contact your system administrator or read the announcement service configuration documentation for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-09509: Announcement not found.

Cause: Announcement object with the supplied announcement ID was not available or it was not accessible.

Action: Provide a valid announcement ID.
Level: 1

Type: WARNING

Impact: Other

WCS-09510: Announcement parent not found.

Cause: Announcement parent object with the supplied ID was not available or it was not accessible.

Action: Provide a valid accessible parent ID.
Level: 1

Type: WARNING

Impact: Other

WCS-09511: Announcement parent not found.

Cause: Announcement parent object is not accessible from discussion forum.

Action: Check if discussion service is configured properly.
Level: 1

Type: WARNING

Impact: Other

WCS-09512: Unable to lookup the announcement connection with name "{0}".

Cause: Either the announcement connection name is not valid or corresponding connection details are deleted from the connection store.

Action: Check the default connection name in adf-config for discussion announcement service or contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09513: Ambiguous announcement connection definitions found in the connection store.

Cause: More than 1 connection type found for discussion announcement service. Unable to decide which one to use.

Action: Configure the appropriate connection name as the default connection to use from the management console or contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09516: Announcement service configuration not found

Cause: service configuration details are missing

Action: Ensure service config details are either loadable from classpath or from adf-config.
Level: 1

Type: WARNING

Impact: Other

WCS-09517: Announcement service configuration not correct.

Cause: service configuration details are not provided as expected.

Action: Correct the service configuration details.
Level: 1

Type: WARNING

Impact: Other

WCS-09518: Host address "{0}" configured in connection store is not correct.

Cause: IP address of the host configured in connection store could not be determined.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09519: Not able to log on to the back-end system with host address "{0}".

Cause: Possible reasons: The IP address of the host configured in the connection store could not be determined, or the connection was refused by the host.

Action: Configure the correct host name in connection store or contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-09520: Expiry date cannot be earlier than start date.

Cause: Expiry date is specified to be earlier than start date.

Action: Specify expiry date to be later than start date.
Level: 1

Type: WARNING

Impact: Other

WCS-09521: Not able to query data from SQL Connection.

Cause: Possible reasons: The database is down or invalid SQL Connection configuration in the DataSource.

Action: Configure the correct SQL Connection in the DataSource.
Level: 1

Type: ERROR

Impact: Other

WCS-09522: Announcement parent not accessible.

Cause: Contact your administrator for access to announcements.

Action: Check if announcements parent exists or user has permissions to access announcements.
Level: 1

Type: WARNING

Impact: Other

WCS-09523: Could not connect to the configured discussions server.

Cause: Configured discussion server is not reachable.

Action: Check if server details are correct or contact your administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-09601: Not able to create announcement configuration file for community {0} due to : {1}.

Cause: Possible failure creating category or announcement or an issue with the MDS write operation.

Action: Contact your system administrator or read the announcement service configuration documentation for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-09602: Failed to flush changes into preference store due to {0}.

Cause: Possible failure in the backing store, or failure to contact the backing store.

Action: Contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-11001: Error on content write: {0}

Cause: The content write operation failed for the given reason.

Action: Investigate the reason for the failure.
Level: 1

Type: ERROR

Impact: Other

WCS-11002: Internal server error: {0}

Cause: An unexpected internal error has occurred.

Action: Contact your Oracle Support representative.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11003: Invalid Request

Cause: The client has submitted an invalid HTTP request.

Action: Re-send the corrected request.
Level: 1

Type: WARNING

Impact: Other

WCS-11004: Path not found: {0}

Cause: The requested path has not been found on the server.

Action: Correct the path on the client and re-send the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11005: Not an ISO8601 date: {0}

Cause: The client supplied a date which is not in ISO8601 format.

Action: Correct the date format on the client and re-send the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11006: Not an HTTP date: {0}

Cause: The client supplied a date which is not in HTTP date format.

Action: Correct the date format on the client and re-send the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11007: Namespace not supported: {0}

Cause: The repository does not support the given namespace.

Action: Specify a valid namespace.
Level: 1

Type: WARNING

Impact: Other

WCS-11008: Bad request

Cause: The client submitted a request that could not be understood by the server.

Action: Correct the syntax and resubmit the request.
Level: 1

Type: WARNING

Impact: Other

WCS-11009: Not modified

Cause: The client has performed a conditional GET request, access is allowed but the document has not changed.

Action: No action required as resource has not been modified and hence it is not returned.
Level: 1

Type: ERROR

Impact: Other

WCS-11010: Not acceptable

Cause: The requested resource could not generate an entity with an acceptable media-type for the client.

Action: If applicable, resubmit the request with a broader acceptance criteria.
Level: 1

Type: ERROR

Impact: Other

WCS-11011: Precondition failed

Cause: A request precondition has failed.

Action: If applicable, resubmit the request with different preconditions.
Level: 1

Type: ERROR

Impact: Other

WCS-11012: The Java virtual machine does not support the UTF-8 character set.

Cause: The UTF-8 character set is not supported by the Java virtual machine.

Action: Contact your Oracle Support Representative.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11013: No DAV dead property name matches the JCR property name {0}.

Cause: A unexpected JCR property name has been found that does not correspond to a DAV dead property name.

Action: Contact your Oracle Support Representative.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-11014: Cannot close the servlet output stream.

Cause: There was an error closing the servlet output stream.

Action: Review the server logs for possible cause of failure.
Level: 1

Type: ERROR

Impact: Other

WCS-11015: Cannot close content input stream.

Cause: There was an error closing the content input stream.

Action: Review the server logs for possible cause of failure.
Level: 1

Type: ERROR

Impact: Other

WCS-11016: Invalid resource name: {0}

Cause: The given name is not a valid resource name.

Action: The client should resubmit the request with a corrected URL.
Level: 1

Type: ERROR

Impact: Other

WCS-11017: Invalid resource name; illegal escape sequence in path: {0}

Cause: The given name was not a valid resource name as it contains an illegal escape sequence.

Action: The client should resubmit the request with a corrected URL.
Level: 1

Type: WARNING

Impact: Other

WCS-11018: Forbidden request method: {0}

Cause: The requested HTTP method was not completed as the server forbids the execution of this type of method.

Action: Compatible clients should not use the specified HTTP method.
Level: 1

Type: ERROR

Impact: Other

WCS-11019: Folder listing is disabled.

Cause: Folder listing has been disabled.

Action: Folder listing must be explicitly enabled in the application's web.xml.
Level: 1

Type: WARNING

Impact: Other

WCS-12001: No handlers could be found for services with IDs: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Handlers that were recorded by the system during export were not available on import.

Action: Ensure that the specified services are included and configured in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12002: The handler found in the classpath at run time cannot process the data or metadata of the archive: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. The version of the handler used during import was not compatible with the version of the handler used while creating the data or metadata on export.

Action: Include compatible versions of handlers in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12003: The required handlers are not found: {0}.

Cause: Handlers enable services to manage their data and metadata in the manner best suited to each service. Not all handlers that were used while creating this archive could be found during the import.

Action: Ensure that the specified services are included and configured in the application and restart the import process.
Level: 1

Type: ERROR

Impact: Other

WCS-12004: Unable to retrieve the JAXB bean for the export/import document in MDS.

Cause: An error occurred in the MDS configuration of the application.

Action: Check the MDS configuration files of the application.
Level: 1

Type: ERROR

Impact: Other

WCS-12006: The export archive does not contain any scope metadata.

Cause: An error occurred during the export process, or the exported archive was damaged.

Action: Reattempt import with a different export file.
Level: 1

Type: ERROR

Impact: Other

WCS-12007: Scope with name {0} already exists in the import destination and it does not match with the scope being imported.

Cause: A scope with the specified name already exists for the current application instance. This caused a conflict between the source and target instances.

Action: Delete the scope from the current application instance and reattempt the import.
Level: 1

Type: ERROR

Impact: Other

WCS-12008: The export archive is from an older application and is not compatible with the current version of application.

Cause: The export archive is created using an older version. This archive cannot be imported into the current version of application.

Action: Reattempt import with a newer export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12009: The Lifecycle Manager MBean cannot be deregistered.

Cause: There are numerous possible reasons for this failure.

Action: For information, review other messages in the log file and the reported exception stacks.
Level: 1

Type: WARNING

Impact: Other

WCS-12010: The Lifecycle Manager MBean cannot be created and registered. This problem will not prevent the application from running. However, the Lifecycle Manager will be unavailable.

Cause: There are numerous possible reasons for this failure.

Action: For information, review other messages in the log file and the reported exception stacks.
Level: 1

Type: WARNING

Impact: Other

WCS-12012: Information related to run time MBeans cannot be saved in the ADFContext application scope.

Cause: The system failed to store data in the ADFContext application scope. Lifecycle functions may not be available.

Action: Review the log files to see if there are any other problems which may have resulted in the ADFContext object becoming unusable.
Level: 1

Type: WARNING

Impact: Other

WCS-12013: An internal class cast error has occurred. Actual class: {0}, cast-to class: {1}.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12014: The activity {0} has ended but completed less child activities ({1}) than the expected ({2}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12015: The activity {0} has ended but completed more child activities ({1}) than the expected ({2}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12016: The activity {0} has completed more child activities ({1}) than the expected ({2}).

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12017: The export/import listener {0} has thrown an exception, which is being ignored.

Cause: A class listening to export/import progress events has thrown an exception.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: WARNING

Impact: Other

WCS-12018: The resource {0} for lifecycle operation cannot be found on the classpath.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12019: The connection {0} cannot be exported because it is not a Reference or Referenceable.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12020: An error has occurred while exporting the connection {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12021: The output stream for table {0} failed to close. The exception {1} will not be thrown.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12022: A SQL exception was thrown while closing the connection. This exception will be ignored.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12023: An error has occurred while closing the output stream to which the XML was being written. The export process will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12024: Value of the SQL type is not recognized, attempting to use the CHAR handler.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12025: Value of the SQL type is not recognized.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12026: A SQL exception {0} was caught while rolling back in response to an earlier exception {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12027: A SQL exception {0} was caught while closing the statement {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12028: A SQL exception {0} was caught while closing the connection {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12029: An error {1} has occurred while creating a DocumentName for table {0}. The import will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12030: An error {1} has occurred while retrieving input stream from MDS for {0}. The import will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12031: An error {1} has occurred while deleting the table export document {0} from MDS. The import will not be aborted.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12032: The Queue Callback handler was interrupted while waiting for child threads to complete.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12033: Exception occurred in child thread: {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12034: The Queue Consumer with name {0} was interrupted while taking an object from the queue. The Queue Consumer will continue and ignore the exception: {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12038: IOException while creating stage directory for export

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12039: IOException while creating temporary directory to extract the import archive to

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12040: IOException extracting import archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12041: Input archive path not set on context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12042: Input archive does not exist.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12043: MDSConfigurationException constructing source instance for MDS transfer.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12044: An unanticipated exception {0} has occurred while generating the oracle-archive.xml deployment descriptor of the export archive.

Cause: Cause is dependent upon the type and details of the exception being processed.

Action: Review the exception being processed for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-12045: Operation aborted because of an exception thrown by subunit ({0})

Cause: The cause of the exception that was thrown is dependent upon the type and details of the exception.

Action: Review the exception thrown for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-12046: MDSException while creating lifecycle document in MDS transfer source

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12047: The import archive file does not contain a metadata archive.

Cause: The supplied file to import was not a valid export archive.

Action: Retry the import operation with a valid export archive.
Level: 1

Type: ERROR

Impact: Other

WCS-12048: FileNotFoundException extracting metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Resolve any hardware or file system errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12049: IOException while extracting metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12050: IOException while creating metadata transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12051: Output path has not been set on operation context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12052: MDSException constructing transfer list for MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12053: MDSException performing MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12054: MDSException deleting existing metadata.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12055: An exception has occurred while creating the transformer factory to write lifecycle information document.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12056: IOException occurred creating lifecycle information document

Cause: An error occurred writing to the file system while creating the lifecycle information document. The possible causes could be application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12057: TransformerException while writing lifecycle information document

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12058: Input path has not been set on operation context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12059: IOException while creating oracle-archive.xml

Cause: An error occurred while writing the oracle-archive.xml file to the file system. The possible causes could be application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12060: IOException while creating transport archive

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12061: Output archive path has not been set on operation context.

Cause: The possible errors could be in the code or application configuration.

Action: Resolve any application configuration errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12062: An unexpected exception occurred while removing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12063: MDSException occurred while removing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12064: A lock is blocking application import.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12065: A lock is blocking application import.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12066: MDSException while creating application import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12067: A lock is blocking the import of scope {0}.

Cause: Another operation was being performed that prevented the import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12068: A lock exists that prevents the import of scope {0}.

Cause: An import of the specified scope was being performed that prevented this import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12069: MDSException while creating scope import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12070: A lock exists that blocks the export set import.

Cause: Another operation was being performed that prevented the export set import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12071: A lock exists that prevents the export set import.

Cause: An export set import was already being performed preventing this import.

Action: Retry the import operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12072: MDSException while creating an export set import lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12073: MDSException while obtaining the Lifecycle bean from the MDS session

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12074: ID of export set in MDS does not match that of the application. MDS ID: {0}, Application ID: {1}.

Cause: An export set was imported from an incompatible source and has been ignored.

Action: Import an export set from a compatible instance.
Level: 1

Type: ERROR

Impact: Other

WCS-12076: NamingException while binding connection {0} to the export connections.xml

Cause: The possible causes could be coding or application configuration errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12077: NamingException while getting environment for exporting the ADF credential store

Cause: The possible causes could be coding or application configuration errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12078: IOException while exporting ADF credential store

Cause: The possible causes could be coding, hardware, or file system errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12079: JPSException while exporting JPS credential store

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12080: MDSException while creating lifecycle information metadata in transport set

Cause: An existing document with the same name as the lifecycle information document was found in the transport set being constructed.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12081: ReferenceException while creating lifecycle information metadata in transport set

Cause: An unexpected exception occurred while creating the lifecycle document in transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12082: UnsupportedUpdateException while creating lifecycle information metadata in transport set

Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12083: MDSException while building transfer list for lifecycle metadata

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12084: MDSException while constructing metadata store for MDS transfer

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12085: ParserConfigurationException while creating lifecycle information document

Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12086: SAXException while creating lifecycle information document

Cause: An unexpected exception occurred while creating the lifecycle document in the transport set.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12087: ServiceException while getting registered services

Cause: There was an error in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12088: Cannot find lifecycle service extension registry

Cause: An error in the application's configuration.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12089: Destination path specified to create the temporary directory is not a directory.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12090: The source path specified to archive does not exist

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12091: The source path specified to archive is not a directory

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Resolve any application configuration or hardware errors. If the problem recurs on subsequent attempts, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12092: A file already exists with the same name as the destination folder.

Cause: A call was made to extract an archive to a destination directory with the same name as an existing file.

Action: Retry the operation that caused this error.
Level: 1

Type: ERROR

Impact: Other

WCS-12093: {0} is an invalid value for the maximum number of steps. The maximum number of steps must be a least 1.

Cause: The probable cause is a coding error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12094: MDSException while constructing metadata store for MDS transfer

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12095: Import archive file does not exist or could not be read.

Cause: The specified file could not be found either because it does not exist or does not have the correct access permissions.

Action: Check that the path is correct, the file exists and has the appropriate access permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-12096: A lock is blocking application export.

Cause: Another operation was being performed that prevented the export.

Action: Retry the export operation after the other operation is complete.
Level: 1

Type: ERROR

Impact: Other

WCS-12097: A lock is blocking application export.

Cause: Another operation was being performed that prevented the export.

Action: Retry the export operation after the other operation is complete
Level: 1

Type: ERROR

Impact: Other

WCS-12098: MDSException while creating application export lock

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12099: An unexpected exception occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: WARNING

Impact: Other

WCS-12100: MDSException occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: WARNING

Impact: Other

WCS-12101: Unable to find data source

Cause: The data source hasn't been configured

Action: Configure the data source
Level: 1

Type: ERROR

Impact: Other

WCS-12102: An exception occurred while refreshing lock {0}:{1}

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12103: Unexpected RuntimeException performing MDS transfer.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12104: Unexpected exception occurred while exporting portlet producer information. The producer may be down or unavailable.

Cause: The possible causes could be the portlet producer is down or unavailable, errors from the portlet producer, or application configuration.

Action: Check that the portlet producers are available, and then retry the export. Review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12106: Document {0} has been excluded from the export set.

Cause: The path of the document exceeds file system constraints and therefore cannot be exported.

Action: None
Level: 1

Type: ERROR

Impact: Other

WCS-12107: InvalidReferenceException constructing MDS rename plan for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12108: MDSException performing MDS rename for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12109: MDSException while committing metadata changes for upgrade.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12110: Unable to import Scope {0} under Scope {0}

Cause: Unable to import scope under itself

Action: Import the scope either as a root level scope or specify a different parent for the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12111: Unable to import {0} as a root level scope as it inherits security.

Cause: Unable to import scope as a root level scope as it inherits security.

Action: Import the scope as a subscope and not as a root level scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12112: The parent scope {0} does not exist

Cause: Unable to import as the parent scope does not exist

Action: Import the scope either as a root level scope or specify a different parent for the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-12113: Export operation aborted due to the following reasons. {0}

Cause: Export operation aborted

Action: Retry the operation fixing the cause of failure
Level: 1

Type: ERROR

Impact: Other

WCS-12114: Failed to fetch the handler due to invalid resource type - {0}

Cause: Invalid Resource type is passed during import.

Action: Retry the operation with the correct resource type.
Level: 1

Type: ERROR

Impact: Other

WCS-12115: Portal Export operation aborted due to the following reasons. {0}

Cause: Backup operation aborted

Action: Retry the operation fixing the cause of failure
Level: 1

Type: ERROR

Impact: Other

WCS-12116: Exception while creating the export label

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Retry the operation and review the full exception stack for details of the exception should it recur.
Level: 1

Type: ERROR

Impact: Other

WCS-12117: Portal {0} already exists. If you want to overwrite the portal use the 'overwrite' option.

Cause: Portal already exists.

Action: If you want to overwrite the existing portal, use the 'overwrite' option.
Level: 1

Type: ERROR

Impact: Other

WCS-12920: A problem was encountered when invoking a method on a remote mBean ({0}) which has caused the local operation to fail.

Cause: In order for the local operation to be performed a method on a remote mBean has to be invoked - there are numerous reasons why the remote method invocation could fail ranging from connection problems between servers to the remote object simply not existing

Action: Review the log files for a record of this error in order to ascertain the primary cause.
Level: 1

Type: ERROR

Impact: Other

WCS-12950: The required customization class is not found: {0}

Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because the class was not included in the classpath.

Action: Include the customization class in the classpath of the application and restart the application.
Level: 1

Type: ERROR

Impact: Other

WCS-12951: The required customization class cannot be instantiated: {0}

Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because it is an interface or abstract class.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12952: The required customization class cannot be instantiated: {0}

Cause: To export the specified customization class, first an instance of the class must be created. An instance of this class could not be created because the current method was unable to access it.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12953: A listener cannot be registered to generate notification about the progress of the export. The export will continue but notification will not be generated on its progress.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12955: The notification arrived out of sequence. Latest sequence:{0}; sequence of this notification:{1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-12957: Exception occurred while importing data. No data imported.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: WARNING

Impact: Other

WCS-12958: Import failed with errors.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12959: Export failed with errors.

Cause: The issue may be due to a hardware error or an application configuration error.

Action: Review other messages in the log file and the reported exception stacks for additional information. Resolve any application configuration or hardware errors.
Level: 1

Type: ERROR

Impact: Other

WCS-12980: Service {0} has not been provisioned for Scope {1}.

Cause: The Service has not been provisioned for the specified Scope.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-12981: Service {0} has already been provisioned for Scope {1}.

Cause: The Service has already been provisioned for the specified Scope.

Action: Do not provision the Service for a Scope it is already provisioned for or unprovision the Service first.
Level: 1

Type: ERROR

Impact: Other

WCS-12982: Scope {0} is not known.

Cause: A Scope with the specified name has not been created.

Action: Create a Scope with the specified name using the createScope method on the ServiceContext.
Level: 1

Type: ERROR

Impact: Other

WCS-12983: Service {0} has not been configured for the application.

Cause: The Service has not been configured for the application.

Action: Configure the Service and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-12984: An error occurred removing the security policies for service {0}.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: ERROR

Impact: Other

WCS-12985: An error occurred invoking isProvisioned for service {0}.

Cause: The possible causes could be coding, application configuration, or hardware errors.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-12986: An error occurred invoking isEnabled for service {0}.

Cause: The possible causes could be coding or application configuration.

Action: Review the full exception stack for details of the exception.
Level: 1

Type: WARNING

Impact: Other

WCS-14001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14002: An object of type {0} with this id ({1}) already exits.

Cause: An attempt was made to create an object with an id that is already in use.

Action: Specify a unique id.
Level: 1

Type: ERROR

Impact: Other

WCS-14004: The name ({0}) is not valid.

Cause: The specified name is not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-14005: The specified list type could not be found.

Cause: The specified list type could not be found. This may be due to the list type being deleted by another user.

Action: Try reloading to see if the list has been deleted.
Level: 1

Type: ERROR

Impact: Other

WCS-14006: Object has been changed by another user.

Cause: The object has been changed by another user.

Action: Reload the object and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-14007: An Object of type {0} with id={1} could not be found.

Cause: The specified object could not be found. This may be due to the list being deleted by another user.

Action: Specify a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-14008: Object ({0}) is immutable.

Cause: An attempt to change this object was made, but this object is currently immutable.

Action: Retrieve mutable object to make changes.
Level: 1

Type: ERROR

Impact: Other

WCS-14010: {0} is not a valid reference name to MDS.

Cause: The name is not a valid MDS reference name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14011: The MDS session does not support updates.

Cause: MDS was not configured correctly to support updates.

Action: Configure the MDS store to support updates.
Level: 1

Type: ERROR

Impact: Other

WCS-14012: An IO error occurred when accessing metadata.

Cause: An IO error occurred in MDS.

Action: See the log for more details on the specific IO error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-14013: The object is not valid.

Cause: The metadata for the object does not pass validation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14014: Failed to construct attribute set for list [{0}].

Cause: Failed to construct attribute set for list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14015: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]

Cause: Failed to add data flavor to ListTransferable.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-14016: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-14017: An error occurred when deleting metadata.

Cause: An error occurred in MDS while deleting metadata.

Action: See the log for more details on the specific error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-14018: A column with the name ({0}) already exists.

Cause: A column was created or renamed with the name of an existing column in the list.

Action: Specify a unique column name within the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14019: A list with the name ({0}) already exists.

Cause: A list was created or renamed with the name of an existing list.

Action: Specify a unique list name.
Level: 1

Type: ERROR

Impact: Other

WCS-14020: The maximum number of columns for this list has been exceeded.

Cause: A list was created or modified with more than 30 columns.

Action: Do not add more than 30 columns to a list.
Level: 1

Type: ERROR

Impact: Other

WCS-14021: User does not have permission to perform {0} operation for {1}.

Cause: User does not have permission to perform the specified operation.

Action: Grant the user permission to perform the specified operation.
Level: 1

Type: ERROR

Impact: Other

WCS-14022: The Lists service is not provisioned for scope {0}.

Cause: The Lists service is not provisioned for the specified scope.

Action: Provision the Lists service for the specified scope.
Level: 1

Type: ERROR

Impact: Other

WCS-14023: The value is the wrong data type. The data type expected is {0}.

Cause: The value is the wrong data type.

Action: Use the value with the correct data type.
Level: 1

Type: ERROR

Impact: Other

WCS-14024: The WebCenter repository is not available.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14025: An error occurred accessing the WebCenter metadata repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14026: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-14027: List are not enabled for this portal or a parent portal.

Cause: Lists are not enabled in this portal.

Action: Enable lists if required by this portal.
Level: 1

Type: WARNING

Impact: Other

WCS-14028: Enabling lists failed.

Cause: An error occurred enabling lists.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14029: Lists not enabled for portal {0}.

Cause: Lists not enabled for the specified portal.

Action: Enable lists for the specified portal.
Level: 1

Type: ERROR

Impact: Other

WCS-14030: An error occurred registering the WebCenter list visualizations.

Cause: An error occurred registering visualizations..

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14031: An Object of type {0} with id={1} could not be deleted.

Cause: The specified object could not be deleted. This may be due to the a constraint.

Action: Check the constraints.
Level: 1

Type: ERROR

Impact: Other

WCS-14501: The list was not found.

Cause: The list could not be found.

Action: Remove the list view for the invalid list from the page.
Level: 1

Type: ERROR

Impact: Other

WCS-14502: Another user deleted the row while you modified it. Discard any unsaved changes, then refresh the list.

Cause: Another user deleted the row while you modified it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14503: Another user modified a row while you modified it. Discard any unsaved changes, then refresh the list.

Cause: Another user modified a row while you modified it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14504: Another user deleted the list after you displayed it. Discard any unsaved changes, then refresh the list.

Cause: Another user deleted the list after you displayed it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14505: Another user modified this list after you displayed it. Discard any unsaved changes, then refresh the list.

Cause: Another user modified this list after you displayed it.

Action: Discard any unsaved changes, then refresh the list.
Level: 1

Type: ERROR

Impact: Other

WCS-14506: Invalid minimum/maximum range

Cause: Minimum value must be less than or equal to maximum value.

Action: Modify the minimum value or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14507: Default value is out of range

Cause: Default value must be between the minimum and maximum values.

Action: Modify the default value, minimum value, or maximum value.
Level: 1

Type: ERROR

Impact: Other

WCS-14508: An error occurred accessing the WebCenter repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-14509: Your permission to perform this operation was revoked. Refresh the list and discard unsaved changes.

Cause: Your permission to perform this operation was revoked.

Action: Request permission to perform this operation.
Level: 1

Type: ERROR

Impact: Other

WCS-14510: The Lists service was disabled, preventing you from performing this operation. Refresh the list and discard unsaved changes.

Cause: The Lists service was disabled, preventing you from performing this operation.

Action: Enable the Lists service.
Level: 1

Type: ERROR

Impact: Other

WCS-14514: An unexpected error occurred. Please retry the operation.

Cause: An unexpected error occurred.

Action: Retry the operation. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-14515: Default value is too long

Cause: Default value must not exceed the maximum length.

Action: Modify the default value or maximum length.
Level: 1

Type: ERROR

Impact: Other

WCS-14516: The WebCenter metadata repository was temporarily unavailable. Please retry the operation.

Cause: The connection to the WebCenter metadata repository failed.

Action: Retry the operation. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-14517: Another user deleted the list after you displayed it. Discard any unsaved changes, then click Close to exit list edit mode.

Cause: Another user deleted the list after you displayed it.

Action: Discard any unsaved changes, then click Close to exit list edit mode.
Level: 1

Type: ERROR

Impact: Other

WCS-14518: Another user deleted the list. Click Close to exit list edit mode.

Cause: Another user deleted the list.

Action: Click Close to exit list edit mode.
Level: 1

Type: ERROR

Impact: Other

WCS-14519: The list row was not found.

Cause: The list row could not be found.

Action: None.
Level: 1

Type: ERROR

Impact: Other

WCS-14522: Lists are disabled, preventing you from performing this operation. Enable lists to continue making changes.

Cause: Lists are disabled, preventing you from performing this operation.

Action: Enable lists.
Level: 1

Type: ERROR

Impact: Other

WCS-18001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18002: Missing Configuration for List of Contacts. Could not locate the class {0}.

Cause: An incorrect class name was provided.

Action: Please contact Oracle Support.
Level: 1

Type: ERROR

Impact: Other

WCS-18003: Class {0} does not implement the interface {1}.

Cause: The specified class had not implemented the required interface.

Action: Ensure that the class implements the required interface.
Level: 1

Type: ERROR

Impact: Other

WCS-18004: Cannot instantiate class {0}.

Cause: The specified class did not have a default constructor accessible to public.

Action: Ensure that the class has a default constructor and it is accessible to public.
Level: 1

Type: ERROR

Impact: Other

WCS-18005: Cannot instantiate class {0}.

Cause: Either the specified class was not a concrete implementation or it did not have a default constructor accessible to public.

Action: Ensure that the class is a concrete implementation and has a default constructor accessible to public.
Level: 1

Type: ERROR

Impact: Other

WCS-18006: The implementation class {0} returned null.

Cause: The implementation class returned a null object.

Action: Ensure that the implementation class returns a non-null list of contacts.
Level: 1

Type: WARNING

Impact: Other

WCS-18007: An error occurred while trying to validate metadata.

Cause: Invalid metadata has been introduced.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18008: Unable to save the metadata in persistence store

Cause: An error occurred while writing to persistence store or metadata was locked by another user.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18009: Cannot apply the current metadata changes to a concurrently modified metadata.

Cause: Recent changes in this session conflicts with changes made in the same session.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18010: Cannot locate the requested metadata.

Cause: The metadata was not found in the configured metadata stores or it had been deleted on this session.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18011: Cannot obtain the metadata for write operations.

Cause: The metadata store could be spanning multiple back-end stores or concurrent updates were attempted.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18012: Metadata already exists in metadata store.

Cause: An attempt was made to create a metadata document when it already exists.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18013: The reference to the specified metadata is invalid.

Cause: The reference to the metadata was incorrect.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18014: Could not be complete the sort operation.

Cause: A null table component was returned.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18015: Could not get contact details.

Cause: The selected contact details were unavailable due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18016: Could not launch the dialog for view {0}.

Cause: Profile page details are unavailable due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18017: Could not perform a people search.

Cause: Instance of identity store is not available.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18018: Could not get display name from user profile.

Cause: User did not have the display name or user's profile was not accessible.

Action: Contact the administrator of directory services/webcenter.
Level: 1

Type: WARNING

Impact: Other

WCS-18019: Could not get name from user profile.

Cause: User does not have the name or user's profile is not accessible.

Action: Please contact the administrator of directory services/webcenter.
Level: 1

Type: WARNING

Impact: Other

WCS-18020: Could not save the search criterion.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18021: Could not fetch the search criterion.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18022: Could not fetch the sort criteria.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18023: Could not save the sort criteria.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18024: Cannot get an instance of the identity store

Cause: There was either an improper configuration or an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18025: Could not create the contacts list.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18026: Could not perform a people search.

Cause: An internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18401: An unexpected error occurred in the Message Board sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18402: Failed to create an instance of Message Board

Cause: Message Board viewing user name not found

Action: Make sure that the user is logged in
Level: 1

Type: ERROR

Impact: Other

WCS-18403: Failed to create an instance of Message Board

Cause: Message Board owner user name not specified

Action: Provide owner user name in the request for an instance of Message Board
Level: 1

Type: ERROR

Impact: Other

WCS-18404: Failed to persist Message Board message

Cause: An unexpected error occurred

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18405: Failed to publish Message Board activity

Cause: Activity Stream service raised an exception

Action: Verify the reason for the failure in the Activity Stream sub-system
Level: 1

Type: ERROR

Impact: Other

WCS-18406: Message Board message cannot be deleted

Cause: User is not authorized to delete this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18407: Failed to delete Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18408: Message Board message cannot be updated

Cause: User is not authorized to update this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18409: Failed to update Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18410: Message Board message cannot be added

Cause: Message content is empty

Action: Provide a non empty message board message text
Level: 1

Type: ERROR

Impact: Other

WCS-18411: Message Board message cannot be hidden

Cause: User is not authorized to hide message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18412: Failed to hide Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18413: Failed to retrieve user display name from profile service

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-18414: Failed to add message to Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18415: Failed to hide or unhide message in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18416: Failed to delete message in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18417: Failed to query messages in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18418: Failed to update message in Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18419: Failed to create an instance of Message Board.

Cause: Message Board preferences manager not specified

Action: Provide preferences manager in the request for Message Board
Level: 1

Type: ERROR

Impact: Other

WCS-18420: Failed to query preferences for Message Board.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18421: Message cannot be added to Message Board.

Cause: User is not authorized to add message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18422: Failed to retrieve Message Board message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18423: Failed to find the portal of the message board.

Cause: The portal doesn't exist.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18424: Failed to find the user of the message board.

Cause: The user doesn't exist.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18425: Failed to attach file to selected portal.

Cause: The portal does not exist or does not have document services configured.

Action: Contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18451: Unexpected error getting preference.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18452: Unexpected error saving preference.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18453: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}.

Cause: An unexpected error occurred.

Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-18501: Error retrieving the Profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18502: User: {0} not found in identity store.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18503: Personal status note can be changed only for the current user

Cause: attempt made by an user to update personal status of another user

Action: login as the user whose status you want to change
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18504: unexpected error operating on personal status note

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18505: unexpected error saving profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18506: User does not have the privilege required to access the user profile.

Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation.

Action: Contact the Administrator to grant the required permission, or contact the target user to allow access.
Level: 1

Type: ERROR

Impact: Other

WCS-18507: Insufficient Privilege.

Cause: Cannot Edit Profile.

Action: Contact Webcenter Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18508: Unexpected error retrieving user {0}''s photo

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18509: Unexpected error saving user {0}''s photo to the back-end. The photo may not have been saved. Please refresh to find out and then retry the operation.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18510: Unexpected error invalidating user {0}''s photo cache

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18511: User not specified

Cause: The supplied username was null or blank.

Action: Specify a valid username that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-18512: Unexpected error serving the requested photo {0}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18514: Unexpected error saving the Profile Admin Settings

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18515: Unexpected error saving the Profile user preference

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18516: Unexpected error initializing the admin config bean

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18517: Unexpected error saving the profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18518: Unexpected Error Initializing profile cache

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18519: Unexpected error doing cache operations on profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18520: Unexpected error retrieving unique identifier for user {0}''s photo

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18521: Unexpected error evaluating property ''{0}'' of base {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18522: Modifying property ''{0}'' of base {1} not allowed

Cause: The application does not allow modifying the value of the specified property of the specified base object.

Action: Ensure that property of the object being modified is not read-only.
Level: 1

Type: ERROR

Impact: Other

WCS-18523: Error getting the instant message address for the person

Cause: unexpected error getting the sip address

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18524: Error getting tag data

Cause: unexpected error getting tag data

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18525: Unexpected error saving attribute: {0}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with the error on the log.
Level: 1

Type: ERROR

Impact: Other

WCS-18526: User does not have the privilege required for updating the user profile

Cause: The system policy restricts the current user from updating the user profile.

Action: Contact the Administrator to obtain the required permission.
Level: 1

Type: ERROR

Impact: Other

WCS-18527: The image file {0} you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the image as the file is null or invalid.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-18528: Unexpected error instantiating object.

Cause: Unexpected error instantiating object.

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18529: Error instantiating profile (user name: {0}, GUID: {1})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18530: Unable to retrieve display name for profile (user name: {0}, GUID: {1}) in locale {2}. For diagnosis, turn on the logging level to FINEST and retry the operation. Error summary: {3}.

Cause: An unexpected error occurred.

Action: To diagnose the error, turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-18531: Error navigating the hierarchy

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18532: Unexpected error writing vcard

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18533: Unexpected error retrieving reporting chain

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18534: Unexpected error searching user profiles

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18535: User: {0} not found in identity store or user does not have the required privilege for updating the user profile.

Cause: Either user is not available in the user repository or system policy restriction is applied.

Action: contact the administrator
Level: 1

Type: ERROR

Impact: Other

WCS-18536: User Class type not expected, found: {0} expected{1}.

Cause: The User instance found in the cache is not of the expected Class type.

Action: Check if the Profile Service Lifecyle Listener is executed which sets the appropriate UserFactory.
Level: 1

Type: ERROR

Impact: Other

WCS-18537: Error updating {0} with {1} and {2}.

Cause: The cause of this error could be MetadataNotFoundException, UnsupportedUpdateException, MDSIOException, ConcurrentMOChangeException or ValidationException

Action: Check if the pages.xml is present, you have update permission on the document or if the pages.xml has some invalid content. If all the things listed are fine then try again after sometime.
Level: 1

Type: ERROR

Impact: Other

WCS-18540: Unknown error accessing assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18541: Action {0} cannot be executed on asset type {1}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18542: You do not have privileges to perform {0} on {1}.

Cause: The user does not have permission to perform the action on the given asset or asset type.

Action: Contact your administrator to give you privileges to perform the required action.
Level: 1

Type: WARNING

Impact: Other

WCS-18543: Unknown error while determining if user can access asset manager in scope {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18544: Unknown error while determining if user can access {0} asset type in asset manager in scope {1}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18545: Unknown error while deleting assets permission for scope {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-18546: Selected operation cannot be performed as the asset is already deleted, refresh the list using the refresh icon.

Cause: The asset on which the action is being performed does not exist.

Action: Refresh the list using the Refresh icon.
Level: 1

Type: ERROR

Impact: Security

WCS-18701: An unexpected error occurred in the Feedback sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18702: Failed to create an instance of Feedback

Cause: Feedback object's viewing user name not found

Action: Make sure that the user is logged in
Level: 1

Type: ERROR

Impact: Other

WCS-18703: Failed to create an instance of Feedback

Cause: Feedback object's user name not specified

Action: Provide user name in the request for an instance of Feedback
Level: 1

Type: ERROR

Impact: Other

WCS-18704: Failed to persist Feedback message

Cause: An unexpected error occurred

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18705: Failed to publish Feedback activity

Cause: Activity Stream service raised an exception

Action: Verify the reason for the failure in the Activity Stream sub-system
Level: 1

Type: ERROR

Impact: Other

WCS-18706: Feedback message cannot be deleted

Cause: User is not authorized to delete this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18707: Failed to delete Feedback message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18708: Feedback message cannot be updated

Cause: User is not authorized to update this message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18709: Failed to update Feedback message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18710: Feedback message cannot be added

Cause: User is not authorized to add message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18711: Feedback message cannot be hidden

Cause: User is not authorized to hide message

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18712: Failed to hide Feedback message

Cause: Message does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-18713: Feedback message cannot be added

Cause: Feedback message content is empty

Action: Provide a non empty feedback message text
Level: 1

Type: ERROR

Impact: Other

WCS-18714: Failed to retrieve user display name from profile service

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-18715: Failed to add feedback.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18716: Failed to hide or unhide feedback.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18717: Failed to delete feedback.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18718: Failed to query feedback messages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18719: Failed to create an instance of Feedback

Cause: Feedback object's preferences manager not specified

Action: Provide preferences manager in the request for an instance of Feedback
Level: 1

Type: ERROR

Impact: Other

WCS-18720: Failed to query preferences for Feedback object.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-18751: Unknown error accessing portal assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18752: Unknown error in instantiating portal assets factory

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18753: Unexpected error occurred while adding a portal asset.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18754: Unexpected error occurred while deleting a portal asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18755: Unexpected error occurred while updating a portal asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18756: Unexpected error occurred while getting the list of portal assets

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18757: Portal asset for update is not valid

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18758: An attribute in this asset is not valid.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18759: An error occurred in setting up the asset

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18760: Copy operation resulted in error. If you see the asset in asset manager, delete it.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18761: Delete operation resulted in error. If you see the asset in asset manager, try deleting it again.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services with logs.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18762: You do not have the privileges required to perform this operation.

Cause: No privilege to do the current operation

Action: Contact webcenter administrator for change in role.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18763: Asset with the same display name already exists.

Cause: An unexpected error occurred.

Action: Enter a new display name for the asset.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18764: An unexpected error occurred while trying to check {0} access for {1}, denying access.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-18765: Unable to import, as the asset being imported conflicts with another asset.

Cause: Another asset in the target has the metadata file or jspx with the same path as the asset being imported.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18766: Unable to import as the asset being imported conflicts with another asset of a different type in the same portal.

Cause: Either the metadata file or jspx with the same path already exists on the target application in same scope.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18767: Unable to validate the content of the archive. Import of asset is aborted.

Cause: Error while trying to check if a document exists in MDS.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18768: Unable to import as {1}, as the asset in the archive is of type {0}

Cause: Select the correct asset type to import.

Action: Select the correct asset type to import.
Level: 1

Type: ERROR

Impact: Other

WCS-18769: Encountered exception while trying to determine if path {0} points to an asset, resorting to default security check.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-18770: Asset with id "{0}" does not exist.

Cause: The asset was possibly deleted by another user.

Action: Refresh the asset manager to see if the asset still exists
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18771: Unable to export as the asset is type {0} but was invoked as {1}

Cause: Incorrect asset type

Action: Select the correct asset type to import.
Level: 1

Type: ERROR

Impact: Other

WCS-18772: Unable to upload as the asset belongs to {0} but is being uploaded into {1}

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18773: Unable to upload the asset. The owner of the asset is not valid.

Cause: Cannot identify the owner of the asset.

Action: The archive is corrupt with invalid documents. Contact Oracle Support Services and provide log information.
Level: 1

Type: ERROR

Impact: Other

WCS-18774: Global asset with ID "{0}" does not exist.

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18775: Asset with ID "{0}" does not exist in the portal "{1}".

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18776: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for the type of shared asset you are attempting to upload/download.

Cause: Verify that you have the appropriate Create/Edit/Delete permission.

Action: Contact your WebCenter Portal administrator to request the required permissions.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18777: You do not have the permissions required to perform the operation. Verify that you have the appropriate Create/Edit/Delete permission for all portal assets or for the specific type of portal asset you are attempting to upload/download.

Cause: Verify that you have the appropriate Create/Edit/Delete asset permissions for the portal.

Action: Contact the portal administrator to request the required permissions.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18778: Unable to upload as the archive does not contain a shared asset.

Cause: The asset you are trying to upload belongs to a specific portal, it is not a shared asset.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18779: Unable to upload the asset as the archive does not contain an asset that belongs to this portal.

Cause: The asset you are trying to upload belongs to a different portal.

Action: Verify which portal owns the asset and then upload the asset to that portal.
Level: 1

Type: ERROR

Impact: Other

WCS-18780: Global asset of type "{2}", with name "{0}" does not exist.

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18781: Asset of type "{2}", with name "{0}" does not exist in the portal "{1}".

Cause: The specified asset was probably deleted by another user.

Action: Refresh the list of assets to see if the asset still exists.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18782: Name or Resource Id of the resource to be exported is not specified. Specify either the name or the Id of the resource.

Cause: Name or ID of the resource to be exported in not mentioned.

Action: Specify either the name or the ID of the resource.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18783: Name, Resource Id and type of the resource to be exported do not match.

Cause: Name, Resource Id and type of the resource to be exported do not match.

Action: Specify either the name or the ID of the resource.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-18784: Asset is a system asset. You cannot export system assets.

Cause: The asset you are trying to export is a system asset.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-18785: Asset is a system asset. You cannot import system assets.

Cause: The asset you are trying to import is a system asset.

Action: Refer to import documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19001: Unexpected error occurred

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19002: Unable to execute operation on {0}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19003: Metadata file {0} not found

Cause: The expected metadata file was not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19004: Unexpected error occurred while creating page table

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19005: Internal error while creating policy store metadata for {0}

Cause: Policy store for WebCenter Portal not found

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19007: Unable to copy application or portal policies for {0}

Cause: Exception occurred while copying policies for WebCenter Portal.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19008: No matching users were found with search string {0}

Cause: No users matched the search string you entered: {0}

Action: Enter a new search term and try again
Level: 1

Type: ERROR

Impact: Other

WCS-19010: Couldn''t retrieve metadata for role {0}

Cause: No roles matched the search string you entered: {0}

Action: Enter a new search term and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19013: User not specified

Cause: A null or empty string was provided for the user name.

Action: Enter a valid user name.
Level: 1

Type: ERROR

Impact: Other

WCS-19014: Role not specified

Cause: A null or empty string was provided for the role name.

Action: Enter a valid role name.
Level: 1

Type: ERROR

Impact: Other

WCS-19016: Unable to grant user {2} with role {1} in {0}

Cause: An attempt to grant a user role failed. Either, role {1} does not exist, user {0} does not exist, or the user is already granted the role

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19017: Unable to revoke role {1} from identity {0}

Cause: An attempt to grant a identity role failed. Either, role {1} does not exist,identity {0} does not exist, or the identity does not have the specified role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19018: Unable to add role {0} to the policy store

Cause: An attempt to create a new role failed. Either the role already exists, or the policy store is currently unavailable

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19019: An error occurred while trying to remove role {0} from the policy store

Cause: An attempt to delete the specified role failed. Either the role does not exist, or the policy store is currently unavailable.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19020: Identity {0} has already been granted the role(s).

Cause: User has been already granted the same role.

Action: Determine the cause and, if necessary, try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19022: Role {0} already exists in the policy store

Cause: An attempt to create a new role failed because the policy store contains a role with the name specified.

Action: Enter a unique name for the role.
Level: 1

Type: ERROR

Impact: Other

WCS-19025: Only authenticated users can perform the requested operation

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your WebCenter Portal administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19026: Unable to revoke permission {0}

Cause: The specified permission was not removed from the policy store. The permission may not exist

Action: Check whether the permission exists in the policy store
Level: 1

Type: ERROR

Impact: Other

WCS-19027: Unable to grant permission {0}

Cause: The user was not granted the specified permission. The user may already be assigned that permission.

Action: Check whether the user is assigned this permission.
Level: 1

Type: ERROR

Impact: Other

WCS-19029: Policy for WebCenter Portal could not be found

Cause: Policy for WebCenter Portal was missing from the policy store.

Action: Check the policy store for WebCenter Portal is configured correctly.
Level: 1

Type: ERROR

Impact: Other

WCS-19030: Page definition for page {0} not found

Cause: Page definition for page {0} does not exist.

Action: Check whether the page definition for page {0} exists
Level: 1

Type: ERROR

Impact: Other

WCS-19031: Policy store instance cannot be null

Cause: No policy store instance was found

Action: Verify and instantiate the policy store instance and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-19032: Security Manager already initialized

Cause: An attempt was made to initialize the Security Manager but it was already initialized.

Action: Use the existing Security Manager.
Level: 1

Type: ERROR

Impact: Other

WCS-19033: Security Manager is not initialized

Cause: A security operation was attempted before the Security Manager was initialized.

Action: Initialize the Security Manager and try again
Level: 1

Type: ERROR

Impact: Other

WCS-19034: WebCenterSecurityManager class cannot be initialized directly

Cause: An attempt was made to initialize the WebCenterSecurityManager class through a protected constructor.

Action: Initialize the WebCenterSecurityManager class with a default constructor.
Level: 1

Type: ERROR

Impact: Other

WCS-19035: Security Manager is null

Cause: Security Manager could not be initialized

Action: Use valid parameters and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-19036: Scoped Security Manager is null for scope {0}

Cause: Security manager can not be initialized

Action: Please try to initialize again with proper parameters
Level: 1

Type: WARNING

Impact: Other

WCS-19037: Invalid context {1} for scope {0}

Cause: Current scope did not match the cached scope

Action: Refresh your page again and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19038: An error occurred while importing security policies.

Cause: Failed to create security policies (grants, roles and permissions) during import.

Action: Verify that the export archive is valid, otherwise check logs for error details and contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19039: ADFContext is NULL, so returning NULL as username

Cause: An internal error occurred while fetching the user name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19040: SecurityContext is NULL, so returning NULL as username

Cause: SecurityContext was not found for the current session

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19042: Unable to retrieve Personal Sidebar items

Cause: An error locating for opening the JSPX document for the Personal Sidebar

Action: Ensure that the JSPX document pointing to the Personal Sidebar is available to the application
Level: 1

Type: ERROR

Impact: Other

WCS-19043: Unable to persist personalization for tag with webcenterId ''{0}'' in the Personal Sidebar

Cause: An error saving the personalization document for the Personal Sidebar JSPX, or the tag with this webcenterId could not be located.

Action: Ensure that the personalization is enabled on the Personal Sidebar JSPX, and the tag has a unique webcenterId
Level: 1

Type: ERROR

Impact: Other

WCS-19044: Unable to retrieve item called {0} from the shell in the request {1}

Cause: Either the item name is incorrect or the item is not available in the current shell context

Action: Verify that the item name is correct and that the shell context is setup properly for the current request.
Level: 1

Type: WARNING

Impact: Other

WCS-19045: Unable to register shell handler of type {0}

Cause: Either the class name of the shell handler is incorrect or there was a problem while instantiating the shell handler

Action: Verify whether the shell handler type is correct or determine why the shell handler is not instantiating properly
Level: 1

Type: WARNING

Impact: Other

WCS-19046: Unable to retrieve the visibility of shell panel {0}

Cause: An error occurred trying to retrieve the visibility information from the shell handler of the current request.

Action: Defaulting visibility to 'true'
Level: 1

Type: WARNING

Impact: Other

WCS-19048: Unable to retrieve panel metadata for panel properties (panel name: {0})

Cause: The metadata for the panel in the shell metadata document may be corrupted or missing, or the name of the panel is incorrect.

Action: Verify whether the panel name is correct and whether the metadata for the panel is valid
Level: 1

Type: ERROR

Impact: Other

WCS-19049: An attempt to set change the skin was ignored

Cause: An attempt was made to change the skin but this feature is not yet implemented.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19051: An attempt was made to set the template and ignored

Cause: This change would not take place as the feature is not implemented

Action: Please contact Oracle Support for more details
Level: 1

Type: WARNING

Impact: Other

WCS-19054: Error retrieving a physical page view-id for the request {0} (context URL {1})

Cause: The request URL could be invalid, or an unknown problem occurred fetching the metadata

Action: Verify the request URL and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19055: Unable to display a page for the requested URL {0}

Cause: The request URL was invalid, either because there was no shell handler or the shell handler could not provide a physical page to forward to.

Action: Verify the request URL and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19058: Unable to retrieve scope IDs for the current user

Cause: An internal error occurred while fetching the scope for the current user.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19061: Unable to INSTANTIATE shell handler factory of type {0}

Cause: Shell handler factory of type {0} was not in the classpath.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19062: Unable to INITIALIZE the shell handler factory

Cause: An internal error occurred while initializing the shell handler factory.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19066: Unable to set up the default shell handler factory.

Cause: An internal error occurred while setting up the default shell handler factory.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19067: Unable to navigate to the page. Page creation might have failed or an error occurred while attempting to load the new page. Open your Manage Pages dialog box to see if the page exists. If the problem persists, contact your administrator.

Cause: An error occurred trying to reference the newly created page (the page may not have been created properly).

Action: Try to selecting the new page from the pages dropdown list. If the page is not listed, try creating the page again
Level: 1

Type: ERROR

Impact: Other

WCS-19068: Unable to create page in the current scope

Cause: An unexpected error occurred while trying to create a page in a scope.

Action: Ask your WebCenter Portal administrator to resolve the issue.
Level: 1

Type: ERROR

Impact: Other

WCS-19070: Unable to delete page {0} ({1})

Cause: An attempt to delete a page failed. Either the page and/or its associated files (for example, ADFm page definition) have been modified but not saved

Action: Verify that the page is not being modified and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19071: Page {0} ({1}) not deleted properly. Unable to remove associated metadata.

Cause: An attempt was made to delete a page when metadata associated with the page was in use.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19072: Unable to retrieve the list of users

Cause: An attempt to retrieve the user list failed.Either the Identity store was corrupt or is inaccessible.

Action: Verify that the identity store is valid and accessible, and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19073: Unable to register page {0} (of scope {1}) for navigation

Cause: An error occurred while registering the page {0}.

Action: Try to register the page again and if unsuccessful contact Oracle Support.
Level: 1

Type: WARNING

Impact: Other

WCS-19075: No users available

Cause: No users found in the identity store associated with WebCenter Portal.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19077: Permission class {0} does not have proper constructor method

Cause: The specified class does not have the required constructor

Action: Provide the required constructor in the specified class
Level: 1

Type: ERROR

Impact: Other

WCS-19079: Unable to process the security extension metadata

Cause: The argument is not an instance of ExtensionPermissionMetadata

Action: Provide an instance of ExtensionPermissionMetadata as the argument
Level: 1

Type: ERROR

Impact: Other

WCS-19080: Unable to access permission class {0} in your project libraries

Cause: Either the specified permission class does not exist or it is not in the correct location.

Action: Ensure that the specified permission class is in the correct location.
Level: 1

Type: ERROR

Impact: Other

WCS-19082: Unable to load up the {0} service.

Cause: An internal error occurred and the {0} service failed to load.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19083: Access to permission class {0} is not allowed

Cause: An attempt was made to access the specified permission class.Permission class {0} is not accessible.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19084: Permission class{0} can not be instantiated

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19085: Unable to instantiate the policy store for WebCenter Portal

Cause: An error occurred while trying to access the policy store associated with WebCenter Portal.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19088: Failed to register application management beans

Cause: Application management beans(MBean) registration failed.Either there are issues with OC4J or the application was not packaged properly.

Action: Restart OC4J or examine OC4J log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19089: Failed to unregister application management beans

Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.

Action: Examine the OC4J log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-19090: An unexpected error has occurred, unable to complete the export process.

Cause: The export process failed due to an internal error.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19101: Unable to save the export archive on the local file system due to an unexpected error.

Cause: Unexpected error occurred while saving the export archive on the local file system.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19102: Unexpected error occurred while exporting the security policy. Unable to export the policy store.

Cause: An unexpected error occurred while exporting policy store metadata to the local file system.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19104: Unable to export connection details for external application with ID {0}

Cause: An internal error occurred. Unable to retrieve details for an external application appearing in WebCenter Portal.

Action: Ask your WebCenter Portal administrator to clean up external applications appearing in the Sidebar or reconfigure the external application connection using Enterprise Manager.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19105: Unable to find connection details for external application with ID {0}

Cause: No connection details found for external application with the specified ID.

Action: Remove the external application link associated with the specified ID from the Applications pane in the Sidebar.
Level: 1

Type: WARNING

Impact: Other

WCS-19106: Unable to save preference settings

Cause: An error occurred while attempting to save preferences settings to the metadata store.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19107: Invalid date format {0} retrieved from the preference store.

Cause: An attempt was made to retrieve date information but the source date format was invalid.

Action: Verify whether the date format source returns the correct date format.
Level: 1

Type: WARNING

Impact: Other

WCS-19108: Invalid time format {0} retrieved from the preference store.

Cause: An attempt was made to retrieve time information but the source time format was invalid.

Action: Verify whether the time format source returns the correct time format
Level: 1

Type: WARNING

Impact: Other

WCS-19109: Unable to find service.

Cause: Unable to find the service metadata in WebCenter Portal

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19119: Unable to add the new link : {0}

Cause: An attempt to add a new link {0} to the metadata store failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19120: Unable to add link as no proper handler found for the selected resource type

Cause: An attempt to add a new link but the resource being added is neither a task flow or an external application.

Action: Only task flows or external application link can be included.
Level: 1

Type: ERROR

Impact: Other

WCS-19121: Unable to retrieve the shell configuration metadata

Cause: The metadata file is corrupt or missing.

Action: Ensure that the file exists and complies with the schema.Alternatively, contact your WebCenter Portal administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19122: Invalid shell panel name

Cause: The shell panel name was probably NULL.

Action: Provide a valid shell panel name.
Level: 1

Type: ERROR

Impact: Other

WCS-19123: Unable to retrieve the shell handler for the current request {1}

Cause: The shell handler was not set for the current request

Action: Verify the URL and that the WebCenter Portal shell filter is configured to handle requests of this kind
Level: 1

Type: WARNING

Impact: Other

WCS-19124: Unable to save changes to shell metadata

Cause: An error occurred while saving the shell metadata document.

Action: Ensure that the shell metadata document is not corrupt and is writeable and personalizable.
Level: 1

Type: ERROR

Impact: Other

WCS-19125: Account for user {0} is disabled

Cause: The account for user {0} account is disabled.

Action: Ask the WebCenter Portal administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19126: Account for user {0} is inactive

Cause: The account for user {0} is disabled.

Action: Ask the WebCenter Portal administrator to activate the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19127: The account for user {0} is locked

Cause: The account is locked for user {0}

Action: Ask the WebCenter Portal administrator to unlock the account.
Level: 1

Type: ERROR

Impact: Other

WCS-19128: Password has expired for user account {0}

Cause: Password for this user has expired

Action: Contact the WebCenter Portal administrator for assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19129: Incorrect Old Password for user account {0}

Cause: The old password specified for this user is not correct.

Action: Enter the correct password
Level: 1

Type: ERROR

Impact: Other

WCS-19130: Password for user account {0} is null

Cause: No password was specified.

Action: Enter a valid password.
Level: 1

Type: ERROR

Impact: Other

WCS-19131: Error occurred granting permissions to user {0} for the newly created page {1}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter Portal administrator
Level: 1

Type: WARNING

Impact: Other

WCS-19132: Unable to retrieve the permission target for page {0}

Cause: An unexpected error occurred. The ADFm page definition of the page may be missing

Action: Ensure that the page definition exists and is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19133: Unable to determine the page in focus

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19134: Unable to hide a page, locked by another user

Cause: An attempt was made to hide a page that is currently locked by another user.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19135: No page selected for hiding

Cause: Unable to determine which page has focus.

Action: Select the page you want to hide and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19136: Unable to hide the page.

Cause: An attempt was made to hide the last open page.

Action: Open some other page and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19137: Unable to determine the page focus for hiding

Cause: Unable to determine which page has focus.

Action: Select the page you want to hide and try again. Alternatively, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19138: Unable to encode the value {1} of parameter {0} using encoding format {2}

Cause: The encoding format was unexpectedly invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19139: Unable to decode the value {1} of parameter {0} using encoding format {2}

Cause: The encoding format was unexpectedly invalid.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19140: Unable to update the page titled {0} ({1})

Cause: An error occurred while saving the changes.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19141: Unable to save changes to the metadata store

Cause: An error occurred while saving the changes.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19142: Role mapping SPIs are throwing exception

Cause: An internal occurred error while accessing role mapping SPIs.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19143: Unable to retrieve the catalog for adding applications

Cause: An attempt to access the external application catalog failed. Either the external application catalog is not configured or configuration details are unavailable.

Action: Check whether the ext-app-catalog attribute is configured in webcenter-config.xml
Level: 1

Type: ERROR

Impact: Other

WCS-19144: Role name for user account is null or contains invalid characters

Cause: Either the role name was left blank or the role name contained invalid characters.

Action: Enter a valid role name.
Level: 1

Type: ERROR

Impact: Other

WCS-19145: Operation succeeded with errors. The mapping of roles failed

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19146: Grant role completed with errors The mapping of roles failed in scope {0}

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19147: Page path can not be null

Cause: The specified page path is null or an empty string.

Action: Provide a valid string for the page path.
Level: 1

Type: ERROR

Impact: Other

WCS-19148: Cannot get the service categories metadata from the application metadata

Cause: Service category metadata has not been defined in the application metadata

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19149: Cannot get metadata for all services from the application metadata.

Cause: All service metadata has not been defined in the application metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19150: Cannot get metadata for configurable services from the application metadata

Cause: Metadata for configurable services has not been defined in the application metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19151: Cannot find a service with the ID {0}

Cause: No definition exists for a service with the specified service identifier

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19152: User {0} already has access.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19153: Edit the user to modify his role.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19154: This exception is due to one or more of the following exceptions -

Cause: One or more services configurations have failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19155: User {0} already has access or is invited.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19156: You cannot send an invite to this user as an invite has already been sent.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19157: Portal {0} may have been deleted or renamed

Cause: An attempt was made to access a portal that has been deleted or renamed.

Action: Contact the portal moderator or try searching for the portals.
Level: 1

Type: ERROR

Impact: Other

WCS-19158: Cannot personalize visibility of page {0} in portal {1}

Cause: A personalization attempt failed. Either the backing store could not be accessed or some other personalization operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19159: Unable to save page creation

Cause: An attempt to save the new page failed. Either the back-end store could not be accessed or another page was created simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19160: Unable to save the personal sequence of pages in scope {0}

Cause: An attempt to personalize the page sequence failed. Either the back-end store could not be accessed or some other personalization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19161: Unable to save the change in sequence of pages in scope {0}

Cause: An attempt to change page sequence failed. Either the back-end store could not be accessed or a similar operation was performed simultaneously.

Action: Try the operation again. If the problem persists, contact your WebCenter Portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19162: Revoke role completed with errors The mapping of roles failed

Cause: Changes in services failed due to the following errors

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19163: Scope is NULL for Security Manager

Cause: Scope identifier passed to the security manager is NULL.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19164: The security policy in the archive file was found to be invalid.

Cause: The imported security policy file was found to be invalid.

Action: Export the data again and try the import operation again.
Level: 1

Type: WARNING

Impact: Other

WCS-19165: The security policy in the archive file to be imported is invalid as it contains more than one jazn-policy node.

Cause: The imported security policy file is invalid as it contains more than one jazn-policy node.

Action: Export the data again the import operation again.
Level: 1

Type: WARNING

Impact: Other

WCS-19166: The security policy in the archive file to be imported is located on a read-only file system and this means the data cannot be updated.

Cause: The imported security policy file is located on a read-only file system and this means the data cannot be updated.

Action: Export the data again and try the import operation again.
Level: 1

Type: WARNING

Impact: Other

WCS-19167: Failed to import security configuration from the selected archive.

Cause: An unexpected error occurred while updating the deployed application in the import source archive.

Action: Check the logs for details of the error.Alternatively, contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19168: Role {0} is created successfully but failed to copy the permissions from role {1}. The role {1} is not found.

Cause: An attempt to create the role failed because the base role was not found.

Action: Check whether the base role is still available.
Level: 1

Type: ERROR

Impact: Other

WCS-19169: An error occurred while trying to remove a role {0} from the policy store.

Cause: The specified role does not exist in the policy store.

Action: Check the details of the error and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19170: Application role {0} still used in the policy store

Cause: The specified role is in use.

Action: Remove the usage of the role and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19171: Application role {0} to be granted is not found

Cause: Specified role was not found.

Action: Check the role name {0} and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19172: Internal error while creating security manager for portal {0}

Cause: Unable to resolve the Scope GUID for Scope {0}

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19173: New passwords for user account {0} do not match

Cause: Passwords were entered incorrectly.

Action: Enter the correct passwords.
Level: 1

Type: ERROR

Impact: Other

WCS-19174: Few of the mandatory resource(s) are in use. Please try again later.

Cause: The lock, client is trying to release is already locked.

Action: Try after some time
Level: 1

Type: ERROR

Impact: Other

WCS-19175: Unable to release the lock on document {0}

Cause: A call to release lock in the back-end has failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19176: Releasing the current lock on {0} failed

Cause: The lock, client is trying to release is already released.

Action: Acquire the lock again to release.
Level: 1

Type: ERROR

Impact: Other

WCS-19177: Name Cannot Be Null

Cause: Name Cannot Be Null

Action: Enter a User or Group
Level: 1

Type: WARNING

Impact: Other

WCS-19178: User Not Found

Cause: User Not Found

Action: Enter a username
Level: 1

Type: WARNING

Impact: Other

WCS-19179: Group not found or multiple groups with the same name exist.

Cause: Group not found or multiple groups with the same name exist

Action: Enter a Group
Level: 1

Type: WARNING

Impact: Other

WCS-19180: User with this name doesn't exist

Cause: User with this name doesn't exist

Action: Enter a role which has users
Level: 1

Type: WARNING

Impact: Other

WCS-19181: Unable to read the application configuration metadata

Cause: The metadata file could have got corrupt or removed

Action: Please ensure that the file exists and complies with the schema, or contact the administrator for assistance
Level: 1

Type: ERROR

Impact: Other

WCS-19182: Unable to move link/folder

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19183: Unable to create folder {0}

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19184: Unable to delete link/folder {0}

Cause: The metadata file could have got corrupt or removed

Action: Contact Oracle Support Services
Level: 1

Type: ERROR

Impact: Other

WCS-19185: Role cannot be created because it contains special characters

Cause: Creation of Role {0} failed because it contains special characters

Action: Remove special characters used in your role and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19186: Role {0} cannot be created, as the role of same name exists in the policy store

Cause: Creation of Role {0} failed because policy store already contains a role of same name

Action: Try changing role name
Level: 1

Type: ERROR

Impact: Other

WCS-19187: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed. You can take actions regarding these warnings in portal settings.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19188: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed. You can take actions regarding these warnings in portal settings.

Cause: revoking of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19189: Mapping the permissions {0} failed. You may want to try the operation again after some time or can contact Administrator.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19190: Fatal Error while granting role for certain services.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19191: User(s) {0} has already been granted the role {1}.

Cause: Current User / Role {0} has been already granted the application role.

Action: Don't Provision this user since it is already provisioned.
Level: 1

Type: ERROR

Impact: Other

WCS-19192: Role has been granted with errors. You might want to contact Administrator or Remove/Grant Role again.

Cause: Role was granted with errors.

Action: Contact the Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19193: Fatal Error while granting the role.

Cause: Fatal Error while granting the role.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19194: Invitations were sent out but persisting the invited users data resulted in fatal error.

Cause: Members Fatal Error while granting the role.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19195: Page {0} cannot be found in the system

Cause: The page may have been deleted or the page path is incorrect

Action: Specify a correct path to an existing page
Level: 1

Type: ERROR

Impact: Other

WCS-19196: {0} : Irresolvable error(s) occurred. You may want to contact Administrator with the error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19197: {0} : Unexpected error(s) occurred. You may want to contact Administrator with the error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19198: {0} : Unknown error(s) occurred. You may want to contact Administrator with the error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19199: {0} : Multiple errors occurred {1}

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19200: Fatal error while removing some grants. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19201: Fatal error while removing the role. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19202: Revoking role was partially successful. You can try this operation again after some time or contact Administrator.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19203: Fatal error while creating the role. Please contact Administrator with error reference.

Cause: Fatal Error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19204: Unable to save Invite message for portal {0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while obtaining the invite message

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19205: Unable to save member changes for a portal{0} due to unknown errors. Please try later or contact administrator

Cause: Error occurred while saving the member changes

Action: Try later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19206: Could not find security policy in the archive file being imported.

Cause: The security policy file was not found in import archive.

Action: Export the data again and try the import operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-19207: One or more mandatory roles are not found in the copied instance for scope {0}. Role Name: {1}

Cause: One or more mandatory roles are not found in the copied instance.

Action: Add the mandatory role {1} in the security metadata to get WebCenter Portal functionality or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19208: Deletion of security metadata failed for scope {0}

Cause: Deletion of roles for the current scope {0} has failed.

Action: Try later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19209: An unexpected error occurred while trying to upload WebCenter Portal logo to path {0}

Cause: MDS StreamedObject creation failed for WebCenter Portal logo

Action: Contact administrator for further assistance.
Level: 1

Type: ERROR

Impact: Other

WCS-19210: The image upload failed as the image file you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the WebCenter Portal logo as the file is null or not available.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19211: An error occurred while trying to retrieve the templates to be used for page creation. Please contact Administrator with error reference.

Cause: An unexpected error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19212: An error occurred while trying to determine the template selected for page creation. Please contact Administrator with error reference.

Cause: An unexpected error occurred.

Action: Contacts the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19213: Unable to persist customization for tag with webcenterId ''{0}'' in the Personal Sidebar

Cause: An error saving customizations on the Personal Sidebar JSPX, or the tag with this webcenterId could not be located.

Action: Ensure that the customization is enabled on the Personal Sidebar JSPX, and the tag has a unique webcenterId
Level: 1

Type: ERROR

Impact: Other

WCS-19214: Failed to get the custom page permission for pageDef {0} for action {1}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19215: Failed to get the roles having permission {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19216: Failed to get the users having permission {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19217: Unable to get list of links

Cause: An error occurred while getting the list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19218: An error occurred while saving the page default settings. The settings may not have been saved.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19219: Unexpected error occurred while deleting the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19220: Search for role {0} resulted in more than one result. Please contact Administrator to get it rectified

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19221: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.

Cause: While copying the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19222: Unknown error in adding link to the table

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19223: Unknown error in retrieving the link information

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19224: Unknown error in updating the link information

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19225: Unknown error in deleting the link

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19226: Unable to close connection

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19227: Unexpected error occurred while restoring the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19228: Unexpected error occurred while creating list of pages

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19229: Error occurred in getting the complete list of pages you can access. Please contact the administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19230: Invalid page name

Cause: Invalid page name

Action: Please enter a valid page name.
Level: 1

Type: ERROR

Impact: Other

WCS-19231: Unexpected error occurred while creating the page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19232: While provisioning the services, errors were encountered for following services - {0}. Check if these services have been configured correctly.

Cause: While provisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19233: While renaming all the provisioned services, errors were encountered for following services - {0}.

Cause: While renaming the portal, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19234: While unprovisioning the services, errors were encountered for following services - {0}.

Cause: While unprovisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19235: Unknown error occurred. Please contact Administrator.

Cause: Unknown error occurred.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19236: The following service(s) are currently unavailable: {0}. If the problem persists contact your administrator.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19237: Unable to export the portal {0}. Either the portal does not exist or the portal is being exported/imported by another user. Refresh the portal list and try again.

Cause: Unable to acquire a lock on the scope of portal.

Action: Refresh the portal list and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19238: Unable to export the portal template {0}. Either the portal template does not exist or the portal template is being exported/imported by another user. Refresh the portal template list and try again.

Cause: Unable to acquire a lock on the scope of portal template.

Action: Refresh the portal template list and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19239: Unable to import portals as required resources are not available. Portals being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal list and try again.

Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portals.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19240: Unable to import portal templates as required resources are not available. Portal templates being replaced on the target either do not exist or are being exported/imported by another user. Refresh the portal template list and try again.

Cause: Unable to acquire a global lock to prevent create, delete, rename or import operations on portal templates.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19241: Errors occurred in the page.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19242: Unexpected error occurred while accessing copyright message.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19243: Unexpected error occurred while accessing privacy URL.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19244: Unexpected error occurred while accessing footer information.

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19245: An error occurred while saving the page security settings. The settings may not have been saved.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19246: Error occurred while refreshing the table of pages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19247: Modification of role operation not supported for scope {0}

Cause: Currently the modification of role not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19248: Portal {0} being exported is either online or being exported/imported by another user. Wait for some time and try the export operation again.

Cause: Portal is either online or blocked by another user/process.

Action: Refresh the portal list and try to export the portal again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19249: Portal template {0} you are trying to export is being exported/imported by another user. Wait for some time and try the export operation again.

Cause: Portal template is blocked by another user/process.

Action: Refresh the portal template list and try to export the portal template again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19250: Portal template {0} you are trying to import is being exported/imported by another user on the target. Wait for some time and try the import operation again.

Cause: Portal template is blocked by another user/process.

Action: Wait for some time and try to import the portal template again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19251: You are trying to import portals but the archive specified contains portal templates. Check the archive file and try again.

Cause: You are trying to import portals but the archive specified contains portal templates.

Action: Use an export archive that contains portals.
Level: 1

Type: ERROR

Impact: Other

WCS-19252: You are trying to import portal templates but the archive specified contains portals. Check the archive file and try again.

Cause: You are trying to import portal templates but the archive specified contains portals.

Action: Use an export archive that contains portal templates.
Level: 1

Type: ERROR

Impact: Other

WCS-19253: Cannot locate the document ''{0}''.

Cause: The path is incorrect or it is not available in the system.

Action: Verify whether the path is correct and is available in the system.
Level: 1

Type: ERROR

Impact: Other

WCS-19254: Error occurred while reading the WebCenter Portal environment configuration file {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19255: Unexpected error occurred while navigating to portal administration pages.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19256: Error occurred while saving the folder.

Cause: An unexpected error occurred while saving the folder.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19257: Unexpected error occurred while acquiring the write lock on the document {0}.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19258: Error occurred while clearing the deleted/renamed portal page.

Cause: Error occurred while clearing the deleted/renamed portal page.

Action: Error occurred while clearing the deleted/renamed portal page.
Level: 1

Type: ERROR

Impact: Other

WCS-19259: Portal "{0}" on the target application is either online or being exported/imported by another user. Wait for some time and try the import operation again.

Cause: Portal either online or blocked by another user/process.

Action: Wait for some time and try the import operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19260: The current process could not be executed. Wait for some time and try again.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19261: Error occurred while saving administration changes.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19262: Another administrator is modifying the setting. Try again later.

Cause: An unexpected error occurred while saving administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19263: Fatal error occurred while getting the roles for current scope.

Cause: An unexpected error occurred while getting the roles.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19264: Fatal error occurred while inviting user {0} for role {1}

Cause: An unexpected error occurred while getting the members.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19265: Fatal error occurred while getting members.

Cause: An unexpected error occurred while getting the members.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19266: Fatal error occurred while getting invitation message from the repository.

Cause: An unexpected error occurred while getting message.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19267: Error occurred while reading the list of tabs from persistence store.

Cause: An unexpected error occurred while reading the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19268: Following error occurred while storing the list of tabs to persistence store - {0}

Cause: An unexpected error occurred while storing the list of tabs.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19269: Error in processing the pages.

Cause: Unexpected error occurred while adding the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19270: Error in processing the pages.

Cause: Unexpected error occurred while removing the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19271: Error in processing the pages.

Cause: Unexpected error occurred while finding the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19272: Error in processing the pages.

Cause: Unexpected error occurred while creating the menu model.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19273: Error in navigation.

Cause: Unexpected error occurred while navigating to secondary page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19274: Error in processing the pages.

Cause: Unexpected error occurred while preparing the children.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19275: Error in processing the pages.

Cause: Unexpected error occurred while preparing the page for current request.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19276: Error in navigation.

Cause: Unexpected error occurred while getting the navigable path to the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19277: An error occurred while changing the page visibility. Refresh the page list and retry.

Cause: Unexpected error occurred while changing the page's visibility.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19278: Error in renaming the page.

Cause: Unexpected error occurred while changing the page name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19279: Error in creating a copy of the page.

Cause: Unexpected error occurred while copying the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19280: The role name {0} is reserved, please use some other name.

Cause: Unexpected error occurred while creating the role name.

Action: Try creating a role with some other name.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19281: Unexpected error occurred while refreshing list of pages.

Cause: Unexpected error occurred while refresh.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19282: Unable to save the BusinessRole sequence of pages.

Cause: An attempt to customize the BR page sequence failed. Either the back-end store could not be accessed or some other customization operation was performed simultaneously

Action: Try the operation again. If the problem persists, contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19283: Error in reordering the pages.

Cause: Unexpected error occurred while reordering the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19284: Error in reordering the business role pages.

Cause: Unexpected error occurred while reordering the business role pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19285: Error in reordering the pages.

Cause: Unexpected error occurred while reordering the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19286: Error in moving the page up.

Cause: Unexpected error occurred while moving the page up.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19287: Error in moving the page down.

Cause: Unexpected error occurred while moving the page down.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19288: Error in processing the pages.

Cause: Unexpected error occurred while closing the page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19289: Unexpected error in closing page(s).

Cause: Unexpected error occurred while closing the pages.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19290: Unexpected error in getting list of moderators.

Cause: Unexpected error occurred while getting the list of moderators.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19291: Unexpected error occurred in getting the page Uri for the favorites.

Cause: Unexpected error occurred while getting the Uri for the favorites.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19292: Unexpected error occurred in creating the new folder.

Cause: Unexpected error occurred while creating a new folder.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19293: Unexpected error occurred while getting the list of favorites.

Cause: Unexpected error occurred while getting the list of favorites.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19294: Unexpected error occurred while trying to navigate to bookmark.

Cause: Unexpected error occurred while trying to navigate to bookmark.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19295: Error occurred while reverting administration changes.

Cause: An unexpected error occurred while reverting administration changes.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19296: The application failed to access backend data store and cannot process requests

Cause: Access to backend data store failed

Action: Ensure the back-end data store that contains the WebCenter Portal schema and MDS schema is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-19297: The URL typed by current user is not accessible, so redirecting to the unAuthorized page

Cause: The current user does not have privileges to see the current URL

Action: Please contact system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19298: Unexpected error occurred, please retry the operation

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19299: Unexpected error occurred while preparing the administration pages

Cause: An internal error occurred

Action: Retry the operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-19300: Unexpected error trying to restore the Login page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19301: Unexpected error trying to navigate to the Login page

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19302: Unexpected error trying to open the Login page for edit

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19303: Unexpected error occurred while moving a page to top of the pages list

Cause: Unexpected error occurred while moving a page to top of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19304: Unexpected error occurred while moving a page to bottom of the pages list

Cause: Unexpected error occurred while moving a page to bottom of the pages list

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19305: Drag and drop is not allowed for ungrouped view

Cause: Drag and drop was attempted in ungrouped view

Action: Drag and drop operation is not allowed for ungrouped view
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19306: Reorder of personal pages is not allowed here

Cause: A personal page was selected as either the drag source or the drop target

Action: Exclude personal pages from drag and drop operations
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19307: Unexpected error occurred while creating mandatory document.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19308: Failed to grant a role {1} to identity {0} in scope {2}

Cause: Failed to find identity {0} in Identity Store while Granting a role {1} in scope {2}

Action: Create a new Identity {0} in Identity Store and try again
Level: 1

Type: WARNING

Impact: Other

WCS-19309: Unexpected error retrieving services for configuration

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19310: Unexpected error occurred while trying to retrieve list of languages

Cause: Unexpected error occurred while trying to retrieve list of languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19311: Error occurred granting role {0} in {1}. Refresh the members list to see which users were added successfully. Some errors are displayed below. Contact your administrator for a complete list of errors.

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19312: Identities : {0}, failed with the errors {1}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19313: Setting {0} role for {1} failed. Please contact Administrator

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19314: Portal template {0} is an out-of-the-box template. You cannot export out-of-the-box portal templates.

Cause: Portal template is an out-of-the-box template.

Action: Refer to export documentation for more information or contact your administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19315: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.

Cause: One or more portal pages are being edited by other users. You cannot export when pages are in edit mode.

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19316: One or more pages of portal {0} are being edited by other users. Wait for some time and try again.

Cause: One or more portal pages are being edited by other users. You cannot import when pages are in edit mode..

Action: Close all the pages from edit mode or contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19317: An unexpected error has occurred while sending notification to the administrator.

Cause: An unexpected error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19318: Granting of Role {0} partially succeeded for identity {1}. Granting permissions for {2} failed.

Cause: Granting of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19319: Revoking of Role {0} partially succeeded for identity {1}. Revoking permissions for {2} failed.

Cause: revoking of Role for certain Services failed due to RoleMapping Exception

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19320: File {0} in location {1} already exists. Do you want to overwrite it?

Cause: File already exists in the location where the export archive is being saved.

Action: Enter a new location or overwrite the file.
Level: 1

Type: ERROR

Impact: Other

WCS-19321: Issues were faced while provisioning the service(s) - {0}. Check the portal services settings page if these services have been provisioned.

Cause: While provisioning the services, errors were encountered for certain services.

Action: Contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19322: You do not have sufficient permission to edit the page.

Cause: Your permission to edit the page might have been revoked.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19323: The image file {0} you tried to upload was invalid. Provide a valid image file.

Cause: Unable to upload the image as the file is null or invalid.

Action: Upload a valid image file
Level: 1

Type: ERROR

Impact: Other

WCS-19324: An error occurred while cleaning the pages from persistence store for current user.

Cause: An unexpected error occurred while cleaning the list of pages.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19325: One needs to login to access this url {0}

Cause: Public Users don't have access to this url

Action: Please login first.
Level: 1

Type: ERROR

Impact: Other

WCS-19326: Couldn''t invalidate joc region {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19327: Could not delete joc region {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19328: Could not add object {1} to joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19329: Could not replace object {1} in joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19330: Could not retrieve object {1} from joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19331: Could not invalidate object {1} in joc region {0} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19332: Unexpected error occurred while processing roles in {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19333: Unexpected error occurred while processing users in {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19334: Unexpected error occurred while retrieving all users who have been assigned {0} in {1}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19335: Could not validate user due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19336: Unexpected error occurred while retrieving enterprise roles for user {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19337: Unexpected error occurred while retrieving application role {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19338: Could not retrieve display name for user {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19339: Unable to retrieve user mail ID for {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19340: Unable to retrieve members mailing list for {0} due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19341: Could not verify lifecycle block status due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19342: Unexpected error occurred while retrieving users / groups who have been granted application role {0}

Cause: An unexpected error occurred.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19343: Unable to send notification to administrator(s). The reason is : {0}.

Cause: The BPEL server is not configured

Action: Configure workflows.
Level: 1

Type: ERROR

Impact: Other

WCS-19344: User(s) {0} has already been invited to portal.

Cause: An unexpected error occurred while inviting users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19345: Errors occurred in inviting user(s) to join the portal {1} as role {0}. Please refresh the members list below to see the latest status about the invited users. Some of the errors are displayed below( Please note that following list may not be listing all the errors. For the complete list of errors, please contact the administrator).

Cause: An unexpected error occurred while inviting users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19346: User {0} not invited to portal {1}.

Cause: User {0} not invited to portal {1}.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19347: The default shell-config document cannot be read for looking up application-specific URL parameters, due to {0}.

Cause: The metadata repository might be down or the document may have got corrupted.

Action: Verify that the metadata repository is up and the document contents are valid.
Level: 1

Type: WARNING

Impact: Other

WCS-19348: Error occurred during permissions related operations. Refresh the roles screen to see the updated information. Contact your administrator for the list of errors.

Cause: An unexpected error occurred during permission related operations.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19349: Could not find application role matching the search string {0} due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19350: Removing rolemapping related to service {0} failed due to {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19351: Could not send notification to administrator as server may be down or Portal workflows are not accessible. Try again after some time.

Cause: Failed to connect to SOA server.

Action: Check if the SOA server is up or if Portal workflows are deployed on SOA server.
Level: 1

Type: ERROR

Impact: Other

WCS-19352: Unable to complete the export process as required resources are not available. Another export or import process might be in progress. Please try export again after sometime.

Cause: Export operation failed. Either another export process or portal operation is in progress.

Action: Wait for some time and try the export operation again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19353: Import failed. The portal archive contains new portals without security information.

Cause: The portal archive you are trying to import contains new portals without security. All new portals must include security information.

Action: Export the portals again with security and try again. If the problem persists, contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19354: The page {0} (in {1}) cannot be copied due to {2}.

Cause: An error occurred while trying to copy the page.

Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19355: Unable to make updates to the attributes of the page {0} due to {1}.

Cause: An error occurred while trying to make updates to the page attributes.

Action: Refine the logging level, retry the operation, and check the logs for more information about the error, or contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19356: Unable to open the requested page.

Cause: An unexpected error while opening the page or while creating a copy of it for editing.

Action: Contact the administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19357: Could not find the page label due to {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19358: Identity(s) {0} has already been added to portal.

Cause: An unexpected error occurred while adding users.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19359: You cannot invite yourself as a member.

Cause: Operation not allowed.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19360: Could not retrieve the role {0}. Please contact administrator.

Cause: An unexpected error occurred.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19361: Could not find the page visibility due to {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19362: You cannot add yourself as a member.

Cause: Operation not allowed.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19363: SDP Messaging URL cannot be obtained due to {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19364: Unable to compute context URL for page {0} with title {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19365: Unable to change password. Contact administrator.

Cause: An unexpected error occurred while setting the password.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19366: Export failed. The export process took too long to complete. Use the export WLST command to perform this export operation.

Cause: Export timeout occurred. Either the export set is too large or the policy store information to be exported is too large.

Action: Try exporting fewer portals or use WLST to perform the export operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19367: Import failed. The import process took too long to complete. Use the import WLST command to perform this import operation.

Cause: Import timeout occurred. Either the import set is too large or the policy store information to be imported is too large.

Action: Try importing fewer portals or use WLST to perform the import operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19368: Could not find the secondary tab for the current request. PrimaryTab found : {0}, SubTabs : {1}, LastAccesedPage(From previous session) : {2}, Page service cache : {3}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19369: Get Member Info not supported for scope

Cause: Currently get Member Info not supported.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19370: You can not invite a group for the portal subscription

Cause: Inviting group is not supported

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19371: Failed to read the notification message from backend datastore

Cause: Notification message is null, try setting it

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19372: Group name is empty

Cause: Given group name is empty

Action: Please pass the correct group name
Level: 1

Type: ERROR

Impact: Other

WCS-19373: Granting of role {0} failed for identities {1}.

Cause: Exception occurred while granting a role {0} to identities {1}

Action: Please check the log for actual error stack.
Level: 1

Type: ERROR

Impact: Other

WCS-19374: Group {0} grant to {1} failed for users {2}. The following users are already granted a role: {3}

Cause: An internal error occurred

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19375: Group {0} is not found in Identity Store

Cause: Given group name is not found

Action: Please pass the correct group name
Level: 1

Type: ERROR

Impact: Other

WCS-19376: {0} User(s) including {1} have already been granted role(s).

Cause: User(s) already granted roles.

Action: User(s) already granted roles.
Level: 1

Type: ERROR

Impact: Other

WCS-19377: Group(s) {0} has already been granted role(s).

Cause: Group(s) already granted role(s)

Action: Group(s) already granted role(s)
Level: 1

Type: ERROR

Impact: Other

WCS-19378: Unable to grant role mapping permissions for role {0} in scope {1}

Cause: The role was not granted role mapping permissions. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19379: Unable to drop role mapping permissions for role {0} in scope {1}

Cause: There was an error while dropping role mapping permissions for the role. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19380: Unexpected error while restoring the Default Profile Gallery Page.

Cause: There was an error while removing the profile page customization. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19381: Unexpected error occurred while setting the language

Cause: Unexpected error occurred while trying to save the language choice

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19382: Copying of members failed for following identities {0}

Cause: Copying of members failed for following identities {0}.

Action: Try again after some time or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19383: Operation not allowed on child portal {0}

Cause: Child portal does not support the operation.

Action: Perform on correct parent portal or Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19384: Unexpected error occurred while getting the list of page templates

Cause: Unexpected error occurred while getting the list of Page Templates

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19385: Unexpected error occurred while getting the list of Resource Catalogs

Cause: Unexpected error occurred while getting the list of Resource Catalogs

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19386: Unexpected error occurred while getting the languages

Cause: Unexpected error occurred while trying to retrieve the languages

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19387: Unexpected error occurred while creating translations for the imported portal.

Cause: Unexpected error occurred while creating the translations.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19388: Unexpected error occurred while collapsing the sidebar

Cause: Unexpected error occurred while

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19389: Unexpected error occurred while expanding the sidebar

Cause: Unexpected error occurred while

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19390: Unexpected error occurred while getting the list of recently accessed portals.

Cause: Unexpected error occurred while getting the list of recently accessed portals.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19391: Unexpected error downloading vcard

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19392: Unexpected error looking up user profile

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19393: Unexpected error launching resource

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19394: Unexpected error occurred while getting the list of portals current user can access.

Cause: Unexpected error occurred while getting the list of portals current user can access.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-19395: A page named {0} already exists.

Cause: A page with the specified name exists.

Action: Specify a unique name for the page.
Level: 1

Type: ERROR

Impact: Other

WCS-19396: Unexpected error while restoring the Default Page.

Cause: There was an error while removing the page customization. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19397: Unexpected error while changing the permission model for portal {0}.

Cause: Unexpected error while changing the permission model for portal {0}.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19398: No users/groups selected

Cause: No users/groups were selected to perform the requested operation on.

Action: Select one or more users/groups and retry the operation.
Level: 1

Type: ERROR

Impact: Other

WCS-19399: Exception occurred while searching groups for a user :{0}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19400: Failed to determine public access on page {0} due to {1}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19401: "Unexpected error getting read lock on {0}

Cause: An unexpected error/exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19402: Error determining the template for the current page

Cause: Unexpected severe error.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19403: Error occurred while fetching the list of navigations.

Cause: Unexpected error while fetching list of navigations.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19404: Scope list cannot be empty.

Cause: Unexpected error while fetching list of portals.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19405: Unable to set the security parent of {0} to {1}.

Cause: Unexpected error while setting the security parent.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19406: Unable to delete base docs from archive.

Cause: Unexpected error while deleting base docs from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19407: Resources conflict. Base resource on target is not same as the base resource on source. Import cannot proceed.

Cause: Resources conflict occurred at the target.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19408: Unable to flush changes for deleted base docs from archive.

Cause: Unexpected error while deleting base docs from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19409: Could not create site registry as folder does not exists.

Cause: Unexpected error while creating the site registry.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19410: Error occurred while refreshing template cache.

Cause: Unexpected error occurred while refreshing template cache.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19411: {0}.

Cause: Unexpected error while fetching list of navigations.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19412: Error occurred while saving the custom attributes in metadata.

Cause: Unexpected error occurred while saving the custom attributes in metadata.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19413: Error occurred while granting permission to portal {0} for the provisioned service(s).

Cause: Unexpected error occurred while granting permission.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19414: Error occurred while checking for portal permission.

Cause: Error occurred while checking community manage permission.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19415: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19416: Check for valid repository failed.

Cause: Either the database is down or the WebCenter Portal repository is not installed.

Action: Check the exception's details to why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WCS-19417: For user {0}, the last accessed page couldn''t be found due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19418: For user {0}, couldn''t clean the last accessed page due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19419: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-19420: Unexpected error occurred while checking custom access for the portal {0}.

Cause: Likely the authorizer class specified in WebCenter Portal configuration could not be accessed. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-19421: Denying access for scope {0} as {1} property not specified in WebCenter Portal configuration

Cause: The authorizer class is not specified against specified property in WebCenter Portal Configuration

Action: Define the specified property pointing to the required ResourceAuthorizer implementation in WebCenter Portal configuration
Level: 1

Type: WARNING

Impact: Other

WCS-19422: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}

Cause: Grant Role to Role Mapped Service for Portal User role not supported in scope {0}.

Action: Do not try this operation in this scope
Level: 1

Type: ERROR

Impact: Other

WCS-19423: Grant Role to Role Mapped Service for Public User role not supported in scope {0}

Cause: Grant Role to Role Mapped Service for Public User role not supported in scope {0}.

Action: Do not try this operation in this scope
Level: 1

Type: ERROR

Impact: Other

WCS-19424: Unable to delete site resource registry file from archive.

Cause: Unexpected error while deleting site resource registry file from archive.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19425: Checking whether portal is published to Portal user is not supported in Home Portal.

Cause: An attempt was made to check whether the portal is published to Portal user in Home portal.

Action: This API must be invoked in the context of portal and not Home portal
Level: 1

Type: ERROR

Impact: Other

WCS-19426: Encountered exception: {0}. For diagnosis, turn on the logging level to FINEST and retry the operation. Details about the current state: {1}

Cause: An exception was encountered unexpectedly.

Action: Turn on the logging level to FINEST and retry the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-19427: Error in setting Show Page of the business role page.

Cause: Unexpected error occurred while setting Show Page of the business role page.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19428: Unexpected error occurred while importing the security policy. Unable to import the policy store.

Cause: An unexpected error occurred while importing policy store metadata from the import archive.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-19429: Unexpected error occurred while checking if the current user can {0} the scope {1}.

Cause: Unexpected error occurred while checking if the current user can {0} the scope {1}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19430: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.

Cause: Unexpected error occurred while checking if the current user can {0} the asset {1} in scope {2}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19431: Unexpected error occurred while fetching roles for user {0} in portal {1}.

Cause: Unexpected error occurred while fetching roles for user {0} in portal {1}.

Action: Try again later or contact administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19432: Fetching the roles of current user is not supported in default scope.

Cause: Fetching the roles of current user is not supported in default scope.

Action: Do not try this operation
Level: 1

Type: ERROR

Impact: Other

WCS-19433: Unexpected error occurred while setting action {0} to role {1}.

Cause: Unexpected error occurred while setting action {0} to role {1}.

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-19434: Fatal error occurred while getting members count.

Cause: An unexpected error occurred while getting the members count.

Action: Please contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19435: Couldn''t get the first accessible page for the Home portal due to {1}.

Cause: Error in getting the first accessible page for the Home portal.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19436: The community query permission is not found

Cause: The community query permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19437: The community manage membership permission is not found

Cause: The community manage membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19438: The community view membership permission is not found

Cause: The community view membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19439: The community edit membership permission is not found

Cause: The community edit membership permission is not found.

Action: Contact the application administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-19440: One or more pages of portal {0} is being edited by other users. The export archive may not contain the page changes.

Cause: One or more portal pages is being edited by other users. The export archive may not contain the page changes.

Action: Close all pages open in edit mode and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19441: One or more pages of portal {0} is being edited by other users. The import may not complete properly.

Cause: One or more portal page is in edit mode. The import may not complete properly.

Action: Close all pages open in edit mode and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-19442: The method {0} is currently not supported.

Cause: There is no implementation for this method.

Action: Do not use this API.
Level: 1

Type: ERROR

Impact: Other

WCS-19443: Unexpected error occurred while creating the experience definition document due to {0}.

Cause: Unexpected error occurred while creating the experience definition document.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19444: Unexpected error occurred while extracting the rules parameters due to {0}.

Cause: Unexpected error occurred while extracting the rules parameters.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19445: Unexpected error occurred while evaluating the rules due to {0}.

Cause: Unexpected error occurred while evaluating the rules.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19446: Unexpected error occurred while loading the experience defintion due to {0}.

Cause: Unexpected error occurred while evaluating the rules.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19447: Unexpected error occurred while loading the experience rules due to {0}.

Cause: Unexpected error occurred while evaluating the rules.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19448: Unexpected error occurred while loading the experience definition document due to {0}.

Cause: Unexpected error occurred while loading the experience definition document.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19449: Unexpected error occurred while checking if the experience defintion is enabled due to {0}.

Cause: Unexpected error occurred while checking if the experience defintion.

Action: Try again later or contact administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19450: Unable to fetch custom property {0} at the application level

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: WARNING

Impact: Other

WCS-19451: Unable to fetch custom property {0} from scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: WARNING

Impact: Other

WCS-19452: Could not initialize Default Portal Setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19453: Could not update the default portal identity settings

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19454: Could not update the default portal public setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19455: Could not update the default portal default setting

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19456: Could not set the redirect on login setting for default portal

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Other

WCS-19457: Could not update default portal settings to handle rename of portal from {0} to {1}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details. Change the portal manually in Administration screens
Level: 1

Type: ERROR

Impact: Other

WCS-19458: Could not update default portal settings to handle delete of portal {0}

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details. Change the portal manually in Administration screens
Level: 1

Type: ERROR

Impact: Other

WCS-19459: The default portal configuration is being modified by another user. Try operation after some time.

Cause: >Another admin user is updating the default portal configuration

Action: Try the operation after some time
Level: 1

Type: WARNING

Impact: Other

WCS-19460: Could not fetch the default portal configuration from webcenter-config

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Go the Default Portal Configuration screen and change the default setting to desired values
Level: 1

Type: WARNING

Impact: Other

WCS-19461: Invalid input - unmatched quotes

Cause: A string was provided with unmatched quotes.

Action: Ensure all quotes are opened and closed.
Level: 1

Type: ERROR

Impact: Other

WCS-19462: Unexpected error while fetching the default portal due to {0}

Cause: Unexpected error while fetching the default portal

Action: Unexpected error while fetching the default portal
Level: 1

Type: WARNING

Impact: Other

WCS-19463: User {0} does not have the privileges required for this operation. Verify that the user has the 'Manage All' permission for Portals/Portal Templates which is required to perform this operation.

Cause: Check if the user has the 'Manage All' permission on Portals

Action: Try performing the operation as an administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-19464: User {0} not authorized to view Application.

Cause: User not authorized to view Application

Action: Contact Administrator to grant more permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-19465: User {0} not authorized to configure Application.

Cause: User not authorized to configure Application

Action: Contact Administrator to grant more permissions.
Level: 1

Type: ERROR

Impact: Other

WCS-19466: Error occurred in creating translated scope resource bundle {0} due to {1}.

Cause: Unexpected error while creating scope resource bundle for newely created Portal/Template.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-19467: Error occurred while parsing document name due to {0}.

Cause: Unexpected error while parsing scope resource bundle file name.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-19468: Unexpected error occurred while adding Business Role Page for Impersonation due to {0}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19469: Error occurred while adding Impersonation page:{0} to pages:{1} due to {2}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-19470: Error occurred while granting navigation permissions for role {0} for the scope {1} due to {2}

Cause: An unexpected error occurred while granting the user permission

Action: Contact the WebCenter Portal administrator
Level: 1

Type: WARNING

Impact: Other

WCS-20001: Error while creating the blog {0}.

Cause: Error while creating the blog.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20002: Error while deleting the blog {0}.

Cause: Error while deleting the blog.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20003: Error while creating the blog entry {0}.

Cause: Error while creating the blog entry.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20004: Error while deleting the blog entry {0}.

Cause: Error while deleting the blog entry.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20005: Error while deleting the blog container {0}.

Cause: Error while deleting the blog container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20006: Error while creating the blog container {0}.

Cause: Error while creating the blog container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20007: Error while editing the blog entry {0}.

Cause: Error while editing the blog entry.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20010: No Blog Selected

Cause: No blog was seleced! Hence couldnot complete operation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20011: No Container Selected

Cause: No container was seleced! Hence couldn't complete operation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20013: No Blog Entry Selected

Cause: No entry was selected! Hence couldn't complete the operation

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20014: Error while listing the blogs.

Cause: Error while listing the blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20015: Error while listing the blog container.

Cause: Error while listing the blog container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20016: Error while listing the blog entries.

Cause: Error while listing the blog entries.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20017: No Blog Container Found.

Cause: No Blog Container Found

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20018: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-20020: Error while listing the recent blogs.

Cause: Error while listing the recent blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20021: Error while listing the popular blogs.

Cause: Error while listing the popular blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-20022: Error while listing the favourite blogs.

Cause: Error while listing the popular blogs.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-23001: unexpected error has occurred

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26001: Search Configuration Error: {0}

Cause: A configuration error has been encountered.

Action: Refer to the error details and the documentation for how to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26021: Invalid Query {0}.

Cause: An invalid query was sent.

Action: Query validity is dependent on the service running it. Refer to the query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26022: Contradiction caused when clause "{0}" is added to "{1}"

Cause: An unexpected programming error occurred. This is not something that can be fixed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26023: The addition of criteria to {0} existing date criterion is not supported

Cause: An unexpected programming error occurred. This is not something that can be fixed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26041: General Search Execution Error

Cause: A general execution error has been encountered.

Action: Query execution error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26042: The execution of the query does not complete within the execution time limit

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: ERROR

Impact: Other

WCS-26061: General Search Response Error

Cause: A general response error has been encountered.

Action: Query execution response error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26062: Query results are immutable; removing elements from it is unsupported.

Cause: A caller tried to remove an element from the result set.

Action: Inform the caller that this is not a supported function.
Level: 1

Type: ERROR

Impact: Other

WCS-26063: SQL ResultSet consumption failed with the message "{0}".

Cause: A SQL ResultSet cannot be consumed.

Action: Refer to the underlying exception to debug this.
Level: 1

Type: WARNING

Impact: Other

WCS-26064: Cannot call "remove" method before calling "next" method.

Cause: Caller tried to call "remove" method of QueryResult class before calling "next" method.

Action: Inform the caller that this is an illegal operation.
Level: 1

Type: ERROR

Impact: Other

WCS-26065: Cannot convert "{0}" value to "{1}".

Cause: The target object had no "valueOf" method to convert the source.

Action: No action is needed; appropriate contingencies have been applied.
Level: 1

Type: WARNING

Impact: Other

WCS-26066: Parameter type {0} cannot be converted into a primitive type.

Cause: The conversion failed because the bean property was not of primitive type.

Action: No action is needed; appropriate contingencies have been applied.
Level: 1

Type: WARNING

Impact: Other

WCS-26081: General Search Authentication Error

Cause: A general authentication error has been encountered.

Action: Query execution authentication error is dependent on the service running it. Refer to the Query in the log and the documentation for the service involved to debug this.
Level: 1

Type: ERROR

Impact: Other

WCS-26091: Search API Implementation error in {0} class

Cause: An implementation error has been encountered.

Action: Report to the provider of the Search API Implementation.
Level: 1

Type: ERROR

Impact: Other

WCS-26101: An error occurred while parsing an XML document at {0}.

Cause: The XML document in question may not be well-formed or valid with respect to the referred XML schema.

Action: Examine the XML document again and check the XML schema to make sure there are not any mistakes or typos.
Level: 1

Type: ERROR

Impact: Other

WCS-26102: An error occurred while parsing the search configuration in adf-config.xml at {0}.

Cause: The XML fragment within adf-config.xml may not be well-formed or valid with respect to what is expected for search configuration.

Action: Examine the adf-config.xml document again and check the documented XML schema to make sure there are not any mistakes or typos.
Level: 1

Type: ERROR

Impact: Other

WCS-26103: An unexpected XML error occurred.

Cause: Something with the underlying XML system or implementation of JAXP failed unexpectedly.

Action: Check the nested exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-26121: A general MDS error has occurred.

Cause: An MDS-related error has occurred. Something with the MDS setup is misconfigured.

Action: Check the nested exception for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-26122: An MDS error has occurred because a Metadata Object by the name of {0} cannot be found.

Cause: An MDS Metadata Object was not found.

Action: Check the details of the Metadata Object and check the MDS repository to confirm that it is there.
Level: 1

Type: ERROR

Impact: Other

WCS-26123: Encountered "{0}" with message "{1}" when committing MDS changes.

Cause: Something within the current MDS Session cannot be committed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26124: Saved Search Deletion aborted because the Metadata Object (MO) Reference for ID "{0}" is not found.

Cause: The system is in an inconsistent state allowing deletion of non-existent MDS documents

Action: There is nothing to be done about this. No deletion is performed.
Level: 1

Type: WARNING

Impact: Other

WCS-26125: Encountered "{0}" with message "{1}" while formulating the final MDS Condition.

Cause: Some MDS conditions that are being joined caused a failure to come up with the final condition.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26126: MDS query result is null

Cause: MDS query result set is null. The MDS repository might be unavailable.

Action: Perform the operation again after MDS repository becomes available again.
Level: 1

Type: ERROR

Impact: Other

WCS-26141: A configuration error has occurred for the Search service model. The offending configuration is {0}.

Cause: The Search service keeps its configuration in adf-config.xml, connections.xml, and MDS.

Action: Check in the appropriate configuration files to see if there are any obvious erroneous data.
Level: 1

Type: ERROR

Impact: Other

WCS-26142: A security error has occurred for the Search service model. The offense is {0}.

Cause: The Search service model security maintained by the service caused a failure.

Action: Check the security settings for each underlying service to identify any anomalies.
Level: 1

Type: ERROR

Impact: Other

WCS-26143: Failed to commit changes to Search preferences, encountering {0}.

Cause: Some underlying MDS issues with the Preferences implementation is causing the failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26144: An error occurred while parsing the default full crawl interval "{0}".

Cause: An internal error occurred while trying to instantiate a DatatypeFactory for parsing Duration values.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-26145: An invalid full crawl interval "{0}" was specified in adf-config.xml.

Cause: The fullCrawlInterval attribute of the crawl-properties element in adf-config.xml may not be well-formed or valid.

Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.
Level: 1

Type: WARNING

Impact: Other

WCS-26146: An invalid full crawl interval "{0}" was specified for service {1}.

Cause: The fullCrawlInterval attribute of a service-crawl-properties element in adf-config.xml may not be well-formed or valid.

Action: Make sure that the fullCrawlInterval attribute value is in the duration format as defined in the W3C XML Schema 1.0.
Level: 1

Type: WARNING

Impact: Other

WCS-26147: An error occurred while parsing the crawl-properties element in adf-config.xml.

Cause: An internal error occurred while trying to parse the crawl-properties element in adf-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-26161: Encountered a message from MDS indicating unsupported operation while deleting a Saved Search with ID "{0}", MO Reference name "{1}", and MO Absolute Name "{2}".

Cause: The deletion of a Saved Search triggered some MDS operation that is not supported on said Saved Search document.

Action: Contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26162: A saved search with name "{0}" already exists, use a different name.

Cause: The name you provided is used already.

Action: Use a different name when saving your searches.
Level: 1

Type: ERROR

Impact: Other

WCS-26163: Duplicated identifier found while adding a saved search with a identifier "{0}" with Metadata Object name "{1}"; replacing with "{2}".

Cause: The system is in an inconsistent state where an old ID is used on a new Saved Search.

Action: This is a cautionary message only. Appropriate actions will be taken to fix the uniqueness issue.
Level: 1

Type: WARNING

Impact: Other

WCS-26164: Encountered an MDS exception "{1}" with message "{2}" while querying for saved searches with condition "{0}".

Cause: An underlying MDS exception occurred during the query execution.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26165: Failed to retrieve a Saved Search in MDS with Metadata Object reference name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26166: Failed to retrieve most recent Saved Searches in MDS with Metadata Object reference name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26167: Encountered an MDS exception "{2}" with message "{3}" while saving a saved search with Metadata Object name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Refer to MDS documentation to resolve a lookup failure with the given details.
Level: 1

Type: ERROR

Impact: Other

WCS-26168: Encountered an MDS exception "{2}" with message "{3}" while deleting a saved search with Metadata Object name "{0}", and absolute name "{1}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26169: Encountered an MDS reference exception "{1}" with message "{2}" while retrieving Saved Search Metadata Object reference in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26170: Saved Search Update aborted because the Metadata Object (MO) Reference for ID "{0}" is not found.

Cause: This can be due to an MDS misconfiguration issue.

Action: Refer to MDS documentation to resolve a lookup failure with the given details.
Level: 1

Type: WARNING

Impact: Other

WCS-26171: Encountered an MDS exception "{1}" with message "{2}" while creating a document with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26181: Failed to retrieve UI Metadata in MDS with Metadata Object reference name "{0}", and absolute name "{1}".

Cause: This can be due to an MDS misconfiguration issue.

Action: Refer to MDS documentation to resolve a lookup failure with the given details.
Level: 1

Type: WARNING

Impact: Other

WCS-26182: Encountered an MDS exception "{2}" with message "{3}" while adding a UI Metadata with identifier "{0}" and Metadata Object name "{1}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26183: Encountered an MDS exception "{1}" with message "{2}" while querying for UI Metadata with condition "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26184: Encountered an MDS reference exception "{1}" with message "{2}" while looking up UI Metadata Object reference in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception caused this.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26185: Encountered an MDS exception "{0}" with message "{1}" while creating default service list in MDS.

Cause: An underlying MDS exception occurred during the creation of the service list in the Search UI Metadata.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26186: Encountered an MDS exception "{1}" with message "{2}" while updating UI Metadata Object in MDS with Metadata Object absolute name "{0}".

Cause: An underlying MDS exception occurred during the update of the Search UI Metadata.

Action: The update by this user will be lost. Refresh the page and continue.
Level: 1

Type: ERROR

Impact: Other

WCS-26201: Encountered "{2}" with message "{3}" when loading QueryManager Class "{0}" for service "{1}" in Extension Handler.

Cause: Any one of the possible exceptions resulting from loading a class using reflection occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26202: Search Extension Registry loading failed, encountering "{0}" with message "{1}".

Cause: There may be misconfiguration in the adf-config.xml file.

Action: Check your adf-config.xml to see if the Search extension registry is declared. Make sure that the version numbers match those specified in the documentation.
Level: 1

Type: ERROR

Impact: Other

WCS-26203: Cannot access children, encountering "{0}" with message "{1}".

Cause: Encountered a Search exception when trying to extract children executors from a Query Federator

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26204: Failed in creating a Row QueryHandler for "{0}", encountering "{1}" with message "{2}".

Cause: A run time or Search exception was encountered. This can be due to the creation process timing out or any service-specific creation failure.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26205: {0} occurred during the preparation of Query Handler with identifier "{1}".

Cause: The Query Handlers are prepared in parallel; the preparation failed because of underlying concurrency mechanism.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26206: Creation of Row QueryHandler did not complete within the time limit for executor {0}.

Cause: The time allowed to create a Row QueryHandler is not sufficient.

Action: If this problem is persistent, increase the value of prepareExecutionTimeoutMs parameter in adf-search-config section of adf-config.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-26221: Search execution was interrupted because of "{0}" with message "{1}".

Cause: The service search execution was interrupted because of a timeout or a failure.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26222: Search execution failure for service "{0}", encountering "{1}" with message "{2}".

Cause: An exception occurred while executing search.

Action: Examine the log to determine the root cause and take appropriate debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26223: Search executors not initialized due to null Query.

Cause: Query is not set so no Query Executors have been initialized.

Action: No action is necessary; this is just a diagnostic message.
Level: 1

Type: WARNING

Impact: Other

WCS-26224: Query Handler creation of {0} was interrupted.

Cause: The Query Handler named took too long to be created and was timed out.

Action: Increase your prepareTimeoutMs value in the search-config section of the adf-config.xml file
Level: 1

Type: WARNING

Impact: Other

WCS-26225: {0} occurred during Search result transfer of service with identifier "{1}" with message "{2}"

Cause: An unexpected exception occurred when transferring search results after execution.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26226: Failed to extract Refiners from executor {0}.

Cause: Failure occurred when extracting refiners from the execution results of an executor.

Action: Inspect the failure message and fix accordingly.
Level: 1

Type: WARNING

Impact: Other

WCS-26227: Column not found for {0}

Cause: When formulating an query with a condition based on an attribute, the attribute is not found.

Action: Inspect your input and make sure that the values for the attributes are one of "name", "title", "description", "creator", "created", "modifier", "modified", and "tags".
Level: 1

Type: WARNING

Impact: Other

WCS-26228: Parsing of date operand "{0}" failed

Cause: When formulating an query with a condition based on a date attribute, the date value specified fails to be parsed.

Action: Inspect your date attribute and make sure that it follows the format: "yyyy-MM-dd"
Level: 1

Type: WARNING

Impact: Other

WCS-26229: Search query execution timed out for service "{0}".

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: WARNING

Impact: Other

WCS-26322: Skipping consumption of a Date ComplexPredicate with 1 child because its type {0} is not AttributePredicate<Calendar> as expected.

Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for its single child.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26323: Skipping consumption of a Date ComplexPredicate with 2 children because their types {0} and {1} are not AttributePredicate<Calendar> as expected.

Cause: A Date ComplexPredicate was passed down from the query that contains the wrong type for both its children.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26324: Skipping consumption of a Date ComplexPredicate with {0} children because we only support at most two.

Cause: Too many children are passed down the Date ComplexPredicate when we can only handle two.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26325: Execution of the search query to show all rows did not complete within the time limit for executor {0}.

Cause: The time allowed to execute the search query to show all rows is not sufficient.

Action: Increase the value of showAllExecutionTimeoutMs parameter in adf-search-config section of adf-config.xml file.
Level: 1

Type: ERROR

Impact: Other

WCS-26326: Execution of the search query did not complete within the time limit for executor {0}.

Cause: The time allowed to execute the search query is not sufficient.

Action: If this problem is persistent, increase the value of executionTimeoutMs parameter in adf-search-config section of adf-config.xml file.
Level: 1

Type: WARNING

Impact: Other

WCS-26327: Query execution failed for {0}.

Cause: Query execution failed.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26328: Search failure: time out error

Cause: Search execution timed out.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26329: Search failure: problem preparing search executor

Cause: Unable to create a search executor.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26330: Search failure: problem with execution

Cause: Search execution problem.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26331: Search failure: problem with adding refiner

Cause: Unable to add refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26332: Search failure: problem with removing refiner

Cause: Unable to remove refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26333: Search failure: problem with updating refiner

Cause: Unable to update the refiner.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26341: Search UI Metadata Lookup Failed: {0}

Cause: The UI Metadata document necessary for rendering Search views could not be found.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26342: Search UI Metadata Update Failed: {0}

Cause: The UI Metadata document necessary for rendering Search views could not be updated (customized).

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26343: Search Options Update Failed

Cause: An MDS error caused the update of search options to fail.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26361: Failed to update the last used date / time of saved search with ID "{0}".

Cause: An MDS error caused the update of the Saved Search document to fail when updating the last accessed date.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26362: Saved Search Update Failed

Cause: An error occurred when trying to update a Saved Search.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26363: Saved Search Creation Failed

Cause: An error occurred when trying to create a Saved Search.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26364: Saved Search Deletion Failed

Cause: An error occurred when trying to delete a Saved Search.

Action: Refer to the error messages presented in the dialog box and act accordingly.
Level: 1

Type: ERROR

Impact: Other

WCS-26365: Failed to delete saved search with ID "{0}".

Cause: An MDS error caused the deletion of the Saved Search document to fail.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26366: Failed to update the sharing setting of saved search with ID "{0}".

Cause: An MDS error caused the update of the Saved Search document to fail when updating the sharing setting.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26367: Saved search with ID "{0}" could not be found.

Cause: Saved search was deleted by another user.

Action: Refresh page to get updated list of saved searches.
Level: 1

Type: WARNING

Impact: Other

WCS-26381: Resource ID is not available to show the resource.

Cause: A link to render a resource did not carry the unique identifier for that resource and therefore could not perform the rendering.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26391: Encountered an exception "{2}" with message "{3}" while populating Data Flavor "{0}" of "{1}" class.

Cause: Failed to populate the given Data Flavor in the Resource Catalog Adapter.

Action: Examine the log for the root cause and take appropriate debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26392: Failed to initialize Search service context DirContext Schema with message "{0}"

Cause: A naming exception was encountered when binding attributes while initializing the Resource Catalog schema for the Search service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-26393: Failed to get attributes of resource "{0}"

Cause: Failed to get attributes of a given resource.

Action: Examine the log for the root cause and take appropriate debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26396: Search Box Size not a number - "{0}". Using Default size instead.

Cause: taskflow parameter passed to this component not an integer.

Action: Examine the taskflow parameter and replace value with a number.
Level: 1

Type: WARNING

Impact: Other

WCS-26397: Search Taskflow ID does not correspond to a valid taskflow. Using Default taskflow instead.

Cause: taskflow parameter passed to this component not a valid taskflow id.

Action: Examine the taskflow parameter and replace with appropriate value.
Level: 1

Type: WARNING

Impact: Other

WCS-26398: Search Scope ID parameter value is not a Scope object - "{0}".

Cause: taskflow parameter EL or value is not a Scope object

Action: Examine the taskflow parameter and replace value with a valid Scope object.
Level: 1

Type: WARNING

Impact: Other

WCS-26401: Encountered "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}".

Cause: The proxy login operation encountered error. Some underlying exception is causing the error.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26402: Received status "{0}" during proxy login with application entity "{1}" to Oracle SES at [{2}], as search user "{3}". Defaulting to public.

Cause: The application entity may not have been provisioned in the identity management system used by SES, or its password may have been expired.

Action: Log on to the Oracle SES administration tool and make sure that the application entity has been provisioned. Then make sure that the account is enabled on the identity management system and has not expired.
Level: 1

Type: WARNING

Impact: Other

WCS-26403: Federation Trusted Entity parameters not configured. Search as public user on Oracle SES.

Cause: Federation Trusted Entity parameters not configured.

Action: Configure Federation Trusted Entity parameters.
Level: 1

Type: WARNING

Impact: Other

WCS-26421: Failed to initialize data group ID from {0} in {1}, encountering {2}

Cause: Either the group ID in question does not exist or SES is down.

Action: Make sure that SES is up and check the group IDs present on SES.
Level: 1

Type: WARNING

Impact: Other

WCS-26422: Failed to discover attributes from {0} in {1}, encountering {2}

Cause: Some underlying exception is causing the discovery of attributes from SES to fail.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26423: No attributes discovered from {0} in {1}

Cause: The SES instance in question does not offer any attributes to query on.

Action: Confirm that Oracle SES is up.
Level: 1

Type: WARNING

Impact: Other

WCS-26424: Failed to discover info source nodes from {0} in {1}, encountering {2}

Cause: Some underlying exception is causing the discovery of info source nodes of SES to fail.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26441: Retrieving the SES Reference failed with Connection Architecture

Cause: Something occurred when getReference of the SesReferenceable is called.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26442: Looking up the SES Connection failed with Connection Architecture

Cause: Encountered a JCA ResourceException when calling getConnection on the connection factory for Searchlets.

Action: Refer to the root exception and identify the proper debugging steps.
Level: 1

Type: WARNING

Impact: Other

WCS-26443: Connection entry "{0}" not found

Cause: The specified connection entry is not in connections.xml

Action: Add the specified connection entry to connections.xml
Level: 1

Type: ERROR

Impact: Other

WCS-26444: Invalid value for addrType attribute in "{1}" entry. Expected value is "{0}"

Cause: Incorrect value for addrType attribute found in connections.xml

Action: Update connections.xml with the correct value for addrType attribute
Level: 1

Type: ERROR

Impact: Other

WCS-26451: Failed to create an instance of class "{0}"

Cause: Failed creating an instance of the XML object representing an SES admin object.

Action: A RuntimeException would have been thrown to propagate the underlying Exception causing this. Please inspect the log to see what else can be done to fix the issue.
Level: 1

Type: WARNING

Impact: Other

WCS-26461: Failed to marshal SES Filter for Advanced Search due to JAXB issues - {0}

Cause: A JAXB problem has caused the marshalling of an SES filter before sending it to SES for execution.

Action: Examine the log to look at the XML structure to verify validity.
Level: 1

Type: WARNING

Impact: Other

WCS-26462: SES Search Execution failed, encountering "{0}" with message "{1}".

Cause: The cause is embedded in the Exception and can be SES-specific.

Action: Examine the log files to extract the root cause to identify the proper debugging steps.
Level: 1

Type: ERROR

Impact: Other

WCS-26463: Can not convert SES Result Element value from {0} to {1}

Cause: Conversion from SES Result Element value failed.

Action: No action is needed. The conversion will default to using String
Level: 1

Type: WARNING

Impact: Other

WCS-26464: Cannot find attribute mapping for column {0}

Cause: You have specified a column ID that cannot be found in the list of SES attributes.

Action: Examine your SES installation and make sure the attribute has a valid column ID.
Level: 1

Type: WARNING

Impact: Other

WCS-26465: Failed to create JAXBContext using package {0}

Cause: A JAXBContext instance could not be created for the SES cluster deserializer.

Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-26466: Failed to unmarshal byte stream into Cluster

Cause: Unmarshalling failed because a JAXBContext instance could not be obtained.

Action: Make sure that the required files can be found in the specified package and that the required classes can be loaded from the classpath.
Level: 1

Type: WARNING

Impact: Other

WCS-26467: SES search query execution timed out - "{0}" with message "{1}".

Cause: The search query does not complete within the time limit.

Action: Re-try the search query again later.
Level: 1

Type: WARNING

Impact: Other

WCS-26481: SearchCrawlExtension class is not found for service {0}

Cause: Portal crawler failed to introspect a Crawlable SPI implementation for the involved service, specified by a URL parameter indicating a crawler's intent to crawl said service. This theoretically should never happen because the URL that crawlers would use are all generated by the Search framework code when crawlers access the root feed that we provide. But if a crawler explicitly starts with a particular service, bypassing our root feed, this warning may result.

Action: Please check the potential crawling SES instances to make sure that there isn't a source that directly targets a service which has no Crawlable implementation.
Level: 1

Type: WARNING

Impact: Other

WCS-26491: The processing and preparing of the control feed for service {0} failed

Cause: The processing and preparing of the control feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.

Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WCS-26492: The processing and preparing of the data feed for service {0} failed

Cause: The processing and preparing of the data feed for service {0} failed. This could mean that there is a fundamental error in the writing the feed content to the output stream which is to be returned to the caller of the URL.

Action: Most likely there is a network issue which may well be temporary. Restart the crawl again and see if the problem persists.
Level: 1

Type: ERROR

Impact: Other

WCS-26501: Creation of the Tags service failed.

Cause: The Tags service is loaded by reflection. Something may have happened to cause that to fail.

Action: Check whether the class name logged is accessible through the class path of the WebCenter Web application.
Level: 1

Type: ERROR

Impact: Other

WCS-26502: Query Federator for the Tags service not created because a Tags Service cannot be created.

Cause: The creation of the Tags service was unsuccessful causing the subsequent creation of a Row Query Federator for Tagging to fail.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26503: findSystemResources failed because of invalid arguments passed in to the method: keywords ({0}).

Cause: One of the input arguments to findSystemResources was invalid.

Action: Make sure that arguments passed in to findSystemResources are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26504: findSystemTags failed because of invalid arguments passed in to the method: keywords ({0}).

Cause: One of the input arguments to findSystemResources was invalid.

Action: Make sure that arguments passed in to findSystemTags are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26505: lookupTag failed because of invalid arguments passed in to the method: tagName ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26506: findFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26507: findTopFilteredSystemTags failed because of invalid arguments passed in to the method:userId({0}), filter ({1}), count({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26508: findTopFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}), count({3}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26509: findAllTopFilteredSystemTags failed because of invalid arguments passed in to the method:userId({0}), filter({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26510: findAllTopFilteredPersonalTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26511: findSystemTags failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26512: findRelatedSystemTagsByTag failed because of invalid arguments passed in to the method: userId ({0}), tagWords ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26513: findRelatedSystemTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26514: findRecommendedTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}), userId ({2}), count ({3}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26515: deleteTag failed because of invalid arguments passed in to the method: tag ({0}).

Cause: One of the input arguments is invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26516: deletePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26517: renamePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), oldTagWord ({1}) newTagWord({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26518: renamePersonalTags failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26519: getTagsByName failed because of invalid arguments passed in to the method: userId ({0}), tagWord ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26520: lookupResource failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26521: createNewResource failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}), resource name ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26522: findFilteredPersonalResource failed because of invalid arguments passed in to the method: userId ({0}), filter ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26523: findSystemResources failed because of invalid arguments passed in to the method: userId ({0}), userFilters ({1}), tagFilters ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26524: findPersonalResources failed because of invalid arguments passed in to the method: userId ({0}), userFilters ({1}), tagFilters ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26525: findRelatedSystemResources failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26526: findRelatedUsers failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}).

Cause: One of the input arguments is invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26527: findRelatedUsersByTag failed because of invalid arguments passed in to the method: userId({0}), tagWords ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26528: createNewBookmark failed because of invalid arguments passed in to the method: userId ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26529: lookupBookmark failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1}, userId ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26530: saveBookmark failed because of invalid arguments passed in to the method: bookmark ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26531: deleteBookmark failed because of invalid arguments passed in to the method: bookmark ({0}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26532: A bookmark has been updated at the same time.

Cause: There was a concurrent update on the bookmarks.

Action: Ask user to retry the operation.
Level: 1

Type: ERROR

Impact: Other

WCS-26533: A database exception was thrown (for example., Unique Key constraint violation error).

Cause: Tried to insert a duplicate object.

Action: Retry the action.
Level: 1

Type: ERROR

Impact: Other

WCS-26534: Resource can not be displayed because the service with ID {0} is not found in the Service Registry.

Cause: Service definition is not found in Service Registry.

Action: Please register the service in Service Registry
Level: 1

Type: ERROR

Impact: Other

WCS-26535: Tags service is not available due to {0}.

Cause: Check the cause specified in the message.

Action: Act appropriately to reverse the cause.
Level: 1

Type: ERROR

Impact: Other

WCS-26536: Resource can not be displayed because the authorizerClass {0} is not found.

Cause: Class specified by authorizerClass is not found.

Action: Check the class path of the application to verify inclusion of the authorizerClass.
Level: 1

Type: WARNING

Impact: Other

WCS-26537: findPopularTags failed because of invalid arguments passed in to the method: userId ({0}), order ({1}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26538: findPopularTags failed because of invalid arguments passed in to the method: userId ({0}), serviceId ({1}), resourceId ({2}).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26539: findUpdatedResources failed because of invalid arguments passed in to the method: serviceId ({0}), date ({1})).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26540: getTags failed because of invalid arguments passed in to the method: serviceId ({0}), resourceId ({1})).

Cause: One of the input arguments was invalid.

Action: Make sure that arguments passed in are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26541: Error encountered while publishing to activity stream due to {0}.

Cause: Error caused by Activity Stream

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26542: Error encountered while retrieving user profile due to {0}.

Cause: Error caused by Profile server

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26543: Error encountered while renaming personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26544: Error encountered while deleting personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26545: Error encountered while finding personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26546: Error encountered while finding personal resources.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26547: saveBookmark callback failed for service {0}.

Cause: The specified service encountered an internal error.

Action: Make sure that the service is configured correctly and that arguments passed in are all valid.
Level: 1

Type: WARNING

Impact: Other

WCS-26548: service-definition.xml requires a resource-type element and one or more object-type elements.

Cause: The service-definition.xml does not have the appropriate components.

Action: Add a resource-type and an object type to the service-definition.xml
Level: 1

Type: WARNING

Impact: Other

WCS-26601: No service ID or resource ID - cannot perform {0}.

Cause: The consumption of the EditBookmarkBean from the view layer did not pass in the service or the resource IDs necessary.

Action: Check the view layer to make sure that the resourceId and the serviceId parameters are passed into the page flow scope.
Level: 1

Type: ERROR

Impact: Other

WCS-26602: Cannot create a recommended list because the Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the recommended list could not be created.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26603: Bookmark cannot be loaded because Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark object could not be created.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26604: Bookmark saving failed because a Tags service cannot be created.

Cause: The creation of the Tags service was unsuccessful, so the bookmark could not be saved.

Action: Check for /META-INF/tagging-class-config.properties and verify that a correct accessible class is specified.
Level: 1

Type: ERROR

Impact: Other

WCS-26605: lookupBookmark failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), and user ID ({2}).

Cause: One of the input arguments to lookupBookmark was invalid.

Action: Make sure that arguments passed in to lookupBookmark are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26606: createBookmark failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), resource name ({2}), and user ID ({3}).

Cause: One of the input arguments to createBookmark was invalid.

Action: Make sure that arguments passed in to createBookmark are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26607: findRecommendedTags failed because of invalid arguments passed in to the method: service ID ({0}), resource ID ({1}), and user ID ({2}).

Cause: One of the input arguments to findRecommendedTags was invalid.

Action: Make sure that arguments passed in to findRecommendedTags are all valid.
Level: 1

Type: ERROR

Impact: Other

WCS-26608: This item has been tagged by the same user at the same time. Re-apply your changes.

Cause: Concurrent update on the bookmarks.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26609: Some items whose tags are to be renamed have been updated at the same time. Re-apply your changes.

Cause: Concurrent update on the bookmarks.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26610: Some items whose tags are to be deleted have been updated at the same time. Re-apply your changes.

Cause: Concurrent update on the bookmarks.

Action: Retry the action
Level: 1

Type: WARNING

Impact: Other

WCS-26611: Tagging Button or Tagging Menu Item will not be rendered because the region "tagging-launch-dialog" is not included in the page.

Cause: While building the page, the tagging button was added without adding a corresponding popup task flow.

Action: Check to make sure the "tagging-launch-dialog" region is indeed included in the page.
Level: 1

Type: WARNING

Impact: Other

WCS-26612: The tagging component "{0}" was not rendered because the underlying Tags service was not available.

Cause: The underlying Tags service was not available.

Action: Look for the errors causing the underlying Tags service to not be available and fix them.
Level: 1

Type: WARNING

Impact: Other

WCS-26613: Error encountered while renaming personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26614: Error encountered while deleting personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26615: Error encountered while finding personal tags.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26616: Error encountered while finding personal resources.

Cause: The creation of the Tagging Service failed or input arguments were invalid

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26617: Error encountered while updating resource with serviceId: {0} resourceId:{1} and resourceName:{2}.

Cause: There was a problem saving the updated resource.

Action: Turn on the logging to finest to check the exception detail.
Level: 1

Type: ERROR

Impact: Other

WCS-26618: This item has been deleted by another user while being tagged. Refresh this page.

Cause: Resource was deleted while being tagged.

Action: Retry the action.
Level: 1

Type: WARNING

Impact: Other

WCS-26621: EncodeBegin error for TaggingPopup tag

Cause: Catastrophic error

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-26622: Error in Tagging Button tag usage - component {0} has attribute {1} whose value is {2}.

Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.

Action: Correct your tag usage.
Level: 1

Type: WARNING

Impact: Other

WCS-26623: Component {0} does not support client listeners.

Cause: Tried to add a client listener to a component that does not support client listeners.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-30001: Error while creating the wiki.

Cause: Error while creating the wiki.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30003: Error while getting the wiki parent.

Cause: Error while getting the wiki parent

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30004: Error while getting wiki.

Cause: Error while getting wiki

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30005: Error while moving to wiki page.

Cause: Error while moving to wiki page

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30006: Error while getting child wikis size.

Cause: Error while getting child wikis size

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30007: Error while deleting wiki.

Cause: Error while deleting wiki

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30008: Error while initializing ContainerWikiBean.

Cause: Error while initializing ContainerWikiBean

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30009: Error while getting wiki list.

Cause: Error while getting wiki list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30010: Error while getting child wiki list.

Cause: Error while getting wiki list

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30011: Error while moving to wiki page.

Cause: Error while moving to wiki page

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30012: Error while getting wikiContainer.

Cause: Error while getting wikiContainer

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30014: Error while setting containerId.

Cause: Error while setting containerId

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30015: Error while getting crumbsList.

Cause: Error while getting crumbsList

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30016: Error while getting different versions for wiki.

Cause: Error while getting different versions for wiki.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30017: Error while creating container.

Cause: Error while creating container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30018: Error while deleting container.

Cause: Error while deleting container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30019: Error while editing container.

Cause: Error while editing container.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30020: Error while getting the wiki hierarchy.

Cause: Error while getting the wiki hierarchy.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30021: {0} not accessible.

Cause: Contact your administrator for access.

Action: Check if data exist or check for appropriate permissions.
Level: 1

Type: WARNING

Impact: Other

WCS-30022: Error while getting the root wiki.

Cause: Error while getting the root wiki.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-30023: Error while getting the tree model.

Cause: Error while getting the tree model.

Action: Contact the administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-32003: Unable to load WebCenter Worklist configuration

Cause: Connections context could not be acquired.

Action: Ensure that the connections.xml file is available and valid.
Level: 1

Type: WARNING

Impact: Other

WCS-32004: Worklist Connection ''{0}'' is an invalid WebCenter Worklist connection.

Cause: The BPEL Worklist connection is invalid.

Action: Verify the specified Worklist connection is to a valid, accessible BPEL Workflow instance.
Level: 1

Type: ERROR

Impact: Other

WCS-32005: The adf-config.xml element associated with the BPEL connection to be used by the To-Dos and Group Tasks service was not present.

Cause: The application's adf-config.xml file was missing the adf-task-config element containing a BPELConnection name.

Action: Add the adf-config.xml entry associated with the To-Dos and Group Tasks service's BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32006: The adf-config.xml element associated with the BPEL connection to be used by the Worklist service was not present.

Cause: The application's adf-config.xml file was missing the adf-worklist-config element containing one or more BPELConnection names.

Action: Add the adf-config.xml entry associated with the Worklist service BPEL connection using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32007: The BPEL Connection named ''{0}'' was not present in the connections.xml file. This will prevent the To-Dos and Group Tasks service from being able to function as a BPEL connection is required.

Cause: The BPEL Connection matching the name specified in the adf-config.xml segment for the To-Dos and Group Tasks service requires adding to connections.xml.

Action: Add the BPEL Connection entry associated with the To-Dos and Group Tasks service adf-config.xml entry to connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32008: The BPEL Connection named ''{0}'' was not present in the connections.xml file. This will prevent the Worklist service from being able to interact with the required this BPEL connection.

Cause: The BPEL Connection matching the name specified in the adf-config.xml segment for the Worklist service requires adding to connections.xml.

Action: Add the BPEL Connection entry associated with the Worklist service adf-config.xml entry to connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32009: The Worklist service does not have a ConnectionName configuration entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the Worklist service was not configured for this application.

Cause: There was no Worklist service ConnectionName entry in adf-config.xml that maps to a corresponding BPELConnection name in connections.xml.

Action: Make sure there is a ConnectionName configuration entry in adf-config.xml in the adf-worklist-config element that maps to a BPELConnection entry in connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32010: The To-Dos and Group Tasks service does not have an entry in adf-config.xml that maps to a BPELConnection in connections.xml, therefore the To-Dos and Group Tasks service was not configured for this application.

Cause: There was no To-Dos and Group Tasks service ConnectionName entry in adf-config.xml that maps to a corresponding BPELConnection name in connections.xml.

Action: Make sure there is a ConnectionName configuration entry in adf-config.xml in the adf-task-config element that maps to a BPELConnection entry in connections.xml using the appropriate configuration manipulation.
Level: 1

Type: WARNING

Impact: Other

WCS-32011: The connection associated with connection name ''{0}'' was not of type BPELConnection. This will prevent the To-Dos and Group Tasks service from being able to use this connection.

Cause: The To-Dos and Group Tasks service ConnectionName entry in adf-config.xml was not mapped to a corresponding BPELConnection name in connections.xml.

Action: Either recreate the connection to one of connection type BPELConnection in connections.xml, or update the To-Dos and Group Tasks service's adf-task-config adf-config.xml entry to refer to a BPELConnection.
Level: 1

Type: WARNING

Impact: Other

WCS-32012: The connection associated with connection name ''{0}'' was not of type BPELConnection. This will prevent the Worklist service from being able to use this connection.

Cause: The Worklist service ConnectionName entry in adf-config.xml was not mapped to a corresponding BPELConnection name in connections.xml.

Action: Either recreate the connection to one of connection type BPELConnection in connections.xml, or update the Worklist service's adf-worklist-config adf-config.xml entry to refer to a BPELConnection.
Level: 1

Type: WARNING

Impact: Other

WCS-32013: Unable to interact with the BPEL client APIs.

Cause: The Worklist service was unable to interact with the BPEL client APIs.

Action: See the exception in the associated notification.
Level: 1

Type: ERROR

Impact: Other

WCS-32100: The WebCenter Worklist has queried the BPEL Worklist connection named ''{0}'', and encountered a WebCenter Executor error. Please see related exception for details. If the WebCenter Worklist is running in an Application Server, check to see if the wsm-pm application is up and running.

Cause: Either, there is an issue with the BPEL Worklist instance being queried or, (if the WebCenter application is running in an Application Server) the wsm-pm application required by the Worklist is down.

Action: Validate the BPEL Worklist connection details in connections.xml, and check that the wsm-pm application process is up and running (if the WebCenter application is running in an Application Server).
Level: 1

Type: ERROR

Impact: Other

WCS-32101: Cache not available.

Cause: Cache is not initialized.

Action: Contact system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-32102: Could not operate on cache object.

Cause: Examine the associated Cache related exceptions that have been logged.

Action: Contact system administrator, if unable to resolve through examination of related logged Cache exception.
Level: 1

Type: ERROR

Impact: Other

WCS-32103: Unable to query BPEL repository.

Cause: The Worklist service was unable to connect to the BPEL repository, as an exception occurred while querying the BPEL Client APIs.

Action: See the exception in the associated notification.
Level: 1

Type: ERROR

Impact: Other

WCS-33001: Exception while executing Query for Recent Activities "{0}" : "{1}".

Cause: The execution of the search query for recent activities failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33002: Unable to find any services to query.

Cause: The Service Framework has not provided any services to query.

Action: Add services to application that can be searched for recent activity.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33003: Exception while executing Search Query Thread for Recent Activities "{0}" : "{1}".

Cause: The query of a specific service for recent activity has failed.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33004: Unable to retrieve user preference "{0}".

Cause: The user preferences could not be read.

Action: Check the WebCenter preference configuration and MDS settings.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33005: Recency value of "{0} minutes" is too low (minimum value is 1 minute).

Cause: The number of minutes considered to be recent is too low.

Action: Increase the recency value preference to greater than or equal to 1 minute.
Level: 1

Type: ERROR

Impact: Programmatic

WCS-33006: Search Execution API returned null.

Cause: The search API used to query for recent activity returned a null object.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

WCS-33007: Service Extension for Recent Activities was not found.

Cause: The WebCenter Service Extension for Recent Activities could not be found.

Action: Check the WebCenter configuration in adf-config.xml.
Level: 1

Type: ERROR

Impact: Configuration

WCS-33008: View Layer API Exception: Exception {0}. Message: {1}.

Cause: Unable to render the recent activity UI.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33009: Exception reading from Recent Activity Cache: {0} : {1}.

Cause: The data cache for recent activity for this user has failed.

Action: Clear the cache by clicking the Refresh button. If the problem persists, contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33010: Invalid recent activity entry returned from service {0} with title "{1}".

Cause: The service returning recent activity has responded with invalid data.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WCS-33011: Unhandled Error or Exception: {0} : {1}.

Cause: The recent activity API has caught an unhandled Exception or Error, possibly thrown in an underlying service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-33012: createExecutors timed out for all services or no services available.

Cause: All searchable services have timed out or are not available.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-33013: Results found, but failed to be processed for service : {0}.

Cause: Results from the given service are invalid and have been ignored.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-33014: Search timed out or cancelled for {0}.

Cause: The search for activity in the given service has taken too long to execute.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-33501: Unable to execute the search for recent activity. Search has not been provisioned.

Cause: The WebCenter Recent Activity Service depends on the availability of the Search service to execute the search for recent activities, but the Search service has not been provisioned for the current scope.

Action: Provision the Search service for this scope.
Level: 1

Type: ERROR

Impact: Other

WCS-33502: The value given for the groupSpace parameter is not a valid portal scope.

Cause: The task flow parameter groupSpace has been set to a scope that does not exist. If this application contains no groupSpace scopes, this parameter must be null.

Action: Edit the task flow parameter in the page definition to set the groupSpace parameter to a valid value (usually null).
Level: 1

Type: ERROR

Impact: Other

WCS-33503: Unable to obtain recent activity data.

Cause: The search may have timed out, failed, or been unable to find anything to search.

Action: Refresh the Recent Activity component using the refresh icon.
Level: 1

Type: ERROR

Impact: Other

WCS-33504: Recent Activity in the Home Portal requires a groupSpace taskflow parameter value to use for the search.

Cause: Recent Activity cannot search the Home Portal.

Action: Edit the Recent Activities taskflow properties and specify a portal taskflow parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-34002: Item not found.

Cause: Item did not exist in repository.

Action: Do not reference items that do not exist.
Level: 1

Type: WARNING

Impact: Other

WCS-34003: Item not found, ancestor depth is not valid.

Cause: The depth of the ancestor was not valid.

Action: Check the depth of the node first.
Level: 1

Type: WARNING

Impact: Other

WCS-34004: This node is not in sync with the file system.

Cause: The session contains stale file system information.

Action: Invoke refresh() or save() to synchronize the session with the file system.
Level: 1

Type: WARNING

Impact: Other

WCS-34005: This node does not have a primary item.

Cause: Folders do not have primary items.

Action: Do not invoke getPrimaryItem() on a folder node.
Level: 1

Type: WARNING

Impact: Other

WCS-34007: Path not found: {0}.

Cause: The method was invoked with an invalid path.

Action: Invoke the method with a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-34008: Unsupported repository operation.

Cause: A method has been invoked that is not supported.

Action: Any code calling this method should be removed or skipped.
Level: 1

Type: WARNING

Impact: Other

WCS-34013: Invalid file system adapter repository reference.

Cause: The Reference provided to initialize the repository does not describe a file system connection or has incorrect parameters.

Action: Invoke the FSRepository constructor with a valid Reference constructed from FSRepository.getReference.
Level: 1

Type: WARNING

Impact: Other

WCS-34014: {0} is not a valid file system mount point.

Cause: The mount point is not a valid file system directory.

Action: Invoke the repository constructor with a valid root directory.
Level: 1

Type: WARNING

Impact: Other

WCS-34015: {0} is not a known workspace in this repository

Cause: Could not access the workspace, as the file system adapter does not support workspaces.

Action: Invoke login() with a null or empty workspace name.
Level: 1

Type: WARNING

Impact: Other

WCS-34016: The file system adapter does not accept login credentials

Cause: Could not login as the file system adapter does not accept login credentials.

Action: Invoke login() with null credentials.
Level: 1

Type: WARNING

Impact: Other

WCS-34017: Impersonation is not allowed.

Cause: Could not execute the impersonate method as the file system adapter does not support impersonation.

Action: Do not invoke the impersonate() method.
Level: 1

Type: WARNING

Impact: Other

WCS-34018: Cannot complete the delete operation.

Cause: An unexpected file system error occurred during the delete operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34019: Cannot complete the move operation.

Cause: An unexpected file system error occurred during the move operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34021: Cannot access the file system.

Cause: There was an error reading a file.

Action: See the chained IOException for more details on this error.
Level: 1

Type: ERROR

Impact: Other

WCS-34022: This property is not a REFERENCE.

Cause: This property is not a REFERENCE.

Action: Do not invoke getNode() on this property.
Level: 1

Type: WARNING

Impact: Other

WCS-34023: Illegal single value access: property is multi valued.

Cause: Accessed a single value property on a multi valued property.

Action: Do not access a single value property on a multi valued property.
Level: 1

Type: WARNING

Impact: Other

WCS-34024: Illegal multi value access: property is single valued.

Cause: Accessed a multi value property on a single value property.

Action: Do not access a multi value property on a single value property.
Level: 1

Type: WARNING

Impact: Other

WCS-34025: XPath error

Cause: Error occurred while processing XPath.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34026: Invalid XPath query

Cause: The XPath query was invalid.

Action: Correct the XPath query.
Level: 1

Type: WARNING

Impact: Other

WCS-34028: Invalid call to setProperty: the target type is not valid.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34029: Invalid call to setProperty: this property cannot be set or the value is not compatible

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34030: Cannot move a file or folder to a file.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34031: Save cannot include only the source or the destination of a move.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34032: Cannot specify an index on move destination.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34034: Cannot move a property.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-34035: An item with the same name already exists at the destination.

Cause: An attempt was made to overwrite an existing item.

Action: Specify the overwrite option, or remove the item before attempting this operation.
Level: 1

Type: WARNING

Impact: Other

WCS-34036: Move prevented by constraint violation.

Cause: Could not perform the requested move operation as it violates the constraints defined in the JCR specification.

Action: Verify that the target node is a valid parent and/or this node can be renamed.
Level: 1

Type: WARNING

Impact: Other

WCS-34037: Access denied

Cause: Could not perform the specified action as it is not allowed on the path specified.

Action: Contact the system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-34038: The session has pending changes.

Cause: The operation could not proceed as there are pending changes in the session.

Action: Invoke save() or refresh() before performing the operation.
Level: 1

Type: WARNING

Impact: Other

WCS-34047: Invalid parameter

Cause: Could not parse a parameter to this call as it is invalid.

Action: Check and correct the parameters for this call.
Level: 1

Type: WARNING

Impact: Other

WCS-34306: Error while executing a search.

Cause: An unexpected error occurred while executing a search.

Action: Check the search criteria is valid and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34307: Invalid node type : {0}

Cause: An invalid node type was specified for the search.

Action: Verify that the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34308: Cannot determine the node type for the search.

Cause: An unexpected error occurred while determining the node type for the search.

Action: Check the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34310: Invalid search query.

Cause: The XPath specified for the search was invalid.

Action: Ensure that the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34311: An error occurred while building the search.

Cause: An error occurred while building the search query.

Action: Ensure the search query is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34320: Property cannot be created for {0} as the data type, {1}, is invalid. Path: {2}; node ID: {3}; node site ID: {4}.

Cause: The data type for the requested property was invalid.

Action: Specify a valid data type for the property, and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34321: Primary item name for node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: The node type was invalid.

Action: Check if the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34322: Property definitions of node type, {0}, cannot be determined.

Cause: An error occurred while creating the property definitions.

Action: Check if the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34323: Super types of node type, {0}, cannot be determined.

Cause: An error occurred while creating the super types.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34324: Primary item name for node type, {0}, cannot be determined.

Cause: The node type was not found.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34325: Node definitions for node type, {0}, cannot be determined.

Cause: Node definition could not be created.

Action: Check the node type is valid and retry.
Level: 1

Type: ERROR

Impact: Other

WCS-34326: Super types of node type, {0}, cannot be determined. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: The node type was not found.

Action: Verify that the requested node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34327: Invalid credentials.

Cause: Session could not be created for the user.

Action: Verify that the credentials passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34328: Database connection could not be obtained.

Cause: Could not access the database, which may be down.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34329: Insufficient privileges to perform the operation.

Cause: You did not have the sufficient privilege to perform this operation.

Action: Contact the Portal administrator to check your privileges.
Level: 1

Type: WARNING

Impact: Other

WCS-34330: The requested node type, {0}, does not exist.

Cause: Could not locate the requested node type as it does not exist.

Action: Verify that the node type exists in the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34331: Property definitions of node type, {0}, cannot be returned. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: An error occurred while creating the property definitions.

Action: Check the node type is valid, verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34332: Property, {0}, cannot be set for node type, {1}. NodeTypeID: {2}; NodeTypeSiteID: {3}.

Cause: Property value was invalid.

Action: Provide a property value that is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34333: Oracle data-source, {0}, cannot be looked up.

Cause: The data-source was not available.

Action: Verify that the data-source is created correctly and is available.
Level: 1

Type: ERROR

Impact: Other

WCS-34335: The root nodes of the Portal repository cannot be obtained.

Cause: An error occurred while listing the root nodes.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34336: Statement/Connection objects cannot be closed.

Cause: An error occurred while closing the statement or connection objects.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34337: The child nodes of folder, {2}, cannot be obtained. Parent folder ID: {0}; folder site ID: {1}.

Cause: A SQL exception occurred while trying to list the child nodes.

Action: Verify the folder ID, folder page group ID and path are valid, verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34338: Property, {0}, is a single-valued property.

Cause: The property was a single valued property.

Action: Verify the value for the property is a single value.
Level: 1

Type: ERROR

Impact: Other

WCS-34339: Unable to check if the session is live.

Cause: An error occurred while checking whether the session is live.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34340: The Portal session cannot be logged out.

Cause: An error occurred while logging out of the Portal session; it is possible the Portal instance is no longer available.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34341: Cannot determine UUID for node, {0}.

Cause: An error occurred while determining the UUID of context node.

Action: Verify that the path is correct and that the node is referenceable.
Level: 1

Type: ERROR

Impact: Other

WCS-34342: Cannot get the node, {0}.

Cause: An error occurred while getting the requested node.

Action: Verify that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34343: Cannot get the node for the given UUID, {0}.

Cause: Error getting the requested node.

Action: Verify that the UUID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34344: Cannot determine if item exists at given path, {0}.

Cause: An error occurred while determining if the requested item exists.

Action: Verify that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34346: Property definitions of node type cannot be determined. NodeTypeID: {0}; NodeTypeSiteID: {1}.

Cause: An error occurred while creating the property definitions.

Action: Verify that the node type exists in the Portal repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34347: Property, {0}, cannot be set for node type. NodeTypeID: {1}; NodeTypeSiteID: {2}.

Cause: Property value was invalid.

Action: Provide a property value that is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34348: Cannot retrieve all the node types from the Portal repository.

Cause: An error occurred while retrieving the Portal node types.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34349: Cannot get the properties for node with ID: {0}, site ID: {1}.

Cause: An error occurred while obtaining the properties of the node from the repository.

Action: Verify that the node and node type are valid, and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34350: Cannot get the references for the requested node. Node ID: {0}; node site ID: {1}.

Cause: An error occurred while obtaining the references for the requested node.

Action: Verify the node is valid, and verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34351: Cannot get binary property value for property, {0}, that belongs to node, {1}.

Cause: An error occurred while fetching the binary property of node.

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

Type: ERROR

Impact: Other

WCS-34352: Cannot get Portal property name for property ID: {0}.

Cause: An error occurred while getting the Portal property name.

Action: Verify that the requested property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34354: The Portal session could not be logged out.

Cause: A SQL error occurred when attempting to log out.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34355: Cannot determine the length of the given input stream.

Cause: An error occurred while determining the length of the input stream.

Action: Verify that the input stream is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34356: Current operation is not supported for the single-valued property, {0}.

Cause: The current operation could not be performed on a single property as single-valued properties are not supported by such an operation.

Action: This API cannot be invoked on a single-valued property.
Level: 1

Type: ERROR

Impact: Other

WCS-34357: This node, {0}, cannot be referenced and hence, does not have a UUID property.

Cause: The context node does not have a UUID property.

Action: Make this request on a referenceable node.
Level: 1

Type: ERROR

Impact: Other

WCS-34358: Current operation is not supported for the multi-valued property, {0}.

Cause: The current operation could not be performed on a multi-valued property as multi-valued properties are not supported by such an operation.

Action: This API cannot be invoked on a multi-valued property.
Level: 1

Type: ERROR

Impact: Other

WCS-34359: This operation is not supported by the Portal repository.

Cause: An error occurred while performing this action as the operation is not supported by the underlying Portal repository.

Action: Check the operation being attempted is a valid operation for the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34360: The Portal repository has only 1 workspace, so this request is invalid.

Cause: The underlying Portal repository has only one workspace.

Action: This is an invalid request since the repository is a single workspace repository. Retry with a valid request.
Level: 1

Type: ERROR

Impact: Other

WCS-34361: Cannot convert length of property, {0}, to long.

Cause: An error occurred while converting the length to the long data type.

Action: Verify the value of the property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34362: Cannot parse the date value for property, {0}.

Cause: An error occurred while parsing the date value.

Action: Verify the value of the property is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34363: The requested property cannot be found. Path of context node: {0}; Relative Path: {1}.

Cause: The property was not found.

Action: Verify that the requested property is valid and that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34364: The requested item, {0}, cannot found.

Cause: An error occurred while getting the requested item.

Action: Verify that the item exists in the Portal repository.
Level: 1

Type: ERROR

Impact: Other

WCS-34365: The property, {0}, cannot be converted to a reference.

Cause: The property could not be converted to a reference or was a multi-valued property.

Action: Verify that the property can be converted to a reference.
Level: 1

Type: ERROR

Impact: Other

WCS-34366: {0} is a folder and hence, it does not have a primary item.

Cause: The request could not be performed because folders cannot have primary items.

Action: This is an invalid request.
Level: 1

Type: ERROR

Impact: Other

WCS-34367: The requested node was not found. Path of context node: {0}; Relative Path: {1}.

Cause: The node was not found.

Action: Verify that the requested node is valid and that the path is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34368: The given path, {0}, is invalid.

Cause: The specified path was invalid.

Action: Provide a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-34416: Error determining if child node, {0}, could be added.

Cause: An error occurred while determining whether the child node could be added.

Action: Verify the node is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34417: Error determining if child node, {0}, based on type, {1}, could be added.

Cause: An error occurred while determining whether a child node based on the given type could be added.

Action: Verify the node and type are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34418: Error removing the child item, {0}, for node type, {1}.

Cause: An error occurred while removing the child item.

Action: Verify item and node type are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34419: Error removing the property, {0}, for node type, {1}.

Cause: An error occurred while removing the property.

Action: Verify the node type and property are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34421: The connection cannot be closed.

Cause: The system encountered an unexpected error while trying to close a database connection.

Action: Verify that the Portal instance is up and running.
Level: 1

Type: ERROR

Impact: Other

WCS-34422: The node types array object could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node types object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34423: The "all node types" node type iterator could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34424: The Portal node types linked list object could not be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the Portal node types linked list object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34425: The cache region, {0}, has already been defined.

Cause: The cache region has already been defined.

Action: No action is required as this is just indicating that the cache region has already been defined.
Level: 1

Type: WARNING

Impact: Other

WCS-34428: Generic cache exception when trying to retrieve object from cache.

Cause: A cache exception occurred when trying to retrieve the object from the cache.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34429: Object cannot be stored in cache as the cache is full.

Cause: The object could not be stored in cache because the cache was full.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34430: The root node does not have a parent node.

Cause: The parent node was requested for a root node.

Action: Request the parent node of any node except the parent node.
Level: 1

Type: ERROR

Impact: Other

WCS-34431: The node type iterator object cannot be removed from the cache.

Cause: The node type iterator object could not be removed from the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34432: The node type name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Verify the specified node type name is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34433: The property name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-34434: The property definition name cannot be returned from the qualified name.

Cause: The namespace could not be resolved.

Action: Verify the property type is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34435: The item at the requested depth, {0}, cannot be found.

Cause: An error occurred while getting the requested item.

Action: Verify that the depth is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-34436: The root node does not have a parent.

Cause: Could not request the parent node as root nodes do not have parent nodes.

Action: Verify that the context node is not the root node.
Level: 1

Type: ERROR

Impact: Other

WCS-34437: The Portal session cannot be restored.

Cause: A SQL error occurred when attempting to restore the session for the user.

Action: Verify that the user has been authenticated.
Level: 1

Type: ERROR

Impact: Other

WCS-34438: The declared property definition array object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the declared property definition array object in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34440: The property definition array object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definition array object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34441: The property iterator object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property iterator object in the cache.

Action: Contact the WebCenter administrator to check the status of the Cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34442: The property object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34443: The node iterator object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node iterator object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34444: The node object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34446: The node type object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34447: The "primary node types" node type iterator cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34448: The "mixin node types" node type iterator cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the node type iterator in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34449: The "super types" node type array cannot be stored in cache.

Cause: The system encountered an unexpected exception when trying to store the node type array in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34450: The child node definitions of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the child node definitions of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34451: The property definitions of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definitions of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34452: The boolean object cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the boolean object in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34453: The requested child node definition of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the child node definition of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34454: The requested property definition of the node type cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the property definition of the node type in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34456: The repository property objects cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the repository property objects in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34457: The repository property definition objects cannot be stored in the cache.

Cause: The system encountered an unexpected exception when trying to store the repository property definition objects in the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34458: One of the cache regions could not be destroyed.

Cause: The system encountered an unexpected exception when trying to destroy one of the cache regions.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34459: The cache could not be initialized.

Cause: The system encountered an unexpected exception when trying to initialize the cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34460: The cache configuration file could not be read.

Cause: The system encountered an IO exception when trying to read the cache configuration file.

Action: Verify that the configuration file exists.
Level: 1

Type: ERROR

Impact: Other

WCS-34461: The repository node type objects could not be stored in cache.

Cause: The system encountered an unexpected exception when trying to store the repository node type objects in cache.

Action: Contact the WebCenter administrator to check the status of the cache.
Level: 1

Type: ERROR

Impact: Other

WCS-34462: Cannot get the super types for node type: {0}.

Cause: An error occurred while fetching the super types of the given node type.

Action: Verify that the requested node type exists in the Portal repository and is a custom type.
Level: 1

Type: ERROR

Impact: Other

WCS-34463: The cache region, {0}, cannot be found.

Cause: Could not find the requested region, as it has not been defined in Java Object Cache (JOC).

Action: Verify that the region name is valid and is expected to exist in this hierarchy.
Level: 1

Type: ERROR

Impact: Other

WCS-34464: Oracle Text search is unable to run.

Cause: An error occurred with Oracle Text while running a search.

Action: Check with the Administrator of the Portal you are trying to search that Oracle Text is valid. Additional information as to the cause of the error may be in the portal diagnostics log.
Level: 1

Type: ERROR

Impact: Other

WCS-34465: A root search can not be performed as the base languages of the page groups are different.

Cause: The search could not be performed because the base language of the page groups to be searched are not the same.

Action: Only perform searches which search a single page group.
Level: 1

Type: ERROR

Impact: Other

WCS-34466: Cannot look up the database connection with the name {0} from connections.xml.

Cause: An error occurred while attempting to look up the database connection; the named database connection may not exist in connections.xml.

Action: Make sure the database connection is created in connections.xml.
Level: 1

Type: ERROR

Impact: Other

WCS-35006: cannot load metadata from XML node

Cause: The content of the data-control file (.dcx) might be invalid.

Action: Verify that the content in the data-control file (.dcx) is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-35008: Login failed.

Cause: The specified user credentials were invalid.

Action: Provide valid user credentials.
Level: 1

Type: ERROR

Impact: Other

WCS-35013: missing method parameters

Cause: The data-control operation was invoked without any parameters.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35016: Retrieving data-control definition from run-time data-control object returned null.

Cause: The ADF framework did not set the data-control definition within the run-time data control.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35300: Parameters for the operation are missing.

Cause: The ADF framework passed a null parameter map to the data-control operation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35301: The path parameter is not correct.

Cause: The path string that was specified was not a valid JCR repository path.

Action: Verify that the specified path string is a valid path in the content repository, and that it starts with /.
Level: 1

Type: ERROR

Impact: Other

WCS-35302: The type parameter is not correct.

Cause: The type string that was specified was not a valid node type in the JCR repository.

Action: Make sure the type specified is valid in the content repository on which the data control is based. Both the prefix and the local name should be valid. For example, nt:file and nt:folder are valid types.
Level: 1

Type: ERROR

Impact: Other

WCS-35303: cannot generate XPath query

Cause: The parameters that were given in the search operation could not be resolved into a valid XPath query string using the content repository session.

Action: Ensure the attribute names and prefixes used in the parameters are valid and registered in the JCR repository.
Level: 1

Type: ERROR

Impact: Other

WCS-35304: incorrect attribute {0} specified in the predicate

Cause: The specified attribute was not found in the repository.

Action: Provide a valid attribute name.
Level: 1

Type: ERROR

Impact: Other

WCS-35305: incorrect prefix for the attribute {0} in the predicate

Cause: The namespace that was used in the attribute was not correct or not registered in the JCR repository.

Action: Provide a valid prefix, or report the problem to the provider of the JCR adapter used with the repository.
Level: 1

Type: ERROR

Impact: Other

WCS-35306: cannot resolve attribute {0} using the repository session

Cause: An invalid attribute or an unregistered prefix was used in the JCR session.

Action: Provide a valid attribute name in the JCR repository session.
Level: 1

Type: ERROR

Impact: Other

WCS-35307: operator {0} not supported

Cause: An invalid operator was specified.

Action: Specify a valid operator.
Level: 1

Type: ERROR

Impact: Other

WCS-35309: The XPath query {0} is not supported by the JCR adapter.

Cause: The JCR adapter might not have been compliant with the XPath support that is required to work with the Content Repository data control.

Action: Verify that the XPath query is supported by this JCR adapter.
Level: 1

Type: ERROR

Impact: Other

WCS-35310: error in the JCR repository

Cause: An error occurred in the JCR adapter.

Action: Check the exception's cause and JCR adapter's error log.
Level: 1

Type: ERROR

Impact: Other

WCS-35311: error getting the item's URL

Cause: An error occurred while generating the URL for an item.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35312: invalid return attribute name {0}

Cause: An invalid Java name was entered. The name of a return attribute must be a valid Java name and must be different from "name", "URL", "path" and "primaryType".

Action: Verify that the attribute name is valid and is not "name", "URL", "path" and "primaryType".
Level: 1

Type: ERROR

Impact: Other

WCS-35313: invalid return attribute type

Cause: An invalid return attribute type was specified. Return attributes must be one of the following JCR types: Boolean, Integer, Double, String, or Date.

Action: Specify a valid return attribute type.
Level: 1

Type: ERROR

Impact: Other

WCS-35314: cannot get value for attribute {0}

Cause: The value for the specified attribute could not be retrieved from the JCR node.

Action: Verify that the JCR path for the attribute is correct.
Level: 1

Type: ERROR

Impact: Other

WCS-35501: No repository was set in the environment.

Cause: No repository was specified for this resource.

Action: Specify a repository to use in creating the resource.
Level: 1

Type: ERROR

Impact: Other

WCS-35502: could not log on to the content repository

Cause: There was a problem logging on to the content repository.

Action: Verify that the connection and credentials are defined correctly and that the repository is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-35503: An error occurred while accessing the content repository.

Cause: There was a problem accessing the content repository.

Action: Verify that the content repository is accessible.
Level: 1

Type: ERROR

Impact: Other

WCS-35504: An error occurred while trying to close the connection.

Cause: Could not close the content repository connection.

Action: Verify that the connection is still available, and try to close it again.
Level: 1

Type: ERROR

Impact: Other

WCS-35505: Item {0} is not a file or folder.

Cause: An item was specified that is not a file or folder.

Action: Specify an item that is either a file or a folder.
Level: 1

Type: ERROR

Impact: Other

WCS-35506: Item {0} does not exist.

Cause: An item was specified that does not exist.

Action: Verify that the specified item exists.
Level: 1

Type: ERROR

Impact: Other

WCS-35507: unknown control type: {0}

Cause: An unknown control type was specified.

Action: Specify a known control type.
Level: 1

Type: ERROR

Impact: Other

WCS-35508: {0} does not name a ContentDirContext.

Cause: An item was specified that is not a ContentDirContext.

Action: Verify that the item specified is a ContentDirContext.
Level: 1

Type: ERROR

Impact: Other

WCS-35509: invalid search operation: {0}

Cause: An unrecognized search operation was specified.

Action: Use only recognized search operations.
Level: 1

Type: ERROR

Impact: Other

WCS-35510: unable to generate schema

Cause: An error occurred while adding attributes to the schema.

Action: Make sure the schema attributes are defined properly and are not already bound.
Level: 1

Type: ERROR

Impact: Other

WCS-35511: unable to create DataFlavor

Cause: An error occurred while trying to create a DataFlavor from the given MIME type.

Action: Make sure the MIME type is valid and non-null, and that any referenced classes can be loaded.
Level: 1

Type: WARNING

Impact: Other

WCS-35513: unable to create TaskFlowDescriptor

Cause: An error occurred while trying to create a TaskFlowDescriptor object.

Action: Make sure the required classes are in the classpath.
Level: 1

Type: ERROR

Impact: Other

WCS-35514: This feature is only available in a design environment.

Cause: A call to a design time only feature was made from run time.

Action: Do not call this method from run time code.
Level: 1

Type: ERROR

Impact: Other

WCS-35515: Error getting information for connection {0}. The connection will be skipped in the resource catalog.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35516: This factory cannot be used at design time.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35517: Not a valid content URL: {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35518: Error getting information for node ID {0}. This node will be skipped in the resource catalog.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35900: Illegal value state, cannot read a value previously streamed.

Cause: The application mixed calls to getStream() and other get* accessors on the same value object.

Action: Verify your application code.
Level: 1

Type: ERROR

Impact: Other

WCS-35901: Illegal value state, cannot stream a value previously read.

Cause: The application mixed calls to getStream() and other get* accessors on the same value object.

Action: Verify your application code.
Level: 1

Type: ERROR

Impact: Other

WCS-35902: Error in value conversion (source type = {0}, target type = {1}).

Cause: The JCR values could not be converted to the specified type; the source and target type may not be compatible.

Action: Verify the value conversion rules defined in the JCR specification.
Level: 1

Type: ERROR

Impact: Other

WCS-35903: Error in value conversion (invalid ISO8601 string).

Cause: The specified string was not a valid ISO8601 string as specified by JCR and therefore could not be converted to a date.

Action: Verify the format of the date string.
Level: 1

Type: ERROR

Impact: Other

WCS-35904: Cannot create REFERENCE values.

Cause: Values of type REFERENCE are not supported by this JCR repository.

Action: Avoid using properties of type REFERENCE in your application.
Level: 1

Type: WARNING

Impact: Other

WCS-35905: Input/Output error while reading the binary stream.

Cause: The data for the binary property could not be accessed.

Action: Verify that the storage medium for the JCR repository is accessible.
Level: 1

Type: WARNING

Impact: Other

WCS-35906: UTF8 encoding not supported on this JVM

Cause: The JVM does not support UTF-8 encoding.

Action: Use a supported Java 5 compliant JVM.
Level: 1

Type: WARNING

Impact: Other

WCS-35907: This iterator does not contain any more elements.

Cause: The iterator has exhausted all its elements.

Action: Check the usage of the RangeIterator by your application.
Level: 1

Type: WARNING

Impact: Other

WCS-35908: This iterator does not support the remove operation.

Cause: The remove() operation is not supported on this iterator.

Action: Avoid making calls to RangeIterator#remove() in your application.
Level: 1

Type: WARNING

Impact: Other

WCS-35909: The item at path {0} is not a node.

Cause: An item was found at the specified path but it was not a node.

Action: Check that your application is specifying the correct path.
Level: 1

Type: WARNING

Impact: Other

WCS-35910: "{0}" is not a known namespace prefix.

Cause: The name or path contained a namespace prefix unknown to this repository.

Action: Check the namespace mappings in the current session.
Level: 1

Type: WARNING

Impact: Other

WCS-35911: "{0}" is not a known namespace URI.

Cause: The repository did not recognize the specified namespace URI.

Action: Check the set of namespaces allowed by the current repository.
Level: 1

Type: WARNING

Impact: Other

WCS-35912: The prefix "{0}" is already used.

Cause: The specified prefix was already mapped to a namespace and could not be remapped.

Action: Change the prefix mapping for the URI associated with that prefix before mapping it to another URI.
Level: 1

Type: WARNING

Impact: Other

WCS-35913: {0} is a reserved namespace prefix and cannot be remapped

Cause: The "xml" prefix could not be remapped as it is reserved by JCR.

Action: Check that your application is not trying to remap the "xml" prefix.
Level: 1

Type: WARNING

Impact: Other

WCS-35914: Namespace prefix remapping is not permitted

Cause: Could not remap the namespace as the JCR repository does not permit persistent namespace remapping.

Action: Use the session for any namespace remapping requirements.
Level: 1

Type: WARNING

Impact: Other

WCS-35915: Invalid JCR name or path: {0}

Cause: The name or path specified was not a valid JCR name or path.

Action: Check that the name or path uses valid namespace prefixes and satisfies the JCR grammar rules for names and paths.
Level: 1

Type: WARNING

Impact: Other

WCS-35916: Cannot append an absolute Path

Cause: Could not append an absolute path to the existing path.

Action: Make sure that the appended path is always relative.
Level: 1

Type: WARNING

Impact: Other

WCS-35918: Unexpected error while accessing node type

Cause: An unexpected error occurred while accessing a node type.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-35919: No such node type: {0}

Cause: The node type specified was unknown to the JCR repository.

Action: Ensure that your are using correct node types for this repository.
Level: 1

Type: WARNING

Impact: Other

WCS-35920: Not a supported query language: {0}

Cause: The query language specified was a not a supported query language; this repository only supports XPath.

Action: Make sure you use only XPath queries.
Level: 1

Type: WARNING

Impact: Other

WCS-35921: Saved queries are not supported.

Cause: Could not save the query as this repository does not support saved queries.

Action: Ensure that your application does not call unsupported JCR functionality.
Level: 1

Type: WARNING

Impact: Other

WCS-35922: Incorrect XPath expression

Cause: Could not recognize the XPath expression specified as it is not supported by this JCR repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35923: XPath expression error: invalid enumeration value.

Cause: An internal data structure used an invalid value.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-35924: XPath expression error: invalid expression tree.

Cause: The XPath expression specified was not recognized as it is not supported by this JCR repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35925: Error while generating XML representation of expression tree

Cause: Could not create an XML representation of this expression tree.

Action: Check the exception stack trace for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-35926: Invalid xpath expression.

Cause: The XPath expression specified was not recognized as it is not supported by this JCR repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35927: Invalid qualified name: {0}

Cause: The specified XPath expression contained an invalid qualified name.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35928: Unexpected error during XML export.

Cause: There was an XML processing error while performing an XML export operation.

Action: Check that you are using Oracle XML parser v2.
Level: 1

Type: WARNING

Impact: Other

WCS-35930: Index out of bound while accessing path

Cause: The specified index for a path element was not valid.

Action: Check your use of the path object.
Level: 1

Type: WARNING

Impact: Other

WCS-35988: FOTY0012: argument node does not have a typed value

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35989: XPST0010: The query uses an axis that is not supported by the query engine.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35990: XPST0081: A QName used in the expression contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35991: "{0}" is not a valid expression for use as a search string with jcr:contains().

Cause: The specified full text search expression was not a valid argument for jcr:contains().

Action: Check the full text search expression syntax defined in the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35992: "{0}" is not a valid expression for use as a search string with jcr:like().

Cause: The specified regular expression was not a valid argument for jcr:like().

Action: Check the regular expression syntax defined in the JCR 1.0 specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35993: This XPath expression contains constructs that are not supported by this query engine.

Cause: Could not execute this XPath query as it contained constructs that were not supported by this repository.

Action: Check that your XPath query conforms to the JCR specification.
Level: 1

Type: WARNING

Impact: Other

WCS-35994: XPTY0004: It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35995: XPST0017: It is a static error if the expanded QName and number of arguments in a function call do not match the name and arity of a function signature in the static context.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35996: FORG0006: invalid argument type

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35997: FORG0001: invalid value for cast/constructor

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35998: XPTY0006: (Not currently used)

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-35999: FONC0001: undefined context item

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36201: Unable to find Page Definition for the template page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36202: Cannot find page with name "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36203: Failed to create SubPath "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36204: Cannot find Page Definition with name "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36205: Unable to find page with path "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36206: Pages metadata file already exists under the path "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36207: Unable to update DataBindings.cpx to update page usageId.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36208: Scope folder "{0}" for rename does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36209: Failed to get Permission class for page "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36210: Failed to get Permission target for page "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36211: Cache is not available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36212: Failed to add pages to cache "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36213: Failed to invalidate cache "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36214: Failed to invalidate cache for scope "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36215: A page with name {0} under path {1} does not exist.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36216: Failed to remove the page permissions for "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36217: Failed to create .rdf file for page "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36218: Failed to delete .rdf file "{0}".

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36301: Unable to find page "{0}" in the Binding Context.

Cause: Page objects do not exist in the Binding Context.

Action: Check if the page in the specified path exists.
Level: 1

Type: ERROR

Impact: Other

WCS-36302: Unable to create a document with name "{0}".

Cause: Invalid MO name supplied for creation in MDS.

Action: Check the name provided for creation of the document and ensure that it is a valid MO name.
Level: 1

Type: ERROR

Impact: Other

WCS-36303: Unable to create a document in path "{0}".

Cause: MDS raised an MDS_UNSUPPORTED_UPDATE exception while creating document.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36304: Unable to create a pagedefs directory under the scope "{0}".

Cause: MDS raised an exception while creating pagedefs folder.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36305: Unable to delete page "{0}".

Cause: MDS raised an exception while deleting the page.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36306: Unable to create metadata for page "{0}".

Cause: MDS raised an exception while creating metadata for page.

Action: The metadata for the page already exists under the scope.
Level: 1

Type: ERROR

Impact: Other

WCS-36307: Unable to copy page "{0}".

Cause: MDS raised an exception while copying the page.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36308: Unable to rename scope "{0}" to "{1}".

Cause: MDS raised an exception while renaming the pages under the scope.

Action: Check the MDS config to ensure that the path is editable.
Level: 1

Type: ERROR

Impact: Other

WCS-36309: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-36310: Unable to create a page with the name "{0}".

Cause: A page with the same name already exists.

Action: Change to use a different name.
Level: 1

Type: ERROR

Impact: Other

WCS-36311: PageService object is not an instance of PageServiceImpl.

Cause: PageService object is not an instance of PageServiceImpl.

Action: Create a Page service instance and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36312: Could not flush changes to MDS. Adding view activity failed.

Cause: Could not flush changes to MDS.

Action: Try to create a new page.
Level: 1

Type: ERROR

Impact: Other

WCS-36313: Unable to find page definition file for page "{0}".

Cause: The page definition file does not exist or the page definition path is wrong in the Binding Context file.

Action: Check if the page definition file exists and make sure its path is correct in the Binding Context file.
Level: 1

Type: ERROR

Impact: Other

WCS-36314: Unable to create a page for now because another page is being created.

Cause: Another page is being created and all page metadata is locked.

Action: Try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36315: The page style is no longer available.

Cause: The page style is deleted or hidden.

Action: Choose another page style.
Level: 1

Type: ERROR

Impact: Other

WCS-36316: Cannot perform the requested operation.

Cause: You do not have sufficient privileges to perform the requested operations.

Action: Ask your administrator to grant you the appropriate privileges and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-36701: Failed to redirect because the page is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36702: An ADF component with name "{0}" is not found.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36703: Failed to redirect because the page is not specified.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36704: User {0} already has access to the page.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36705: You do not have permission to change page security settings anymore.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36706: You do not have permission to change page properties anymore.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36707: Failed to save the changes because another page operation was in progress.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36708: Failed to instantiate DocSecurityBean.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36709: Failed to instantiate PageSecurityManager.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-36801: Failed to change page permission to "{0}".

Cause: An unexpected error occurred when changing page permission.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36802: Failed to grant page permission "{0}" to user "{1}".

Cause: An unexpected error occurred when granting page permission to a user.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36803: Failed to revoke page permission from user "{0}".

Cause: An unexpected error occurred when granting page permission to a user.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36804: Failed to change page security to default mode.

Cause: An unexpected error occurred when changing page security mode.

Action: Check error stack for details.
Level: 1

Type: ERROR

Impact: Other

WCS-36805: A page named {0} already exists.

Cause: A page with the specified name exists.

Action: Specify a unique name for the page.
Level: 1

Type: ERROR

Impact: Other

WCS-37001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-37002: An object of type {0} with this ID ({1}) already exits.

Cause: An attempt was made to create an object with an existing ID.

Action: Use a unique ID to Create the object.
Level: 1

Type: ERROR

Impact: Other

WCS-37003: Configuration invalid.

Cause: Either the configuration does not exist or the MDS instance is not specified.

Action: Specify a valid configuration with a MDS instance.
Level: 1

Type: ERROR

Impact: Other

WCS-37004: The name ({0}) is invalid.

Cause: The name specified was not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-37006: Object modified by another user.

Cause: The object has been changed by another user.

Action: Refresh the object and try again.
Level: 1

Type: WARNING

Impact: Other

WCS-37007: Object of type {0} with ID={1} could not be found.

Cause: The ID is invalid.

Action: Specify a valid object ID.
Level: 1

Type: ERROR

Impact: Other

WCS-37008: Object ({0}) is immutable.

Cause: An attempt to change this object was made but this object is currently immutable.

Action: Either update object to allow changes or perform this operation on another object.
Level: 1

Type: ERROR

Impact: Other

WCS-37009: Method: {1} in class: {0} is invalid.

Cause: The specified class.method does not exist or is invalid.

Action: Check underlying method/property specification.
Level: 1

Type: ERROR

Impact: Other

WCS-37010: {0} is not a valid reference name to MDS.

Cause: The name specified is not a valid MDS reference name.

Action: Correct the name to a valid reference.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-37500: The note no longer exists.

Cause: Another user deleted the note.

Action: Refresh the links to see the latest changes.
Level: 1

Type: ERROR

Impact: Other

WCS-37501: This note has been modified by another user.

Cause: Another user modified the note. You can only modify the latest version.

Action: Refresh the page to see the latest changes.
Level: 1

Type: ERROR

Impact: Other

WCS-38001: An unexpected error occurred.

Cause: The cause of this error is unknown.

Action: Try repeating the action that caused this error.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-38002: Data source ({0}) does not exist.

Cause: The specified data source is invalid.

Action: Specify a valid data source and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38003: Invalid configuration.

Cause: Either the configuration does not exist or MDSInstance is not specified.

Action: Specify a valid MDS configuration and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38004: Object ({0}) is immutable.

Cause: An attempt to change this object was made but this object is currently immutable.

Action: Either update the object to allow changes or perform this operation on another object.
Level: 1

Type: ERROR

Impact: Other

WCS-38005: An object of type {0} with ID={1} could not be found.

Cause: The object ID is invalid.

Action: Specify a valid object ID.
Level: 1

Type: ERROR

Impact: Other

WCS-38006: Unable to perform transformation

Cause: Transformation input sources were invalid.

Action: Validate the input sources and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38007: A search error occurred while searching for lists.

Cause: The search parameters were invalid.

Action: Validate the search parameters and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38008: An error occurred while configuring the List API.

Cause: An invalid List API configuration was specified.

Action: Specify a valid List API configuration and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38009: An error occurred while looking up list row data.

Cause: The database connection not found.

Action: Verify that a valid database connection exists and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38010: A search error occurred while searching the discussion forums.

Cause: A connection to the discussion forum service could not be established.

Action: Validate the discussion forum connection details in connections.xml and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38011: An error occurred while retrieving recent activity information.

Cause: Invalid parameters were passed to the Recent Activity API.

Action: Validate the API usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38012: A search error occurred while searching the service.

Cause: Invalid parameters were passed to the Search API.

Action: Validate the API usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38013: Unable to instantiate class

Cause: An invalid class reference was detected.

Action: Validate the class usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38014: Illegal access exception while accessing class

Cause: An invalid class reference was detected.

Action: Validate the class usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38015: Unable to find class

Cause: An unknown class was referenced.

Action: Verify the class reference and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38016: Unable to find 'getEnabledScopes' method in class

Cause: Class is missing required method.

Action: Verify that the method exists and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38017: Service exception while getting service registry.

Cause: Invalid parameters were passed to the Service Registry API.

Action: Validate the API usage and try again.
Level: 1

Type: ERROR

Impact: Other

WCS-38018: A null stream was returned for the RSS XML

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38019: Object instance for reading RSS feed is not available

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38020: Unable to get a HTTP connection object for the URL {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38021: Null object for the XML document

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-38022: The RSS XML does not have a root element

Cause: Invalid XML content detected

Action: Ensure that the RSS feed URL returns XML conforming to the RSS format
Level: 1

Type: WARNING

Impact: Other

WCS-38023: The root element name of the RSS XML is not rss

Cause: The XML content is not RSS XML format compliant.

Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-38024: The root element name of the RSS XML does not have any child elements

Cause: The XML content returned by the feed URL is not valid

Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-38025: The XML content returned by the feed URL does not have the channel element

Cause: The XML content is not RSS XML format compliant

Action: Ensure that XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-38026: The channel element of the RSS XML does not have any child elements

Cause: The XML content returned by the feed URL is invalid

Action: Ensure that the XML returned by the feed URL is RSS XML format compliant.
Level: 1

Type: WARNING

Impact: Other

WCS-44001: cannot load role provider implementation for service ID: {0}

Cause: The provider class configured in role-mapping-metadata tag of the specified service definition was not available to the classloader.

Action: Ensure that the provider class specified in the service-definition.xml file is available to the classloader.
Level: 1

Type: ERROR

Impact: Security

WCS-44002: The Role Mapping provider encountered an exception while performing security role mapping for service {0}.

Cause: This is caused by an error experienced by service-specific Role Mapping provider.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44003: The Role Mapping provider cannot find the service role: {0}. Exception from the provider: {1}.

Cause: The Role Mapping provider cannot find the service role. Review the exception from the provider to determine the exact cause.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44004: An internal JPS error has occurred while retrieving role-mapping information from the Application Policy Store.

Cause: Review the underlying exception in the logs to determine the cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44005: cannot find security extension in Service Registry for service ID: {0}

Cause: No security extension was registered for the given service. Perhaps the service library was not available in the classpath.

Action: Check the service library is available in the classpath. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44006: There is no mapped service role for the WebCenter Portal role {1} to which the user {0} is assigned.

Cause: A user was assigned to a WebCenter Portal role that was not yet mapped to any service role.

Action: Ensure that the WebCenter Portal role is mapped to a service role.
Level: 1

Type: WARNING

Impact: Security

WCS-44007: An internal JPS error occurred while initializing the Application Policy Store.

Cause: The Application Policy Store (jps-config.xml) was probably not configured correctly.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44009: Error obtaining JPS Service instance: {0}.

Cause: The value returned for the JPS Service instance was null. This may be caused by configuration error in jps-config.xml.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44010: A JPS error occurred while deleting users from the service ID/service role: {0} / {1}.

Cause: The error was caused while accessing the application policy store for deleting users. Review the underlying exception in the logs to determine the exact cause.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44011: Error getting handle to application policy for application {0}.

Cause: Either the application policy is not available or policy store is not configured correctly. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44012: Error getting handle to default policy store.

Cause: Either the policy store is not accessible or not configured correctly. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44101: Invalid PeoplePicker Scope {0} passed.

Cause: The scope is not of the valid type. It can be GLOBAL or SUB_SCOPED

Action: Pass a valid scope
Level: 1

Type: WARNING

Impact: Configuration

WCS-44102: Invalid PeoplePicker Scope ID {0} passed.

Cause: An invalid Scope ID has been passed.

Action: Ensure a valid scope/community ID is passed.
Level: 1

Type: WARNING

Impact: Configuration

WCS-44103: Unknown error encountered while selecting user(s) in people picker.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44104: Scope Id is a required parameter for scoped people search.

Cause: Scope Id not provided.

Action: Provide Scope Id.
Level: 1

Type: WARNING

Impact: Security

WCS-44105: And unknown error occurred while trying to validate if user {0} exists

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44106: Unknown error encountered while selecting group(s) in group picker.

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44107: And unknown error occurred while trying to validate if group {0} exists

Cause: Review the root cause of the exception for more details.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44108: The search exceeded the time limit. Check the identity store connection details or refine your search criterion.

Cause: The underlying identity store and policy store could be down.

Action: Check that underlying repositories are accessible. Check logs and contact Oracle Support
Level: 1

Type: WARNING

Impact: Security

WCS-44109: The search exceeded the size limit. Refine your search criterion.

Cause: The search results in a large dataset that is not supported by the underlying identity store.

Action: Refine your search criterion to something more narrow.
Level: 1

Type: WARNING

Impact: Security

WCS-44110: An unexpected error occurred while searching for users/roles. Check logs for further details.

Cause: An unexpected error occurred while searching for identities. Consult the underlying cause.

Action: If the underlying cause does not provide any action, contact Oracle Support.
Level: 1

Type: ERROR

Impact: Security

WCS-44151: An error occurred while retrieving the Identity Store.

Cause: This is caused when the Identity Store configured in jps-config.xml is not accessible or is not running. Review the underlying exception in the logs to determine the exact cause.

Action: Ensure that the Identity Store is configured correctly in jps-config.xml and is running. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Security

WCS-44152: An error occurred while sending an e-mail.

Cause: The error occurred because the e-mail account or the e-mail service was not configured correctly or the e-mail server was not running.

Action: Ensure that your e-mail account and the e-mail service are configured properly and the e-mail server is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44153: An error occurred while generating the HMAC token.

Cause: The JVM did not support MessageDigest algorithms, such as MD5 or SHA, or the UTF8 encoding.

Action: Ensure the JVM supports UTF8 encoding and MD5/SHA message digest algorithms. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44154: An error occurred while getting the scope roles for scope ID {0}.

Cause: Either the policy store was configured incorrectly or was inaccessible or the scope ID passed was invalid.

Action: Ensure that the policy store is configured correctly and is running. Also, ensure that the scope ID passed is valid.
Level: 1

Type: ERROR

Impact: Security

WCS-44155: The permission class is null for the service ID: {0}.

Cause: The permission class was not defined in the service-definition.xml file.

Action: Ensure that the permission class is defined in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44156: The value of resource bundle is null for the service ID: {0}.

Cause: The resource bundle was not defined in the service-definition.xml file.

Action: Ensure that the resource bundle is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44157: The value of permission target is null for the service ID: {0}.

Cause: The permission target was not defined in the service-definition.xml file.

Action: Ensure that the permission target is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44158: The value of permission action is not defined for the service ID: {0}.

Cause: The permission action (permission-action-list tag) was not defined in the service-definition.xml file.

Action: Ensure that the permission actions are defined in the service-definition.xml file by using the permission-action-list tag.
Level: 1

Type: ERROR

Impact: Security

WCS-44159: The value of permission admin action is not defined for the service ID: {0}.

Cause: The permission admin action (permission-manage-action tag) was not defined in the service-definition.xml file.

Action: Ensure that the permission admin actions are defined in the service-definition.xml file by using the permission-manage-action tag.
Level: 1

Type: ERROR

Impact: Security

WCS-44160: The role mapping class is not defined for the service ID: {0}.

Cause: The role mapping class was not defined in the service-definition.xml file.

Action: Ensure that the role mapping class is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44161: The role mapping resource bundle is not defined for the service ID: {0}.

Cause: The role mapping resource bundle was not defined in the service-definition.xml file.

Action: Ensure that the role mapping resource bundle is defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44162: Security Extension is not defined for the service ID: {0}.

Cause: The Security Extension (security-definition node) was not defined in the service-definition.xml file of the service.

Action: Ensure that the Security Extension (security-definition node) is properly defined in the service-definition.xml file.
Level: 1

Type: ERROR

Impact: Security

WCS-44163: An error occurred while retrieving service extension definition(service-definition.xml).

Cause: The service jars are not correctly packaged or the jars are corrupt.

Action: Ensure that webcenter framework shared library is correctly defined and the library jars are not corrupt.
Level: 1

Type: ERROR

Impact: Security

WCS-44164: An error occurred while retrieving the spi file .

Cause: The are multiple spi files.

Action: Ensure that only spi file with the name oracle.webcenter.security.selfregistration.custom.SelfRegActionHandlerSpi.properties exists.
Level: 1

Type: ERROR

Impact: Security

WCS-44165: The principal is not of type JpsRole

Cause: The principal object passed to the api is not of type JpsRole.

Action: Ensure that the parameter passed to the api is of type JpsRole.
Level: 1

Type: WARNING

Impact: Security

WCS-44166: Application Policy for {0} does not exist. Creating a new application policy.

Cause: The application did not package any policies.

Action: None as a new policy has been created. However ensure that application did not indeed package any policies and this was not a case of policies not being migrated. Contact Oracle Support in that case.
Level: 1

Type: WARNING

Impact: Security

WCS-44167: Public registration is not enabled for this site.

Cause: The public registration option is not enabled.

Action: Ensure that public registration is enabled in the general tab of Webcenter administration.
Level: 1

Type: WARNING

Impact: Security

WCS-44168: The principal argument is null

Cause: The principal object passed to the api is null.

Action: Ensure that the parameter passed to the api is not null.
Level: 1

Type: WARNING

Impact: Security

WCS-44169: Error while determining security attributes for user {0}

Cause: The user {0} passed to determine security attributes does not exist in the underlying identity store.

Action: Ensure the user name is valid.
Level: 1

Type: WARNING

Impact: Security

WCS-44170: Error occurred while retrieving the security attributes of user {0}

Cause: An error occurred while querying the identity store or the policy store to determine the user's security attributes. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44171: Error occurred while determining security attributes for service {0}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44172: Error occurred while determining security attributes for service {0} in scope {1}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and scope. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44173: Error occurred while determining security attributes for artifact {0} belonging to service {1}

Cause: An error occurred while querying the policy store to determine the principals that were granted view access for the given service and artifact. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44174: Error encountered while getting the HMAC initial key from the credential store

Cause: There is a problem while accessing the credential store. Review the underlying exception in the logs to determine the exact cause.

Action: Ensure the credential store is setup properly. Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44175: Error occurred while obtaining mapped service {0} roles for WebCenter Portal role {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44176: Error occurred while obtaining mapped application roles for service {0} and service role with ID {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44177: Error occurred while adding role mapping entry for service {0} and service role {1} to webcenter role {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services. This error can be ignored if upgrade is being re-run.
Level: 1

Type: ERROR

Impact: Security

WCS-44178: Error occurred while removing role mapping entry for service {0} and service role {1} from WebCenter Portal role {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44179: Error occurred while removing role mapping entries for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44180: Error occurred while removing role mapping entries for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44181: Error occurred while fetching role mapping metadata for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44182: Error occurred while adding role mapping metadata to scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44183: Cannot copy role mapping metadata for scope {0} as the metadata already exists

Cause: Role mapping metadata already existed for the given scope.

Action: Remove the role mapping metadata for the scope and then perform this operation again. Alternatively, you can pass a different scope for which the role mapping metadata does not already exist.
Level: 1

Type: ERROR

Impact: Security

WCS-44184: Error occurred while fetching role mapping metadata for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44185: Error occurred while adding role mapping metadata for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44186: Unable to obtain service {0} role mapping metadata for scope {1}

Cause: The query to obtain role mapping metadata for the scope returned a path for which the metadata did not exist.

Action: Ensure the service role mapping metadata exists for the scope.
Level: 1

Type: WARNING

Impact: Security

WCS-44187: The role mapping metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.

Cause: Another user acquired the write lock on the service role mapping metadata.

Action: Try the operation after some time.
Level: 1

Type: WARNING

Impact: Security

WCS-44188: Cannot copy the role mapping metadata for service {0} in scope {1}

Cause: The service role mapping metadata for the scope already existed.

Action: Remove the service role mapping for the scope and then perform the operation again. Alternatively, you can pass a different service and scope for which the role mapping metadata does not already exist.
Level: 1

Type: ERROR

Impact: Security

WCS-44189: Cannot find the WebCenter Portal application role {0}

Cause: The WebCenter Portal application role passed to Role Manager did not exist.

Action: Ensure that a valid application role is passed to Role Manager.
Level: 1

Type: ERROR

Impact: Security

WCS-44190: Error copying role mapping metadata from role {0} to role {1} in scope {2}

Cause: Role mapping metadata could not be copied. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. To perform role mapping, use the Roles tab in the portal settings.
Level: 1

Type: ERROR

Impact: Security

WCS-44191: Error deleting role mapping metadata from role {0} in scope {1}

Cause: The role mapping metadata could not be deleted. Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44192: Error while determining enterprise role mapping support. Enterprise groups, and not the individual group members, will be added directly as members.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: If a service configured does not support enterprise role mapping, then take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44193: The permission action is invalid for the service ID: {0}.

Cause: Either permission action name or icon was not specified in the service-definition.xml file.

Action: Ensure that the permission action name and icon is defined correctly in the service-definition.xml file for the service. The permission action should be specified as <permission-action name="view" icon="/adf/webcenter/view_qualifier.png"/>
Level: 1

Type: ERROR

Impact: Security

WCS-44194: The application level permission class is null for the service ID: {0}.

Cause: The application permission class was not defined in the service-definition.xml file.

Action: Ensure that the application permission class is defined in the service-definition.xml file for the service. The application permission class should be specified as <application-permission-impl>permission class</application-permission-impl> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44195: The application level permission target is not defined for the service ID: {0}.

Cause: The application permission target was not defined in the service-definition.xml file.

Action: Ensure that the application permission target is defined in the service-definition.xml file for the service. The application permission target should be specified as <application-permission-target-id>permission target</application-permission-target-id> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44196: The application level permission actions is not defined for the service ID: {0}.

Cause: The application permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the application permission actions list is defined in the service-definition.xml file for the service. The application permission actions should be specified as <application-permission-action-list>permission actions</application-permission-action-list> in <application-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44197: The scope level permission class is not defined for the service ID: {0}.

Cause: The scope permission class was not defined in the service-definition.xml file.

Action: Ensure that the scope permission class is defined in the service-definition.xml file for the service. The scope permission class should be specified as <scope-permission-impl>permission class</scope-permission-impl> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44198: The scope level permission target is not defined for the service ID: {0}.

Cause: The scope permission target was not defined in the service-definition.xml file.

Action: Ensure that the scope permission target is defined in the service-definition.xml file for the service. The scope permission target should be specified as <scope-permission-target-id>permission target</scope-permission-target-id> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44199: The scope level permission actions is not defined for the service ID: {0}.

Cause: The scope permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the scope permission actions list is defined in the service-definition.xml file for the service. The scope permission actions should be specified as <scope-permission-action-list>permission actions</scope-permission-action-list> in <scope-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44200: The resource level permission class is not defined for the service ID: {0}.

Cause: The resource permission class was not defined in the service-definition.xml file.

Action: Ensure that the resource permission class is defined in the service-definition.xml file for the service. The resource permission class should be specified as <resource-permission-impl>permission class</resource-permission-impl> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44201: The resource level permission target is not defined for the service ID: {0}.

Cause: The resource permission target was not defined in the service-definition.xml file.

Action: Ensure that the resource permission target is defined in the service-definition.xml file for the service. The resource permission target should be specified as <resource-permission-target-id>permission target</resource-permission-target-id> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44202: The resource level permission actions is not defined for the service ID: {0}.

Cause: The resource permission actions list was not defined in the service-definition.xml file.

Action: Ensure that the resource permission actions list is defined in the service-definition.xml file for the service. The resource permission actions should be specified as <resource-permission-action-list>permission actions</resource-permission-action-list> in <resource-permission> node.
Level: 1

Type: ERROR

Impact: Security

WCS-44203: The application role operations list is not specified at the application level for the service ID: {0}.

Cause: The application role operations list is not specified at the application level. It was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the application level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44204: The application role operations list is not specified at the scope level for the service ID: {0}.

Cause: The application role operations list is not specified at the scope level was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the scope level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44205: The application role operations list is not specified at the resource level for the service ID: {0}.

Cause: The application role operations list is not specified at the resource level was not defined in the service-definition.xml file.

Action: Ensure that the application role operations list is defined at the resource level in the service-definition.xml file for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44206: The application role operation specified is invalid for the service ID: {0}.

Cause: Operation name or application role or icon has not been specified correctly for the application role operation in service-definition.xml

Action: Ensure that the application role operation is specified correctly with operation name, application role and icon in the service-definition.xml file for the service. An application role operation entry looks like this - <application-operation name="manage" approle="AppConnectionManager" icon="/adf/webcenter/manage.png"/>
Level: 1

Type: ERROR

Impact: Security

WCS-44207: Error occurred while adding resource {0} security override entry for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44208: Error occurred while removing resource {0} security override entry for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44209: Error occurred while checking if resource {0} override security for service {1} in scope {2}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44210: Error occurred while removing security override entries for scope {0}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44211: Error occurred while removing security override entries for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44212: The security override metadata for service {0} in scope {1} is being modified by another user. Try the operation again after some time.

Cause: Another user acquired the write lock on the service security override metadata.

Action: Try the operation after some time.
Level: 1

Type: WARNING

Impact: Security

WCS-44213: Invalid Security Handler for service {0}. Expected Type: {1} Actual Type: {2}.

Cause: Security Handler defined in service-definition was of incorrect type

Action: Define the correct security handler in the service-definition as specified
Level: 1

Type: ERROR

Impact: Security

WCS-44214: Security Extension not found for service {0}.

Cause: Security Extension not defined in service-definition.

Action: Define the security extension appropriately in the service-definition.
Level: 1

Type: ERROR

Impact: Security

WCS-44215: Security Handler not found for service {0}.

Cause: Security Handler specified in the security extension is either undefined or could not be found.

Action: Ensure the correct security handler class is defined in the security extension of service-definition.
Level: 1

Type: ERROR

Impact: Security

WCS-44216: Could not determine security authorization type for service {0}. It needs to be one of the following - PERMISSION, APPLICATION_ROLE or ROLEMAPPING.

Cause: The security extension either does not contain any authorization model or contains more than one.

Action: Depending on the authorization model, security extension must be updated to specify the appropriate security model.
Level: 1

Type: ERROR

Impact: Security

WCS-44217: Permission security model not defined at {0} level for service {1}.

Cause: Permission check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level permission security model

Action: Either define specified level permission security metadata or do not attempt security provisioning or check at given level for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44218: Application Roles security model not defined at {0} level for service {1}.

Cause: Security check or provisioning is being attempted at specified level where as the security extension in the service-definition does not define given level application role security model

Action: Either define specified level application role security metadata or do not attempt security provisioning or check at given level for the service.
Level: 1

Type: ERROR

Impact: Security

WCS-44219: Error occurred revoking permissions for {0} service resource {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44220: Application Role not defined for {0} service action {1} at {2} level.

Cause: Application Role for the given service action and level not defined in security extension of service-definition.

Action: Define the application role mapping for the given service action at the given level else do not attempt security provisioning or check for the service at given level.
Level: 1

Type: ERROR

Impact: Security

WCS-44221: Error occurred checking {0} action for {1} service at {2} level.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44222: An error occurred while retrieving the policies or permissions.

Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.

Action: Ensure that the policy store and service definition is configured properly and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44223: An error occurred while saving the permissions.

Cause: This is caused when the policy store is not accessible or is not running or the service definition is not defined properly.

Action: Ensure that the policy store and service definition is configured properly and is running.
Level: 1

Type: ERROR

Impact: Security

WCS-44224: An error occurred while saving the permissions.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44225: An error occurred while setting service id.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44226: Error while accessing data from OPSS Policy Store.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details. If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Security

WCS-44227: An error occurred while getting portal assets and WebCenter Portal services

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44228: An error occurred while determining list of portal assets that override security for service {0} in scope {1}

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44229: An error encountered while getting mapped action.

Cause: This is caused when the service definition is not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: WARNING

Impact: Security

WCS-44230: An error encountered while trying to retrieve {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44231: An error encountered while trying to grant {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause. The grant could already exist.

Action: Take action based on the underlying exception details. If the grant already exists, revoke the grant using WLST and perform operation again.
Level: 1

Type: ERROR

Impact: Security

WCS-44232: An error encountered while trying to revoke {0} service policies at {1} level for scope {2} and asset {3}.

Cause: Review the underlying exception in the logs to determine the exact cause. The grant being revoked probably does not exist.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44233: An error encountered while trying to obtain subject for user {0}, returning anonymous user subject instead.

Cause: Review the underlying exception in the logs to determine the exact cause.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44234: An error encountered while trying to create role {0}.

Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44235: An error encountered while trying to get application roles.

Cause: Review the underlying exception in the logs to determine the exact cause. The roles may not exists or there is an issue with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44236: An error encountered while trying to create role {0}.

Cause: Review the underlying exception in the logs to determine the exact cause. The role may be already exists or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44237: An error encountered while trying to get members.

Cause: Review the underlying exception in the logs to determine the exact cause. The members may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44238: An error encountered while trying to get members.

Cause: Review the underlying exception in the logs to determine the exact cause. The member may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44239: An error encountered while trying to delete members.

Cause: Review the underlying exception in the logs to determine the exact cause. The member may already exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44240: Cannot access the resource

Cause: The service was not defined properly.

Action: Ensure that the service definition is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44241: Failed to issue token.

Cause: Trust Service Token Manager failed to issue the token.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44242: TrustService instance is null.

Cause: Failed to get TrustService instance from the JPS context.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44243: TokenManager instance is null.

Cause: Failed to get TokenManager instance from the TrustService.

Action: Take action based on the underlying exception details.
Level: 1

Type: WARNING

Impact: Security

WCS-44244: Could not execute search

Cause: The identity store is not up or is not configured properly.

Action: Ensure that the identity store is up and configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44245: Could not add to role

Cause: The policy object already exists or the policy store is not configured properly.

Action: Ensure that the policy is not already added and policy store is configured properly.
Level: 1

Type: ERROR

Impact: Security

WCS-44246: An internal JPS error occurred while exporting / importing application roles.

Cause: This may have been caused when retrieving information from the Application Policy Store or while granting permissions to roles.

Action: Review the exception to determine exact cause.
Level: 1

Type: WARNING

Impact: Security

WCS-44247: Could not delete application role {0}.

Cause: This may have been caused because the role to be deleted does not exist any more.

Action: Review the exception to determine exact cause.
Level: 1

Type: WARNING

Impact: Security

WCS-44248: The documents role mapping failed during import for portal : {0} and application role {1}.

Cause: This is caused by an error experienced by service-specific Role Mapping provider.

Action: Inspect the server logs and rectify the problem encountered by the service Role Mapping provider.
Level: 1

Type: ERROR

Impact: Security

WCS-44249: No application role found for scope : {0}.

Cause: This may be due to an error that could have occurred during Portal creation or import due to which the roles were not created.

Action: Inspect the logs to confirm which Portal is this error being thrown for and try manually accessing the Portal. If the Portal is inaccessible, re try import or, re create the Portal.
Level: 1

Type: WARNING

Impact: Security

WCS-44250: Unable to obtain MDSSession to initialize {0} store.

Cause: This is caused by an underlying MDS Configuration exception while trying to initialize the customization config.

Action: Review the exception to determine exact cause.
Level: 1

Type: ERROR

Impact: Security

WCS-44251: Start time {0} specified for an impersonation grant cannot be after end time {1}

Cause: Start time for impersonation grant is after end time

Action: Ensure start time specified for an impersonation grant is before end time
Level: 1

Type: WARNING

Impact: Security

WCS-44252: You cannot add, update, or remove yourself as an impersonator

Cause: Adding, updating, or removing oneself as an impersonator is not allowed

Action: Ensure impersonator being added, updated or removed is a valid impersonator
Level: 1

Type: WARNING

Impact: Security

WCS-44253: Impersonator {0} already added for user {1}

Cause: You can add an impersonator only once for a user

Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant
Level: 1

Type: WARNING

Impact: Security

WCS-44254: Impersonatee {0} already added for user {1}

Cause: You can add an impersonator only once for a user

Action: Ensure you add an impersonator only once for a user. To specify a different time duration, edit the existing grant
Level: 1

Type: WARNING

Impact: Security

WCS-44255: Cannot update or delete impersonator {0} for user {1} as impersonator not yet added

Cause: The impersonator being updated or deleted has not been added yet

Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant
Level: 1

Type: WARNING

Impact: Security

WCS-44256: Cannot update or delete impersonatee {0} for user {1} as impersonatee not yet added

Cause: The impersonator being updated or deleted has not been added yet

Action: Ensure the impersonator has been added before trying to update or remove the impersonation grant
Level: 1

Type: WARNING

Impact: Security

WCS-44257: Impersonator user {0} could not be found

Cause: The impersonator specified is not a valid user

Action: Ensure you specify a valid impersonator
Level: 1

Type: WARNING

Impact: Security

WCS-44258: Impersonatee user {0} could not be found

Cause: The impersonatee specified is not a valid user

Action: Ensure you specify a valid impersonatee
Level: 1

Type: WARNING

Impact: Security

WCS-44259: Fetching Impersonator user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44260: Fetching Impersonatee user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44261: Adding impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44262: Updating impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44263: Removing impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44264: Getting impersonators for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44265: Getting impersonatees for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44266: Removing expired impersonation grants for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44267: Starting impersonation session for user {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44268: Terminating impersonation session for current user failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44269: User {0} is not a valid impersonator

Cause: The user specified as impersonator does not belong to webcenter#-#impersonators role.

Action: Ensure you specify a user that belongs to webcenter#-#impersontors role.
Level: 1

Type: WARNING

Impact: Security

WCS-44270: Determining if user {0} is a valid impersonator failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44271: Adding or updating impersonator {0} for user {1} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44272: Searching for impersonators matching pattern {0} failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44273: Impersonation Time delta {0} specified is in invalid format

Cause: Time delta specified was not a valid integer

Action: Check documentation to understand the format in which this delta needs to be specified. It needs to be a valid integer
Level: 1

Type: WARNING

Impact: Security

WCS-44274: Impersonation configuration check failed

Cause: Review the underlying exception in the logs to determine the exact cause

Action: Take action based on the underlying exception details
Level: 1

Type: ERROR

Impact: Security

WCS-44300: An error encountered while granting permissions

Cause: Review the underlying exception in the logs to determine the exact cause. The policy may already have been granted or the identity may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44301: An error encountered while revoking permissions

Cause: Review the underlying exception in the logs to determine the exact cause. The policy may not exist or the identity may not exist or there is a problem with the policy store.

Action: Take action based on the underlying exception details.
Level: 1

Type: ERROR

Impact: Security

WCS-44302: An OPSS error occurred while locating the audit service.

Cause: The error would be caused when Audit Service is not configured. Review the jps-config.xml configuration file in conjunction with the stack trace if Audit Service needs to be enabled for WebCenter Portal.

Action: If the exception details do not provide sufficient information to resolve the issue, then contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Security

WCS-44304: Invalid security attribute {0} obtained for artifact {1} in service {2}

Cause: The security attribute returned by the service does not comply to the list of expected security attributes

Action: Ensure the security attribute is one of the expected values i.e. user, group, application role, authenticated and anonymous roles
Level: 1

Type: ERROR

Impact: Security

WCS-47201: An unexpected error occurred in the Activity Stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47202: The publish activity failed because invalid arguments were passed to the method: activity ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47203: The retrieve activities failed because invalid arguments were passed to the method: privateAndUpActorIds ({0}), sharedAndUpActorIds ({1}), publicActorIds ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47205: Cannot establish connections. A connections exception was thrown.

Cause: A connections exception has been thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47206: A Service Framework exception was thrown.

Cause: A Service Framework exception has been thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47207: A Settings exception was thrown.

Cause: A Settings exception was thrown.

Action: Check the exception's details to see why it was thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-47208: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47209: The retrieve activities failed because invalid arguments were passed to the method: applicationId ({0}), servivceId ({1}), activityType ({2}), sinceDate ({3}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47210: A database exception occurred in the Activity Stream Toplink module.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47211: A query exception occurred in the Activity Stream Toplink module.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47212: Create Actor failed because an invalid argument was passed to the method: guid ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47213: Create Object failed because an invalid argument was passed to the method: guid ({0}), type ({1}), displayName ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47214: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), scope ({1}), serviceID ({2}), activityType ({3}), actors ({4}), permission ({5}), activityTime ({6}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47215: Create Activity Type failed because an invalid argument was passed to the method: id ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47216: Create Object Type failed because an invalid argument was passed to the method: id ({0}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47217: Create Activity Element failed because an invalid argument was passed to the method: applicationID ({0}), activityType ({1}), actors ({2}), permission ({3}), activityTime ({4}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47218: Publish activity {0} failed due to {1}.

Cause: An unexpected error during the publishing activity.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47219: An error occurred due to {0}.

Cause: An exception occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47220: An unexpected error occurred resolving property ''{0}'':''{1}'' for an Analytics event of type {2}

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47221: Unable to publish the Analytics event (of type {0}).

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47222: This operation is not supported.

Cause: This operation not supported.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47223: Skipping profile information for user {0}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47224: For user {0}, the last accessed page couldn''t be found due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47225: Check for valid repository failed.

Cause: Either the database is down or the WebCenter repository is not installed.

Action: Check the exception's details to why this error occurred.
Level: 1

Type: ERROR

Impact: Other

WCS-47226: For user {0}, couldn''t retrieve the list of pages last accessed due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47227: For user {0}, couldn''t retrieve the last accessed page in {1} due to {2}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47228: For user {0}, couldn''t clean the last accessed page due to {1}

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-47229: The task flow instance was not specified.

Cause: The supplied taskflow instance ID was null or blank.

Action: Specify a valid taskflow instance ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47230: An activity exception was encountered during the bulk publish operation.

Cause: One or more activities threw an exception.

Action: Check the individual activity exception.
Level: 1

Type: ERROR

Impact: Other

WCS-47231: Create Cust Attr failed because an invalid argument was passed to the method: name ({0}), value ({1}), url ({2}).

Cause: One of the input arguments was invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47232: An unexpected error occurred while setting up the Comments service.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47233: An unexpected error occurred while retrieving comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47234: An unexpected error occurred while posting a comment.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47235: An unexpected error occurred while preparing a comments summary.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47236: An unexpected error occurred while preparing comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47237: Comment text cannot be empty.

Cause: The supplied text for the comment is null or blank.

Action: Specify a non-empty text for the comment.
Level: 1

Type: ERROR

Impact: Other

WCS-47238: An object was not specified.

Cause: The supplied object identifier is null.

Action: Specify a non-null object identifier.
Level: 1

Type: ERROR

Impact: Other

WCS-47239: An object ID is not present for the specified object.

Cause: The ID of the specified object is null.

Action: Specify an object with a valid ID.
Level: 1

Type: ERROR

Impact: Other

WCS-47240: A service ID is not present for the specified object.

Cause: The service ID for the specified object is null.

Action: Specify an object with a valid service ID.
Level: 1

Type: ERROR

Impact: Other

WCS-47241: An object type is not present for the specified object.

Cause: The object type for the specified object is null.

Action: Specify an object with a valid object type.
Level: 1

Type: ERROR

Impact: Other

WCS-47242: An unexpected error while expanding comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47243: An unexpected error occurred while collapsing comments.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47244: An unexpected error occurred while setting up the Likes service.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47245: An unexpected error occurred while retrieving Likes.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47246: An unexpected error occurred while retrieving Likes.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47247: An unexpected error occurred while posting a Like.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47248: A comment ID not specified.

Cause: The supplied comment ID was null or blank.

Action: Specify a valid comment ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47249: An unexpected error occurred while deleting a comment.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47250: An unexpected error occurred while initializing the scope.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47252: The followed object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}), object service id ({2}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47253: Can''t archive due to an invalid argument: date ({0}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47254: An unexpected error occurred while archiving.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47255: Failed to register application management beans.

Cause: Application management beans(MBean) registration failed. Either there are issues with WebLogic or the application was not packaged properly.

Action: Restart WebLogic or examine WebLogic log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-47256: Failed to unregister application management beans.

Cause: Application management beans(MBean) unregistration failed. Either the Mbeans were not registered or the Mbeans were already unregistered.

Action: Examine the WebLogic log files for further details.
Level: 1

Type: ERROR

Impact: Other

WCS-47257: An unexpected error occurred while deleting service data corresponding to the activity.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47258: The advanced query parameter contains invalid or unsupported constructs.

Cause: There are invalid or unsupported SQL constructs specified in the Advanced Query filter parameter.

Action: Correct the Advanced Query filter parameter.
Level: 1

Type: ERROR

Impact: Other

WCS-47259: An unexpected error occurred in setting up the JMS queue {0}.

Cause: The AQ JMS ConnectionFactory or Queue lookup failed.

Action: Correct JMS Modules in Admin Console.
Level: 1

Type: ERROR

Impact: Other

WCS-47260: An unexpected error occurred while send message to the JMS queue.

Cause: The JMS Queue found, but enqueue failed.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47261: Fail to get Resource URI for published Activity.

Cause: The ResourceActionUtils.getUrl() failed for input Activity.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47262: Fail to get Activity message for message key {0} in bundle {1}.

Cause: The getMessage() failed for input Activity.

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47263: Failed to unfollow objects due to {0}.

Cause: An unexpected error occurred during the unfollowing objects.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47264: The unfollowed object failed because an invalid arguments was passed to the method: actor ({0}), object ({1}).

Cause: One of the input arguments is invalid.

Action: Ensure that all arguments passed are valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47265: Failed to initialize context for asynchronous activity listeners processing.

Cause: Failed to initialize context for asynchronous activity listeners processing.

Action: Contact Administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-47266: Failed to parse the actitvity definition file {0} due to {1}

Cause: Validate the activity-definition.xml file..

Action: Examine the Weblogic log files for exception details.
Level: 1

Type: ERROR

Impact: Other

WCS-47267: Failed to lookup connection for name {0}.

Cause: Invalid OSN connection name.

Action: Contact Administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-47268: Could not load extension handler due to {0}.

Cause: Could not load extension handler.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47269: Can not close transaction due to {0}.

Cause: Can not close transaction.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47270: Can not close statement due to {0}.

Cause: Can not close statement.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47271: Can not get result set due to {0}.

Cause: Can not get result set.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47272: Can not rollback transaction due to {0}.

Cause: Can not rollback transaction.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47273: Can not load XML actor detail data due to {0}.

Cause: Can not load XML actor detail data.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47274: Can not insert new actor details due to {0}.

Cause: Can not insert new actor details.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47275: Error occurs when processing activity {0} for activity listener{1} due to {2}.

Cause: Could not call activity listener's onsActivity method.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47276: Failed while retrieving activity listeners due to {0}

Cause: Failed while retrieving activity listeners.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47277: Failed to initialize due to {0}

Cause: Failed to initialize.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47278: Cannot get service registry due to {0}.

Cause: Error to get service registry.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47279: Error closing entity manager factory due to {0}

Cause: An unexpected exception occured while closing the entity manager factory.

Action: Review the exception thrown for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47280: No default value found for key {0}.

Cause: No default value found for key {0}.

Action: Ensure default value for key {0} is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-47281: Cannot get activity services list due to {0}.

Cause: Cannot get activity services list.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47282: Resource bundle not found. bundle = {0}, key = {1} .

Cause: Resource bundle not found.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47283: Key not found. bundle = {0}, key = {1} .

Cause: Key not found.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47284: Service category {0} is invalid, title key not found, ignoring.

Cause: Service category is invalid, therefore title key not found.

Action: Examine the WebCenter log files for exception details
Level: 1

Type: WARNING

Impact: Other

WCS-47285: Unable to compare Service Settings due to {0}.

Cause: Unable to compare Service Settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47286: Cannot parse to date due to {0}.

Cause: Cannot parse to date.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47287: Cannot parse from date due to {0}.

Cause: Cannot parse from date.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47288: Cannot set access control configurable due to {0}.

Cause: Cannot set access control configurable.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47289: Cannot set configurable service category settings due to {0}.

Cause: Cannot set configurable service category settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47290: Can not process activity {0} due to {1}.

Cause: >Can not process activity.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47291: Failed to get profile guid {0} due to {1}.

Cause: Failed to get profile guid.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47292: Failed to get profile id {0} due to {1}.

Cause: Failed to get profile guid.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47293: Cannot summarize activities due to activity list is null.

Cause: Cannot summarize activities due mActivities is null.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47294: Cannot get object type display name due to {0}.

Cause: Cannot get object type display name.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47295: Could not publish activity even after retry due to {0}.

Cause: Could not publish activity even after retry.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47296: Error while retrieving activities due to {0}.

Cause: Error while retrieving activities.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47297: Error while processing personal criteria due to {0}.

Cause: Error while processing personal criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47298: Error while processing portals criteria due to {0}.

Cause: Error while processing portals criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47299: Error while processing service id criteria due to {0}.

Cause: Error while processing service id criteria .

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47300: Error while processing activity type criteria due to {0}.

Cause: Error while processing activity type criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47302: Error while processing enterprise id criteria due to {0}.

Cause: Error while processing enterprise id criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47303: Error while processing date criteria due to {0}.

Cause: Error while processing date criteria.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47304: Skipping rendering activity {0} due to {1}.

Cause: Skipping rendering activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47305: Cannot get profile due to {0}.

Cause: Cannot get profile.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47306: Failed to get activity type icon url due to {0}.

Cause: Failed to get activity type icon url.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47307: Failed to get activity type due to {0}.

Cause: Failed to get activity type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47308: Failed to get activity type category due to {0}.

Cause: Failed to get activity type category.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47309: Failed to get inline preview due to {0}.

Cause: Failed to get inline preview.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47310: Failed to get object type due to {0}.

Cause: Failed to get object type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47311: Client listener not supported {0}.

Cause: Client listener not supported.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47312: Cannot convert user guid {0} to id due to {1}.

Cause: Cannot convert user guid to id.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47313: Could not publish activity due to {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47314: Cannot get preference maps due to {0}.

Cause: Cannot get preference maps .

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47315: Cannot obtain scope {0} due to {1}.

Cause: Cannot obtain scope.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47316: Failed to publish Activity. Activity Detail: {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47317: Failed to publish Activity. Actor Detail: {0}.

Cause: Could not publish activity.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47318: Cannot summarize activities due to {0}.

Cause: Cannot summarize activities.

Action: Examine the WebCenter log files for more details.
Level: 1

Type: WARNING

Impact: Other

WCS-47319: Cannot get service {0} due to {1}.

Cause: Error to get service.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47320: During creating of UI components, can not get the object type.

Cause: During creating of UI components, can not get the object type.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47321: Failed to initialize activity stream settings due to {0}

Cause: Fail to initialize activity stream settings.

Action: Examine the WebCenter log files for exception details.
Level: 1

Type: WARNING

Impact: Other

WCS-47695: Unexpected error saving settings

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47696: Fatal error initializing the settings management sub-system

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47697: Unexpected error retrieving settings

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47698: Unable to locate the settings document

Cause: Either the document path was incorrect or the document had got deleted.

Action: Ensure that the document path is correct and that the document exists.
Level: 1

Type: ERROR

Impact: Other

WCS-47699: Unable to determine current user

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47700: An unexpected error occurred in the People Connections sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47801: An unexpected error occurred in the Connections sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-47802: User not specified

Cause: The supplied username was null or blank.

Action: Specify a valid username that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47803: Unexpected error retrieving connections for user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47804: Unexpected error retrieving invitations for current user

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47805: User ''{0}'' not found

Cause: The system could not find any user with the specified username.

Action: Specify a valid username.
Level: 1

Type: ERROR

Impact: Other

WCS-47806: Unexpected error sending invitation to user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47807: Invitation not found (the invitation may have been withdrawn, accepted, or declined already)

Cause: The system could not find any invitation with the specified ID.

Action: Ensure that the specified invitation ID is valid.
Level: 1

Type: ERROR

Impact: Other

WCS-47808: Invitation ID not specified

Cause: The supplied invitation ID was null or blank.

Action: Specify a valid invitation ID that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47809: Unexpected error accepting invitation with ID ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47810: Unexpected error declining invitation with ID ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47811: Unexpected error ignoring invitation with ID ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47812: Unexpected error removing connection with user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47813: Unexpected error retrieving profile of user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47814: Unexpected error retrieving the connection lists owned by user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47815: Connection list not specified

Cause: The supplied connection list name was null or blank.

Action: Specify a valid connection list name that is not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-47816: Connection list named ''{0}'' not found for user ''{1}''

Cause: The system could not find any connection list with the specified name owned by the specified user.

Action: Ensure that the username is correct and that the connection list name refers to a connection list owned by that user.
Level: 1

Type: ERROR

Impact: Other

WCS-47817: Unexpected error getting Connection list ''{0}'' for user ''{1}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47818: User does not have the privilege required to perform specified operation

Cause: Either the system policy or the target user's access control settings restrict the current user from performing this operation

Action: Contact the Administrator to grant the required permission, or contact the target user to allow access
Level: 1

Type: ERROR

Impact: Other

WCS-47819: Unexpected error creating a Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47820: Unexpected error adding users to Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47821: Unexpected error deleting Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47822: Unexpected error retrieving members of Connection list with name ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47823: Unexpected error retrieving invitations sent by current user

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47824: Unexpected error removing user ''{0}'' from one or more Connection lists

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47825: Unexpected error setting Connection list membership of user ''{0}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47826: Unexpected error retrieving the Connection lists to which user ''{0}'' belongs

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47827: Unexpected error creating a connection between users ''{0}'' and ''{1}''

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47828: Unexpected error preparing the user invitation screen

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47829: Cannot invite oneself as a connection

Cause: You have specified yourself as the invitee.

Action: Specify a username other than that of yourself.
Level: 1

Type: ERROR

Impact: Other

WCS-47830: Cannot invite a user who has been invited already ({0})

Cause: The user you have specified has already been invited.

Action: Wait for the invited user to act on your invitation.
Level: 1

Type: ERROR

Impact: Other

WCS-47831: Cannot invite a user who has already invited you ({0})

Cause: The user you have specified has already invited you.

Action: Accept the invitation you have received from the user.
Level: 1

Type: ERROR

Impact: Other

WCS-47832: Cannot invite a user you are already connected with ({0})

Cause: You have specified one of your existing connections as the invitee.

Action: Specify a username other than that of your existing connections.
Level: 1

Type: ERROR

Impact: Other

WCS-47833: Unexpected error searching for users

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47834: Cannot create a connection between users ''{0}'' and ''{1}'' who already connected

Cause: The specified users are already connected with each other.

Action: Specify users who are not yet connected.
Level: 1

Type: ERROR

Impact: Other

WCS-47835: Unexpected error reading configuration

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47836: Unexpected error getting connections with preferences (userGuid = {0}, applicationId = {1}, scope = {2}, serviceId = {3}, settingKey = {4}, configurableSettingKey = {5})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47837: Unexpected error getting connections lists with preferences (listNames = {0}, userGuid = {1}, applicationId = {2}, scope = {3}, serviceId = {4}, settingKey = {5}, configurableSettingKey = {6})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-47838: Cannot create a Connection list with the same name as existing one ({0})

Cause: You already have a connection list with the specified name.

Action: Specify a name other than that of your existing connection lists.
Level: 1

Type: ERROR

Impact: Other

WCS-47839: Unexpected error getting all connections (startIndex = {0}, itemsPerPage = {1})

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-49001: Injectable Service provider did not set list service

Cause: Injectable Service provider could not find the list service.

Action: Make sure List Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49002: List id is null

Cause: List ID was not specified in request.

Action: Make sure List ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49003: Column id is null

Cause: Column ID was not specified in request.

Action: Make sure Column ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49004: Row id is null

Cause: Row ID was not specified in request.

Action: Make sure Row ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49005: No 'column' in the request body

Cause: Column data was not found in the request body.

Action: Make sure Column data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49006: No 'list' in the request body

Cause: List data was not found in the request body.

Action: Make sure List data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49007: No 'row' in the request body

Cause: Row data was not found in the request body.

Action: Make sure Row data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49008: List could not be found for list id [{0}]

Cause: List ID was not found.

Action: Make sure List ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49009: Column could not be found for column id [{0}]

Cause: Column ID was not found.

Action: Make sure Column ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49010: Row could not be found for row id [{0}]

Cause: Row ID was not found.

Action: Make sure Row ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49011: Unable to create list

Cause: List was not created.

Action: See logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-49012: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: ERROR

Impact: Other

WCS-49013: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49014: Comparator [{0}] is invalid

Cause: Invalid search comparator.

Action: Use valid search comparator.
Level: 1

Type: ERROR

Impact: Other

WCS-49015: MetaColumn [{0}] is a required field, and cannot be set to null

Cause: Missing required field.

Action: Make sure required field is present.
Level: 1

Type: ERROR

Impact: Other

WCS-49016: Invalid ''row'' data in the request body [{0}]

Cause: Invalid row data was found in the request body.

Action: Make sure valid row data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49017: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49018: Portal name not found for GUID [{0}]

Cause: Portal name GUID not found.

Action: Please specify a valid portal name GUID.
Level: 1

Type: ERROR

Impact: Other

WCS-49101: Injectable Service provider did not set forum service

Cause: Injectable Service provider could not find the forum service.

Action: Make sure Forum Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49102: Can't establish Forum Session

Cause: Injectable Service provider could not establish a Forum Session.

Action: Make sure Jive Forum is configured and running and/or you have a valid user session established. Re-authenticating may help.
Level: 1

Type: ERROR

Impact: Other

WCS-49103: Forum id not found [{0}]

Cause: Forum not found.

Action: Please specify a valid forum.
Level: 1

Type: ERROR

Impact: Other

WCS-49104: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49105: All resources require a name.

Cause: Resource name required.

Action: Please specify a resource name in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49106: Topic id not found [{0}]

Cause: Topic not found.

Action: Please specify a valid topic.
Level: 1

Type: ERROR

Impact: Other

WCS-49201: Injectable Service provider did not set Spaces service

Cause: Injectable Service provider could not find Space the service.

Action: Make sure Space Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49202: Portal id is null

Cause: Portal ID was not specified in request.

Action: Make sure Portal ID is specified in request.
Level: 1

Type: ERROR

Impact: Other

WCS-49203: No 'document' in the request body

Cause: Portal document data was not found in the request body.

Action: Make sure Portal document is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49204: Portal name not found [{0}]

Cause: Portal name not found.

Action: Please specify a valid portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49205: Members not found for portal [{0}]

Cause: No Members found.

Action: Please specify a portal with members.
Level: 1

Type: ERROR

Impact: Other

WCS-49206: Member [{0}] not found in portal [{1}]

Cause: Member not found.

Action: Please specify a different member or portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49207: Attributes not found in portal [{0}]

Cause: Attributes not found.

Action: Please specify a different portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49208: Attribute name [{0}] not found in portal [{1}]

Cause: Attribute name not found.

Action: Please specify a different Attribute name or portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49209: Portal params [{0}] and [{1}] result in exception

Cause: General exception.

Action: Please specify a different set of parameters.
Level: 1

Type: ERROR

Impact: Other

WCS-49210: Attempted operation resulted in security exception

Cause: Insufficient authorization.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49211: Retrieving Portal failed due to service unavailability

Cause: Service unaccessible.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49212: Failed to retrieve document repository info for portal.

Cause: Unknown document repository error.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49213: No Portal provided in body.

Cause: Portal was not provided in POST body of request.

Action: Provide Portal in POST body of request.
Level: 1

Type: ERROR

Impact: Other

WCS-49214: Portal template name not specified.

Cause: No portal template name was specified in POST body of request.

Action: Please specify a portal template name.
Level: 1

Type: ERROR

Impact: Other

WCS-49215: Portal name not specified.

Cause: No portal name was specified in POST body of request.

Action: Please specify a portal name.
Level: 1

Type: ERROR

Impact: Other

WCS-49216: Unable to create Portal.

Cause: Internal error creating Portal.

Action: Contact portal administrator and/or see logs for additional errors.
Level: 1

Type: ERROR

Impact: Other

WCS-49217: No Member provided in body.

Cause: Member was not provided in POST body of request.

Action: Provide Member in POST body of request.
Level: 1

Type: ERROR

Impact: Other

WCS-49218: Member name not specified.

Cause: No member name was specified in POST body of request.

Action: Please specify a member name.
Level: 1

Type: ERROR

Impact: Other

WCS-49219: Role name not specified.

Cause: No role name was specified in POST body of request.

Action: Please specify a role name.
Level: 1

Type: ERROR

Impact: Other

WCS-49220: Retrieving Portal Assets failed due to service unavailability

Cause: Service unaccessible.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49251: REST API Injectable Service provider did not set message board service.

Cause: REST API Injectable Service provider did not set message board service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49252: No 'message' in the request body

Cause: Message data was not found in the request body.

Action: Make sure Message data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49253: Message body not specified

Cause: No 'message' in the body when trying to create a new message.

Action: Specify a valid message body that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49254: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49255: Error accessing profile for user with GUID {0}. Ignoring.

Cause: Error retrieving user profile.

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

Type: WARNING

Impact: Other

WCS-49256: Permissions class called with wrong number of resource IDs. Expecting 2 or 3, but got {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49257: Error accessing user or portal message board {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49258: Error accessing message {0} from user or portal message board {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49259: Error retrieving messages {0} to {1} from user or portal message board {2}.

Cause: Error retrieving message from user's message board.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49260: Error trying to delete message {0} from message board for user or portal {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49261: Error trying to create message on message board for user or portal {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49262: Invalid message board type. Got ''{0}'', expected ''person'' or ''space''.

Cause: Invalid message board type in URI.

Action: Verify that the message board type is either 'person' or 'space'.
Level: 1

Type: ERROR

Impact: Other

WCS-49263: Invalid message type. Got ''{0}'', expected ''private'' or ''public''.

Cause: Invalid message type in URI.

Action: Verify that the message type is either 'private' or 'public'.
Level: 1

Type: ERROR

Impact: Other

WCS-49264: Message type ''{0}'' not supported with message board type ''{1}''.

Cause: Invalid message type in URI.

Action: Verify that the message type is empty.
Level: 1

Type: ERROR

Impact: Other

WCS-49265: Message type ''{0}'' not supported for users other than current user.

Cause: Invalid message type in URI.

Action: Verify that the message type is empty.
Level: 1

Type: ERROR

Impact: Other

WCS-49301: REST API Injectable Service provider did not set profile service.

Cause: REST API Injectable Service provider did not set profile service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49302: Cannot delete a member from a list that the current user does not own.

Cause: Cannot delete a member from a list that the current user does not own.

Action: Make sure REST URL specifies the correct list and is accessing list for the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49303: Retrieving list names is only supported for current user. Found GUID {0}.

Cause: Retrieving list names is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49304: Creating lists is only supported for the current user. Found GUID {0}.

Cause: Creating lists is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49305: No 'list' in the request body

Cause: List data was not found in the request body.

Action: Make sure List data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49306: List name not specified

Cause: No 'name' in the body when trying to create a new list.

Action: Specify a valid list name that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49307: Creating connections is only supported for the current user. Found GUID {0}.

Cause: Creating connections is only supported for current user.

Action: Make sure REST URL specifies the current user GUID (or @me).
Level: 1

Type: WARNING

Impact: Other

WCS-49308: No 'member' in the request body

Cause: Member data was not found in the request body.

Action: Make sure member data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49309: Connection GUID not specified

Cause: No 'guid' in the body when trying to create a new connection.

Action: Specify a valid user GUID that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49310: Only connection lists can be deleted, and only by the current user. Found GUID {0} and list ID {1}.

Cause: Only connection lists can be deleted, not the current user or the intrinsic connections list. They can only be deleted by the current user.

Action: Make sure REST URL specifies the connection list ID, not @self or @connections, and is accessing the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49311: Accessing status is only supported for @self id. Found selector {0}.

Cause: Accessing status is only supported for @self id.

Action: Make sure REST URL specifies the @self selector.
Level: 1

Type: WARNING

Impact: Other

WCS-49312: Updating status is only supported for the current user. Found GUID {0}.

Cause: Accessing status is only supported for the current user.

Action: Make sure REST URL is accessing the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49313: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49314: Error checking for people permissions. Wrong number of arguments. Expected 1-3, but found {0} for permission {1}. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49315: Error checking for people permissions. Could not parse type {0}. Expected: person, status, lists, list, member. Ignoring.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49316: Error trying to access connection lists for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49317: Error accessing connection list {0}.

Cause: Error accessing connection list.

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

Type: WARNING

Impact: Other

WCS-49318: Error accessing connection relationship of user {0} to current user {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49319: Error adding/deleting user {0} for list {1} of current user.

Cause: Error adding/deleting user in connection list of current user.

Action: Verify that the list ID is correct and is not @CONNECTIONS (use invitations instead) and the user GUID is correct, and that the user is not already a member of the list when adding user.
Level: 1

Type: WARNING

Impact: Other

WCS-49320: "Error using Resource Action Handler to get link to user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49321: Invalid user search query {0}. Unable to process search. Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].

Cause: Invalid search query was passed into People REST API.

Action: Verify that the search query is of the form [loginid:equals:X] or [guid:equals:Y].
Level: 1

Type: WARNING

Impact: Other

WCS-49322: Error accessing connection list {0} for user {1}.

Cause: Error accessing connection list.

Action: Verify that the list ID and GUID are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49323: Invalid invitation search query {0}. Unable to process search. Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].

Cause: Invalid search query was passed into People Invitations REST API.

Action: Verify that the search query is either [invitor:equals:@me] or [invitee:equals:@me].
Level: 1

Type: WARNING

Impact: Other

WCS-49324: No 'invitation' in the request body

Cause: Invitation data was not found in the request body when trying to create a new invitation.

Action: Make sure Invitation data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49325: Invitation invitee GUID not specified

Cause: No 'invitee' item or 'guid' item in 'invitee' in the body when trying to create a new invitation.

Action: Specify a valid invitee user GUID that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49326: Error retrieving invitations for current user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49327: Error inviting user {0} to be a connection of the current user

Cause: Error inviting user {0} to be a connection of the current user.

Action: Verify the invitee user GUID is correct and is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49328: The invitation ID in the request body ({0}) did not match the ID in the query string ({1})

Cause: The invitation ID in the request body did not match the ID in the query string when trying to update invitation status.

Action: Make sure the invitation ID specified in the request body matches the invitation ID in the query string.
Level: 1

Type: WARNING

Impact: Other

WCS-49329: Error deleting invitation {0}

Cause: Error deleting invitation {0}.

Action: Verify the invitation ID is correct, and that the current user has permissions to delete the invitation (i.e. created or received it).
Level: 1

Type: WARNING

Impact: Other

WCS-49330: Unable to update invitation {0} with status {1}. Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".

Cause: Unable to update invitation status.

Action: Verify that the invitation id is valid, the current user has permission to update the invitation, and that the status is either "accepted" or "ignored".
Level: 1

Type: WARNING

Impact: Other

WCS-49331: Error inviting user {0} to be a connection of current user.

Cause: Error inviting user to be a connection of current user.

Action: Verify that the user GUID is correct, and that the user has not already been invited by the current user.
Level: 1

Type: WARNING

Impact: Other

WCS-49332: Error accessing relationship information for connections and invitations of current user.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49333: Unable to lookup email address {0}.

Cause: Unable to lookup email address.

Action: Make sure the email address is correct, and the identity store is configure properly.
Level: 1

Type: WARNING

Impact: Other

WCS-49334: Error creating connection list {0}. List already exists.

Cause: Error creating connection list. List already exists.

Action: Choose a new name for the new connection list.
Level: 1

Type: WARNING

Impact: Other

WCS-49351: REST API Injectable Service provider did not set activity service.

Cause: REST API Injectable Service provider did not set activity service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49352: No 'activity' in the request body

Cause: Activity data was not found in the request body.

Action: Make sure Activity data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49353: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49354: Creating activities requires the service ID and activity type to be present.

Cause: Creating activities requires the service ID and activity type.

Action: Make sure the activity POST contains the service ID and activity type.
Level: 1

Type: WARNING

Impact: Other

WCS-49355: Error accessing activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49356: Error accessing activities for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49357: Error accessing activities for Portal {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49358: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49359: Unable to retrieve object type for parameter object {0} in activity {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49360: Unable to retrieve object with index {0} for parameter object {1} in activity {2}, because there are only {3} objects available.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49361: Unable to parse key {0}, activity type {1}, service id {2}, activity id {3} for activity parameter. Should be of form ''{actor[n]''} or ''{object[n]''}.

Cause: Unable to parse key for activity parameter.

Action: Make sure key starts with actor or object and the index is numeric.
Level: 1

Type: WARNING

Impact: Other

WCS-49362: Unable to find Portal scope for {0}.

Cause: Unable to find Portal scope from specified value.

Action: Make sure Portal value is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49363: Unable to publish activity for service {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49364: Error accessing comments for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49365: Error creating comment for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49366: Error deleting comment {0}.

Cause: Unable to delete comment.

Action: Make sure current user has permission to delete this comment.
Level: 1

Type: WARNING

Impact: Other

WCS-49367: Error accessing activity object with id {2} with service id {0} and type {1}.

Cause: Unable to access activity object.

Action: Make sure the service id, object type, and object id are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49368: Error accessing activity object details for object with id {2} with service id {0} and type {1}.

Cause: Unable to access activity object details.

Action: Make sure the service id, object type, and object id are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49369: Error accessing comments service.

Cause: Error accessing comments service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49370: REST API Injectable Service provider did not set comment service.

Cause: REST API Injectable Service provider did not set comment service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49371: No 'comment' in the request body

Cause: Comment data was not found in the request body.

Action: Make sure comment data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49372: Creating comments requires the comment text to be present.

Cause: Creating comments requires the comment text.

Action: Make sure the comment POST contains the comment text.
Level: 1

Type: WARNING

Impact: Other

WCS-49373: Invalid data parameter ''{0}'' for activity. Must include ''data'', and may include ''commentsSummary'' and ''likesSummary''.

Cause: Invalid data parameter for activity.

Action: Make sure the data parameter includes 'data'. 'commentsSummary' and 'likesSummary' are optional.
Level: 1

Type: WARNING

Impact: Other

WCS-49374: Error accessing likes for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49375: Error creating like for object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49376: Error deleting like {0}.

Cause: Unable to delete like.

Action: Make sure current user has permission to delete this like.
Level: 1

Type: WARNING

Impact: Other

WCS-49377: Error accessing likes service.

Cause: Error accessing likes service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49378: REST API Injectable Service provider did not set like service.

Cause: REST API Injectable Service provider did not set like service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49379: No 'like' in the request body

Cause: Like data was not found in the request body.

Action: Make sure like data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49380: Activity ID is null

Cause: Activity ID cannot be null.

Action: Use valid activity ID.
Level: 1

Type: WARNING

Impact: Other

WCS-49382: Error accessing comments for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49383: Error creating comment for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49384: Error creating like for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49385: Error accessing likes for activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49386: User has insufficient permission to access object {2} with service id {0} and type {1}.

Cause: Unable to access the object due to permission settings.

Action: Make sure current user has permission to access this object.
Level: 1

Type: WARNING

Impact: Other

WCS-49387: User has insufficient permission to access activity {0}.

Cause: Unable to access the object due to permission settings.

Action: Make sure current user has permission to access this object.
Level: 1

Type: WARNING

Impact: Other

WCS-49388: User has insufficient permission to access object {2} with service id {0} and type {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49389: User has insufficient permission to access activity {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49401: REST API Injectable Service provider did not set feedback service.

Cause: REST API Injectable Service provider did not set feedback service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49402: No 'message' in the request body

Cause: Message data was not found in the request body.

Action: Make sure Message data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49403: Message body not specified

Cause: No 'message' in the body when trying to create a new feedback item.

Action: Specify a valid message body that is not null or blank.
Level: 1

Type: WARNING

Impact: Other

WCS-49404: 'id' should not be supplied with a POST -- use PUT if you want to update

Cause: 'id' should not be supplied with a POST.

Action: Use PUT if you want to update.
Level: 1

Type: WARNING

Impact: Other

WCS-49405: Error retrieving display name from profile for user with GUID {0}. Ignoring.

Cause: Error retrieving user profile.

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

Type: WARNING

Impact: Other

WCS-49406: Permissions class called with wrong number of resource IDs. Expecting 1 or 2, but got {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49407: Error accessing feedback for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49408: Error accessing feedback item from user {1}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49409: Error retrieving received feedback items from {0} to {1} for user {2}.

Cause: Error retrieving received feedback for user.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49410: Error retrieving given feedback items from user {0} for items {1} to {2}.

Cause: Error retrieving feedback for user.

Action: Check startIndex and itemsPerPage.
Level: 1

Type: ERROR

Impact: Other

WCS-49411: Error trying to delete feedback {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49412: Error trying to create feedback for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49413: Unable to find link {0} for feedback item {1}..

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49414: Error trying to get feedback for user. Either unknown GUID {0} or unknown selector {1}.

Cause: Either an unknown GUID was entered, expected @me or GUID or unknown selector was entered, expected @self, @all, or valid GUID. Selector can only be a valid GUID if the {guid} value entered is @me or the GUID of the current logged in user.

Action: Double check the GUID or selector entered is valid.
Level: 1

Type: WARNING

Impact: Other

WCS-49415: No 'receivedUser' in the request body

Cause: The received user data was not found in the request body.

Action: Make sure the received user is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49416: Invalid selector for creating feedback. Expected ''@self'', but found ''{0}''.

Cause: Feedback can only be POSTed to a URI of the form {guid}/@self.

Action: Make sure the URI selector is @self.
Level: 1

Type: WARNING

Impact: Other

WCS-49417: GUID specified in URI and GUID specified in POST body do not match. URI GUID was ''{0}'', POST body received user GUID was ''{1}''.

Cause: GUID in URI and GUID specified in POST body received user GUID must match.

Action: Make sure the URI GUID and POST body received user GUID match.
Level: 1

Type: WARNING

Impact: Other

WCS-49451: Error trying to access profile for user {0}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49452: The current DB version does not support this REST API. Expected version 11.1.1.2.0 or greater.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49453: Unable to use Resource Action Handler to get link to object with type {0} from service {1} and ID {2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49454: The ''{0}'' parameter was not found in the query string, or was empty.

Cause: The query string was missing a required parameter.

Action: Make sure the specified parameter is present in the query string and is not empty.
Level: 1

Type: WARNING

Impact: Other

WCS-49455: The ''{0}'' date time parameter could not be parsed: ''{1}''

Cause: The query string date time parameter was not formatted correctly.

Action: Make sure the specified date time parameter is formatted according to the XSD spec: YYYY-MM-DD with optional time and timezone components Thh:mm:ss, +HH:mm, -HH:mm, or Z. The time component may include milliseconds, but they will not be used.
Level: 1

Type: WARNING

Impact: Other

WCS-49456: Unable to encode data for use in URI.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-49457: Unable to decode data from URI: {0}.

Cause: Unable to decode data from URI.

Action: Make sure the specified data is correctly URL encoded before being passed to the server.
Level: 1

Type: WARNING

Impact: Other

WCS-49458: A query string parameter was set to the default value of ''{0}'', which is a default template parameter, not a valid value.

Cause: A query string parameter was set to a default template parameter value with a starting '{ and ending '}, which is not a valid value.

Action: Make sure the query string parameter is either set to a valid value, or removed.
Level: 1

Type: WARNING

Impact: Other

WCS-49459: Secure Enterprise Search is not configured.

Cause: SES Crawl is not enabled for this instance

Action: Make sure crawl is enabled for Documents, Forums, and Portals sources
Level: 1

Type: WARNING

Impact: Other

WCS-49460: This Secure Enterprise Search version is not supporting facets.

Cause: SES Version is not supporting faceted queries

Action: Make sure to use the SES version that supports faceted serch
Level: 1

Type: WARNING

Impact: Other

WCS-49501: Injectable Service provider did not set search service

Cause: Injectable Service provider could not find the search service.

Action: Make sure Search Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49509: Column could not be found for column id [{0}]

Cause: Column ID was not found.

Action: Make sure Column ID exists.
Level: 1

Type: ERROR

Impact: Other

WCS-49513: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49514: Search parameter must follow [column:[operator:]]value;[column:[operator:]value] syntax

Cause: Search parameter syntax not understood.

Action: Syntax must follow: [column:[operator:]]value;[column:[operator:]value]
Level: 1

Type: ERROR

Impact: Other

WCS-49515: Comparator [{0}] is invalid

Cause: Invalid search comparator.

Action: Use valid search comparator.
Level: 1

Type: ERROR

Impact: Other

WCS-49516: Invalid argument: [{0}]

Cause: Invalid search argument.

Action: Use valid search argument.
Level: 1

Type: ERROR

Impact: Other

WCS-49517: Internal Search Error: [{0}]

Cause: Internal search error.

Action: Please see error on server console.
Level: 1

Type: ERROR

Impact: Other

WCS-49551: REST API Injectable Service provider did not set event service.

Cause: REST API Injectable Service provider did not set event service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49552: Unable to find Portal scope for {0}.

Cause: Unable to find Portal scope from specified value.

Action: Make sure Portal value is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49553: Unable to access calendar for scope {0}.

Cause: Unable to access requested calendar.

Action: Make sure the scope value is a valid Portal GUID.
Level: 1

Type: WARNING

Impact: Other

WCS-49554: Unable to access event {0} in Portal scope {1}.

Cause: Unable to access Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49555: Unable to create event in Portal scope {1}.

Cause: Unable to create Portal event.

Action: Make sure the Portal ID is correct and the current user has permission to create an event in that Portal.
Level: 1

Type: WARNING

Impact: Other

WCS-49556: Unable to update event {0} in Portal scope {1}.

Cause: Unable to update Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49557: Unable to delete event {0} in Portal scope {1}.

Cause: Unable to delete Portal event.

Action: Make sure Portal and event ID values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49558: No 'event' in the request body.

Cause: Event data was not found in the request body.

Action: Make sure Event data is specified in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49559: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.

Cause: Event POST or PUT request bodies cannot contain the ID, author, created date, modifier, modified date, or duration.

Action: Make sure Event data does not contain the ID, author, created date, modifier, modified date, or duration in the request body.
Level: 1

Type: WARNING

Impact: Other

WCS-49560: The event object was missing required data. Events are required to have summary, startTime, and endTime data.

Cause: The event object was missing required data.

Action: Make sure Event summary, startTime, and endTime data are specified in the event object.
Level: 1

Type: WARNING

Impact: Other

WCS-49561: Invalid portal GUID {0}.

Cause: This GUID does not refer to a valid portal.

Action: Make sure the portal GUID is not null or empty, and refers to a valid portal. Home Portal cannot be used for portal events.
Level: 1

Type: WARNING

Impact: Other

WCS-49562: Invalid time sequence: startTime {0} must be before endTime {1}..

Cause: The startTime must be before the endTime.

Action: Make sure the startTime is before the endTime.
Level: 1

Type: WARNING

Impact: Other

WCS-49563: Unable to access event categories for Portal scope {0}.

Cause: Unable to access Portal event categories.

Action: Make sure Portal guid is correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49564: Unable to create event category {0} in Portal scope {1}.

Cause: Unable to create Portal event category.

Action: Make sure the Portal ID is correct and the current user has permission to create an event category in that Portal.
Level: 1

Type: WARNING

Impact: Other

WCS-49565: Unable to delete event category {0} in Portal scope {1}.

Cause: Unable to delete Portal event category.

Action: Make sure Portal and event category name values are correct.
Level: 1

Type: WARNING

Impact: Other

WCS-49601: Injectable Service provider did not set tagging service

Cause: Injectable Service provider could not find the tagging service.

Action: Make sure Tagging Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49613: Required query Parameter "{0}" was not found.

Cause: Query parameter "{0}" ommmited or null.

Action: Query parameter "{0}" required. Please try again with a non-null value for this parameter
Level: 1

Type: ERROR

Impact: Other

WCS-49614: {1} Body must include "{0}" as a field. Could not complete POST Request.

Cause: {1} Body must include "{0}" as a field.

Action: Provide a complete {1} Object as the body for this request
Level: 1

Type: ERROR

Impact: Other

WCS-49615: Tag {0} could not be deleted.

Cause: There was an error while deleting this item

Action: Please check if item exists and if you have the appropriate permissions to delete this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49616: Item with service Id: {0} and resource id: {1} could not be deleted.

Cause: There was an error while deleting this item

Action: Please check if item exists and if you have the appropriate permissions to delete this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49617: Item with service id: {0} and resource id: {1} is already tagged by you

Cause: There was an error while tagging this item

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49618: Item with service id: {0} and resource id: {1} was not found

Cause: There was an error while finding this item

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49619: Tag {0} could not be found.

Cause: There was an error while finding this tag

Action: Please check if item exists and if you have the appropriate permissions to tag this item.
Level: 1

Type: ERROR

Impact: Other

WCS-49620: Required query Parameter "{0}" was not valid.

Cause: Query parameter "{0}" not valid.

Action: Query parameter "{0}" required. Please try again with a valid value for this parameter
Level: 1

Type: ERROR

Impact: Other

WCS-49651: REST API Injectable Service provider did not set links service.

Cause: REST API Injectable Service provider did not set links service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49652: No 'source' in the request body

Cause: Links source object was not found in the request body.

Action: Make sure source object is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49653: No 'target' in the request body

Cause: Links target object was not found in the request body.

Action: Make sure target object is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49654: Error trying to create links.

Cause: Error trying to create links

Action: Make sure webcenter repository is available.
Level: 1

Type: ERROR

Impact: Other

WCS-49655: No 'link' in the request body

Cause: Link data was not found in the request body.

Action: Make sure Link data is specified in the request body.
Level: 1

Type: ERROR

Impact: Other

WCS-49656: Unable to create link

Cause: Link was not created.

Action: See logs for more information.
Level: 1

Type: ERROR

Impact: Other

WCS-49657: Source "serviceid" or "resourceid" not specified

Cause: No source "serviceid" or "resourceid" when trying to create a link.

Action: Specify valid "serviceid" and "resourceid" that are not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-49658: Target "serviceid" or "resourceid" not specified

Cause: No target "serviceid" or "resourceid" when trying to create a link.

Action: Specify valid "serviceid" and "resourceid" that are not null or blank.
Level: 1

Type: ERROR

Impact: Other

WCS-49659: Attempted operation resulted in security exception

Cause: Insufficient authorization.

Action: Contact portal administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-49701: Injectable Service provider did not set recommendation service

Cause: Injectable Service provider could not find the recommendation service.

Action: Make sure the Activity Graph Service injectable provider is available in webapp.
Level: 1

Type: ERROR

Impact: Other

WCS-49702: A database exception occured when connecting to the recommendation service

Cause: A database exception occured when connecting to the recommendation service

Action: Make sure the Activities data source is correctly configured and that the database server is working.
Level: 1

Type: ERROR

Impact: Other

WCS-49703: The Activity Graph engines have not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.

Cause: The Activity Graph engines have not been run yet and there is no data to query.

Action: Please contact your administrator to configure and run the Activity Graph engines.
Level: 1

Type: WARNING

Impact: Other

WCS-49704: An exception occured when connecting to the recommendation service

Cause: An exception occured when connecting to the recommendation service

Action: Make sure the Activity Graph server is correctly configured and is working.
Level: 1

Type: WARNING

Impact: Other

WCS-49705: The item class urn and object urns in the request body ({0}, {1}) did not match the values in the path ({2}, {3})

Cause: The item class urn and object urns in the request body did not match the values in the path when trying to update item status.

Action: Make sure the item class urn and object urn specified in the request body matches the values in the uri path.
Level: 1

Type: WARNING

Impact: Other

WCS-49706: Unable to update item {0}, {1} with status {2}. Verify that the item''s class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".

Cause: Unable to update the item's status.

Action: Verify that the item's class URN and object URN are valid, that the current user has permission to update the item, and that the status is either "interested" or "not interested".
Level: 1

Type: WARNING

Impact: Other

WCS-49707: Unable to update item. Verify that the item's class URN and object URN are valid.

Cause: The item's class URN and object URN must be specified

Action: Verify that the item's class URN and object URN are valid and specified
Level: 1

Type: ERROR

Impact: Other

WCS-49708: Unable to query for common items. Verify that the required parameters are valid and specified.

Cause: One or more mandatory query paramters have not been specified.

Action: Verify that the required parameters are valid and specified.
Level: 1

Type: WARNING

Impact: Other

WCS-49709: Unable to query for recommendations. Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.

Cause: One or more mandatory query paramters have not been specified.

Action: Verify that the required parameters are valid and specified. You need to provide a recipe, an objectURN and either a classURN or serviceId parameters.
Level: 1

Type: WARNING

Impact: Other

WCS-49710: One of the query arguments is invalid. Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.

Cause: One or more query paramters is invalid.

Action: Verify that all arguments are correct, and that recipe and similarity URNs match the specified object types.
Level: 1

Type: WARNING

Impact: Other

WCS-49711: The following recipe is invalid: {0}. Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.

Cause: The recipe is invalid.

Action: Verify that all similarity URNs are correct, that each URN has a positive weight, and that the recipe is formatted like this: item-edit:100;item-tag:10.
Level: 1

Type: WARNING

Impact: Other

WCS-49712: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly. Please contact your administrator to install and configure the Activity Graph service.

Cause: The Activity Graph service is not present in this installation. It has either not been installed or not been configured correctly.

Action: Please contact your administrator to install and configure the Activity Graph service.
Level: 1

Type: WARNING

Impact: Other

WCS-49713: Unable to query for top items. Verify that the required parameters are valid and specified.

Cause: One or more mandatory query paramters have not been specified.

Action: Verify that the required parameters are valid and specified.
Level: 1

Type: WARNING

Impact: Other

WCS-49714: Unable to query for autocompletions because the query string or index URNs are empty or missing. Verify that the required query string and index URN arguments are present and not empty.

Cause: The autocomplete query string or index URNs are missing.

Action: Verify that the autocomplete query string and index URN arguments are present and not empty.
Level: 1

Type: WARNING

Impact: Other

WCS-49715: The Activity Graph autocomplete engine has not been run yet; there is no data to query. Please contact your administrator to configure and run the Activity Graph engines.

Cause: The Activity Graph autocomplete engine has not been run yet and there is no data to query.

Action: Please contact your administrator to configure and run the Activity Graph engines.
Level: 1

Type: WARNING

Impact: Other

WCS-49716: An exception occured when connecting to the autocomplete service

Cause: An exception occured when connecting to the autocomplete service

Action: Make sure the Activity Graph server is correctly configured and is working.
Level: 1

Type: WARNING

Impact: Other

WCS-49751: REST API Injectable Service provider did not set resource catalogs service.

Cause: REST API Injectable Service provider did not set resource catalogs service.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-49752: Catalog ID is not valid: {0}.

Cause: The given catalog ID is not valid to access Resource Catalog REST.

Action: Valid value for Catalog ID is: @BI. Passing any other value is not yet supported.
Level: 1

Type: WARNING

Impact: Other

WCS-49753: Catalog path not found when trying to access: {0}.

Cause: The given path is not valid to access a Resource Catalog.

Action: Verify the given path and make sure to pass a valid path.
Level: 1

Type: WARNING

Impact: Other

WCS-49754: Oracle Business Inteligence (BI) Server is not responding. Connection name: {0}

Cause: The Oracle BI server configured for this connection is not responding.

Action: Please contact your administrator to verify the connection to Oracle BI server.
Level: 1

Type: ERROR

Impact: Other

WCS-50001: An unexpected error occurred in the notification sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50002: Error in Notification Button tag usage - component {0} has attribute {1} whose value is {2}.

Cause: The attribute mentioned in the error cannot be null, but no value was found for this attribute.

Action: Correct your tag usage.
Level: 1

Type: WARNING

Impact: Other

WCS-50003: Component {0} does not support client listeners.

Cause: Tried to add a client listener to a component that does not support client listeners.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-50004: Mandatory parameter {0} not provided in parameters

Cause: The caller did not provide the required parameter to generate notification

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50005: Notification template {0} not found

Cause: The service failed to read the notification template. The template is not available

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50006: Could not create notification contents based on default template {0}

Cause: The service failed to process the default notification template.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50007: Invalid child element {0} found for parent {1}

Cause: The template contains invalid child elements.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50008: End tag {0} not found in CDATA section corresponding to the tag at index {2}

Cause: The CDATA section of the template contains a notification tag without corresponding end tag.

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50009: Value for the token {0} not found in parameters

Cause: The value for the token is not provided in the list of parameter values

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50010: Message key {0} not defined in resource bundle of service {1}

Cause: The message key used in the template does not exist in the service resource bundle

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50011: Error occurred in parsing message {0} in resource bundle of service {1}

Cause: The message has invalid syntax

Action: Contact your system administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50012: An unexpected error occurred in the notification sub-system.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: WARNING

Impact: Other

WCS-50013: Failed to add subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50014: Failed to remove subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50015: Failed to query subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50016: Failed to update subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50017: Failed to save subscription.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WCS-50018: Failed to remove subscription.

Cause: Subscription does not exist

Action: Resubmit the request with correct parameters
Level: 1

Type: ERROR

Impact: Other

WCS-50019: Subscription cannot be added.

Cause: Subscription content is empty

Action: Provide a non empty description
Level: 1

Type: ERROR

Impact: Other

WCS-50020: Error occurred in initializing the notification sender

Cause: Failed initialize notification sender

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50021: Error occurred in sending notification

Cause: Failed to send notification

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50022: Fail to get UMS instance url.

Cause: An unexpected error occurred.

Action: Contact your system administrator.
Level: 1

Type: ERROR

Impact: Other

WCS-50023: Error occurred in saving user preference settings

Cause: Failed to save user preference settings

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50024: The settings document is invalid

Cause: Contents of the settings document are invalid

Action: Verify and correct the settings document
Level: 1

Type: ERROR

Impact: Other

WCS-50025: Fail to get user preference settings for the service {0}

Cause: Fail to get user preference settings for the service

Action: Verify and correct the service
Level: 1

Type: ERROR

Impact: Other

WCS-50026: Service Framework Exception is thrown.

Cause: Service Framework exception thrown.

Action: Check the exception's detail to see the reason why the exception is thrown.
Level: 1

Type: ERROR

Impact: Other

WCS-50027: Notification sender is not configured

Cause: Notification sender is not configured

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50028: Error in parsing notification configuration

Cause: Error in parsing notification configuration

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50029: Error processing activity for notifications

Cause: Error in processing activity for notification

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50030: Failed to initialize context for asynchronous processingError processing

Cause: Failed to initialize context for asynchronous processingError processing

Action: Contact Administrator
Level: 1

Type: ERROR

Impact: Other

WCS-50031: Unexpected error occurred, please retry the unsubscribe operation

Cause: An internal error occurred

Action: Retry the unsubscribe operation. Contact Oracle Support Services if the issue persists.
Level: 1

Type: ERROR

Impact: Other

WCS-50032: Can not find scope for the given name

Cause: The given scope name is invalid

Action: Verify and correct the scope name
Level: 1

Type: ERROR

Impact: Other

WCS-51001: Document {0} cannot be checked out as it is locked by user {1}.

Cause: Another user has checked out the document.

Action: Contact the other user, or wait until they have checked in the document.
Level: 1

Type: ERROR

Impact: Files

WCS-51002: Unspecified Error

Cause: See underlying error.final

Action: See underlying error
Level: 1

Type: ERROR

Impact: Other

WCS-51003: Document {0} does not exist.

Cause: File may have been deleted, or the current user no longer has access to it.

Action: Check if file exists in the space.
Level: 1

Type: ERROR

Impact: Files

WCS-51004: Document {0} cannot be checked in as it is not checked out.

Cause: File is not checked out.

Action: Check out the file before attempting to check it in.
Level: 1

Type: ERROR

Impact: Files

WCS-51005: User {0} does not have the rights to access document {1}.

Cause: User does not have rights to access documents.

Action: Check user rights to document.
Level: 1

Type: ERROR

Impact: Files

WCS-51006: Folder {0} already exists in this parent folder.

Cause: Folder already exists.

Action: type the name of a folder that does not already exist.
Level: 1

Type: ERROR

Impact: Files

WCS-52002: error obtaining content repository connection

Cause: A JNDI naming exception occurred while attempting to obtain the content repository connection.

Action: Verify that connections.xml contains a valid entry for the content repository connection.
Level: 1

Type: WARNING

Impact: Other

WCS-52003: error obtaining blog folder for the page

Cause: The blog folder for the page cannot be found or created.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-52004: After fail-over, failed to get the item {0} from the repository.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-52005: error obtaining blog entry for the page

Cause: The blog entry for the page cannot be found.

Action: Check the server logs for details on this exception.
Level: 1

Type: WARNING

Impact: Other

WCS-60001: Unable to fetch category listing

Cause: Failed to retrieve category list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60002: Unable to fetch category with id {0}

Cause: Failed to retrieve category information from the data store.

Action: Ensure that valid category id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60003: Unable to create category with name {0}

Cause: Failed to create a new category.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60004: Unable to delete category with id {0}

Cause: Failed to delete category.

Action: Ensure that valid category id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60005: Unable to fetch list of top contributors

Cause: Failed to get list of top contributors in the current category.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60006: Unable to edit category with id {0}

Cause: Failed to edit category information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60007: Unable to fetch forum with id {0}

Cause: Failed to retrieve forum information from the data store.

Action: Ensure that valid forum id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60008: Unable to create forum with name {0}

Cause: Failed to create a new forum.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60009: Unable to delete forum with id {0}

Cause: Failed to delete forum.

Action: Ensure that valid forum id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60010: Unable to fetch list of forums for category with id {0}

Cause: Failed to retrieve forum list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60011: Unable to edit forum with id {0}

Cause: Failed to edit forum information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60012: Unable to fetch list of topics for forum with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60013: Unable to fetch topic with id {0}

Cause: Failed to retrieve topic information from the data store.

Action: Ensure that valid topic id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60014: Unable to delete topic with id {0}

Cause: Failed to delete topic.

Action: Ensure that valid topic id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60015: Unable to lock forum with id {0}

Cause: Failed to lock forum to prevent updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60016: Unable to unlock forum with id {0}

Cause: Failed to unlock forum to allow updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60017: Unable to create topic with title "{0}"

Cause: Failed to create a new topic.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60018: Unable to edit topic with id {0}

Cause: Failed to edit topic information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60019: Unable to fetch list of messages for topic with id {0}

Cause: Failed to retrieve message list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60020: Unable to fetch message with id {0}

Cause: Failed to retrieve message information from the data store.

Action: Ensure that valid message id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60021: Unable to delete message with id {0}

Cause: Failed to delete message.

Action: Ensure that valid message id has been supplied and the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60022: Unable to lock topic with id {0}

Cause: Failed to lock topic to prevent updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60023: Unable to unlock topic with id {0}

Cause: Failed to unlock topic to allow updates.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60024: Unable to check if the topic with id {0} is answered or not

Cause: Failed to check the answered status of the topic.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60025: Unable to fetch number of messages in topic with id {0}

Cause: Failed to fetch the message count in the topic.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60026: Unable to create message

Cause: Failed to create a new message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60027: Unable to fetch list of answers for topic with id {0}

Cause: Failed to retrieve answer list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60028: Unable to edit message with id {0}

Cause: Failed to edit message information in the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60029: Unable to fetch list of sub messages for message with id {0}

Cause: Failed to retrieve message list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60030: Unable to like message with id {0}

Cause: Failed to like message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60031: Unable to unlike message with id {0}

Cause: Failed to unlike message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60032: Unable to mark message with id {0} as the answer

Cause: Failed to mark message as the answer.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60033: Unable to unmark message with id {0} as the answer

Cause: Failed to unmark message as the answer.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60034: Unable to check if the message with id {0} is an answer or not

Cause: Failed to check if the message is an answer.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60035: Unable to create a sub message to message with id {0}

Cause: Failed to create a sub message.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60036: Unable to fetch number of topics in forum with id {0}

Cause: Failed to retrieve topic count from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60037: Unable to fetch number of answered topics in forum with id {0}

Cause: Failed to retrieve topic count from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60038: Unable to fetch number of unanswered topics in forum with id {0}

Cause: Failed to retrieve topic count from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60039: Unable to fetch list of recent topics for category with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60040: Unable to instantiate forum factory class {0}

Cause: Failed to reinstantiate factory class.

Action: Ensure that the correct factory class name has been supplied.
Level: 1

Type: WARNING

Impact: Other

WCS-60041: Unable to perform operation, since forum/topic is locked

Cause: Unable to perform operation.

Action: Ensure the forum/topic is not locked.
Level: 1

Type: WARNING

Impact: Other

WCS-60042: Unable to fetch list of recent topics for forum with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60043: Unable to fetch list of popular topics for forum with id {0}

Cause: Failed to retrieve topic list from the data store.

Action: Ensure that the backend server is up and running.
Level: 1

Type: WARNING

Impact: Other

WCS-60044: Unable to fetch OSN connection details

Cause: Failed to retrieve OSN Connection.

Action: Ensure that the OSN Connection is created via WLST/EM.
Level: 1

Type: WARNING

Impact: Other

WCS-63001: An unexpected error occurred.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63002: An object of type {0} with this id ({1}) already exits.

Cause: An attempt was made to create an object with an id that is already in use.

Action: Specify a unique id.
Level: 1

Type: ERROR

Impact: Other

WCS-63003: The name ({0}) is not valid.

Cause: The specified name is not valid.

Action: Specify a valid name.
Level: 1

Type: ERROR

Impact: Other

WCS-63004: Object has been changed by another user.

Cause: The object has been changed by another user.

Action: Reload the object and try the operation again.
Level: 1

Type: ERROR

Impact: Other

WCS-63005: An Object of type {0} with id={1} could not be found.

Cause: The specified object could not be found. This may be due to the object being deleted by another user.

Action: Specify a valid id.
Level: 1

Type: ERROR

Impact: Other

WCS-63006: Object ({0}) is immutable.

Cause: An attempt to change this object was made, but this object is currently immutable.

Action: Retrieve mutable object to make changes.
Level: 1

Type: ERROR

Impact: Other

WCS-63007: {0} is not a valid reference name to MDS.

Cause: The name is not a valid MDS reference name.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63008: The MDS session does not support updates.

Cause: MDS was not configured correctly to support updates.

Action: Configure the MDS store to support updates.
Level: 1

Type: ERROR

Impact: Other

WCS-63009: An IO error occurred when accessing metadata.

Cause: An IO error occurred in MDS.

Action: See the log for more details on the specific IO error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-63010: The object is not valid.

Cause: The metadata for the object does not pass validation.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63011: Failed to construct attribute set for list [{0}].

Cause: Failed to construct attribute set for list.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63012: Failed to add data flavor to ListTransferable. List=[{0}] DataFlavor=[{1}]

Cause: Failed to add data flavor to ListTransferable.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-63013: The query attribute predicate {0}{1}{2} was ignored because the column does not exist or the comparator is not supported.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-63014: An error occurred when deleting metadata.

Cause: An error occurred in MDS while deleting metadata.

Action: See the log for more details on the specific error to correct the problem.
Level: 1

Type: ERROR

Impact: Other

WCS-63015: A column with the name ({0}) already exists.

Cause: A column was created or renamed with the name of an existing column in the list.

Action: Specify a unique column name within the list.
Level: 1

Type: ERROR

Impact: Other

WCS-63016: A list with the name ({0}) already exists.

Cause: A list was created or renamed with the name of an existing list.

Action: Specify a unique list name.
Level: 1

Type: ERROR

Impact: Other

WCS-63017: The maximum number of columns for this list has been exceeded.

Cause: A list was created or modified with more than 30 columns.

Action: Do not add more than 30 columns to a list.
Level: 1

Type: ERROR

Impact: Other

WCS-63019: The Lists service is not provisioned for scope {0}.

Cause: The Lists service is not provisioned for the specified scope.

Action: Provision the Lists service for the specified scope.
Level: 1

Type: ERROR

Impact: Other

WCS-63020: The value is the wrong data type. The data type expected is {0}.

Cause: The value is the wrong data type.

Action: Use the value with the correct data type.
Level: 1

Type: ERROR

Impact: Other

WCS-63021: The WebCenter repository is not available.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-63022: An error occurred accessing the WebCenter metadata repository.

Cause: An error occurred accessing the repository.

Action: Contact your system administrator. Check the log for more details.
Level: 1

Type: ERROR

Impact: Other

WCS-63023: List column values were converted or deleted based on list column changes during import: scope={0}, list={1}, column={2}.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Other

WCS-64001: JAXRS framework encryption service threw exception with message {0}.

Cause: JAXRS framework encryption service not initialized correctly.

Action: Ensure JAXRS framework encryption service is initialized.
Level: 1

Type: ERROR

Impact: Other

WCS-64002: JAXRS framework encryption service set up required. Key generator algorithm not set up in credential store framework.

Cause: Key generator algorithm not set up in credential store framework.

Action: Set up key generator algorithm in credential store framework.
Level: 1

Type: WARNING

Impact: Other

WCS-64003: JAXRS framework encryption service set up required. Cipher transformation not set up in credential store framework.

Cause: Cipher transformation not set up in credential store framework.

Action: Set up cipher transformation in credential store framework.
Level: 1

Type: WARNING

Impact: Other

WCS-70001: Invalid value "{1}" supplied for argument "{0}"

Cause: Argument value is empty or invalid.

Action: Please provide appropriate value to the argument.
Level: 1

Type: WARNING

Impact: Other

WCS-70002: Resource of type "{0}" with id {1} not found

Cause: The resource with supplied id could not be found.

Action: Please provide valid resource id.
Level: 1

Type: WARNING

Impact: Other

WCS-70003: Operation {0} is not supported by the resource of type "{0}" with id {1}

Cause: The operation is not supported by the resource.

Action: Please ensure that the operation invoked on the resource is supported by the backend.
Level: 1

Type: WARNING

Impact: Other

WCS-80001: The blog is locked. You cannot create new entries

Cause: The blog has been locked.

Action: Unlock the block to enable creating new entries.
Level: 1

Type: WARNING

Impact: Other

WCS-89001: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89002: WSRP Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89003: Web Service Connection Name {0} already exists. WSRP connection {1} cannot be created.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89004: Cannot register the producer due to connectivity issues.

Cause: Failed to connect to the producer. Either the connection details specified were invalid or there was a network problem.

Action: Verify that the producer connection details are correct, and then check to see if a firewall or some other network issue is blocking the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89005: Unable to register the producer due to an invalid WSDL URL.

Cause: The WSDL URL specified for the WSRP producer was invalid.

Action: Specify a valid WSDL URL, and then try again.
Level: 1

Type: ERROR

Impact: Other

WCS-89006: URL Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for the connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89007: Web Producer Name {0} already exists.

Cause: Web Producer Name used already exists.

Action: Use a different name for the Web producer.
Level: 1

Type: ERROR

Impact: Other

WCS-89008: Unable to register the producer due to exception {0}. Contact your administrator.

Cause: Error occurred registering the producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89009: Unable to unregister the producer due to exception {0}. Contact your administrator.

Cause: Error occurred deregistering the producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89010: Unable to get producer connections due to exception {0}. Contact your administrator.

Cause: Error occurred retrieving the list of producers.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89011: Unable to register the WSRP producer due to exception {0}. Contact your administrator.

Cause: Error occurred registering the WSRP producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89012: Unable to register the JPDK producer due to exception {0}. Contact your administrator.

Cause: Encountered an exception when registering the JPDK producer.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89013: Unable to create the WSRP producer connection due to exception {0}. Contact your administrator.

Cause: Error occurred creating the WSRP producer connection.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89014: Unable to refresh the producer connections due to exception {0}

Cause: Error occurred refreshing the list of producers.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89015: Failed to clean up producer registration due to exception {0}. Contact your administrator.

Cause: Error occurred cleaning up the producer registration.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89016: The operation failed due to an exception. Contact your administrator.

Cause: Error occurred performing the operation.

Action: Examine the log files for more detail.
Level: 1

Type: ERROR

Impact: Other

WCS-89501: An unexpected error occurred in the activity stream sub-system.

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

WCS-89502: External Application Connection Name {0} already exists.

Cause: Connection Name used already exists.

Action: Use a different name for Connection.
Level: 1

Type: ERROR

Impact: Other

WCS-89503: No connection selected for this operation.

Cause: No External Application connection selected for this operation.

Action: Select a External Application connection from the table listing the available connections.
Level: 1

Type: ERROR

Impact: Other

WCS-90100: No moveplan.xml file available.

Cause: moveplan.xml file missing.

Action: Contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WCS-90200: Error in validating the source environment.

Cause: Invalid source environment.

Action: Contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

52 WSM-00001 to WSM-09024

WSM-00001: A JAXB context for path "{0}" cannot be created due to underlying error "{1}".

Cause: The error could have been caused by creating the JAXB2.0 marshaller/unmarshaller.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00001: A JAXB context for path "{0}" cannot be created due to underlying error "{1}".

Cause: The error could have been caused by creating the JAXB2.0 marshaller/unmarshaller.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00002: A class of type {0} cannot be marshaled due to underlying error "{1}".

Cause: Error occurred in JAXB marshalling (1.e converting java object to xml.)

Action: Contact Oracle Support Services or refer to http://java.net/jaxb.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00002: A class of type {0} cannot be marshaled due to underlying error "{1}".

Cause: Error occurred in JAXB marshalling (1.e converting java object to xml.)

Action: Contact Oracle Support Services or refer to http://java.net/jaxb.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00003: An element of type {0} cannot be unmarshaled due to underlying error "{1}".

Cause: Error occurred while doing JAXB unmarshall i.e converting XML to Java.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00003: An element of type {0} cannot be unmarshaled due to underlying error "{1}".

Cause: Error occurred while doing JAXB unmarshall i.e converting XML to Java.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00004: WS-Security Exception : {0}

Cause: The system encountered a generic failure in security.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00004: WS-Security Exception : {0}

Cause: The system encountered a generic failure in security.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00005: Error in sending the request.

Cause: Failure occurred while trying to send the request message, possibly due to a failure in security code.

Action: Retry the operation for a maximum of 3 times. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00005: Error in sending the request.

Cause: Failure occurred while trying to send the request message, possibly due to a failure in security code.

Action: Retry the operation for a maximum of 3 times. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00006: Error in receiving the request: {0}.

Cause: Failure occurred while processing the request message, possibly due to a failure in security checks.

Action: Refer to the policy for the expected nature of the request message and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00006: Error in receiving the request: {0}.

Cause: Failure occurred while processing the request message, possibly due to a failure in security checks.

Action: Refer to the policy for the expected nature of the request message and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00007: JPS exception

Cause: The error was most likely due to an invalid JPS configuration.

Action: Correct the JPS configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00007: JPS exception

Cause: The error was most likely due to an invalid JPS configuration.

Action: Correct the JPS configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00008: Web service authentication failed.

Cause: Authentication failed at the server end.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00008: Web service authentication failed.

Cause: Authentication failed at the server end.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00009: The password policy does not match. Expected: {0}, Received:{1}.

Cause: The expected and actual password types did not match.

Action: Refer to the policy to determine the allowed password type value.
Level: 1

Type: ERROR

Impact: Security

WSM-00009: The password policy does not match. Expected: {0}, Received:{1}.

Cause: The expected and actual password types did not match.

Action: Refer to the policy to determine the allowed password type value.
Level: 1

Type: ERROR

Impact: Security

WSM-00010: Message rejected as the nonce element in the WS-Security header is missing.

Cause: Nonce was required according to policy requirements, but was not found.

Action: Resend the request with valid value of nonce.
Level: 1

Type: ERROR

Impact: Security

WSM-00010: Message rejected as the nonce element in the WS-Security header is missing.

Cause: Nonce was required according to policy requirements, but was not found.

Action: Resend the request with valid value of nonce.
Level: 1

Type: ERROR

Impact: Security

WSM-00011: The wsu:Created element is required.

Cause: The Created element was required, but was not found.

Action: Resend the request with valid value of the Created element with the UTC timestamp of the instance in which the request was created.
Level: 1

Type: ERROR

Impact: Security

WSM-00011: The wsu:Created element is required.

Cause: The Created element was required, but was not found.

Action: Resend the request with valid value of the Created element with the UTC timestamp of the instance in which the request was created.
Level: 1

Type: ERROR

Impact: Security

WSM-00012: The password is ignored, as it is not required by the policy.

Cause: The password was sent in the <UsernameToken>, when it was not required.

Action: The password type prescribed by the policy is None, so password should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00012: The password is ignored, as it is not required by the policy.

Cause: The password was sent in the <UsernameToken>, when it was not required.

Action: The password type prescribed by the policy is None, so password should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00013: The nonce is ignored, as it is not required by the policy.

Cause: The nonce was sent in the <UsernameToken>, when it was not required.

Action: Because the policy does not require the nonce, it should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00013: The nonce is ignored, as it is not required by the policy.

Cause: The nonce was sent in the <UsernameToken>, when it was not required.

Action: Because the policy does not require the nonce, it should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00014: The creation timestamp is ignored, as it is not required by the policy.

Cause: The creation timestamp was sent in the <UsernameToken>, when it was not required.

Action: Because the policy does not require the creation timestamp inside <UsernameToken>, it should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00014: The creation timestamp is ignored, as it is not required by the policy.

Cause: The creation timestamp was sent in the <UsernameToken>, when it was not required.

Action: Because the policy does not require the creation timestamp inside <UsernameToken>, it should not be sent.
Level: 1

Type: WARNING

Impact: Security

WSM-00015: The user name is missing.

Cause: Username was expected but was not found.

Action: Either the username element or the username inside the username element is missing. Resend the request with a valid username.
Level: 1

Type: ERROR

Impact: Security

WSM-00015: The user name is missing.

Cause: Username was expected but was not found.

Action: Either the username element or the username inside the username element is missing. Resend the request with a valid username.
Level: 1

Type: ERROR

Impact: Security

WSM-00016: The username/password credentials or certificates {0} are missing.

Cause: It is possible that username/password or certificate is missing.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00016: The username/password credentials or certificates {0} are missing.

Cause: It is possible that username/password or certificate is missing.

Action: Resend valid credentials.
Level: 1

Type: ERROR

Impact: Security

WSM-00017: The <bindings> element for {0}:{1} is missing.

Cause: It is likely that the bindings element is missing inside policy.

Action: Re-create the policy with valid bindings.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00017: The <bindings> element for {0}:{1} is missing.

Cause: It is likely that the bindings element is missing inside policy.

Action: Re-create the policy with valid bindings.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00018: There is more than one security header with the same role {0}.

Cause: More than one security header was found with the same role associated.

Action: Refer to the WS-Security 1.0 or 1.1 specifications. Do not send more than one security header having the same role.
Level: 1

Type: ERROR

Impact: Security

WSM-00018: There is more than one security header with the same role {0}.

Cause: More than one security header was found with the same role associated.

Action: Refer to the WS-Security 1.0 or 1.1 specifications. Do not send more than one security header having the same role.
Level: 1

Type: ERROR

Impact: Security

WSM-00019: The version of SOAP used is not supported: {0}.

Cause: An envelope was obtained that conforms to an unsupported version of SOAP.

Action: Use a supported version. SOAP 1.1 and 1.2 are supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00019: The version of SOAP used is not supported: {0}.

Cause: An envelope was obtained that conforms to an unsupported version of SOAP.

Action: Use a supported version. SOAP 1.1 and 1.2 are supported.
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00020: Error sending the response.

Cause: A failure occurred while building the response.

Action: Retry a maximum of three times. If the retry attempts fail, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00020: Error sending the response.

Cause: A failure occurred while building the response.

Action: Retry a maximum of three times. If the retry attempts fail, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00021: Error receiving the response.

Cause: A failure occurred while processing the response, most likely due to a failure in the security check.

Action: Retry sending the response to the client.
Level: 1

Type: ERROR

Impact: Security

WSM-00021: Error receiving the response.

Cause: A failure occurred while processing the response, most likely due to a failure in the security check.

Action: Retry sending the response to the client.
Level: 1

Type: ERROR

Impact: Security

WSM-00022: Error sending a fault.

Cause: A failure occurred while sending the fault.

Action: Retry for a maximum of three times. If the retry attempts fail, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00022: Error sending a fault.

Cause: A failure occurred while sending the fault.

Action: Retry for a maximum of three times. If the retry attempts fail, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00023: Error receiving a fault.

Cause: A failure occurred while processing the fault, most likely due to a failure in the security check.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00023: Error receiving a fault.

Cause: A failure occurred while processing the fault, most likely due to a failure in the security check.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00024: The SAML token is missing from the security header. Ensure that there is a SAML token policy attached on the client side. Tokens found in the security header are :- {0}.

Cause: The SAML assertion that was expected inside the security header was not found.

Action: Insert valid SAML assertions and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00024: The SAML token is missing from the security header. Ensure that there is a SAML token policy attached on the client side. Tokens found in the security header are :- {0}.

Cause: The SAML assertion that was expected inside the security header was not found.

Action: Insert valid SAML assertions and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00025: SAML token verification failure.

Cause: SAML token verification failed.

Action: Check the validity period of the SAML assertion using Conditions, or determine whether the assertion must be signed. Ensure that the SAML token conforms to the requirements of the SAML 1.0 specification.
Level: 1

Type: ERROR

Impact: Security

WSM-00025: SAML token verification failure.

Cause: SAML token verification failed.

Action: Check the validity period of the SAML assertion using Conditions, or determine whether the assertion must be signed. Ensure that the SAML token conforms to the requirements of the SAML 1.0 specification.
Level: 1

Type: ERROR

Impact: Security

WSM-00026: The SAML token cannot be added to the security header.

Cause: A failure occurred while adding the SAML token to the security header.

Action: Check the log file for a possible cause.
Level: 1

Type: ERROR

Impact: Other

WSM-00026: The SAML token cannot be added to the security header.

Cause: A failure occurred while adding the SAML token to the security header.

Action: Check the log file for a possible cause.
Level: 1

Type: ERROR

Impact: Other

WSM-00027: The configuration parameter {0} contains an invalid value [{1}].

Cause: The configuration settings were invalid.

Action: Check the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00027: The configuration parameter {0} contains an invalid value [{1}].

Cause: The configuration settings were invalid.

Action: Check the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00028: Failure in getting user credentials from client.

Cause: Failure occurred while extracting user credentials from the client side.

Action: Check Keystore/Username and the Password/CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00028: Failure in getting user credentials from client.

Cause: Failure occurred while extracting user credentials from the client side.

Action: Check Keystore/Username and the Password/CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00029: The algorithms used to encrypt the data do not match those specified in the policy. : Expected : {0}, Actual : {1}.

Cause: The expected and actual data encryption algorithms did not match.

Action: Check the policy to determine the permitted values for the data encryption algorithm.
Level: 1

Type: ERROR

Impact: Security

WSM-00029: The algorithms used to encrypt the data do not match those specified in the policy. : Expected : {0}, Actual : {1}.

Cause: The expected and actual data encryption algorithms did not match.

Action: Check the policy to determine the permitted values for the data encryption algorithm.
Level: 1

Type: ERROR

Impact: Security

WSM-00030: The encryption method key wrap algorithms do not match : Expected : {0}, Actual : {1}.

Cause: The expected and actual key wrap encryption algorithms did not match.

Action: Check the policy to determine the permitted values for the key wrap encryption algorithm. In addition, refer to WS-Security Policy 1.1 for a list of allowed values.
Level: 1

Type: ERROR

Impact: Security

WSM-00030: The encryption method key wrap algorithms do not match : Expected : {0}, Actual : {1}.

Cause: The expected and actual key wrap encryption algorithms did not match.

Action: Check the policy to determine the permitted values for the key wrap encryption algorithm. In addition, refer to WS-Security Policy 1.1 for a list of allowed values.
Level: 1

Type: ERROR

Impact: Security

WSM-00031: The digest algorithms do not match.

Cause: The actual digest algorithms for the signature did not match the expected algorithms.

Action: Check the policy to determine the permitted values for the signature digest algorithms.
Level: 1

Type: ERROR

Impact: Security

WSM-00031: The digest algorithms do not match.

Cause: The actual digest algorithms for the signature did not match the expected algorithms.

Action: Check the policy to determine the permitted values for the signature digest algorithms.
Level: 1

Type: ERROR

Impact: Security

WSM-00033: The encrypted message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be encrypted:- {0}

Cause: Parts or elements to be encrypted according to policy were different from those in the SOAP message.

Action: Refer to the policy and WS-Security specifications to ensure that all encryption requirements mandated by the policy and the specifications are met.
Level: 1

Type: ERROR

Impact: Security

WSM-00033: The encrypted message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be encrypted:- {0}

Cause: Parts or elements to be encrypted according to policy were different from those in the SOAP message.

Action: Refer to the policy and WS-Security specifications to ensure that all encryption requirements mandated by the policy and the specifications are met.
Level: 1

Type: ERROR

Impact: Security

WSM-00034: Error in Encryption reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.

Cause: The expected and actual encryption reference mechanisms did not match.

Action: Check the policy to determine the permitted values for the encryption reference mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00034: Error in Encryption reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.

Cause: The expected and actual encryption reference mechanisms did not match.

Action: Check the policy to determine the permitted values for the encryption reference mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00035: Error in Signature reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.

Cause: The expected and actual signature reference mechanisms did not match.

Action: Check the policy to determine the allowed value of the signature reference mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00035: Error in Signature reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.

Cause: The expected and actual signature reference mechanisms did not match.

Action: Check the policy to determine the allowed value of the signature reference mechanism.
Level: 1

Type: ERROR

Impact: Security

WSM-00036: The signed message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be signed:- {0}

Cause: Parts or elements to be signed according to policy were different from those in the soap message.

Action: Refer to the policy and WS-Security specifications to make sure that all the signature requirements mandated by the policy and the specifications are met.
Level: 1

Type: ERROR

Impact: Security

WSM-00036: The signed message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be signed:- {0}

Cause: Parts or elements to be signed according to policy were different from those in the soap message.

Action: Refer to the policy and WS-Security specifications to make sure that all the signature requirements mandated by the policy and the specifications are met.
Level: 1

Type: ERROR

Impact: Security

WSM-00037: Error in signature confirmation compliance.

Cause: The error could have occurred because the response signature confirmation element was not signed.

Action: Check that all the signature confirmations in the response are signed and referenced in the response signature.
Level: 1

Type: ERROR

Impact: Security

WSM-00037: Error in signature confirmation compliance.

Cause: The error could have occurred because the response signature confirmation element was not signed.

Action: Check that all the signature confirmations in the response are signed and referenced in the response signature.
Level: 1

Type: ERROR

Impact: Security

WSM-00039: Timestamp element is not found in the message in accordance with policy.

Cause: Timestamp policy compliance failed.

Action: Check the policy to find out whether a timestamp is required. If the policy indicates that the timestamp is not required, it should not be present; if timestamp is required, it should be present.
Level: 1

Type: ERROR

Impact: Security

WSM-00039: Timestamp element is not found in the message in accordance with policy.

Cause: Timestamp policy compliance failed.

Action: Check the policy to find out whether a timestamp is required. If the policy indicates that the timestamp is not required, it should not be present; if timestamp is required, it should be present.
Level: 1

Type: ERROR

Impact: Security

WSM-00042: The request must be made over SSL.

Cause: The request was expected to be sent over SSL, but it was not.

Action: Check the SSL port and send the request over SSL.
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00042: The request must be made over SSL.

Cause: The request was expected to be sent over SSL, but it was not.

Action: Check the SSL port and send the request over SSL.
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00043: No peer certificates are present from the HTTP request.

Cause: A certificate in the trust chain is missing.

Action: Ensure that the complete certificate chain is propagated in the request, if certificates signed by CA are used.
Level: 1

Type: ERROR

Impact: Security

WSM-00043: No peer certificates are present from the HTTP request.

Cause: A certificate in the trust chain is missing.

Action: Ensure that the complete certificate chain is propagated in the request, if certificates signed by CA are used.
Level: 1

Type: ERROR

Impact: Security

WSM-00044: The HTTP authorization header is missing.

Cause: The authorization Header was not found.

Action: For basic over HTTP authentication, ensure that the request HTTP headers contain an authorization header.
Level: 1

Type: ERROR

Impact: Security

WSM-00044: The HTTP authorization header is missing.

Cause: The authorization Header was not found.

Action: For basic over HTTP authentication, ensure that the request HTTP headers contain an authorization header.
Level: 1

Type: ERROR

Impact: Security

WSM-00045: HTTP authentication/authorization failure.

Cause: Failure occurred in basic authentication.

Action: Use the appropriate Base64 encoded combination of a valid username and password.
Level: 1

Type: ERROR

Impact: Security

WSM-00045: HTTP authentication/authorization failure.

Cause: Failure occurred in basic authentication.

Action: Use the appropriate Base64 encoded combination of a valid username and password.
Level: 1

Type: ERROR

Impact: Security

WSM-00046: Error in advertisement of WS-Policy.

Cause: An error occurred while advertising ORAWSDL to WS-Policy.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00046: Error in advertisement of WS-Policy.

Cause: An error occurred while advertising ORAWSDL to WS-Policy.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00047: Invalid key referencing mechanism: {0}.

Cause: The sign or encryption key reference mechanism used was invalid.

Action: Valid supported values are direct, issuerserial, SKI, or thumbprint.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00047: Invalid key referencing mechanism: {0}.

Cause: The sign or encryption key reference mechanism used was invalid.

Action: Valid supported values are direct, issuerserial, SKI, or thumbprint.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00048: The signature confirmation value is invalid. Expected : {0}, Actual : {1}.

Cause: Signature confirmation sent in the response was invalid.

Action: See the WS-Security 1.1 specification for the correct @Value of SignatureConfirmation.
Level: 1

Type: ERROR

Impact: Security

WSM-00048: The signature confirmation value is invalid. Expected : {0}, Actual : {1}.

Cause: Signature confirmation sent in the response was invalid.

Action: See the WS-Security 1.1 specification for the correct @Value of SignatureConfirmation.
Level: 1

Type: ERROR

Impact: Security

WSM-00049: The expected {0} signature is missing in the request messsage.

Cause: No signature (message, or endorsing) was found in the request to confirm.

Action: Resend the request with at least one <Signature>.
Level: 1

Type: WARNING

Impact: Security

WSM-00049: The expected {0} signature is missing in the request messsage.

Cause: No signature (message, or endorsing) was found in the request to confirm.

Action: Resend the request with at least one <Signature>.
Level: 1

Type: WARNING

Impact: Security

WSM-00050: Cannot obtain security token reference.

Cause: The message was not signed or encrypted properly.

Action: Check the <ds:Reference> section of the message.
Level: 1

Type: ERROR

Impact: Other

WSM-00050: Cannot obtain security token reference.

Cause: The message was not signed or encrypted properly.

Action: Check the <ds:Reference> section of the message.
Level: 1

Type: ERROR

Impact: Other

WSM-00051: The encrypted data or key cannot be obtained.

Cause: The referenced encrypted object could not be found.

Action: Ensure that the reference points to valid <EncryptedData> element.
Level: 1

Type: ERROR

Impact: Other

Cause: The referenced encrypted object could not be found.

Action: Ensure that the reference points to valid <EncryptedKey> element.

WSM-00051: The encrypted data or key cannot be obtained.

Cause: The referenced encrypted object could not be found.

Action: Ensure that the reference points to valid <EncryptedData> element.
Level: 1

Type: ERROR

Impact: Other

Cause: The referenced encrypted object could not be found.

Action: Ensure that the reference points to valid <EncryptedKey> element.

WSM-00052: There is an invalid or nonexistent configuration for the Login Module class [{1}] in the Java Platform Security (JPS) context [{0}].

Cause: An invalid or nonexistent configuration for Login Module could have been used.

Action: Change the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00052: There is an invalid or nonexistent configuration for the Login Module class [{1}] in the Java Platform Security (JPS) context [{0}].

Cause: An invalid or nonexistent configuration for Login Module could have been used.

Action: Change the configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00053: The propagated subject is either null or empty.

Cause: No Subject was found.

Action: Send a valid nonempty Subject.
Level: 1

Type: ERROR

Impact: Security

WSM-00053: The propagated subject is either null or empty.

Cause: No Subject was found.

Action: Send a valid nonempty Subject.
Level: 1

Type: ERROR

Impact: Security

WSM-00054: The password credentials cannot be obtained from the Credential Store Framework (CSF). Unable to retrive the csfKey "{0}". The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2}

Cause: Failure occurred while doing query for credentials from Credential Store Framework (CSF).

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00054: The password credentials cannot be obtained from the Credential Store Framework (CSF). Unable to retrive the csfKey "{0}". The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2}

Cause: Failure occurred while doing query for credentials from Credential Store Framework (CSF).

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00055: The keystore located at {0} cannot be loaded due to {1}. Ensure that valid keystore type and password are configured.

Cause: The following keystore-related configuration properties may not be valid:keystore.type, keystore.pass. Also, the keystore could be corrupt or could have been tampered with.

Action: Verify the configuration properties mentioned above and retry the operation. In a rare situation, replace or regenerate the keystore.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00055: The keystore located at {0} cannot be loaded due to {1}. Ensure that valid keystore type and password are configured.

Cause: The following keystore-related configuration properties may not be valid:keystore.type, keystore.pass. Also, the keystore could be corrupt or could have been tampered with.

Action: Verify the configuration properties mentioned above and retry the operation. In a rare situation, replace or regenerate the keystore.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00056: The key, {0}, is not retrieved.{4}Ensure that the correct key password is set in the credential store for the above key. The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}

Cause: Error occurred while obtaining key from store.

Action: Make sure the key exists in the keystore. Check JPS configuration settings for correct key alias, key password and keystore password. Also, check the values of the key keystore-csf-key and its password in the oracle.wsm.security map, through EM or WLST. In a rare situation, this error can also happen if the actual keystore type is ORACLE_WALLET and the keystore type specified in JPS configuration file is PKCS12.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00056: The key, {0}, is not retrieved.{4}Ensure that the correct key password is set in the credential store for the above key. The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}

Cause: Error occurred while obtaining key from store.

Action: Make sure the key exists in the keystore. Check JPS configuration settings for correct key alias, key password and keystore password. Also, check the values of the key keystore-csf-key and its password in the oracle.wsm.security map, through EM or WLST. In a rare situation, this error can also happen if the actual keystore type is ORACLE_WALLET and the keystore type specified in JPS configuration file is PKCS12.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00057: The certificate, {0}, is not retrieved.{4}The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}

Cause: Failure occurred while retrieving certificate from store.

Action: Verify keystore location configuration property as well as make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00057: The certificate, {0}, is not retrieved.{4}The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}

Cause: Failure occurred while retrieving certificate from store.

Action: Verify keystore location configuration property as well as make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00058: The key type {0} is not supported.

Cause: The private key algorithm that was used is unsupported.

Action: Ensure that the private key follows the RSA algorithm.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00058: The key type {0} is not supported.

Cause: The private key algorithm that was used is unsupported.

Action: Ensure that the private key follows the RSA algorithm.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00059: Signature method algorithms are mismatched. Expected : {0}, Actual : {1}.

Cause: Expected and actual values of signature method algorithms did not match.

Action: Check the policy and WS-Security Policy 1.1 specification for valid values.
Level: 1

Type: ERROR

Impact: Security

WSM-00059: Signature method algorithms are mismatched. Expected : {0}, Actual : {1}.

Cause: Expected and actual values of signature method algorithms did not match.

Action: Check the policy and WS-Security Policy 1.1 specification for valid values.
Level: 1

Type: ERROR

Impact: Security

WSM-00060: Error validating timestamp.

Cause: Timestamp is expired.

Action: Check the timestamp. Check the allowed clockskew and message expiration time.
Level: 1

Type: ERROR

Impact: Security

WSM-00060: Error validating timestamp.

Cause: Timestamp is expired.

Action: Check the timestamp. Check the allowed clockskew and message expiration time.
Level: 1

Type: ERROR

Impact: Security

WSM-00061: Signature digest verification failure. The system property xml.debug.verify should be enabled for the details about the digest calculations during verification phase (note xml.debug.verify slows down the signature verification for very large messages). Caused by:-{0}

Cause: Digest verification failed possibly due to corrupted digest, or a message that was tampered with.

Action: Recompute the digest and send the message again.
Level: 1

Type: ERROR

Impact: Security

WSM-00061: Signature digest verification failure. The system property xml.debug.verify should be enabled for the details about the digest calculations during verification phase (note xml.debug.verify slows down the signature verification for very large messages). Caused by:-{0}

Cause: Digest verification failed possibly due to corrupted digest, or a message that was tampered with.

Action: Recompute the digest and send the message again.
Level: 1

Type: ERROR

Impact: Security

WSM-00062: The path to the certificate used for the signature is invalid.

Cause: The intermediate and root certificates of the signing certificate were not present in the keystore at the verifying end.

Action: Make sure that the entire certificate chain is available in the keystore for verification.
Level: 1

Type: ERROR

Impact: Security

WSM-00062: The path to the certificate used for the signature is invalid.

Cause: The intermediate and root certificates of the signing certificate were not present in the keystore at the verifying end.

Action: Make sure that the entire certificate chain is available in the keystore for verification.
Level: 1

Type: ERROR

Impact: Security

WSM-00063: The version of SAML is incorrect. Expected : {0}, Actual : {1}.

Cause: SAML version in the SAML assertion did not match the expected version.

Action: Check to see that the major version and minor version of the assertion are according to policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00063: The version of SAML is incorrect. Expected : {0}, Actual : {1}.

Cause: SAML version in the SAML assertion did not match the expected version.

Action: Check to see that the major version and minor version of the assertion are according to policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00064: SAML subject confirmation mismatch. Expected : {0}, Actual : {1}.

Cause: Subject confirmation method in SAML assertion did not match the policy requirements.

Action: Check to see that the confirmation method for all the SAML assertions is sender-vouches.
Level: 1

Type: ERROR

Impact: Security

WSM-00064: SAML subject confirmation mismatch. Expected : {0}, Actual : {1}.

Cause: Subject confirmation method in SAML assertion did not match the policy requirements.

Action: Check to see that the confirmation method for all the SAML assertions is sender-vouches.
Level: 1

Type: ERROR

Impact: Security

WSM-00065: Error sending request over SSL.

Cause: Failure in creating SSL request possibly due to invalid configuration of Credential Store FrameWork (CSF).

Action: Check the JPS configuration for CSF.
Level: 1

Type: ERROR

Impact: Other

WSM-00065: Error sending request over SSL.

Cause: Failure in creating SSL request possibly due to invalid configuration of Credential Store FrameWork (CSF).

Action: Check the JPS configuration for CSF.
Level: 1

Type: ERROR

Impact: Other

WSM-00066: The matching certificate for the given Subject Key Identifier (SKI) cannot be found.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00066: The matching certificate for the given Subject Key Identifier (SKI) cannot be found.

Cause: None

Action: None
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00067: None SOAP message parts can be encrypted.

Cause: The elements to be encrypted in the policy were selected to be either of soap Envelope/Body/Header.

Action: The core soap nodes cannot be encrypted according to WS-Security 1.0 specification.
Level: 1

Type: ERROR

Impact: Security

WSM-00067: None SOAP message parts can be encrypted.

Cause: The elements to be encrypted in the policy were selected to be either of soap Envelope/Body/Header.

Action: The core soap nodes cannot be encrypted according to WS-Security 1.0 specification.
Level: 1

Type: ERROR

Impact: Security

WSM-00068: The security token is missing.

Cause: Security token was expected but was not found.

Action: Security token is missing. Resend request with valid Security token.
Level: 1

Type: ERROR

Impact: Security

WSM-00068: The security token is missing.

Cause: Security token was expected but was not found.

Action: Security token is missing. Resend request with valid Security token.
Level: 1

Type: ERROR

Impact: Security

WSM-00069: The security header is missing. Ensure that there is a valid security policy attached at the client side, and the policy is enabled.

Cause: Security header was expected but was not found.

Action: Security header is missing. It could be that client side policy has not been applied. Resend request with appropriate Security header.
Level: 1

Type: ERROR

Impact: Security

WSM-00069: The security header is missing. Ensure that there is a valid security policy attached at the client side, and the policy is enabled.

Cause: Security header was expected but was not found.

Action: Security header is missing. It could be that client side policy has not been applied. Resend request with appropriate Security header.
Level: 1

Type: ERROR

Impact: Security

WSM-00070: The nonce cannot be validated.

Cause: Failure occurred while performing nonce Validation.

Action: This may be due to a repeated value of nonce. Resend the request with a valid nonce.
Level: 1

Type: ERROR

Impact: Security

WSM-00070: The nonce cannot be validated.

Cause: Failure occurred while performing nonce Validation.

Action: This may be due to a repeated value of nonce. Resend the request with a valid nonce.
Level: 1

Type: ERROR

Impact: Security

WSM-00071: Error validating the wsu:Created attribute.

Cause: Failure occurred while doing Created(Timestamp) validation.

Action: Resend the request with a valid timestamp, and or within the expiration limits.
Level: 1

Type: ERROR

Impact: Security

WSM-00071: Error validating the wsu:Created attribute.

Cause: Failure occurred while doing Created(Timestamp) validation.

Action: Resend the request with a valid timestamp, and or within the expiration limits.
Level: 1

Type: ERROR

Impact: Security

WSM-00072: An encryption algorithm suite policy compliance failure occurred.

Cause: Failure occurred in encryption algorithms policy compliance check.

Action: Check the encryption algorithm requirements of the policy and resend the message with appropriate value of algorithm suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00072: An encryption algorithm suite policy compliance failure occurred.

Cause: Failure occurred in encryption algorithms policy compliance check.

Action: Check the encryption algorithm requirements of the policy and resend the message with appropriate value of algorithm suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00073: The mechanism {0} used in the authentication header is not supported.

Cause: The value of mechanism attribute used was not supported.

Action: Change the policy to point to valid value of mechanism(basic), and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00073: The mechanism {0} used in the authentication header is not supported.

Cause: The value of mechanism attribute used was not supported.

Action: Change the policy to point to valid value of mechanism(basic), and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00074: The authorization header {0} is not correctly encoded using the Base64 encoding.

Cause: The authorization header was not encoded according to Base64 requirements.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00074: The authorization header {0} is not correctly encoded using the Base64 encoding.

Cause: The authorization header was not encoded according to Base64 requirements.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00075: The realm property is not configured in the policy.

Cause: The realm property was not configured in the policy.

Action: Configure appropriate value of realm inside the policy.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00075: The realm property is not configured in the policy.

Cause: The realm property was not configured in the policy.

Action: Configure appropriate value of realm inside the policy.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00076: The user name is missing from the encoded authorization header.

Cause: The Authorization header did not contain a properly encoded username, or username was null.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00076: The user name is missing from the encoded authorization header.

Cause: The Authorization header did not contain a properly encoded username, or username was null.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00077: The password is missing from the encoded authorization header.

Cause: The Authorization header did not contain password encoded properly, or password was null.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00077: The password is missing from the encoded authorization header.

Cause: The Authorization header did not contain password encoded properly, or password was null.

Action: Encode the header with Base64(username:realm:password) format and resend the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00078: The configuration of the credentials in the policy is incorrect.

Cause: Credential configuration in the policy was incorrect.

Action: Configure policy with valid Credential Store Framework (CSF) key, or username/password properties.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00078: The configuration of the credentials in the policy is incorrect.

Cause: Credential configuration in the policy was incorrect.

Action: Configure policy with valid Credential Store Framework (CSF) key, or username/password properties.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00079: The <BinarySecurityToken> element is missing.

Cause: <BinarySecurityToken> was not found.

Action: For reference mechanisms that are configured with value direct, send the certificate inside <BinarySecurityToken> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00079: The <BinarySecurityToken> element is missing.

Cause: <BinarySecurityToken> was not found.

Action: For reference mechanisms that are configured with value direct, send the certificate inside <BinarySecurityToken> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00080: STR Dereferencing Transform not found

Cause: STR Dereferencing Transform was not found.

Action: For reference mechanisms that are configured with value SKI, the Transforms section should contain the STR Dereferencing Transform.
Level: 1

Type: ERROR

Impact: Security

WSM-00080: STR Dereferencing Transform not found

Cause: STR Dereferencing Transform was not found.

Action: For reference mechanisms that are configured with value SKI, the Transforms section should contain the STR Dereferencing Transform.
Level: 1

Type: ERROR

Impact: Security

WSM-00081: The X.509 certificate is not signed.

Cause: The X509 token used was not signed according to requirements of certificate authentication scenario.

Action: Sign the X509 token (depending upon the reference mechanism used) for certificate authentication.
Level: 1

Type: ERROR

Impact: Security

WSM-00081: The X.509 certificate is not signed.

Cause: The X509 token used was not signed according to requirements of certificate authentication scenario.

Action: Sign the X509 token (depending upon the reference mechanism used) for certificate authentication.
Level: 1

Type: ERROR

Impact: Security

WSM-00082: The roles and/or attributes of the user profile cannot be retrieved.

Cause: No information could be obtained regarding the user roles or attributes.

Action: Try resending the request for another user.
Level: 1

Type: ERROR

Impact: Security

WSM-00082: The roles and/or attributes of the user profile cannot be retrieved.

Cause: No information could be obtained regarding the user roles or attributes.

Action: Try resending the request for another user.
Level: 1

Type: ERROR

Impact: Security

WSM-00083: Error computing the digest for this reference.

Cause: Digest computation for the <Reference> failed.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00083: Error computing the digest for this reference.

Cause: Digest computation for the <Reference> failed.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00084: Error computing <SignatureValue> for this signature block.

Cause: Signature value computation for the signature block failed.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00084: Error computing <SignatureValue> for this signature block.

Cause: Signature value computation for the signature block failed.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00085: The certificates cannot be retrieved from the keystore.

Cause: Failure occurred while trying to retrieve certificate from keystore.

Action: Use a valid alias for the certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00085: The certificates cannot be retrieved from the keystore.

Cause: Failure occurred while trying to retrieve certificate from keystore.

Action: Use a valid alias for the certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00086: Error initializating nonce cache.

Cause: Failure occurred while initializing iAS Cache.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00086: Error initializating nonce cache.

Cause: Failure occurred while initializing iAS Cache.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00087: Either {0} property or the oracle.j2ee.home system property is not set.

Cause: The cache configuration file for iAS cache was not found.

Action: Set the system property oracle.j2ee.home or javacache.config.home system property to the path of the configuration file javacache.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00087: Either {0} property or the oracle.j2ee.home system property is not set.

Cause: The cache configuration file for iAS cache was not found.

Action: Set the system property oracle.j2ee.home or javacache.config.home system property to the path of the configuration file javacache.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00088: The ObSSOCookie is missing.

Cause: The OAM security token was not found.

Action: Resend the request by embedding the ObSSOCookie token inside a <BinarySecurityToken> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00088: The ObSSOCookie is missing.

Cause: The OAM security token was not found.

Action: Resend the request by embedding the ObSSOCookie token inside a <BinarySecurityToken> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00089: The attachments security transform is incorrect. Expected : {0}, Actual : {1}.

Cause: The attachment security transform used was incorrect.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00089: The attachments security transform is incorrect. Expected : {0}, Actual : {1}.

Cause: The attachment security transform used was incorrect.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00090: The signature for the attachment is non-compliant.

Cause: The attachment signature was not compliant.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00090: The signature for the attachment is non-compliant.

Cause: The attachment signature was not compliant.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00091: The encryption of the attachment is non-compliant.

Cause: The attachment encryption was not compliant.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00091: The encryption of the attachment is non-compliant.

Cause: The attachment encryption was not compliant.

Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.
Level: 1

Type: ERROR

Impact: Security

WSM-00092: The <EncryptedKey> element is missing in the request. Ensure that there is a message protection policy attached at the client side.

Cause: No <EncryptedKey> elements were found in the request.

Action: Refer to the WS-Security 1.0 and 1.0 specifications for the semantics.
Level: 1

Type: ERROR

Impact: Security

WSM-00092: The <EncryptedKey> element is missing in the request. Ensure that there is a message protection policy attached at the client side.

Cause: No <EncryptedKey> elements were found in the request.

Action: Refer to the WS-Security 1.0 and 1.0 specifications for the semantics.
Level: 1

Type: ERROR

Impact: Security

WSM-00093: The <saml:Assertion> element is missing in the security header. Ensure that there is a SAML token policy attached at the client side. Tokens found in the security header are:- {0}.

Cause: No SAML assertions were found inside the security Header.

Action: Resend the message with at least one SAML assertion in the header.
Level: 1

Type: ERROR

Impact: Security

WSM-00093: The <saml:Assertion> element is missing in the security header. Ensure that there is a SAML token policy attached at the client side. Tokens found in the security header are:- {0}.

Cause: No SAML assertions were found inside the security Header.

Action: Resend the message with at least one SAML assertion in the header.
Level: 1

Type: ERROR

Impact: Security

WSM-00094: The negotiated cipher suite does not meet policy requirements. Expected : {0}, Actual : {1}.

Cause: The negotiated cipher suite did not meet policy requirements.

Action: Check the recipient's policy for the permitted values of the cipher suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00094: The negotiated cipher suite does not meet policy requirements. Expected : {0}, Actual : {1}.

Cause: The negotiated cipher suite did not meet policy requirements.

Action: Check the recipient's policy for the permitted values of the cipher suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00095: There is more than one assertion assigned to the same category {0} in the security policy.

Cause: Two or more assertions assigned to the same category were used.

Action: Ensure that assertions inside a security policy belong to different categories.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00095: There is more than one assertion assigned to the same category {0} in the security policy.

Cause: Two or more assertions assigned to the same category were used.

Action: Ensure that assertions inside a security policy belong to different categories.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00096: The order of the assertions is incorrect.

Cause: Assertion order does not match the requirements of policy.

Action: Use the following order for client side policy : authentication -> msgprotection or authentication -> authorization and following for server side security policy msg-protection -> authentication or msg-protection -> authentication -> authorization.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00096: The order of the assertions is incorrect.

Cause: Assertion order does not match the requirements of policy.

Action: Use the following order for client side policy : authentication -> msgprotection or authentication -> authorization and following for server side security policy msg-protection -> authentication or msg-protection -> authentication -> authorization.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00097: HTTP basic authentication header is missing.

Cause: HTTP basic authentication header was missing.

Action: Client must provide the HTTP basic authentication header.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00097: HTTP basic authentication header is missing.

Cause: HTTP basic authentication header was missing.

Action: Client must provide the HTTP basic authentication header.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00098: User realm {0} is either null or is a mismatch with service realm {1}.

Cause: User realm was either null or was a mismatch with service realm.

Action: Make sure user realm sent from client matches with the service realm.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00098: User realm {0} is either null or is a mismatch with service realm {1}.

Cause: User realm was either null or was a mismatch with service realm.

Action: Make sure user realm sent from client matches with the service realm.
Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00099: Username, password, or both are missing from the HTTP authentication header.

Cause: Username, password, or both were missing from HTTP authentication header.

Action: Make sure the HTTP request header contains the username/password token.
Level: 1

Type: ERROR

Impact: Security

WSM-00099: Username, password, or both are missing from the HTTP authentication header.

Cause: Username, password, or both were missing from HTTP authentication header.

Action: Make sure the HTTP request header contains the username/password token.
Level: 1

Type: ERROR

Impact: Security

WSM-00100: Found more than one keystore files {0} in application classpath. By default the first keystore is used. Make sure the desired keystore is being used by clearing others from the classpath.

Cause: Found more than one keystore file in application classpath. By default, the first keystore is used.

Action: To ensure the desired keystore is being used, remove other keystores from the classpath, if possible.
Level: 1

Type: WARNING

Impact: Security

WSM-00100: Found more than one keystore files {0} in application classpath. By default the first keystore is used. Make sure the desired keystore is being used by clearing others from the classpath.

Cause: Found more than one keystore file in application classpath. By default, the first keystore is used.

Action: To ensure the desired keystore is being used, remove other keystores from the classpath, if possible.
Level: 1

Type: WARNING

Impact: Security

WSM-00101: The specified keystore file {0} cannot be found; it either does not exist or its path is not included in the application classpath.

Cause: Keystore file did not exist or its path was either incorrect or not included in the application classpath.

Action: Verify the keystore file does exist and its path is included in the application classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00101: The specified keystore file {0} cannot be found; it either does not exist or its path is not included in the application classpath.

Cause: Keystore file did not exist or its path was either incorrect or not included in the application classpath.

Action: Verify the keystore file does exist and its path is included in the application classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00102: The specified user/subject does not belong to any role in system ID store.

Cause: The subject/user did not belong to any defined role in system ID store.

Action: Verify and make sure that the specified user belongs to one or more roles.
Level: 1

Type: ERROR

Impact: Security

WSM-00102: The specified user/subject does not belong to any role in system ID store.

Cause: The subject/user did not belong to any defined role in system ID store.

Action: Verify and make sure that the specified user belongs to one or more roles.
Level: 1

Type: ERROR

Impact: Security

WSM-00103: The policy is configured incorrectly without specifying roles, or denyAll or permitAll elements.

Cause: The policy was incorrectly configured with no roles and no denyAll/permitAll elements.

Action: Correct the policy by configuring it with a denyAll element, a permitAll element, or at least one role.
Level: 1

Type: ERROR

Impact: Security

WSM-00103: The policy is configured incorrectly without specifying roles, or denyAll or permitAll elements.

Cause: The policy was incorrectly configured with no roles and no denyAll/permitAll elements.

Action: Correct the policy by configuring it with a denyAll element, a permitAll element, or at least one role.
Level: 1

Type: ERROR

Impact: Security

WSM-00104: The specified JPS context {0} cannot be found in system-level JPS configuration file.

Cause: The JPS context could not be found in system level JPS configuration.

Action: Verify system level JPS configuration file to ensure that it contains the context.
Level: 1

Type: ERROR

Impact: Security

WSM-00104: The specified JPS context {0} cannot be found in system-level JPS configuration file.

Cause: The JPS context could not be found in system level JPS configuration.

Action: Verify system level JPS configuration file to ensure that it contains the context.
Level: 1

Type: ERROR

Impact: Security

WSM-00105: Credential Store service instance is missing. Either the Oracle WSM JPS context being used for the keystore does not contain a reference to the Credential Store service instance, or the reference is not valid. The Credential Store service instance needs to be declared at the same level (system or application) as the keystore service instance. Therefore, if an application-level keystore is being used, a Credential Store Framework (CSF) store must also be declared at the application level.

Cause: No Credential Store (CSF) was found at the level where keystore was used.

Action: Verify that the WSM JPS context is configured correctly. The error indicates that either the WSM JPS context which is being used for keystore does not contain reference to the Credential Store service instance, or the reference is not valid. The Credential Store service instance needs to be declared at the same level (system or application) as the keystore service instance. Therefore, if an application level keystore is being used, a CSF store must also be declared at the the application level.
Level: 1

Type: ERROR

Impact: Security

WSM-00105: Credential Store service instance is missing. Either the Oracle WSM JPS context being used for the keystore does not contain a reference to the Credential Store service instance, or the reference is not valid. The Credential Store service instance needs to be declared at the same level (system or application) as the keystore service instance. Therefore, if an application-level keystore is being used, a Credential Store Framework (CSF) store must also be declared at the application level.

Cause: No Credential Store (CSF) was found at the level where keystore was used.

Action: Verify that the WSM JPS context is configured correctly. The error indicates that either the WSM JPS context which is being used for keystore does not contain reference to the Credential Store service instance, or the reference is not valid. The Credential Store service instance needs to be declared at the same level (system or application) as the keystore service instance. Therefore, if an application level keystore is being used, a CSF store must also be declared at the the application level.
Level: 1

Type: ERROR

Impact: Security

WSM-00106: Assertion assigned to a non-security category {0} cannot be added to policy assigned to a security category.

Cause: Assertion belonging to non-security categories could not be added to policies belonging to security category.

Action: Ensure that assertions in security policy also belongs to security category.
Level: 1

Type: ERROR

Impact: Security

WSM-00106: Assertion assigned to a non-security category {0} cannot be added to policy assigned to a security category.

Cause: Assertion belonging to non-security categories could not be added to policies belonging to security category.

Action: Ensure that assertions in security policy also belongs to security category.
Level: 1

Type: ERROR

Impact: Security

WSM-00107: Assertion belonging to {0} category is not valid for generic policy. Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Check the assertions added to the generic policy.

Cause: Invalid assertions were found in generic policy.

Action: Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Recheck the assertions added to the generic policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00107: Assertion belonging to {0} category is not valid for generic policy. Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Check the assertions added to the generic policy.

Cause: Invalid assertions were found in generic policy.

Action: Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Recheck the assertions added to the generic policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00108: If password type is set to digest, addNonce and addCreated should be true.

Cause: UserNameToken Assertion had Passwordtype as digest but addNonce or addCreated was false.

Action: In case of passwordtype as digest, addNonce and addCreated both should be true. Recheck the assertion.
Level: 1

Type: ERROR

Impact: Security

WSM-00108: If password type is set to digest, addNonce and addCreated should be true.

Cause: UserNameToken Assertion had Passwordtype as digest but addNonce or addCreated was false.

Action: In case of passwordtype as digest, addNonce and addCreated both should be true. Recheck the assertion.
Level: 1

Type: ERROR

Impact: Security

WSM-00109: Algorithm suite is not supported, only TripleDes is supported for Kerberos assertion.

Cause: Kerberos Assertion had algorithm-suite other than TripleDES.

Action: Only TripleDES algorithm is supported in case of Kerberos, so set algorithm-suite as TripleDes.
Level: 1

Type: ERROR

Impact: Security

WSM-00109: Algorithm suite is not supported, only TripleDes is supported for Kerberos assertion.

Cause: Kerberos Assertion had algorithm-suite other than TripleDES.

Action: Only TripleDES algorithm is supported in case of Kerberos, so set algorithm-suite as TripleDes.
Level: 1

Type: ERROR

Impact: Security

WSM-00110: Basic192 and *RSA15 algorithm-suites are not supported for SSL. Change the algorithm suite to one that is supported.

Cause: Basic192 or RSA algorithm-suite was used for SSL.

Action: Use other supported Algorithm-suite for SSL except Basic192 and RSA algorithms.
Level: 1

Type: ERROR

Impact: Security

WSM-00110: Basic192 and *RSA15 algorithm-suites are not supported for SSL. Change the algorithm suite to one that is supported.

Cause: Basic192 or RSA algorithm-suite was used for SSL.

Action: Use other supported Algorithm-suite for SSL except Basic192 and RSA algorithms.
Level: 1

Type: ERROR

Impact: Security

WSM-00111: Keystore is not properly configured in JPS config.

Cause: Keystore was not properly configured in JPS configuration or through config override properties.

Action: Check the keystore configuration, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00111: Keystore is not properly configured in JPS config.

Cause: Keystore was not properly configured in JPS configuration or through config override properties.

Action: Check the keystore configuration, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00112: Missing keystore service instance reference in Oracle WSM JPS context.

Cause: Keystore Service instance reference was not found in WSM JPS context.

Action: Add the keystore service instance reference to WSM JPS context, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00112: Missing keystore service instance reference in Oracle WSM JPS context.

Cause: Keystore Service instance reference was not found in WSM JPS context.

Action: Add the keystore service instance reference to WSM JPS context, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00113: Unsupported configuration value for Client Credential Configuration location.

Cause: An unsupported configuration value of Client Credential location configuration was provided.

Action: Refer to the documentation for valid values and add the proper configuration value for Client Credential Configuration Location, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00113: Unsupported configuration value for Client Credential Configuration location.

Cause: An unsupported configuration value of Client Credential location configuration was provided.

Action: Refer to the documentation for valid values and add the proper configuration value for Client Credential Configuration Location, and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00114: No matching SSL cipher suite is found for algorithm suite value, specified in the Policy.

Cause: No matching SSL cipher suite was found for algorithm suite value, specified in WS Policy.

Action: Set algorithm suite of Web Service policy to a value that has matching SSL cipher suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00114: No matching SSL cipher suite is found for algorithm suite value, specified in the Policy.

Cause: No matching SSL cipher suite was found for algorithm suite value, specified in WS Policy.

Action: Set algorithm suite of Web Service policy to a value that has matching SSL cipher suite.
Level: 1

Type: ERROR

Impact: Security

WSM-00115: JSSE System Property for SSL cipher suite is either not set or does not match algorithm suite value specified in WS Policy.

Cause: JSSE System Property for SSL cipher suite was either not set or did not match algorithm suite value specified in WS Policy.

Action: Set JSSE System Property (https.cipherSuites) to a value that matches algorithm suite as specified in WS Policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00115: JSSE System Property for SSL cipher suite is either not set or does not match algorithm suite value specified in WS Policy.

Cause: JSSE System Property for SSL cipher suite was either not set or did not match algorithm suite value specified in WS Policy.

Action: Set JSSE System Property (https.cipherSuites) to a value that matches algorithm suite as specified in WS Policy.
Level: 1

Type: ERROR

Impact: Security

WSM-00116: Error retrieving SOAP body from SOAP message.

Cause: An error ocurred while retrieving SOAPBody from SOAPMessage. Either the SOAPMessage was not proper or had been tampered with.

Action: Check whether the SOAPMessage is according to the Specifications and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00116: Error retrieving SOAP body from SOAP message.

Cause: An error ocurred while retrieving SOAPBody from SOAPMessage. Either the SOAPMessage was not proper or had been tampered with.

Action: Check whether the SOAPMessage is according to the Specifications and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00117: Error occurred while transforming the security header.

Cause: TransformerException occurred while transforming the WssHeader to String. The SOAPMessage might not have been proper or it did not conform to the specifications.

Action: Check the SOAPMessage and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00117: Error occurred while transforming the security header.

Cause: TransformerException occurred while transforming the WssHeader to String. The SOAPMessage might not have been proper or it did not conform to the specifications.

Action: Check the SOAPMessage and try again.
Level: 1

Type: ERROR

Impact: Security

WSM-00118: OAM token can be inserted only on hosted clients where authenticated subject has been established.

Cause: Insertion of an OAM token tried from a non-hosted client where Authenticated Subject is not established.

Action: Try to add OAM token from a hosted client as only the hosted clients can insert the OAM token extracting it from Authenticated Subject
Level: 1

Type: ERROR

Impact: Security

WSM-00118: OAM token can be inserted only on hosted clients where authenticated subject has been established.

Cause: Insertion of an OAM token tried from a non-hosted client where Authenticated Subject is not established.

Action: Try to add OAM token from a hosted client as only the hosted clients can insert the OAM token extracting it from Authenticated Subject
Level: 1

Type: ERROR

Impact: Security

WSM-00119: Either authorization header or requireTLS must be present.

Cause: The security policy attached did not have either auth Header or requireTLS set to true.

Action: Change the policy to have either auth Header or requireTLS to be true.
Level: 1

Type: ERROR

Impact: Security

WSM-00119: Either authorization header or requireTLS must be present.

Cause: The security policy attached did not have either auth Header or requireTLS set to true.

Action: Change the policy to have either auth Header or requireTLS to be true.
Level: 1

Type: ERROR

Impact: Security

WSM-00120: Cannot compute endorsing signature as no message signature is present.

Cause: The security policy did not sign anything from the message, so no signature was there. Endorsing Signature could not be computed as the signature which it was trying to endorse was not present.

Action: Change the policy to Sign at least something in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00120: Cannot compute endorsing signature as no message signature is present.

Cause: The security policy did not sign anything from the message, so no signature was there. Endorsing Signature could not be computed as the signature which it was trying to endorse was not present.

Action: Change the policy to Sign at least something in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00121: Only the attachments are to be signed/encrypted and they are not present.

Cause: Only the attachments were to be signed/encrypted and they were not present.

Action: Retry after putting attachments in the SOAP Message.
Level: 1

Type: ERROR

Impact: Security

WSM-00121: Only the attachments are to be signed/encrypted and they are not present.

Cause: Only the attachments were to be signed/encrypted and they were not present.

Action: Retry after putting attachments in the SOAP Message.
Level: 1

Type: ERROR

Impact: Security

WSM-00122: Valid timestamp is not present in the message.

Cause: Timestamp was not present in the message or the timestamp present did not conform to specifications.

Action: Ensure the timestamp is present in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00122: Valid timestamp is not present in the message.

Cause: Timestamp was not present in the message or the timestamp present did not conform to specifications.

Action: Ensure the timestamp is present in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00123: Timestamp of the message is in future.

Cause: The message had Created timestamp of a time in future so it failed Future message validation.

Action: Ensure freshness of the message and check policy-accessor-config.xml for the configured values of agent.clock.skew.
Level: 1

Type: ERROR

Impact: Security

WSM-00123: Timestamp of the message is in future.

Cause: The message had Created timestamp of a time in future so it failed Future message validation.

Action: Ensure freshness of the message and check policy-accessor-config.xml for the configured values of agent.clock.skew.
Level: 1

Type: ERROR

Impact: Security

WSM-00124: Timestamp of the message is in past.

Cause: The message was older than the permissible time limit so it failed Past message validation.

Action: Ensure freshness of the Message and check the policy-accessor-config.xml for the configured values of agent.clock.skew and agent.expire.time.
Level: 1

Type: ERROR

Impact: Security

WSM-00124: Timestamp of the message is in past.

Cause: The message was older than the permissible time limit so it failed Past message validation.

Action: Ensure freshness of the Message and check the policy-accessor-config.xml for the configured values of agent.clock.skew and agent.expire.time.
Level: 1

Type: ERROR

Impact: Security

WSM-00125: Password digest validation failed.

Cause: The password digest in the message was not correct so it failed the digest validation.

Action: Retry after ensuring password digest is proper.
Level: 1

Type: ERROR

Impact: Security

WSM-00125: Password digest validation failed.

Cause: The password digest in the message was not correct so it failed the digest validation.

Action: Retry after ensuring password digest is proper.
Level: 1

Type: ERROR

Impact: Security

WSM-00126: Subject does not contain JPS user.

Cause: The subject mentioned did not have the JPS User.

Action: Retry after ensuring JPS user in the subject.
Level: 1

Type: ERROR

Impact: Security

WSM-00126: Subject does not contain JPS user.

Cause: The subject mentioned did not have the JPS User.

Action: Retry after ensuring JPS user in the subject.
Level: 1

Type: ERROR

Impact: Security

WSM-00127: User not in identity store.

Cause: The user mentioned was not present in the identity store.

Action: Retry after ensuring that user is present in the identity Store.
Level: 1

Type: ERROR

Impact: Security

WSM-00127: User not in identity store.

Cause: The user mentioned was not present in the identity store.

Action: Retry after ensuring that user is present in the identity Store.
Level: 1

Type: ERROR

Impact: Security

WSM-00128: Keystore instance is null.

Cause: Could not obtain keystore instance. Either the keystore instance type was wrong or the keystore configuration was wrong.

Action: Check JPS configuration settings. Use correct keystore instance type.
Level: 1

Type: ERROR

Impact: Security

WSM-00128: Keystore instance is null.

Cause: Could not obtain keystore instance. Either the keystore instance type was wrong or the keystore configuration was wrong.

Action: Check JPS configuration settings. Use correct keystore instance type.
Level: 1

Type: ERROR

Impact: Security

WSM-00129: Unsupported SAML token provided : {0}.

Cause: An unsupported SAML token confirmation method was provided.

Action: Provide a supported SAML token confirmation method and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00129: Unsupported SAML token provided : {0}.

Cause: An unsupported SAML token confirmation method was provided.

Action: Provide a supported SAML token confirmation method and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00130: SAML assertion subject is missing.

Cause: The SAML assertion subject name was not specified.

Action: Provide the SAML assertion subject and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00130: SAML assertion subject is missing.

Cause: The SAML assertion subject name was not specified.

Action: Provide the SAML assertion subject and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00131: Unsupported data encryption algorithm: {0}.

Cause: An unsupported data encryption algorithm was provided.

Action: Consult the documentation for the supported encryption algorithms and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00131: Unsupported data encryption algorithm: {0}.

Cause: An unsupported data encryption algorithm was provided.

Action: Consult the documentation for the supported encryption algorithms and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00132: Invalid JPS configuration.

Cause: An invalid JPS configuration was provided.

Action: Make sure that the JPS configuration is valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00132: Invalid JPS configuration.

Cause: An invalid JPS configuration was provided.

Action: Make sure that the JPS configuration is valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00133: Unsupported MessageContext type {0}.

Cause: Unsupported MessageContext type was provided.

Action: Correct the MessageContext type and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-00133: Unsupported MessageContext type {0}.

Cause: Unsupported MessageContext type was provided.

Action: Correct the MessageContext type and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-00134: The signature key, {0}, is not retrieved due to exception {1}.

Cause: Error occurred while obtaining the signature key from store.

Action: Check JPS configuration settings. Make sure that the key password , keystore password, and key alias are valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00134: The signature key, {0}, is not retrieved due to exception {1}.

Cause: Error occurred while obtaining the signature key from store.

Action: Check JPS configuration settings. Make sure that the key password , keystore password, and key alias are valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00135: The encryption key, {0}, is not retrieved due to exception {1}.

Cause: Error occurred while obtaining encryption key from store.

Action: Check JPS configuration settings. Use correct key password, keystore password, and key alias.
Level: 1

Type: ERROR

Impact: Security

WSM-00135: The encryption key, {0}, is not retrieved due to exception {1}.

Cause: Error occurred while obtaining encryption key from store.

Action: Check JPS configuration settings. Use correct key password, keystore password, and key alias.
Level: 1

Type: ERROR

Impact: Security

WSM-00136: The signature certificate, {0}, is not retrieved due to exception {1}.

Cause: Failure occurred while retrieving the signature certificate from store.

Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Security

WSM-00136: The signature certificate, {0}, is not retrieved due to exception {1}.

Cause: Failure occurred while retrieving the signature certificate from store.

Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Security

WSM-00137: The encryption certificate, {0}, is not retrieved due to exception {1}.

Cause: Failure occurred while retrieving the encryption certificate from store.

Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Security

WSM-00137: The encryption certificate, {0}, is not retrieved due to exception {1}.

Cause: Failure occurred while retrieving the encryption certificate from store.

Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.
Level: 1

Type: ERROR

Impact: Security

WSM-00138: The path to the certificate is invalid. Validation failed for the certificate {0} Certificates in cert path used for validation are:- {1}

Cause: The intermediate and root certificates of the certificate were not present in the keystore during verification.

Action: Make sure that the entire certificate chain is available in the keystore for verification.
Level: 1

Type: ERROR

Impact: Security

WSM-00138: The path to the certificate is invalid. Validation failed for the certificate {0} Certificates in cert path used for validation are:- {1}

Cause: The intermediate and root certificates of the certificate were not present in the keystore during verification.

Action: Make sure that the entire certificate chain is available in the keystore for verification.
Level: 1

Type: ERROR

Impact: Security

WSM-00139: The scenario category {0} is not supported.

Cause: The scenario category is not supported.

Action: Consult the Oracle documentation for supported categories.
Level: 1

Type: ERROR

Impact: Security

WSM-00139: The scenario category {0} is not supported.

Cause: The scenario category is not supported.

Action: Consult the Oracle documentation for supported categories.
Level: 1

Type: ERROR

Impact: Security

WSM-00140: Invalid execution stage {0} resulting in system internal error.

Cause: System encountered an invalid execution stage.

Action: Retry the operation, If problem persists contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00140: Invalid execution stage {0} resulting in system internal error.

Cause: System encountered an invalid execution stage.

Action: Retry the operation, If problem persists contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00141: Error retrieving SOAP header from SOAP message.

Cause: An error occurred while retrieving the header from the SOAP Message. The SOAP message was invalid or was tampered with.

Action: Make sure that the SOAP message is valid according to the specifications and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00141: Error retrieving SOAP header from SOAP message.

Cause: An error occurred while retrieving the header from the SOAP Message. The SOAP message was invalid or was tampered with.

Action: Make sure that the SOAP message is valid according to the specifications and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00142: Assertion belonging to {0} category is not valid for Component policy

Cause: Assertion belonging to authentication or message protection category was found in Component policy and it is invalid.

Action: Modify the policy to correct the problem and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00142: Assertion belonging to {0} category is not valid for Component policy

Cause: Assertion belonging to authentication or message protection category was found in Component policy and it is invalid.

Action: Modify the policy to correct the problem and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00143: Failure creating Java Keystore instance for type {0}.

Cause: Either the keystore type provided is not supported or there is no implementation provider for Java keystore.

Action: Consult the Oracle documentation for supported Keystore types and make sure the implementation provider for Java Keystore is available.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00143: Failure creating Java Keystore instance for type {0}.

Cause: Either the keystore type provided is not supported or there is no implementation provider for Java keystore.

Action: Consult the Oracle documentation for supported Keystore types and make sure the implementation provider for Java Keystore is available.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00144: Failure retrieving Keystore aliases.

Cause: Keystore may have not been initialized.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00144: Failure retrieving Keystore aliases.

Cause: Keystore may have not been initialized.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00145: Keystore location or path can not be null or empty; it must be configured through JPS configuration or policy configuration override.

Cause: Keystore location/path was either missing, set to be null, or empty.

Action: Make sure that Keystore location is configured properly in the JPS configuration or through policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00145: Keystore location or path can not be null or empty; it must be configured through JPS configuration or policy configuration override.

Cause: Keystore location/path was either missing, set to be null, or empty.

Action: Make sure that Keystore location is configured properly in the JPS configuration or through policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00146: Keystore type {0} defined using keystore.type property in the JPS configuration or through policy configuration override is not supported.

Cause: Invalid or unsupported keystore.type property value was found.

Action: Consult the oracle documentation to ensure that a valid keystore.type is configured either through JPS configuration or using policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00146: Keystore type {0} defined using keystore.type property in the JPS configuration or through policy configuration override is not supported.

Cause: Invalid or unsupported keystore.type property value was found.

Action: Consult the oracle documentation to ensure that a valid keystore.type is configured either through JPS configuration or using policy configuration override.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00147: JPS context property is no longer supported in policy configuration

Cause: Unsupported JPS context property value was found.

Action: Remove JPS context property from the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00147: JPS context property is no longer supported in policy configuration

Cause: Unsupported JPS context property value was found.

Action: Remove JPS context property from the configuration file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00148: Security policy cannot be applied to streamed attachments. Streaming should be turned off if there are any security policies for attachments.

Cause: Security policy cannot be applied to streamed attachments.

Action: Make sure streaming is off if security policies are being used for attachments.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00148: Security policy cannot be applied to streamed attachments. Streaming should be turned off if there are any security policies for attachments.

Cause: Security policy cannot be applied to streamed attachments.

Action: Make sure streaming is off if security policies are being used for attachments.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00149: SAML assertion is missing.

Cause: Failed to locate SAML assertion with ID {0}.

Action: Make sure that a valid SAML asssertion exists.
Level: 1

Type: ERROR

Impact: Security

WSM-00149: SAML assertion is missing.

Cause: Failed to locate SAML assertion with ID {0}.

Action: Make sure that a valid SAML asssertion exists.
Level: 1

Type: ERROR

Impact: Security

WSM-00150: Processed header list fetched from InterceptorContext is null, agentFunction:{0}, listType:{1}.

Cause: Processed header list fetched from InterceptorContext is null.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00150: Processed header list fetched from InterceptorContext is null, agentFunction:{0}, listType:{1}.

Cause: Processed header list fetched from InterceptorContext is null.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00151: Role class {0} specified in the policy is either invalid or is not available in the classpath. Exception thrown : {1}.

Cause: Class name required for retrieving principal/role from subject is either invalid or class not present in the classpath

Action: Specify a valid class name in the policy and ensure that the instances of the class specified are associated with the subject created.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00151: Role class {0} specified in the policy is either invalid or is not available in the classpath. Exception thrown : {1}.

Cause: Class name required for retrieving principal/role from subject is either invalid or class not present in the classpath

Action: Specify a valid class name in the policy and ensure that the instances of the class specified are associated with the subject created.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00152: Callback {0} is not supported by Oracle WSM callback handler.

Cause: Callback specified is not supported by Oracle WSM callback handler.

Action: Specify a valid callback class that Oracle WSM callback handler can support.
Level: 1

Type: WARNING

Impact: Security

WSM-00152: Callback {0} is not supported by Oracle WSM callback handler.

Cause: Callback specified is not supported by Oracle WSM callback handler.

Action: Specify a valid callback class that Oracle WSM callback handler can support.
Level: 1

Type: WARNING

Impact: Security

WSM-00153: Error retrieving Weblogic Server subject from JPS subject using SubjectSecurityUtil API

Cause: A failure occurred while converting JPS subject to Weblogic Server subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00153: Error retrieving Weblogic Server subject from JPS subject using SubjectSecurityUtil API

Cause: A failure occurred while converting JPS subject to Weblogic Server subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00154: The empty or all-spaces value set explicitly for property {0} is detected and it is not valid value.

Cause: The property value was probably set unintentionally to empty or all-spaces through policy configuration override or JPS configuration.

Action: Make sure that the value provided either through policy configuration override, policy binding, or JPS configuration is not empty or all spaces.
Level: 1

Type: ERROR

Impact: Security

WSM-00154: The empty or all-spaces value set explicitly for property {0} is detected and it is not valid value.

Cause: The property value was probably set unintentionally to empty or all-spaces through policy configuration override or JPS configuration.

Action: Make sure that the value provided either through policy configuration override, policy binding, or JPS configuration is not empty or all spaces.
Level: 1

Type: ERROR

Impact: Security

WSM-00155: Error retrieving Oracle WSM security policies.

Cause: A failure occurred while retrieving Oracle WSM security policies.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00155: Error retrieving Oracle WSM security policies.

Cause: A failure occurred while retrieving Oracle WSM security policies.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-00156: Invalid binary security token.

Cause: Binary security token in the header and the certificate used for endorsing signature did not match.

Action: Make sure a valid binary security token is being passed.
Level: 1

Type: ERROR

Impact: Security

WSM-00156: Invalid binary security token.

Cause: Binary security token in the header and the certificate used for endorsing signature did not match.

Action: Make sure a valid binary security token is being passed.
Level: 1

Type: ERROR

Impact: Security

WSM-00157: Recipient key alias not configured and signer certificate was not available because no part of the request was signed.

Cause: Recipient key alias not configured and signer's certificate was not available because no part of request was signed.

Action: Set recipient key alias in service policy or sign part of the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00157: Recipient key alias not configured and signer certificate was not available because no part of the request was signed.

Cause: Recipient key alias not configured and signer's certificate was not available because no part of request was signed.

Action: Set recipient key alias in service policy or sign part of the request.
Level: 1

Type: ERROR

Impact: Security

WSM-00158: KerberosLoginModule class is not available in the classpath

Cause: The class for the Kerberos login module was not available in the classpath.

Action: Make sure that the KerberosLoginModule class is included in the classpath, and configure the class name properly in policy-config.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00158: KerberosLoginModule class is not available in the classpath

Cause: The class for the Kerberos login module was not available in the classpath.

Action: Make sure that the KerberosLoginModule class is included in the classpath, and configure the class name properly in policy-config.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00159: TextCallbackHandler class is not available in the classpath

Cause: The class for the Text callback handler was not available in the classpath.

Action: Make sure that the TextCallbackHandler class is included in the classpath, and configure the class name properly in policy-config.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00159: TextCallbackHandler class is not available in the classpath

Cause: The class for the Text callback handler was not available in the classpath.

Action: Make sure that the TextCallbackHandler class is included in the classpath, and configure the class name properly in policy-config.xml.
Level: 1

Type: ERROR

Impact: Security

WSM-00160: The SSL policy must contain a requireTLS element.

Cause: The security policy attached did not have requireTLS set to true.

Action: Change the policy to have requireTLS as true.
Level: 1

Type: ERROR

Impact: Security

WSM-00160: The SSL policy must contain a requireTLS element.

Cause: The security policy attached did not have requireTLS set to true.

Action: Change the policy to have requireTLS as true.
Level: 1

Type: ERROR

Impact: Security

WSM-00161: Client encryption public certificate is not configured for Async web service client

Cause: Client encryption public certificate is not configured for async web service client with message protection.

Action: Make sure that client public certificate is configured in client keystore, or provided through client config override for Async web service client that uses message protection
Level: 1

Type: ERROR

Impact: Security

WSM-00161: Client encryption public certificate is not configured for Async web service client

Cause: Client encryption public certificate is not configured for async web service client with message protection.

Action: Make sure that client public certificate is configured in client keystore, or provided through client config override for Async web service client that uses message protection
Level: 1

Type: ERROR

Impact: Security

WSM-00162: Invalid recipient cert type: {0} may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.

Cause: Invalid recipient cert type may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.

Action: Verify that only X509Certificate object, or Base64 encoded String value are provided in Policy, descriptor file or through program.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00162: Invalid recipient cert type: {0} may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.

Cause: Invalid recipient cert type may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.

Action: Verify that only X509Certificate object, or Base64 encoded String value are provided in Policy, descriptor file or through program.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00163: Failure in getting recipient certificate using recipient key alias {0}

Cause: The recipient key alias might not be valid

Action: Check to see if there is such certificate in keystore corresponding to the recipient key alias provided.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00163: Failure in getting recipient certificate using recipient key alias {0}

Cause: The recipient key alias might not be valid

Action: Check to see if there is such certificate in keystore corresponding to the recipient key alias provided.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00164: Cannot obtain a valid recipient cert for client message sending

Cause: Encountered error while obtaining recipient certificate for sending request.

Action: Must provide valid recipient certificate, or recipient alias for client to send request with message protection.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00164: Cannot obtain a valid recipient cert for client message sending

Cause: Encountered error while obtaining recipient certificate for sending request.

Action: Must provide valid recipient certificate, or recipient alias for client to send request with message protection.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00165: Creating recipient certificate from base64 encoded string: {0} failed.

Cause: Encountered error while creating recipient certificate from base64 encoded string.

Action: Must provide valid certificate in valid base64 encoded string.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00165: Creating recipient certificate from base64 encoded string: {0} failed.

Cause: Encountered error while creating recipient certificate from base64 encoded string.

Action: Must provide valid certificate in valid base64 encoded string.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00166: Extract certificate from saved ReplyTo header failed.

Cause: X509Certificate within ReplyTo header element might be invalid.

Action: Ensure that cert. insertion, ReplyTo header serialization/deserializaton to JMS queue are all working properly.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00166: Extract certificate from saved ReplyTo header failed.

Cause: X509Certificate within ReplyTo header element might be invalid.

Action: Ensure that cert. insertion, ReplyTo header serialization/deserializaton to JMS queue are all working properly.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00167: Actual Hostname {0} and Hostname retrieved from Certificate {1} do not match

Cause: HostName verification of certificate retrieved from WSDL failed

Action: Either ensure that the Subject Dn matches the Hostname of the Service or disable the HostName Verification check
Level: 1

Type: ERROR

Impact: Security

WSM-00167: Actual Hostname {0} and Hostname retrieved from Certificate {1} do not match

Cause: HostName verification of certificate retrieved from WSDL failed

Action: Either ensure that the Subject Dn matches the Hostname of the Service or disable the HostName Verification check
Level: 1

Type: ERROR

Impact: Security

WSM-00168: Unable to extract X509Certificate from WSDL Definition Object as WSDL definition Object is unavailable

Cause: WSDL definition required for extraction of X509Certificate not available

Action: Ensure that WSDL Definition Object is available from the MessageContext
Level: 1

Type: ERROR

Impact: Security

WSM-00168: Unable to extract X509Certificate from WSDL Definition Object as WSDL definition Object is unavailable

Cause: WSDL definition required for extraction of X509Certificate not available

Action: Ensure that WSDL Definition Object is available from the MessageContext
Level: 1

Type: ERROR

Impact: Security

WSM-00169: Error decrypting the request message.

Cause: The request message could not be decrypted using the key specified for decryption.

Action: Ensure that the key used for decryption is same as the one used for encryption.
Level: 1

Type: ERROR

Impact: Security

WSM-00169: Error decrypting the request message.

Cause: The request message could not be decrypted using the key specified for decryption.

Action: Ensure that the key used for decryption is same as the one used for encryption.
Level: 1

Type: ERROR

Impact: Security

WSM-00170: There are no assertions available under the ExactlyOne policy operator.

Cause: There are no assertions under ExactlyOne policy operator.

Action: Ensure that one or more security assertions are kept under ExactlyOne policy operator.
Level: 1

Type: ERROR

Impact: Security

WSM-00170: There are no assertions available under the ExactlyOne policy operator.

Cause: There are no assertions under ExactlyOne policy operator.

Action: Ensure that one or more security assertions are kept under ExactlyOne policy operator.
Level: 1

Type: ERROR

Impact: Security

WSM-00171: A client policy contains an ExactlyOne policy operator.

Cause: A client policy contained an ExactlyOne policy operator.

Action: Remove the ExactlyOne policy operator or switch to a service binding.
Level: 1

Type: ERROR

Impact: Security

WSM-00171: A client policy contains an ExactlyOne policy operator.

Cause: A client policy contained an ExactlyOne policy operator.

Action: Remove the ExactlyOne policy operator or switch to a service binding.
Level: 1

Type: ERROR

Impact: Security

WSM-00172: A generic policy contains an ExactlyOne policy operator.

Cause: A generic policy contained an ExactlyOne policy operator.

Action: Remove the ExactlyOne policy operator or switch to a service binding.
Level: 1

Type: ERROR

Impact: Security

WSM-00172: A generic policy contains an ExactlyOne policy operator.

Cause: A generic policy contained an ExactlyOne policy operator.

Action: Remove the ExactlyOne policy operator or switch to a service binding.
Level: 1

Type: ERROR

Impact: Security

WSM-00173: A policy contains more than one ExactlyOne policy operator.

Cause: A policy contained more than one ExactlyOne policy operator.

Action: Remove the additional ExactlyOne policy operators.
Level: 1

Type: ERROR

Impact: Security

WSM-00173: A policy contains more than one ExactlyOne policy operator.

Cause: A policy contained more than one ExactlyOne policy operator.

Action: Remove the additional ExactlyOne policy operators.
Level: 1

Type: ERROR

Impact: Security

WSM-00174: A policy contains a nested ExactlyOne policy operator.

Cause: A policy contained a nested ExactlyOne policy operator.

Action: Remove the nested ExactlyOne policy operators.
Level: 1

Type: ERROR

Impact: Security

WSM-00174: A policy contains a nested ExactlyOne policy operator.

Cause: A policy contained a nested ExactlyOne policy operator.

Action: Remove the nested ExactlyOne policy operators.
Level: 1

Type: ERROR

Impact: Security

WSM-00175: Recipient Certificate for async callback client is not found under the ReplyTo element in async callback client message context

Cause: Recipient cert. for async callback client is not available from message context.

Action: Ensure that original async client has public encryption certificate configured and is inserted into the ReplyTo header or the original async request. Also ensure that the original ReplyTo header along with client encryption certification is preserved and restored to the callback client message context.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00175: Recipient Certificate for async callback client is not found under the ReplyTo element in async callback client message context

Cause: Recipient cert. for async callback client is not available from message context.

Action: Ensure that original async client has public encryption certificate configured and is inserted into the ReplyTo header or the original async request. Also ensure that the original ReplyTo header along with client encryption certification is preserved and restored to the callback client message context.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00176: The mapped long name(s) for property {0} is null, the property might not be available for client programmatic override. Make sure it is indeed the intension, otherwise, add a mapping to map ConfigOverrideMapping.

Cause: The config override property does not have a corresponding long name mapping

Action: Make sure this is indeed intended, otherwise, add a mapping to the ConfigOverrideMapping.
Level: 1

Type: WARNING

Impact: Configuration

WSM-00176: The mapped long name(s) for property {0} is null, the property might not be available for client programmatic override. Make sure it is indeed the intension, otherwise, add a mapping to map ConfigOverrideMapping.

Cause: The config override property does not have a corresponding long name mapping

Action: Make sure this is indeed intended, otherwise, add a mapping to the ConfigOverrideMapping.
Level: 1

Type: WARNING

Impact: Configuration

WSM-00177: The CSF key provided by the user is not present in the credential store. So using the default key is being used.

Cause: The CSF key provided by the user is not present in the credential store

Action: Provide a valid key. Till then the default key will be used.
Level: 1

Type: WARNING

Impact: Security

WSM-00177: The CSF key provided by the user is not present in the credential store. So using the default key is being used.

Cause: The CSF key provided by the user is not present in the credential store

Action: Provide a valid key. Till then the default key will be used.
Level: 1

Type: WARNING

Impact: Security

WSM-00178: Public key not found for SAML signature verification.

Cause: Public key not found for SAML signature verification

Action: Ensure that public key is present in Security header which is reqruied For SAML signature verification
Level: 1

Type: WARNING

Impact: Configuration

WSM-00178: Public key not found for SAML signature verification.

Cause: Public key not found for SAML signature verification

Action: Ensure that public key is present in Security header which is reqruied For SAML signature verification
Level: 1

Type: WARNING

Impact: Configuration

WSM-00179: SAML assertion issuer name is invalid.

Cause: SAML assertion issuer name is invalid.

Action: Check to see that the overridden SAML trused issuers has SAML assertion issuer name.
Level: 1

Type: ERROR

Impact: Security

WSM-00179: SAML assertion issuer name is invalid.

Cause: SAML assertion issuer name is invalid.

Action: Check to see that the overridden SAML trused issuers has SAML assertion issuer name.
Level: 1

Type: ERROR

Impact: Security

WSM-00180: The trust version {0} is not supported for policy advertisement, hence ignored. The default trust version {1} is advertised.

Cause: The trust version specified in the policy is not supported.

Action: Modify the policy with a supported trust version.
Level: 1

Type: WARNING

Impact: Configuration

WSM-00180: The trust version {0} is not supported for policy advertisement, hence ignored. The default trust version {1} is advertised.

Cause: The trust version specified in the policy is not supported.

Action: Modify the policy with a supported trust version.
Level: 1

Type: WARNING

Impact: Configuration

WSM-00181: A policy issued-token attributes require-internal-reference and require-external-reference both are false, one of them has to be true.

Cause: A policy issued-token attribute require-internal-reference and require-external-reference can not both be false.

Action: At least one of the attribute require-internal-reference and require-external-reference must be set to true
Level: 1

Type: ERROR

Impact: Configuration

WSM-00181: A policy issued-token attributes require-internal-reference and require-external-reference both are false, one of them has to be true.

Cause: A policy issued-token attribute require-internal-reference and require-external-reference can not both be false.

Action: At least one of the attribute require-internal-reference and require-external-reference must be set to true
Level: 1

Type: ERROR

Impact: Configuration

WSM-00182: A policy request-security-token-template element attribute token-type has an unsupported value: {0}

Cause: A policy request-security-token-template element contains a token-type that is not supported.

Action: Check documentation for supported token-type
Level: 1

Type: ERROR

Impact: Configuration

WSM-00182: A policy request-security-token-template element attribute token-type has an unsupported value: {0}

Cause: A policy request-security-token-template element contains a token-type that is not supported.

Action: Check documentation for supported token-type
Level: 1

Type: ERROR

Impact: Configuration

WSM-00183: A policy request-security-token-template element attribute algorithm-suite has a value: {0} which does not match to that of msg-security: {1}, change it to match {1}.

Cause: A policy request-security-token-template element contains an algorithm-suite value that does not match to that of msg-security.

Action: Change the algorithm-suite attribute value to match exactly the one in msg-security
Level: 1

Type: ERROR

Impact: Configuration

WSM-00183: A policy request-security-token-template element attribute algorithm-suite has a value: {0} which does not match to that of msg-security: {1}, change it to match {1}.

Cause: A policy request-security-token-template element contains an algorithm-suite value that does not match to that of msg-security.

Action: Change the algorithm-suite attribute value to match exactly the one in msg-security
Level: 1

Type: ERROR

Impact: Configuration

WSM-00184: An attribute trust-version has an unsupported version: {0}

Cause: A policy contains an unsupported WS-TRUST version.

Action: Check documentation for supported WS-TRUST version
Level: 1

Type: ERROR

Impact: Configuration

WSM-00184: An attribute trust-version has an unsupported version: {0}

Cause: A policy contains an unsupported WS-TRUST version.

Action: Check documentation for supported WS-TRUST version
Level: 1

Type: ERROR

Impact: Configuration

WSM-00185: Attribute require-client-entropy and require-server-entropy can not both be set to false, at lease one of them must be set to true.

Cause: A policy can not have both require-client-entropy and require-server-entropy attributes set to false.

Action: At lease set one of them to true
Level: 1

Type: ERROR

Impact: Configuration

WSM-00185: Attribute require-client-entropy and require-server-entropy can not both be set to false, at lease one of them must be set to true.

Cause: A policy can not have both require-client-entropy and require-server-entropy attributes set to false.

Action: At lease set one of them to true
Level: 1

Type: ERROR

Impact: Configuration

WSM-00186: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}

Cause: A policy request-security-token-template key-type attribute value is not set to the expected Bearer.

Action: Set the attribute value to the expected
Level: 1

Type: ERROR

Impact: Configuration

WSM-00186: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}

Cause: A policy request-security-token-template key-type attribute value is not set to the expected Bearer.

Action: Set the attribute value to the expected
Level: 1

Type: ERROR

Impact: Configuration

WSM-00187: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}

Cause: A Bearer policy request-security-token-template key-type attribute value is not set to the expected Symmetric or Public.

Action: Set the attribute value to one of the expeted value Symmetric or Public
Level: 1

Type: ERROR

Impact: Configuration

WSM-00187: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}

Cause: A Bearer policy request-security-token-template key-type attribute value is not set to the expected Symmetric or Public.

Action: Set the attribute value to one of the expeted value Symmetric or Public
Level: 1

Type: ERROR

Impact: Configuration

WSM-00188: STS Trust Config policy attribute port-uri has invalid value "{0}", it must be not null, not empty and in the format of http(s)://host:port/sts-service

Cause: STS trust config attribute port-uri is either null, empty or not in the format of "http(s)://host:port/sts-service-name".

Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service"
Level: 1

Type: ERROR

Impact: Configuration

WSM-00188: STS Trust Config policy attribute port-uri has invalid value "{0}", it must be not null, not empty and in the format of http(s)://host:port/sts-service

Cause: STS trust config attribute port-uri is either null, empty or not in the format of "http(s)://host:port/sts-service-name".

Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service"
Level: 1

Type: ERROR

Impact: Configuration

WSM-00189: STS Trust Config policy attribute port-endpoint has invalid value "{0}", it must be not empty and in the format of target-namespace#wsdl.endpoint(service-name/port-name)

Cause: STS trust config attribute port-endpoint is either empty or not in the format of "target-namespace#wsdl.endpoint(service-name/port-name)".

Action: Provide valid attribute value which is in the format of "target-namespace#wsdl.endpoint(service-name/port-name)"
Level: 1

Type: ERROR

Impact: Configuration

WSM-00189: STS Trust Config policy attribute port-endpoint has invalid value "{0}", it must be not empty and in the format of target-namespace#wsdl.endpoint(service-name/port-name)

Cause: STS trust config attribute port-endpoint is either empty or not in the format of "target-namespace#wsdl.endpoint(service-name/port-name)".

Action: Provide valid attribute value which is in the format of "target-namespace#wsdl.endpoint(service-name/port-name)"
Level: 1

Type: ERROR

Impact: Configuration

WSM-00190: STS Trust Config policy attribute policy-reference-uri can not have empty value.

Cause: The value of STS trust config attribute policy-reference-uri is empty or not in the URI format

Action: Specify value for attribute policy-reference-uri
Level: 1

Type: ERROR

Impact: Configuration

WSM-00190: STS Trust Config policy attribute policy-reference-uri can not have empty value.

Cause: The value of STS trust config attribute policy-reference-uri is empty or not in the URI format

Action: Specify value for attribute policy-reference-uri
Level: 1

Type: ERROR

Impact: Configuration

WSM-00191: STS Trust Config policy attribute sts-keystore-recipient-alias can not have null or empty value.

Cause: The value of STS trust config attribute sts-keystore-recipient-alias is null or empty

Action: Specify a non null or empty value for attribute sts-keystore-recipient-alias
Level: 1

Type: ERROR

Impact: Configuration

WSM-00191: STS Trust Config policy attribute sts-keystore-recipient-alias can not have null or empty value.

Cause: The value of STS trust config attribute sts-keystore-recipient-alias is null or empty

Action: Specify a non null or empty value for attribute sts-keystore-recipient-alias
Level: 1

Type: ERROR

Impact: Configuration

WSM-00192: Kerberos name identifier format is not supported for SAML 1.1 token.

Cause: Kerberos name identifier format is not supported for SAML 1.1 token.

Action: Kerberos name identifier format is only for SAML 2.0 token, use other name identifier formats.
Level: 1

Type: ERROR

Impact: Security

WSM-00192: Kerberos name identifier format is not supported for SAML 1.1 token.

Cause: Kerberos name identifier format is not supported for SAML 1.1 token.

Action: Kerberos name identifier format is only for SAML 2.0 token, use other name identifier formats.
Level: 1

Type: ERROR

Impact: Security

WSM-00193: Security policy contains NULL or empty value for signed-element local name or namespace.

Cause: Security policy contains NULL or empty value for signed-element local name or namespace.

Action: Signed-element local name or namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00193: Security policy contains NULL or empty value for signed-element local name or namespace.

Cause: Security policy contains NULL or empty value for signed-element local name or namespace.

Action: Signed-element local name or namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00194: Security policy contains NULL or empty value for signed-part header namespace.

Cause: Security policy contains NULL or empty value for signed-part header namespace.

Action: Signed-part header namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00194: Security policy contains NULL or empty value for signed-part header namespace.

Cause: Security policy contains NULL or empty value for signed-part header namespace.

Action: Signed-part header namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00195: Security context for derived key unknown (cannot determine the base symmetric key).

Cause: Security context for derived key unknown (cannot determine the base symmetric key).

Action: DerivedKeyToken should include SecurityReferenceToken (can only be empty in responses where the message context includes the base key).
Level: 1

Type: ERROR

Impact: Security

WSM-00195: Security context for derived key unknown (cannot determine the base symmetric key).

Cause: Security context for derived key unknown (cannot determine the base symmetric key).

Action: DerivedKeyToken should include SecurityReferenceToken (can only be empty in responses where the message context includes the base key).
Level: 1

Type: ERROR

Impact: Security

WSM-00196: Unable to resolve base key referenced in DerivedKeyToken.

Cause: Unable to resolve base key referenced in DerivedKeyToken.

Action: Ensure the SecurityTokenReference in the DerivedKeyToken specifies a valid base key within the security context.
Level: 1

Type: ERROR

Impact: Security

WSM-00196: Unable to resolve base key referenced in DerivedKeyToken.

Cause: Unable to resolve base key referenced in DerivedKeyToken.

Action: Ensure the SecurityTokenReference in the DerivedKeyToken specifies a valid base key within the security context.
Level: 1

Type: ERROR

Impact: Security

WSM-00197: Unsupported SecurityTokenReference type for DerivedKeyToken.

Cause: Unsupported SecurityTokenReference type for DerivedKeyToken.

Action: Ensure the SecurityTokenReference in the DerivedKeyToken is one of the supported types.
Level: 1

Type: ERROR

Impact: Security

WSM-00197: Unsupported SecurityTokenReference type for DerivedKeyToken.

Cause: Unsupported SecurityTokenReference type for DerivedKeyToken.

Action: Ensure the SecurityTokenReference in the DerivedKeyToken is one of the supported types.
Level: 1

Type: ERROR

Impact: Security

WSM-00198: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.

Cause: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.

Action: The value of the EncryptedKeySHA1 should match an encrypted key in the security context.
Level: 1

Type: ERROR

Impact: Security

WSM-00198: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.

Cause: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.

Action: The value of the EncryptedKeySHA1 should match an encrypted key in the security context.
Level: 1

Type: ERROR

Impact: Security

WSM-00199: Unsupported key identifier type "{0}" in security token reference.

Cause: Unsupported key identifier type in security token reference.

Action: Use only of the supported key idetifier types in the security token.
Level: 1

Type: ERROR

Impact: Security

WSM-00199: Unsupported key identifier type "{0}" in security token reference.

Cause: Unsupported key identifier type in security token reference.

Action: Use only of the supported key idetifier types in the security token.
Level: 1

Type: ERROR

Impact: Security

WSM-00200: Exception encountered while checking compliance; returning false.

Cause: Exception encountered while checking compliance; returning false.

Action: Check log for exception details.
Level: 1

Type: ERROR

Impact: Security

WSM-00200: Exception encountered while checking compliance; returning false.

Cause: Exception encountered while checking compliance; returning false.

Action: Check log for exception details.
Level: 1

Type: ERROR

Impact: Security

WSM-00201: There are no <EncryptedKey> elements in the request.

Cause: There are no <EncryptedKey> elements in the request.

Action: The request should have an <EncryptedKey> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00201: There are no <EncryptedKey> elements in the request.

Cause: There are no <EncryptedKey> elements in the request.

Action: The request should have an <EncryptedKey> element.
Level: 1

Type: ERROR

Impact: Security

WSM-00202: Proof key type is invalid, valid vaues are null, public, symmetric.

Cause: The value of ketype is invalid for SAML Issued Token Policy , valid values are null (no proof key), public, symmetric

Action: Specify valid value for keytype based on the policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00202: Proof key type is invalid, valid vaues are null, public, symmetric.

Cause: The value of ketype is invalid for SAML Issued Token Policy , valid values are null (no proof key), public, symmetric

Action: Specify valid value for keytype based on the policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00203: Invalid OPSS Trust Service

Cause: OPSS TrustService is empty or null

Action: Configure Trust Service in OPSS
Level: 1

Type: ERROR

Impact: Configuration

WSM-00203: Invalid OPSS Trust Service

Cause: OPSS TrustService is empty or null

Action: Configure Trust Service in OPSS
Level: 1

Type: ERROR

Impact: Configuration

WSM-00204: Invlaid issued token from trust token exchange

Cause: Issued token is null

Action: Check Logs and correct any errors during issuance
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00204: Invlaid issued token from trust token exchange

Cause: Issued token is null

Action: Check Logs and correct any errors during issuance
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00205: Proof key type is invalid, valid value is bearer

Cause: The value of ketype is invalid for SAML Bearer Issued Token Policy , valid value is bearer

Action: Specify bearer as the key type for this policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00205: Proof key type is invalid, valid value is bearer

Cause: The value of ketype is invalid for SAML Bearer Issued Token Policy , valid value is bearer

Action: Specify bearer as the key type for this policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00206: Requester credentials for authenticating to STS are invalid

Cause: Requester Credentials required for autenticating to STS are missing

Action: Configure sts.auth.user.csf.key or sts.auth.x509.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00206: Requester credentials for authenticating to STS are invalid

Cause: Requester Credentials required for autenticating to STS are missing

Action: Configure sts.auth.user.csf.key or sts.auth.x509.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00207: Assymetric proof key is invalid

Cause: Assymetric proof key is invalid

Action: Configure sts.auth.x509.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00207: Assymetric proof key is invalid

Cause: Assymetric proof key is invalid

Action: Configure sts.auth.x509.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00208: STS On behalf of user is invalid

Cause: STS On behalf of user is invalid

Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00208: STS On behalf of user is invalid

Cause: STS On behalf of user is invalid

Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00209: Permission{0} required to switch the identity not granted to the resource. {1}

Cause: Permission required to switch the identity not granted

Action: Grant Permission for identity switching to the codesource.
Level: 1

Type: ERROR

Impact: Security

WSM-00209: Permission{0} required to switch the identity not granted to the resource. {1}

Cause: Permission required to switch the identity not granted

Action: Grant Permission for identity switching to the codesource.
Level: 1

Type: ERROR

Impact: Security

WSM-00210: Client is unable to find actual webservice endpoint to set in appliesTo

Cause: Client requires appliesTo and unable to find the actual webservice endpoint URL

Action: Chenck if agent binding ws port ID , service name and port name in log file
Level: 1

Type: ERROR

Impact: Configuration

WSM-00210: Client is unable to find actual webservice endpoint to set in appliesTo

Cause: Client requires appliesTo and unable to find the actual webservice endpoint URL

Action: Chenck if agent binding ws port ID , service name and port name in log file
Level: 1

Type: ERROR

Impact: Configuration

WSM-00211: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid

Cause: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid

Action: Check the asymmetric key algorithm
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00211: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid

Cause: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid

Action: Check the asymmetric key algorithm
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00212: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid

Cause: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid

Action: Check if sts.auth.x509.csf.key is configured correctly in issued token client policy
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00212: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid

Cause: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid

Action: Check if sts.auth.x509.csf.key is configured correctly in issued token client policy
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00213: Unable to parse SOAP message sent by STS

Cause: Unable to parse SOAP message sent by STS

Action: Check if message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00213: Unable to parse SOAP message sent by STS

Cause: Unable to parse SOAP message sent by STS

Action: Check if message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00214: Unable to parse RequestSecurityTokenRespnseCollection

Cause: Unable to parse RequestSecurityTokenResponseCollection

Action: Check if RequestSecurityTokenResponseCollection message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00214: Unable to parse RequestSecurityTokenRespnseCollection

Cause: Unable to parse RequestSecurityTokenResponseCollection

Action: Check if RequestSecurityTokenResponseCollection message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00215: Unable to parse STSTrustConfig

Cause: Unable to parse STSTrustConfig

Action: Check if STSTrustConfig is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00215: Unable to parse STSTrustConfig

Cause: Unable to parse STSTrustConfig

Action: Check if STSTrustConfig is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00216: Unable to create SOAP RequestSecurityToken message

Cause: Unable to create SOAP RequestSecurityToken message

Action: Failure in creating SOAP RequestSecurityToken message, check log files
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00216: Unable to create SOAP RequestSecurityToken message

Cause: Unable to create SOAP RequestSecurityToken message

Action: Failure in creating SOAP RequestSecurityToken message, check log files
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00217: STS endpoint URL or WSDL URL (if configured) is invalid

Cause: STS endpoit URL is invalid

Action: Check if STS endpoint URL is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00217: STS endpoint URL or WSDL URL (if configured) is invalid

Cause: STS endpoit URL is invalid

Action: Check if STS endpoint URL is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00218: Security token returned by STS is null

Cause: Security token returned by STS is null

Action: Check if RSTR message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00218: Security token returned by STS is null

Cause: Security token returned by STS is null

Action: Check if RSTR message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00219: Proof token returned by STS is null

Cause: Proof token returned by STS is null

Action: Check if RSTR message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00219: Proof token returned by STS is null

Cause: Proof token returned by STS is null

Action: Check if RSTR message sent by STS is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00220: Invalid proof token type, valid values are computedKey and BinarySecret

Cause: Invalid proof token type, valid values are computedKey and BinarySecret

Action: Check the proof token type, valid values are computedKey and BinarySecret
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00220: Invalid proof token type, valid values are computedKey and BinarySecret

Cause: Invalid proof token type, valid values are computedKey and BinarySecret

Action: Check the proof token type, valid values are computedKey and BinarySecret
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00221: Computed key in RSTR message sent by STS is invalid

Cause: Computed key in RSTR message sent by STS is invalid

Action: Check the computed key in RSTR message sent by STS
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00221: Computed key in RSTR message sent by STS is invalid

Cause: Computed key in RSTR message sent by STS is invalid

Action: Check the computed key in RSTR message sent by STS
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00222: Computed key algorithm in RSTR message sent by STS is invalid}

Cause: Computed key algorithm in RSTR message sent by STS is invalid, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1

Action: Check the computed key in RSTR message sent by STS, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00222: Computed key algorithm in RSTR message sent by STS is invalid}

Cause: Computed key algorithm in RSTR message sent by STS is invalid, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1

Action: Check the computed key in RSTR message sent by STS, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00223: Request type is invalid, valid value is issue

Cause: Request type invalid, valid value is issue

Action: Check request type in response sent by STS
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00223: Request type is invalid, valid value is issue

Cause: Request type invalid, valid value is issue

Action: Check request type in response sent by STS
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00224: User credentials of the user on behalf of whom the token is to be issued is missing

Cause: User credentials of the user on behalf of whom the token is to be issued is missing

Action: Check on.behalf.of property in issued token policy. If its set to true then either subject or sts.auth.on.behalf.of.csf-key property needs to be present
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00224: User credentials of the user on behalf of whom the token is to be issued is missing

Cause: User credentials of the user on behalf of whom the token is to be issued is missing

Action: Check on.behalf.of property in issued token policy. If its set to true then either subject or sts.auth.on.behalf.of.csf-key property needs to be present
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00225: STS On behalf of user password is invalid

Cause: STS On behalf of user password is invalid

Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00225: STS On behalf of user password is invalid

Cause: STS On behalf of user password is invalid

Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy
Level: 1

Type: ERROR

Impact: Configuration

WSM-00226: Security policy contains NULL or empty value for encrypted-element local name or namespace.

Cause: Security policy contains NULL or empty value for encrypted-element local name or namespace.

Action: Encrypted-element local name or namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00226: Security policy contains NULL or empty value for encrypted-element local name or namespace.

Cause: Security policy contains NULL or empty value for encrypted-element local name or namespace.

Action: Encrypted-element local name or namespace must not be null or empty.
Level: 1

Type: ERROR

Impact: Security

WSM-00227: Could not resolve key to use for decryption.

Cause: Could not resolve key to use for decryption.

Action: Ensure request contains all the information necessary to succesfully resolve decryption key.
Level: 1

Type: ERROR

Impact: Security

WSM-00227: Could not resolve key to use for decryption.

Cause: Could not resolve key to use for decryption.

Action: Ensure request contains all the information necessary to succesfully resolve decryption key.
Level: 1

Type: ERROR

Impact: Security

WSM-00228: Oracle system user is missing in identity store

Cause: Could not find oracle system user .

Action: Check if OracleSystemUser exists in identity store
Level: 1

Type: ERROR

Impact: Configuration

WSM-00228: Oracle system user is missing in identity store

Cause: Could not find oracle system user .

Action: Check if OracleSystemUser exists in identity store
Level: 1

Type: ERROR

Impact: Configuration

WSM-00229: jndi.lookup.csf.key missing in policy-accessor-config

Cause: Could not find valid jndi.lookup.csf.key in policy-accessor-config.xml .

Action: Check jndi.lookup.csf.key is configured correclty in policy-accessor-config.xml
Level: 1

Type: ERROR

Impact: Configuration

WSM-00229: jndi.lookup.csf.key missing in policy-accessor-config

Cause: Could not find valid jndi.lookup.csf.key in policy-accessor-config.xml .

Action: Check jndi.lookup.csf.key is configured correclty in policy-accessor-config.xml
Level: 1

Type: ERROR

Impact: Configuration

WSM-00230: Cannot find service information from WSDL {0}

Cause: Cannot find service information from WSDL

Action: Check the service information in the WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00230: Cannot find service information from WSDL {0}

Cause: Cannot find service information from WSDL

Action: Check the service information in the WSDL
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00231: Cannot find client compatible policy for STS {0}, port name {1}

Cause: Cannot find compatible client policy for STS invocation

Action: Check if policy store has compatible client policy
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00231: Cannot find client compatible policy for STS {0}, port name {1}

Cause: Cannot find compatible client policy for STS invocation

Action: Check if policy store has compatible client policy
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00232: Failed to create dynamic STS policy

Cause: Failed to create dynamic STS policy

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00232: Failed to create dynamic STS policy

Cause: Failed to create dynamic STS policy

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00233: STS WSDL URI {0} is invalid

Cause: STS trust config attribute wsdl-uri is not in the format of "http(s)://host:port/sts-service?wsdl".

Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service?wsdl
Level: 1

Type: ERROR

Impact: Configuration

WSM-00233: STS WSDL URI {0} is invalid

Cause: STS trust config attribute wsdl-uri is not in the format of "http(s)://host:port/sts-service?wsdl".

Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service?wsdl
Level: 1

Type: ERROR

Impact: Configuration

WSM-00234: The <saml:Assertion> element of version {0} is missing in the security header.

Cause: Saml assertion with specific version e.g. 1.1, or 2.0 etc. is missing. in the received message

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00234: The <saml:Assertion> element of version {0} is missing in the security header.

Cause: Saml assertion with specific version e.g. 1.1, or 2.0 etc. is missing. in the received message

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00235: Failed to initialize dispatcher

Cause: Failed to initialize dispatcher for client to STS communication

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00235: Failed to initialize dispatcher

Cause: Failed to initialize dispatcher for client to STS communication

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00236: Keystore name property value was not set through JPS configuration

Cause: Keystore name property value was not set through JPS configuration.

Action: Make sure that the value is provided for keystore name through JPS configuration.
Level: 1

Type: ERROR

Impact: Security

WSM-00236: Keystore name property value was not set through JPS configuration

Cause: Keystore name property value was not set through JPS configuration.

Action: Make sure that the value is provided for keystore name through JPS configuration.
Level: 1

Type: ERROR

Impact: Security

WSM-00237: FKS keystore with stripeName {0}, keystoreName {1} can not be loaded due to {2}.

Cause: The following FKS keystore-related configuration properties may not be valid:keystore.type, keystore.pass, keystore.name. Also, check permissions on the keystore.

Action: Verify the configuration properties mentioned above and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00237: FKS keystore with stripeName {0}, keystoreName {1} can not be loaded due to {2}.

Cause: The following FKS keystore-related configuration properties may not be valid:keystore.type, keystore.pass, keystore.name. Also, check permissions on the keystore.

Action: Verify the configuration properties mentioned above and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00238: Unable to read FKS keystore. Grant necessary permission to read FKS keystore, stripe name {0} and keystore name {1}

Cause: FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that necessary permission to read FKS keystore is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00238: Unable to read FKS keystore. Grant necessary permission to read FKS keystore, stripe name {0} and keystore name {1}

Cause: FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that necessary permission to read FKS keystore is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00239: FKS trust store can not be loaded, ensure that necessary permissions are granted.

Cause: FKS trust store can not be loaded, probably necessary permissions are not granted.

Action: Ensure that necessary permission to read FKS trust store is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00239: FKS trust store can not be loaded, ensure that necessary permissions are granted.

Cause: FKS trust store can not be loaded, probably necessary permissions are not granted.

Action: Ensure that necessary permission to read FKS trust store is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00240: FKS trust store is NULL, ensure that FKS system trust store exist.

Cause: FKS trust store is NULL, may be it doesn't exists or probably necessary permissions are not granted.

Action: Ensure that FKS trust store exists in system stripe and permissions are granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00240: FKS trust store is NULL, ensure that FKS system trust store exist.

Cause: FKS trust store is NULL, may be it doesn't exists or probably necessary permissions are not granted.

Action: Ensure that FKS trust store exists in system stripe and permissions are granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00241: Failure retrieving FKS trust store aliases.

Cause: FKS trust store may have not been initialized.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00241: Failure retrieving FKS trust store aliases.

Cause: FKS trust store may have not been initialized.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00242: The certificates cannot be retrieved from the trust store.

Cause: Failure occurred while trying to retrieve certificate from trust store.

Action: Use a valid alias for the certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00242: The certificates cannot be retrieved from the trust store.

Cause: Failure occurred while trying to retrieve certificate from trust store.

Action: Use a valid alias for the certificate and retry the operation.
Level: 1

Type: ERROR

Impact: Security

WSM-00243: Unable to read key from FKS keystore. Grant necessary permission to read alias {2} from FKS keystore, stripe name {0} and keystore name {1}

Cause: Unable to read key from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00243: Unable to read key from FKS keystore. Grant necessary permission to read alias {2} from FKS keystore, stripe name {0} and keystore name {1}

Cause: Unable to read key from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00244: Unable to read certificate from FKS keystore. Grant necessary permission to read certificate alias {2} from FKS keystore, stripe name {0} and keystore name {1}

Cause: Unable to read certificate from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that alias exists in keystore and necessary permission to read certificate alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00244: Unable to read certificate from FKS keystore. Grant necessary permission to read certificate alias {2} from FKS keystore, stripe name {0} and keystore name {1}

Cause: Unable to read certificate from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.

Action: Ensure that alias exists in keystore and necessary permission to read certificate alias is granted.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00245: Failure retrieving FKS key store aliases.

Cause: Unable to list alias from FKS key store.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00245: Failure retrieving FKS key store aliases.

Cause: Unable to list alias from FKS key store.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-00246: Failure retrieving IssuedTokenAssertion from advertised policy.

Cause: Possibilly there is a failure in parsing the advertised policy

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-00246: Failure retrieving IssuedTokenAssertion from advertised policy.

Cause: Possibilly there is a failure in parsing the advertised policy

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-00247: Failed to sign with RSA Key Pair

Cause: Failed to sign with RSA Key Pair

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Security

WSM-00247: Failed to sign with RSA Key Pair

Cause: Failed to sign with RSA Key Pair

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Security

WSM-00248: Attesting entity attribute {0} is unsupported.

Cause: Unsupported attesting entity attribute is used

Action: Attesting entity attribute must be DN.
Level: 1

Type: ERROR

Impact: Security

WSM-00248: Attesting entity attribute {0} is unsupported.

Cause: Unsupported attesting entity attribute is used

Action: Attesting entity attribute must be DN.
Level: 1

Type: ERROR

Impact: Security

WSM-00249: SAML token DN validation failed for SAML assertion signer DN {0}.

Cause: SAML token DN list validation failed.

Action: Assertion signer DN is not present in trusted DN list, if DN is valid then add it to trusted DNs list.
Level: 1

Type: ERROR

Impact: Security

WSM-00249: SAML token DN validation failed for SAML assertion signer DN {0}.

Cause: SAML token DN list validation failed.

Action: Assertion signer DN is not present in trusted DN list, if DN is valid then add it to trusted DNs list.
Level: 1

Type: ERROR

Impact: Security

WSM-00250: Unable to find an implementation class for {0}.

Cause: Unable to find an implementation class for 'javax.el.ExpressionFactory'.

Action: Make sure that the implementation class for 'javax.el.ExpressionFactory' is available in the classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00250: Unable to find an implementation class for {0}.

Cause: Unable to find an implementation class for 'javax.el.ExpressionFactory'.

Action: Make sure that the implementation class for 'javax.el.ExpressionFactory' is available in the classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00251: Failed to create an instance of {0}.

Cause: Failed to create an instance of the javax.el.ExpressionFactory implementation class.

Action: Make sure that the javax.el.ExpressionFactory implementation class can be instantiated.
Level: 1

Type: ERROR

Impact: Security

WSM-00251: Failed to create an instance of {0}.

Cause: Failed to create an instance of the javax.el.ExpressionFactory implementation class.

Action: Make sure that the javax.el.ExpressionFactory implementation class can be instantiated.
Level: 1

Type: ERROR

Impact: Security

WSM-00252: Failed to evaluate the constraint expression "{0}" due to the exception: {1}

Cause: Failed to evaluate the constraint expression.

Action: Make sure that the constraint expression is valid. Check exception stack trace for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00252: Failed to evaluate the constraint expression "{0}" due to the exception: {1}

Cause: Failed to evaluate the constraint expression.

Action: Make sure that the constraint expression is valid. Check exception stack trace for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00253: The constraint expression "{0}" is not valid. The constraint expression should evaluate to the boolean values.

Cause: The constraint expression is not valid.

Action: Make sure that the constraint expression evaluates to the boolean values.
Level: 1

Type: ERROR

Impact: Security

WSM-00253: The constraint expression "{0}" is not valid. The constraint expression should evaluate to the boolean values.

Cause: The constraint expression is not valid.

Action: Make sure that the constraint expression evaluates to the boolean values.
Level: 1

Type: ERROR

Impact: Security

WSM-00254: The current server time is "{0}", incoming message creation time is "{6}", configured agent expiry is {5} seconds, incoming message expiry is {7} seconds, effective message expiry (minimum of agent expiry and incoming message expiry) is {1} seconds, configured clock skew is {2} seconds. The acceptable time range is "{3}" to "{4}". The incoming message is before/after the acceptable time.

Cause: The incoming message is outside the valid range as allowed by clock skew and expiry times.

Action: Adjust times on servers/clients. Check the allowed clockskew and message expiration time and configure them as required.
Level: 1

Type: ERROR

Impact: Security

WSM-00254: The current server time is "{0}", incoming message creation time is "{6}", configured agent expiry is {5} seconds, incoming message expiry is {7} seconds, effective message expiry (minimum of agent expiry and incoming message expiry) is {1} seconds, configured clock skew is {2} seconds. The acceptable time range is "{3}" to "{4}". The incoming message is before/after the acceptable time.

Cause: The incoming message is outside the valid range as allowed by clock skew and expiry times.

Action: Adjust times on servers/clients. Check the allowed clockskew and message expiration time and configure them as required.
Level: 1

Type: ERROR

Impact: Security

WSM-00256: The property "{0}" is not set. The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2} The properties found in the JPS config are <PropertyName: Value>:- {3}

Cause: The property value is null.

Action: Make sure that the value provided either through policy configuration override, policy binding, or JPS configuration is not null.
Level: 1

Type: ERROR

Impact: Security

WSM-00256: The property "{0}" is not set. The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2} The properties found in the JPS config are <PropertyName: Value>:- {3}

Cause: The property value is null.

Action: Make sure that the value provided either through policy configuration override, policy binding, or JPS configuration is not null.
Level: 1

Type: ERROR

Impact: Security

WSM-00257: Callback class name "{0}" set for SAML certificate validation not found

Cause: Callback class set for SAML certificate validation not found.

Action: Make sure that callback class name is correct and added in classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00257: Callback class name "{0}" set for SAML certificate validation not found

Cause: Callback class set for SAML certificate validation not found.

Action: Make sure that callback class name is correct and added in classpath.
Level: 1

Type: ERROR

Impact: Security

WSM-00258: Callback class name "{0}" set for SAML certificate validation is invalid.

Cause: Callback class set for SAML certificate validation is not valid.

Action: Make sure that callback class correctly extends required class.
Level: 1

Type: ERROR

Impact: Security

WSM-00258: Callback class name "{0}" set for SAML certificate validation is invalid.

Cause: Callback class set for SAML certificate validation is not valid.

Action: Make sure that callback class correctly extends required class.
Level: 1

Type: ERROR

Impact: Security

WSM-00259: SAML certificate validation callback failed. {0}.

Cause: Callback class set for SAML certificate validation failed.

Action: Check the error message for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00259: SAML certificate validation callback failed. {0}.

Cause: Callback class set for SAML certificate validation failed.

Action: Check the error message for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00260: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ. Actual certificate DN={0} and callback cert DN={1}

Cause: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ.

Action: Make sure that client certificate sent over SSL and certificate returned from callback are same.
Level: 1

Type: ERROR

Impact: Security

WSM-00260: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ. Actual certificate DN={0} and callback cert DN={1}

Cause: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ.

Action: Make sure that client certificate sent over SSL and certificate returned from callback are same.
Level: 1

Type: ERROR

Impact: Security

WSM-00261: SAML certificate validation callback failed because certificate returned from callback is NULL.

Cause: Callback class set for SAML certificate validation failed because certificate returned from callback is NULL.

Action: Check callback implementation class for the reason of null certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00261: SAML certificate validation callback failed because certificate returned from callback is NULL.

Cause: Callback class set for SAML certificate validation failed because certificate returned from callback is NULL.

Action: Check callback implementation class for the reason of null certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00262: SAML assertion with confirmation method {0} is missing inside signature.

Cause: SAML assertion is missing inside signature.

Action: Ensure that SAML assertion has required inside signature.
Level: 1

Type: ERROR

Impact: Security

WSM-00262: SAML assertion with confirmation method {0} is missing inside signature.

Cause: SAML assertion is missing inside signature.

Action: Ensure that SAML assertion has required inside signature.
Level: 1

Type: ERROR

Impact: Security

WSM-00263: Failed to create SAML token as 'anonymous' user principal found in Subject.

Cause: Failed to create SAML token as 'anonymous' user principal found in Subject.

Action: Make sure that the subject is created from a valid user.
Level: 1

Type: ERROR

Impact: Security

WSM-00263: Failed to create SAML token as 'anonymous' user principal found in Subject.

Cause: Failed to create SAML token as 'anonymous' user principal found in Subject.

Action: Make sure that the subject is created from a valid user.
Level: 1

Type: ERROR

Impact: Security

WSM-00264: Must Understand check failed for headers: '{0}' in the SOAP message.

Cause: Unprocessed 'mustUnderstand' header element in SOAP message.

Action: Make sure that you have attached security policy at service side.
Level: 1

Type: ERROR

Impact: Security

WSM-00264: Must Understand check failed for headers: '{0}' in the SOAP message.

Cause: Unprocessed 'mustUnderstand' header element in SOAP message.

Action: Make sure that you have attached security policy at service side.
Level: 1

Type: ERROR

Impact: Security

WSM-00265: The Username token is missing in the security header. Ensure that there is a Username token policy attached on the client side. Tokens found in the security header are :- {0}.

Cause: Username token was expected in the security header but was not found.

Action: Username token is missing. Resend request with valid username token.
Level: 1

Type: ERROR

Impact: Security

WSM-00265: The Username token is missing in the security header. Ensure that there is a Username token policy attached on the client side. Tokens found in the security header are :- {0}.

Cause: Username token was expected in the security header but was not found.

Action: Username token is missing. Resend request with valid username token.
Level: 1

Type: ERROR

Impact: Security

WSM-00266: The Kerberos token is missing in the security header.

Cause: Kerberos token was expected in the security header but was not found.

Action: Resend request with valid kerberos token.
Level: 1

Type: ERROR

Impact: Security

WSM-00266: The Kerberos token is missing in the security header.

Cause: Kerberos token was expected in the security header but was not found.

Action: Resend request with valid kerberos token.
Level: 1

Type: ERROR

Impact: Security

WSM-00268: The certificate to be validated is NULL.

Cause: The certficate to be validated is null.

Action: Make sure that the certificate to be validated is not null.
Level: 1

Type: ERROR

Impact: Security

WSM-00268: The certificate to be validated is NULL.

Cause: The certficate to be validated is null.

Action: Make sure that the certificate to be validated is not null.
Level: 1

Type: ERROR

Impact: Security

WSM-00269: There is no trusted certificate found in the trust store.

Cause: Trust store does not have any trusted certificate.

Action: Make sure that the required trusted certificates are present in the trust store.
Level: 1

Type: ERROR

Impact: Security

WSM-00269: There is no trusted certificate found in the trust store.

Cause: Trust store does not have any trusted certificate.

Action: Make sure that the required trusted certificates are present in the trust store.
Level: 1

Type: ERROR

Impact: Security

WSM-00270: The issuer "{0}" is not found in the trust store.

Cause: The issuer certificate is not present in the trust store.

Action: Make sure that the issuer certificate is present in the trust store.
Level: 1

Type: ERROR

Impact: Security

WSM-00270: The issuer "{0}" is not found in the trust store.

Cause: The issuer certificate is not present in the trust store.

Action: Make sure that the issuer certificate is present in the trust store.
Level: 1

Type: ERROR

Impact: Security

WSM-00271: Basic constraints check failed due to the certificate "{0}" is not a CA certificate.

Cause: The certificate is not a CA certificate.

Action: Make sure that the issuer certificate is a CA certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00271: Basic constraints check failed due to the certificate "{0}" is not a CA certificate.

Cause: The certificate is not a CA certificate.

Action: Make sure that the issuer certificate is a CA certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00272: Basic Constraints check failed for the certificate "{0}", since only an end-entity certificate may follow this certificate in the certification path chain.

Cause: Basic Constraints check failed for the issuer certificate.

Action: Make sure that the issuer certificate is a valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00272: Basic Constraints check failed for the certificate "{0}", since only an end-entity certificate may follow this certificate in the certification path chain.

Cause: Basic Constraints check failed for the issuer certificate.

Action: Make sure that the issuer certificate is a valid.
Level: 1

Type: ERROR

Impact: Security

WSM-00273: Failed to verify the issuer "{0}".

Cause: The issuer certificate verification failed.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00273: Failed to verify the issuer "{0}".

Cause: The issuer certificate verification failed.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00274: The certification path for the certificate "{0}" is NULL.

Cause: The certification path is found to be null.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00274: The certification path for the certificate "{0}" is NULL.

Cause: The certification path is found to be null.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00275: The Identity type "{0}" is not suported.

Cause: The Identity type published in the WSDL certificate is not supported.

Action: Make sure that the identity type published in the WSDL certificate is either X509Certificate or supported one.
Level: 1

Type: ERROR

Impact: Security

WSM-00275: The Identity type "{0}" is not suported.

Cause: The Identity type published in the WSDL certificate is not supported.

Action: Make sure that the identity type published in the WSDL certificate is either X509Certificate or supported one.
Level: 1

Type: ERROR

Impact: Security

WSM-00276: Validation failed for the identity published in the WSDL endpoint "{1}". Caused By: {0}

Cause: Validation failed for the Identity published in the WSDL certificate.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00276: Validation failed for the identity published in the WSDL endpoint "{1}". Caused By: {0}

Cause: Validation failed for the Identity published in the WSDL certificate.

Action: Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00277: Endorsing signature is not found in the message. Ensure that a compatible policy is attached at the client side. The security policy "{1}" is attached to the service. Tokens found in the security header are :- {0}.

Cause: Endorsing signature is expected in the message but not found.

Action: Make sure that the endorsing signature is included in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00277: Endorsing signature is not found in the message. Ensure that a compatible policy is attached at the client side. The security policy "{1}" is attached to the service. Tokens found in the security header are :- {0}.

Cause: Endorsing signature is expected in the message but not found.

Action: Make sure that the endorsing signature is included in the message.
Level: 1

Type: ERROR

Impact: Security

WSM-00278: Failed to decrypt the encrypted key due to {1}. Ensure that the client is properly configured with the server certificate. Client should be using this certificate:- {0}.

Cause: An error occurred while decrypting the encrypted key.

Action: Ensure that the client is properly configured with the server's certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00278: Failed to decrypt the encrypted key due to {1}. Ensure that the client is properly configured with the server certificate. Client should be using this certificate:- {0}.

Cause: An error occurred while decrypting the encrypted key.

Action: Ensure that the client is properly configured with the server's certificate.
Level: 1

Type: ERROR

Impact: Security

WSM-00279: The following Fault Message is received at the client side from the service:- {0}. The client side policy is:- {4}. The service endpoint url is:- {3}. Keystore properties:- {1}. Properties found in the message context (Partial list):- {7}. PolicyReference OverrideProperty: {6} Policy configuration properties (some of these may be overridden by the properties passed in the PolicyReference or message context, for details about the order of precedence of properties consult documentation):- {5}. Other related information:- {2}.

Cause: Fault Message received at the client side from the service

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-00279: The following Fault Message is received at the client side from the service:- {0}. The client side policy is:- {4}. The service endpoint url is:- {3}. Keystore properties:- {1}. Properties found in the message context (Partial list):- {7}. PolicyReference OverrideProperty: {6} Policy configuration properties (some of these may be overridden by the properties passed in the PolicyReference or message context, for details about the order of precedence of properties consult documentation):- {5}. Other related information:- {2}.

Cause: Fault Message received at the client side from the service

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-00311: Keystore reloading failed due to {0}

Cause: Reloading of the keystore failed.

Action: Restart the server to load the latest keystore.
Level: 1

Type: ERROR

Impact: Security

WSM-00311: Keystore reloading failed due to {0}

Cause: Reloading of the keystore failed.

Action: Restart the server to load the latest keystore.
Level: 1

Type: ERROR

Impact: Security

WSM-00314: The Xpath transformation of the type "{0}" is not allowed. Only Xpath transformations of the type "{1}" are allowed. To allow all the Xpath transformations, set the property "{2}" to true.

Cause: The Xpath transformation present in the incoming SOAP message is not supported.

Action: Make sure that incoming SOAP message contains only supported Xpath expressions, see the exception stack trace for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00314: The Xpath transformation of the type "{0}" is not allowed. Only Xpath transformations of the type "{1}" are allowed. To allow all the Xpath transformations, set the property "{2}" to true.

Cause: The Xpath transformation present in the incoming SOAP message is not supported.

Action: Make sure that incoming SOAP message contains only supported Xpath expressions, see the exception stack trace for details.
Level: 1

Type: ERROR

Impact: Security

WSM-00315: The details of the keystore {0} removed from the system.

Cause: Removing the keystore details as keystore was replaced with a wrong one.

Action: Replace the keystore with a valid one. After keystore has been replaced, it will be reloaded on next invocation.
Level: 1

Type: ERROR

Impact: Security

WSM-00315: The details of the keystore {0} removed from the system.

Cause: Removing the keystore details as keystore was replaced with a wrong one.

Action: Replace the keystore with a valid one. After keystore has been replaced, it will be reloaded on next invocation.
Level: 1

Type: ERROR

Impact: Security

WSM-00316: The CSF key "{0}" is reserved and can not be used for username credentials. Ensure that the reserved CSF keys {1} and {2} are not used.

Cause: The CSF key being used is reserved and can not be used for username credentials.

Action: Ensure that the reserved CSF keys are not used. Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-00316: The CSF key "{0}" is reserved and can not be used for username credentials. Ensure that the reserved CSF keys {1} and {2} are not used.

Cause: The CSF key being used is reserved and can not be used for username credentials.

Action: Ensure that the reserved CSF keys are not used. Check error logs for more details.
Level: 1

Type: ERROR

Impact: Security

WSM-01501: failure in parsing the policy attachment

Cause: The XML was not well formed, or the XML did not follow the policy attachment schema.

Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01501: failure in parsing the policy attachment

Cause: The XML was not well formed, or the XML did not follow the policy attachment schema.

Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01502: failure in parsing the assertion template

Cause: The XML was not well formed, or the XML did not follow the assertion template schema.

Action: Ensure that the XML is well formed, and the XML follows the assertion template schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01502: failure in parsing the assertion template

Cause: The XML was not well formed, or the XML did not follow the assertion template schema.

Action: Ensure that the XML is well formed, and the XML follows the assertion template schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01503: failure in parsing the assertion

Cause: The XML was not well formed, or the XML did not follow the assertion schema.

Action: Ensure that the XML is well formed, and the XML follows the assertion schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01503: failure in parsing the assertion

Cause: The XML was not well formed, or the XML did not follow the assertion schema.

Action: Ensure that the XML is well formed, and the XML follows the assertion schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01504: failure in parsing the property set configuration

Cause: The XML was not well formed, or the XML did not follow the property set Config schema.

Action: Ensure that the XML is well formed, and the XML follows the property set Config schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01504: failure in parsing the property set configuration

Cause: The XML was not well formed, or the XML did not follow the property set Config schema.

Action: Ensure that the XML is well formed, and the XML follows the property set Config schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01505: failure in creating a copy of the policy {0}

Cause: Copying of the policy failed.

Action: Ensure that the policy to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01505: failure in creating a copy of the policy {0}

Cause: Copying of the policy failed.

Action: Ensure that the policy to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01506: failure in creating a copy of the assertion template {0}

Cause: Copying of the assertion template failed.

Action: Ensure that the assertion template to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01506: failure in creating a copy of the assertion template {0}

Cause: Copying of the assertion template failed.

Action: Ensure that the assertion template to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01507: failure in creating a copy of the assertion {0}

Cause: Copying of the assertion failed.

Action: Ensure that the assertion to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01507: failure in creating a copy of the assertion {0}

Cause: Copying of the assertion failed.

Action: Ensure that the assertion to be copied is valid. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01508: failure in transforming policy {0} to XML

Cause: The policy could not be serialized to XML.

Action: Ensure that the policy Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01508: failure in transforming policy {0} to XML

Cause: The policy could not be serialized to XML.

Action: Ensure that the policy Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01509: failure in transforming policy set {0} to XML

Cause: The policy set could not be serialized to XML.

Action: Ensure that the policy set Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01509: failure in transforming policy set {0} to XML

Cause: The policy set could not be serialized to XML.

Action: Ensure that the policy set Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01510: failure in transforming policy attachment {0} to XML

Cause: The policy attachment could not be serialized to XML.

Action: Ensure that the policy attachment Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01510: failure in transforming policy attachment {0} to XML

Cause: The policy attachment could not be serialized to XML.

Action: Ensure that the policy attachment Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01511: failure in transforming assertion template {0} to XML

Cause: The assertion template could not be serialized to XML.

Action: Ensure that the assertion template Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01511: failure in transforming assertion template {0} to XML

Cause: The assertion template could not be serialized to XML.

Action: Ensure that the assertion template Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01512: failure in transforming assertion {0} to XML

Cause: The assertion could not be serialized to XML.

Action: Ensure that the assertion Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01512: failure in transforming assertion {0} to XML

Cause: The assertion could not be serialized to XML.

Action: Ensure that the assertion Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01513: failure in transforming configuration {0} to XML

Cause: The configuration could not be serialized to XML.

Action: Ensure that the configuration Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01513: failure in transforming configuration {0} to XML

Cause: The configuration could not be serialized to XML.

Action: Ensure that the configuration Java object can be serialized to XML format.
Level: 1

Type: ERROR

Impact: Data

WSM-01514: failure in transforming policy reference {0} to XML

Cause: System could not serialize policy reference to XML.

Action: Ensure passed policy reference Java object doesn't have issues that causes the serialization to XML to fail.
Level: 1

Type: ERROR

Impact: Data

WSM-01514: failure in transforming policy reference {0} to XML

Cause: System could not serialize policy reference to XML.

Action: Ensure passed policy reference Java object doesn't have issues that causes the serialization to XML to fail.
Level: 1

Type: ERROR

Impact: Data

WSM-01515: failure in transforming policy subject {0} to XML

Cause: System could not serialize policy subject to XML.

Action: Ensure passed policy subject Java object doesn't have issues that cause the serialization to XML to fail.
Level: 1

Type: ERROR

Impact: Data

WSM-01515: failure in transforming policy subject {0} to XML

Cause: System could not serialize policy subject to XML.

Action: Ensure passed policy subject Java object doesn't have issues that cause the serialization to XML to fail.
Level: 1

Type: ERROR

Impact: Data

WSM-01524: failure in serialization of WSDL

Cause: WSDL Serialization failed.

Action: Ensure WSDL Extensions are available and configured. Consult diagnostic log for details or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01524: failure in serialization of WSDL

Cause: WSDL Serialization failed.

Action: Ensure WSDL Extensions are available and configured. Consult diagnostic log for details or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01526: WSDL Definition object is null

Cause: WSDL Definition Object is not available

Action: Ensure that a valid WSDL Definition object is sent to OWSM for advertisement of wsdl.
Level: 1

Type: ERROR

Impact: Data

WSM-01526: WSDL Definition object is null

Cause: WSDL Definition Object is not available

Action: Ensure that a valid WSDL Definition object is sent to OWSM for advertisement of wsdl.
Level: 1

Type: ERROR

Impact: Data

WSM-01600: error in creating or initializing the assertion, key={0}, qname={1}, wspqname={2}, constructorName={3}

Cause: An assertion object could not be created.

Action: Verify that the assertion follows the interface requirements defined in the Oracle documentation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01600: error in creating or initializing the assertion, key={0}, qname={1}, wspqname={2}, constructorName={3}

Cause: An assertion object could not be created.

Action: Verify that the assertion follows the interface requirements defined in the Oracle documentation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01601: failure in loading the resource

Cause: The requested resource could not be loaded.

Action: Ensure that the requested resource is present in the class path.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01601: failure in loading the resource

Cause: The requested resource could not be loaded.

Action: Ensure that the requested resource is present in the class path.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01602: error in loading class {0}

Cause: The requested class could not be loaded.

Action: Ensure that the requested class is present in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01602: error in loading class {0}

Cause: The requested class could not be loaded.

Action: Ensure that the requested class is present in the class path.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01603: failure in parsing the policy

Cause: Parsing of the policy failed.

Action: Ensure that the policy XML follows the policy schema, or a valid policy file exists.
Level: 1

Type: ERROR

Impact: Data

WSM-01603: failure in parsing the policy

Cause: Parsing of the policy failed.

Action: Ensure that the policy XML follows the policy schema, or a valid policy file exists.
Level: 1

Type: ERROR

Impact: Data

WSM-01604: XML Parser Configuration error

Cause: The XML Parser was not configured properly.

Action: Consult Oracle documentation or Java documentation on how to configure the XML Parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01604: XML Parser Configuration error

Cause: The XML Parser was not configured properly.

Action: Consult Oracle documentation or Java documentation on how to configure the XML Parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01605: XML parser exception

Cause: Parsing of the XML failed.

Action: Ensure that the XML is well formed.
Level: 1

Type: ERROR

Impact: Data

WSM-01605: XML parser exception

Cause: Parsing of the XML failed.

Action: Ensure that the XML is well formed.
Level: 1

Type: ERROR

Impact: Data

WSM-01606: system I/O error

Cause: The system could not open the Input/Output streams.

Action: Consult the Java documentation.
Level: 1

Type: ERROR

Impact: Files

WSM-01606: system I/O error

Cause: The system could not open the Input/Output streams.

Action: Consult the Java documentation.
Level: 1

Type: ERROR

Impact: Files

WSM-01607: XPath expression evaluation error

Cause: Evaluation of the XPATH expression failed.

Action: Ensure that the XPATH expression is valid, and the XML follows the schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01607: XPath expression evaluation error

Cause: Evaluation of the XPATH expression failed.

Action: Ensure that the XPATH expression is valid, and the XML follows the schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01608: The class cannot be found.

Cause: The requested class was not found in the class path.

Action: Ensure that the class name is correct in the configuration files and is in the class path.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01608: The class cannot be found.

Cause: The requested class was not found in the class path.

Action: Ensure that the class name is correct in the configuration files and is in the class path.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01610: cannot initialize standard serializers/deserializers

Cause: The standard serializer and deserializer objects could not be loaded.

Action: Ensure that the product configuration is correct. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01610: cannot initialize standard serializers/deserializers

Cause: The standard serializer and deserializer objects could not be loaded.

Action: Ensure that the product configuration is correct. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01611: The class cannot be loaded because of Java security restrictions.

Cause: The requested classes could not be loaded due to class loading security restrictions.

Action: Contact the site administrator or consult the Java documentation to ensure that the classes have the necessary Java security permissions.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01611: The class cannot be loaded because of Java security restrictions.

Cause: The requested classes could not be loaded due to class loading security restrictions.

Action: Contact the site administrator or consult the Java documentation to ensure that the classes have the necessary Java security permissions.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01612: An instance of the requested class cannot be created.

Cause: The system could not create an instance of the requested class.

Action: Consult the Java documentation or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01612: An instance of the requested class cannot be created.

Cause: The system could not create an instance of the requested class.

Action: Consult the Java documentation or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01613: The XML parser cannot be configured.

Cause: The XML parser could not be configured.

Action: Consult the Java documentation on how to configure the XML parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01613: The XML parser cannot be configured.

Cause: The XML parser could not be configured.

Action: Consult the Java documentation on how to configure the XML parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01614: The assertion XML Java Document cannot be serialized to a String.

Cause: The assertion XML Java Document could not be serialized to a String.

Action: Check the assertion for any errors and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01614: The assertion XML Java Document cannot be serialized to a String.

Cause: The assertion XML Java Document could not be serialized to a String.

Action: Check the assertion for any errors and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-01615: The assertion XML String cannot be converted to a Java object.

Cause: The assertion XML String could not converted to a Java Document.

Action: Ensure that the String being converted to XML is a well-formed XML.
Level: 1

Type: ERROR

Impact: Data

WSM-01615: The assertion XML String cannot be converted to a Java object.

Cause: The assertion XML String could not converted to a Java Document.

Action: Ensure that the String being converted to XML is a well-formed XML.
Level: 1

Type: ERROR

Impact: Data

WSM-01616: Policy {0} cannot be inserted into the WSDL.

Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.

Action: Ensure that the WSDL extensions for the policy being injected are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01616: Policy {0} cannot be inserted into the WSDL.

Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.

Action: Ensure that the WSDL extensions for the policy being injected are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01617: error in parsing the policies embedded in the WSDL

Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.

Action: Ensure that the WSDL extensions for policy are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01617: error in parsing the policies embedded in the WSDL

Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.

Action: Ensure that the WSDL extensions for policy are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01618: error in parsing the policy references embedded in the WSDL

Cause: The XML for the policy references in the WSDL could not be parsed.

Action: Ensure that the WSDL extensions for the policy reference are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01618: error in parsing the policy references embedded in the WSDL

Cause: The XML for the policy references in the WSDL could not be parsed.

Action: Ensure that the WSDL extensions for the policy reference are available and configured. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01619: This assertion type is not recognized.

Cause: The assertion type was not recognized.

Action: Consult Oracle documentation for the supported assertion types.
Level: 1

Type: ERROR

Impact: Data

WSM-01619: This assertion type is not recognized.

Cause: The assertion type was not recognized.

Action: Consult Oracle documentation for the supported assertion types.
Level: 1

Type: ERROR

Impact: Data

WSM-01620: cannot convert XML Java Document to String

Cause: The XML Java Document being converted was not well formed.

Action: Ensure that the assertions can be serialized to a String.
Level: 1

Type: ERROR

Impact: Data

WSM-01620: cannot convert XML Java Document to String

Cause: The XML Java Document being converted was not well formed.

Action: Ensure that the assertions can be serialized to a String.
Level: 1

Type: ERROR

Impact: Data

WSM-01621: Policy intersection algorithm is not defined for assertion type :

Cause: The policy intersection algorithm was not found for the assertion.

Action: Ensure that the intersection algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01621: Policy intersection algorithm is not defined for assertion type :

Cause: The policy intersection algorithm was not found for the assertion.

Action: Ensure that the intersection algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01622: Policy merge algorithm is not defined for assertion type :

Cause: The policy merge algorithm was not found for the assertion.

Action: Ensure that the merge algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01622: Policy merge algorithm is not defined for assertion type :

Cause: The policy merge algorithm was not found for the assertion.

Action: Ensure that the merge algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01623: Policy reference cannot be resolved :

Cause: The policy reference was invalid.

Action: Ensure that the policy reference is valid.
Level: 1

Type: ERROR

Impact: Data

WSM-01623: Policy reference cannot be resolved :

Cause: The policy reference was invalid.

Action: Ensure that the policy reference is valid.
Level: 1

Type: ERROR

Impact: Data

WSM-01624: The policy does not exist in the policy store :

Cause: The policy reference was invalid, or the referenced policy could not be retrieved.

Action: Ensure that the policy reference is valid, and the policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01624: The policy does not exist in the policy store :

Cause: The policy reference was invalid, or the referenced policy could not be retrieved.

Action: Ensure that the policy reference is valid, and the policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01625: The Name attribute of the property is missing.

Cause: The Name attribute for a property was missing.

Action: Provide a value for the Name attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01625: The Name attribute of the property is missing.

Cause: The Name attribute for a property was missing.

Action: Provide a value for the Name attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01626: The Type attribute of the property is missing.

Cause: The Type attribute for a property was missing.

Action: Provide a value for the Type attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01626: The Type attribute of the property is missing.

Cause: The Type attribute for a property was missing.

Action: Provide a value for the Type attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01627: The assertion contains too many bindings.

Cause: The assertion contained more than one binding.

Action: Ensure that the assertion contains a single binding.
Level: 1

Type: ERROR

Impact: Data

WSM-01627: The assertion contains too many bindings.

Cause: The assertion contained more than one binding.

Action: Ensure that the assertion contains a single binding.
Level: 1

Type: ERROR

Impact: Data

WSM-01628: The policy normalization algorithm is not defined for this assertion type

Cause: The policy normalization algorithm was not found for the assertion.

Action: Ensure that the normalization algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01628: The policy normalization algorithm is not defined for this assertion type

Cause: The policy normalization algorithm was not found for the assertion.

Action: Ensure that the normalization algorithm for the assertion used is configured.
Level: 1

Type: ERROR

Impact: Data

WSM-01629: The assertion template contains too many assertions.

Cause: The assertion template contained more than one assertion.

Action: Ensure that assertion template contains only one assertion.
Level: 1

Type: ERROR

Impact: Data

WSM-01629: The assertion template contains too many assertions.

Cause: The assertion template contained more than one assertion.

Action: Ensure that assertion template contains only one assertion.
Level: 1

Type: ERROR

Impact: Data

WSM-01630: Element {0} is not a known policy element.

Cause: XML parsing failed; the system encountered unsupported XML elements.

Action: Ensure that the XML follows the schema, and the XML contains only those elements that are supported.
Level: 1

Type: ERROR

Impact: Data

WSM-01630: Element {0} is not a known policy element.

Cause: XML parsing failed; the system encountered unsupported XML elements.

Action: Ensure that the XML follows the schema, and the XML contains only those elements that are supported.
Level: 1

Type: ERROR

Impact: Data

WSM-01631: The assertion {0} contains multiple bindings.

Cause: The assertion contained more than one binding.

Action: Ensure that the assertion contains only one binding.
Level: 1

Type: ERROR

Impact: Data

WSM-01631: The assertion {0} contains multiple bindings.

Cause: The assertion contained more than one binding.

Action: Ensure that the assertion contains only one binding.
Level: 1

Type: ERROR

Impact: Data

WSM-01632: The assertion {0} contains multiple policies as child elements.

Cause: The assertion contained more than one policy child element.

Action: Ensure that the assertion contains only one policy child element.
Level: 1

Type: ERROR

Impact: Data

WSM-01632: The assertion {0} contains multiple policies as child elements.

Cause: The assertion contained more than one policy child element.

Action: Ensure that the assertion contains only one policy child element.
Level: 1

Type: ERROR

Impact: Data

WSM-01633: Assertion type {0} does not match the corresponding Java Object type created.

Cause: The assertion type was incorrectly defined for the assertion.

Action: Ensure that the correct assertion type is set for the assertion.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01633: Assertion type {0} does not match the corresponding Java Object type created.

Cause: The assertion type was incorrectly defined for the assertion.

Action: Ensure that the correct assertion type is set for the assertion.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01635: Passed Java Object {0} does not extend the Assertion class

Cause: The Assertion class did not extend the correct classes.

Action: Consult Oracle Documentation for creating assertion implementations.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01635: Passed Java Object {0} does not extend the Assertion class

Cause: The Assertion class did not extend the correct classes.

Action: Consult Oracle Documentation for creating assertion implementations.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01636: The assertion type {0} is not supported.

Cause: The assertion type does not match any of the predefined assertion types.

Action: Ensure that the assertion type is supported.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01636: The assertion type {0} is not supported.

Cause: The assertion type does not match any of the predefined assertion types.

Action: Ensure that the assertion type is supported.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01637: The policy attachment cannot be parsed.

Cause: The policy attachment XML was invalid.

Action: Ensure that policy attachment XML follows the policy attachment XML schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01637: The policy attachment cannot be parsed.

Cause: The policy attachment XML was invalid.

Action: Ensure that policy attachment XML follows the policy attachment XML schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01638: The policy attachment is not valid because the domain is not specified.

Cause: The policy attachment did not contain domain expressions.

Action: Ensure that policy attachment XML follows the policy attachment XML schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01638: The policy attachment is not valid because the domain is not specified.

Cause: The policy attachment did not contain domain expressions.

Action: Ensure that policy attachment XML follows the policy attachment XML schema.
Level: 1

Type: ERROR

Impact: Data

WSM-01640: The policy reference {0} is not valid.

Cause: The policy reference could not be resolved.

Action: Ensure that the referenced policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01640: The policy reference {0} is not valid.

Cause: The policy reference could not be resolved.

Action: Ensure that the referenced policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01641: The policy advertisement level is not specified for the policy.

Cause: The policy advertisement level was not specified.

Action: Ensure that a valid value is set for the policy advertisement level.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01641: The policy advertisement level is not specified for the policy.

Cause: The policy advertisement level was not specified.

Action: Ensure that a valid value is set for the policy advertisement level.
Level: 1

Type: ERROR

Impact: Configuration

WSM-01642: Policy advertisement is not supported for unsupported WSDL elements.

Cause: Policy advertisement was not supported for the WSDL object.

Action: Consult Oracle documentation for supported WSDL objects.
Level: 1

Type: ERROR

Impact: Data

WSM-01642: Policy advertisement is not supported for unsupported WSDL elements.

Cause: Policy advertisement was not supported for the WSDL object.

Action: Consult Oracle documentation for supported WSDL objects.
Level: 1

Type: ERROR

Impact: Data

WSM-01643: What the XML system expects is different from what is encountered.

Cause: Usage of system was invalid or the feature was unsupported.

Action: Consult Documentation on usage and supported features.
Level: 1

Type: ERROR

Impact: Data

WSM-01643: What the XML system expects is different from what is encountered.

Cause: Usage of system was invalid or the feature was unsupported.

Action: Consult Documentation on usage and supported features.
Level: 1

Type: ERROR

Impact: Data

WSM-01644: The WSDL object {0} is not supported.

Cause: The WSDL object was not supported.

Action: Consult Oracle documentation for the supported WSDL objects.
Level: 1

Type: ERROR

Impact: Data

WSM-01644: The WSDL object {0} is not supported.

Cause: The WSDL object was not supported.

Action: Consult Oracle documentation for the supported WSDL objects.
Level: 1

Type: ERROR

Impact: Data

WSM-01645: The resource pattern {0} does not match the corresponding WSDL object.

Cause: WSDL Objects did not match.

Action: Ensure that the WSDL Objects match.
Level: 1

Type: ERROR

Impact: Data

WSM-01645: The resource pattern {0} does not match the corresponding WSDL object.

Cause: WSDL Objects did not match.

Action: Ensure that the WSDL Objects match.
Level: 1

Type: ERROR

Impact: Data

WSM-01646: The value for the attachTo attribute of the policy is not valid.

Cause: The attachTo attribute of the policy did not match any of the predefined attachTo values.

Action: Consult Oracle documentation for the valid values for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01646: The value for the attachTo attribute of the policy is not valid.

Cause: The attachTo attribute of the policy did not match any of the predefined attachTo values.

Action: Consult Oracle documentation for the valid values for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01647: There are no policies that match the specified category {0} and resource pattern {1}.

Cause: No policies matched the specified search criteria.

Action: Ensure that the policies that match the search categories exist in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01647: There are no policies that match the specified category {0} and resource pattern {1}.

Cause: No policies matched the specified search criteria.

Action: Ensure that the policies that match the search categories exist in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01650: cannot construct policy object

Cause: Construction of the policy Java object failed.

Action: Consult the diagnostic log for details.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01650: cannot construct policy object

Cause: Construction of the policy Java object failed.

Action: Consult the diagnostic log for details.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01651: cannot advertise requested policies

Cause: Advertisement of the policies failed.

Action: Consult the diagnostic log for details, or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Programmatic

WSM-01651: cannot advertise requested policies

Cause: Advertisement of the policies failed.

Action: Consult the diagnostic log for details, or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Programmatic

WSM-01652: error in parsing the time stamp in the policy set document

Cause: The Timestamp attribute in the XML representation of a policy set document is not a valid number.

Action: Correct or remove the invalid attribute value.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01652: error in parsing the time stamp in the policy set document

Cause: The Timestamp attribute in the XML representation of a policy set document is not a valid number.

Action: Correct or remove the invalid attribute value.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01653: The assertion contains more than one Guard element.

Cause: The assertion contained more than one guard.

Action: Ensure that the assertion contains a single guard.
Level: 1

Type: ERROR

Impact: Data

WSM-01653: The assertion contains more than one Guard element.

Cause: The assertion contained more than one guard.

Action: Ensure that the assertion contains a single guard.
Level: 1

Type: ERROR

Impact: Data

WSM-01654: failure in serialization of security scenario assertion

Cause: The SecurityScenario in OraPolicy could not be serialized or was incorrectly configured.

Action: Ensure that the OraPolicy is correct. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01654: failure in serialization of security scenario assertion

Cause: The SecurityScenario in OraPolicy could not be serialized or was incorrectly configured.

Action: Ensure that the OraPolicy is correct. Consult Oracle documentation for more information.
Level: 1

Type: ERROR

Impact: Data

WSM-01655: There are no policies that match the specified category {0}.

Cause: No policies matched the specified category.

Action: Ensure that the policies that match the search category exist in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01655: There are no policies that match the specified category {0}.

Cause: No policies matched the specified category.

Action: Ensure that the policies that match the search category exist in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01656: generic Oracle WSM Policy Manager error

Cause: An internal error occurred during the Policy related operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01656: generic Oracle WSM Policy Manager error

Cause: An internal error occurred during the Policy related operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01657: Oracle WSM Advertisement Engine must be initialized with valid properties. Following properties [{0}] are either empty or null

Cause: WSM Advertisement Engine initialized with invalid parameters.

Action: Ensure that valid parameters are set during WSM Advertisement Engine configuration
Level: 1

Type: ERROR

Impact: Configuration

WSM-01657: Oracle WSM Advertisement Engine must be initialized with valid properties. Following properties [{0}] are either empty or null

Cause: WSM Advertisement Engine initialized with invalid parameters.

Action: Ensure that valid parameters are set during WSM Advertisement Engine configuration
Level: 1

Type: ERROR

Impact: Configuration

WSM-01658: X509 Certificate will not be advertised as {0} not found

Cause: Implementation class for advertising X509 Certificate in WSDL is not available

Action: Ensure that implementation class required for advertising X509 Certificate in WSDL is not available. Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WSM-01658: X509 Certificate will not be advertised as {0} not found

Cause: Implementation class for advertising X509 Certificate in WSDL is not available

Action: Ensure that implementation class required for advertising X509 Certificate in WSDL is not available. Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: WARNING

Impact: Other

WSM-01659: A JAXBContext cannot be created due to underlying exception "{0}".

Cause: One or more expected classes could not be located.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01659: A JAXBContext cannot be created due to underlying exception "{0}".

Cause: One or more expected classes could not be located.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01660: A JAXB unmarshaller cannot be created due to underlying exception "{0}".

Cause: An error occurred while creating an unmarshaller.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01660: A JAXB unmarshaller cannot be created due to underlying exception "{0}".

Cause: An error occurred while creating an unmarshaller.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01661: A string cannot be unmarshalled into an object due to underlying exception "{0}".

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01661: A string cannot be unmarshalled into an object due to underlying exception "{0}".

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01662: The QName "{0}" does not match the expected QName "{1}" for the unmarshalled object.

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01662: The QName "{0}" does not match the expected QName "{1}" for the unmarshalled object.

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01663: A null or empty string cannot be unmarshalled into an Intent object.

Cause: An attempt was made to unmarshall an Intent from a null or empty String.

Action: Provide a String that contains a marshalled Intent.
Level: 1

Type: ERROR

Impact: Data

WSM-01663: A null or empty string cannot be unmarshalled into an Intent object.

Cause: An attempt was made to unmarshall an Intent from a null or empty String.

Action: Provide a String that contains a marshalled Intent.
Level: 1

Type: ERROR

Impact: Data

WSM-01664: A null or empty string cannot be unmarshalled into a PolicySet object.

Cause: An attempt was made to unmarshall a PolicySet from a null or empty String.

Action: Provide a String that contains a marshalled PolicySet.
Level: 1

Type: ERROR

Impact: Data

WSM-01664: A null or empty string cannot be unmarshalled into a PolicySet object.

Cause: An attempt was made to unmarshall a PolicySet from a null or empty String.

Action: Provide a String that contains a marshalled PolicySet.
Level: 1

Type: ERROR

Impact: Data

WSM-01665: A JAXB marshaller cannot be created due to underlying exception "{0}".

Cause: An error occurred while creating a marshaller.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01665: A JAXB marshaller cannot be created due to underlying exception "{0}".

Cause: An error occurred while creating a marshaller.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-01666: An object cannot be marshalled to a string due to underlying exception "{0}".

Cause: Marshalling the supplied type of the object is not supported.

Action: Provide an object of a supported type.
Level: 1

Type: ERROR

Impact: Data

WSM-01666: An object cannot be marshalled to a string due to underlying exception "{0}".

Cause: Marshalling the supplied type of the object is not supported.

Action: Provide an object of a supported type.
Level: 1

Type: ERROR

Impact: Data

WSM-01667: An object cannot be marshalled to a DOM object due to underlying exception "{0}".

Cause: Marshalling the supplied type of the object is not supported.

Action: Provide an object of a supported type.
Level: 1

Type: ERROR

Impact: Data

WSM-01667: An object cannot be marshalled to a DOM object due to underlying exception "{0}".

Cause: Marshalling the supplied type of the object is not supported.

Action: Provide an object of a supported type.
Level: 1

Type: ERROR

Impact: Data

WSM-01668: A null Intent object cannot be marshalled.

Cause: An attempt was made to marshall a null Intent object.

Action: Provide a non-null Intent object.
Level: 1

Type: ERROR

Impact: Data

WSM-01668: A null Intent object cannot be marshalled.

Cause: An attempt was made to marshall a null Intent object.

Action: Provide a non-null Intent object.
Level: 1

Type: ERROR

Impact: Data

WSM-01669: A null PolicySet object cannot be marshalled.

Cause: An attempt was made to marshall a null PolicySet object.

Action: Provide a non-null PolicySet object.
Level: 1

Type: ERROR

Impact: Data

WSM-01669: A null PolicySet object cannot be marshalled.

Cause: An attempt was made to marshall a null PolicySet object.

Action: Provide a non-null PolicySet object.
Level: 1

Type: ERROR

Impact: Data

WSM-01670: An object cannot be marshalled into a null DOM object.

Cause: An attempt was made to marshall an object into a null Document object.

Action: Provide a non-null Document object.
Level: 1

Type: ERROR

Impact: Data

WSM-01670: An object cannot be marshalled into a null DOM object.

Cause: An attempt was made to marshall an object into a null Document object.

Action: Provide a non-null Document object.
Level: 1

Type: ERROR

Impact: Data

WSM-01671: The DOM element cannot be null for policy subject identified by the resource pattern: "{0}".

Cause: The null DOM element was passed.

Action: Pass a valid non-null DOM element.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01671: The DOM element cannot be null for policy subject identified by the resource pattern: "{0}".

Cause: The null DOM element was passed.

Action: Pass a valid non-null DOM element.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01672: The policy reference URI: "{1}" for policy subject identified by the resource pattern: "{0}" cannot be empty.

Cause: Empty policy references were found in the DOM element node.

Action: Verify the DOM element node and make sure the policy references specify a valid value and the referenced policies exist in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01672: The policy reference URI: "{1}" for policy subject identified by the resource pattern: "{0}" cannot be empty.

Cause: Empty policy references were found in the DOM element node.

Action: Verify the DOM element node and make sure the policy references specify a valid value and the referenced policies exist in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01673: Duplicate policy references: "{1}" are found for policy subject identified by resource pattern "{0}".

Cause: Duplicate policy references were found in the same DOM element node.

Action: Remove the duplicate policy references from the DOM element node.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01673: Duplicate policy references: "{1}" are found for policy subject identified by resource pattern "{0}".

Cause: Duplicate policy references were found in the same DOM element node.

Action: Remove the duplicate policy references from the DOM element node.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01674: The DOM element: "{1}" for policy subject identified by resource pattern "{0}" is unsupported element.

Cause: Policies cannot be retrieved for unsupported DOM element node.

Action: Verify that a supported DOM element node is provided for retrieving the policy.
Level: 1

Type: WARNING

Impact: Compliance

WSM-01674: The DOM element: "{1}" for policy subject identified by resource pattern "{0}" is unsupported element.

Cause: Policies cannot be retrieved for unsupported DOM element node.

Action: Verify that a supported DOM element node is provided for retrieving the policy.
Level: 1

Type: WARNING

Impact: Compliance

WSM-01675: The policy references cannot be null.

Cause: A null policy reference was passed.

Action: Pass the valid non-null policy reference object.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01675: The policy references cannot be null.

Cause: A null policy reference was passed.

Action: Pass the valid non-null policy reference object.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01676: The resource pattern cannot be null.

Cause: A null resource pattern was passed.

Action: Pass a valid non-null resource pattern.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01676: The resource pattern cannot be null.

Cause: A null resource pattern was passed.

Action: Pass a valid non-null resource pattern.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01677: The domain expression cannot be null.

Cause: A null domain expression was passed.

Action: Pass a valid non-null domain expression.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01677: The domain expression cannot be null.

Cause: A null domain expression was passed.

Action: Pass a valid non-null domain expression.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01678: Element {0} is not a valid child element for Policy object.

Cause: Invalid child element found for Policy object.

Action: Check the policy string being parsed and make sure only valid child elements are present for the Policy.
Level: 1

Type: ERROR

Impact: Data

WSM-01678: Element {0} is not a valid child element for Policy object.

Cause: Invalid child element found for Policy object.

Action: Check the policy string being parsed and make sure only valid child elements are present for the Policy.
Level: 1

Type: ERROR

Impact: Data

WSM-01679: A DOM node cannot be unmarshalled into an object due to underlying exception "{0}".

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01679: A DOM node cannot be unmarshalled into an object due to underlying exception "{0}".

Cause: The string is not suitable for unmarshalling to the requested type.

Action: Provide a string that is suitable for unmarshalling to the requested type.
Level: 1

Type: ERROR

Impact: Data

WSM-01680: A null node cannot be unmarshalled into a RepositoryInfo object.

Cause: An attempt was made to unmarshall a RepositoryInfo from a null node.

Action: Provide a node that contains a marshalled RepositoryInfo.
Level: 1

Type: ERROR

Impact: Data

WSM-01680: A null node cannot be unmarshalled into a RepositoryInfo object.

Cause: An attempt was made to unmarshall a RepositoryInfo from a null node.

Action: Provide a node that contains a marshalled RepositoryInfo.
Level: 1

Type: ERROR

Impact: Data

WSM-01681: A null or empty string cannot be unmarshalled into a RepositoryInfo object.

Cause: An attempt was made to unmarshall a RepositoryInfo from a null or empty String.

Action: Provide a String that contains a marshalled RepositoryInfo.
Level: 1

Type: ERROR

Impact: Data

WSM-01681: A null or empty string cannot be unmarshalled into a RepositoryInfo object.

Cause: An attempt was made to unmarshall a RepositoryInfo from a null or empty String.

Action: Provide a String that contains a marshalled RepositoryInfo.
Level: 1

Type: ERROR

Impact: Data

WSM-01682: A null RepositoryInfo object cannot be marshalled.

Cause: An attempt was made to marshall a null RepositoryInfo object.

Action: Provide a non-null RepositoryInfo object.
Level: 1

Type: ERROR

Impact: Data

WSM-01682: A null RepositoryInfo object cannot be marshalled.

Cause: An attempt was made to marshall a null RepositoryInfo object.

Action: Provide a non-null RepositoryInfo object.
Level: 1

Type: ERROR

Impact: Data

WSM-01683: The passed String "{0}" could not be parsed using UTF encoding.

Cause: Underlying JVM does not support UTF-8 encoding.

Action: Check the JVM configuration to make sure it supports UTF-8 encoding format.
Level: 1

Type: ERROR

Impact: Data

WSM-01683: The passed String "{0}" could not be parsed using UTF encoding.

Cause: Underlying JVM does not support UTF-8 encoding.

Action: Check the JVM configuration to make sure it supports UTF-8 encoding format.
Level: 1

Type: ERROR

Impact: Data

WSM-01684: A null or empty string cannot be unmarshalled into a Policy object.

Cause: An attempt was made to unmarshall a Policy from a null or empty String.

Action: Provide a String that contains a marshalled Policy.
Level: 1

Type: ERROR

Impact: Data

WSM-01684: A null or empty string cannot be unmarshalled into a Policy object.

Cause: An attempt was made to unmarshall a Policy from a null or empty String.

Action: Provide a String that contains a marshalled Policy.
Level: 1

Type: ERROR

Impact: Data

WSM-01685: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.

Cause: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.

Action: Attach sts_trust_config_service_policy if not attached yet, or specify issuer uri value in the policy if not specified. Ignore if using sts_trust_config_client_policy.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-01685: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.

Cause: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.

Action: Attach sts_trust_config_service_policy if not attached yet, or specify issuer uri value in the policy if not specified. Ignore if using sts_trust_config_client_policy.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-01686: Advertisement failed due to an unexpected assertion type: {0}.

Cause: The assertion type is not recognized.

Action: Internal error. Provide
Level: 1

Type: ERROR

Impact: Configuration

WSM-01686: Advertisement failed due to an unexpected assertion type: {0}.

Cause: The assertion type is not recognized.

Action: Internal error. Provide
Level: 1

Type: ERROR

Impact: Configuration

WSM-01687: The constant property "{0}" cannot be overriden.

Cause: There is an attempt to override a property value which is defined as a constant in the policy.

Action: Ensure that there is no attempt to override a constant property.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01687: The constant property "{0}" cannot be overriden.

Cause: There is an attempt to override a property value which is defined as a constant in the policy.

Action: Ensure that there is no attempt to override a constant property.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01688: X509 Certificate will not be advertised due to underlying exception "{0}".

Cause: Either the keystore was not available or the keystore configuration was incorrect.

Action: Ensure the keystore exists and that the keystore password and aliases are correct.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01688: X509 Certificate will not be advertised due to underlying exception "{0}".

Cause: Either the keystore was not available or the keystore configuration was incorrect.

Action: Ensure the keystore exists and that the keystore password and aliases are correct.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01689: Advertisement failed due to an incorrect ws-policy/ws-securitypolicy specification version {0}/{1}.

Cause: Invalid ws-policy/ws-securitypolicy specification version used to advertise policy.

Action: Ensure the ws-policy/ws-securitypolicy specification versions are correct.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01689: Advertisement failed due to an incorrect ws-policy/ws-securitypolicy specification version {0}/{1}.

Cause: Invalid ws-policy/ws-securitypolicy specification version used to advertise policy.

Action: Ensure the ws-policy/ws-securitypolicy specification versions are correct.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01690: Assertion {0} located by QName {1} is not an instanceof type {2}.

Cause: An internal error, probably policy was not deserialized into the correct assertion instance.

Action: Consult diagnostic log for details or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01690: Assertion {0} located by QName {1} is not an instanceof type {2}.

Cause: An internal error, probably policy was not deserialized into the correct assertion instance.

Action: Consult diagnostic log for details or contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01691: Cannot construct or access policy object for policy "{0}" due to underlying exception "{1}".

Cause: Construction of the policy Java object failed for the given policy name.

Action: Consult the diagnostic log for details.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01691: Cannot construct or access policy object for policy "{0}" due to underlying exception "{1}".

Cause: Construction of the policy Java object failed for the given policy name.

Action: Consult the diagnostic log for details.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-01692: Advertisement failed due to multiple ws-policy specification version specified.

Cause: Multiple ws-policy specification version used to advertise policy.

Action: Remove the duplicate ws-policy specification versions and try again.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01692: Advertisement failed due to multiple ws-policy specification version specified.

Cause: Multiple ws-policy specification version used to advertise policy.

Action: Remove the duplicate ws-policy specification versions and try again.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01693: Advertisement failed due to multiple wssecurity-policy specification version specified.

Cause: Multiple ws-securitypolicy specification version used to advertise policy.

Action: Remove the duplicate ws-securitypolicy specification versions and try again.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01693: Advertisement failed due to multiple wssecurity-policy specification version specified.

Cause: Multiple ws-securitypolicy specification version used to advertise policy.

Action: Remove the duplicate ws-securitypolicy specification versions and try again.
Level: 1

Type: WARNING

Impact: Configuration

WSM-01694: Policy compatibility check failed due to invalid policy set. {0}.

Cause: Policy compatibility check failed due to invalid policy set.

Action: Ensure that the policy set attached to the client is a valid policy set. Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WSM-01694: Policy compatibility check failed due to invalid policy set. {0}.

Cause: Policy compatibility check failed due to invalid policy set.

Action: Ensure that the policy set attached to the client is a valid policy set. Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WSM-01695: Encountered internal error while attempting to reorder PolicyReferences "{0}" in a PolicySet "{1}".

Cause: Encountered unexpected Policy model exception during reordering PolicyReferences in a PolicySet

Action: Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WSM-01695: Encountered internal error while attempting to reorder PolicyReferences "{0}" in a PolicySet "{1}".

Cause: Encountered unexpected Policy model exception during reordering PolicyReferences in a PolicySet

Action: Consult diagnostic log for details or contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Other

WSM-01696: While validating the input PolicySet array to be merged, the PolicySet in the array have no common ResourcePattern, basePattern={0}, invalid input PolicySet array= {1}

Cause: While validating the input PolicySet array to be merged, the PolicySet in the array have no common ResourcePattern

Action: Make sure ResourcePattern of all PolicySet in the array either all null, or for non-null ones they must all have the same ResourcePattern.
Level: 1

Type: ERROR

Impact: Other

WSM-01696: While validating the input PolicySet array to be merged, the PolicySet in the array have no common ResourcePattern, basePattern={0}, invalid input PolicySet array= {1}

Cause: While validating the input PolicySet array to be merged, the PolicySet in the array have no common ResourcePattern

Action: Make sure ResourcePattern of all PolicySet in the array either all null, or for non-null ones they must all have the same ResourcePattern.
Level: 1

Type: ERROR

Impact: Other

WSM-01697: While validating the input PolicySet array to be merged, there are multple PolicySet that have ResourcePattern that are not the same as that of the base, only single PolicySet in the input is allowed, basePattern={0}, invalid input PolicySet array= {1}

Cause: While validating the input PolicySet array to be merged, there are multple PolicySet that have ResourcePattern that are not the same as that of the base PolicySet

Action: Make sure that the input PolicySet array has a single PolicySet if its ResourcePattern is different that that of the base PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-01697: While validating the input PolicySet array to be merged, there are multple PolicySet that have ResourcePattern that are not the same as that of the base, only single PolicySet in the input is allowed, basePattern={0}, invalid input PolicySet array= {1}

Cause: While validating the input PolicySet array to be merged, there are multple PolicySet that have ResourcePattern that are not the same as that of the base PolicySet

Action: Make sure that the input PolicySet array has a single PolicySet if its ResourcePattern is different that that of the base PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-01698: Runtime PolicySet is locked and it can not be modified with operation "{0}" and argument "{1}".

Cause: Runtime PolicySet is locked and read only; it cannot be modified

Action: Donot modify PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-01698: Runtime PolicySet is locked and it can not be modified with operation "{0}" and argument "{1}".

Cause: Runtime PolicySet is locked and read only; it cannot be modified

Action: Donot modify PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-01699: Runtime PolicySet "{0}" operation got an invalid argument "{1}" with value "{2}".

Cause: Runtime PolicySet add method passed in a null or invalid argment(s).

Action: Check the arguments and correct them.
Level: 1

Type: ERROR

Impact: Other

WSM-01699: Runtime PolicySet "{0}" operation got an invalid argument "{1}" with value "{2}".

Cause: Runtime PolicySet add method passed in a null or invalid argment(s).

Action: Check the arguments and correct them.
Level: 1

Type: ERROR

Impact: Other

WSM-01700: The current Runtime PolicySet "{0}" merge method got an invalid PolicySet "{1}" in the List of PolicySet passed in; it is not an instance of PolicySet, very likely it is a CallbackPolicySet

Cause: Runtime PolicySet merge method passed invalid argument.

Action: Check the arguments and correct them.
Level: 1

Type: ERROR

Impact: Other

WSM-01700: The current Runtime PolicySet "{0}" merge method got an invalid PolicySet "{1}" in the List of PolicySet passed in; it is not an instance of PolicySet, very likely it is a CallbackPolicySet

Cause: Runtime PolicySet merge method passed invalid argument.

Action: Check the arguments and correct them.
Level: 1

Type: ERROR

Impact: Other

WSM-01751: The name of an assertion property is empty.

Cause: The name of an assertion property was empty.

Action: Make sure that you specify a name for all assertion properties.
Level: 1

Type: ERROR

Impact: Data

WSM-01751: The name of an assertion property is empty.

Cause: The name of an assertion property was empty.

Action: Make sure that you specify a name for all assertion properties.
Level: 1

Type: ERROR

Impact: Data

WSM-01752: The data type of the value does not match the data type of property {0}. The expected data type is String.

Cause: The datatype of the property value entered was not of type String.

Action: Make sure that the data type for the property value is of type String.
Level: 1

Type: ERROR

Impact: Data

WSM-01752: The data type of the value does not match the data type of property {0}. The expected data type is String.

Cause: The datatype of the property value entered was not of type String.

Action: Make sure that the data type for the property value is of type String.
Level: 1

Type: ERROR

Impact: Data

WSM-01753: The data type of the value does not match the data type of property {0}. The expected data type is Boolean.

Cause: The data type of the property value entered was not of type Boolean.

Action: Make sure that the data type for the property value is of type Boolean.
Level: 1

Type: ERROR

Impact: Data

WSM-01753: The data type of the value does not match the data type of property {0}. The expected data type is Boolean.

Cause: The data type of the property value entered was not of type Boolean.

Action: Make sure that the data type for the property value is of type Boolean.
Level: 1

Type: ERROR

Impact: Data

WSM-01754: The data type of the value does not match the data type of property {0}. The expected data type is Integer.

Cause: The data type of the property value entered was not of type Integer.

Action: Make sure that the data type for the property value is of type Integer.
Level: 1

Type: ERROR

Impact: Data

WSM-01754: The data type of the value does not match the data type of property {0}. The expected data type is Integer.

Cause: The data type of the property value entered was not of type Integer.

Action: Make sure that the data type for the property value is of type Integer.
Level: 1

Type: ERROR

Impact: Data

WSM-01755: An empty value is specified for property {0}.

Cause: An empty value was specified for a property that has a data type of type Password.

Action: Specify a value for all properties that have a data type of type Password.
Level: 1

Type: ERROR

Impact: Data

WSM-01755: An empty value is specified for property {0}.

Cause: An empty value was specified for a property that has a data type of type Password.

Action: Specify a value for all properties that have a data type of type Password.
Level: 1

Type: ERROR

Impact: Data

WSM-01756: The Property Set name field of context: {0} is empty

Cause: The Property Set Name field in one of the assertions was empty.

Action: Make sure that you specify a name for all assertion property sets.
Level: 1

Type: ERROR

Impact: Data

WSM-01756: The Property Set name field of context: {0} is empty

Cause: The Property Set Name field in one of the assertions was empty.

Action: Make sure that you specify a name for all assertion property sets.
Level: 1

Type: ERROR

Impact: Data

WSM-01757: The name attribute for the "Config" element is empty.

Cause: The name for the Config element was empty.

Action: Make sure that a name is specified for the Config element.
Level: 1

Type: ERROR

Impact: Data

WSM-01757: The name attribute for the "Config" element is empty.

Cause: The name for the Config element was empty.

Action: Make sure that a name is specified for the Config element.
Level: 1

Type: ERROR

Impact: Data

WSM-01758: The assertion name is empty.

Cause: The assertion name was empty.

Action: Make sure that the assertion name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01758: The assertion name is empty.

Cause: The assertion name was empty.

Action: Make sure that the assertion name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01759: The policy ID is empty.

Cause: The policy ID was empty.

Action: Make sure that the policy ID is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01759: The policy ID is empty.

Cause: The policy ID was empty.

Action: Make sure that the policy ID is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01760: The policy name is empty.

Cause: The policy name was empty.

Action: Make sure that the policy name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01760: The policy name is empty.

Cause: The policy name was empty.

Action: Make sure that the policy name is specified.
Level: 1

Type: ERROR

Impact: Data

WSM-01761: Specifying a policy ID for a child policy is not permitted : {0}.

Cause: Policy ID must not be specified for child policies.

Action: Remove the policy ID of the child policy.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01761: Specifying a policy ID for a child policy is not permitted : {0}.

Cause: Policy ID must not be specified for child policies.

Action: Remove the policy ID of the child policy.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01762: Specifying a policy name for a child policy is not permitted : {0}.

Cause: Policy name must not be specified for child policies.

Action: Remove the policy name of the child policy.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01762: Specifying a policy name for a child policy is not permitted : {0}.

Cause: Policy name must not be specified for child policies.

Action: Remove the policy name of the child policy.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01763: The value specified for the policy attachTo attribute {0}, does not match any of the supported values.

Cause: The value specified for the policy attachTo attribute did not match any of the supported values.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01763: The value specified for the policy attachTo attribute {0}, does not match any of the supported values.

Cause: The value specified for the policy attachTo attribute did not match any of the supported values.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01764: The value specified for the policy category {0} does not match any of the supported values.

Cause: The value specified for policy category attribute did not match any of the supported values.

Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01764: The value specified for the policy category {0} does not match any of the supported values.

Cause: The value specified for policy category attribute did not match any of the supported values.

Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01765: The data type of the value specified for property {0} is not supported.

Cause: The data type specified for the property did not match any of the supported data types.

Action: Specify a valid data type for the property. Consult the Oracle documentation for the supported data types.
Level: 1

Type: ERROR

Impact: Data

WSM-01765: The data type of the value specified for property {0} is not supported.

Cause: The data type specified for the property did not match any of the supported data types.

Action: Specify a valid data type for the property. Consult the Oracle documentation for the supported data types.
Level: 1

Type: ERROR

Impact: Data

WSM-01766: The assertion template ID cannot be empty.

Cause: The assertion template ID was empty.

Action: Specify a value for assertion template ID.
Level: 1

Type: ERROR

Impact: Data

WSM-01766: The assertion template ID cannot be empty.

Cause: The assertion template ID was empty.

Action: Specify a value for assertion template ID.
Level: 1

Type: ERROR

Impact: Data

WSM-01767: The assertion template name cannot be empty.

Cause: The assertion template name was empty.

Action: Specify a value for the assertion template name.
Level: 1

Type: ERROR

Impact: Data

WSM-01767: The assertion template name cannot be empty.

Cause: The assertion template name was empty.

Action: Specify a value for the assertion template name.
Level: 1

Type: ERROR

Impact: Data

WSM-01768: The value specified for the assertion template attachTo attribute {0} does not match any of the supported values.

Cause: The value specified for the assertion template attachTo attribute did not match any of the supported values.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01768: The value specified for the assertion template attachTo attribute {0} does not match any of the supported values.

Cause: The value specified for the assertion template attachTo attribute did not match any of the supported values.

Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01769: The value specified for the assertion template category {0} does not match any of the supported values.

Cause: The value specified for the assertion template category attribute did not match any of the supported values.

Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01769: The value specified for the assertion template category {0} does not match any of the supported values.

Cause: The value specified for the assertion template category attribute did not match any of the supported values.

Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01770: A value or default value is not specified for property {0}.

Cause: No value or default value was specified for the property.

Action: Specify a value or a default value for the property.
Level: 1

Type: ERROR

Impact: Data

WSM-01770: A value or default value is not specified for property {0}.

Cause: No value or default value was specified for the property.

Action: Specify a value or a default value for the property.
Level: 1

Type: ERROR

Impact: Data

WSM-01771: Attaching multiple reliable messaging policies is not supported. Only one reliable messaging policy can be attached to a policy subject

Cause: More than one reliable messaging policy was attached to a policy subject.

Action: Make sure that only one reliable messaging policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01771: Attaching multiple reliable messaging policies is not supported. Only one reliable messaging policy can be attached to a policy subject

Cause: More than one reliable messaging policy was attached to a policy subject.

Action: Make sure that only one reliable messaging policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01772: Attaching multiple Message Transmission Optimization Mechanism (MTOM) policies is not supported. Only one MTOM policy can be attached to a policy subject.

Cause: More than one MTOM policy was attached to a policy subject.

Action: Make sure that only one reliable MTOM is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01772: Attaching multiple Message Transmission Optimization Mechanism (MTOM) policies is not supported. Only one MTOM policy can be attached to a policy subject.

Cause: More than one MTOM policy was attached to a policy subject.

Action: Make sure that only one reliable MTOM is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01773: Attaching multiple WS-Addressing policies is not supported. Only one WS-Addressing policy can be attached to a policy subject.

Cause: The user attached more than one WS-Addressing policy.

Action: Make sure that only one reliable WS-Addressing is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01773: Attaching multiple WS-Addressing policies is not supported. Only one WS-Addressing policy can be attached to a policy subject.

Cause: The user attached more than one WS-Addressing policy.

Action: Make sure that only one reliable WS-Addressing is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01774: The policy "{0}" cannot be attached to policy subject "{1}" having unsupported subject type "{2}".

Cause: A policy was attached to an unsupported policy subject.

Action: Make sure that the policy subject supports policy attachment. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01774: The policy "{0}" cannot be attached to policy subject "{1}" having unsupported subject type "{2}".

Cause: A policy was attached to an unsupported policy subject.

Action: Make sure that the policy subject supports policy attachment. Consult the Oracle documentation for the supported values.
Level: 1

Type: ERROR

Impact: Data

WSM-01775: The policy "{0}" cannot be attached to ResourcePattern "{1}" SubjectType "{2}" of attachTo "{3}" since it may only be used with "{4}".

Cause: An incompatible policy was attached to the policy subject.

Action: Make sure that the attached policy is compatible with the policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01775: The policy "{0}" cannot be attached to ResourcePattern "{1}" SubjectType "{2}" of attachTo "{3}" since it may only be used with "{4}".

Cause: An incompatible policy was attached to the policy subject.

Action: Make sure that the attached policy is compatible with the policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01776: The policy reference "{0}" is invalid.

Cause: The policy reference was invalid because the policy did not exist.

Action: Make sure that the referenced policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01776: The policy reference "{0}" is invalid.

Cause: The policy reference was invalid because the policy did not exist.

Action: Make sure that the referenced policy exists in the policy store.
Level: 1

Type: ERROR

Impact: Data

WSM-01777: Attaching multiple authorization security policies is not supported. Only one authorization security policy can be attached to a policy subject.

Cause: More than one authorization security policy was attached to a policy subject.

Action: Make sure that only one authorization security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01777: Attaching multiple authorization security policies is not supported. Only one authorization security policy can be attached to a policy subject.

Cause: More than one authorization security policy was attached to a policy subject.

Action: Make sure that only one authorization security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01778: Attaching multiple authentication security policies is not supported. Only one authentication security policy can be attached to a policy subject.

Cause: More than one authentication security policy was attached to a policy subject.

Action: Make sure that only one authentication security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01778: Attaching multiple authentication security policies is not supported. Only one authentication security policy can be attached to a policy subject.

Cause: More than one authentication security policy was attached to a policy subject.

Action: Make sure that only one authentication security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01779: Attaching multiple message protection security policies is not supported. Only one message protection security policy can be attached to a policy subject.

Cause: More than one message protection security policy was attached to a policy subject.

Action: Make sure that only one message protection security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01779: Attaching multiple message protection security policies is not supported. Only one message protection security policy can be attached to a policy subject.

Cause: More than one message protection security policy was attached to a policy subject.

Action: Make sure that only one message protection security policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01780: The policy reference category and the policy category do not match.

Cause: There was a mismatch between the policy reference category and the policy category.

Action: Ensure that the policy reference category matches the policy category.
Level: 1

Type: ERROR

Impact: Data

WSM-01780: The policy reference category and the policy category do not match.

Cause: There was a mismatch between the policy reference category and the policy category.

Action: Ensure that the policy reference category matches the policy category.
Level: 1

Type: ERROR

Impact: Data

WSM-01781: Validation failure due to generic error.

Cause: A generic internal error occurred.

Action: Consult the diagnostic logs for details.
Level: 1

Type: ERROR

Impact: Data

WSM-01781: Validation failure due to generic error.

Cause: A generic internal error occurred.

Action: Consult the diagnostic logs for details.
Level: 1

Type: ERROR

Impact: Data

WSM-01782: Policy contains no assertions. A policy must contain at least one assertion.

Cause: The policy did not contain any assertions.

Action: Make sure that the policy contains at least one assertion.
Level: 1

Type: ERROR

Impact: Data

WSM-01782: Policy contains no assertions. A policy must contain at least one assertion.

Cause: The policy did not contain any assertions.

Action: Make sure that the policy contains at least one assertion.
Level: 1

Type: ERROR

Impact: Data

WSM-01783: Guard does not contain any of the three elements of resource-match, action-match and constraint-match.

Cause: Guard does not contain any of the three elments of resource-match, action-match and constraint-match.

Action: Make sure that at least one of three elements of resource-match, action-match and constraint-match is specified with its corresponding value in the Guard element.
Level: 1

Type: ERROR

Impact: Data

WSM-01783: Guard does not contain any of the three elements of resource-match, action-match and constraint-match.

Cause: Guard does not contain any of the three elments of resource-match, action-match and constraint-match.

Action: Make sure that at least one of three elements of resource-match, action-match and constraint-match is specified with its corresponding value in the Guard element.
Level: 1

Type: ERROR

Impact: Data

WSM-01784: Validation not supported for Custom Documents. Only a Policy or PolicySet can be validated.

Cause: Validation is not supported for Custom Documents.

Action: Ensure that the document is either a Policy or a PolicySet.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01784: Validation not supported for Custom Documents. Only a Policy or PolicySet can be validated.

Cause: Validation is not supported for Custom Documents.

Action: Ensure that the document is either a Policy or a PolicySet.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01785: Signing or encryption of the soap fault is not supported.

Cause: The soap fault is to be signed or encrypted.

Action: Make sure that the soap fault is not to be signed or encrypted.
Level: 1

Type: ERROR

Impact: Data

WSM-01785: Signing or encryption of the soap fault is not supported.

Cause: The soap fault is to be signed or encrypted.

Action: Make sure that the soap fault is not to be signed or encrypted.
Level: 1

Type: ERROR

Impact: Data

WSM-01786: Attaching multiple STS-Config policies is not supported. Only one STS-Config policy can be attached to a policy subject.

Cause: More than one sts-config policy was attached to a policy subject.

Action: Make sure that only one sts-config policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01786: Attaching multiple STS-Config policies is not supported. Only one STS-Config policy can be attached to a policy subject.

Cause: More than one sts-config policy was attached to a policy subject.

Action: Make sure that only one sts-config policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01791: Combination of a sts-config policy and a non sts authentication/message protection policy is not valid.

Cause: sts-config policy and non sts policy was attached to a policy subject.

Action: Make sure that a sts-config policy and a non sts config policy are not attached together to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01791: Combination of a sts-config policy and a non sts authentication/message protection policy is not valid.

Cause: sts-config policy and non sts policy was attached to a policy subject.

Action: Make sure that a sts-config policy and a non sts config policy are not attached together to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01792: Attachment of a sts-config policy without any sts policy is invalid. Attach a valid sts policy together with a sts-config policy.

Cause: Sts policy was attached without sts-config policy to a policy subject.

Action: Make sure that a sts config policy is attached together with a sts policy to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01792: Attachment of a sts-config policy without any sts policy is invalid. Attach a valid sts policy together with a sts-config policy.

Cause: Sts policy was attached without sts-config policy to a policy subject.

Action: Make sure that a sts config policy is attached together with a sts policy to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01801: The type of resources expression is empty or missing.

Cause: The value specified for the appliesTo attribute was empty.

Action: Specify a valid non-empty value for the appliesTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01801: The type of resources expression is empty or missing.

Cause: The value specified for the appliesTo attribute was empty.

Action: Specify a valid non-empty value for the appliesTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01802: The type of resources expression "{0}" is not supported.

Cause: The value specified for the appliesTo attribute was invalid.

Action: Specify a valid value for the appliesTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01802: The type of resources expression "{0}" is not supported.

Cause: The value specified for the appliesTo attribute was invalid.

Action: Specify a valid value for the appliesTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01811: The attachment expression is empty or missing. A non-empty expression with a function is expected.

Cause: The value specified for the attachTo attribute was empty.

Action: Specify a valid, non-empty value for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01811: The attachment expression is empty or missing. A non-empty expression with a function is expected.

Cause: The value specified for the attachTo attribute was empty.

Action: Specify a valid, non-empty value for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-01812: The function "{2}" at index {1} in attachment expression "{0}" is empty. A function requires a non-empty value.

Cause: The argument for a function was missing or empty.

Action: Specify a valid, non-empty value for the function argument.
Level: 1

Type: ERROR

Impact: Data

WSM-01812: The function "{2}" at index {1} in attachment expression "{0}" is empty. A function requires a non-empty value.

Cause: The argument for a function was missing or empty.

Action: Specify a valid, non-empty value for the function argument.
Level: 1

Type: ERROR

Impact: Data

WSM-01813: The function "{2}" at index {1} in attachment expression "{0}" duplicates a previous function. A function may only appear once in an expression.

Cause: A function appeared more than once in an attachment expression.

Action: Remove the duplicated function from the expression.
Level: 1

Type: ERROR

Impact: Data

WSM-01813: The function "{2}" at index {1} in attachment expression "{0}" duplicates a previous function. A function may only appear once in an expression.

Cause: A function appeared more than once in an attachment expression.

Action: Remove the duplicated function from the expression.
Level: 1

Type: ERROR

Impact: Data

WSM-01814: The function "{2}" is not expected at index {1} in attachment expression "{0}". An operator is expected at this point.

Cause: A function was found in an attachment expression where an operator was expected.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01814: The function "{2}" is not expected at index {1} in attachment expression "{0}". An operator is expected at this point.

Cause: A function was found in an attachment expression where an operator was expected.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01815: A function is expected at index {1} in attachment expression "{0}".

Cause: The attachment expression ended with an operator.

Action: Remove the dangling operator or add the missing function.
Level: 1

Type: ERROR

Impact: Data

WSM-01815: A function is expected at index {1} in attachment expression "{0}".

Cause: The attachment expression ended with an operator.

Action: Remove the dangling operator or add the missing function.
Level: 1

Type: ERROR

Impact: Data

WSM-01816: The operator "{2}" at index {1} in attachment expression "{0}" is not supported. "and" is the only supported operator.

Cause: An unrecognized operator was found in an attachment expression.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01816: The operator "{2}" at index {1} in attachment expression "{0}" is not supported. "and" is the only supported operator.

Cause: An unrecognized operator was found in an attachment expression.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01817: The text "{2}" at index {1} in attachment expression "{0}" is not expected. A function is expected at this point.

Cause: An unrecognized block of text was found in an attachment expression where a function was expected.

Action: Specify a valid function in the expression.
Level: 1

Type: ERROR

Impact: Data

WSM-01817: The text "{2}" at index {1} in attachment expression "{0}" is not expected. A function is expected at this point.

Cause: An unrecognized block of text was found in an attachment expression where a function was expected.

Action: Specify a valid function in the expression.
Level: 1

Type: ERROR

Impact: Data

WSM-01818: The text "{2}" at index {1} in attachment expression "{0}" is unrecognized. The operator "and" is expected at this point.

Cause: An unrecognized block of text was found in an attachment expression where an operator was expected.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01818: The text "{2}" at index {1} in attachment expression "{0}" is unrecognized. The operator "and" is expected at this point.

Cause: An unrecognized block of text was found in an attachment expression where an operator was expected.

Action: Specify the "and" operator between each function.
Level: 1

Type: ERROR

Impact: Data

WSM-01821: The function "{0}" in attachment expression "{1}" is incompatible with "{2}" type of resources.

Cause: A function was found in an attachment expression that is not usable with the type of resource.

Action: Specify a function that is compatible with the associated type of resource.
Level: 1

Type: ERROR

Impact: Data

WSM-01821: The function "{0}" in attachment expression "{1}" is incompatible with "{2}" type of resources.

Cause: A function was found in an attachment expression that is not usable with the type of resource.

Action: Specify a function that is compatible with the associated type of resource.
Level: 1

Type: ERROR

Impact: Data

WSM-01822: The function "{0}" in attachment expression "{1}" is not supported for attachment.

Cause: A function was found in an attachment expression that is not usable for attachment.

Action: Specify a function that is compatible with the associated type of resource.
Level: 1

Type: ERROR

Impact: Data

WSM-01822: The function "{0}" in attachment expression "{1}" is not supported for attachment.

Cause: A function was found in an attachment expression that is not usable for attachment.

Action: Specify a function that is compatible with the associated type of resource.
Level: 1

Type: ERROR

Impact: Data

WSM-01823: Attaching multiple policies of category "{0}" is not supported. Policies in list [ "{1}" ] already have the category, current policy "{2}" also has that category.

Cause: More than one policy with the same category was attached to a policy subject.

Action: Make sure that only one such policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01823: Attaching multiple policies of category "{0}" is not supported. Policies in list [ "{1}" ] already have the category, current policy "{2}" also has that category.

Cause: More than one policy with the same category was attached to a policy subject.

Action: Make sure that only one such policy is attached to a policy subject.
Level: 1

Type: ERROR

Impact: Data

WSM-01824: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.

Cause: The Policy category provided was not valid.

Action: Verify that the Policy category is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01824: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.

Cause: The Policy category provided was not valid.

Action: Verify that the Policy category is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-01825: Policy: {0} contains unsupported assertions.

Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-01825: Policy: {0} contains unsupported assertions.

Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-02000: Cannot retrieve assertion template {0}.

Cause: A failure occurred while retrieving the assertion template from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02000: Cannot retrieve assertion template {0}.

Cause: A failure occurred while retrieving the assertion template from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02001: Cannot serialize XML to policy attachment.

Cause: The policy attachment XML was not well formed, or the XML did not follow the policy attachment schema.

Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.
Level: 1

Type: ERROR

Impact: Data

WSM-02001: Cannot serialize XML to policy attachment.

Cause: The policy attachment XML was not well formed, or the XML did not follow the policy attachment schema.

Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.
Level: 1

Type: ERROR

Impact: Data

WSM-02002: Cannot retrieve policies.

Cause: A failure occurred while retrieving policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02002: Cannot retrieve policies.

Cause: A failure occurred while retrieving policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02003: Cannot retrieve policy references for resource pattern {0}.

Cause: A failure occurred while retrieving policy references from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02003: Cannot retrieve policy references for resource pattern {0}.

Cause: A failure occurred while retrieving policy references from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02004: Cannot search policies for condition {0}.

Cause: A failure occurred while searching for policies in the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02004: Cannot search policies for condition {0}.

Cause: A failure occurred while searching for policies in the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02005: Cannot perform policy compatibility check for policies {0}.

Cause: An internal error was encountered while performing the policy compatibility check.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02005: Cannot perform policy compatibility check for policies {0}.

Cause: An internal error was encountered while performing the policy compatibility check.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02006: Cannot add policies {0} to data store.

Cause: A failure occurred while adding policies to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02006: Cannot add policies {0} to data store.

Cause: A failure occurred while adding policies to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02007: Cannot delete assertion templates {0}.

Cause: A failure occurred while deleting assertion templates from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02007: Cannot delete assertion templates {0}.

Cause: A failure occurred while deleting assertion templates from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02008: Cannot delete policies {0}.

Cause: A failure occurred while deleting policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02008: Cannot delete policies {0}.

Cause: A failure occurred while deleting policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02009: Cannot delete all assertion templates from the data store.

Cause: A failure occurred while deleting all assertion templates from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02009: Cannot delete all assertion templates from the data store.

Cause: A failure occurred while deleting all assertion templates from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02010: Unable to delete all policies from the data store.

Cause: A failure occurred while deleting all policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02010: Unable to delete all policies from the data store.

Cause: A failure occurred while deleting all policies from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02011: Cannot delete assertion template {0}.

Cause: A failure occurred while deleting the specified assertion template from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02011: Cannot delete assertion template {0}.

Cause: A failure occurred while deleting the specified assertion template from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02012: Cannot delete policy {0}.

Cause: A failure occurred while deleting the specified policy from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02012: Cannot delete policy {0}.

Cause: A failure occurred while deleting the specified policy from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02013: Cannot retrieve policy configuration {0}.

Cause: A failure occurred while retrieving the policy configuration.

Action: Check the policy configuration, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02013: Cannot retrieve policy configuration {0}.

Cause: A failure occurred while retrieving the policy configuration.

Action: Check the policy configuration, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02014: The value for the attachTo attribute {0} is not valid.

Cause: The value for the attachTo attribute is not valid.

Action: Consult Oracle documentation for the valid values for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-02014: The value for the attachTo attribute {0} is not valid.

Cause: The value for the attachTo attribute is not valid.

Action: Consult Oracle documentation for the valid values for the attachTo attribute.
Level: 1

Type: ERROR

Impact: Data

WSM-02015: Cannot retrieve object(s) due to Java RuntimeException.

Cause: The unexpected RuntimeException was encountered while trying to access data store.

Action: Check the log file for possible causes, and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02015: Cannot retrieve object(s) due to Java RuntimeException.

Cause: The unexpected RuntimeException was encountered while trying to access data store.

Action: Check the log file for possible causes, and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02016: Cannot retrieve timestamp for the last data store update.

Cause: A problem occurred while accessing the repository.

Action: Examine the logs for the cause of the failure.
Level: 1

Type: WARNING

Impact: Data

WSM-02016: Cannot retrieve timestamp for the last data store update.

Cause: A problem occurred while accessing the repository.

Action: Examine the logs for the cause of the failure.
Level: 1

Type: WARNING

Impact: Data

WSM-02044: Cannot save assertion template {0} to data store.

Cause: Another process was trying to update the same assertion template.

Action: Ensure that no other process is trying to update the same assertion template object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02044: Cannot save assertion template {0} to data store.

Cause: Another process was trying to update the same assertion template.

Action: Ensure that no other process is trying to update the same assertion template object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02045: Cannot delete policy version from data store.

Cause: Failure occurred while deleting policy versions from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02045: Cannot delete policy version from data store.

Cause: Failure occurred while deleting policy versions from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02046: Cannot delete assertion template versions from data store.

Cause: Failure occurred while deleting assertion template versions from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02046: Cannot delete assertion template versions from data store.

Cause: Failure occurred while deleting assertion template versions from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02047: Unable to create multiple policies.

Cause: Failure occurred while creating multiple policies

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02047: Unable to create multiple policies.

Cause: Failure occurred while creating multiple policies

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02048: Unable to update multiple policies.

Cause: Failure occurred while updating multiple policies.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02048: Unable to update multiple policies.

Cause: Failure occurred while updating multiple policies.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02049: Unable to update the assertion template.

Cause: Failure occurred while updating an assertion template.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02049: Unable to update the assertion template.

Cause: Failure occurred while updating an assertion template.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02050: Unable to set the older version of a policy as the latest version.

Cause: Failure occurred while setting an older version of a policy as the latest version.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02050: Unable to set the older version of a policy as the latest version.

Cause: Failure occurred while setting an older version of a policy as the latest version.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02051: Unable to add resources to policy attachment.

Cause: Failure occurred while trying to add resources to a policy attachment.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02051: Unable to add resources to policy attachment.

Cause: Failure occurred while trying to add resources to a policy attachment.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02052: Unable to remove resources from policy attachment.

Cause: Failure occurred while trying to remove resources from policy attachment.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02052: Unable to remove resources from policy attachment.

Cause: Failure occurred while trying to remove resources from policy attachment.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02053: Unable to set the older version of a policy as the latest version.

Cause: Failure occurred while setting an older version of a policy as the latest version.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02053: Unable to set the older version of a policy as the latest version.

Cause: Failure occurred while setting an older version of a policy as the latest version.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02054: Failure in looking up EJB component.The EJB JNDI name is "{0}", the provider URL is "{1}"..

Cause: Failure occurred in looking up requested component on the application server.

Action: Make sure that the right configuration is passed for the EJB lookup and retry the operation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-02054: Failure in looking up EJB component.The EJB JNDI name is "{0}", the provider URL is "{1}"..

Cause: Failure occurred in looking up requested component on the application server.

Action: Make sure that the right configuration is passed for the EJB lookup and retry the operation.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-02055: Failure calculating smart digest for policy {0}

Cause: Failure occurred in calculating smart digest when updating or creating policy.

Action: You can ignore this message or you can retry the operation. Increase the log levels for more details as to the underlying cause for the smart digest calculation failure.
Level: 1

Type: WARNING

Impact: Data

WSM-02055: Failure calculating smart digest for policy {0}

Cause: Failure occurred in calculating smart digest when updating or creating policy.

Action: You can ignore this message or you can retry the operation. Increase the log levels for more details as to the underlying cause for the smart digest calculation failure.
Level: 1

Type: WARNING

Impact: Data

WSM-02056: Unable to locate the RMI port for communication

Cause: Failure occurred when looking up RMI port for the application server.

Action: Confirm that the RMI port settings are correct in the application server configuration and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02056: Unable to locate the RMI port for communication

Cause: Failure occurred when looking up RMI port for the application server.

Action: Confirm that the RMI port settings are correct in the application server configuration and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02057: Mismatch in EJB lookup. Expected object type: {0}, Actual object type: {1}.

Cause: Mismatch in expected EJB object type and actual object type.

Action: Confirm that the Policy Manager EJB is configured correctly, and its version is compatible with the client.
Level: 1

Type: WARNING

Impact: Data

WSM-02057: Mismatch in EJB lookup. Expected object type: {0}, Actual object type: {1}.

Cause: Mismatch in expected EJB object type and actual object type.

Action: Confirm that the Policy Manager EJB is configured correctly, and its version is compatible with the client.
Level: 1

Type: WARNING

Impact: Data

WSM-02058: Failure occurred in Policy Manager while seeding policies in data store.

Cause: Failure occurred in Policy Manager while seeding policies in data store.

Action: Make sure the correct configuration is passed to Policy Manager for seeding policies.
Level: 1

Type: ERROR

Impact: Data

WSM-02058: Failure occurred in Policy Manager while seeding policies in data store.

Cause: Failure occurred in Policy Manager while seeding policies in data store.

Action: Make sure the correct configuration is passed to Policy Manager for seeding policies.
Level: 1

Type: ERROR

Impact: Data

WSM-02059: Version-related operations are not supported for the configured datastore.

Cause: Version-related operations are not supported for the configured datastore.

Action: Make sure the datastore used is a database and not file-system based.
Level: 1

Type: ERROR

Impact: Data

WSM-02059: Version-related operations are not supported for the configured datastore.

Cause: Version-related operations are not supported for the configured datastore.

Action: Make sure the datastore used is a database and not file-system based.
Level: 1

Type: ERROR

Impact: Data

WSM-02060: EJB lookup failed due to invalid lookup configuration

Cause: Unable to perform EJB lookup.

Action: Make sure that valid JNDI name and JNDI properties are supplied for EJB lookups.
Level: 1

Type: ERROR

Impact: Data

WSM-02060: EJB lookup failed due to invalid lookup configuration

Cause: Unable to perform EJB lookup.

Action: Make sure that valid JNDI name and JNDI properties are supplied for EJB lookups.
Level: 1

Type: ERROR

Impact: Data

WSM-02061: Failed to close Initial Context created for EJB lookups

Cause: Unable to close the Java Initial Context.

Action: Confirm that no other component is using the context and there are no memory leaks.
Level: 1

Type: ERROR

Impact: Data

WSM-02061: Failed to close Initial Context created for EJB lookups

Cause: Unable to close the Java Initial Context.

Action: Confirm that no other component is using the context and there are no memory leaks.
Level: 1

Type: ERROR

Impact: Data

WSM-02062: Unable to retrieve credentials for the specified csf-key {0}

Cause: Credential configuration in the policy accessor configuration file was incorrect.

Action: Configure policy with valid CSF key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02062: Unable to retrieve credentials for the specified csf-key {0}

Cause: Credential configuration in the policy accessor configuration file was incorrect.

Action: Configure policy with valid CSF key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02063: The password credentials cannot be obtained from the Credential Store.

Cause: Failure occurred while querying for credentials from CSF.

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02063: The password credentials cannot be obtained from the Credential Store.

Cause: Failure occurred while querying for credentials from CSF.

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02064: The Java Object Name {0} being created is invalid.

Cause: An error occurred while creating the specifed JMX ObjectName.

Action: Check the MBean ObjectName being instantiated and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02064: The Java Object Name {0} being created is invalid.

Cause: An error occurred while creating the specifed JMX ObjectName.

Action: Check the MBean ObjectName being instantiated and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02065: The MBean being registered is not a JMX compliant MBean

Cause: Failed to register MBean.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02065: The MBean being registered is not a JMX compliant MBean

Cause: Failed to register MBean.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02066: Failed to get server context

Cause: Failed to get server initial context.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02066: Failed to get server context

Cause: Failed to get server initial context.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02067: Cannot register MBean {0}, an MBean with same name already exists on the server

Cause: The MBean being registered already exists on the server.

Action: Check the name of the MBean being registered and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02067: Cannot register MBean {0}, an MBean with same name already exists on the server

Cause: The MBean being registered already exists on the server.

Action: Check the name of the MBean being registered and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02068: Failed to register MBean {0}

Cause: Failed to register MBean.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02068: Failed to register MBean {0}

Cause: Failed to register MBean.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02069: Failed to deregister MBean {0}

Cause: Failed to deregister MBean.

Action: No action needs to be taken at this time. However, if the server exhibits any erraneous behavior, try restarting the server.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02069: Failed to deregister MBean {0}

Cause: Failed to deregister MBean.

Action: No action needs to be taken at this time. However, if the server exhibits any erraneous behavior, try restarting the server.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02070: Failed to load updates.xml file

Cause: Failed to load updates.xml file.

Action: Make sure that the wsm-seed-policies.jar exists and it corresponds to the latest version and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02070: Failed to load updates.xml file

Cause: Failed to load updates.xml file.

Action: Make sure that the wsm-seed-policies.jar exists and it corresponds to the latest version and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02071: No entries found in the wsm-seed-policies.jar file

Cause: The wsm-seed-policies.jar file does not contain any entries.

Action: Make sure that the wsm-seed-policies.jar file is not corrupted and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02071: No entries found in the wsm-seed-policies.jar file

Cause: The wsm-seed-policies.jar file does not contain any entries.

Action: Make sure that the wsm-seed-policies.jar file is not corrupted and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02072: Failed to load wsm-seed-policies.jar file

Cause: The wsm-seed-policies.jar file could not be loaded.

Action: Make sure that the wsm-seed-policies.jar file exists in the application classpath and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02072: Failed to load wsm-seed-policies.jar file

Cause: The wsm-seed-policies.jar file could not be loaded.

Action: Make sure that the wsm-seed-policies.jar file exists in the application classpath and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02073: Unable to connect to the WSM datastore

Cause: Unable to connect to the WSM datastore.

Action: Make sure the datastore settings are correctly set in the wsm-pm application and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02073: Unable to connect to the WSM datastore

Cause: Unable to connect to the WSM datastore.

Action: Make sure the datastore settings are correctly set in the wsm-pm application and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02074: Invalid arguments passed to find the difference in shipped documents between versions

Cause: The arguments supplied to find difference between repository versions are invalid.

Action: Make sure that the arguments passed comply with the Javadoc requirements and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02074: Invalid arguments passed to find the difference in shipped documents between versions

Cause: The arguments supplied to find difference between repository versions are invalid.

Action: Make sure that the arguments passed comply with the Javadoc requirements and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02075: Cannot unregister MBean {0}. since it does not exist on the server

Cause: The MBean being unregistered does not exists on the sever.

Action: Check the name of the MBean being unregistered and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02075: Cannot unregister MBean {0}. since it does not exist on the server

Cause: The MBean being unregistered does not exists on the sever.

Action: Check the name of the MBean being unregistered and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02076: Unable to get an instance of PortableMBeanFactory.

Cause: Could not obtain an instance of PortableMBeanFactory.

Action: Check the configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02076: Unable to get an instance of PortableMBeanFactory.

Cause: Could not obtain an instance of PortableMBeanFactory.

Action: Check the configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02077: Unable to get a handle to MBeanServer.

Cause: Could not obtain an instance to MBeanServer

Action: Check the configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02077: Unable to get a handle to MBeanServer.

Cause: Could not obtain an instance to MBeanServer

Action: Check the configuration and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02078: Unable to construct MBean ObjectName due to null object name string.

Cause: MBean object name is invalid.

Action: Make sure that the supplied object name is not null and retry the lookup.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02078: Unable to construct MBean ObjectName due to null object name string.

Cause: MBean object name is invalid.

Action: Make sure that the supplied object name is not null and retry the lookup.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02079: Failed to connect to Policy Manager instance due to error "{0}".

Cause: Connection to Policy Manager failed.

Action: Make sure that the WSM Policy Manager is up and running and retry the operation.
Level: 1

Type: TRACE

Impact: Data

WSM-02079: Failed to connect to Policy Manager instance due to error "{0}".

Cause: Connection to Policy Manager failed.

Action: Make sure that the WSM Policy Manager is up and running and retry the operation.
Level: 1

Type: TRACE

Impact: Data

WSM-02080: Failure to get executor due to underlying error "{0}".

Cause: Failed to get the correct executor to perform requested action.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02080: Failure to get executor due to underlying error "{0}".

Cause: Failed to get the correct executor to perform requested action.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02081: Failed to login to perform requested action.

Cause: Failed to login to perform requested action.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02081: Failed to login to perform requested action.

Cause: Failed to login to perform requested action.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02082: Unsupported callback handler.

Cause: Unsupported callback handler.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02082: Unsupported callback handler.

Cause: Unsupported callback handler.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02083: Invalid security configuration entry name.

Cause: Invalid security configuration entry name.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02083: Invalid security configuration entry name.

Cause: Invalid security configuration entry name.

Action: Check the system security configuration and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02084: Access denied. Permission "{0}" is required to access the wsm policy manager "{1}" method "{2}".

Cause: Permission required to access the policy manager API.

Action: Ensure that the user accessing policy manager api has required permission.
Level: 1

Type: ERROR

Impact: Security

WSM-02084: Access denied. Permission "{0}" is required to access the wsm policy manager "{1}" method "{2}".

Cause: Permission required to access the policy manager API.

Action: Ensure that the user accessing policy manager api has required permission.
Level: 1

Type: ERROR

Impact: Security

WSM-02100: Error parsing the resource from String {0}.

Cause: An XML parsing failure occurred while creating the document from the passed String.

Action: Verify that the passed String is a well-formed XML and follows the XML schema for its object type.
Level: 1

Type: ERROR

Impact: Data

WSM-02100: Error parsing the resource from String {0}.

Cause: An XML parsing failure occurred while creating the document from the passed String.

Action: Verify that the passed String is a well-formed XML and follows the XML schema for its object type.
Level: 1

Type: ERROR

Impact: Data

WSM-02101: Generic Oracle WSM Policy Manager error.

Cause: An internal error occurred during the Policy Manager operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02101: Generic Oracle WSM Policy Manager error.

Cause: An internal error occurred during the Policy Manager operation.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02102: The policy name is missing.

Cause: The policy name was missing.

Action: Make sure that the supplied policy has a valid name, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02102: The policy name is missing.

Cause: The policy name was missing.

Action: Make sure that the supplied policy has a valid name, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02103: The assertion template name is missing.

Cause: The assertion template name was missing.

Action: Make sure that the supplied assertion template has a valid name, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02103: The assertion template name is missing.

Cause: The assertion template name was missing.

Action: Make sure that the supplied assertion template has a valid name, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02104: The assertion template from file {0} cannot be parsed.

Cause: A failure occurred while parsing the assertion template from the file.

Action: Check for any syntax errors in the file specified, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02104: The assertion template from file {0} cannot be parsed.

Cause: A failure occurred while parsing the assertion template from the file.

Action: Check for any syntax errors in the file specified, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02105: The policy search query is not valid.

Cause: An invalid policy search condition was specified.

Action: Check the search query and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02105: The policy search query is not valid.

Cause: An invalid policy search condition was specified.

Action: Check the search query and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02106: Cannot retrieve policy {0}.

Cause: A failure occurred while retrieving the policy.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02106: Cannot retrieve policy {0}.

Cause: A failure occurred while retrieving the policy.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02107: Cannot update policy {0}.

Cause: A failure occurred while updating the policy.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02107: Cannot update policy {0}.

Cause: A failure occurred while updating the policy.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02108: Cannot retrieve version {0} of policy {1}.

Cause: A failure occurred while retrieving the requested version of the policy.

Action: Check the version and policy details and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02108: Cannot retrieve version {0} of policy {1}.

Cause: A failure occurred while retrieving the requested version of the policy.

Action: Check the version and policy details and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02109: Cannot retrieve version {0} of assertion template {1}.

Cause: A failure occurred while retrieving the requested version of the specified assertion template.

Action: Check the version and assertion template details, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02109: Cannot retrieve version {0} of assertion template {1}.

Cause: A failure occurred while retrieving the requested version of the specified assertion template.

Action: Check the version and assertion template details, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02111: The configuration name is missing.

Cause: The policy configuration name was missing.

Action: Provide a valid name for the policy configuration, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02111: The configuration name is missing.

Cause: The policy configuration name was missing.

Action: Provide a valid name for the policy configuration, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02112: The policy attachment name is missing.

Cause: The policy attachment name was missing.

Action: Provide a valid policy attachment name, and retry the operation
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02112: The policy attachment name is missing.

Cause: The policy attachment name was missing.

Action: Provide a valid policy attachment name, and retry the operation
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02113: Error in creating the policy attachment {0}.

Cause: A failure occurred while creating the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02113: Error in creating the policy attachment {0}.

Cause: A failure occurred while creating the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02114: Error in deleting the policy attachment {0}.

Cause: A failure occurred while deleting the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02114: Error in deleting the policy attachment {0}.

Cause: A failure occurred while deleting the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02115: Error in updating the policy attachment {0}.

Cause: A failure occurred while updating the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02115: Error in updating the policy attachment {0}.

Cause: A failure occurred while updating the policy attachment.

Action: Check the specified values and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02116: The resource pattern used in the search is empty or contains wildcard characters like %.

Cause: The resource pattern specified in the search was empty or contained wildcard characters such as %.

Action: Correct the search criteria and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02116: The resource pattern used in the search is empty or contains wildcard characters like %.

Cause: The resource pattern specified in the search was empty or contained wildcard characters such as %.

Action: Correct the search criteria and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02117: Cannot delete all policy attachments from the data store.

Cause: A failure occurred when deleting multiple policy attachments from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02117: Cannot delete all policy attachments from the data store.

Cause: A failure occurred when deleting multiple policy attachments from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02118: The query service cannot be created.

Cause: A failure occurred while creating the query service.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02118: The query service cannot be created.

Cause: A failure occurred while creating the query service.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02119: The update service cannot be created.

Cause: A failure occurred while creating the update service.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02119: The update service cannot be created.

Cause: A failure occurred while creating the update service.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02120: Unable to connect to the policy access service.

Cause: A connection to the policy access service could not be created.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02120: Unable to connect to the policy access service.

Cause: A connection to the policy access service could not be created.

Action: Check the Policy Manager configuration and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02121: Internal system error, cannot look up credential.

Cause: A failure occurred while looking up credentials due to an internal system configuration error.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02121: Internal system error, cannot look up credential.

Cause: A failure occurred while looking up credentials due to an internal system configuration error.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02122: The protocol is invalid.

Cause: The protocol was invalid.

Action: Check Oracle documentation for the supported protocols.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02122: The protocol is invalid.

Cause: The protocol was invalid.

Action: Check Oracle documentation for the supported protocols.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02123: Cannot access policy-accessor-config.xml file.

Cause: A failure occurred while reading the policy-accessor-config.xml file.

Action: Ensure that the file exists.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02123: Cannot access policy-accessor-config.xml file.

Cause: A failure occurred while reading the policy-accessor-config.xml file.

Action: Ensure that the file exists.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02124: Cannot create policy access service.

Cause: The user connecting to the policy access service did not have sufficient privileges.

Action: Confirm that the user has rights to connect to the policy access service, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02124: Cannot create policy access service.

Cause: The user connecting to the policy access service did not have sufficient privileges.

Action: Confirm that the user has rights to connect to the policy access service, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02125: Cannot perform policy compatibility check.

Cause: A failure occurred while performing a policy compatibility check.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02125: Cannot perform policy compatibility check.

Cause: A failure occurred while performing a policy compatibility check.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02126: Cannot add policy {0} to data store.

Cause: A failure occurred while adding the policy to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02126: Cannot add policy {0} to data store.

Cause: A failure occurred while adding the policy to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02127: Cannot add assertion template {0} to data store.

Cause: A failure occurred while adding the assertion template to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02127: Cannot add assertion template {0} to data store.

Cause: A failure occurred while adding the assertion template to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02128: Cannot read WSDL.

Cause: A failure occurred while parsing the WSDL.

Action: Confirm that the supplied WSDL follows the WSDL XML schema.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02128: Cannot read WSDL.

Cause: A failure occurred while parsing the WSDL.

Action: Confirm that the supplied WSDL follows the WSDL XML schema.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02129: Cannot create policy service.

Cause: The user connecting to the policy service did not have sufficient privileges.

Action: Confirm that the user has privileges to connect to the policy service, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02129: Cannot create policy service.

Cause: The user connecting to the policy service did not have sufficient privileges.

Action: Confirm that the user has privileges to connect to the policy service, and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02130: Cannot retrieve policy attachment from data store.

Cause: A failure occurred while retrieving the policy attachment from the data store.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02130: Cannot retrieve policy attachment from data store.

Cause: A failure occurred while retrieving the policy attachment from the data store.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02131: Standard WSDL is provided, but ORAWSDL is required.

Cause: The WSDL did not have the expected Oracle extensions.

Action: Retry the operation with WSDL with Oracle Extensions.
Level: 1

Type: WARNING

Impact: Data

WSM-02131: Standard WSDL is provided, but ORAWSDL is required.

Cause: The WSDL did not have the expected Oracle extensions.

Action: Retry the operation with WSDL with Oracle Extensions.
Level: 1

Type: WARNING

Impact: Data

WSM-02132: Cannot find service {0} in WSDL.

Cause: The service was not found in the WSDL.

Action: Retry the operation with the correct parameters.
Level: 1

Type: WARNING

Impact: Data

WSM-02132: Cannot find service {0} in WSDL.

Cause: The service was not found in the WSDL.

Action: Retry the operation with the correct parameters.
Level: 1

Type: WARNING

Impact: Data

WSM-02133: Cannot find policies in WSDL.

Cause: No policies were found in the WSDL.

Action: Confirm that the supplied WSDL contains the correct policies.
Level: 1

Type: WARNING

Impact: Data

WSM-02133: Cannot find policies in WSDL.

Cause: No policies were found in the WSDL.

Action: Confirm that the supplied WSDL contains the correct policies.
Level: 1

Type: WARNING

Impact: Data

WSM-02134: Cannot access Policy Manager EJB.

Cause: The user connecting to the Policy Manager EJB did not have sufficient privileges.

Action: Confirm that the user has privileges to connect to the Policy Manager EJB, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02134: Cannot access Policy Manager EJB.

Cause: The user connecting to the Policy Manager EJB did not have sufficient privileges.

Action: Confirm that the user has privileges to connect to the Policy Manager EJB, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02135: Insufficient privileges for accessing the Policy Manager interface.

Cause: Caller's privileges for accessing the Policy Manager EJB were insufficient.

Action: Examine underlying errors for root cause.
Level: 1

Type: ERROR

Impact: Data

WSM-02135: Insufficient privileges for accessing the Policy Manager interface.

Cause: Caller's privileges for accessing the Policy Manager EJB were insufficient.

Action: Examine underlying errors for root cause.
Level: 1

Type: ERROR

Impact: Data

WSM-02136: Bulk update operations are not supported for file-based data stores.

Cause: The bulk update operation failed because the data store does not support transactions.

Action: Use a repository that supports transactions, for example, a database repository.
Level: 1

Type: ERROR

Impact: Data

WSM-02136: Bulk update operations are not supported for file-based data stores.

Cause: The bulk update operation failed because the data store does not support transactions.

Action: Use a repository that supports transactions, for example, a database repository.
Level: 1

Type: ERROR

Impact: Data

WSM-02138: Cannot save policy attachment {0} to data store.

Cause: A concurrent update failure occurred while saving the policy attachment in the data store.

Action: Make sure no other process is trying to update the same policy attachment object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02138: Cannot save policy attachment {0} to data store.

Cause: A concurrent update failure occurred while saving the policy attachment in the data store.

Action: Make sure no other process is trying to update the same policy attachment object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02139: Cannot save policy {0} to data store.

Cause: A concurrent update failure occurred while saving the policy in the data store.

Action: Make sure no other process is trying to update the same policy object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02139: Cannot save policy {0} to data store.

Cause: A concurrent update failure occurred while saving the policy in the data store.

Action: Make sure no other process is trying to update the same policy object and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02201: A comparator is required for a search criterion.

Cause: A search comparator was not provided.

Action: Supply a comparator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02201: A comparator is required for a search criterion.

Cause: A search comparator was not provided.

Action: Supply a comparator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02202: The comparator "{0}" is not supported for a numeric attribute search criterion.

Cause: The search comparator is not supported for numeric comparisons.

Action: Supply a comparator that supports numeric comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02202: The comparator "{0}" is not supported for a numeric attribute search criterion.

Cause: The search comparator is not supported for numeric comparisons.

Action: Supply a comparator that supports numeric comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02203: The comparator "{0}" is not supported for a text attribute search criterion.

Cause: The search comparator is not supported for numeric comparisons.

Action: Supply a comparator that supports numeric comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02203: The comparator "{0}" is not supported for a text attribute search criterion.

Cause: The search comparator is not supported for numeric comparisons.

Action: Supply a comparator that supports numeric comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02204: The comparator "UNKNOWN" is not supported for an attribute search criterion.

Cause: The search comparator UNKNOWN is not supported for attribute comparisons.

Action: Supply a comparator that supports attribute comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02204: The comparator "UNKNOWN" is not supported for an attribute search criterion.

Cause: The search comparator UNKNOWN is not supported for attribute comparisons.

Action: Supply a comparator that supports attribute comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02205: The search criterion "{0}" cannot be parsed.

Cause: The search criterion was corrupt or used an unrecognized schema.

Action: Supply a supported search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02205: The search criterion "{0}" cannot be parsed.

Cause: The search criterion was corrupt or used an unrecognized schema.

Action: Supply a supported search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02206: The document name "{0}" is not valid for a search criterion.

Cause: The document name contained illegal characters, such as a slash character.

Action: Supply a legal document name.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02206: The document name "{0}" is not valid for a search criterion.

Cause: The document name contained illegal characters, such as a slash character.

Action: Supply a legal document name.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02207: A document type is required for a search criterion.

Cause: The document type was null, whitespace, or empty.

Action: Supply a non-empty document type.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02207: A document type is required for a search criterion.

Cause: The document type was null, whitespace, or empty.

Action: Supply a non-empty document type.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02208: A document URI ends with a path separator.

Cause: The document URI ends with a path separator.

Action: Supply a document URI that does not appear to be a path.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02208: A document URI ends with a path separator.

Cause: The document URI ends with a path separator.

Action: Supply a document URI that does not appear to be a path.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02209: A document URI is required for a search criterion.

Cause: The document URI was empty.

Action: Supply a non-empty document URI.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02209: A document URI is required for a search criterion.

Cause: The document URI was empty.

Action: Supply a non-empty document URI.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02210: An element search criterion cannot be created with the child search expression "{0}" because it contains a non-attribute criterion.

Cause: The search expression contained one or more attribute criteria.

Action: Supply an expression containing only attribute criteria.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02210: An element search criterion cannot be created with the child search expression "{0}" because it contains a non-attribute criterion.

Cause: The search expression contained one or more attribute criteria.

Action: Supply an expression containing only attribute criteria.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02211: A number is required for a search criterion.

Cause: A number was not provided.

Action: Supply a valid number.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02211: A number is required for a search criterion.

Cause: A number was not provided.

Action: Supply a valid number.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02212: The search expression "{0}" contains invalid operator "{1}".

Cause: The search expression contained an invalid operator.

Action: Supply an expression with a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02212: The search expression "{0}" contains invalid operator "{1}".

Cause: The search expression contained an invalid operator.

Action: Supply an expression with a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02213: A search operator is required for a search expression.

Cause: A search operator was not provided.

Action: Supply a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02213: A search operator is required for a search expression.

Cause: A search operator was not provided.

Action: Supply a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02214: The operator "UNKNOWN" is not supported for a search expression.

Cause: The search operator UNKNOWN is not supported for expressions.

Action: Supply a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02214: The operator "UNKNOWN" is not supported for a search expression.

Cause: The search operator UNKNOWN is not supported for expressions.

Action: Supply a valid operator.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02215: A QName is required for a search criterion.

Cause: A search QName was not provided.

Action: Supply a valid Name.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02215: A QName is required for a search criterion.

Cause: A search QName was not provided.

Action: Supply a valid Name.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02216: The search expression "{0}" contains a close parenthesis at index {1} without a matching open parenthesis.

Cause: The search expression contained an unbalanced parenthesis.

Action: Supply an expression with matching open and close parenthesis.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02216: The search expression "{0}" contains a close parenthesis at index {1} without a matching open parenthesis.

Cause: The search expression contained an unbalanced parenthesis.

Action: Supply an expression with matching open and close parenthesis.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02217: The search expression "{0}" contains an open parenthesis without a matching close parenthesis.

Cause: The search expression contained an unclosed parenthesis.

Action: Supply an expression with matching open and close parenthesis.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02217: The search expression "{0}" contains an open parenthesis without a matching close parenthesis.

Cause: The search expression contained an unclosed parenthesis.

Action: Supply an expression with matching open and close parenthesis.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02218: The comparator "{0}" is not supported for text content search criterion.

Cause: The search comparator is not supported for text comparisons.

Action: Supply a comparator that supports text comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02218: The comparator "{0}" is not supported for text content search criterion.

Cause: The search comparator is not supported for text comparisons.

Action: Supply a comparator that supports text comparisons.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02251: Subject metadata is required to build a PolicySet.

Cause: Subject metadata was not provided for building a PolicySet.

Action: Supply valid subject metadata.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02251: Subject metadata is required to build a PolicySet.

Cause: Subject metadata was not provided for building a PolicySet.

Action: Supply valid subject metadata.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02252: A repository accessor is required to build a PolicySet.

Cause: A repository accessor was not provided for building a PolicySet.

Action: Supply suitable repository accessor instance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02252: A repository accessor is required to build a PolicySet.

Cause: A repository accessor was not provided for building a PolicySet.

Action: Supply suitable repository accessor instance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02253: The resource pattern for the subject "{0}" is invalid. External attachments and policy usage tracking is disabled.

Cause: An invalid resource pattern was provided with the metadata for a policy subject.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02253: The resource pattern for the subject "{0}" is invalid. External attachments and policy usage tracking is disabled.

Cause: An invalid resource pattern was provided with the metadata for a policy subject.

Action: Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02254: The constraint value "{0}" is invalid and caused ParseException, process continues as if there is no constraint being set in the global PolicySet.

Cause: Parsing of constraint set in the global PolicySet caused ParseException

Action: Correct the value of constraint in global PolicySet and retry.
Level: 1

Type: WARNING

Impact: Data

WSM-02254: The constraint value "{0}" is invalid and caused ParseException, process continues as if there is no constraint being set in the global PolicySet.

Cause: Parsing of constraint set in the global PolicySet caused ParseException

Action: Correct the value of constraint in global PolicySet and retry.
Level: 1

Type: WARNING

Impact: Data

WSM-02261: A map of terms is required when creating a ResourcePattern.

Cause: A null map of terms was provided to the ResourcePattern constructor.

Action: Supply a valid map of terms when creating a resource pattern.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02261: A map of terms is required when creating a ResourcePattern.

Cause: A null map of terms was provided to the ResourcePattern constructor.

Action: Supply a valid map of terms when creating a resource pattern.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02262: A "{0}" term is required when creating a ResourcePattern.

Cause: The required term was not provided to the ResourcePattern constructor.

Action: Supply a valid map of terms when creating a resource pattern.
Level: 1

Type: ERROR

Impact: Data

WSM-02262: A "{0}" term is required when creating a ResourcePattern.

Cause: The required term was not provided to the ResourcePattern constructor.

Action: Supply a valid map of terms when creating a resource pattern.
Level: 1

Type: ERROR

Impact: Data

WSM-02263: A map of terms is required when creating a ResourcePattern.

Cause: A null String was provided to the ResourcePattern constructor.

Action: Supply a valid resource pattern String.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02263: A map of terms is required when creating a ResourcePattern.

Cause: A null String was provided to the ResourcePattern constructor.

Action: Supply a valid resource pattern String.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02264: "{0}" is not a recognized resource pattern.

Cause: The supplied String did not match one of the known resource pattern formats.

Action: Supply a valid resource pattern String.
Level: 1

Type: ERROR

Impact: Data

WSM-02264: "{0}" is not a recognized resource pattern.

Cause: The supplied String did not match one of the known resource pattern formats.

Action: Supply a valid resource pattern String.
Level: 1

Type: ERROR

Impact: Data

WSM-02265: The resource patterns to be combined must be provided.

Cause: The resource pattern to combine must be supplied for creating valid resource pattern.

Action: Supply valid resource patterns
Level: 1

Type: ERROR

Impact: Data

WSM-02265: The resource patterns to be combined must be provided.

Cause: The resource pattern to combine must be supplied for creating valid resource pattern.

Action: Supply valid resource patterns
Level: 1

Type: ERROR

Impact: Data

WSM-02301: Failed to get document from URL "{0}" due to underlying error "{1}"

Cause: URL resource was not loaded.

Action: Check that the passed URL is valid and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02301: Failed to get document from URL "{0}" due to underlying error "{1}"

Cause: URL resource was not loaded.

Action: Check that the passed URL is valid and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02302: Failed to access document repository due to underlying error "{0}"

Cause: The Document Repository could not be accessed.

Action: Check the configuration for accessing Document Repository and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Requests/Responses

WSM-02302: Failed to access document repository due to underlying error "{0}"

Cause: The Document Repository could not be accessed.

Action: Check the configuration for accessing Document Repository and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Requests/Responses

WSM-02303: The passed search expression "{0}" could not be parsed due to underlying error "{1}"

Cause: Failure in parsing the passed search expression.

Action: Check that the passed search expression is valid and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02303: The passed search expression "{0}" could not be parsed due to underlying error "{1}"

Cause: Failure in parsing the passed search expression.

Action: Check that the passed search expression is valid and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02304: The passed expressionMap "{0}" contains search expression which cannot be parsed due to underlying error "{1}".

Cause: Failure in parsing the search expression contained in the passed expressionMap.

Action: Check that the passed expressionMap contains valid search expression and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02304: The passed expressionMap "{0}" contains search expression which cannot be parsed due to underlying error "{1}".

Cause: Failure in parsing the search expression contained in the passed expressionMap.

Action: Check that the passed expressionMap contains valid search expression and retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02310: Failed to retrieve requested documents due to underlying error "{0}". The operation will be retried.

Cause: Failure in retrieving the requested documents.

Action: No corrective action needed as this time, the operation will be retried.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02310: Failed to retrieve requested documents due to underlying error "{0}". The operation will be retried.

Cause: Failure in retrieving the requested documents.

Action: No corrective action needed as this time, the operation will be retried.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02311: Failed to retrieve requested documents due to underlying error "{0}".

Cause: Failure in retrieving the requested documents.

Action: Check that the document repository is reachable and is correctly configured.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02311: Failed to retrieve requested documents due to underlying error "{0}".

Cause: Failure in retrieving the requested documents.

Action: Check that the document repository is reachable and is correctly configured.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02312: Failed to store resource usage information to underlying error "{0}". The operation will be retried.

Cause: Failure in persisting usage information.

Action: This condition can happen in a normal situation and the operation would be retried automatically. There is no immediate concern unless the warning message displays continuously even in a low usage environment.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02312: Failed to store resource usage information to underlying error "{0}". The operation will be retried.

Cause: Failure in persisting usage information.

Action: This condition can happen in a normal situation and the operation would be retried automatically. There is no immediate concern unless the warning message displays continuously even in a low usage environment.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02313: Failed to store resource usage information to underlying error "{0}".

Cause: Failure in persisting usage information.

Action: Check that the document repository is reachable and is correctly configured.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02313: Failed to store resource usage information to underlying error "{0}".

Cause: Failure in persisting usage information.

Action: Check that the document repository is reachable and is correctly configured.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02351: A invalid bean class "{0}" is provided.

Cause: A invalid bean class was provided to the bean factory to create a bean instance.

Action: Provide a valid bean class.
Level: 1

Type: ERROR

Impact: Data

WSM-02351: A invalid bean class "{0}" is provided.

Cause: A invalid bean class was provided to the bean factory to create a bean instance.

Action: Provide a valid bean class.
Level: 1

Type: ERROR

Impact: Data

WSM-02352: A invalid bean type "{0}" is provided.

Cause: A invalid bean type was provided to the bean factory to create a bean instance.

Action: Provide a valid bean type.
Level: 1

Type: ERROR

Impact: Data

WSM-02352: A invalid bean type "{0}" is provided.

Cause: A invalid bean type was provided to the bean factory to create a bean instance.

Action: Provide a valid bean type.
Level: 1

Type: ERROR

Impact: Data

WSM-02353: Unable to get the Action Executor.

Cause: A failure occurred while getting Action Executor.

Action: Check that valid subject is passed to get the Action Executor
Level: 1

Type: ERROR

Impact: Configuration

WSM-02353: Unable to get the Action Executor.

Cause: A failure occurred while getting Action Executor.

Action: Check that valid subject is passed to get the Action Executor
Level: 1

Type: ERROR

Impact: Configuration

WSM-02354: Unexpected exception "{0}" caught when privileged method is called.

Cause: Unexpected exception caught on calling a privileged code.

Action: Check the underlying signature of method called in privileged code
Level: 1

Type: ERROR

Impact: Configuration

WSM-02354: Unexpected exception "{0}" caught when privileged method is called.

Cause: Unexpected exception caught on calling a privileged code.

Action: Check the underlying signature of method called in privileged code
Level: 1

Type: ERROR

Impact: Configuration

WSM-02355: A subject passed to BeanFactory is null.

Cause: The subject passed to the bean factory is null.

Action: Ensure that the subject is not null.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02355: A subject passed to BeanFactory is null.

Cause: The subject passed to the bean factory is null.

Action: Ensure that the subject is not null.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02356: Cannot cast to "{0}" object.

Cause: Unable to cast the object. It may be using older implementation.

Action: Verify that the older implementation is not being used.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02356: Cannot cast to "{0}" object.

Cause: Unable to cast the object. It may be using older implementation.

Action: Verify that the older implementation is not being used.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02359: Lookup attempted for unsupported Server.

Cause: A lookup is attempted for unsupported Server.

Action: Check the system configurations to ensure correct server is running.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02359: Lookup attempted for unsupported Server.

Cause: A lookup is attempted for unsupported Server.

Action: Check the system configurations to ensure correct server is running.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02360: The path to the jar file "{0}" is either invalid or the jar file is corrupt.

Cause: The path provided to the jar file is either incorrect or the jar file is corrupt

Action: Provide the path to a valid jar file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02360: The path to the jar file "{0}" is either invalid or the jar file is corrupt.

Cause: The path provided to the jar file is either incorrect or the jar file is corrupt

Action: Provide the path to a valid jar file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02361: A invalid Policy Manager RESTful service URI "{0}" is provided.

Cause: A invalid Policy Manager RESTful service URI was provided to the bean factory to create a bean instance.

Action: Provide a valid Policy Manager RESTful service URI.
Level: 1

Type: ERROR

Impact: Data

WSM-02361: A invalid Policy Manager RESTful service URI "{0}" is provided.

Cause: A invalid Policy Manager RESTful service URI was provided to the bean factory to create a bean instance.

Action: Provide a valid Policy Manager RESTful service URI.
Level: 1

Type: ERROR

Impact: Data

WSM-02362: An unsupported operation "{0}" is invoked.

Cause: An unsupported operation was invoked.

Action: Invoke a supported operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02362: An unsupported operation "{0}" is invoked.

Cause: An unsupported operation was invoked.

Action: Invoke a supported operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02363: An invalid keystore/truststore specified as system property.

Cause: An invalid keystore/truststore specified as system property.

Action: Provide a valid keystore/truststore as system property.
Level: 1

Type: WARNING

Impact: Data

WSM-02363: An invalid keystore/truststore specified as system property.

Cause: An invalid keystore/truststore specified as system property.

Action: Provide a valid keystore/truststore as system property.
Level: 1

Type: WARNING

Impact: Data

WSM-02364: An invalid cryptographic algorithm specified in keystore/truststore.

Cause: An invalid cryptographic algorithm specified in keystore/truststore.

Action: Provide a valid cryptographic algorithm in keystore/truststore.
Level: 1

Type: WARNING

Impact: Data

WSM-02364: An invalid cryptographic algorithm specified in keystore/truststore.

Cause: An invalid cryptographic algorithm specified in keystore/truststore.

Action: Provide a valid cryptographic algorithm in keystore/truststore.
Level: 1

Type: WARNING

Impact: Data

WSM-02365: A invalid trust or key store location "{0}" is provided.

Cause: An invalid trust/key store path was provided to the bean factory to create a bean instance.

Action: Provide a valid trust/key store path.
Level: 1

Type: ERROR

Impact: Data

WSM-02365: A invalid trust or key store location "{0}" is provided.

Cause: An invalid trust/key store path was provided to the bean factory to create a bean instance.

Action: Provide a valid trust/key store path.
Level: 1

Type: ERROR

Impact: Data

WSM-02366: Keystore instance of type "{0}" is not found.

Cause: Keystore instance is not found.

Action: Add the keystore instance and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02366: Keystore instance of type "{0}" is not found.

Cause: Keystore instance is not found.

Action: Add the keystore instance and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02367: An invalid cryptographic algorithm is requested.

Cause: An invalid cryptographic algorithm is requested but is not available in the environment.

Action: Provide a valid algorithm and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02367: An invalid cryptographic algorithm is requested.

Cause: An invalid cryptographic algorithm is requested but is not available in the environment.

Action: Provide a valid algorithm and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02368: A certificate provided in keystore "{0}" is invalid.

Cause: A certificate in the trust chain is missing.

Action: Ensure that the complete certificate chain is propagated.
Level: 1

Type: ERROR

Impact: Data

WSM-02368: A certificate provided in keystore "{0}" is invalid.

Cause: A certificate in the trust chain is missing.

Action: Ensure that the complete certificate chain is propagated.
Level: 1

Type: ERROR

Impact: Data

WSM-02369: Certificate location "{0}" is invalid.

Cause: A certificate location is invalid.

Action: Provide valid certificate location and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02369: Certificate location "{0}" is invalid.

Cause: A certificate location is invalid.

Action: Provide valid certificate location and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02370: Unable to read certificate from keystore "{0}".

Cause: Unable to read certificate from keystore.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Data

WSM-02370: Unable to read certificate from keystore "{0}".

Cause: Unable to read certificate from keystore.

Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.
Level: 1

Type: ERROR

Impact: Data

WSM-02371: Unable to recover key from keystore "{0}".

Cause: Security provider is requested is not available in the environment.

Action: Ensure to request correct security provider.
Level: 1

Type: ERROR

Impact: Data

WSM-02371: Unable to recover key from keystore "{0}".

Cause: Security provider is requested is not available in the environment.

Action: Ensure to request correct security provider.
Level: 1

Type: ERROR

Impact: Data

WSM-02373: Policy manager url "{0}" is not supported in this environment.

Cause: An unsupported policy manager url was configured.

Action: Correct policy manager configuration and try again.
Level: 1

Type: WARNING

Impact: Data

WSM-02373: Policy manager url "{0}" is not supported in this environment.

Cause: An unsupported policy manager url was configured.

Action: Correct policy manager configuration and try again.
Level: 1

Type: WARNING

Impact: Data

WSM-02374: The policy manager repository path "{0}" does not contain any valid directories.

Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02374: The policy manager repository path "{0}" does not contain any valid directories.

Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02375: One or more directories are required to connect to a file-based policy manager.

Cause: A path was not provided when attempting to create a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02375: One or more directories are required to connect to a file-based policy manager.

Cause: A path was not provided when attempting to create a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-02376: The policy manager repository session cannot be created due to underlying error "{0}".

Cause: Policy manager encountered an unexpected condition.

Action: Follow the recommendations for the underlying exception.
Level: 1

Type: ERROR

Impact: Data

WSM-02376: The policy manager repository session cannot be created due to underlying error "{0}".

Cause: Policy manager encountered an unexpected condition.

Action: Follow the recommendations for the underlying exception.
Level: 1

Type: ERROR

Impact: Data

WSM-02377: Unable to access member "{0}" of class "{1}".

Cause: Unable to access field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02377: Unable to access member "{0}" of class "{1}".

Cause: Unable to access field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02378: Unable to find member "{0}" of class "{1}".

Cause: Unable to find field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02378: Unable to find member "{0}" of class "{1}".

Cause: Unable to find field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02379: Trying to access member "{0}" of class "{1}" illegally that violates its access modifiers.

Cause: Trying to access illegally field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02379: Trying to access member "{0}" of class "{1}" illegally that violates its access modifiers.

Cause: Trying to access illegally field or method of a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02380: Unable to find implementation of member "{0}" in class "{1}".

Cause: Unable to find implementation of field or method in a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02380: Unable to find implementation of member "{0}" in class "{1}".

Cause: Unable to find implementation of field or method in a class.

Action: Ensure to field name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02381: Unable to invoke method "{0}" of class "{1}" with values "{2}".

Cause: Unable to invoke method of a class.

Action: Ensure to method name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02381: Unable to invoke method "{0}" of class "{1}" with values "{2}".

Cause: Unable to invoke method of a class.

Action: Ensure to method name and class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02382: The path to the jar files "{0}" are either invalid or the jar files are corrupt.

Cause: The path provided to the jersey jar files are either incorrect or the jar files are corrupt

Action: Provide the path to a valid jar file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02382: The path to the jar files "{0}" are either invalid or the jar files are corrupt.

Cause: The path provided to the jersey jar files are either incorrect or the jar files are corrupt

Action: Provide the path to a valid jar file.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02383: Class name cannot be null.

Cause: Class name is null or invalid.

Action: Ensure to class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02383: Class name cannot be null.

Cause: Class name is null or invalid.

Action: Ensure to class name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02384: Class method name cannot be null.

Cause: Method name is null or invalid.

Action: Ensure to method name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02384: Class method name cannot be null.

Cause: Method name is null or invalid.

Action: Ensure to method name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02385: Class field name cannot be null.

Cause: Class field name is null or invalid.

Action: Ensure to class field name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02385: Class field name cannot be null.

Cause: Class field name is null or invalid.

Action: Ensure to class field name is correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02386: Failure constructing object for class ( "{0}" ) with the given params: "{1}".

Cause: Unable to create instance of class.

Action: Ensure to call correct constructor.
Level: 1

Type: ERROR

Impact: Data

WSM-02386: Failure constructing object for class ( "{0}" ) with the given params: "{1}".

Cause: Unable to create instance of class.

Action: Ensure to call correct constructor.
Level: 1

Type: ERROR

Impact: Data

WSM-02387: Class cannot be null.

Cause: Class is null or invalid.

Action: Ensure to class loaded correctly.
Level: 1

Type: ERROR

Impact: Data

WSM-02387: Class cannot be null.

Cause: Class is null or invalid.

Action: Ensure to class loaded correctly.
Level: 1

Type: ERROR

Impact: Data

WSM-02388: Unable to load class "{0}".

Cause: Unable to load class.

Action: Ensure to class name correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02388: Unable to load class "{0}".

Cause: Unable to load class.

Action: Ensure to class name correct.
Level: 1

Type: ERROR

Impact: Data

WSM-02401: Failed to store policy usage information to the repository because document criterion "{1}" is not a valid document name for the repository due to underlying error "{0}".

Cause: The document criterion contains invalid document name for the repository.

Action: Choose a valid document name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02401: Failed to store policy usage information to the repository because document criterion "{1}" is not a valid document name for the repository due to underlying error "{0}".

Cause: The document criterion contains invalid document name for the repository.

Action: Choose a valid document name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02402: Expression "{0}" does not identify specific documents.

Cause: An invalid search expression was specified.

Action: Check the search expression and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02402: Expression "{0}" does not identify specific documents.

Cause: An invalid search expression was specified.

Action: Check the search expression and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-02403: Failed to store policy usage information to the repository because the expressionMap "{0}" has document criterion with invalid document name for the repository resulting in underlying error "{1}".

Cause: The search expression within the map has document criterion having invalid document name for the repository.

Action: Choose a valid document name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02403: Failed to store policy usage information to the repository because the expressionMap "{0}" has document criterion with invalid document name for the repository resulting in underlying error "{1}".

Cause: The search expression within the map has document criterion having invalid document name for the repository.

Action: Choose a valid document name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-02451: Document cannot be deleted from repository due to underlying error "{0}".

Cause: Failure in deleting requested document.

Action: Check that the document exists in the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02451: Document cannot be deleted from repository due to underlying error "{0}".

Cause: Failure in deleting requested document.

Action: Check that the document exists in the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02452: Document criterion "{0}" is invalid for the requested operation due to underlying error "{0}".

Cause: Document criteria is invalid for the requested operation.

Action: Check that the document criterion is valid for the repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02452: Document criterion "{0}" is invalid for the requested operation due to underlying error "{0}".

Cause: Document criteria is invalid for the requested operation.

Action: Check that the document criterion is valid for the repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02453: Failed to delete the document with version "{1}" and criterion "{0}" due to underlying error "{2}".

Cause: Failure in deleting the specified version of the document.

Action: Check that the document with the specified version exists in repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02453: Failed to delete the document with version "{1}" and criterion "{0}" due to underlying error "{2}".

Cause: Failure in deleting the specified version of the document.

Action: Check that the document with the specified version exists in repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02454: The search expression "{0}" does not identify a unique document.

Cause: The search expression do not identify unique document.

Action: Supply an expression which identifies unique document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02454: The search expression "{0}" does not identify a unique document.

Cause: The search expression do not identify unique document.

Action: Supply an expression which identifies unique document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02455: Document version cannot be promoted to tip due to underlying error "{0}".

Cause: Failure in promoting the requested document.

Action: Check that the document exists in the repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02455: Document version cannot be promoted to tip due to underlying error "{0}".

Cause: Failure in promoting the requested document.

Action: Check that the document exists in the repository.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02456: A retrieval flag cannot be parsed into a number due to underlying error "{0}".

Cause: Failure in parsing flags for document retrieval operation.

Action: Check that the value specified for the flags are valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02456: A retrieval flag cannot be parsed into a number due to underlying error "{0}".

Cause: Failure in parsing flags for document retrieval operation.

Action: Check that the value specified for the flags are valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02457: Document retrieval failed due to underlying error "{0}".

Cause: Failure in retrieving documents due to invalid document criteria.

Action: Check that the value specified for the document criteria are valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02457: Document retrieval failed due to underlying error "{0}".

Cause: Failure in retrieving documents due to invalid document criteria.

Action: Check that the value specified for the document criteria are valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02458: Document "{0}" cannot be overwritten as it does not exist in the repository.

Cause: Failure in write operation using WRITE_EXISTING mode since document do not exist in repository.

Action: Define a new search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02458: Document "{0}" cannot be overwritten as it does not exist in the repository.

Cause: Failure in write operation using WRITE_EXISTING mode since document do not exist in repository.

Action: Define a new search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02459: Document "{0}" cannot be created as already exists in the repository.

Cause: Failure in write operation using WRITE_NEW mode since document exists in repository.

Action: Define a new search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02459: Document "{0}" cannot be created as already exists in the repository.

Cause: Failure in write operation using WRITE_NEW mode since document exists in repository.

Action: Define a new search criterion.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02460: Unable to write invalid document due to underlying error "{0}".

Cause: URI for the document is invalid for the write operation.

Action: Check that the document URI is valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02460: Unable to write invalid document due to underlying error "{0}".

Cause: URI for the document is invalid for the write operation.

Action: Check that the document URI is valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02461: A document without a naming attribute cannot be written.

Cause: Document name is not specified at time of document creation.

Action: Please specify a valid document name for the document creation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02461: A document without a naming attribute cannot be written.

Cause: Document name is not specified at time of document creation.

Action: Please specify a valid document name for the document creation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02462: The session state is invalid due to underlying error "{0}".

Cause: Session state is invalid for the given operation.

Action: Retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02462: The session state is invalid due to underlying error "{0}".

Cause: Session state is invalid for the given operation.

Action: Retry the operation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02463: A document transformer cannot be created due to underlying error "{0}".

Cause: The DOM Parser was not configured properly.

Action: Consult Java documentation.
Level: 1

Type: ERROR

Impact: Other

WSM-02463: A document transformer cannot be created due to underlying error "{0}".

Cause: The DOM Parser was not configured properly.

Action: Consult Java documentation.
Level: 1

Type: ERROR

Impact: Other

WSM-02464: A DOM document cannot be marshalled into XML due to underlying transformation error "{0}".

Cause: Parsing of the document failed.

Action: Ensure that the document is in well-formed XML format.
Level: 1

Type: ERROR

Impact: Other

WSM-02464: A DOM document cannot be marshalled into XML due to underlying transformation error "{0}".

Cause: Parsing of the document failed.

Action: Ensure that the document is in well-formed XML format.
Level: 1

Type: ERROR

Impact: Other

WSM-02465: A DOM document builder cannot be created due to underlying error "{0}".

Cause: The XML Parser was not configured properly.

Action: Consult Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02465: A DOM document builder cannot be created due to underlying error "{0}".

Cause: The XML Parser was not configured properly.

Action: Consult Java documentation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02466: An XML document cannot be unmarshalled into DOM due to underlying parsing error "{0}".

Cause: Parsing of the XML failed.

Action: Ensure that the XML is well formed.
Level: 1

Type: ERROR

Impact: Data

WSM-02466: An XML document cannot be unmarshalled into DOM due to underlying parsing error "{0}".

Cause: Parsing of the XML failed.

Action: Ensure that the XML is well formed.
Level: 1

Type: ERROR

Impact: Data

WSM-02467: An XML document cannot be unmarshalled into DOM due to underlying I/O error "{0}".

Cause: The system could not open the Input/Output streams.

Action: Consult the Java documentation.
Level: 1

Type: ERROR

Impact: Files

WSM-02467: An XML document cannot be unmarshalled into DOM due to underlying I/O error "{0}".

Cause: The system could not open the Input/Output streams.

Action: Consult the Java documentation.
Level: 1

Type: ERROR

Impact: Files

WSM-02468: The document specified in search expresion "{0}" resulted in underlying error "{1}".

Cause: The document name specified for the repository is invalid.

Action: Please specify a valid document name.
Level: 1

Type: ERROR

Impact: Files

WSM-02468: The document specified in search expresion "{0}" resulted in underlying error "{1}".

Cause: The document name specified for the repository is invalid.

Action: Please specify a valid document name.
Level: 1

Type: ERROR

Impact: Files

WSM-02469: Unable to retrieve document due to underlying error "{0}".

Cause: URI for the document is invalid for the retrieve operation.

Action: Check that the document URI is valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02469: Unable to retrieve document due to underlying error "{0}".

Cause: URI for the document is invalid for the retrieve operation.

Action: Check that the document URI is valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02470: Unable to write document due to invalid Write Mode "{0}".

Cause: Invalid Write Mode specified to write a document.

Action: Check that a valid Write Mode is specified to write a document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02470: Unable to write document due to invalid Write Mode "{0}".

Cause: Invalid Write Mode specified to write a document.

Action: Check that a valid Write Mode is specified to write a document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02471: The exception "{0}" is caused because invalid document uri is being used.

Cause: URI for any document is invalid.

Action: Check that all the document URI used are valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02471: The exception "{0}" is caused because invalid document uri is being used.

Cause: URI for any document is invalid.

Action: Check that all the document URI used are valid for the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02472: REST client got an unexpected error, http status:"{0}", msg:"{1}", type:"{2}".

Cause: REST client got an unexpected error.

Action: Check the REST client request and error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02472: REST client got an unexpected error, http status:"{0}", msg:"{1}", type:"{2}".

Cause: REST client got an unexpected error.

Action: Check the REST client request and error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02473: REST Service got an exception, http status:"{0}", msg:"{1}", type:"{2}", uriPath:"{3}" .

Cause: REST service got an expection.

Action: Check the REST request and server error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02473: REST Service got an exception, http status:"{0}", msg:"{1}", type:"{2}", uriPath:"{3}" .

Cause: REST service got an expection.

Action: Check the REST request and server error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02474: REST Client got an exception, http status:"{0}", msg:"{1}", type:"{2}", uriPath:"{3}" .

Cause: REST client got an expection.

Action: Check the REST client request and client error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02474: REST Client got an exception, http status:"{0}", msg:"{1}", type:"{2}", uriPath:"{3}" .

Cause: REST client got an expection.

Action: Check the REST client request and client error message logged for possible cause
Level: 1

Type: ERROR

Impact: Data

WSM-02475: Unable to marshal/unmarshall the document "{1}" due to underlying error "{0}" resulting in deletion failure.

Cause: Unable to marshal/unmarshall the document resulting in deletion failure.

Action: Check that the document exists in the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02475: Unable to marshal/unmarshall the document "{1}" due to underlying error "{0}" resulting in deletion failure.

Cause: Unable to marshal/unmarshall the document resulting in deletion failure.

Action: Check that the document exists in the repository
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02476: The document "{0}" cannot be deleted since it is being used by other documents.

Cause: Cannot delete a referenced document.

Action: Before deleting the document, delete othe documents referring the document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02476: The document "{0}" cannot be deleted since it is being used by other documents.

Cause: Cannot delete a referenced document.

Action: Before deleting the document, delete othe documents referring the document.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02477: Unable to create object for marshalling/unmarshalling of resource documents due to underlying error "{0}".

Cause: Failed to create instance of ResourceMarshaller.

Action: Refer the logs for details.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02477: Unable to create object for marshalling/unmarshalling of resource documents due to underlying error "{0}".

Cause: Failed to create instance of ResourceMarshaller.

Action: Refer the logs for details.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02478: Unable to marshal/unmarshall the document due to underlying error "{0}".

Cause: Unable to marshal/unmarshall the document.

Action: Check that the document is valid
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02478: Unable to marshal/unmarshall the document due to underlying error "{0}".

Cause: Unable to marshal/unmarshall the document.

Action: Check that the document is valid
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02479: The specified document "{0}" is invalid and cannot be created as it cannot be marshaled.

Cause: The specified document is invalid as it cannot be marshaled.

Action: Please specify a valid document for the document creation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02479: The specified document "{0}" is invalid and cannot be created as it cannot be marshaled.

Cause: The specified document is invalid as it cannot be marshaled.

Action: Please specify a valid document for the document creation.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02551: Unable to retrieve document due to underlying error "{0}".

Cause: URI for the jar is invalid for the retrieve operation.

Action: Check that the jar URI is valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02551: Unable to retrieve document due to underlying error "{0}".

Cause: URI for the jar is invalid for the retrieve operation.

Action: Check that the jar URI is valid.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02552: Unable to load seed policies jar file

Cause: Inability to load seed policies jar either automatically or by a provided path

Action: Check that the path to the jar file is correct
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02552: Unable to load seed policies jar file

Cause: Inability to load seed policies jar either automatically or by a provided path

Action: Check that the path to the jar file is correct
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02553: Unable to load updates.xml from the seed policy jar

Cause: There is some problem while loading updates.xml from the seed policies jar

Action: Make sure a valid seed policies jar is provided containing a valid updates.xml file
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02553: Unable to load updates.xml from the seed policy jar

Cause: There is some problem while loading updates.xml from the seed policies jar

Action: Make sure a valid seed policies jar is provided containing a valid updates.xml file
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02554: The access to the store or credentials is denied.

Cause: The credentials store access is denied.

Action: Ensure Store is properly initialized.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02554: The access to the store or credentials is denied.

Cause: The credentials store access is denied.

Action: Ensure Store is properly initialized.
Level: 1

Type: ERROR

Impact: Configuration

WSM-02555: Cannot retrieve requested documents for condition {0}.

Cause: A failure occurred retriving documents from the data store.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02555: Cannot retrieve requested documents for condition {0}.

Cause: A failure occurred retriving documents from the data store.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02556: Document(s) identified by condition {0} does not exist in the data store

Cause: A failure occured retriving document(s) from the data store.

Action: Make sure the document(s) being requested exists in the data store and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-02556: Document(s) identified by condition {0} does not exist in the data store

Cause: A failure occured retriving document(s) from the data store.

Action: Make sure the document(s) being requested exists in the data store and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-03001: Oracle WSM Monitor internal error {0}

Cause: An unexpected error occurred while monitoring Oracle WSM Agent.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-03001: Oracle WSM Monitor internal error {0}

Cause: An unexpected error occurred while monitoring Oracle WSM Agent.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-03002: Failure initializing Oracle WSM Monitor, {0} is null.

Cause: Creation of one or more DMS Event sensors failed while initializing Oracle WSM Monitor.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03002: Failure initializing Oracle WSM Monitor, {0} is null.

Cause: Creation of one or more DMS Event sensors failed while initializing Oracle WSM Monitor.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03003: The topology node value {0} is not valid.

Cause: The topology node value passed from the security interceptor to Oracle WSM Agent was invalid.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03003: The topology node value {0} is not valid.

Cause: The topology node value passed from the security interceptor to Oracle WSM Agent was invalid.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03004: The parameter {0} is not valid.

Cause: The parameter was either null or invalid.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-03004: The parameter {0} is not valid.

Cause: The parameter was either null or invalid.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04501: generic error in accessing the data store

Cause: An internal error occurred while accessing the MDS data store.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04501: generic error in accessing the data store

Cause: An internal error occurred while accessing the MDS data store.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04502: The name of the resource is empty.

Cause: The name of the resource to be updated or retrieved was empty.

Action: Assign a name to the resource being processed.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04502: The name of the resource is empty.

Cause: The name of the resource to be updated or retrieved was empty.

Action: Assign a name to the resource being processed.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04503: resource {0} does not exist in the data store

Cause: The requested resource was not found in the data store.

Action: Check the search criteria and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04503: resource {0} does not exist in the data store

Cause: The requested resource was not found in the data store.

Action: Check the search criteria and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04504: resource {0} cannot be updated

Cause: The resource could not be updated.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-04504: resource {0} cannot be updated

Cause: The resource could not be updated.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Data

WSM-04505: resource {0} cannot be created

Cause: The specified name has already been assigned to another resource.

Action: Specify a unique name, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04505: resource {0} cannot be created

Cause: The specified name has already been assigned to another resource.

Action: Specify a unique name, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04506: cannot create resource {0}

Cause: The resource could not be saved to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04506: cannot create resource {0}

Cause: The resource could not be saved to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04507: cannot delete resource {0}

Cause: The resource could not be deleted from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04507: cannot delete resource {0}

Cause: The resource could not be deleted from the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04508: cannot update resource {0}

Cause: The resource could not be updated to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04508: cannot update resource {0}

Cause: The resource could not be updated to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04509: cannot initialize the connection to the data store

Cause: Connecting to the data store failed.

Action: Check the data store credentials, and retry the operation. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.
Level: 1

Type: ERROR

Impact: Data

WSM-04509: cannot initialize the connection to the data store

Cause: Connecting to the data store failed.

Action: Check the data store credentials, and retry the operation. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.
Level: 1

Type: ERROR

Impact: Data

WSM-04510: The version {0} for resource {1} cannot be found.

Cause: The requested version for the specified resource was not found.

Action: Check the search criteria, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04510: The version {0} for resource {1} cannot be found.

Cause: The requested version for the specified resource was not found.

Action: Check the search criteria, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04511: cannot perform simultaneous deletes

Cause: Deleting multiple resources simultaneously from the data store failed.

Action: Check supplied data, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04511: cannot perform simultaneous deletes

Cause: Deleting multiple resources simultaneously from the data store failed.

Action: Check supplied data, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04512: internal data store error

Cause: A generic data store exception occurred.

Action: Check the data store credentials that were provided and retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04512: internal data store error

Cause: A generic data store exception occurred.

Action: Check the data store credentials that were provided and retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04513: cannot commit changes to the repository

Cause: A failure occurred while finalizing changes to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04513: cannot commit changes to the repository

Cause: A failure occurred while finalizing changes to the data store.

Action: Retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04514: The version {0} for resource {1} cannot be deleted.

Cause: Deleting the specified version(s) of the resource failed.

Action: Check the supplied values, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04514: The version {0} for resource {1} cannot be deleted.

Cause: Deleting the specified version(s) of the resource failed.

Action: Check the supplied values, and retry the operation.
Level: 1

Type: ERROR

Impact: Data

WSM-04515: Auditing is disabled for MDS operations.

Cause: An internal error occurred; failed to initialize the auditor.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04515: Auditing is disabled for MDS operations.

Cause: An internal error occurred; failed to initialize the auditor.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04516: The version of the passed resource is invalid.

Cause: The requested version of the resource was invalid.

Action: The version number must be a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04516: The version of the passed resource is invalid.

Cause: The requested version of the resource was invalid.

Action: The version number must be a positive integer.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04517: cannot update resource {0}

Cause: The resource to be updated was concurrently being updated by another process.

Action: Make sure no other process is attempting to change the resource being updated, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04517: cannot update resource {0}

Cause: The resource to be updated was concurrently being updated by another process.

Action: Make sure no other process is attempting to change the resource being updated, and retry the operation.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04518: document name is invalid

Cause: The document name was invalid.

Action: Specify a name for the document that follows the document naming conventions. Refer to Oracle documentation for the naming rules.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04518: document name is invalid

Cause: The document name was invalid.

Action: Specify a name for the document that follows the document naming conventions. Refer to Oracle documentation for the naming rules.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04519: Unable to create document.

Cause: The repository permissions were read-only. Creation of a new document requires write permissions.

Action: Reconfigure the repository to have write permissions.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04519: Unable to create document.

Cause: The repository permissions were read-only. Creation of a new document requires write permissions.

Action: Reconfigure the repository to have write permissions.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04520: The repository timestamp is invalid.

Cause: The repository timestamp was invalid or missing.

Action: Retry the operation. If the problem persists, consult the diagnostic logs.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04520: The repository timestamp is invalid.

Cause: The repository timestamp was invalid or missing.

Action: Retry the operation. If the problem persists, consult the diagnostic logs.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04521: Resource to be deleted does not exist in datastore.

Cause: The resource could not be deleted since it does not exist in the data store.

Action: You don't need to take any action, the resource is not present in the datastore.
Level: 1

Type: ERROR

Impact: Data

WSM-04521: Resource to be deleted does not exist in datastore.

Cause: The resource could not be deleted since it does not exist in the data store.

Action: You don't need to take any action, the resource is not present in the datastore.
Level: 1

Type: ERROR

Impact: Data

WSM-04601: A JDBC URL is required to connect to a database-based MDS repository.

Cause: A null or empty JDBC URL was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid JDBC URL and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04601: A JDBC URL is required to connect to a database-based MDS repository.

Cause: A null or empty JDBC URL was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid JDBC URL and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04602: A password is required to connect to a database-based MDS repository.

Cause: A null or empty password was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid password and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04602: A password is required to connect to a database-based MDS repository.

Cause: A null or empty password was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid password and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04603: A username is required to connect to a database-based MDS repository.

Cause: A null or empty username was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid username and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04603: A username is required to connect to a database-based MDS repository.

Cause: A null or empty username was provided when attempting to create an MDS instance for a database-based repository.

Action: Provide a valid username and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04606: One or more directories are required to connect to a file-based MDS repository.

Cause: A path was not provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04606: One or more directories are required to connect to a file-based MDS repository.

Cause: A path was not provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04611: An MDS session cannot be created due to underlying error "{0}".

Cause: MDS encountered an unexpected condition.

Action: Follow the recommendations for the underlying exception.
Level: 1

Type: ERROR

Impact: Data

WSM-04611: An MDS session cannot be created due to underlying error "{0}".

Cause: MDS encountered an unexpected condition.

Action: Follow the recommendations for the underlying exception.
Level: 1

Type: ERROR

Impact: Data

WSM-04641: The operation "{0}" for document "{1}" cannot be performed on a closed session.

Cause: A operation was requested on a session that has already been closed.

Action: Create a new repository session and perform the operation again.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04641: The operation "{0}" for document "{1}" cannot be performed on a closed session.

Cause: A operation was requested on a session that has already been closed.

Action: Create a new repository session and perform the operation again.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04642: The operation "{0}" for document "{1}" cannot be performed on a read-only session.

Cause: A write operation was requested on a read-only session.

Action: Provide the name of a creator to associate with write operations.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: See error message.

Action: Create a new session on a writable repository and try again.

WSM-04642: The operation "{0}" for document "{1}" cannot be performed on a read-only session.

Cause: A write operation was requested on a read-only session.

Action: Provide the name of a creator to associate with write operations.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: See error message.

Action: Create a new session on a writable repository and try again.

WSM-04643: The operation "{0}" cannot be performed on virtual document "{1}".

Cause: A write operation was requested on a virtual document.

Action: Choose a different document name and try again.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-04643: The operation "{0}" cannot be performed on virtual document "{1}".

Cause: A write operation was requested on a virtual document.

Action: Choose a different document name and try again.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-04651: The search criterion "{0}" does not identify a specific document to be created.

Cause: The supplied criterion does not have the correct type.

Action: Supply a NAME search criterion.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04651: The search criterion "{0}" does not identify a specific document to be created.

Cause: The supplied criterion does not have the correct type.

Action: Supply a NAME search criterion.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04652: The document "{0}" already exists in the repository.

Cause: The document already exists in the repository.

Action: Choose a different name for the document to create or perform an update instead.
Level: 1

Type: ERROR

Impact: Data

WSM-04652: The document "{0}" already exists in the repository.

Cause: The document already exists in the repository.

Action: Choose a different name for the document to create or perform an update instead.
Level: 1

Type: ERROR

Impact: Data

WSM-04653: The document "{0}" cannot be created in a read-only repository.

Cause: The repository is read-only.

Action: Reconfigure the repository to support writes and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04653: The document "{0}" cannot be created in a read-only repository.

Cause: The repository is read-only.

Action: Reconfigure the repository to support writes and try again.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04654: The name "{0}" is invalid for creating a document due to underlying reason "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04654: The name "{0}" is invalid for creating a document due to underlying reason "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04655: Repository information cannot be marshalled due to underlying parser error "{2}"

Cause: The system does not support the required DOM document builder configuration.

Action: Correct underlying error or contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-04655: Repository information cannot be marshalled due to underlying parser error "{2}"

Cause: The system does not support the required DOM document builder configuration.

Action: Correct underlying error or contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-04656: Repository information cannot be marshalled due to underlying marshalling error "{2}"

Cause: The repository information object could not be marshalled into a DOM document.

Action: Correct underlying error or contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04656: Repository information cannot be marshalled due to underlying marshalling error "{2}"

Cause: The repository information object could not be marshalled into a DOM document.

Action: Correct underlying error or contact Oracle Support Services for assistance.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04657: The document "{0}" cannot be created in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be created belongs in a store that is different from other write operations in the session.

Action: Create the document in a different session.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04657: The document "{0}" cannot be created in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be created belongs in a store that is different from other write operations in the session.

Action: Create the document in a different session.
Level: 1

Type: ERROR

Impact: Configuration

WSM-04661: The document "{0}" cannot be deleted in a read-only repository.

Cause: The repository is read-only.

Action: Reconfigure the repository to support writes and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04661: The document "{0}" cannot be deleted in a read-only repository.

Cause: The repository is read-only.

Action: Reconfigure the repository to support writes and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04662: The name "{0}" is invalid for deleting a document due to underlying reason "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04662: The name "{0}" is invalid for deleting a document due to underlying reason "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04663: The document "{0}" cannot be deleted in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be created belongs in a store that is different from other write operations in the session.

Action: Delete the document in a different session.
Level: 1

Type: ERROR

Impact: Data

WSM-04663: The document "{0}" cannot be deleted in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be created belongs in a store that is different from other write operations in the session.

Action: Delete the document in a different session.
Level: 1

Type: ERROR

Impact: Data

WSM-04664: Version {1} to {3} of document "{0}" cannot be deleted.

Cause: The repository does not support deletion of individual versions of a document.

Action: Ignore the document version or delete the entire document.
Level: 1

Type: ERROR

Impact: Data

WSM-04664: Version {1} to {3} of document "{0}" cannot be deleted.

Cause: The repository does not support deletion of individual versions of a document.

Action: Ignore the document version or delete the entire document.
Level: 1

Type: ERROR

Impact: Data

WSM-04671: A concurrent write prevented the document "{0}" from being written due to underlying error "{2}".

Cause: Two or more incompatible operations were performed on the same document.

Action: Perform the incompatible operations in different sessions.
Level: 1

Type: ERROR

Impact: Data

Cause: A document in this session was modified by another session.

Action: Retry the operation.

WSM-04671: A concurrent write prevented the document "{0}" from being written due to underlying error "{2}".

Cause: Two or more incompatible operations were performed on the same document.

Action: Perform the incompatible operations in different sessions.
Level: 1

Type: ERROR

Impact: Data

Cause: A document in this session was modified by another session.

Action: Retry the operation.

WSM-04672: The document "{0}" cannot be written to repository due to underlying error "{2}".

Cause: An I/O error occurred while writing to repository.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04672: The document "{0}" cannot be written to repository due to underlying error "{2}".

Cause: An I/O error occurred while writing to repository.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04673: The session cannot be commited due to underlying error "{2}".

Cause: The resource could not be deleted since it does not exist in the data store.

Action: You don't need to take any action, the resource is not present in the datastore.
Level: 1

Type: ERROR

Impact: Data

WSM-04673: The session cannot be commited due to underlying error "{2}".

Cause: The resource could not be deleted since it does not exist in the data store.

Action: You don't need to take any action, the resource is not present in the datastore.
Level: 1

Type: ERROR

Impact: Data

WSM-04674: The document "{0}" cannot be validated due to underlying error "{2}".

Cause: Validation failed for a metadata object written in the session.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04674: The document "{0}" cannot be validated due to underlying error "{2}".

Cause: Validation failed for a metadata object written in the session.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04681: The document "{0}" to be modified was not found in the repository due to underlying error "{2}".

Cause: The document was not found in the repository.

Action: Create the document instead of modifying it.
Level: 1

Type: ERROR

Impact: Data

WSM-04681: The document "{0}" to be modified was not found in the repository due to underlying error "{2}".

Cause: The document was not found in the repository.

Action: Create the document instead of modifying it.
Level: 1

Type: ERROR

Impact: Data

WSM-04682: The document "{0}" cannot be modified in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be modified belongs in a store that is different from other write operations in the session.

Action: Modify the document in a different session.
Level: 1

Type: ERROR

Impact: Data

WSM-04682: The document "{0}" cannot be modified in a session spanning multiple stores due to underlying error "{2}".

Cause: The document to be modified belongs in a store that is different from other write operations in the session.

Action: Modify the document in a different session.
Level: 1

Type: ERROR

Impact: Data

WSM-04691: The document "{0}" cannot be found in repository due to underlying error "{2}".

Cause: The document was not found in the repository.

Action: Create the document and try again.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-04691: The document "{0}" cannot be found in repository due to underlying error "{2}".

Cause: The document was not found in the repository.

Action: Create the document and try again.
Level: 1

Type: NOTIFICATION

Impact: Data

WSM-04692: The name "{0}" is invalid for retrieving a document due to the error "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04692: The name "{0}" is invalid for retrieving a document due to the error "{2}".

Cause: The document name is invalid for the repository.

Action: Choose a valid name and try again.
Level: 1

Type: ERROR

Impact: Data

WSM-04693: Version information is not available for document "{0}".

Cause: The document does not exist

Action: Create the document first.
Level: 1

Type: ERROR

Impact: Data

Cause: The repository does not support versioning.

Action: Configure the repository to support versioning.

WSM-04693: Version information is not available for document "{0}".

Cause: The document does not exist

Action: Create the document first.
Level: 1

Type: ERROR

Impact: Data

Cause: The repository does not support versioning.

Action: Configure the repository to support versioning.

WSM-04694: An invalid directory was provided to connect to a file-base MDS repository.

Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04694: An invalid directory was provided to connect to a file-base MDS repository.

Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.

Action: Provide a valid directory and try again.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-04695: The retrieved version of document "{0}" is no longer available.

Cause: A new version of the document was created after it was initially retrieved.

Action: Retry the operation to get the latest version of the document.
Level: 1

Type: ERROR

Impact: Data

WSM-04695: The retrieved version of document "{0}" is no longer available.

Cause: A new version of the document was created after it was initially retrieved.

Action: Retry the operation to get the latest version of the document.
Level: 1

Type: ERROR

Impact: Data

WSM-04696: The operation "{0}" cannot be performed on a closed session.

Cause: A operation was requested on a session that has already been closed.

Action: Create a new repository session and perform the operation again.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04696: The operation "{0}" cannot be performed on a closed session.

Cause: A operation was requested on a session that has already been closed.

Action: Create a new repository session and perform the operation again.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04697: The operation "{0}" cannot be performed on a read-only session.

Cause: A write operation was requested on a read-only session.

Action: Provide the name of a creator to associate with write operations.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: See error message.

Action: Create a new session on a writable repository and try again.

WSM-04697: The operation "{0}" cannot be performed on a read-only session.

Cause: A write operation was requested on a read-only session.

Action: Provide the name of a creator to associate with write operations.
Level: 1

Type: NOTIFICATION

Impact: Configuration

Cause: See error message.

Action: Create a new session on a writable repository and try again.

WSM-04698: Versions {1} to {3} of document "{0}" are not deletable due to underlying error "{2}".

Cause: An I/O error occurred while trying to delete versions of a document from repository.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04698: Versions {1} to {3} of document "{0}" are not deletable due to underlying error "{2}".

Cause: An I/O error occurred while trying to delete versions of a document from repository.

Action: Correct the underlying problem and retry.
Level: 1

Type: ERROR

Impact: Data

WSM-04699: A write lock is not available to delete versions {1} to {3} of document "{0}" due to underlying error "{2}".

Cause: A write lock could not be obtained to delete versions of a document.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-04699: A write lock is not available to delete versions {1} to {3} of document "{0}" due to underlying error "{2}".

Cause: A write lock could not be obtained to delete versions of a document.

Action: Retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-06001: Error obtaining Policy Set.

Cause: Failed to get PolicySet.

Action: Check log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06001: Error obtaining Policy Set.

Cause: Failed to get PolicySet.

Action: Check log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06017: Error converting to the canonical path for the File Policy Resolver.

Cause: An invalid canonical path was passed for the File Policy Resolver.

Action: Verify the canonical path passed for the File Policy Resolver and retry the operation.
Level: 1

Type: ERROR

Impact: Files

WSM-06017: Error converting to the canonical path for the File Policy Resolver.

Cause: An invalid canonical path was passed for the File Policy Resolver.

Action: Verify the canonical path passed for the File Policy Resolver and retry the operation.
Level: 1

Type: ERROR

Impact: Files

WSM-06036: The class cannot be instantiated.

Cause: The system could not instantiate a class.

Action: Consult the Java documentation or Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06036: The class cannot be instantiated.

Cause: The system could not instantiate a class.

Action: Consult the Java documentation or Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06101: The policy set cannot be created for null Service Component Architecture (SCA) node.

Cause: The PolicySet could not be generated for the null Service Component Architecture (SCA) node.

Action: Pass a valid SCA node object.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06101: The policy set cannot be created for null Service Component Architecture (SCA) node.

Cause: The PolicySet could not be generated for the null Service Component Architecture (SCA) node.

Action: Pass a valid SCA node object.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06102: The policy reference URI "{0}" is not valid.

Cause: The Policy Reference URI provided was not valid.

Action: Verify that the Policy Reference URI in the SCA node is correct and the policy exists in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06102: The policy reference URI "{0}" is not valid.

Cause: The Policy Reference URI provided was not valid.

Action: Verify that the Policy Reference URI in the SCA node is correct and the policy exists in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06103: No configuration has been specified for the Policy Accessor.

Cause: The Policy Accessor object could not be initialized because it is not correctly configured.

Action: Call the init method to initialize the Policy Accessor object before invoking this method.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06103: No configuration has been specified for the Policy Accessor.

Cause: The Policy Accessor object could not be initialized because it is not correctly configured.

Action: Call the init method to initialize the Policy Accessor object before invoking this method.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06104: The protocol specified for Policy Accessor is not supported.

Cause: A policy access protocol was specified that was invalid for this environment.

Action: Change protocol to one that is supported by the environment. For J2EE environments, the supported protocols are "local" and "remote"; for J2SE environments, the supported protocols are "classpath", "local", and "remote".
Level: 1

Type: ERROR

Impact: Compliance

WSM-06104: The protocol specified for Policy Accessor is not supported.

Cause: A policy access protocol was specified that was invalid for this environment.

Action: Change protocol to one that is supported by the environment. For J2EE environments, the supported protocols are "local" and "remote"; for J2SE environments, the supported protocols are "classpath", "local", and "remote".
Level: 1

Type: ERROR

Impact: Compliance

WSM-06105: The duplicate policy references are found in the same Service Component Architecture (SCA) binding node.

Cause: The same policy has been attached multiple times and so duplicate policy references were found in the same Service Component Architecture (SCA) binding node.

Action: Remove the duplicate policy references from the SCA binding node by attaching each policy only once.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06105: The duplicate policy references are found in the same Service Component Architecture (SCA) binding node.

Cause: The same policy has been attached multiple times and so duplicate policy references were found in the same Service Component Architecture (SCA) binding node.

Action: Remove the duplicate policy references from the SCA binding node by attaching each policy only once.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06106: The policy reference URI cannot be empty.

Cause: Empty policy references were found in the Service Component Architecture (SCA) node.

Action: Verify the Service Component Architecture (SCA) node and make sure the policy references specify a valid value and the referenced policies exist in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06106: The policy reference URI cannot be empty.

Cause: Empty policy references were found in the Service Component Architecture (SCA) node.

Action: Verify the Service Component Architecture (SCA) node and make sure the policy references specify a valid value and the referenced policies exist in the repository.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06107: The node that is expected is <binding.ws> or <component>. The node {0} passed is not a supported node.

Cause: An unsupported Service Component Architecture (SCA) node was found.

Action: Specify a supported SCA node. Consult Oracle documentation for further details
Level: 1

Type: ERROR

Impact: Compliance

WSM-06107: The node that is expected is <binding.ws> or <component>. The node {0} passed is not a supported node.

Cause: An unsupported Service Component Architecture (SCA) node was found.

Action: Specify a supported SCA node. Consult Oracle documentation for further details
Level: 1

Type: ERROR

Impact: Compliance

WSM-06108: Error initializing the Oracle WSM Policy Resolver because incorrect configuration is passed

Cause: The Policy Resolver did not get created. This could be due to the wrong configuration being passed.

Action: Verify the configuration passed for creating the Policy Resolver. Verify that the correct Policy Accessor protocol is passed.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06108: Error initializing the Oracle WSM Policy Resolver because incorrect configuration is passed

Cause: The Policy Resolver did not get created. This could be due to the wrong configuration being passed.

Action: Verify the configuration passed for creating the Policy Resolver. Verify that the correct Policy Accessor protocol is passed.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06109: Cannot retrieve policies.

Cause: The policies were not retrieved. This may be due to incorrect policy references in the Service Component Architecture (SCA) node.

Action: Verify that the policy references are referring to policies that exist in the repository. Also, ensure that the data store is seeded with policies.
Level: 1

Type: ERROR

Impact: Data

WSM-06109: Cannot retrieve policies.

Cause: The policies were not retrieved. This may be due to incorrect policy references in the Service Component Architecture (SCA) node.

Action: Verify that the policy references are referring to policies that exist in the repository. Also, ensure that the data store is seeded with policies.
Level: 1

Type: ERROR

Impact: Data

WSM-06110: The MetaData Store (MDS) home cannot be null.

Cause: The Policy Repository was not valid because MDS Home is set to null.

Action: Check the mds.home.module property for the correct value for MDS Home.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06110: The MetaData Store (MDS) home cannot be null.

Cause: The Policy Repository was not valid because MDS Home is set to null.

Action: Check the mds.home.module property for the correct value for MDS Home.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06111: The policy name cannot be null.

Cause: The policy name passed was null or empty.

Action: Verify that the policy name is not an empty string, and verify that a null policy name is not being passed.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06111: The policy name cannot be null.

Cause: The policy name passed was null or empty.

Action: Verify that the policy name is not an empty string, and verify that a null policy name is not being passed.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06112: Policies are not supported for a node of type:{0}.

Cause: Policies cannot be retrieved for unsupported Service Component Architecture (SCA) nodes.

Action: Verify that a supported SCA node is provided for retrieving the policy.
Level: 1

Type: WARNING

Impact: Compliance

WSM-06112: Policies are not supported for a node of type:{0}.

Cause: Policies cannot be retrieved for unsupported Service Component Architecture (SCA) nodes.

Action: Verify that a supported SCA node is provided for retrieving the policy.
Level: 1

Type: WARNING

Impact: Compliance

WSM-06113: The configuration name cannot be null or empty.

Cause: The configuration file was either empty or did not exist.

Action: Verify that the configuration file exists and contains policy references to retrieve policies from the Policy Repository.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06113: The configuration name cannot be null or empty.

Cause: The configuration file was either empty or did not exist.

Action: Verify that the configuration file exists and contains policy references to retrieve policies from the Policy Repository.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06114: The home directory for the File Policy Resolver cannot be null.

Cause: The home directory for File Policy Resolver was null.

Action: Verify that a valid home directory is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06114: The home directory for the File Policy Resolver cannot be null.

Cause: The home directory for File Policy Resolver was null.

Action: Verify that a valid home directory is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06115: The path for the File Policy Resolver does not exist.

Cause: The path for File Policy Resolver did not exist.

Action: Ensure that a valid path is passed for File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06115: The path for the File Policy Resolver does not exist.

Cause: The path for File Policy Resolver did not exist.

Action: Ensure that a valid path is passed for File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06116: The path for the File Policy Resolver is not a directory.

Cause: An invalid directory name was passed for the File Policy Resolver.

Action: Verify that a valid directory name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06116: The path for the File Policy Resolver is not a directory.

Cause: An invalid directory name was passed for the File Policy Resolver.

Action: Verify that a valid directory name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06118: The resource name for the File Policy Resolver cannot be null.

Cause: The resource name for the File Policy Resolver is null.

Action: Verify that a valid resource name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06118: The resource name for the File Policy Resolver cannot be null.

Cause: The resource name for the File Policy Resolver is null.

Action: Verify that a valid resource name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06119: The file {0} for the File Policy Resolver does not exist under {1}.

Cause: The file did not exist.

Action: Verify that the file exists at the specified location.
Level: 1

Type: ERROR

Impact: Files

WSM-06119: The file {0} for the File Policy Resolver does not exist under {1}.

Cause: The file did not exist.

Action: Verify that the file exists at the specified location.
Level: 1

Type: ERROR

Impact: Files

WSM-06120: The resource name for the File Policy Resolver cannot be null.

Cause: The resource name for the File Policy Resolver was null.

Action: Ensure that a non-null resource name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06120: The resource name for the File Policy Resolver cannot be null.

Cause: The resource name for the File Policy Resolver was null.

Action: Ensure that a non-null resource name is passed for the File Policy Resolver.
Level: 1

Type: ERROR

Impact: Files

WSM-06121: No policy is found for the policy reference: {0}.

Cause: No policy was found for the specified policy reference.

Action: Verify that the policy exists in the repository for the given policy reference, and that the correct policy reference is passed.
Level: 1

Type: ERROR

Impact: Data

WSM-06121: No policy is found for the policy reference: {0}.

Cause: No policy was found for the specified policy reference.

Action: Verify that the policy exists in the repository for the given policy reference, and that the correct policy reference is passed.
Level: 1

Type: ERROR

Impact: Data

WSM-06122: Error retrieving policies.

Cause: An unexpected error occurred while retrieving the policies from the Policy Manager.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-06122: Error retrieving policies.

Cause: An unexpected error occurred while retrieving the policies from the Policy Manager.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-06123: Error initializing internally the File Policy Resolver: {0} {1}

Cause: An unexpected error occurred while initializing the File Policy Resolver.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-06123: Error initializing internally the File Policy Resolver: {0} {1}

Cause: An unexpected error occurred while initializing the File Policy Resolver.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-06124: Error initializing the Oracle WSM Policy Manager Policy Resolver : {0} {1}.

Cause: An unexpected error occurred while initializing the Policy Manager Policy Resolver. The Policy Manager Policy Resolver was not able to find the property named mds.config

Action: Verify that the property mds.config exists and is referencing a valid property file.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06124: Error initializing the Oracle WSM Policy Manager Policy Resolver : {0} {1}.

Cause: An unexpected error occurred while initializing the Policy Manager Policy Resolver. The Policy Manager Policy Resolver was not able to find the property named mds.config

Action: Verify that the property mds.config exists and is referencing a valid property file.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06125: Error in the XPath expression {0}.

Cause: The XPath Expression for the policy reference for the given Service Component Architecture (SCA) node was invalid.

Action: Verify the XPath for the policy reference within the SCA node.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06125: Error in the XPath expression {0}.

Cause: The XPath Expression for the policy reference for the given Service Component Architecture (SCA) node was invalid.

Action: Verify the XPath for the policy reference within the SCA node.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06128: Error accessing the PolicySet : {0} : {1}.

Cause: An unexpected error occurred while accessing the PolicySet.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06128: Error accessing the PolicySet : {0} : {1}.

Cause: An unexpected error occurred while accessing the PolicySet.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06129: Error parsing the PolicySet : {0} : {1}.

Cause: An unexpected error occurred while parsing the PolicySet.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06129: Error parsing the PolicySet : {0} : {1}.

Cause: An unexpected error occurred while parsing the PolicySet.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06130: Error creating the policy parser.

Cause: The Policy Parser did not get created.

Action: Check the configuration for the Policy Parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06130: Error creating the policy parser.

Cause: The Policy Parser did not get created.

Action: Check the configuration for the Policy Parser.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06132: Error creating a connection to Oracle WSM Policy Manager.

Cause: A failure occurred while connecting to the Policy Manager.

Action: Ensure that the Policy Manager is up and running. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06132: Error creating a connection to Oracle WSM Policy Manager.

Cause: A failure occurred while connecting to the Policy Manager.

Action: Ensure that the Policy Manager is up and running. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06133: Error connecting to Oracle WSM Policy Manager.

Cause: A failure occurred while connecting to Policy Manager J2EE Application.

Action: Before connecting to a Policy Manager, ensure that the Policy Manager is up and running.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06133: Error connecting to Oracle WSM Policy Manager.

Cause: A failure occurred while connecting to Policy Manager J2EE Application.

Action: Before connecting to a Policy Manager, ensure that the Policy Manager is up and running.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06134: The class cannot be found.

Cause: The class could not be found in the classpath.

Action: Verify that the class name is correct in the configuration files and ensure that the class is specified in the classpath variable.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06134: The class cannot be found.

Cause: The class could not be found in the classpath.

Action: Verify that the class name is correct in the configuration files and ensure that the class is specified in the classpath variable.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06135: The class cannot be loaded due to Java 2 security restrictions.

Cause: Some classes were not loaded due to class loading security restrictions.

Action: Contact the site administrator or Java documentation to ensure that the classes have the necessary Java2 security permissions.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06135: The class cannot be loaded due to Java 2 security restrictions.

Cause: Some classes were not loaded due to class loading security restrictions.

Action: Contact the site administrator or Java documentation to ensure that the classes have the necessary Java2 security permissions.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06137: The "mds" policy access protocol is deprecated - use "local" instead.

Cause: A deprecated Policy Accessor Protocol was specified.

Action: Update the configuration to use the standard protocol name.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06137: The "mds" policy access protocol is deprecated - use "local" instead.

Cause: A deprecated Policy Accessor Protocol was specified.

Action: Update the configuration to use the standard protocol name.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06138: The "owsm" policy access protocol is deprecated - use "remote" instead.

Cause: A deprecated Policy Accessor protocol was specified.

Action: Update the configuration to use the standard protocol name.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06138: The "owsm" policy access protocol is deprecated - use "remote" instead.

Cause: A deprecated Policy Accessor protocol was specified.

Action: Update the configuration to use the standard protocol name.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06139: Error closing a stream

Cause: Failure occurred in closing the stream while parsing the configuration file or the policy in the FILE protocol.

Action: Verify that the correct configuration file or policy name is provided.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06139: Error closing a stream

Cause: Failure occurred in closing the stream while parsing the configuration file or the policy in the FILE protocol.

Action: Verify that the correct configuration file or policy name is provided.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06140: Failure finding policy {0} in the classpath roots path {1}.

Cause: The policy did not exist in any of the configured roots.

Action: Correct the reference to point to a policy that exists.
Level: 1

Type: WARNING

Impact: Configuration

Cause: The configured roots are invalid.

Action: Correct the classpath roots to point to the correct locations.

WSM-06140: Failure finding policy {0} in the classpath roots path {1}.

Cause: The policy did not exist in any of the configured roots.

Action: Correct the reference to point to a policy that exists.
Level: 1

Type: WARNING

Impact: Configuration

Cause: The configured roots are invalid.

Action: Correct the classpath roots to point to the correct locations.

WSM-06141: Error initializing Policy Resolver.

Cause: The Policy Resolver was not initialized.

Action: Invoke the init method to initialize the Policy Resolver before executing this method.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06141: Error initializing Policy Resolver.

Cause: The Policy Resolver was not initialized.

Action: Invoke the init method to initialize the Policy Resolver before executing this method.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06142: Unable to retrieve policy store timestamp.

Cause: The Policy Resolver could not connect to Policy Manager to retrieve the policy store timestamp.

Action: Check the MDS configuration file.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06142: Unable to retrieve policy store timestamp.

Cause: The Policy Resolver could not connect to Policy Manager to retrieve the policy store timestamp.

Action: Check the MDS configuration file.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06143: The validation check in the policy "{0}" failed.

Cause: An error occurred while validating the policy.

Action: Ensure that the policy is valid.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06143: The validation check in the policy "{0}" failed.

Cause: An error occurred while validating the policy.

Action: Ensure that the policy is valid.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06144: Null policy subject value is not allowed from JEE application.

Cause: The null policy subject value was passed from JEE application.

Action: Ensure that a valid policy subject is passed from the JEE application.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06144: Null policy subject value is not allowed from JEE application.

Cause: The null policy subject value was passed from JEE application.

Action: Ensure that a valid policy subject is passed from the JEE application.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06145: Internal system error, cannot look up credential

Cause: Failure occurred while looking up credentials.

Action: Internal system configuration error. Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06145: Internal system error, cannot look up credential

Cause: Failure occurred while looking up credentials.

Action: Internal system configuration error. Contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06146: Error deleting the attachment entries.

Cause: Failure occurred while deleting the attachment entries.

Action: Ensure that a valid list of policy subjects for deactivated lifecycle type is passed
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06146: Error deleting the attachment entries.

Cause: Failure occurred while deleting the attachment entries.

Action: Ensure that a valid list of policy subjects for deactivated lifecycle type is passed
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06147: There is mismatch in Policy reference category "{0}" and Policy category "{1}". Policy reference category should match with Policy category.

Cause: Mismatch in expected policy category and fetched policy category.

Action: Confirm that the Policy Reference category is correct and that it matches the Policy category.
Level: 1

Type: WARNING

Impact: Data

WSM-06147: There is mismatch in Policy reference category "{0}" and Policy category "{1}". Policy reference category should match with Policy category.

Cause: Mismatch in expected policy category and fetched policy category.

Action: Confirm that the Policy Reference category is correct and that it matches the Policy category.
Level: 1

Type: WARNING

Impact: Data

WSM-06148: Unable to apply property overrides to Policy

Cause: Unable to apply property overrides to Policy.

Action: Make sure the policy model conforms to the Oracle Web service policy model.
Level: 1

Type: WARNING

Impact: Data

WSM-06148: Unable to apply property overrides to Policy

Cause: Unable to apply property overrides to Policy.

Action: Make sure the policy model conforms to the Oracle Web service policy model.
Level: 1

Type: WARNING

Impact: Data

WSM-06149: The policy reference URI is not valid : {0}

Cause: The Policy Reference URI provided was not valid.

Action: Verify that the Policy Reference URI is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06149: The policy reference URI is not valid : {0}

Cause: The Policy Reference URI provided was not valid.

Action: Verify that the Policy Reference URI is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06150: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.

Cause: The Policy category provided was not valid.

Action: Verify that the Policy category is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06150: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.

Cause: The Policy category provided was not valid.

Action: Verify that the Policy category is correct.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06152: The Policy Cache is not available.

Cause: The Policy Cache is not available.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06152: The Policy Cache is not available.

Cause: The Policy Cache is not available.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06153: Could not access the Policy Cache.

Cause: Cannot access the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06153: Could not access the Policy Cache.

Cause: Cannot access the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06154: Could not initialize Policy Java Object Cache.

Cause: Cannot initialize the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06154: Could not initialize Policy Java Object Cache.

Cause: Cannot initialize the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06155: Could not re-create Policy Java Object Cache.

Cause: Could not re-create the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06155: Could not re-create Policy Java Object Cache.

Cause: Could not re-create the Policy Cache.

Action: You may need to restart the server.
Level: 1

Type: ERROR

Impact: Compliance

WSM-06201: The {0} repository accessor class cannot be accessed due to underlying error "{1}".

Cause: The nullary constructor for the specified accessor is not accessible to the configuration framework.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06201: The {0} repository accessor class cannot be accessed due to underlying error "{1}".

Cause: The nullary constructor for the specified accessor is not accessible to the configuration framework.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06202: The {0} repository accessor class cannot be initialized due to underlying error "{1}".

Cause: A exception was encountered during evaluation of a static initializer for the specified accessor class.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06202: The {0} repository accessor class cannot be initialized due to underlying error "{1}".

Cause: A exception was encountered during evaluation of a static initializer for the specified accessor class.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06203: The {0} repository accessor class cannot be used as a repository accessor because it does not implement the {1} interface.

Cause: The specified accessor does not implement the IRepositoryAccessor interface.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06203: The {0} repository accessor class cannot be used as a repository accessor because it does not implement the {1} interface.

Cause: The specified accessor does not implement the IRepositoryAccessor interface.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06204: The {0} repository accessor class cannot be linked due to underlying error "{1}".

Cause: The specified accessor depends on a class whose signature has changed since the accessor was compiled.

Action: Update the accessor class or revert to an older version of the dependent class.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06204: The {0} repository accessor class cannot be linked due to underlying error "{1}".

Cause: The specified accessor depends on a class whose signature has changed since the accessor was compiled.

Action: Update the accessor class or revert to an older version of the dependent class.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06205: The repository accessor "{0}" cannot be found due to underlying error "{1}".

Cause: The specified accessor was not found.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06205: The repository accessor "{0}" cannot be found due to underlying error "{1}".

Cause: The specified accessor was not found.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06206: The {0} repository accessor class cannot be instantiated due to underlying error "{1}".

Cause: The specified accessor is an abstract class, an interface, an array class, a primitive type, or void, or the class does not have a nullary constructor.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06206: The {0} repository accessor class cannot be instantiated due to underlying error "{1}".

Cause: The specified accessor is an abstract class, an interface, an array class, a primitive type, or void, or the class does not have a nullary constructor.

Action: Specify a valid accessor.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06207: A task scheduler was not available for configuring the {0} repository accessor for context "{1}".

Cause: A task scheduler was not supplied to the configuration framework.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06207: A task scheduler was not available for configuring the {0} repository accessor for context "{1}".

Cause: A task scheduler was not supplied to the configuration framework.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06208: Access to the {0} repository accessor class is denied due to underlying error "{1}".

Cause: The configuration framework does not have permission to instantiate the specified accessor.

Action: Ensure the necessary permissions are granted to the WSM code base.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06208: Access to the {0} repository accessor class is denied due to underlying error "{1}".

Cause: The configuration framework does not have permission to instantiate the specified accessor.

Action: Ensure the necessary permissions are granted to the WSM code base.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06209: An action executor cannot be created for user "{0}" due to underlying error "{1}".

Cause: The configuration framework did not have permission to get an action executor.

Action: Ensure the necessary permissions are granted to the WSM code base.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06209: An action executor cannot be created for user "{0}" due to underlying error "{1}".

Cause: The configuration framework did not have permission to get an action executor.

Action: Ensure the necessary permissions are granted to the WSM code base.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06210: An instance of the {2} bean for the local repository at path "{3}" was not available for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06210: An instance of the {2} bean for the local repository at path "{3}" was not available for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06211: An instance of the {2} bean for the local repository at path "{3}" was provided for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06211: An instance of the {2} bean for the local repository at path "{3}" was provided for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06212: An instance of the {2} bean for a remote repository was not available for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06212: An instance of the {2} bean for a remote repository was not available for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06213: An instance of the {2} bean for a remote repository was provided for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06213: An instance of the {2} bean for a remote repository was provided for configuring the {0} repository accessor for context "{1}".

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06214: A task scheduler was provided for configuring the {0} repository accessor for context "{1}".

Cause: A task scheduler was supplied to the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06214: A task scheduler was provided for configuring the {0} repository accessor for context "{1}".

Cause: A task scheduler was supplied to the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06215: An instance of the {1} bean for the local repository at path "{2}" was not available for configuring the {0} repository accessor for the default context.

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06215: An instance of the {1} bean for the local repository at path "{2}" was not available for configuring the {0} repository accessor for the default context.

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06216: An instance of the {1} bean for the local repository at path "{2}" was provided for configuring the {0} repository accessor for the default context.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06216: An instance of the {1} bean for the local repository at path "{2}" was provided for configuring the {0} repository accessor for the default context.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06217: An instance of the {1} bean for a remote repository was not available for configuring the {0} repository accessor for the default context.

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06217: An instance of the {1} bean for a remote repository was not available for configuring the {0} repository accessor for the default context.

Cause: A bean instance could not be obtained by the configuration framework.

Action: Correct underlying problem and wait for coniguration refresh.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06218: An instance of the {1} bean for a remote repository was provided for configuring the {0} repository accessor for the default context.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06218: An instance of the {1} bean for a remote repository was provided for configuring the {0} repository accessor for the default context.

Cause: A bean instance was obtained by the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06219: A task scheduler was not available for configuring the {0} repository accessor for the default context.

Cause: A task scheduler was not supplied to the configuration framework.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06219: A task scheduler was not available for configuring the {0} repository accessor for the default context.

Cause: A task scheduler was not supplied to the configuration framework.

Action: Provide a task scheduler to the configuration framework.
Level: 1

Type: WARNING

Impact: Configuration

WSM-06220: A task scheduler was provided for configuring the {0} repository accessor for the default context.

Cause: A task scheduler was supplied to the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06220: A task scheduler was provided for configuring the {0} repository accessor for the default context.

Cause: A task scheduler was supplied to the configuration framework.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06221: The password credentials cannot be obtained from the Credential Store.

Cause: Failure occurred while querying for credentials from CSF.

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06221: The password credentials cannot be obtained from the Credential Store.

Cause: Failure occurred while querying for credentials from CSF.

Action: Check CSF configuration.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06222: The credentials passed to the credentials store are expired.

Cause: The Credentials have expired.

Action: Ensure valid credentials are passed
Level: 1

Type: ERROR

Impact: Configuration

WSM-06222: The credentials passed to the credentials store are expired.

Cause: The Credentials have expired.

Action: Ensure valid credentials are passed
Level: 1

Type: ERROR

Impact: Configuration

WSM-06223: The access to the store or credentials is denied.

Cause: The requested access Credentials or Store is denied.

Action: Ensure Store is properly initialized and valid credentials are passed
Level: 1

Type: ERROR

Impact: Configuration

WSM-06223: The access to the store or credentials is denied.

Cause: The requested access Credentials or Store is denied.

Action: Ensure Store is properly initialized and valid credentials are passed
Level: 1

Type: ERROR

Impact: Configuration

WSM-06224: Unexpected exception "{0}" caught when privileged method is called.

Cause: Unexpected exception caught on calling a privileged code.

Action: Check the underlying signature of method called in privileged code
Level: 1

Type: ERROR

Impact: Configuration

WSM-06224: Unexpected exception "{0}" caught when privileged method is called.

Cause: Unexpected exception caught on calling a privileged code.

Action: Check the underlying signature of method called in privileged code
Level: 1

Type: ERROR

Impact: Configuration

WSM-06225: Unable to retrieve credentials for the specified CSF key {0}.

Cause: Credential configuration in the policy accessor configuration file was incorrect.

Action: Configure policy with valid CSF key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06225: Unable to retrieve credentials for the specified CSF key {0}.

Cause: Credential configuration in the policy accessor configuration file was incorrect.

Action: Configure policy with valid CSF key.
Level: 1

Type: ERROR

Impact: Configuration

WSM-06301: Subject Metadata is required when registering a listener.

Cause: A null value was provided for the subject metadata.

Action: Provide a valid metadata.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06301: Subject Metadata is required when registering a listener.

Cause: A null value was provided for the subject metadata.

Action: Provide a valid metadata.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06302: A listener is required for asynchronous notification.

Cause: A null value was provided for asynchronous listener registration.

Action: Provide a valid listener.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06302: A listener is required for asynchronous notification.

Cause: A null value was provided for asynchronous listener registration.

Action: Provide a valid listener.
Level: 1

Type: ERROR

Impact: Programmatic

WSM-06303: The method "{0}" was not called with required permission "{1}"

Cause: The method was not called with required permission

Action: Ensure necessary permissions are granted to the caller before calling the required methods.
Level: 1

Type: ERROR

Impact: Security

WSM-06303: The method "{0}" was not called with required permission "{1}"

Cause: The method was not called with required permission

Action: Ensure necessary permissions are granted to the caller before calling the required methods.
Level: 1

Type: ERROR

Impact: Security

WSM-07501: Failure in Oracle WSM Agent processRequest, category={0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing request failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07501: Failure in Oracle WSM Agent processRequest, category={0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing request failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07502: Failure in Oracle WSM Agent processResponse, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing response failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07502: Failure in Oracle WSM Agent processResponse, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing response failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07503: Failure in Oracle WSM Agent processFault, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing fault failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07503: Failure in Oracle WSM Agent processFault, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.

Cause: Processing fault failed in the security interceptor while enforcing policy.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07504: Failure in Oracle WSM Agent processEvent, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.

Cause: Processing Fabric Lifecycle event failed in security interceptor.

Action: Check the log file for possible causes
Level: 1

Type: ERROR

Impact: Configuration

WSM-07504: Failure in Oracle WSM Agent processEvent, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.

Cause: Processing Fabric Lifecycle event failed in security interceptor.

Action: Check the log file for possible causes
Level: 1

Type: ERROR

Impact: Configuration

WSM-07505: Failure in Oracle WSM Agent initialization, category= {0}, function={1}.

Cause: Agent initialization failed in the security interceptor.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07505: Failure in Oracle WSM Agent initialization, category= {0}, function={1}.

Cause: Agent initialization failed in the security interceptor.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07506: Failure in Oracle WSM Agent processFinish, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.

Cause: Agent finish failed in the security interceptor.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07506: Failure in Oracle WSM Agent processFinish, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.

Cause: Agent finish failed in the security interceptor.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Configuration

WSM-07507: Failure in Oracle WSM Agent, category= {0}, function={1}, stage={2} due to RuntimeException.

Cause: An unexpected RuntimeException was encountered while trying to access security interceptor.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-07507: Failure in Oracle WSM Agent, category= {0}, function={1}, stage={2} due to RuntimeException.

Cause: An unexpected RuntimeException was encountered while trying to access security interceptor.

Action: Check the log file for possible causes and retry the operation.
Level: 1

Type: WARNING

Impact: Data

WSM-07508: Oracle WSM Agent initialization failed due to PolicySet validation errors: {0}, with PolicySet={1}

Cause: Agent not initialized due to PolicySet validation errors

Action: Check the log for detail
Level: 1

Type: ERROR

Impact: Configuration

WSM-07508: Oracle WSM Agent initialization failed due to PolicySet validation errors: {0}, with PolicySet={1}

Cause: Agent not initialized due to PolicySet validation errors

Action: Check the log for detail
Level: 1

Type: ERROR

Impact: Configuration

WSM-07509: Oracle WSM Agent must be initialized with valid properties. Following parameters [{0}] are either Empty or null

Cause: Agent not initialized with valid parameters.

Action: Initialize the Agent with required parameters
Level: 1

Type: ERROR

Impact: Configuration

WSM-07509: Oracle WSM Agent must be initialized with valid properties. Following parameters [{0}] are either Empty or null

Cause: Agent not initialized with valid parameters.

Action: Initialize the Agent with required parameters
Level: 1

Type: ERROR

Impact: Configuration

WSM-07600: Error while copying the message.

Cause: An unexpected error occurred while cloning SOAP or normalized message context.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07600: Error while copying the message.

Cause: An unexpected error occurred while cloning SOAP or normalized message context.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07601: Failure initializing the WSPolicyExecutor class {0}.

Cause: An unexpected error occurred while initializing the policy engine.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07601: Failure initializing the WSPolicyExecutor class {0}.

Cause: An unexpected error occurred while initializing the policy engine.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07602: Failure in WS-Policy Execution due to exception.

Cause: Due to an unexpected error, policy execution failed at runtime.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07602: Failure in WS-Policy Execution due to exception.

Cause: Due to an unexpected error, policy execution failed at runtime.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07603: Failure in log assertion execution caused by exception.

Cause: File I/O problem or SOAP message access problem occurred.

Action: Verify file access permission and the SOAP message.
Level: 1

Type: ERROR

Impact: Files

WSM-07603: Failure in log assertion execution caused by exception.

Cause: File I/O problem or SOAP message access problem occurred.

Action: Verify file access permission and the SOAP message.
Level: 1

Type: ERROR

Impact: Files

WSM-07604: Internal error during policy enforcement.

Cause: An unexpected error occurred while enforcing the policy.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07604: Internal error during policy enforcement.

Cause: An unexpected error occurred while enforcing the policy.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07605: The binding.ws port ID {0} is invalid.

Cause: An unexpected error occurred in the Oracle WSM processEvent API.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07605: The binding.ws port ID {0} is invalid.

Cause: An unexpected error occurred in the Oracle WSM processEvent API.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07606: Policy {0} execution failure.

Cause: Due to an unexpected error, policy execution failed at runtime.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07606: Policy {0} execution failure.

Cause: Due to an unexpected error, policy execution failed at runtime.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07607: Failure in execution of assertion {0} executor class {1}.

Cause: The policy engine failed to execute an assertion.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07607: Failure in execution of assertion {0} executor class {1}.

Cause: The policy engine failed to execute an assertion.

Action: Check the log file for possible causes.
Level: 1

Type: ERROR

Impact: Security

WSM-07608: The assertion type is not valid.

Cause: Policy execution failed due to an invalid assertion.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-07608: The assertion type is not valid.

Cause: Policy execution failed due to an invalid assertion.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-07609: Policy with attachto value of {0} cannot be applied to subject of type {1}.

Cause: The attached policy was incompatible with the subject.

Action: Verify that the subject type and the policy's Attachto value are compatible.
Level: 1

Type: ERROR

Impact: Security

WSM-07609: Policy with attachto value of {0} cannot be applied to subject of type {1}.

Cause: The attached policy was incompatible with the subject.

Action: Verify that the subject type and the policy's Attachto value are compatible.
Level: 1

Type: ERROR

Impact: Security

WSM-07610: Internal error in policy status audit. One or more of the argument passed is null, result:{0}, agentFunction:{1}, policy:{2}, msgCtx:{3}

Cause: An internal error occurred; the enforcement auditor encountered one or more null arguments.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07610: Internal error in policy status audit. One or more of the argument passed is null, result:{0}, agentFunction:{1}, policy:{2}, msgCtx:{3}

Cause: An internal error occurred; the enforcement auditor encountered one or more null arguments.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07611: Failure initializing of enforcement auditor: category={0}, function= {1}, topologyNode={2}.

Cause: An internal error occurred; the enforcement auditor initialization failed.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07611: Failure initializing of enforcement auditor: category={0}, function= {1}, topologyNode={2}.

Cause: An internal error occurred; the enforcement auditor initialization failed.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07612: Failure shutting down enforcement auditor.

Cause: An internal error occurred; the enforcement auditor shutdown failed.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07612: Failure shutting down enforcement auditor.

Cause: An internal error occurred; the enforcement auditor shutdown failed.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07613: Failure enforcing auditing policy.

Cause: An internal error occurred while auditing security or management policy enforcement.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07613: Failure enforcing auditing policy.

Cause: An internal error occurred while auditing security or management policy enforcement.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07614: Failure in Agent initialization due to invalid topology node path. Topology node path cannot be null or empty for non-JSE client. category={0}, function={1}, topologyNode={2}, isRunningInJEE={3}

Cause: Oracle WSM Agent initialization failed due to problem creating and initializing DMS instrumentation. An invalid, null, or empty topology node path was encountered for non-JSE client.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07614: Failure in Agent initialization due to invalid topology node path. Topology node path cannot be null or empty for non-JSE client. category={0}, function={1}, topologyNode={2}, isRunningInJEE={3}

Cause: Oracle WSM Agent initialization failed due to problem creating and initializing DMS instrumentation. An invalid, null, or empty topology node path was encountered for non-JSE client.

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07616: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext

Cause: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07616: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext

Cause: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext

Action: Retry the operation. If the problem persists, contact Oracle Support Services.
Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07617: Policy: {0} contains unsupported assertions.

Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-07617: Policy: {0} contains unsupported assertions.

Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.

Action: Check the assertion type.
Level: 1

Type: ERROR

Impact: Security

WSM-07618: Failed to execute the assertion "{0}" in the conditional policy. {1}

Cause: Failed to execute the assertion

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Security

WSM-07618: Failed to execute the assertion "{0}" in the conditional policy. {1}

Cause: Failed to execute the assertion

Action: Check exception stack trace for details
Level: 1

Type: ERROR

Impact: Security

WSM-07619: Failed to retrieve the Welogic Server subject.

Cause: An error occurred while retrieving Weblogic Server subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-07619: Failed to retrieve the Welogic Server subject.

Cause: An error occurred while retrieving Weblogic Server subject.

Action: Check log file for possible cause.
Level: 1

Type: ERROR

Impact: Security

WSM-07620: Agent cannot enforce policies due to either failure in retrieving polices or error in validations, detail= "{0}".

Cause: Either policies can not be retrieved or Policy/PolicySet have validation errors.

Action: Correct the validation errors and retry again.
Level: 1

Type: ERROR

Impact: Security

WSM-07620: Agent cannot enforce policies due to either failure in retrieving polices or error in validations, detail= "{0}".

Cause: Either policies can not be retrieved or Policy/PolicySet have validation errors.

Action: Correct the validation errors and retry again.
Level: 1

Type: ERROR

Impact: Security

WSM-07621: Oracle WSM Advertisement Engine failed with valid PolicySet, validation errors: [{0}], and PolicySet: [{1}]

Cause: Advertisment failed due to runtime PolicySet validation error in WSMEngineInvoker

Action: Check log for detail to correct Runtime PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-07621: Oracle WSM Advertisement Engine failed with valid PolicySet, validation errors: [{0}], and PolicySet: [{1}]

Cause: Advertisment failed due to runtime PolicySet validation error in WSMEngineInvoker

Action: Check log for detail to correct Runtime PolicySet
Level: 1

Type: ERROR

Impact: Other

WSM-09001: The audit event definitions cannot be found.

Cause: Component audit event definitions were missing.

Action: Check the installation for any missing or corrupted JAR files.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09001: The audit event definitions cannot be found.

Cause: Component audit event definitions were missing.

Action: Check the installation for any missing or corrupted JAR files.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09002: The audit event definitions file cannot be opened.

Cause: Component audit event definitions could not be opened.

Action: Check the installation for any corrupted JAR files, or free up system resources.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09002: The audit event definitions file cannot be opened.

Cause: Component audit event definitions could not be opened.

Action: Check the installation for any corrupted JAR files, or free up system resources.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09003: The audit event definitions file cannot be read.

Cause: Component's audit event definitions were not readable.

Action: Check the installation for any corrupted JAR files.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09003: The audit event definitions file cannot be read.

Cause: Component's audit event definitions were not readable.

Action: Check the installation for any corrupted JAR files.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09004: Component auditing cannot be initialized.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: WARNING

Impact: Logging

WSM-09004: Component auditing cannot be initialized.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: WARNING

Impact: Logging

WSM-09005: It is not possible to verify that the event is enabled.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09005: It is not possible to verify that the event is enabled.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09006: The event cannot be audited. Another attempt will be made to audit the event.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

WSM-09006: The event cannot be audited. Another attempt will be made to audit the event.

Cause:

Action:
Level: 1

Type: WARNING

Impact: Logging

WSM-09007: The event cannot be audited.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09007: The event cannot be audited.

Cause: The audit framework encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09008: A URL cannot be created for {0}.

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09008: A URL cannot be created for {0}.

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09009: Failure parsing the XML file

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09009: Failure parsing the XML file

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09010: Error opening and/or closing the stream

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09010: Error opening and/or closing the stream

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09011: Error writing the XML file

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09011: Error writing the XML file

Cause: XML utility encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09012: Key, {0}, is not found in the resource bundle {1}.

Cause: No key was found in the provided resource bundle.

Action: Add the key to the resource bundle and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09012: Key, {0}, is not found in the resource bundle {1}.

Cause: No key was found in the provided resource bundle.

Action: Add the key to the resource bundle and retry the operation.
Level: 1

Type: ERROR

Impact: Configuration

WSM-09013: Failure shutting down auditing.

Cause: An exception was caught when attempting to shut down the audit framework.

Action: Examine the stack trace for any underlying errors.
Level: 1

Type: WARNING

Impact: Logging

WSM-09013: Failure shutting down auditing.

Cause: An exception was caught when attempting to shut down the audit framework.

Action: Examine the stack trace for any underlying errors.
Level: 1

Type: WARNING

Impact: Logging

WSM-09014: Streaming SOAP message attachment is not being logged.

Cause: SOAP message attachment was not logged because it was a streaming attachment.

Action: Check the logs for the possible causes.
Level: 1

Type: WARNING

Impact: Logging

WSM-09014: Streaming SOAP message attachment is not being logged.

Cause: SOAP message attachment was not logged because it was a streaming attachment.

Action: Check the logs for the possible causes.
Level: 1

Type: WARNING

Impact: Logging

WSM-09015: Interrupted while checking out object from pool.

Cause: Received interrupt while checking out from pool.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09015: Interrupted while checking out object from pool.

Cause: Received interrupt while checking out from pool.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09016: Failure creating transformer using factory {0}.

Cause: Transformer factory failed to create new transformer instance.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09016: Failure creating transformer using factory {0}.

Cause: Transformer factory failed to create new transformer instance.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09017: Failure checking out a transformer instance.

Cause: Failure checking out a transformer instance.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09017: Failure checking out a transformer instance.

Cause: Failure checking out a transformer instance.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09018: A ScheduledExecutorService is required when creating a scheduler wrapper.

Cause: A ScheduledExecutorService was not provided when constructing a wrapper.

Action: Provide a valid ScheduledExecutorService instance.
Level: 1

Type: ERROR

Impact: Other

WSM-09018: A ScheduledExecutorService is required when creating a scheduler wrapper.

Cause: A ScheduledExecutorService was not provided when constructing a wrapper.

Action: Provide a valid ScheduledExecutorService instance.
Level: 1

Type: ERROR

Impact: Other

WSM-09019: An executor requires a task for scheduling.

Cause: A task was not provided when scheduling a task.

Action: Provide a valid task.
Level: 1

Type: ERROR

Impact: Other

WSM-09019: An executor requires a task for scheduling.

Cause: A task was not provided when scheduling a task.

Action: Provide a valid task.
Level: 1

Type: ERROR

Impact: Other

WSM-09020: An executor rejected a task due to error "{0}".

Cause: The ScheduledExecutorService refused to schedule a task.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09020: An executor rejected a task due to error "{0}".

Cause: The ScheduledExecutorService refused to schedule a task.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Other

WSM-09021: A TimerManager is required when creating a scheduler wrapper.

Cause: A TimerManager was not provided when constructing a wrapper.

Action: Provide a valid TimerManager instance.
Level: 1

Type: ERROR

Impact: Other

WSM-09021: A TimerManager is required when creating a scheduler wrapper.

Cause: A TimerManager was not provided when constructing a wrapper.

Action: Provide a valid TimerManager instance.
Level: 1

Type: ERROR

Impact: Other

WSM-09022: A timer cannot schedule a task due to illegal argument error "{0}".

Cause: A task was not provided when scheduling a task.

Action: Provide a valid task.
Level: 1

Type: ERROR

Impact: Other

Cause: The scheduling parameters were negative.

Action: Provide non-negative values.

WSM-09022: A timer cannot schedule a task due to illegal argument error "{0}".

Cause: A task was not provided when scheduling a task.

Action: Provide a valid task.
Level: 1

Type: ERROR

Impact: Other

Cause: The scheduling parameters were negative.

Action: Provide non-negative values.

WSM-09023: A timer cannot schedule a task due to illegal state error "{0}".

Cause: A task could not be scheduled because the underlying TimerManager was stopped.

Action: Schedule the task using a running TimerManager.
Level: 1

Type: ERROR

Impact: Other

WSM-09023: A timer cannot schedule a task due to illegal state error "{0}".

Cause: A task could not be scheduled because the underlying TimerManager was stopped.

Action: Schedule the task using a running TimerManager.
Level: 1

Type: ERROR

Impact: Other

WSM-09024: Failure parsing the XML URL when: {0}, from: {1}

Cause: XML utility parseXMLDocument from URL encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

WSM-09024: Failure parsing the XML URL when: {0}, from: {1}

Cause: XML utility parseXMLDocument from URL encountered an error.

Action: Check the logs for the possible causes.
Level: 1

Type: ERROR

Impact: Logging

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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, then 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.

Hazardous Applications Notice

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 fail-safe, 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.

Trademark Notice

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

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 that have purchased support 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.